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

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
95
GRADE
A
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from Amsterdam, Netherlands
200 OK
Checks
9
7 PASS 2 REVIEW
B
DNS Records
4 A records, 651 ms lookup
REVIEW
4 A records, 651 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 3.174.193.23, 3.174.193.83, 3.174.193.39, 3.174.193.113
Info::
Has 8 IPv6 (AAAA) record(s)
Got: 2600:9000:2906:b000:0:91c:a40:93a1, 2600:9000:2906:f400:0:91c:a40:93a1, 2600:9000:2906:3a00:0:91c:a40:93a1, 2600:9000:2906:200:0:91c:a40:93a1, 2600:9000:2906:2e00:0:91c:a40:93a1, 2600:9000:2906:9c00:0:91c:a40:93a1, 2600:9000:2906:8800:0:91c:a40:93a1, 2600:9000:2906:d000:0:91c:a40:93a1
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: www.usa.gov.external-domains-production.cloud.gov
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'.
Warning::
DNS resolution is slow (651 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 651 ms
A3.174.193.23, 3.174.193.83, 3.174.193.39, 3.174.193.113
AAAA2600:9000:2906:b000:0:91c:a40:93a1, 2600:9000:2906:f400:0:91c:a40:93a1, 2600:9000:2906:3a00:0:91c:a40:93a1, 2600:9000:2906:200:0:91c:a40:93a1, 2600:9000:2906:2e00:0:91c:a40:93a1, 2600:9000:2906:9c00:0:91c:a40:93a1, 2600:9000:2906:8800:0:91c:a40:93a1, 2600:9000:2906:d000:0:91c:a40:93a1
CNAMEwww.usa.gov.external-domains-production.cloud.gov
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 651 ms

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)

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

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

Certificate validity

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

Recommended actions

  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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.usa.gov

https://www.usa.gov

694 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.usa.gov200694 msHTTP/1.1
A+
IPv6 Readiness
IPv6 reachable (15 ms)
PASS
IPv6 reachable (15 ms)
Info::
IPv6 is configured and reachable at 2600:9000:2906:b000:0:91c:a40:93a1, 2600:9000:2906:f400:0:91c:a40:93a1, 2600:9000:2906:3a00:0:91c:a40:93a1, 2600:9000:2906:200:0:91c:a40:93a1, 2600:9000:2906:2e00:0:91c:a40:93a1, 2600:9000:2906:9c00:0:91c:a40:93a1, 2600:9000:2906:8800:0:91c:a40:93a1, 2600:9000:2906:d000:0:91c:a40:93a1
Got: 15 ms connect
IPv6 Ready
AAAA Records 2600:9000:2906:b000:0:91c:a40:93a1, 2600:9000:2906:f400:0:91c:a40:93a1, 2600:9000:2906:3a00:0:91c:a40:93a1, 2600:9000:2906:200:0:91c:a40:93a1, 2600:9000:2906:2e00:0:91c:a40:93a1, 2600:9000:2906:9c00:0:91c:a40:93a1, 2600:9000:2906:8800:0:91c:a40:93a1, 2600:9000:2906:d000:0:91c:a40:93a1 Connection Reachable (15 ms)
A+
Crawlability
robots.txt present, sitemap with 1535 URLs
PASS
robots.txt present, sitemap with 1535 URLs
Info::
robots.txt is present
Got: 1558 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1535 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1558 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
#
# robots.txt
#
# This file is to prevent the crawling and indexing of certain parts
# of your site by web crawlers and spiders run by sites like Yahoo!
# and Google. By telling these "robots" where not to go on your site,
# you save bandwidth and server resources.
#
# This file will be ignored unless it is at the root of your host:
# Used:    http://example.com/robots.txt
# Ignored: http://example.com/site/robots.txt
#
# For more information about the robots.txt standard, see:
# http://www.robotstxt.org/robotstxt.html

User-agent: *
Crawl-delay: 10

# Sitemaps
Sitemap: https://www.usa.gov/sitemap.xml

# CSS, JS, Images
Allow: /misc/*.css$
Allow: /misc/*.css?
Allow: /misc/*.js$
Allow: /misc/*.js?
Allow: /misc/*.gif
Allow: /misc/*.jpg
Allow: /misc/*.jpeg
Allow: /misc/*.png
Allow: /modules/*.css$
Allow: /modules/*.css?
Allow: /modules/*.js$
Allow: /modules/*.js?
Allow: /modules/*.gif
Allow: /modules/*.jpg
Allow: /modules/*.jpeg
Allow: /modules/*.png
Allow: /profiles/*.css$
Allow: /profiles/*.css?
Allow: /profiles/*.js$
Allow: /profiles/*.js?
Allow: /profiles/*.gif
Allow: /profiles/*.jpg
Allow: /profiles/*.jpeg
Allow: /profiles/*.png
Allow: /themes/*.css$
Allow: /themes/*.css?
Allow: /themes/*.js$
Allow: /themes/*.js?
Allow: /themes/*.gif
Allow: /themes/*.jpg
Allow: /themes/*.jpeg
Allow: /themes/*.png
# Directories 
Disallow: /includes/
Disallow: /misc/
Disallow: /modules/
Disallow: /profiles/
Disallow: /scripts/
Disallow: /themes/
# We shouldn't have these, but:
Disallow: /node
Disallow: /node/
Disallow: /es/node
Disallow: /es/node/
sitemap.xml 200 OK
Type URL Set URLs 1535 entries Valid XML Yes
Sample URLs:
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.usa.gov/
302https://usa.gov/

Preferred variant: www

HTTP → HTTPS

301http://www.usa.gov/ → https://www.usa.gov/

Consistent

A+
Domain Intelligence
usa.gov — via get.gov, 27 years old
PASS
usa.gov — via get.gov, 27 years old
Info::
Domain registered until Aug 18, 2026 (4 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: get.gov
Domain expiry

37 days

August 18, 2026

SSL certificate

76 days

Issued by Let's Encrypt

Domain age

27 years

Registered August 18, 1999

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2600:1f18:f88:4313:6df7:f986:f915:78d6

Registrar

get.gov

Lock status unknown 5 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
Registrar get.gov
Created August 18, 1999 (27 years ago)
Expires August 18, 2026 (4 months)
Last Updated November 6, 2025
Name Servers dns.gsa.gov, dns2.gsa.gov, dns3.gsa.gov, dns4.gsa.gov, dns5.gsa.gov
DNSSEC Enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 2600:1f18:f88:4313:6df7:f986:f915:78d6
Data source: rdap (0.7s)
A
HTTP Probe Timing
Total 708 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
656 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
14 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.
707 ms
Total Time Total request time from DNS lookup through full response.
708 ms

Connection waterfall

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

Send Feedback