Skip to content
https://fda.gov

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Amsterdam, Netherlands
302 Found
Checks
9
4 PASS 4 REVIEW 1 FIX
D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
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
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 302 Expected: 301 redirect to HTTPS

www / non-www

200https://www.fda.gov/
200https://fda.gov/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://fda.gov/ /apology_objects/abuse-detection-apology.html

HTTP version does not redirect to HTTPS

B
Redirect Chain
2 redirect(s), 266 ms total
REVIEW
2 redirect(s), 266 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://fda.gov

https://fda.gov

17 ms · HTTP/1.1

302

https://fda.gov/apology_objects/abuse-de...

14 ms · HTTP/1.1

301

https://www.fda.gov/apology_objects/abus...

234 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://fda.gov30217 msHTTP/1.1AkamaiGHost
2https://fda.gov/apology_objects/abuse-de...30114 msHTTP/1.1AkamaiGHost
3https://www.fda.gov/apology_objects/abus...404234 msHTTP/1.1AkamaiNetStorage

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
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

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 No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

330
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
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, 10 ms lookup
PASS
2 A records, 10 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 2.16.6.139, 2.16.6.143
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2a02:26f0:6100::6861:eba
Info::
6 nameserver(s) configured
Got: a2-65.akam.net, a7-67.akam.net, a1-242.akam.net, a13-64.akam.net, a20-65.akam.net, a24-66.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: 10 ms
Got: 10 ms
A2.16.6.139, 2.16.6.143
AAAA2a02:26f0:6100::6861:eba
CNAME
NSa2-65.akam.net, a7-67.akam.net, a1-242.akam.net, a13-64.akam.net, a20-65.akam.net, a24-66.akam.net
MX
10 smtp9.fda.gov
10 smtp8.fda.gov
10 smtp7.fda.gov
10 smtp6.fda.gov
TXT
MS=ms48783525
SPF v=spf1 include:_spf.fda.gov -all
ZOOM_verify_vTEkbQm_QTOaBDWdXKwrAw
FMICzGkJO5j02YNdmENBs5kgzkmhZC/fMYTvO5fowMXe
jamf-site-verification=PGVYWecttOGQ2AWnehEHWQ
amazonses:jdV8OLJfTXw9mxS1imtjFUwKFRGSek+dBX1mXWxE2Es=
openai-domain-verification=dv-AxQqxffHhvOZOt4t4C17dZSm
identrust_validate=4JTBEWb4UcAjNl/lyEYdU+hWXoNWrn9TdDN8Z3OvGSBG
identrust_validate=S0MNbkM5L+oiB5jyFKX0Hu8G0oony8eebRYByXxdxA9o
identrust_validate=c7KW+Ztf7fiYpL/1dimy5BACS/7wAWQAM+0vrb32x8qs
identrust_validate=o4/9QHV5pc4hVjOw4+Ebgwt4DdfKspg017PqghCYCY01
identrust_validate=zXXOEi6CQ2E8NN+fqgQ0q+KVdRi7KOa6XTwefj9zhOe6
smartsheet-gov-site-validation=HsHsNQ2BWzqEo3REvnA4aHm-csXa-eHu
webexdomainverification.11G31=8411e648-086b-4727-aca0-c784ecb9827e
RkQjM5mARE3LHFCQ454owCcYmNyZVV3lM3ziXSPPWtCW2/xeFfwDOYtSzHx1bO5BxQTV9hcMjMr/00cL...
dZbV+0DRySs9wEKyoyX85nwTMJN6TX7SJ4Imh+uTXak5Ps5JnMhZFfKFe8efScPW04tj7oErmE4HUwRk...
cisco-ci-domain-verification=74f9a92409e8b5db0b46652e631823388bcc0461ced801a6b1a...
CAALookup not available with standard resolver
Resolved in 10 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 (2 ms)
PASS
IPv6 reachable (2 ms)
Info::
IPv6 is configured and reachable at 2a02:26f0:6100::6861:eba
Got: 2 ms connect
IPv6 Ready
AAAA Records 2a02:26f0:6100::6861:eba Connection Reachable (2 ms)
A+
Domain Intelligence
fda.gov — via get.gov, 26 years, 1 months old
PASS
fda.gov — via get.gov, 26 years, 1 months old
Info::
Domain registered until Aug 16, 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

34 days

August 16, 2026

SSL certificate

330 days

Issued by IdenTrust

Domain age

26 years, 1 months

Registered July 26, 2000

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2a02:26f0:6100::6861:eba

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 July 26, 2000 (26 years, 1 months ago)
Expires August 16, 2026 (4 months)
Last Updated December 1, 2025
Name Servers a1-242.akam.net, a13-64.akam.net, a2-65.akam.net, a20-65.akam.net, a24-66.akam.net, a7-67.akam.net
DNSSEC Enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 2a02:26f0:6100::6861:eba
Data source: rdap (0.3s)

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

Connection waterfall

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