Skip to content
https://texas.gov

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Sao Paulo, Brazil
302 Found
Checks
9
4 PASS 4 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.

B
Redirect Chain
1 redirect(s), 1070 ms total
REVIEW
1 redirect(s), 1070 ms total
Info::
Single redirect
Got: https://texas.gov → https://www.texas.gov:443/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://texas.gov
Warning::
Redirect overhead: 1070 ms total
Got: 1070 ms

https://texas.gov

603 ms · HTTP/1.1

302

https://www.texas.gov:443/

467 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://texas.gov302603 msHTTP/1.1awselb/2.0
2https://www.texas.gov:443/200467 msHTTP/1.1AmazonS3

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

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

C
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.texas.gov/
200https://texas.gov/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://texas.gov/ https://texas.gov:443/

Use 301 (permanent) instead of 302 (temporary)

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

Certificate validity

231
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
  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
2 A records, 150 ms lookup
PASS
2 A records, 150 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 75.2.85.206, 99.83.171.12
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns.capnet.state.tx.us, ns5.capnet.state.tx.us, ns9.tex-an.net, merlin.texan.state.tx.us
Info::
2 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: 150 ms
Got: 150 ms
A75.2.85.206, 99.83.171.12
AAAA
CNAME
NSns.capnet.state.tx.us, ns5.capnet.state.tx.us, ns9.tex-an.net, merlin.texan.state.tx.us
MX
0 pigeon.state.tx.us
2 emu.tx.net
TXT
g6bv01schrk1tnn28n7ofo2086
orgodtbd4obcsemi442u9rqcos
SPF v=spf1 ip4:141.198.193.120/29 ip4:168.58.222.3 ip4:206.16.212.246 ip4:204.66.40....
CAALookup not available with standard resolver
Resolved in 150 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+
Crawlability
robots.txt present, sitemap with 303 URLs
PASS
robots.txt present, sitemap with 303 URLs
Info::
robots.txt is present
Got: 328 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 303 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 328 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /
Disallow: /government-services-directory/*/
Disallow: /texas-state-agencies-departments/*/
Disallow: /es/directorio-servicios-gubernamentales/*/
Disallow: /es/agencias-departamentos-del-estado-de-texas/*/
Disallow: /search/?search=
Disallow: /es/search/?search=
Sitemap: https://www.texas.gov/sitemap.xml

A+
Domain Intelligence
texas.gov — via get.gov, 28 years, 11 months old, hosted on AWS
PASS
texas.gov — via get.gov, 28 years, 11 months old, hosted on AWS
Info::
Domain registered until Sep 2, 2026 (4 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: AWS
Got: AS16509
Domain expiry

81 days

September 2, 2026

SSL certificate

231 days

Issued by Amazon

Domain age

28 years, 11 months

Registered October 2, 1997

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

75.2.85.206

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 2, 1997 (28 years, 11 months ago)
Expires September 2, 2026 (4 months)
Last Updated September 7, 2025
Name Servers merlin.texan.state.tx.us, ns.capnet.state.tx.us, ns5.capnet.state.tx.us, ns9.tex-an.net
DNSSEC Enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 75.2.85.206
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.9s)

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 600 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
149 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.
336 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
600 ms
Total Time Total request time from DNS lookup through full response.
600 ms

Connection waterfall

DNS Lookup 149 ms TCP Connect 1 ms TLS Handshake 336 ms Server Processing 113 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