Skip to content
https://blm.gov

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 4 REVIEW
B
Redirect Chain
1 redirect(s), 1225 ms total
REVIEW
1 redirect(s), 1225 ms total
Info::
Single redirect
Got: https://blm.gov → https://www.blm.gov/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1225 ms total
Got: 1225 ms

https://blm.gov

340 ms · HTTP/1.1

301

https://www.blm.gov/

884 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://blm.gov301340 msHTTP/1.1cloudflare
2https://www.blm.gov/200884 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

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.blm.gov/
200https://blm.gov/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://blm.gov/ https://blm.gov/

Consistent

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

Certificate validity

89
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
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: ORD)
Got: cf-ray: 9f075fee282de8d0-ORD
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9f075fee282de8d0-ORD
A+
DNS Records
4 A records, 33 ms lookup
PASS
4 A records, 33 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 172.65.90.25, 172.65.90.27, 172.65.90.24, 172.65.90.26
Info::
Has 4 IPv6 (AAAA) record(s)
Got: 2606:4700:78::90:0:180, 2606:4700:78::90:0:183, 2606:4700:78::90:0:182, 2606:4700:78::90:0:181
Info::
2 nameserver(s) configured
Got: diva.ns.cloudflare.com, guss.ns.cloudflare.com
Info::
1 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: 33 ms
Got: 33 ms
A172.65.90.25, 172.65.90.27, 172.65.90.24, 172.65.90.26
AAAA2606:4700:78::90:0:180, 2606:4700:78::90:0:183, 2606:4700:78::90:0:182, 2606:4700:78::90:0:181
CNAME
NSdiva.ns.cloudflare.com, guss.ns.cloudflare.com
MX
0 blm-gov.mail.protection.outlook.com
TXT
SPF v=spf1 include:_spf.doi.gov include:spf.protection.outlook.com include:_spf.sale...
smartsheet-gov-site-validation=Zd0tPMsbgsF8EBdC4SzC8LsOK79C40o5
MS=ms46338243
adobe-idp-site-verification=6f9f2f634017c5c85b7faabcaee4ca242e6c7cbba3ea1a3afa8b...
openai-domain-verification=dv-GaynB36yiClglMIQ21PIbkjA
google-site-verification=Po6ak0B6d8qtPNgK34HUP9plc5eqH-m6laWy3f6MNIk
_qx6ujsovch46qgbn8apvd3ssvpzezwa
CAALookup not available with standard resolver
Resolved in 33 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 (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700:78::90:0:180, 2606:4700:78::90:0:183, 2606:4700:78::90:0:182, 2606:4700:78::90:0:181
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700:78::90:0:180, 2606:4700:78::90:0:183, 2606:4700:78::90:0:182, 2606:4700:78::90:0:181 Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 15 URLs
PASS
robots.txt present, sitemap with 15 URLs
Info::
robots.txt is present
Got: 2056 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 15 entries
Info::
Sitemap index with 15 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 2056 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/
# Files
Disallow: /README.md
Disallow: /composer/Metapackage/README.txt
Disallow: /composer/Plugin/ProjectMessage/README.md
Disallow: /composer/Plugin/Scaffold/README.md
Disallow: /composer/Plugin/VendorHardening/README.txt
Disallow: /composer/Template/README.txt
Disallow: /modules/README.txt
Disallow: /sites/README.txt
Disallow: /themes/README.txt
# Paths (clean URLs)
Disallow: /admin/
Disallow: /comment/reply/
Disallow: /filter/tips
Disallow: /node/add/
Disallow: /search/
Disallow: /user/register
Disallow: /user/password
Disallow: /user/login
Disallow: /user/logout
Disallow: /media/oembed
Disallow: /*/media/oembed
# 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/search/
Disallow: /index.php/user/password
Disallow: /index.php/user/register
Disallow: /index.php/user/login
Disallow: /index.php/user/logout
Disallow: /index.php/media/oembed
Disallow: /index.php/*/media/oembed
# Sitemap
Sitemap: https://www.blm.gov/sitemap.xml

A+
Domain Intelligence
blm.gov — via get.gov, 28 years, 11 months old
PASS
blm.gov — via get.gov, 28 years, 11 months old
Info::
Domain registered until Sep 11, 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

90 days

September 11, 2026

SSL certificate

89 days

Issued by Let's Encrypt

Domain age

28 years, 11 months

Registered October 2, 1997

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:78::90:0:180

Registrar

get.gov

Unlocked 2 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 October 2, 1997 (28 years, 11 months ago)
Expires September 11, 2026 (4 months)
Last Updated September 16, 2025
Name Servers diva.ns.cloudflare.com, guss.ns.cloudflare.com
DNSSEC Enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 2606:4700:78::90:0:180
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 385 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
51 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
17 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
207 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
385 ms
Total Time Total request time from DNS lookup through full response.
386 ms

Connection waterfall

DNS Lookup 51 ms TCP Connect 17 ms TLS Handshake 207 ms Server Processing 111 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