Skip to content
https://az.gov

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Madrid, Spain
403 Forbidden
Checks
9
5 PASS 4 REVIEW
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
TLS Certificate Expiry & Recommendations
86 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

86
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
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9f07ee7e38c213f4-CDG
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9f07ee7e38c213f4-CDG
A+
DNS Records
2 A records, 162 ms lookup
PASS
2 A records, 162 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.18.20.208, 104.18.21.208
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1968.awsdns-54.co.uk, ns-675.awsdns-20.net, ns-1324.awsdns-37.org, ns-127.awsdns-15.com
Info::
5 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: 162 ms
Got: 162 ms
A104.18.20.208, 104.18.21.208
AAAA
CNAME
NSns-1968.awsdns-54.co.uk, ns-675.awsdns-20.net, ns-1324.awsdns-37.org, ns-127.awsdns-15.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 alt4.aspmx.l.google.com
10 alt3.aspmx.l.google.com
TXT
SPF v=spf1 a ip4:68.232.140.126 ip4:34.239.38.245 ip4:68.232.137.110 ip4:166.86.2.15...
p6q35pe7kcj1veb5apor8tb92s
00D3d0000008bLc=1TBcs00000004LU
ca3-63d6cbd880b74747b5efb8e6c8a664fa
q1scqnms10isd0m332pojb2688
nqsq947ninv6drk9uf4j9nadgm
6j2mqshbtbvik2j56s6ldguae7
knowbe4-site-verification=398c042428026112b07145a5249dd62c
ca3-0d243a4a0e2a466c87b5f2e7d3f7c761
MS=ms86533034
MS=ms66454069
e88hafov3r7acss559gsruee42
68mm779fj4hsc278rhj3eaff4n
6fxm6nx3ny16fc9pxklskjhz1ks8q5m8
asv=30208d5c0a1e798c74fa727f87155d21
duo_sso_verification=59J4QeBAVwZ7OeYG42YOuu07XOewDRqL3B1MF4Df3ZFTwN7gDNMAsQsZuk4...
704edqestpnad6dbt62ukcn41t
apple-domain-verification=OmqIaD8pD2jRpBkP
dlav7r8it1sag860au9n9itj8t
apple-domain-verification=Uv54yVdjHUIyiSZD
5vf5smdkaujsq92ss6an53rkgf
baki2ss7ks2gl6vmh87ksfueeo
2408qakb3nambilsratucg4g2s
adobe-idp-site-verification=d932a666c2f545dbe1cb3fa71bd4b2fc601c7e492299951b4e38...
smartsheet-site-validation=GdPAD4v1tPsHRKXsrPKMOVzr7XRIzlR8
google-site-verification=V3iqgari4r-YwltEnKr5nn4ucqlkd1fiGBFUOcUhKUs
google-site-verification=zzJlACVSrIqhD-KcDT_M_I_VLnhZ0BSEoDzj8DXUBK0
girai28m5hjrdntv1e0t72sv8q
9uv96d84hp34pgdk195rjc0lvh
ame7tbpo8o0mk8v0t14fsr20ev
lbu3ktfhkvf7b6bucjdrsdicu1
mgtnha3dcsp5m63wtdb9
duo_sso_verification=ZNSmHEQyLggqmq3Fr27UuHvtwLQoF708pkDy6LB5Zoryx0W7B2C5IwWjbMy...
_r9qiqrmb2hodgs3u8786ew5i8syo04m
_qlu7rcdyzq13hij2nwpz687d1176rft
ks8lfwfdtsj3f5v57ln45zb9s9prgrt9
e7iudl99girkg8g2qcn0nddpde
1e6dgsc8rhfpbvv37vet62ehvf
duo_sso_verification=f1iPFvoxhb9irVv7lDY2YJLOhcLYxTkLqRYKJy78bEbBidYd8JWvwACGPzP...
apple-domain-verification=jRyeNFjJe3wXyt2o
_globalsign-domain-verification=3e727VkmgbxMfl86szVfmT94H7DohvdUEI4EmKJAkY
MS=ms68240651
apple-domain-verification=7SAGDNZQ25Ei1WLt
df7gedplrclf68q3mbul0b9k96
google-site-verification=wOI0eSanI_wvGq9CpLl7FO7r46_nlMThOmXFDiek30M
mhjqt97g0w2g2bb3c1l6hhjrjyjr2sm1
google-site-verification=7RW7MMlxOCiLToWFP-eUECkJ7kSRCSUCRS1asO4soCM
CAALookup not available with standard resolver
Resolved in 162 ms

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
0 redirect(s), 76 ms total
PASS
0 redirect(s), 76 ms total

https://az.gov

76 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://az.gov40376 msHTTP/1.1cloudflare
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.az.gov/
200https://az.gov/

Preferred variant: non-www

HTTP → HTTPS

301http://az.gov/ https://az.gov/

Consistent

A
Domain Intelligence
az.gov — via get.gov, 27 years, 4 months old, hosted on Cloudflare
PASS
az.gov — via get.gov, 27 years, 4 months old, hosted on Cloudflare
Warning::
Domain expires in 83 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jul 15, 2026
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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: Cloudflare
Got: AS13335
Domain expiry

1 day

July 15, 2026

SSL certificate

86 days

Issued by Google Trust Services

Domain age

27 years, 4 months

Registered May 5, 1999

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

104.18.20.208

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 DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar get.gov
Created May 5, 1999 (27 years, 4 months ago)
Expires July 15, 2026 (2 months)
Last Updated July 20, 2025
Name Servers ns-127.awsdns-15.com, ns-1324.awsdns-37.org, ns-1968.awsdns-54.co.uk, ns-675.awsdns-20.net
DNSSEC Not enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 104.18.20.208
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
Data source: rdap (1.6s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

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.

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 121 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
47 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
17 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
22 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
121 ms
Total Time Total request time from DNS lookup through full response.
121 ms

Connection waterfall

DNS Lookup 47 ms TCP Connect 17 ms TLS Handshake 22 ms Server Processing 35 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