Overview
Findings
Actions
Details
Related
B-
82 / 100

usa.gov

Security report · Scanned February 15, 2026

Checks
8
Passed
6
Warnings
1
Critical
1
AI-Generated Summary
What this means

usa.gov scored 82/100, demonstrating a strong security posture. Minor improvements are noted below.

Critical gaps in: Security Headers. Positive signals: Known Breaches, TLS Configuration, DNS Configuration all passed.

2 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 usa.gov compares

Grade distribution across 2598 companies we've scanned. usa.gov scores better than 72% of them.

72th percentile
0 Percentile rank 100
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
usa.gov — Grade B- (82/100) 2598 companies scanned
Security checks

Each check inspects a different part of usa.gov's public security setup. Green means healthy, yellow needs attention, red is a problem.

Security Headers
Only 2/5 security headers present. Missing: CSP, Referrer-Policy, Permissions-Policy. This exposes the application to clickjacking, MIME-sniffing, and other client-side attacks.
Problem
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); SPF record present with soft-fail (~all). Issues: No DKIM records found for common selectors (may use non-standard selectors).
Needs work
Known Breaches
No known breaches found in public disclosure databases.
Healthy
HSTS Header
HSTS enabled: max-age=63072000. includeSubDomains present. Missing preload directive.
Healthy
DNS Configuration
Strengths: 5 nameservers configured (dns5.gsa.gov., dns4.gsa.gov., dns3.gsa.gov., dns.gsa.gov.); DNSSEC enabled; Zone transfers properly restricted.
Healthy
CVE Exposure
Detected technologies: Proxy/CDN. (Proxy/CDN detected but excluded from CVE matching — upstream infrastructure). All detected technologies are upstream CDN/proxy infrastructure. No application-level software versions exposed.
Healthy
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
Healthy
Certificate Hygiene
Strengths: Certificate valid, 63 days remaining; Issued by Let's Encrypt.
Healthy
Recommended actions
2 items

Steps to improve usa.gov's security grade, ranked by impact.

1
Add missing security headers (CSP, Referrer-Policy, Permissions-Policy)
Impact: 1–2 Hours
HIGH
3 of 5 recommended security headers are missing on usa.gov: CSP, Referrer-Policy, Permissions-Policy. These headers protect against clickjacking, MIME-sniffing, and unauthorized browser feature access. Adding them is a server configuration change with no application code changes required.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Security headers are required application controls
OWASPSecure Headers
Recommended baseline for web applications
How to fix this
1
Add Content-Security-Policy header (start with report-only to avoid breakage)
2
Add: Referrer-Policy: strict-origin-when-cross-origin
3
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
4
Verify with: curl -sI https://usa.gov | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
2
Strengthen email authentication configuration
Impact: 2–4 Hours
HIGH
Email authentication is partially configured for usa.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.usa.gov
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 soft-fail (~all). Issues: No DKIM records found for common selectors (may use non-standard selectors).
SPF Record
Present
v=spf1 include:amazonses.com include:532040.spf10.hubspotemail.net ~all
Security Headers
2/5 present
Missing: CSP, Referrer-Policy, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=63072000. includeSubDomains present. Missing preload directive.
SSL Certificate
Valid
Strengths: Certificate valid, 63 days remaining; Issued by Let's Encrypt.
DNSSEC
Enabled
Strengths: 5 nameservers configured (dns5.gsa.gov., dns4.gsa.gov., dns3.gsa.gov., dns.gsa.gov.); DNSSEC enabled; Zone transfers properly restricted.