Is chatgpt.com a scam site? Scam, spam & reviews
Scores & key points
Overview
OpenAIが開発したチャットボット
+119 Show more languages
Caution signals ⓘ
- [Medium] An HTTP error occurred when accessing the landing page.
Reputation
Review summary — chatgpt.com
Overall 80 (Mostly safe)Multiple security indicators are favorable and there are few major risk signals.
Strengths
- Valid SSL/TLS certificate
- HSTS enabled
- SPF configured
- DMARC configured
- Domain age ≥ 1 year
Weaknesses
- CSP not set
- HTTP error on landing page
Detailed review — chatgpt.com
Domain review
Domain created: 2022-11-30T23:59:19Z (≈ 2y 11m). Registrar: MarkMonitor Inc.. Hosting / AS: CLOUDFLARENET, US. Popularity: Tranco #164, OPR 7.06/10. Reputation: GSB clean WebRisk clean. Email security: SPF On, DMARC reject. Certificate valid until: 2026-02-08T20:28:04+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 403 Client error · Server CLOUDFLARENET, US. HSTS Off (preload: Preloaded). Applies 5/6 security headers. DNSSEC Off. Email security: SPF On, DMARC reject. MTA‑STS policy: None. TLS‑RPT Off. security.txt: available (https://chatgpt.com/.well-known/security.txt). Missing cookie attributes: Secure×0 / HttpOnly×0 / SameSite×0. JS obfuscation score 0. Reputation: GSB clean, WebRisk clean → overall Good.
Explanation — strengths and stability
Age: about (≈ 2y 11m) (created on 2022-11-30T23:59:19Z).
GSB clean
WebRisk clean
Certificate valid until: 2026-02-08T20:28:04+00:00.
Email security: SPF On, DMARC reject.
Applies 5/6 security headers.
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.
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.
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.
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-17 11:28:43
Claim website ownership
Performance
Security headers
- HSTS ⓘ
- Content‑Security‑Policy ⓘ
- X‑Content‑Type‑Options ⓘ
- X‑Frame‑Options ⓘ
- Referrer‑Policy ⓘ
- Permissions‑Policy ⓘ
add_header Content-Security-Policy "default-src 'self'; img-src 'self' data:; object-src 'none'; base-uri 'self'";
@ 3600 MX 10 mail.chatgpt.com.
Essentials
DMARC details
v=DMARC1; p=reject; sp=reject; adkim=s; aspf=s; rua=mailto:tdfyvl0n@ag.us.dmarcian.com; ruf=mailto:tdfyvl0n@fr.us.dmarcian.com;v=DMARC1; p=reject; sp=reject; adkim=s; aspf=s; rua=mailto:tdfyvl0n@ag.us.dmarcian.com; ruf=mailto:tdfyvl0n@fr.us.dmarcian.com;Threat insight
- Without HSTS, downgrade and man‑in‑the‑middle attacks can weaken HTTPS enforcement. Enable HSTS and prepare for preload registration.
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)
- The site is blocking automated access, limiting detailed inspection.
- Some cookie security attributes (Secure/HttpOnly/SameSite) are missing.
Confirm that you accessed this site via an official link or in‑app navigation, and before payment or login, verify that the domain in the address bar matches the official one. For session/login cookies, always set Secure, HttpOnly, and SameSite.
Set‑Cookie (samples)
__cf_bm=z6OMeuOxqJwhrJ588mhgdfuC_0qkRaar2MM4Ps5JTeo-1763378861-1.0.1.1-37CpdYbKong_ajGmJIa.ay9Vn5CqgkLNwiWV1bJts13UMwsKaJ99On.trTqou9c34Zn58q6Q_tmhDxCNNjAbS49m_CB8yhLdSMyCtzr2pNY; path=/; expires=Mon, 17-Nov-25 11:57:41 GMT; domain=.chatgpt.com; HttpOnly</code><br><code>__cf_bm=HJC7vxBqrYE1Aj8gbgKACd7qAk_sHGcKHByvzNRPNRo-1763378861-1.0.1.1-MFsUHTbpvOM87O97ECXXqAKGSc21yWp15CdpfdhhytoeK2Cn8k5FvciFEwyzH3cunflvf7tyYBU.2igdoQk7z.MBXjSi6l1CwYivTODx620; path=/; expires=Mon, 17-Nov-25 11:57:41 GMT; domain=.chatgpt.com; HttpOnly; Secure; SameSite=None
Server location ⓘ
History
Change ⓘ --Recently added sites
Reviews
Average - / total 0
Checksum 203d6a6b32aeb93e93949c0f09c7797da04a3efe283f51e84f59c28fc7791a5e
Analyzing
Collecting various signals and public data.
- Start
- Fetch DNS / WHOIS
- Check HTTP response
- Verify SSL/TLS
- Query reputation
- Collect PageSpeed data
- Analyze security headers
- Check email security
- Integrate extended signals
- Build report