Skip to content
https://www.nasa.gov

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
2
REVIEW
2
PASS
5
INFO
0
Probed from Santa Clara, United Stated
200 OK
Checks
9
5 PASS 2 REVIEW 2 FIX
F
IPv6 Readiness
Action
IPv6 records exist but unreachable
FIX
IPv6 records exist but unreachable
Warning::
IPv6 DNS records exist but server is not reachable
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Got: 2a04:fa87:fffd::c000:426c
Info::
IPv6 connection error
Got: dial tcp6 [2a04:fa87:fffd::c000:426c]:443: connect: network is unreachable
IPv6 Misconfigured
AAAA Records 2a04:fa87:fffd::c000:426c Connection UNREACHABLE

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Why this matters

Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.

Learn more

Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.

Source: RFC 8305 (Happy Eyeballs)

D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

B
DNS Records
1 A records, 19 ms lookup
REVIEW
1 A records, 19 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 192.0.66.108
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2a04:fa87:fffd::c000:426c
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: nasa-gov.go-vip.net
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 19 ms
Got: 19 ms
A192.0.66.108
AAAA2a04:fa87:fffd::c000:426c
CNAMEnasa-gov.go-vip.net
NS
MX
TXT
CAALookup not available with standard resolver
Resolved in 19 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

B
TLS Certificate Expiry & Recommendations
31 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

31
days left
0d 30d 60d 90d+

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.nasa.gov

https://www.nasa.gov

15 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.nasa.gov20015 msHTTP/1.1nginx
A+
Crawlability
robots.txt present, sitemap with 77 URLs
PASS
robots.txt present, sitemap with 77 URLs
Info::
robots.txt is present
Got: 69 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 77 entries
Info::
Sitemap index with 77 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 69 B Sitemaps referenced 0 User-agents usasearch, * Blocking No — crawling allowed
User-agent: usasearch
Crawl-delay: 1
Allow: /

User-agent: *
Allow: /
sitemap.xml 200 OK
Type Sitemap Index URLs 77 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.nasa.gov/
302https://nasa.gov/

Preferred variant: www

HTTP → HTTPS

301http://www.nasa.gov/ https://www.nasa.gov/

Consistent

A+
Domain Intelligence
nasa.gov — via get.gov, 28 years, 11 months old, hosted on WordPress.com (Automattic)
PASS
nasa.gov — via get.gov, 28 years, 11 months old, hosted on WordPress.com (Automattic)
Info::
Domain registered until Jul 31, 2026 (3 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: get.gov
Info::
Hosting: WordPress.com (Automattic)
Got: AS2635
Domain expiry

EXPIRED

July 31, 2026

SSL certificate

31 days

Issued by Let's Encrypt

Domain age

28 years, 11 months

Registered October 2, 1997

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

WordPress.com (Automattic)

ASN AS2635

192.0.66.108

Registrar

get.gov

Lock status unknown 6 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
Registrar get.gov
Created October 2, 1997 (28 years, 11 months ago)
Expires July 31, 2026 (3 months)
Last Updated September 7, 2025
Name Servers a1-32.akam.net, a12-64.akam.net, a14-67.akam.net, a5-66.akam.net, a8-66.akam.net, a9-64.akam.net
DNSSEC Enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 192.0.66.108
ASN AS2635 (AUTOMATTIC - Automattic, Inc, US)
Provider WordPress.com (Automattic)
Data source: rdap (0.3s)
A+
HTTP Probe Timing
Total 16 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
7 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
4 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
15 ms
Total Time Total request time from DNS lookup through full response.
16 ms

Connection waterfall

DNS Lookup 7 ms TCP Connect 1 ms TLS Handshake 4 ms Server Processing 3 ms Content Transfer 1 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback