Skip to content
https://recreation.gov

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 4 REVIEW
C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
Crawlability
robots.txt present, sitemap with 0 URLs
REVIEW
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 326 bytes
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt references sitemap

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

robots.txt 200 OK
Size 326 B Sitemaps referenced 4 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: /account/*
Disallow: /cart
Disallow: /cart/*
Disallow: /api
Disallow: /api/*
Crawl-delay: 10

Sitemap: https://www.recreation.gov/sitemap.xml.gz
Sitemap: https://www.recreation.gov/sitemap1.xml.gz
Sitemap: https://www.recreation.gov/sitemap2.xml.gz
Sitemap: https://www.recreation.gov/sitemap3.xml.gz

sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
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.recreation.gov/
200https://recreation.gov/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://recreation.gov/ https://recreation.gov/

Consistent

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

Certificate validity

306
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
4 A records, 46 ms lookup
PASS
4 A records, 46 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 18.164.52.127, 18.164.52.10, 18.164.52.59, 18.164.52.69
Info::
No IPv6 (AAAA) records
Info::
6 nameserver(s) configured
Got: a1-219.akam.net, a22-67.akam.net, a11-64.akam.net, a20-66.akam.net, a18-65.akam.net, a3-64.akam.net
Info::
5 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: 46 ms
Got: 46 ms
A18.164.52.127, 18.164.52.10, 18.164.52.59, 18.164.52.69
AAAA
CNAME
NSa1-219.akam.net, a22-67.akam.net, a11-64.akam.net, a20-66.akam.net, a18-65.akam.net, a3-64.akam.net
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 alt3.aspmx.l.google.com
10 alt4.aspmx.l.google.com
TXT
_globalsign-domain-verification=GTiJAGCB4a7PTzYpGTm86opaMCl_7tM1I-qtu7x2Wo
SPF v=spf1 include:amazonses.com include:_spf.google.com include:_netblocks.google.c...
google-site-verification-old=W9yzqxkoByeHkODxv2I8XJ-ceB66ROJo30Gx5W6Tmrc
_globalsign-domain-verification-old=K438LYKZT1yvye9TiUE5EHYr-JysC8BCdP5VNT5bFt
google-site-verification=xC94crFTjWruWIH8nHRGz9aH96kkEegmddCJ0uuU1_g
CAALookup not available with standard resolver
Resolved in 46 ms

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), 403 ms total
PASS
1 redirect(s), 403 ms total
Info::
Single redirect
Got: https://recreation.gov → https://www.recreation.gov/ (301)
Info::
WWW normalization redirect

https://recreation.gov

53 ms · HTTP/1.1

301

https://www.recreation.gov/

351 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://recreation.gov30153 msHTTP/1.1AmazonS3
2https://www.recreation.gov/200351 msHTTP/1.1r1s

See the visual redirect chain in the HTTP Probe tab →

A+
Domain Intelligence
recreation.gov — via get.gov, 28 years, 7 months old, hosted on AWS
PASS
recreation.gov — via get.gov, 28 years, 7 months old, hosted on AWS
Info::
Domain registered until Sep 8, 2026 (4 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.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

85 days

September 8, 2026

SSL certificate

306 days

Issued by Amazon

Domain age

28 years, 7 months

Registered February 11, 1998

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

18.164.52.127

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 February 11, 1998 (28 years, 7 months ago)
Expires September 8, 2026 (4 months)
Last Updated September 13, 2025
Name Servers a1-219.akam.net, a11-64.akam.net, a18-65.akam.net, a20-66.akam.net, a22-67.akam.net, a3-64.akam.net
DNSSEC Enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 18.164.52.127
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.6s)

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 102 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
47 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
16 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
20 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
103 ms
Total Time Total request time from DNS lookup through full response.
103 ms

Connection waterfall

DNS Lookup 47 ms TCP Connect 16 ms TLS Handshake 20 ms Server Processing 20 ms Content Transfer 0 ms
A+
CDN & Delivery
AWS CloudFront (Hit from cloudfront)
PASS
AWS CloudFront (Hit from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: CDG50-P4)
Got: x-amz-cf-id: kKDl7x-v6BnN4sar5gzMCzl20vzsNK672bi5et4M7sxIfZ8Wb1uOeg==
Info::
CDN cache status: Hit from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status Hit from cloudfront Evidence x-amz-cf-id: kKDl7x-v6BnN4sar5gzMCzl20vzsNK672bi5et4M7sxIfZ8Wb1uOeg==
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback