Skip to content
https://fbi.gov

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
0
REVIEW
8
PASS
9
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
9 PASS 8 REVIEW
C
Reverse DNS
Action
0/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR lookup failed for 104.16.148.244: lookup 104.16.148.244: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 104.16.149.244: lookup 104.16.149.244: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2606:4700::6810:95f4: lookup 2606:4700::6810:95f4: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2606:4700::6810:94f4: lookup 2606:4700::6810:94f4: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
B
Crawlability
robots.txt present, sitemap with 0 URLs
REVIEW
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 1017 bytes
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt references sitemap

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more ▾

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more ▾

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

robots.txt 200 OK
Size 1017 B Sitemaps referenced 1 User-agents *, Googlebot, Bingbot, Slurp, DuckDuckBot Blocking No — crawling allowed
Sitemap: https://www.fbi.gov/sitemap.xml.gz


# Define access-restrictions for robots/spiders

# http://www.robotstxt.org/wc/norobots.html




# By default we allow robots to access all areas of our site

# already accessible to anonymous users


User-agent: *

Disallow:




# Add Googlebot-specific syntax extension to exclude forms

# that are repeated for each piece of content in the site

# the wildcard is only supported by Googlebot

# http://www.google.com/support/webmasters/bin/answer.py?answer=40367&ctx=sibling


User-Agent: Googlebot

User-Agent: Bingbot

User-Agent: Slurp

User-Agent: DuckDuckBot


Disallow: /@@search?

Disallow: /search?

Disallow: /*atct_album_view$

Disallow: /*folder_factories$

Disallow: /*folder_summary_view$

Disallow: /*login_form$

Disallow: /*mail_password_form$

Disallow: /*search_rss$

Disallow: /*sendto_form$

Disallow: /*summary_view$

Disallow: /*thumbnail_view$

Disallow: /plonejsi18n$

Disallow: /*@@castle.cms.querylisting*?

Disallow: /*interactive*
sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
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.fbi.gov/
200https://fbi.gov/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Certificate validity

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

Recommended actions

  • 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: CDG)
Got: cf-ray: a1926be088df2a5f-CDG
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: a1926be088df2a5f-CDG
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: connection error, /health: 404, /healthz: connection error, /ping: 404, /status: 404.
A+
DNS Records
2 A records, 25 ms lookup
PASS
2 A records, 25 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.16.148.244, 104.16.149.244
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700::6810:95f4, 2606:4700::6810:94f4
Info::
4 nameserver(s) configured
Got: ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e1.googledomains.com
Info::
2 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 25 ms
Got: 25 ms
A104.16.148.244, 104.16.149.244
AAAA2606:4700::6810:95f4, 2606:4700::6810:94f4
CNAME—
NSns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e1.googledomains.com
MX
10 mx-east.fbi.gov
20 mx-west.fbi.gov
TXT
C8WWN4MbK7z5BL4Ivc/DSxEeVsr18DB5/P8GxlM1S3OfCxexrFpFzpY7MBDBoid3h/OxYU+1H0pFrKWh...
_globalsign-domain-verification=xZMJnzdDAgURaBjUZ6qbqWaaYmV5W3sfo3TF8mUxne
ublrZj1CzpSEiwtiRFKDAyiek8hRqkqaTTApxvhwai14i8JqVBOauW4cA06i39H5Lhl3HnALCM/xfTxI...
625558384-8740534
MS=ms39271050
fastly-domain-delegation-weownfbi.gov-273985-2020-08-06
google-site-verification=L8cauHJF4MANoTCkMbrLkAVfHBta28ctva9n1IDekTo
SPF v=spf1 +mx ip4:153.31.0.0/16 -all
google-site-verification=6UEk-jfg1xPNjz_rQGcRFJOBGxMy1aARDZUTXgSNAqw
google-site-verification=uTH4Vg-Xcc9hTqSdeThbT9UnYvuphObtVSpCEgaGr78
adobe-idp-site-verification=101945e35b37c6efd526cf706f04bc9545a02f9cdc58dbf71867...
apple-domain-verification=oOspXl6Jvnx9HzLM
amazonses: iUbfpGEqhMPlcmJ0aykJZREltK6pWio9wOgRngnJOQE=
CAALookup not available with standard resolver
Resolved in 25 ms
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
DNSSEC
Signed and validating
PASS
Signed and validating
Info::
DNSSEC fully signed and chain validates (RSASHA256)
A
CAA Records
issue: amazon.com, digicert.com, entrust.net, letsencrypt.org, pki.goog, sectigo.com
PASS
issue: amazon.com, digicert.com, entrust.net, letsencrypt.org, pki.goog, sectigo.com
Info::
CAA issue tag present — authorized CA(s): amazon.com, digicert.com, entrust.net, letsencrypt.org, pki.goog, sectigo.com
Info::
No CAA iodef tag — won't be notified of failed issuance attempts
Add `0 iodef "mailto:security@example.com"` to receive notifications when a CA refuses issuance because it doesn't match your CAA policy. Useful signal for detecting issuance attempts by unauthorized CAs.
A+
Multi-Resolver DNS Speed
Mean 24ms across 3 resolvers (spread 9ms)
PASS
Mean 24ms across 3 resolvers (spread 9ms)
Info::
Google: 20ms
Got: 20ms via 8.8.8.8:53
Info::
Cloudflare: 25ms
Got: 25ms via 1.1.1.1:53
Info::
Quad9: 29ms
Got: 29ms via 9.9.9.9:53
A
Redirect Chain
1 redirect(s), 286 ms total
PASS
1 redirect(s), 286 ms total
Info::
Single redirect
Got: https://fbi.gov → https://www.fbi.gov/ (301)
Info::
WWW normalization redirect

https://fbi.gov

65 ms · HTTP/1.1

301

https://www.fbi.gov/

221 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://fbi.gov30165 msHTTP/1.1cloudflare
2https://www.fbi.gov/200221 msHTTP/1.1cloudflare

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 2606:4700::6810:95f4, 2606:4700::6810:94f4
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700::6810:95f4, 2606:4700::6810:94f4 Connection Reachable (17 ms)
A
Domain Intelligence
fbi.gov — via get.gov, 29 years, 2 months old
PASS
fbi.gov — via get.gov, 29 years, 2 months old
Warning::
Domain expires in 41 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Aug 21, 2026
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

40 days

August 21, 2026

SSL certificate

86 days

Issued by Google Trust Services

Domain age

29 years, 2 months

Registered October 2, 1997

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700::6810:94f4

Registrar

get.gov

Unlocked 4 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 (29 years, 2 months ago)
Expires August 21, 2026 (1 months)
Last Updated August 26, 2025
Name Servers ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com
DNSSEC Enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 2606:4700::6810:94f4
Data source: rdap (0.3s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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 102 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
31 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.
24 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
102 ms
Total Time Total request time from DNS lookup through full response.
103 ms

Connection waterfall

DNS Lookup 31 ms TCP Connect 17 ms TLS Handshake 24 ms Server Processing 31 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