Is asahi.com a scam site? Scam, spam & reviews

Score ⓘ

HTTP status ⓘ

200

https://www.asahi.com/

SSL/TLS ⓘ

Valid

2026-02-06T23:59:59+00:00

Server/AS ⓘ

AKAMAI-AS, US

118.214.69.9

Open site

Scores & key points

Security

Reputation

Scam risk

Overview

Label

朝日新聞デジタル

朝日新聞社が運営するニュースサイト

Sources:

Wikidata Wikipedia (Japanese)

Caution signals ⓘ

[Low] Security headers such as HSTS and CSP are missing or insufficient.
[Low] Cookie security attributes are insufficient (total 3).

Reputation

Open PageRank ⓘ 6.07 / 10

Tranco ⓘ 2941 Global

Source: top-1m.csv

Review summary — asahi.com

Overall 89 (Mostly safe)

Multiple security indicators are favorable and there are few major risk signals.

Strengths

Valid SSL/TLS certificate
SPF configured
DMARC configured
Domain age ≥ 1 year

Weaknesses

HSTS not set
CSP not set

Detailed review — asahi.com

Domain review

Domain created: 1995-07-29T04:00:00Z (≈ 30y 4m). Registrar: Japan Registry Services Co.,Ltd.(JPRS). Hosting / AS: AKAMAI-AS, US — South Korea. Popularity: Tranco #2941, OPR 6.07/10. Reputation: GSB clean WebRisk clean. Email security: SPF On, DMARC None. Certificate valid until: 2026-02-06T23:59:59+00:00.

Shop / transaction review

No mixed content detected. No mixed content detected. Structured data: Organization Absent, contactPoint Absent. Hidden text ratio 0%.

Technical review

HTTP 200 Success · Server AKAMAI-AS, US. HSTS Off (preload: Unknown). Applies 0/6 security headers. DNSSEC Off. Email security: SPF On, DMARC None. MTA‑STS policy: None. TLS‑RPT Off. security.txt: not available. Missing cookie attributes: Secure×1 / HttpOnly×1 / SameSite×1. JS obfuscation score 0. Reputation: GSB clean, WebRisk clean → overall Good.

Explanation — strengths and stability

Age: about (≈ 30y 4m) (created on 1995-07-29T04:00:00Z).

GSB clean

WebRisk clean

Certificate valid until: 2026-02-06T23:59:59+00:00.

Email security: SPF On, DMARC none.

No mixed content detected.

Looking at operator information together with trust metrics helps you judge brand/merchant consistency and the likelihood of long‑term operation.

Checking payment page security (HTTPS enforcement, form target host consistency, script integrity) along with customer support and return policy gives a more accurate sense of real‑world trust.

In parallel, applying security headers, automated certificate renewal, email domain protection (DMARC/TLS‑RPT), and removing mixed content will improve overall reliability and delivery/search stability.

Explanation — risks and areas to improve

Without HSTS, downgrade and man‑in‑the‑middle attacks can weaken HTTPS enforcement. Enable HSTS and prepare for preload registration.

Missing key security headers leaves the site vulnerable to clickjacking, MIME sniffing, and data leakage.

Without DNSSEC, trust relies solely on parent name servers and DNS tampering risks can be higher in some environments.

If DMARC is absent or set to p=none, protection against sender spoofing is weak. Consider quarantine/reject policies.

Without MTA‑STS, SMTP TLS enforcement is weaker.

Without TLS‑RPT, it is harder to collect TLS failure signals and operational insight.

Without security.txt, the vulnerability disclosure channel is unclear and response may be delayed.

Cookies without Secure / HttpOnly / SameSite can be vulnerable to theft or session fixation attacks.

Estimated domain age ⓘ

30y 4m

Registrar ⓘ

Japan Registry Services Co.,Ltd.(JPRS)

SSL valid ⓘ

Yes

SSL expires ⓘ

2026-02-06T23:59:59+00:00

HTTP status ⓘ

200

Server / ASN ⓘ

AKAMAI-AS, US

Final URL ⓘ

https://www.asahi.com/

SPF

Yes

DMARC

Yes

CT wildcard usage ⓘ

HSTS preload ⓘ

Unknown

security.txt ⓘ

TLS‑RPT receivers ⓘ

Absent

Domain creation date ⓘ

1995-07-29T04:00:00Z

Hosting / AS ⓘ

AKAMAI-AS

Hosting country ⓘ

South Korea

GSB status ⓘ

No match

WebRisk status ⓘ

No match

DMARC policy

None

DNSSEC ⓘ

Absent

Legal/contact pages

Structured data: Organization ⓘ

Absent

Structured data: contactPoint ⓘ

Absent

Registry risk (0–100) ⓘ

dmarc_p ⓘ

None

dmarc_rua ⓘ

mailto:tech-dmarc-report@asahi.com,mailto:ci-dmarc@asahi.com

mixed_http ⓘ

cookie_no_secure ⓘ

cookie_no_httponly ⓘ

cookie_no_samesite ⓘ

JS obfuscation score ⓘ

Payment logo count ⓘ

Hidden text ratio (%) ⓘ

Cross‑domain POST form count ⓘ

External host logos/icons ⓘ

YARA matches ⓘ

Registration Possible Deals Helpdesk

This analysis is an automated, data‑based opinion for reference only. Please verify the information yourself before paying or downloading anything.

About this report

First analysis: -
Last updated: 2025-11-30 05:48:01

Traffic signals

UTM source -

UTM medium -

ref / from -

Shortened URLs on page 0

Performance

Field LCPⓘ-ms

Field INPⓘ-ms

Field CLSⓘ-

Lab LCPⓘ-ms

Lab TBTⓘ-ms

Mobile scoreⓘ-

Mobile measurement error: request_failed

Open PageSpeed (mobile)

Lab LCPⓘ-ms

Lab TBTⓘ-ms

Desktop scoreⓘ-

Desktop measurement error: request_failed

Open PageSpeed (desktop)

https://www.asahi.com/

Security headers

HSTS ⓘ
Content‑Security‑Policy ⓘ
X‑Content‑Type‑Options ⓘ
X‑Frame‑Options ⓘ
Referrer‑Policy ⓘ
Permissions‑Policy ⓘ

Enable HSTS

ⓘ

add_header Strict-Transport-Security "max-age=15552000; includeSubDomains; preload" always;

Set CSP

This is a minimal CSP example. Adjust allowed sources to your project.

ⓘ

add_header Content-Security-Policy "default-src 'self'; img-src 'self' data:; object-src 'none'; base-uri 'self'";

Prevent content type sniffing

ⓘ

add_header X-Content-Type-Options "nosniff" always;

Prevent clickjacking

ⓘ

add_header X-Frame-Options "SAMEORIGIN" always;

Set Referrer‑Policy

ⓘ

add_header Referrer-Policy "strict-origin-when-cross-origin" always;

Set Permissions‑Policy

ⓘ

add_header Permissions-Policy "geolocation=(); microphone=(); camera=()" always;

Add security attributes to cookies

ⓘ

Set-Cookie: name=value; Path=/; Secure; HttpOnly; SameSite=Lax

Examples: LocChecked=1

Domain lineage

1995-07-29

Domain registered: 1995-07-29T04:00:00Z

Essentials

Google Safe Browsingⓘ No match

Google Web Riskⓘ No match

AbuseIPDBⓘ 0%

SPFⓘ Configured

DMARCⓘ Configured

DNSSECⓘ No

Cookie security ⓘ Secure×1 / HttpOnly×1 / SameSite×1

Mixed content (http)ⓘ 0

Legal pages ⓘ Absent

DMARC details

DMARC policy (p): none

Aggregate reports (rua): mailto:tech-dmarc-report@asahi.com,mailto:ci-dmarc@asahi.com

TXT:

v=DMARC1; p=none; rua=mailto:tech-dmarc-report@asahi.com,mailto:ci-dmarc@asahi.com;v=DMARC1; p=none; rua=mailto:tech-dmarc-report@asahi.com,mailto:ci-dmarc@asahi.com;

HTTP statusⓘ200

Server ⓘ AKAMAI-AS, US

CDN / Hosting ⓘ Akamai CDN

HSTSⓘNo

Valid untilⓘ2026-02-06T23:59:59+00:00

IssuerⓘDigiCert Inc / DigiCert TLS RSA SHA256 2020 CA1

Registrant / organizationⓘAKAMAI-AS, US

RegistrarⓘJapan Registry Services Co.,Ltd.(JPRS)

ASNⓘ16625

Networkⓘ118.215.0.0/17

Titleⓘ朝日新聞：朝日新聞社のニュースサイト

Final URL: https://www.asahi.com/

Threat insight

Mostly safe (risk 13/100)

Without HSTS, downgrade and man‑in‑the‑middle attacks can weaken HTTPS enforcement. Enable HSTS and prepare for preload registration.
Missing key security headers leaves the site vulnerable to clickjacking, MIME sniffing, and data leakage.
HTTP resources found on HTTPS page

The risk score of this site is calculated by combining browser security headers, SSL status, mixed content, email domain protection (SPF/DMARC), redirect/obfuscation patterns, and the results of Google Safe Browsing and WebRisk. There are currently few clear signs of malicious behavior, but insufficient security headers or email protection can increase the risk of phishing or man‑in‑the‑middle attacks. Before entering important information, re‑check the domain spelling and how you reached the site (ads, DMs, shortened URLs, etc.). Before entering payment or personal information, verify operator information (company/contact), HTTPS enforcement, DMARC/TLS‑RPT, and check for mixed content.

Deep scan (HTML / headers)

Caution (deep 56/100)

Unencrypted (HTTP) resources are being loaded.
Some cookie security attributes (Secure/HttpOnly/SameSite) are missing.
The site heavily relies on third‑party resources.

If possible, configure the site to use HTTPS only and replace HTTP resources in the page with HTTPS. For session/login cookies, always set Secure, HttpOnly, and SameSite.

HTTP status (deep) 200

Set‑Cookie (count) 1

Cookie security insufficient Secure×1 / HttpOnly×1 / SameSite×1

HTTP resources (deep) 1

Top third‑party hosts 8

Collection time: 2025-11-30T05:48:01+00:00

asahicom.jp asahi.com googletagmanager.com contents.comment.digital.asahi.com securepubads.g.doubleclick.net cdnjs.cloudflare.com i.ytimg.com cdnjs.cloudflare.com

Show examples of HTTP resources

http://www.asahicom.jp/images/logo/top/logo_comment_sakura_osamu.jpg

Iframe hosts

googletagmanager.com

Set‑Cookie (samples)

LocChecked=1;expires=Sun, 30 Nov 2025 05:48:02 GMT; path=/;

User scenarios

If you make a payment on this site

Some technical or reputation signals suggest caution. Check the address bar, HTTPS and browser warnings before entering payment details. Mixed or non-encrypted (HTTP) resources or weak TLS can expose payment data or session tokens on some networks.

If you log in or enter personal data

No clear malicious patterns were found, but treat passwords and 2FA codes as highly sensitive. Avoid reusing passwords across sites. Missing cookie security attributes or cross-domain POST forms can make sessions easier to steal or misuse. After logging in, watch for unusual account or billing activity.