Skip to content
https://cms.gov

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
93
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Madrid, Spain
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.cms.gov/
200https://cms.gov/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://cms.gov/ https://cms.gov/

Consistent

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

Certificate validity

98
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, 82 ms lookup
PASS
1 A records, 82 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 104.85.50.85
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a02:26f0:680:4a3::28a, 2a02:26f0:680:483::28a
Info::
6 nameserver(s) configured
Got: a3-66.akam.net, a1-86.akam.net, a8-67.akam.net, a10-67.akam.net, a13-64.akam.net, a24-65.akam.net
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: 82 ms
Got: 82 ms
A104.85.50.85
AAAA2a02:26f0:680:4a3::28a, 2a02:26f0:680:483::28a
CNAME
NSa3-66.akam.net, a1-86.akam.net, a8-67.akam.net, a10-67.akam.net, a13-64.akam.net, a24-65.akam.net
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
identrust_validate=JDXQyrvdi4u4csBVW53QJrn58NGFNML/YX9w8UtRx3WF
_qm4av6bzsp5uujahwa11fsttdhvxzv9
webexdomainverification.KR4G=d2e70405-10af-4863-bc64-388ca30ea4d4
G7+0noMBL6fSl8UVSBtZmj35+02tBOTulPKWucrYjkLJFMZz21/GxFxVzTMDYCjNXRIdENxZHifEHLds...
MS=ms27639832
webexdomainverification.3MUBG=00360c1a-741f-4d9f-983a-55d0a63cdc92
google-site-verification=yuNrclUiclwAtByggN3Jae8WgxDsb6CjtRpPD-EPjXY
google-site-verification=sMIzpCg2oaPmasINAKfMmE9mOmdZRxL0myxnvSlIUOk
webexdomainverification.KR46=1f876bb9-300d-49ad-bf2b-74b544bc5efa
SPF v=spf1 ip4:15.200.33.0/24 ip4:15.200.32.0/24 ip4:63.88.93.240/28 ip4:158.72.139....
identrust_validate=t41124Xnt5NJgr+E8ne/qqL2LpycASgSenCxnQdzssO4
google-site-verification=MdcB5nKEy-LwlvUBhBoh3YTH01HW1OZNszN9b-C4HV8
identrust_validate=3RmnW/hkqKXUGdB9rQVSUxgwI6kLD3XsbHJh0jZyq2n/
webexdomainverification.3MUDJ=0d5d8346-7f34-4cc3-84c1-28f4eb80829f
webexdomainverification.KR4B=358c3255-c680-4387-b8f3-38a73619240e
ed5vo0xgnd
identrust_validate=UUQCTX9hak2EePyL9SYBOliViCCAiRhPmlyycwfCy/o8
MS=ms59622794
webexdomainverification.KR41=b9eafa45-e96e-4b68-a167-4740e31ccd75
ciscocidomainverification=f1d51662d07e32cdf508fe2103f9060ac5ba2f9efeaa79274003d1...
CAALookup not available with standard resolver
Resolved in 82 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), 114 ms total
PASS
1 redirect(s), 114 ms total
Info::
Single redirect
Got: https://cms.gov → https://www.cms.gov/ (301)
Info::
WWW normalization redirect

https://cms.gov

60 ms · HTTP/1.1

301

https://www.cms.gov/

54 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://cms.gov30160 msHTTP/1.1
2https://www.cms.gov/20054 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2a02:26f0:680:4a3::28a, 2a02:26f0:680:483::28a
Got: 17 ms connect
IPv6 Ready
AAAA Records 2a02:26f0:680:4a3::28a, 2a02:26f0:680:483::28a Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 74 URLs
PASS
robots.txt present, sitemap with 74 URLs
Info::
robots.txt is present
Got: 1476 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 74 entries
Info::
Sitemap index with 74 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1476 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: *

# 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/

Disallow: /node/

Disallow: /media/

# Files

Disallow: /README.txt

Disallow: /web.config

# Paths with query strings

Allow: /sitemap.xml?

Allow: /medicare-coverage-database/*?

Disallow: /*?

# Paths (clean URLs)

Disallow: /admin/

Disallow: /comment/reply/

Disallow: /filter/tips

Disallow: /node/add/

Disallow: /user/

Disallow: /es/

# Paths (no clean URLs)

Disallow: /index.php/

# Sitemap

Sitemap: https://www.cms.gov/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 74 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
cms.gov — via get.gov, 25 years, 2 months old
PASS
cms.gov — via get.gov, 25 years, 2 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

61 days

September 15, 2026

SSL certificate

98 days

Issued by DigiCert Inc

Domain age

25 years, 2 months

Registered June 20, 2001

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2a02:26f0:680:483::28a

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 June 20, 2001 (25 years, 2 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 2a02:26f0:680:483::28a
Data source: rdap (0.4s)

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

Connection waterfall

DNS Lookup 27 ms TCP Connect 16 ms TLS Handshake 18 ms Server Processing 26 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