Skip to content
https://arkansas.gov

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
6 PASS 2 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.

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
TLS Certificate Expiry & Recommendations
115 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

115
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
1 A records, 166 ms lookup
PASS
1 A records, 166 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 170.94.194.134
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
5 nameserver(s) configured
Got: dns4.state.ar.us, dns1.state.ar.us, dns5.state.ar.us, dns3.state.ar.us, dns2.state.ar.us
Info::
1 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: 166 ms
Got: 166 ms
A170.94.194.134
AAAA—
CNAME—
NSdns4.state.ar.us, dns1.state.ar.us, dns5.state.ar.us, dns3.state.ar.us, dns2.state.ar.us
MX
10 arkansas-gov.mail.protection.outlook.com
TXT
ms-domain-verification=5774a07d-95c0-4f60-8cec-48c953bb268a
SPF v=spf1 mx ip4:170.94.213.83/32 ip4:170.94.213.94/32 ip4:170.94.157.25/32 ip4:170...
breachbits-verification=bd8cb086480be96e79ce82694da1be8ce9a1b5bb
google-site-verification=6rWGVqyb2f-5RY4VzuBYEWvEKK-nhOLenAvtfbCpShw
plmsol6843387u3eqkhsuua5q2
CAALookup not available with standard resolver
Resolved in 166 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more ▾

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

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
1 redirect(s), 950 ms total
PASS
1 redirect(s), 950 ms total
Info::
Single redirect
Got: https://arkansas.gov → https://portal.arkansas.gov/ (301)
Info::
Redirect overhead: 950 ms total
Got: 950 ms
Info::
Cross-domain redirect detected

https://arkansas.gov

544 ms · HTTP/1.1

301

https://portal.arkansas.gov/

406 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://arkansas.gov301544 msHTTP/1.1
2https://portal.arkansas.gov/200406 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 21 URLs
PASS
robots.txt present, sitemap with 21 URLs
Info::
robots.txt is present
Got: 2586 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 21 entries
Info::
Sitemap index with 21 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 2586 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /accessanswers.php
Disallow: /accessresults.php
Disallow: /add_favorite.php
Disallow: /ag/opinions/search-agops.php
Disallow: /arjudiciary/ # courts.state.ar.us
Disallow: /asp/ # www.asp.state.ar.us
Disallow: /aspb/ # www.plantboard.org
Disallow: /awcc/ # www.awcc.state.ar.us
Disallow: /basic_notifications.php
Disallow: /childcare/detail.php
Disallow: /demo/ # demo pages
Disallow: /development/ # development area
Disallow: /dfa/child_support/ocse_offices_results.php
Disallow: /dfa/osra/osra_revenue_detail.php
Disallow: /dfa/osra/osra_map_detail.php
Disallow: /directory/
Disallow: /doc/inmate_info/search.cgi
Disallow: /doc/inmate_info/search.php
Disallow: /forestry/ # www.forestry.state.ar.us
Disallow: /index.php
Disallow: /government.php
Disallow: /government_assn.php
Disallow: /government_details.php
Disallow: /government_details_expanded.php
Disallow: /government_exec.php
Disallow: /government_fed.php
Disallow: /government_hs.php
Disallow: /government_local.php
Disallow: /government_local_search.php
Disallow: /government_name.php
Disallow: /government_pr.php
Disallow: /government_rep_search.php
Disallow: /ha/trails/index.php
Disallow: /business.php
Disallow: /business_emp.php
Disallow: /business_gov.php
Disallow: /business_ind.php
Disallow: /business_pro.php
Disallow: /business_res.php
Disallow: /comingsoon.php
Disallow: /community.php
Disallow: /community_gov.php
Disallow: /community_his.php
Disallow: /community_lib_results.php
Disallow: /community_liv.php
Disallow: /community_liv_search.php
Disallow: /community_ncg.php
Disallow: /community_pr.php
Disallow: /education.php
Disallow: /education_gov.php
Disallow: /education_res.php
Disallow: /education_sch_alpha.php
Disallow: /education_sch_search.php
Disallow: /event_detail.php
Disallow: /family.php
Disallow: /family_child.php
Disallow: /family_gen.php
Disallow: /family_health.php
Disallow: /family_seniors.php
Disallow: /online_services_alpha.php
Disallow: /online_services.php
Disallow: /resource_detail.php
Disallow: /show_calendar.php
Disallow: /travel.php
Disallow: /travel_all.php
Disallow: /travel_gov.php
Disallow: /travel_results.php
Disallow: /travel_search.php
Disallow: /travel_tour.php
Disallow: /reports/
Disallow: /governor/gems/forum
Disallow: /governor/gems/eletter/view-archive.cgi
Disallow: /governor/map/
Disallow: /health/ # www.healthyarkansas.com
Disallow: /labor/code.php
Disallow: /lobbyist/arliab/index.php
Disallow: /nurse/ # www.arsbn.org
Disallow: /sos/ # www.sosweb.state.ar.us
Disallow: /staff/ # local stuff
Disallow: /search/
Disallow: /search2/
sitemap.xml 200 OK
Type Sitemap Index URLs 21 entries Valid XML Yes
Child Sitemaps:
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.arkansas.gov/
200https://arkansas.gov/

Preferred variant: non-www

HTTP → HTTPS

301http://arkansas.gov/ → https://portal.arkansas.gov/

Consistent

A+
Domain Intelligence
arkansas.gov — via get.gov, 26 years, 1 months old, hosted on DISNW1 - State Of Arkansas, Division of Information Systems, US
PASS
arkansas.gov — via get.gov, 26 years, 1 months old, hosted on DISNW1 - State Of Arkansas, Division of Information Systems, US
Info::
Domain registered until Aug 19, 2026 (3 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: DISNW1 - State Of Arkansas, Division of Information Systems, US
Got: AS21852
Domain expiry

65 days

August 19, 2026

SSL certificate

115 days

Issued by Sectigo Limited

Domain age

26 years, 1 months

Registered July 24, 2000

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

DISNW1 - State Of Arkansas, Division of Information Systems, US

ASN AS21852

170.94.194.134

Registrar

get.gov

Unlocked 5 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 July 24, 2000 (26 years, 1 months ago)
Expires August 19, 2026 (3 months)
Last Updated August 24, 2025
Name Servers dns1.state.ar.us, dns2.state.ar.us, dns3.state.ar.us, dns4.state.ar.us, dns5.state.ar.us
DNSSEC Not enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 170.94.194.134
ASN AS21852 (DISNW1 - State Of Arkansas, Division of Information Systems, US)
Provider DISNW1 - State Of Arkansas, Division of Information Systems, US
Data source: rdap (0.7s)

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

Connection waterfall

DNS Lookup 159 ms TCP Connect 139 ms TLS Handshake 286 ms Server Processing 142 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