90
nist.gov
Findings
6
·
2
·
0
Checks
8 passive
Executive Summary
AI-GENERATED
nist.gov scored 90/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: DMARC / Email Security, Known Breaches, 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.
Action Items
Ordered by priority · 2 items
1
Add optional security headers (Referrer-Policy, Permissions-Policy)
nist.gov has most security headers configured. Missing: Referrer-Policy, Permissions-Policy. These are best-practice additions that reduce the attack surface for client-side vulnerabilities.
Remediation Steps
1
Add: Referrer-Policy: strict-origin-when-cross-origin
2
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
3
Verify with: curl -sI https://nist.gov | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
Unlock the full remediation plan
Get detailed steps, compliance mapping, and ownership for all 2 action items. Free — just enter your work email.
No spam. We'll only contact you about this report.
✓ Report unlocked. Scroll down for full details.
2
Review certificate configuration
Certificate issues found for nist.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.
Remediation Steps
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
Scan Findings
Security Headers
Warning
Certificate Hygiene
Warning
DMARC / Email Security
Healthy
Known Breaches
Healthy
DNS Configuration
Healthy
TLS Configuration
Healthy
HSTS Header
Healthy
CVE Exposure
Healthy