Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.FIPv6 ReadinessActionIPv6 records exist but unreachableFIX
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.
Learn more ▾ ▴
Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.
Source: RFC 8305 (Happy Eyeballs)
DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BCrawlabilityno robots.txt, no sitemapREVIEW
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
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.
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
No robots.txt found
This is fine for most sites — a missing robots.txt allows all crawling by default.
No sitemap found
Adding a sitemap helps search engines discover your pages.
BTLS Certificate Expiry & Recommendations242 days until leaf cert expires — 2 issues to addressREVIEW
Certificate validity
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
A+DNS Records1 A records, 51 ms lookupPASS
| A | 162.99.249.241 |
| AAAA | 2607:f220:410:405::a263:f9f1 |
| CNAME | — |
| NS | steven.ns.cloudflare.com, collins.ns.cloudflare.com |
| MX | 10 nihcesxwayst05.hub.nih.gov 10 nihcesxwayst04.hub.nih.gov 10 nihcesxway6.hub.nih.gov 10 nihcesxway3.hub.nih.gov 10 nihcesxwayst06.hub.nih.gov 10 nihcesxway5.hub.nih.gov 10 nihcesxwayst03.hub.nih.gov 10 nihcesxway4.hub.nih.gov |
| TXT | _u4q4fh8pi7q6rcasbqvken4fq4k5vss openai-domain-verification=dv-CHWw8KGNrNobWwf1ysbMcT7G adobe-idp-site-verification=a8cac6bfb792055eedb05a454797fb3da8f92e2704942172754c... q0wg343v1m9ywj3htc6g9hws1zp3cz6c docusign=2485d8b6-f19e-4116-85dc-6bef9cf2ce2c v2r3jy0ztblqm0zqrcqjhvcjmsn672k4 3ms9wpynsj7ntm3cz8v2z5wkxkvvqv5w pk0kssxvw5qdwhsyyx49x6prs8qlf8c8 SPF v=spf1 include:nih.gov ip4:128.121.42.218 include:ees.hhs.gov ip4:3.32.94.73 a:s... docusign=047b2204-0dcc-4ead-8654-51fb92a92949 _qh6ad8l1ymu3wmnqbtdsx6j55yhv0dw |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
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.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
ARedirect Chain1 redirect(s), 507 ms totalPASS
https://hrsa.gov
421 ms · HTTP/1.1
https://www.hrsa.gov/
86 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://hrsa.gov | 301 | 421 ms | HTTP/1.1 | Microsoft-IIS/10.0 |
| 2 | https://www.hrsa.gov/ | 403 | 86 ms | HTTP/1.1 |
See the visual redirect chain in the HTTP Probe tab →
AURL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
HTTP → HTTPS
Use 301 (permanent) instead of 302 (temporary)
A+Domain Intelligencehrsa.gov — via get.gov, 28 years, 2 months oldPASS
39 days
August 25, 2026
242 days
Issued by IdenTrust
28 years, 2 months
Registered June 23, 1998
Enabled
Protects against DNS spoofing
Unknown
2607:f220:410:405::a263:f9f1
get.gov
Expiry timeline
Recommended actions
- Renew the domain or enable auto-renewal to prevent accidental expiry
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
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.
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