Skip to content
https://nasa.gov

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
92
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Madrid, Spain
302 Found
Checks
9
6 PASS 2 REVIEW 1 FIX
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
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

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

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Certificate validity

83
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+
DNS Records
1 A records, 61 ms lookup
PASS
1 A records, 61 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
Info::
6 nameserver(s) configured
Got: a9-64.akam.net, a8-66.akam.net, a14-67.akam.net, a12-64.akam.net, a5-66.akam.net, a1-32.akam.net
Info::
1 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 61 ms
Got: 61 ms
A192.0.66.108
AAAA2a04:fa87:fffd::c000:426c
CNAME—
NSa9-64.akam.net, a8-66.akam.net, a14-67.akam.net, a12-64.akam.net, a5-66.akam.net, a1-32.akam.net
MX
0 nasa-gov.mail.protection.outlook.com
TXT
uechcfoubh169akghg2214p54n
atlassian-sending-domain-verification=4730ddf4-d24e-4a91-9612-cb14998d0e47
apple-domain-verification=qw51K0kGzRHLbN9S
amazonses:PvUL7T41LO87xjr+2nfgxTu11i75NeT9HzY3xYv82Ko=
1HqDXPHdt8JOt02qy6FB+l3+Z1zXScqcPxlE/faXjZLS9FRbVhHCUCHQE2bWofZt2TWKPchjjma3Pqli...
MS=ms93625004
nmh1f9tgxhmfmjkshg7qh595drdfgnf1
openai-domain-verification=dv-Fbq5PVntP9qLelQPUBKniDjr
docusign=4025560e-93c9-4920-bb13-849c6fc35d58
atlassian-domain-verification=oNzRM7G9GIAL/LLP5c7sPOQiAHsHrQ1hKcU7GGZ0ADRZJFhUB/...
google-site-verification=ZKpcXLqaBX3jND8Fybkvr3MaaOpC_6MRjXBYm0XNkJQ
HRlHXyx8jXo+9pIaJWFVBPOLVfeI2biAj3VT1woaTFpp05D5/q6AoD5KpUgws539/d2jl8wBJiEr58OE...
google-site-verification=BUxd0xTJY4ZjGohBwKDpNms-yOATz92Y54kgme4eKHs
mj8729pr7k44dx62wwtx5745xr5njzkn
n39n7frbwnkhcmky2nps779y4ttn61wl
amazonses:FXFVeQnEO3Wua+aY/H4aOIH3sSwteE+7YpGrwm8kF/s=
SPF v=spf1 include:_spf-4a.nasa.gov include:_spf-4b.nasa.gov include:_spf-4c.nasa.go...
webexdomainverification.1YPST=f98a61ea-b92e-41f2-87aa-5651b2af43b8
openai-domain-verification=dv-CO0ENDLO7EB9V5E4JnmE6pS8
pvv8mevb6qrmqvqi8alhmreg42
CAALookup not available with standard resolver
Resolved in 61 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

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.

A
Redirect Chain
1 redirect(s), 44 ms total
PASS
1 redirect(s), 44 ms total
Info::
Single redirect
Got: https://nasa.gov → https://www.nasa.gov/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://nasa.gov

https://nasa.gov

8 ms · HTTP/1.1

302

https://www.nasa.gov/

36 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://nasa.gov3028 msHTTP/1.1nginx
2https://www.nasa.gov/20036 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

A+
IPv6 Readiness
IPv6 reachable (0 ms)
PASS
IPv6 reachable (0 ms)
Info::
IPv6 is configured and reachable at 2a04:fa87:fffd::c000:426c
Got: 0 ms connect
IPv6 Ready
AAAA Records 2a04:fa87:fffd::c000:426c Connection Reachable (0 ms)
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+
Domain Intelligence
nasa.gov — via get.gov, 28 years, 11 months old
PASS
nasa.gov — via get.gov, 28 years, 11 months old
Info::
Domain registered until Jul 31, 2026 (3 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: get.gov
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Domain expiry

46 days

July 31, 2026

SSL certificate

83 days

Issued by Let's Encrypt

Domain age

28 years, 11 months

Registered October 2, 1997

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2a04:fa87:fffd::c000:426c

Registrar

get.gov

Unlocked 6 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
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 2a04:fa87:fffd::c000:426c
Data source: rdap (0.5s)

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more ▾

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A+
HTTP Probe Timing
Total 178 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
27 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
0 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
3 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
179 ms
Total Time Total request time from DNS lookup through full response.
179 ms

Connection waterfall

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

Send Feedback