Skip to content
https://medicare.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 New York, United Stated
301 Moved Permanently
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.medicare.gov/
200https://medicare.gov/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Certificate validity

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

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • 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+
DNS Records
1 A records, 11 ms lookup
PASS
1 A records, 11 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 23.201.161.222
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 5 IPv6 (AAAA) record(s)
Got: 2600:141b:1c00:22a6::348, 2600:141b:1c00:22a1::348, 2600:141b:1c00:229f::348, 2600:141b:1c00:2295::348, 2600:141b:1c00:228d::348
Info::
6 nameserver(s) configured
Got: a1-86.akam.net, a3-66.akam.net, a8-67.akam.net, a10-67.akam.net, a13-64.akam.net, a24-65.akam.net
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::
SPF record present in TXT
Info::
DNS resolution time: 11 ms
Got: 11 ms
A23.201.161.222
AAAA2600:141b:1c00:22a6::348, 2600:141b:1c00:22a1::348, 2600:141b:1c00:229f::348, 2600:141b:1c00:2295::348, 2600:141b:1c00:228d::348
CNAME—
NSa1-86.akam.net, a3-66.akam.net, a8-67.akam.net, a10-67.akam.net, a13-64.akam.net, a24-65.akam.net
MX—
TXT
SPF v=spf1 ip4:198.21.2.165/32 ip4:199.15.212.120/32 -all
identrust_validate=FTSIo3p1oWBPZ6p6ZN/OqbNwbSJxzch4d1r1C7auMF0f
identrust_validate=HcGXgntLqk6dsJG3OKeE8lPLHazGQ2xmrMDFtwOv3PZR
identrust_validate=VNNwei3SI6JIF4k9f4c8NntKUmZH3R6890KyPJjZw8f4
google-site-verification=9FOlCtgOp-aWZU-dT2blcA-vFHjOmdDuChFNj2h26GQ
google-site-verification=CA_mQUXGGCp7YGytjJEW-Sg4i80nje4Zetp_fwvmk_Q
CAALookup not available with standard resolver
Resolved in 11 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), 141 ms total
PASS
1 redirect(s), 141 ms total
Info::
Single redirect
Got: https://medicare.gov → https://www.medicare.gov/ (301)
Info::
WWW normalization redirect

https://medicare.gov

24 ms · HTTP/1.1

301

https://www.medicare.gov/

116 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://medicare.gov30124 msHTTP/1.1
2https://www.medicare.gov/200116 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2600:141b:1c00:22a6::348, 2600:141b:1c00:22a1::348, 2600:141b:1c00:229f::348, 2600:141b:1c00:2295::348, 2600:141b:1c00:228d::348
Got: 1 ms connect
IPv6 Ready
AAAA Records 2600:141b:1c00:22a6::348, 2600:141b:1c00:22a1::348, 2600:141b:1c00:229f::348, 2600:141b:1c00:2295::348, 2600:141b:1c00:228d::348 Connection Reachable (1 ms)
A+
Crawlability
robots.txt present, sitemap with 924 URLs
PASS
robots.txt present, sitemap with 924 URLs
Info::
robots.txt is present
Got: 1893 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 924 entries
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 1893 B Sitemaps referenced 0 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: *

# CSS, JS, Images

Allow: /core/*.css$

Allow: /core/*.css?

Allow: /core/*.js$

Allow: /core/*.js?

Allow: /core/*.gif

Allow: /core/*.jpg

Allow: /core/*.jpeg

Allow: /core/*.png

Allow: /core/*.svg

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: /profiles/*.svg

# Directories

Disallow: /core/

Disallow: /profiles/

# Files

Disallow: /README.txt

Disallow: /web.config

# Paths (clean URLs)

Disallow: /admin/

Disallow: /comment/reply/

Disallow: /filter/tips

Disallow: /node/add/

Disallow: /node/

Disallow: /es/node/

Disallow: /app-static-content/

Disallow: /search/

Disallow: /medicare-search/

Disallow: /user/register/

Disallow: /user/password/

Disallow: /user/login/

Disallow: /user/logout/

# Paths (no clean URLs)

Disallow: /index.php/admin/

Disallow: /index.php/comment/reply/

Disallow: /index.php/filter/tips

Disallow: /index.php/node/add/

Disallow: /index.php/node/

Disallow: /index.php/es/node/

Disallow: /index.php/app-static-content/

Disallow: /index.php/search/

Disallow: /index.php/medicare-search/

Disallow: /index.php/user/password/

Disallow: /index.php/user/register/

Disallow: /index.php/user/login/

Disallow: /index.php/user/logout/
sitemap.xml 200 OK
Type URL Set URLs 924 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
medicare.gov — via get.gov, 28 years, 9 months old
PASS
medicare.gov — via get.gov, 28 years, 9 months old
Info::
Domain registered until Sep 15, 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.
Domain expiry

59 days

September 15, 2026

SSL certificate

210 days

Issued by DigiCert Inc

Domain age

28 years, 9 months

Registered November 21, 1997

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2600:141b:1c00:228d::348

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 November 21, 1997 (28 years, 9 months ago)
Expires September 15, 2026 (4 months)
Last Updated September 20, 2025
Name Servers a1-86.akam.net, a10-67.akam.net, a13-64.akam.net, a24-65.akam.net, a3-66.akam.net, a8-67.akam.net
DNSSEC Enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 2600:141b:1c00:228d::348
Data source: rdap (0.2s)

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 24 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.
3 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
24 ms
Total Time Total request time from DNS lookup through full response.
24 ms

Connection waterfall

DNS Lookup 7 ms TCP Connect 1 ms TLS Handshake 3 ms Server Processing 13 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