Skip to content
https://ic3.gov

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
308 Permanent Redirect
Checks
9
4 PASS 4 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
Redirect Chain
1 redirect(s), 1511 ms total
REVIEW
1 redirect(s), 1511 ms total
Info::
Single redirect
Got: https://ic3.gov → https://www.ic3.gov/ (308)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1511 ms total
Got: 1511 ms

https://ic3.gov

393 ms · HTTP/1.1

308

https://www.ic3.gov/

1118 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ic3.gov308393 msHTTP/1.1
2https://www.ic3.gov/2001118 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 165 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your 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

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 165 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
# robots.txt - IC3.gov


User-agent: *

Disallow: /assets/

Disallow: /css/

Disallow: /img/

Disallow: /ContactFBICyber/

Disallow: /PIFSurvey/

Disallow: /Search/
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://ic3.gov/ https://ic3.gov/

Consistent

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

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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
A+
DNS Records
2 A records, 108 ms lookup
PASS
2 A records, 108 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 20.141.170.64, 52.126.48.246
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2001:489a:3102:6::62, 2001:489a:3600::13
Info::
4 nameserver(s) configured
Got: ns1-35.azuregov-dns.us, ns2-35.azuregov-dns.us, ns3-35.azuregov-dns.us, ns4-35.azuregov-dns.us
Info::
2 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: 108 ms
Got: 108 ms
A20.141.170.64, 52.126.48.246
AAAA2001:489a:3102:6::62, 2001:489a:3600::13
CNAME
NSns1-35.azuregov-dns.us, ns2-35.azuregov-dns.us, ns3-35.azuregov-dns.us, ns4-35.azuregov-dns.us
MX
10 mail1.ic3.gov
25 mail2.ic3.gov
TXT
_khghqassscz3aae29b9b22xb3pxffyb
SPF v=spf1 a:smtp.ic3.gov mx exp=spf-exp.ic3.gov -all
CAALookup not available with standard resolver
Resolved in 108 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 (98 ms)
PASS
IPv6 reachable (98 ms)
Info::
IPv6 is configured and reachable at 2001:489a:3102:6::62, 2001:489a:3600::13
Got: 98 ms connect
IPv6 Ready
AAAA Records 2001:489a:3102:6::62, 2001:489a:3600::13 Connection Reachable (98 ms)
A+
Domain Intelligence
ic3.gov — via get.gov, 22 years, 9 months old
PASS
ic3.gov — via get.gov, 22 years, 9 months old
Info::
Domain registered until Aug 12, 2026 (3 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

25 days

August 12, 2026

SSL certificate

259 days

Issued by DigiCert Inc

Domain age

22 years, 9 months

Registered November 13, 2003

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2001:489a:3102:6::62

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 November 13, 2003 (22 years, 9 months ago)
Expires August 12, 2026 (3 months)
Last Updated August 20, 2025
Name Servers ns1-35.azuregov-dns.us, ns2-35.azuregov-dns.us, ns3-35.azuregov-dns.us, ns4-35.azuregov-dns.us
DNSSEC Enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 2001:489a:3102:6::62
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 602 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
203 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
103 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
199 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
602 ms
Total Time Total request time from DNS lookup through full response.
602 ms

Connection waterfall

DNS Lookup 203 ms TCP Connect 103 ms TLS Handshake 199 ms Server Processing 98 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