Skip to content
https://consumerfinance.gov

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
92
GRADE
A
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
6 PASS 3 REVIEW
B
Redirect Chain
2 redirect(s), 291 ms total
REVIEW
2 redirect(s), 291 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.consumerfinance.gov/

https://consumerfinance.gov

8 ms · HTTP/1.1

301

https://www.consumerfinance.gov/

277 ms · HTTP/1.1

302

https://www.consumerfinance.gov/complain...

6 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://consumerfinance.gov3018 msHTTP/1.1AkamaiGHost
2https://www.consumerfinance.gov/302277 msHTTP/1.1envoy
3https://www.consumerfinance.gov/complain...2006 msHTTP/1.1envoy

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

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

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
CDN & Delivery
Akamai
REVIEW
Akamai
Info::
Site is served via Akamai CDN
Got: server header
CDN Detected: Akamai
Provider Akamai Evidence server header
A+
DNS Records
2 A records, 49 ms lookup
PASS
2 A records, 49 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 23.211.15.158, 23.211.15.153
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a02:26f0:e0::211:25ba, 2a02:26f0:e0::211:2592
Info::
6 nameserver(s) configured
Got: a16-64.akam.net, a20-65.akam.net, a5-64.akam.net, a26-66.akam.net, a1-188.akam.net, a13-67.akam.net
Info::
3 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: 49 ms
Got: 49 ms
A23.211.15.158, 23.211.15.153
AAAA2a02:26f0:e0::211:25ba, 2a02:26f0:e0::211:2592
CNAME
NSa16-64.akam.net, a20-65.akam.net, a5-64.akam.net, a26-66.akam.net, a1-188.akam.net, a13-67.akam.net
MX
5 consumerfinance-gov.mail.protection.outlook.com
10 stn-mtpe-01-03-p.inet.qwest.net
15 cec-mtpe-01-03-p.inet.qwest.net
TXT
_ljtp924su729bgdn97kndq4uvjye8c8
qxwdb7w0v0pzcft5b3lnfv38cyhf2nmk
MS=ms32447474
SPF v=spf1 ip4:66.77.183.130 ip4:66.77.82.98 include:spf.protection.outlook.com incl...
s02cmmnmlw3b1hh792ptlhj9fcpkdtww
google-site-verification=8U_zbw7mKcakHqcvmNY9U-eYX8IuBtwhDdjSTG28h9g
CAALookup not available with standard resolver
Resolved in 49 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+
IPv6 Readiness
IPv6 reachable (0 ms)
PASS
IPv6 reachable (0 ms)
Info::
IPv6 is configured and reachable at 2a02:26f0:e0::211:25ba, 2a02:26f0:e0::211:2592
Got: 0 ms connect
IPv6 Ready
AAAA Records 2a02:26f0:e0::211:25ba, 2a02:26f0:e0::211:2592 Connection Reachable (0 ms)
A
Crawlability
robots.txt present, no sitemap
PASS
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 589 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt references sitemap

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 200 OK
Size 589 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /about-us/the-bureau/leadership-calendar/pdf
Disallow: /es/obtener-respuestas/*.imprimir.html
Disallow: /*?success
Disallow: *form-id=*
Disallow: /?page=
Disallow: /hud-api-replace
Disallow: /yourstory
Disallow: /ask-cfpb/search/
Disallow: /ask-cfpb/search-by-tag/
Disallow: /askcfpb/search/
Disallow: /es/obtener-respuestas/buscar/
Disallow: /es/obtener-respuestas/buscar-por-etiqueta/
Disallow: /consumer-tools/educator-tools/youth-financial-education/curriculum-review/tool/*
Disallow: /paying-for-college2/*

Sitemap: https://www.consumerfinance.gov/sitemap.xml
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

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

HTTP → HTTPS

301http://consumerfinance.gov/ https://www.consumerfinance.gov/

Consistent

A+
Domain Intelligence
consumerfinance.gov — via get.gov, 15 years, 5 months old
PASS
consumerfinance.gov — via get.gov, 15 years, 5 months old
Info::
Domain registered until Feb 19, 2027 (10 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

248 days

February 19, 2027

SSL certificate

113 days

Issued by DigiCert Inc

Domain age

15 years, 5 months

Registered January 26, 2011

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2a02:26f0:e0::211:2592

Registrar

get.gov

Unlocked 6 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar get.gov
Created January 26, 2011 (15 years, 5 months ago)
Expires February 19, 2027 (10 months)
Last Updated April 6, 2026
Name Servers a1-188.akam.net, a13-67.akam.net, a16-64.akam.net, a20-65.akam.net, a26-66.akam.net, a5-64.akam.net
DNSSEC Enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 2a02:26f0:e0::211:2592
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 71 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
45 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.
23 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
71 ms
Total Time Total request time from DNS lookup through full response.
71 ms

Connection waterfall

DNS Lookup 45 ms TCP Connect 1 ms TLS Handshake 23 ms Server Processing 2 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