Skip to content
https://ahrq.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
3
PASS
5
INFO
0
Probed from Madrid, Spain
302 Found
Checks
9
5 PASS 3 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
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 3808 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 3808 B Sitemaps referenced 0 User-agents *, GPTBot, ChatGPT-User, CCBot, anthropic-ai, Claude-Web, Googlebot Blocking No — crawling allowed
#

# robots.txt

#

# This file is to prevent the crawling and indexing of certain parts

# of your site by web crawlers and spiders run by sites like Yahoo!

# and Google. By telling these "robots" where not to go on your site,

# you save bandwidth and server resources.

#

# This file will be ignored unless it is at the root of your host:

# Used:    http://example.com/robots.txt

# Ignored: http://example.com/site/robots.txt

#

# For more information about the robots.txt standard, see:

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


User-agent: *

Crawl-delay: 1
# CSS, JS, Images

Allow: /core/*.css$

Allow: /core/*.css?

Allow: /core/*.js$

Allow: /core/*.js?

Allow: /core/*.gif

Allow: /core/*.jpg

Allow: /core/*.jpeg

Allow: /core/*.png

Allow: /core/*.svg

Allow: /profiles/*.css$

Allow: /profiles/*.css?

Allow: /profiles/*.js$

Allow: /profiles/*.js?

Allow: /profiles/*.gif

Allow: /profiles/*.jpg

Allow: /profiles/*.jpeg

Allow: /profiles/*.png

Allow: /profiles/*.svg

# Directories

Disallow: /core/

Disallow: /profiles/

# Files

Disallow: /README.txt

Disallow: /web.config

# Paths (clean URLs)

Disallow: /admin/

Disallow: /comment/reply/

Disallow: /filter/tips

Disallow: /node/add/

Disallow: /search/

Disallow: /user/register/

Disallow: /user/password/

Disallow: /user/login/

Disallow: /user/logout/

# Paths (no clean URLs)

Disallow: /index.php/admin/

Disallow: /index.php/comment/reply/

Disallow: /index.php/filter/tips

Disallow: /index.php/node/add/

Disallow: /index.php/search/

Disallow: /index.php/user/password/

Disallow: /index.php/user/register/

Disallow: /index.php/user/login/

Disallow: /index.php/user/logout/



# CUSTOM CONFIG BELOW

Disallow /redirects/

# Filterable view pages

Disallow: /research/findings/evidence-based-reports/search.html?

Disallow: /research/findings/studies/index.html?

Disallow: /news/newsletters/e-newsletter/index.html?

Disallow: /news/events/other/index.html?

Disallow: /news/newsroom/press-releases/index.html?

Disallow: /news/newsroom/noticias/index.html?

Disallow: /news/newsroom/articles-of-interest/index.html?

Disallow: /news/newsroom/case-studies/index.html?

Disallow: /cahps/bibliography/index.html?

Disallow: /cahps/surveys-guidance/item-sets/search.html?

Disallow: /cahps/faq/index.html?

Disallow: /programs/index.html?

Disallow: /tools/index.html?

Disallow: /data/dataresources/index.html?


# PBRN Registry filtered pages - prevent aggressive bot crawling

Disallow: /ncepcr/communities/pbrn/registry/index.html?


# Block aggressive AI/ML bots from PBRN Registry

User-agent: GPTBot

Disallow: /ncepcr/communities/pbrn/


User-agent: ChatGPT-User

Disallow: /ncepcr/communities/pbrn/


User-agent: CCBot

Disallow: /ncepcr/communities/pbrn/


User-agent: anthropic-ai

Disallow: /ncepcr/communities/pbrn/


User-agent: Claude-Web

Disallow: /ncepcr/communities/pbrn/



# Googlebot - Allow all paths

User-agent: Googlebot

Allow: /

Disallow:


# Special use pages

Disallow: /research/findings/ta/technical-assistance-form-thank-you.html

Disallow: /funding/contracts/proposal-instructions.html


# Deprecated pages

Disallow: /sites/default/files/publications/files/organization-chart.pdf

Disallow: /whatsnew.html


# Temporary

Disallow: /news/events/ahrq-research-summit-learning.html

Allow: /professionals/quality-patient-safety/hais/tools/perinatal-care/index.html

Disallow: /professionals/quality-patient-safety/hais/tools/perinatal-care/

Disallow: /nhguide/toolkits/determine-whether-to-treat/antibiotic-tool.html

Disallow: /topics/index-v2-f5L2sheVSpUMT9tL.html

Disallow: /learning-health-systems/

Disallow: /whatsnew.html

Disallow: /health-literacy

Disallow: /rural-post-partum-challenge

Disallow: /questions

Disallow: /challenges

Disallow: /innovations
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

34
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
1 A records, 48 ms lookup
PASS
1 A records, 48 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 162.99.46.11
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns4-06.azure-dns.info, ns1-06.azure-dns.com, ns2-06.azure-dns.net, ns3-06.azure-dns.org
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: 48 ms
Got: 48 ms
A162.99.46.11
AAAA
CNAME
NSns4-06.azure-dns.info, ns1-06.azure-dns.com, ns2-06.azure-dns.net, ns3-06.azure-dns.org
MX
10 primary.us.etp.fireeyegov.com
20 alt1.us.etp.fireeyegov.com
30 alt2.us.etp.fireeyegov.com
40 alt3.us.etp.fireeyegov.com
TXT
SPF v=spf1 ip4:34.225.84.221 ip4:158.70.152.0/24 ip4:158.72.152.0/24 ip4:158.72.139....
_eqomgmy4ltlt89m2jot0y42ydi6oqko
ZOOM_verify_eC889e4NlFpCXbpNJIrowh
identrust_validate=1inhnmKQGZ8YyvkkCxXOMhqUdPEPiGje0k1x13LWoZen
_jnzp2py7hverf59gcmtt0ik0wo4vg86
google-site-verification=h6coIDB6HuIKJJa_8aCW8F8RDQxE0uqdm3r8aINiyk4
n8mc4y5f068k42xcpxyzcd4nz5whkkkt
qcxwgj0l6yrhdy14gtpqp2ncr8qcgqwd
MS=ms15674864
PUIKiiNL899E/tXyWrUruOxPD7N3RFhj+cEN9oFyeIU4XkTEdSzPjVjWaFhmPnwc9NSdRFO0zNLG/rSV...
lccwl3rcvlrz0dx6mv8r4256r4lmlk85
rbv0pdlgfgcof2bkbda134fj4u
CAALookup not available with standard resolver
Resolved in 48 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
1 redirect(s), 438 ms total
PASS
1 redirect(s), 438 ms total
Info::
Single redirect
Got: https://ahrq.gov → https://www.ahrq.gov/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://ahrq.gov

https://ahrq.gov

396 ms · HTTP/1.1

302

https://www.ahrq.gov/

42 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ahrq.gov302396 msHTTP/1.1Microsoft-IIS/10.0
2https://www.ahrq.gov/40342 msHTTP/1.1CloudFront

See the visual redirect chain in the HTTP Probe tab →

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

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

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

HTTP → HTTPS

301http://ahrq.gov/ https://ahrq.gov/

Consistent

A+
Domain Intelligence
ahrq.gov — via get.gov, 26 years, 10 months old, hosted on HHSNET-NOC-ASN - U.S. Dept. of Health and Human Services, US
PASS
ahrq.gov — via get.gov, 26 years, 10 months old, hosted on HHSNET-NOC-ASN - U.S. Dept. of Health and Human Services, US
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.
Info::
Hosting: HHSNET-NOC-ASN - U.S. Dept. of Health and Human Services, US
Got: AS26810
Domain expiry

26 days

August 12, 2026

SSL certificate

34 days

Issued by DigiCert Inc

Domain age

26 years, 10 months

Registered October 13, 1999

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

HHSNET-NOC-ASN - U.S. Dept. of Health and Human Services, US

ASN AS26810

162.99.46.11

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 13, 1999 (26 years, 10 months ago)
Expires August 12, 2026 (3 months)
Last Updated September 9, 2025
Name Servers ns1-06.azure-dns.com, ns2-06.azure-dns.net, ns3-06.azure-dns.org, ns4-06.azure-dns.info
DNSSEC Enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 162.99.46.11
ASN AS26810 (HHSNET-NOC-ASN - U.S. Dept. of Health and Human Services, US)
Provider HHSNET-NOC-ASN - U.S. Dept. of Health and Human Services, US
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 455 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
58 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
98 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
203 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
456 ms
Total Time Total request time from DNS lookup through full response.
456 ms

Connection waterfall

DNS Lookup 58 ms TCP Connect 98 ms TLS Handshake 203 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