Website check
chatgpt.com
In plain English
The site scored an A (93/100), which is a strong result. The most important item is the missing Content Security Policy, a setting that tells browsers which scripts are allowed to run; adding one would make it harder for injected code to steal logins or alter pages. The other finding is informational: a missing CAA record, which would limit which certificate authorities can issue certificates for the domain. Visitors do not need to be worried based on this check alone, since the findings are a hardening gap rather than an active problem.
No Content Security Policy
A Content Security Policy limits which scripts can run, which blunts attacks that inject code to steal logins or change the page.
How to fix: Add a Content-Security-Policy header. Start in report-only mode, then enforce it once nothing breaks.
No CAA record
CAA records limit which certificate authorities may issue certificates for chatgpt.com, which makes a wrongly issued certificate less likely.
How to fix: Add a CAA record naming your certificate provider, for example 0 issue "letsencrypt.org".
What the agent did (13 steps)
- 01Picked up a daily rating check
- 02Looking up chatgpt.com and connecting over HTTPS
- 03Connected over HTTPS: chatgpt.com answered 403
- 04Certificate from Google Trust Services, valid 58 more days (TLSv1.3)
- 05Read the security headers: HSTS, X-Frame-Options, nosniff, Referrer-Policy set; missing CSP
- 06Checked 1 cookie for Secure, HttpOnly and SameSite
- 07No PHP version given away
- 08Found 0 script sources from other sites
- 09Old TLS 1.0/1.1: refused
- 10Plain http:// redirects to HTTPS
- 11security.txt found
- 12Email spoofing protection: SPF set, DMARC set
- 13Scored 93/100, grade A. Writing it up in plain English
Technical details (30)
- ip
- 104.18.32.47
- caa
- tls cipher
- TLS_AES_256_GCM_SHA384
- tls issuer
- Google Trust Services
- tls subject
- chatgpt.com
- tls validTo
- 2026-12-19T21:31:25.000Z
- tls daysLeft
- 58
- tls protocol
- TLSv1.3
- tls authorized
- true
- email spf
- v=spf1 include:_spf.mx.cloudflare.net -all
- email apex
- chatgpt.com
- email dmarc
- v=DMARC1; p=reject; sp=reject; adkim=s; aspf=s; rua=mailto:tdfyvl0n@ag.us.dmarcian.com; ruf=mailto:tdfyvl0n@fr.us.dmarcian.com;
- status
- 403
- cookies
- __cf_bm
- headers server
- cloudflare
- headers referrer-policy
- same-origin
- headers x-frame-options
- SAMEORIGIN
- headers permissions-policy
- accelerometer=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),s...
- headers x-content-type-options
- nosniff
- headers strict-transport-security
- max-age=31536000; includeSubDomains; preload
- finalUrl
- https://chatgpt.com/
- requests
- 3
- timingMs
- 71
- reachable
- true
- redirects
- oldTlsProbe
- rejected
- securityTxt
- true
- httpRedirect
- redirects to https
- thirdPartyScripts
- 0
- thirdPartyScriptHosts
This check is passive and automated: it reads only what a normal visit can see and can miss problems a full audit would find. A good grade is not a guarantee. If you run this site and something here is wrong, the fix steps are a starting point, not a substitute for your host or a security professional.