Overview
Findings
Details
Related
AI-Generated Summary
What this means
chatgpt.com scored 100/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: MX Records & Mail Provider, DNS Configuration, TLS Configuration all passed.
How chatgpt.com compares
Grade distribution across 2612 companies we've scanned. chatgpt.com scores better than 99% of them.
85
A+
25
A
189
A-
197
B+
75
B
362
B-
132
C+
114
C
333
C-
121
D+
95
D
256
D-
628
F
chatgpt.com — Grade A+ (100/100)
2612 companies scanned
Security checks
Each check inspects a different part of chatgpt.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
MTA-STS & TLS Reporting
Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks. Sending servers cannot verify that your mail server requires TLS; No TLSRPT record — TLS delivery failures won't be reported to domain owner.
DNS CAA Records
No CAA records found. Without CAA, any Certificate Authority can issue certificates for this domain. Adding CAA records restricts issuance to authorized CAs only, reducing the risk of misissued certificates.
Cookie Security
Strengths: 1 cookie(s) analyzed; All cookies have Secure flag; All cookies have HttpOnly flag. Issues: 1/1 cookie(s) missing SameSite attribute (__cf_bm).
MX Records & Mail Provider
No MX records found. This domain does not receive email directly — this is intentional for many domains and carries no security risk. If email is expected, verify mail routing via A/AAAA fallback or a mail provider.
DNS Configuration
Strengths: 2 nameservers configured (savanna.ns.cloudflare.com., hassan.ns.cloudflare.com.); DNSSEC enabled; Zone transfers properly restricted.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
TLS Protocol Support
Strengths: TLS 1.3 supported; TLS 1.2 supported; TLS 1.3 supported (strongest). Protocol support: TLS 1.3: Yes, TLS 1.2: Yes, TLS 1.1: No, TLS 1.0: No.
HSTS Header
HSTS enabled: max-age=31536000s (365 days) with includeSubDomains and preload. Meets best-practice configuration.
Security Headers
4/5 security headers present. Missing: CSP.
security.txt (RFC 9116)
Strengths: security.txt found with 7 field(s); Contact: https://bugcrowd.com/openai, mailto:[email protected]; PGP signed (authenticity verifiable); Encryption key provided for secure reporting; Disclosure policy: https://openai.com/policies/coordinated-vulnerability-disclosure-policy; Canonical URL specified; Security hiring link included; Acknowledgments/hall-of-fame link included. Issues: Missing 'Expires' field (required by RFC 9116).
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all); DKIM configured (selectors: default, google, selector1, selector2, s1, s2, k1, dkim, mail, proofpoint, pphosted, pp1, pp2, everlytickey1, everlytickey2, mandrill, mxvault, cm, zendesk1, zendesk2, smtpapi, em, amazonses).
Known Breaches
No known breaches found in public disclosure databases.
CVE Exposure
Detected technologies: cloudflare. (cloudflare detected but excluded from CVE matching — upstream infrastructure). All detected technologies are upstream CDN/proxy infrastructure. No application-level software versions exposed.
Certificate Hygiene
Strengths: Certificate valid, 62 days remaining; Issued by Google Trust Services. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
At a glance
Key data points from the scan.
TLS Version
TLSv1.3
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC Policy
p=reject
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all); DKIM configured (selectors: default, google, selector1, selector2, s1, s2, k1, dkim, mail, proofpoint, pphosted, pp1, pp2, everlytickey1, everlytickey2, mandrill, mxvault, cm, zendesk1, zendesk2, smtpapi, em, amazonses).
SPF Record
Present
v=spf1 -all
Security Headers
4/5 present
Missing: CSP
HSTS
Enabled
HSTS enabled: max-age=31536000s (365 days) with includeSubDomains and preload. Meets best-practice configuration.
SSL Certificate
Valid
Strengths: Certificate valid, 62 days remaining; Issued by Google Trust Services. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
DNSSEC
Enabled
Strengths: 2 nameservers configured (savanna.ns.cloudflare.com., hassan.ns.cloudflare.com.); DNSSEC enabled; Zone transfers properly restricted.