Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
facebook.com scored 72/100, meeting baseline requirements but with 3 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Critical gaps in: Known Breaches. Positive signals: TLS Configuration, DMARC / Email Security, Security Headers 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 facebook.com compares
Grade distribution across 2378 companies we've scanned. facebook.com scores better than 47% of them.
71
A+
22
A
180
A-
181
B+
69
B
333
B-
111
C+
111
C
295
C-
110
D+
92
D
216
D-
587
F
facebook.com — Grade C- (72/100)
2378 companies scanned
Security checks
Each check inspects a different part of facebook.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
Known Breaches
2 breach(es) found (2 verified). Total accounts affected: 509,535,795. Breaches: Facebook (2019-08-01, 509,458,528 accounts); Facebook Marketplace (2023-10-01, 77,267 accounts).
DNS Configuration
Strengths: 4 nameservers configured (a.ns.facebook.com., b.ns.facebook.com., d.ns.facebook.com., c.ns.facebook.com.); 1 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
HSTS Header
HSTS present but max-age is low (15552000s). Recommended minimum: 15768000 (6 months).
Certificate Hygiene
Strengths: Issued by DigiCert Inc. Issues: Certificate expires in 7 days — critical; Wildcard certificate in use — broader attack surface if compromised.
TLS Configuration
TLSv1.3 negotiated with TLS_CHACHA20_POLY1305_SHA256 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); SPF record present; DKIM configured (selectors: default).
Security Headers
4/5 security headers present. Missing: Referrer-Policy.
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.
Recommended actions
4 items
Steps to improve facebook.com's security grade, ranked by impact.
1
Address 2 known data breaches
facebook.com appears in 2 public breach disclosures. Breached credentials may still be in use. Assess exposure, force password resets for affected accounts, and review whether notification obligations apply.
Compliance impact
PDPA (SG)Part 6A
Mandatory breach notification to PDPC
NIST CSFRS.CO-2
Incidents are reported consistent with criteria
How to fix this
1
Identify which accounts and data types were exposed
2
Force password resets for any affected accounts
3
Check if breach notification has been filed with relevant authorities
4
Review and update incident response procedures
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for facebook.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 facebook.com
3
Increase HSTS max-age duration
HSTS is enabled but the max-age (0s) is below the recommended minimum of 15768000s (6 months). A short max-age means browsers forget the HTTPS-only policy quickly, reducing protection between visits.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Application security header configuration
How to fix this
1
Update header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
2
Verify: curl -sI https://facebook.com | grep -i strict
4
Review certificate configuration — expires in 7 days
Certificate issues found for facebook.com: certificate expires in 7 days; wildcard certificate in use. Wildcard certificates have a broader blast radius if compromised. Ensure auto-renewal is configured to prevent expiry. These are operational hygiene items, not immediate security risks.
How to fix this
1
Verify auto-renewal is configured (Let's Encrypt: certbot renew --dry-run)
2
Consider replacing wildcard cert with individual certs for critical subdomains
3
Consolidate certificate issuance to 1–2 trusted CAs
At a glance
Key data points from the scan.
TLS Version
TLSv1.3
TLSv1.3 negotiated with TLS_CHACHA20_POLY1305_SHA256 (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; DKIM configured (selectors: default).
SPF Record
Present
v=spf1 redirect=_spf.facebook.com
Security Headers
4/5 present
Missing: Referrer-Policy
HSTS
Not enabled
HSTS present but max-age is low (15552000s). Recommended minimum: 15768000 (6 months).
SSL Certificate
Issues
Strengths: Issued by DigiCert Inc. Issues: Certificate expires in 7 days — critical; Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (a.ns.facebook.com., b.ns.facebook.com., d.ns.facebook.com., c.ns.facebook.com.); 1 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.