Skip to content
https://govtrank.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
73
GRADE
C
FIX
1
REVIEW
9
PASS
6
INFO
1
Probed from Sao Paulo, Brazil
200 OK
Checks
17
6 PASS 9 REVIEW 1 FIX
F
Multi-Resolver DNS Speed
Action
All public resolvers failed to resolve the domain
FIX
All public resolvers failed to resolve the domain
Critical::
DNS resolution failed against all public resolvers
1.1.1.1, 8.8.8.8, and 9.9.9.9 all failed to resolve this domain. Almost always means the domain is delegated incorrectly, the authoritative servers are unreachable, or the resolution returned NXDOMAIN/SERVFAIL across the board.
C
DNSSEC
Action
DNSSEC posture not checked
REVIEW
DNSSEC posture not checked
Info::
DNSSEC posture not checked
Could not query the validating resolver for DNSSEC status. Network or resolver outage.
C
CAA Records
Action
CAA posture not checked
REVIEW
CAA posture not checked
Info::
CAA records not checked
Could not query the resolver for CAA records. Network or resolver outage.
C
Reverse DNS
Action
0/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR lookup failed for 172.67.174.88: lookup 172.67.174.88: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 104.21.80.49: lookup 104.21.80.49: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2606:4700:3030::ac43:ae58: lookup 2606:4700:3030::ac43:ae58: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2606:4700:3030::6815:5031: lookup 2606:4700:3030::6815:5031: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
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 0 Expected: 301 redirect to HTTPS

www / non-www

https://www.govtrank.com/
200https://govtrank.com/

HTTP → HTTPS

http://govtrank.com/

HTTP version does not redirect to HTTPS

C
HTTP Probe Timing
Action
Total 1721 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
14 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.
12 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
719 ms
Total Time Total request time from DNS lookup through full response.
1.72 s

Connection waterfall

DNS Lookup 14 ms TCP Connect 1 ms TLS Handshake 12 ms Server Processing 692 ms Content Transfer 1.00 s
B
TLS Certificate Expiry & Recommendations
75 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: connection error, /health: connection error, /healthz: connection error, /ping: connection error, /status: connection error.
A+
DNS Records
2 A records, 15 ms lookup
PASS
2 A records, 15 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 172.67.174.88, 104.21.80.49
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:3030::ac43:ae58, 2606:4700:3030::6815:5031
Info::
2 nameserver(s) configured
Got: amy.ns.cloudflare.com, yew.ns.cloudflare.com
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 15 ms
Got: 15 ms
A172.67.174.88, 104.21.80.49
AAAA2606:4700:3030::ac43:ae58, 2606:4700:3030::6815:5031
CNAME—
NSamy.ns.cloudflare.com, yew.ns.cloudflare.com
MX
10 mail.govtrank.com
TXT
SPF v=spf1 a mx ip4:111.118.176.141 include:_spf.sitecountry.net ~all
CAALookup not available with standard resolver
Resolved in 15 ms
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Redirect Chain
No redirect data available
PASS
No redirect data available
Info::
No redirect data captured
A+
IPv6 Readiness
IPv6 reachable (3 ms)
PASS
IPv6 reachable (3 ms)
Info::
IPv6 is configured and reachable at 2606:4700:3030::ac43:ae58, 2606:4700:3030::6815:5031
Got: 3 ms connect
IPv6 Ready
AAAA Records 2606:4700:3030::ac43:ae58, 2606:4700:3030::6815:5031 Connection Reachable (3 ms)
A
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Site is served via Cloudflare CDN (edge: GRU)
Got: cf-ray: a1b0b1506e20aa89-GRU
Info::
CDN cache status: DYNAMIC
CDN Detected: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: a1b0b1506e20aa89-GRU
A+
CDN Cache Observability
Cache state: DYNAMIC
PASS
Cache state: DYNAMIC
Info::
CDN cache state observable via 1 header(s)
Got: cf-cache-status=DYNAMIC
Domain Intelligence
Domain intelligence data not available
INFO
Domain intelligence data not available

RDAP and WHOIS lookup both failed

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback