Is hatena.ne.jp a scam site? Scam, spam & reviews

Score
83
HTTP status
200
https://www.hatena.ne.jp:443/
SSL/TLS
Valid
2026-10-10T23:59:59+00:00
Server/AS
nginx
52.195.124.152
Open site

Scores & key points

Security
Reputation
Scam risk

Overview

Label
はてな

日本のインターネットサービス会社

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 5.01 / 10
Tranco 2401 Global
Source: top-1m.csv

Review summary — hatena.ne.jp

Overall 83 (Mostly safe)

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

Strengths

  • Valid SSL/TLS certificate
  • SPF configured
  • DMARC configured

Weaknesses

  • HSTS not set
  • CSP not set

Detailed review — hatena.ne.jp

Domain review

Hosting / AS: nginx — Japan. Popularity: Tranco #2401, OPR 5.01/10. Reputation: GSB clean WebRisk clean. Email security: SPF On, DMARC quarantine. Certificate valid until: 2026-10-10T23: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 nginx. HSTS Off (preload: Unknown). Applies 2/6 security headers. DNSSEC Off. Email security: SPF On, DMARC quarantine. MTA‑STS policy: None. TLS‑RPT Off. security.txt: available (https://hatena.ne.jp/.well-known/security.txt). Missing cookie attributes: Secure×1 / HttpOnly×1 / SameSite×1. JS obfuscation score 0. Reputation: GSB clean, WebRisk clean → overall Good.

Explanation — strengths and stability

GSB clean

WebRisk clean

Certificate valid until: 2026-10-10T23:59:59+00:00.

Email security: SPF On, DMARC quarantine.

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.

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

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

SSL valid
Yes
SSL expires
2026-10-10T23:59:59+00:00
HTTP status
200
Server / ASN
nginx / AMAZON-02, US
Final URL
https://www.hatena.ne.jp:443/
SPF
Yes
DMARC
Yes
CT wildcard usage
No
HSTS preload
Unknown
security.txt
Yes
TLS‑RPT receivers
Absent
Hosting / AS
AMAZON-02
Hosting country
Japan
GSB status
No match
WebRisk status
No match
DMARC policy
quarantine
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@hatena.ne.jp
dmarc_ruf
mailto:dmarc@hatena.ne.jp
mixed_http
0
cookie_no_secure
1
cookie_no_httponly
1
cookie_no_samesite
1
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
Registration Possible 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-22 18:25:29
Email

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
Lab LCP-ms
Lab TBT-ms
Desktop score-
Desktop measurement error: request_failed
https://www.hatena.ne.jp:443/

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'";
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: b=$1$S5QfuXKJ$2xGYErBH9Y1db1hTjwI0d/

Essentials

Google Safe Browsing No match
Google Web Risk No match
AbuseIPDB -
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): quarantine
Aggregate reports (rua): mailto:dmarc@hatena.ne.jp
Failure reports (ruf): mailto:dmarc@hatena.ne.jp
TXT: v=DMARC1; p=quarantine; rua=mailto:dmarc@hatena.ne.jp; ruf=mailto:dmarc@hatena.ne.jpv=DMARC1; p=quarantine; rua=mailto:dmarc@hatena.ne.jp; ruf=mailto:dmarc@hatena.ne.jp
HTTP status200
Server nginx
CDN / Hosting AWS CloudFront
HSTSNo
Valid until2026-10-10T23:59:59+00:00
IssuerAmazon / Amazon RSA 2048 M04
Registrant / organizationAMAZON-02, US
Registrar-
ASN16509
Network52.194.0.0/15
Titleはてな
Final URL: https://www.hatena.ne.jp:443/

Threat insight

Mostly safe (risk 8/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.

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) 1
Cookie security insufficient Secure×1 / HttpOnly×1 / SameSite×1
HTTP resources (deep) 0
Top third‑party hosts 2
Collection time: 2025-11-22T18:25:29+00:00
cdn-ak2.favicon.st-hatena.com googletagmanager.com
Iframe hosts
googletagmanager.com
Set‑Cookie (samples)
b=$1$43jxztjM$KcTEOXs7aNWmr8ho3oy4F0; expires=Fri, 17-Nov-2045 18:25:29 GMT; domain=hatena.ne.jp; path=/

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

Japan (JP) · ASN 16509 / AMAZON-02

History

Change --

Recently added sites

Reviews

Average - / total 0

Checksum e4f3abe01fd13acbd69a14c60d3716f3f68ff376adf1d6bc8ff0a173a23b4896

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