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

Score
80
HTTP status
302
https://nikkei.com/
SSL/TLS
Valid
2026-11-22T23:59:59+00:00
Server/AS
AMAZON-02, US
2600:9000:a717:b171:7f68:c620:6880:1f5a
Open site

Scores & key points

Security
Reputation
Scam risk

Caution signals

No clear warnings detected.

Reputation

Open PageRank 6.18 / 10
Tranco 755 Global
Source: top-1m.csv

Review summary — nikkei.com

Overall 80 (Mostly safe)

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

Strengths

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

Weaknesses

  • HSTS not set
  • CSP not set
  • SPF not configured

Detailed review — nikkei.com

Domain review

Domain created: 1995-05-09T04:00:00Z (≈ 30y 7m). Registrar: Japan Registry Services Co.,Ltd.(JPRS). Hosting / AS: AMAZON-02, US — United States. Popularity: Tranco #755, OPR 6.18/10. Reputation: GSB clean WebRisk clean. Email security: SPF Off, DMARC quarantine. Certificate valid until: 2026-11-22T23: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 302 Redirect · Server AMAZON-02, US. HSTS Off (preload: Unknown). Applies 0/6 security headers. DNSSEC Off. Email security: SPF Off, DMARC quarantine. MTA‑STS policy: None. TLS‑RPT Off. security.txt: available (https://nikkei.com/security.txt). JS obfuscation score 0. Reputation: GSB clean, WebRisk clean → overall Good.

Explanation — strengths and stability

Age: about (≈ 30y 7m) (created on 1995-05-09T04:00:00Z).

GSB clean

WebRisk clean

Certificate valid until: 2026-11-22T23:59:59+00:00.

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.

Without MTA‑STS, SMTP TLS enforcement is weaker.

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

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

Estimated domain age
30y 7m
Registrar
Japan Registry Services Co.,Ltd.(JPRS)
SSL valid
Yes
SSL expires
2026-11-22T23:59:59+00:00
HTTP status
302
Server / ASN
AMAZON-02, US
Final URL
https://nikkei.com/
SPF
No
DMARC
Yes
CT wildcard usage
No
HSTS preload
Unknown
security.txt
Yes
TLS‑RPT receivers
Absent
Domain creation date
1995-05-09T04:00:00Z
Hosting / AS
AMAZON-02
Hosting country
United States
GSB status
No match
WebRisk status
No match
DMARC policy
quarantine
PSI mobile
80
PSI desktop
97
DNSSEC
Absent
Legal/contact pages
No
Structured data: Organization
Absent
Structured data: contactPoint
Absent
Registry risk (0–100)
5
dmarc_p
quarantine
dmarc_rua
mailto:dmarc-nikkeicom@mx.nikkei.com
mixed_http
0
JS obfuscation score
0
Payment logo count
0
Hidden text ratio (%)
0
Cross‑domain POST form count
0
External host logos/icons
0
YARA matches
0

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-22 18:34:37
Email

Traffic signals

UTM source -
UTM medium -
ref / from -
Shortened URLs on page 0

Performance

Field LCP1211ms
Field INP-ms
Field CLS0
Lab LCP4081ms
Lab TBT109ms
Mobile score80
Lab LCP911ms
Lab TBT116.5ms
Desktop score97
https://nikkei.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;
Configure SPF
v=spf1 include:_spf.google.com ~all
Add MX records
@  3600  MX  10  mail.nikkei.com.

Domain lineage

  1. 1995-05-09
    Domain registered: 1995-05-09T04:00:00Z

Essentials

Google Safe Browsing No match
Google Web Risk No match
AbuseIPDB -
SPF -
DMARC Configured
DNSSEC No
Cookie security Absent
Mixed content (http) 0
Legal pages Absent
DMARC details
DMARC policy (p): quarantine
Aggregate reports (rua): mailto:dmarc-nikkeicom@mx.nikkei.com
TXT: v=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc-nikkeicom@mx.nikkei.comv=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc-nikkeicom@mx.nikkei.com
HTTP status302
Server AMAZON-02, US
CDN / Hosting AWS CloudFront
HSTSNo
Valid until2026-11-22T23:59:59+00:00
IssuerAmazon / Amazon RSA 2048 M04
Registrant / organizationAMAZON-02, US
RegistrarJapan Registry Services Co.,Ltd.(JPRS)
ASN16509
Network35.71.64.0/18
Title302 Found
Final URL: https://nikkei.com/

Threat insight

Mostly safe (risk 11/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.
  • Without SPF, resistance to email sender spoofing is low. We recommend setting SPF records on any domain that sends email.

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)

Mostly safe (deep 10/100)
  • Some cookie security attributes (Secure/HttpOnly/SameSite) are missing.

For session/login cookies, always set Secure, HttpOnly, and SameSite.

HTTP status (deep) 200
Set‑Cookie (count) 5
Cookie security insufficient Secure×4 / HttpOnly×5 / SameSite×4
HTTP resources (deep) 0
Top third‑party hosts 5
Collection time: 2025-11-22T18:34:37+00:00
article-image-ix.nikkei.com nikkei.com cdn.speedcurve.com partsa.nikkei.com cf-images.ap-northeast-1.prod.boltdns.net
Set‑Cookie (samples)
atlasId=6922023d.na0o33jz4rng9lixcwg0rmoawaoebr3y; Domain=.nikkei.com; Path=/; Max-Age=157680000; SameSite=Lax; Secure</code><br><code>RNikkeiAuth=deleted; expires=Thu, 01 Jan 1970 00:00:00 GMT</code><br><code>RNikkeiUserInfo=deleted; expires=Thu, 01 Jan 1970 00:00:00 GMT</code><br><code>RNikkeiAuth=deleted; domain=nikkei.com; expires=Thu, 01 Jan 1970 00:00:00 GMT</code><br><code>RNikkeiUserInfo=deleted; domain=nikkei.com; expires=Thu, 01 Jan 1970 00:00:00 GMT

User scenarios

If you make a payment on this site

No strong malicious signs were found, but online payments always carry some risk. Double-check the amount, payee and refund policy before you pay.

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.

Server location

United States (US) · ASN 16509 / AMAZON-02

History

Change --

Recently added sites

Reviews

Average - / total 0

Checksum 23720b657b342a824a1acd535b2243b9dd503e8bff91f493f41c6be32f5825fc

Analyzing

Collecting various signals and public data.

  1. Start
  2. Fetch DNS / WHOIS
  3. Check HTTP response
  4. Verify SSL/TLS
  5. Query reputation
  6. Collect PageSpeed data
  7. Analyze security headers
  8. Check email security
  9. Integrate extended signals
  10. Build report