70
claude.com
Findings
4
·
3
·
1
Checks
8 passive
Executive Summary
AI-GENERATED
claude.com scored 70/100, meeting baseline requirements but with 3 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Critical gaps in: HSTS Header. Positive signals: Known Breaches, Security Headers, CVE Exposure all passed.
4 action items identified, including 0 critical. The issues are configuration gaps, not architectural problems. A focused remediation effort of 2–5 days could address all findings.
Action Items
Ordered by priority · 4 items
1
Enable HSTS (HTTP Strict Transport Security)
The HSTS header is missing on claude.com. Without it, connections can be downgraded from HTTPS to HTTP via man-in-the-middle attacks. This is a straightforward server configuration change.
Compliance Impact
PCI-DSS 4.0Req 6.4.1
Required application security controls
NIST 800-53SC-8
Transmission confidentiality and integrity
Remediation Steps
1
Add header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
2
Verify all subdomains support HTTPS before adding includeSubDomains
3
Test with: curl -sI https://claude.com | grep -i strict
4
Submit to hstspreload.org after confirming the header is correct
Unlock the full remediation plan
Get detailed steps, compliance mapping, and ownership for all 4 action items. Free — just enter your work email.
No spam. We'll only contact you about this report.
✓ Report unlocked. Scroll down for full details.
2
Strengthen email authentication configuration
Email authentication is partially configured for claude.com but has gaps. Actions needed: add SPF record; configure DKIM. Until DMARC enforcement is active, spoofed emails may still reach recipients.
Compliance Impact
NIST CSFPR.AC-7
Email authentication is a required access control
Remediation Steps
1
Add SPF record if missing: v=spf1 include:_spf.google.com -all
2
Configure DKIM and publish public key in DNS
3
Verify with: nslookup -type=txt _dmarc.claude.com
3
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for claude.com can be spoofed, potentially redirecting users to malicious sites. This requires coordination with your domain registrar to publish DS records.
Compliance Impact
NIST 800-53SC-20
Secure name/address resolution service
Remediation Steps
1
Check if your DNS provider supports DNSSEC (Cloudflare, Route53, etc.)
2
Enable DNSSEC signing in your DNS provider dashboard
3
Add the DS record to your registrar for .com TLD
4
Verify: dig +dnssec claude.com
4
Upgrade to TLS 1.3
claude.com negotiated TLSv1.2. TLS 1.2 is still compliant under all major security frameworks and is not a vulnerability. TLS 1.3 offers faster handshakes and removes legacy cipher negotiation. This is a best-practice improvement, not a compliance gap.
Remediation Steps
1
Update web server config to prefer TLS 1.3 (nginx: ssl_protocols TLSv1.2 TLSv1.3)
2
Verify: openssl s_client -connect claude.com:443 -tls1_3
Scan Findings
HSTS Header
Critical
TLS Configuration
Warning
DMARC / Email Security
Warning
DNS Configuration
Warning
Known Breaches
Healthy
Security Headers
Healthy
CVE Exposure
Healthy
Certificate Hygiene
Healthy