Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DTLS Certificate Expiry & RecommendationsAction6 days until leaf cert expires — 5 issues to addressFIX
Certificate validity
Recommended actions
- Renew certificate — 6 days remaining
- Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
- 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
DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BRedirect Chain1 redirect(s), 1114 ms totalREVIEW
https://alabama.gov
467 ms · HTTP/1.0
https://www.alabama.gov/
647 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://alabama.gov | 301 | 467 ms | HTTP/1.0 | BigIP |
| 2 | https://www.alabama.gov/ | 200 | 647 ms | HTTP/1.1 | AmazonS3 |
See the visual redirect chain in the HTTP Probe tab →
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
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.
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
A+DNS Records2 A records, 66 ms lookupPASS
| A | 206.16.212.91, 63.241.205.163 |
| AAAA | — |
| CNAME | — |
| NS | ns4-08.azure-dns.info, ns2-08.azure-dns.net, ns1-08.azure-dns.com, ns3-08.azure-dns.org |
| MX | 10 alabama-gov.mail.protection.outlook.com |
| TXT | btQuZ10Ko19O0xAGyXUMwqvnIc75G6PfMK9WrE3pD7k= v8brd5f9afrml3uett875g3a3e globalsign-domain-verification=DF22864608EFC969D782609F40207234 openai-domain-verification=dv-Jg10R3MvWQ3VKZmYVWWUJOeD sudlrcg7juboi0el7991smim44 y3ElM4GytFetLzQo7oB9CorUy8I395FngeX3B3ZvrEzINQXaZiy3Mpa3vwmjug1mM4AzrEqjzA9GhdJ+... SPF v=spf1 include:_spf.alabama.gov -all 1712e6a50be51e52f5bb8414d44970f088a7fde1c243b57a738bba73f465432 8h7pv0pdobs80r03r0lcfvir36 enpvlt8duah0onoi6rl727l8o MS=ms45881342 ajeigu8euk8dck0eparm4v0u41 |
| CAA | Lookup not available with standard resolver |
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.
A+Domain Intelligencealabama.gov — via get.gov, 24 years, 6 months old, hosted on TYLERTECH-NIC2 - Tyler Technologies, Inc., USPASS
50 days
August 4, 2026
6 days
Issued by GlobalSign nv-sa
24 years, 6 months
Registered January 29, 2002
Not enabled
Protects against DNS spoofing
TYLERTECH-NIC2 - Tyler Technologies, Inc., US
ASN AS393360
63.241.205.163
get.gov
Expiry timeline
Recommended actions
- Renew the domain or enable auto-renewal to prevent accidental expiry
- Renew the TLS certificate or verify auto-renewal is working
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.
Learn more ▾ ▴
DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.
Source: ICANN / RFC 4033
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