Skip to content
https://la.gov

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
80
GRADE
B
FIX
1
REVIEW
5
PASS
3
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
3 PASS 5 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), 1082 ms total
REVIEW
1 redirect(s), 1082 ms total
Info::
Single redirect
Got: https://la.gov → https://www.louisiana.gov:443/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1082 ms total
Got: 1082 ms
Info::
Cross-domain redirect detected

https://la.gov

394 ms · HTTP/1.1

301

https://www.louisiana.gov:443/

688 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://la.gov301394 msHTTP/1.1awselb/2.0
2https://www.louisiana.gov:443/200688 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

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
URL Variants
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
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.la.gov/
200https://la.gov/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://la.gov/ https://www.louisiana.gov:443/

Consistent

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

Certificate validity

184
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 DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
2 A records, 163 ms lookup
PASS
2 A records, 163 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 99.83.196.67, 75.2.103.148
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-495.awsdns-61.com, ns-1880.awsdns-43.co.uk, ns-906.awsdns-49.net, ns-1064.awsdns-05.org
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: 163 ms
Got: 163 ms
A99.83.196.67, 75.2.103.148
AAAA
CNAME
NSns-495.awsdns-61.com, ns-1880.awsdns-43.co.uk, ns-906.awsdns-49.net, ns-1064.awsdns-05.org
MX
10 mx0a-00188601.pphosted.com
10 mx0b-00188601.pphosted.com
TXT
e2ma-verification=rysgb
SPF v=spf1 mx ip4:204.196.242.0/24 ip4:159.39.80.20/30 ip4:159.39.80.24/29 ip4:20.23...
airtable-verification=b1f83070ddaec141976c451b3376ad16
docusign=754cbdcb-9f02-4c77-bcea-2dfe2d89305a
2vbe6cs4mt1rdenpciaftku32b
google-site-verification=rgrWS-d6TxS4RizzWLW5Vc60S4mMDKcFB4dn-ECltOg
google-site-verification=0Ci7etmuy1eEjwv1FnxWgrN_fp3_QIjC4h0UzV40CH8
airtable-verification=96a338071995cd60d38e420128db139c
protonmail-verification=9059a7dd4fe017f327081f710ed16323dd628dcb
google-site-verification=XGMQPyQLfAVxPE3VlbCKFTznXXzZ5MRqQqoSVmTGuF0
7ufplq8b5glp1gmube81mekgbl
RjXwufSxdXnHaQfHDkMsNaXCwJyT8Hp0a2hLo8rIon3VVuNOlWmR+lyJAr2vY+4+aOg5cITth1U4qZxh...
knowbe4-site-verification=c999477a712fcaedff62ccdc75f4ce4f
wpe-verification=lernlagov
cloudflare-verify=187959715-738631009
bkdSY20/JhTO8wEPTsyCNbljiMZlBdeNfcKz8ZIHJHfTYPjiQ0R7ImZrQoElBk1Ns4tlszUBggAuwFTl...
successfactors-site-verification=OWFkNjk1Njk3Y2FlNDExYTQyNDNmZmFlNmY0ZjEyNWUxNjg...
esnefslk5ce1fr3f58n3p11i3s
cloudfare-verify=343716855-545494978
google-site-verification=oxZkCuQkJlK5YZSwX_LRjrSjaH9DXwOtj6KcSBnX7Cw
ufqf4t21n1gn1vbm061kpd1cc7
google-site-verification=_f6DFVum98e3GgFsP0qTV-_s3RoVCyGGqP5H4V1cksA
vd2bgzfnm514ggwn80kr3xzf92y24cb9
google-site-verification=6IIjBTmGOwLzSxnlCfFXkDj3_JU0iYIvPb1ifHLg4JU
apple-domain-verification=m1C7OWuWNqccYkDx
google-site-verification=9Z52tzPxOi-v5c5GXiOWtatjLTc7ThOfpH50aMLeNMk
kcmg5fbr8zwqnts9m57ns6pwwcsvqtxb
wpx2pf6lvnrzjjm61gp6nf3520z5rzl7
google-site-verification=0W-GkAK6wpizfBhoAHcLojibF0LQO-P68rs4VGvYTjM
7j99je6lqtr7qp17kvrocj8mms
duo_sso_verification=s9TrEVX1e6V7YaFw5KPVOCrOhcXJK3417rlxtKrsNduU8sJeLbsj49jQd5q...
google-site-verification=KMgxA1KZk0Y0Cs9DYNeRki5drourSQLAndGjEPpYSfE
7t26sde0lop3nfg7i466nds15p
adobe-idp-site-verification=59750f94e1e9635eccc0a0bfd8a69a9e73128cc815a0bb9b0ebc...
tadpj5h6248io6tqqqe9trcprt
MS=ms35698706
a9j0s5ij0ak4se4lit79dadpbj
CAALookup not available with standard resolver
Resolved in 163 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+
Domain Intelligence
la.gov — via get.gov, 26 years, 10 months old, hosted on AWS
PASS
la.gov — via get.gov, 26 years, 10 months old, hosted on AWS
Info::
Domain registered until Sep 3, 2026 (4 months remaining)
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: AWS
Got: AS16509
Domain expiry

80 days

September 3, 2026

SSL certificate

184 days

Issued by Amazon

Domain age

26 years, 10 months

Registered October 25, 1999

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

99.83.196.67

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 October 25, 1999 (26 years, 10 months ago)
Expires September 3, 2026 (4 months)
Last Updated September 8, 2025
Name Servers ns-1064.awsdns-05.org, ns-1880.awsdns-43.co.uk, ns-495.awsdns-61.com, ns-906.awsdns-49.net
DNSSEC Not enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 99.83.196.67
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.4s)

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

Connection waterfall

DNS Lookup 51 ms TCP Connect 1 ms TLS Handshake 315 ms Server Processing 106 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