Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
fbi.gov scored 82/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: TLS Configuration, Known Breaches, HSTS Header 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 fbi.gov compares
Grade distribution across 2598 companies we've scanned. fbi.gov scores better than 72% 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
fbi.gov — Grade B- (82/100)
2598 companies scanned
Security checks
Each check inspects a different part of fbi.gov's public security setup. Green means healthy, yellow needs attention, red is a problem.
Security Headers
3/5 security headers present. Missing: CSP, Permissions-Policy.
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all). Issues: No DKIM records found for common selectors (may use non-standard selectors).
Certificate Hygiene
Strengths: Certificate valid, 32 days remaining; Issued by Google Trust Services. Issues: Wildcard certificate in use — broader attack surface if compromised.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
Known Breaches
No known breaches found in public disclosure databases.
HSTS Header
HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.
DNS Configuration
Strengths: 4 nameservers configured (ns-cloud-e3.googledomains.com., ns-cloud-e2.googledomains.com., ns-cloud-e4.googledomains.com., ns-cloud-e1.googledomains.com.); 2 MX records present; DNSSEC enabled; Zone transfers properly restricted.
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.
Recommended actions
3 items
Steps to improve fbi.gov's security grade, ranked by impact.
1
Strengthen email authentication configuration
Email authentication is partially configured for fbi.gov 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.fbi.gov
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Add optional security headers (CSP, Permissions-Policy)
fbi.gov has most security headers configured. Missing: CSP, Permissions-Policy. These are best-practice additions that reduce the attack surface for client-side vulnerabilities.
How to fix this
1
Add Content-Security-Policy header (start with report-only to avoid breakage)
2
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
3
Verify with: curl -sI https://fbi.gov | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
3
Review certificate configuration
Certificate issues found for fbi.gov: 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_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). Issues: No DKIM records found for common selectors (may use non-standard selectors).
SPF Record
Present
v=spf1 +mx ip4:153.31.0.0/16 -all
Security Headers
3/5 present
Missing: CSP, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.
SSL Certificate
Issues
Strengths: Certificate valid, 32 days remaining; Issued by Google Trust Services. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Enabled
Strengths: 4 nameservers configured (ns-cloud-e3.googledomains.com., ns-cloud-e2.googledomains.com., ns-cloud-e4.googledomains.com., ns-cloud-e1.googledomains.com.); 2 MX records present; DNSSEC enabled; Zone transfers properly restricted.