Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
nasa.gov scored 90/100, demonstrating a strong security posture. No material issues found.
Critical gaps in: Security Headers. Positive signals: TLS Configuration, HSTS Header, DNS Configuration all passed.
1 action item 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 nasa.gov compares
Grade distribution across 2598 companies we've scanned. nasa.gov scores better than 89% 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
nasa.gov — Grade A- (90/100)
2598 companies scanned
Security checks
Each check inspects a different part of nasa.gov's public security setup. Green means healthy, yellow needs attention, red is a problem.
Security Headers
Only 1/5 security headers present. Missing: CSP, X-Content-Type-Options, Referrer-Policy, Permissions-Policy. This exposes the application to clickjacking, MIME-sniffing, and other client-side attacks.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (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 with hard-fail (-all); DKIM configured (selectors: selector1). Issues: SPF record has 9 includes — may be overly permissive or hit lookup limits.
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.
CVE Exposure
Detected technologies: nginx. No version information exposed — CVE matching not possible (this is good practice).
DNS Configuration
Strengths: 6 nameservers configured (a5-66.akam.net., a9-64.akam.net., a8-66.akam.net., a1-32.akam.net.); 1 MX records present; DNSSEC enabled; Zone transfers properly restricted.
Certificate Hygiene
Strengths: Certificate valid, 81 days remaining; Issued by Let's Encrypt.
Recommended actions
1 item
Steps to improve nasa.gov's security grade, ranked by impact.
1
Add missing security headers (CSP, X-Content-Type-Options, Referrer-Policy, Permissions-Policy)
4 of 5 recommended security headers are missing on nasa.gov: CSP, X-Content-Type-Options, 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: X-Content-Type-Options: nosniff
3
Add: Referrer-Policy: strict-origin-when-cross-origin
4
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
5
Verify with: curl -sI https://nasa.gov | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
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); DKIM configured (selectors: selector1). Issues: SPF record has 9 includes — may be overly permissive or hit lookup limits.
SPF Record
Present
v=spf1 include:_spf-4a.nasa.gov include:_spf-4b.nasa.gov include:_spf-4c.nasa.gov include:_spf-4d.na
Security Headers
1/5 present
Missing: CSP, X-Content-Type-Options, Referrer-Policy, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.
SSL Certificate
Valid
Strengths: Certificate valid, 81 days remaining; Issued by Let's Encrypt.
DNSSEC
Enabled
Strengths: 6 nameservers configured (a5-66.akam.net., a9-64.akam.net., a8-66.akam.net., a1-32.akam.net.); 1 MX records present; DNSSEC enabled; Zone transfers properly restricted.