Security checks — sorted by severity
Cookie Security
Strengths: 1 cookie(s) analyzed. Issues: 1/1 cookie(s) missing Secure flag (MCDCountry_code); 1/1 cookie(s) missing HttpOnly flag (MCDCountry_code); 1/1 cookie(s) missing SameSite attribute (MCDCountry_code).
Strengths: 1 cookie(s) analyzed. Issues: 1/1 cookie(s) missing Secure flag (MCDCountry_code); 1/1 cookie(s) missing HttpOnly flag (MCDCountry_code); 1/1 cookie(s) missing SameSite attribute (MCDCountry_code).
Security Headers
2/5 security headers present. Missing: CSP, Referrer-Policy, Permissions-Policy. This exposes the application to clickjacking, MIME-sniffing, and other client-side attacks. Quality issues: X-XSS-Protection: '1; mode=block' — this header is deprecated and removed from Chrome, Firefox, and Edge. Non-zero values introduce timing side-channel risks; set to '0' or remove the header entirely.
2/5 security headers present. Missing: CSP, Referrer-Policy, Permissions-Policy. This exposes the application to clickjacking, MIME-sniffing, and other client-side attacks. Quality issues: X-XSS-Protection: '1; mode=block' — this header is deprecated and removed from Chrome, Firefox, and Edge. Non-zero values introduce timing side-channel risks; set to '0' or remove the header entirely.
MX Records & Mail Provider
Strengths: Mail handled by sesmail.mcdonalds.com; 1 MX record(s) configured. Issues: Only 1 MX record — no failover if primary mail server is unavailable.
Strengths: Mail handled by sesmail.mcdonalds.com; 1 MX record(s) configured. Issues: Only 1 MX record — no failover if primary mail server is unavailable.
MTA-STS & TLS Reporting
Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks; sending servers cannot verify your mail server requires TLS; No TLSRPT record (_smtp._tls) — TLS delivery failures won't be reported to the domain owner.
Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks; sending servers cannot verify your mail server requires TLS; No TLSRPT record (_smtp._tls) — TLS delivery failures won't be reported to the domain owner.
DNS CAA Records
No CAA records found in the DNS tree for this domain. Without CAA, any Certificate Authority can issue certificates for this domain. Adding CAA records restricts issuance to authorised CAs only, reducing the risk of misissued certificates.
No CAA records found in the DNS tree for this domain. Without CAA, any Certificate Authority can issue certificates for this domain. Adding CAA records restricts issuance to authorised CAs only, reducing the risk of misissued certificates.
DNS Configuration
Strengths: 4 nameservers configured (ns-1445.awsdns-52.org, ns-1685.awsdns-18.co.uk, ns-76.awsdns-09.com, ns-840.awsdns-41.net); NS records span 4 providers (awsdns-52.org, co.uk, awsdns-09.com, awsdns-41.net) — genuine redundancy; SOA record present and MNAME consistent with NS set; 1 MX record(s) present; Zone transfers properly restricted on all nameservers; Address records present: 1 A record(s). Issues: DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).
Strengths: 4 nameservers configured (ns-1445.awsdns-52.org, ns-1685.awsdns-18.co.uk, ns-76.awsdns-09.com, ns-840.awsdns-41.net); NS records span 4 providers (awsdns-52.org, co.uk, awsdns-09.com, awsdns-41.net) — genuine redundancy; SOA record present and MNAME consistent with NS set; 1 MX record(s) present; Zone transfers properly restricted on all nameservers; Address records present: 1 A record(s). Issues: DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).
DMARC / Email Security
Strengths: DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; Forensic reports (ruf) configured; SPF soft-fail (~all) configured; SPF DNS lookup count: 6/10 (within limit); DKIM configured (selectors: s1, s2). Issues: DMARC policy is 'none' (monitoring only, no enforcement).
Strengths: DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; Forensic reports (ruf) configured; SPF soft-fail (~all) configured; SPF DNS lookup count: 6/10 (within limit); DKIM configured (selectors: s1, s2). Issues: DMARC policy is 'none' (monitoring only, no enforcement).
security.txt (RFC 9116)
No security.txt found. Publishing a security.txt at /.well-known/security.txt is the industry standard (RFC 9116) for vulnerability disclosure policies. Its absence may indicate a less mature security program.
No security.txt found. Publishing a security.txt at /.well-known/security.txt is the industry standard (RFC 9116) for vulnerability disclosure policies. Its absence may indicate a less mature security program.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
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.
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.
Known Breaches
No known breaches found in public disclosure databases.
No known breaches found in public disclosure databases.
HSTS Header
HSTS enabled: max-age=31557600s (365 days). Missing includeSubDomains — subdomains not covered. Missing preload directive.
HSTS enabled: max-age=31557600s (365 days). Missing includeSubDomains — subdomains not covered. Missing preload directive.
CVE Exposure
No server software versions detected in HTTP response headers. This is good practice (version hiding) but means CVE exposure cannot be assessed from external signals alone.
No server software versions detected in HTTP response headers. This is good practice (version hiding) but means CVE exposure cannot be assessed from external signals alone.
Certificate Hygiene
Strengths: Certificate valid, 87 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.
Strengths: Certificate valid, 87 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
1+ items
Steps to improve mcdonalds.com's security grade, ranked by impact.
1
Strengthen email authentication configuration
DMARC / Email Security
Email authentication is partially configured for mcdonalds.com but has gaps. Actions needed: upgrade DMARC policy from 'none' to 'quarantine' or 'reject'. Until DMARC enforcement is active, spoofed emails may still reach recipients.
NIST CSFPR.AC-7
Email authentication is a required access control
How to fix this
1
Upgrade DMARC policy to p=quarantine (then p=reject after monitoring)
2
Verify with: nslookup -type=txt _dmarc.mcdonalds.com
See all 2 remaining recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
AI Summary
What this means
mcdonalds.com scored 80/100, demonstrating a strong security posture. Minor improvements are noted below.
Critical gaps in: Cookie Security, Security Headers. Positive signals: TLS Configuration, TLS Protocol Support, Known Breaches all passed.
3 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 mcdonalds.com compares
Grade distribution across 2685 companies we've scanned. mcdonalds.com scores better than 64% of them.
88
A+
28
A
196
A-
202
B+
76
B
376
B-
138
C+
117
C
347
C-
123
D+
96
D
266
D-
632
F
mcdonalds.com — Grade B- (80/100)
2685 companies scanned
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=none
Strengths: DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; Forensic reports (ruf) configured; SPF soft-fail (~all) configured; SPF DNS lookup count: 6/10 (within limit); DKIM configured (selectors: s1, s2). Issues: DMARC policy is 'none' (monitoring only, no enforcement).
SPF Record
Present
v=spf1 include:spf.mailjet.com include:_spf.q4press.com include:amazonses.com include:_spf.tivian.co
Security Headers
2/5 present
Missing: CSP, Referrer-Policy, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31557600s (365 days). Missing includeSubDomains — subdomains not covered. Missing preload directive.
SSL Certificate
Valid
Strengths: Certificate valid, 87 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: 4 nameservers configured (ns-1445.awsdns-52.org, ns-1685.awsdns-18.co.uk, ns-76.awsdns-09.com, ns-840.awsdns-41.net); NS records span 4 providers (awsdns-52.org, co.uk, awsdns-09.com, awsdns-41.net) — genuine redundancy; SOA record present and MNAME consistent with NS set; 1 MX record(s) present; Zone transfers properly restricted on all nameservers; Address records present: 1 A record(s). Issues: DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).
Similar companies
Other domains with comparable security profiles.
