Skip to content
https://drugabuse.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 Madrid, Spain
202 HTTP 202
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.

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

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 202 Expected: 301 redirect to HTTPS

www / non-www

202https://www.drugabuse.gov/
200https://drugabuse.gov/

HTTP → HTTPS

202http://drugabuse.gov/

HTTP version does not redirect to HTTPS

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

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A
DNS Records
1 A records, 386 ms lookup
PASS
1 A records, 386 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 3.33.152.5
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ns3.nih.gov, ns2.nih.gov, ns.nih.gov
Info::
11 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
Warning::
DNS resolution is slow (386 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 386 ms
A3.33.152.5
AAAA
CNAME
NSns3.nih.gov, ns2.nih.gov, ns.nih.gov
MX
10 nihcesxway.hub.nih.gov
10 nihcesxwayst06.hub.nih.gov
10 nihcesxwayst03.hub.nih.gov
10 nihcesxwayst01.hub.nih.gov
10 nihcesxway2.hub.nih.gov
10 nihcesxwayst04.hub.nih.gov
10 nihcesxwayst05.hub.nih.gov
10 nihcesxway5.hub.nih.gov
10 nihcesxway3.hub.nih.gov
10 nihcesxway4.hub.nih.gov
10 nihcesxwayst02.hub.nih.gov
TXT
e999d0a9546a4f98ac4913ba861f03bd
MS=ms39407702
SPF v=spf1 include:nih.gov ~all
hS8ZY6GnqAqWGMmQB7i9sEmrpw9wOiIeanrOYNAfuw6bvmjYr52KEFEB5QsVEaF+IFkTX9GnerkIJSSf...
CAALookup not available with standard resolver
Resolved in 386 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.

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://drugabuse.gov

https://drugabuse.gov

306 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://drugabuse.gov202306 msHTTP/1.1awselb/2.0
A+
Domain Intelligence
drugabuse.gov — via get.gov, 27 years, 2 months old, hosted on AWS
PASS
drugabuse.gov — via get.gov, 27 years, 2 months old, hosted on AWS
Info::
Domain registered until Aug 25, 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.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

8 days

August 25, 2026

SSL certificate

94 days

Issued by Entrust Limited

Domain age

27 years, 2 months

Registered July 8, 1999

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

3.33.152.5

Registrar

get.gov

Unlocked 3 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 8, 1999 (27 years, 2 months ago)
Expires August 25, 2026 (4 months)
Last Updated March 4, 2026
Name Servers ns.nih.gov, ns2.nih.gov, ns3.nih.gov
DNSSEC Enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 3.33.152.5
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.5s)

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

Connection waterfall

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