Skip to content
https://dea.gov

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
89
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Sao Paulo, Brazil
403 Forbidden
Checks
9
5 PASS 4 REVIEW
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
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 403 Expected: 301 redirect to HTTPS

www / non-www

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

HTTP → HTTPS

403http://dea.gov/

HTTP version does not redirect to HTTPS

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

Certificate validity

181
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
1 A records, 13 ms lookup
PASS
1 A records, 13 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 23.38.151.192
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2600:1419:6200:287::2b0e, 2600:1419:6200:296::2b0e
Info::
6 nameserver(s) configured
Got: a1-61.akam.net, a7-65.akam.net, a8-66.akam.net, a10-66.akam.net, a12-67.akam.net, a13-64.akam.net
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: 13 ms
Got: 13 ms
A23.38.151.192
AAAA2600:1419:6200:287::2b0e, 2600:1419:6200:296::2b0e
CNAME
NSa1-61.akam.net, a7-65.akam.net, a8-66.akam.net, a10-66.akam.net, a12-67.akam.net, a13-64.akam.net
MX
10 mx-jdcw.usdoj.gov
10 mx-da6.usdoj.gov
TXT
2929236
MS=ms50608472
00dsj00000098xp2ai
_c4bb2k21xzoal2pmpnnhn37em57ndmt
_eafad9uu6p2loga3eix3xh9fojjcib6
_mw4galg4cd0fqcrbb1zu65k84qv1kz3
ywpc4yws0svftpndms4sgk39wnbcq1b9
apple-domain-verification=ZZPwQoiyGM3KmKlk
docusign=249d6a53-e3e7-4688-ad47-321077d2aaa9
google-gws-recovery-domain-verification=47176714
google-site-verification=zlftlmnNWctEAO5IRuB0_iyssOn2Pi6E8WcHMUy69PU
YjVqxBtTDCzBQKPoFOPaDASJVuammQEhUg5X5uo0F9fGWK/mD7gB3RmBrYSVLp6oSIZPJ7uDPNBDyaSa...
SPF v=spf1 include:in.spf.usdoj.gov include:_spf.salesforce.com include:acadisonline...
adobe-idp-site-verification=86640689d0bd466f7f7c8c98b61747e35e4535c00b32121fa575...
cisco-ci-domain-verification=30637df38d6d77bec0706b5da6685ac7f771c8d7a45506b5386...
atlassian-domain-verification=TmuPJ4i6JTJ0zDgapDZNnou/jKJSVgar8fb8hvDPy1ajuoZlol...
CAALookup not available with standard resolver
Resolved in 13 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

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+
Redirect Chain
0 redirect(s), 48 ms total
PASS
0 redirect(s), 48 ms total

https://dea.gov

48 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://dea.gov40348 msHTTP/1.1AkamaiGHost
A+
IPv6 Readiness
IPv6 reachable (0 ms)
PASS
IPv6 reachable (0 ms)
Info::
IPv6 is configured and reachable at 2600:1419:6200:287::2b0e, 2600:1419:6200:296::2b0e
Got: 0 ms connect
IPv6 Ready
AAAA Records 2600:1419:6200:287::2b0e, 2600:1419:6200:296::2b0e Connection Reachable (0 ms)
A
Domain Intelligence
dea.gov — via get.gov, 25 years, 10 months old
PASS
dea.gov — via get.gov, 25 years, 10 months old
Warning::
Domain expires in 82 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jul 14, 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

EXPIRED

July 14, 2026

SSL certificate

181 days

Issued by DigiCert Inc

Domain age

25 years, 10 months

Registered November 1, 2000

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2600:1419:6200:287::2b0e

Registrar

get.gov

Unlocked 6 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar get.gov
Created November 1, 2000 (25 years, 10 months ago)
Expires July 14, 2026 (2 months)
Last Updated July 19, 2025
Name Servers a1-61.akam.net, a10-66.akam.net, a12-67.akam.net, a13-64.akam.net, a7-65.akam.net, a8-66.akam.net
DNSSEC Enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 2600:1419:6200:287::2b0e
Data source: rdap (0.5s)

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 24 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
11 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.
25 ms
Total Time Total request time from DNS lookup through full response.
25 ms

Connection waterfall

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