Skip to content
https://hhs.gov

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Santa Clara, United States
301 Moved Permanently
Checks
9
4 PASS 4 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.

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
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 302 Expected: 301 redirect to HTTPS

www / non-www

403https://www.hhs.gov/
200https://hhs.gov/

HTTP → HTTPS

302http://hhs.gov/ http://www.hhs.gov/web/508//

HTTP version does not redirect to HTTPS

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

Certificate validity

244
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, 25 ms lookup
PASS
1 A records, 25 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 52.7.111.176
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns1-08.azure-dns.com, ns2-08.azure-dns.net, ns3-08.azure-dns.org, ns4-08.azure-dns.info
Info::
4 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: 25 ms
Got: 25 ms
A52.7.111.176
AAAA
CNAME
NSns1-08.azure-dns.com, ns2-08.azure-dns.net, ns3-08.azure-dns.org, ns4-08.azure-dns.info
MX
10 primary.us.etp.fireeyegov.com
20 alt1.us.etp.fireeyegov.com
30 alt2.us.etp.fireeyegov.com
40 alt3.us.etp.fireeyegov.com
TXT
MS=ms64846770
_mhpeli9n9zj3rasw6wfiuch30t2sjlw
_yisrerc92l98wrlwv35fgae8dfjyb74
trp8mnslnd5f4qfl3d4y163c586f6tw8
asv=3b51201285febd9e73acc1c45ac3d860
apple-domain-verification=72XseDBHesRrQfTY
amazonses:JDqzXiXlKv2Hvj9Q2k806vbbw8kFyawBULRmQ9Gr5NE=
amazonses:dbAg9/zw+CGJulsEfo3LTw5CPeos0EPF5MTsGy27rAE=
openai-domain-verification=dv-blf0EAB2mJKrhWyhAQ9up5VX
identrust_validate=x3ScnmX5SgobMk7g2d4eVFgbmuCP4eTnomhvM63NuVmX
adobe-idp-site-verification=6c635562-097e-4cc2-951c-5b1075850ccd
webexdomainverification.6NPKN=e802456e-1a37-4768-a1fe-c373f37da215
X9G1TmgB48q57rXrdg5KBDnoWK8:1492-1506-51EC-1832-58D2-9861-C6F7-EFA3
eeF86nEAnEy1pCNHr280d3YTjws:4B79-6E84-1B1F-128A-033C-EAA2-7F77-CC2E
google-site-verification=KLEt4BTsTqluQcp1A32_3nT1blhKaPGll5rhFvNjC5k
google-site-verification=qvxIzivOAKg-85yku4SCDh_yaNUFDeepf37yBYccim0
adobe-sign-verification=cf65728d6e6215c1c3a5f7dbf0618dd781583133bf27d560a84cb29e...
odCuL+S87L9S82Vtp7lmVdYUCrkVhYzbKgS7JHm4Z8yKwFO35YIQBpcLX4emahZsvBc6G+zmi8ksZAKB...
atlassian-domain-verification=aYxhu5Uzd3KmKdIr/oZxVRHqY9BjfmuKC5CebTiTd/LRykPUdV...
SPF v=spf1 ip4:52.2.163.127 ip4:128.121.42.218 ip4:158.70.152.0/24 ip4:69.31.168.128...
CAALookup not available with standard resolver
Resolved in 25 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), 243 ms total
PASS
1 redirect(s), 243 ms total
Info::
Single redirect
Got: https://hhs.gov → https://www.hhs.gov/ (301)
Info::
WWW normalization redirect

https://hhs.gov

211 ms · HTTP/1.1

301

https://www.hhs.gov/

32 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://hhs.gov301211 msHTTP/1.1Apache
2https://www.hhs.gov/40332 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
Domain Intelligence
hhs.gov — via get.gov, 28 years, 11 months old, hosted on AWS
PASS
hhs.gov — via get.gov, 28 years, 11 months old, hosted on AWS
Info::
Domain registered until Jul 24, 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.
Info::
Hosting: AWS
Got: AS14618
Domain expiry

EXPIRED

July 24, 2026

SSL certificate

244 days

Issued by DigiCert Inc

Domain age

28 years, 11 months

Registered October 2, 1997

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

52.7.111.176

Registrar

get.gov

Unlocked 4 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
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar get.gov
Created October 2, 1997 (28 years, 11 months ago)
Expires July 24, 2026 (3 months)
Last Updated September 13, 2025
Name Servers ns1-08.azure-dns.com, ns2-08.azure-dns.net, ns3-08.azure-dns.org, ns4-08.azure-dns.info
DNSSEC Enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 52.7.111.176
ASN AS14618 (AMAZON-AES - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.3s)

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 209 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.
66 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
69 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
209 ms
Total Time Total request time from DNS lookup through full response.
209 ms

Connection waterfall

DNS Lookup 7 ms TCP Connect 66 ms TLS Handshake 69 ms Server Processing 67 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