Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
yahoo.com scored 78/100, meeting baseline requirements but with 5 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Critical gaps in: Cookie Security. Positive signals: MX Records & Mail Provider, DNS CAA Records, TLS Configuration 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.
How yahoo.com compares
Grade distribution across 2598 companies we've scanned. yahoo.com scores better than 59% of them.
83
A+
25
A
190
A-
196
B+
75
B
362
B-
129
C+
114
C
330
C-
119
D+
95
D
252
D-
628
F
yahoo.com — Grade C+ (78/100)
2598 companies scanned
Security checks
Each check inspects a different part of yahoo.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
Cookie Security
Strengths: 4 cookie(s) analyzed. Issues: 2/4 cookie(s) missing Secure flag (AWSALBTG, AWSALBTG); 4/4 cookie(s) missing HttpOnly flag (AWSALBTG, AWSALBTGCORS, AWSALBTG...); 2/4 cookie(s) missing SameSite attribute (AWSALBTG, AWSALBTG).
MTA-STS & TLS Reporting
Strengths: MX patterns specified: *.am0.yahoodns.net, *.mail.gm0.yahoodns.net, *.mail.am0.yahoodns.net; SMTP TLS Reporting (TLSRPT) configured — delivery failures will be reported. Issues: MTA-STS in testing mode — TLS failures are reported but not enforced; MTA-STS max_age is only 1 day(s) — should be at least 7 days.
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); SPF record present. Issues: No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
Known Breaches
1 breach(es) found (1 verified). Total accounts affected: 453,427. Breaches: Yahoo (2012-07-11, 453,427 accounts).
DNS Configuration
Strengths: 5 nameservers configured (ns5.yahoo.com., ns4.yahoo.com., ns3.yahoo.com., ns2.yahoo.com.); 3 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
Security Headers
3/5 security headers present. Missing: X-Frame-Options, Permissions-Policy.
MX Records & Mail Provider
Strengths: Mail handled by Yahoo Mail; 3 MX record(s) configured; Multiple MX records provide redundancy; All MX records share the same priority (1) — round-robin load balancing (no primary/backup distinction).
DNS CAA Records
Strengths: CAA records configured (4 record(s)); Authorized CAs: digicert.com, sectigo.com, globalsign.com; Violation reporting (iodef) configured.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-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.
security.txt (RFC 9116)
Strengths: security.txt found with 6 field(s); Contact: mailto:[email protected], https://app.intigriti.com/programs/yahoo/yahoobugbounty/detail; Disclosure policy: https://legal.yahoo.com/xw/en/yahoo/coordinated-vulnerability-disclosure-program-policy/index.html; Security hiring link included; Acknowledgments/hall-of-fame link included. Issues: security.txt expired 109 days ago (2025-12-31T12:00:00.0Z); Not PGP signed (recommended for authenticity).
HSTS Header
HSTS enabled: max-age=31536000s (365 days). Missing includeSubDomains — subdomains not covered. Missing preload directive.
CVE Exposure
Detected technologies: ATS. No version information exposed — CVE matching not possible (this is good practice).
Certificate Hygiene
Strengths: Certificate valid, 129 days remaining; Issued by DigiCert Inc. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
Recommended actions
4 items
Steps to improve yahoo.com's security grade, ranked by impact.
1
Strengthen email authentication configuration
Email authentication is partially configured for yahoo.com but has gaps. Actions needed: 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
How to fix this
1
Configure DKIM and publish public key in DNS
2
Verify with: nslookup -type=txt _dmarc.yahoo.com
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Review unverified breach disclosure
yahoo.com appears in an unverified breach report. This may be a false positive or data aggregation error. Investigate to confirm or rule out exposure.
How to fix this
1
Review the breach details on haveibeenpwned.com
2
Cross-reference with internal incident records
3
If confirmed, follow breach response procedures
3
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for yahoo.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
How to fix this
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 yahoo.com
4
Add optional security headers (X-Frame-Options, Permissions-Policy)
yahoo.com has most security headers configured. Missing: X-Frame-Options, Permissions-Policy. These are best-practice additions that reduce the attack surface for client-side vulnerabilities.
How to fix this
1
Add: X-Frame-Options: SAMEORIGIN (use DENY only if you never embed your pages in iframes)
2
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
3
Verify with: curl -sI https://yahoo.com | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
At a glance
Key data points from the scan.
TLS Version
TLSv1.3
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-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. Issues: No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
SPF Record
Present
v=spf1 redirect=_spf.mail.yahoo.com
Security Headers
3/5 present
Missing: X-Frame-Options, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000s (365 days). Missing includeSubDomains — subdomains not covered. Missing preload directive.
SSL Certificate
Valid
Strengths: Certificate valid, 129 days remaining; Issued by DigiCert Inc. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
DNSSEC
Not enabled
Strengths: 5 nameservers configured (ns5.yahoo.com., ns4.yahoo.com., ns3.yahoo.com., ns2.yahoo.com.); 3 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.