Is 5ch.net a scam site? Scam, spam & reviews

Score
95
HTTP status
200
https://5ch.net/
SSL/TLS
Valid
2026-02-26T22:31:34+00:00
Server/AS
CLOUDFLARENET, US
2606:4700:10::ac42:941d
Open site

Scores & key points

Security
Reputation
Scam risk

Overview

Label
5ちゃんねる

1999年に開設された匿名掲示板

Caution signals

  • [Low] Security headers such as HSTS and CSP are missing or insufficient.

Reputation

Open PageRank 4.26 / 10
Tranco 6177 Global
Source: top-1m.csv

Review summary — 5ch.net

Overall 95 (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 — 5ch.net

Domain review

Domain created: 2000-03-01T16:38:39Z (≈ 25y 9m). Registrar: Epik LLC. Hosting / AS: CLOUDFLARENET, US. Popularity: Tranco #6177, OPR 4.26/10. Reputation: GSB clean WebRisk clean. Email security: SPF On, DMARC quarantine. Certificate valid until: 2026-02-26T22:31:34+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 CLOUDFLARENET, US. HSTS Off (preload: Unknown). Applies 0/6 security headers. DNSSEC Off. Email security: SPF On, DMARC quarantine. MTA‑STS policy: None. TLS‑RPT Off. security.txt: available (https://5ch.net/.well-known/security.txt). JS obfuscation score 0. Reputation: GSB clean, WebRisk clean → overall Good.

Explanation — strengths and stability

Age: about (≈ 25y 9m) (created on 2000-03-01T16:38:39Z).

GSB clean

WebRisk clean

Certificate valid until: 2026-02-26T22:31:34+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.

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

Estimated domain age
25y 9m
Registrar
Epik LLC
Registrant / organization
Anonymize LLC
SSL valid
Yes
SSL expires
2026-02-26T22:31:34+00:00
HTTP status
200
Server / ASN
CLOUDFLARENET, US
Final URL
https://5ch.net/
SPF
Yes
DMARC
Yes
CT wildcard usage
Yes
HSTS preload
Unknown
security.txt
Yes
TLS‑RPT receivers
Absent
Domain creation date
2000-03-01T16:38:39Z
Hosting / AS
CLOUDFLARENET
GSB status
No match
WebRisk status
No match
DMARC policy
quarantine
PSI mobile
79
PSI desktop
95
DNSSEC
Absent
Legal/contact pages
No
Structured data: Organization
Absent
Structured data: contactPoint
Absent
Registry risk (0–100)
5
dmarc_p
quarantine
dmarc_sp
quarantine
dmarc_align
-/s
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
Registration Possible

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:34:39
Email

Traffic signals

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

Performance

Field LCP1158ms
Field INP-ms
Field CLS0
Lab LCP4136.5ms
Lab TBT96.5ms
Mobile score79
Lab LCP1294.7ms
Lab TBT55.5ms
Desktop score95
https://5ch.net/

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;

Domain lineage

  1. 2000-03-01
    Domain registered: 2000-03-01T16:38:39Z

Essentials

Google Safe Browsing No match
Google Web Risk No match
AbuseIPDB 0%
SPF Configured
DMARC quarantine
DNSSEC No
Cookie security Absent
Mixed content (http) 0
Legal pages Absent
DMARC details
DMARC policy (p): quarantine
Organizational policy (sp): quarantine
SPF alignment (aspf): s
TXT: v=DMARC1;p=quarantine;sp=quarantine;pct=100;ri=86400;aspf=s;fo=1v=DMARC1;p=quarantine;sp=quarantine;pct=100;ri=86400;aspf=s;fo=1
HTTP status200
Server CLOUDFLARENET, US
CDN / Hosting Cloudflare CDN
HSTSNo
Valid until2026-02-26T22:31:34+00:00
IssuerGoogle Trust Services / WE1
Registrant / organizationAnonymize LLC
RegistrarEpik LLC
ASN13335
Network104.16.0.0/12
Title5ちゃんねる
Final URL: https://5ch.net/

Threat insight

Mostly safe (risk 7/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.
  • Suspicious JavaScript patterns detected

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 20/100)
  • Suspicious JavaScript obfuscation patterns have been observed.

If unexpected popups, wallet connection requests, or download prompts appear, cancel once and re‑check via official announcements or community channels.

HTTP status (deep) 200
Set‑Cookie (count) 0
Cookie security insufficient Secure×0 / HttpOnly×0 / SameSite×0
HTTP resources (deep) 0
Top third‑party hosts 4
Suspicious JS patterns 1
Collection time: 2025-11-30T05:34:39+00:00
js.ad-stir.com googletagmanager.com hb.vntsm.com i.imgur.com

Social

  • X
  • YouTube

Platforms that this site may be using.

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.

Server location

- (-) · ASN 13335 / CLOUDFLARENET

History

Change --

Recently added sites

Reviews

Average - / total 0

Checksum b094afa92b0b88710c6f2297e5a3aa052084db00ef60b0eacd9fcbe0623a080b

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