Skip to content
https://ohio.gov

Infrastructure

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

C
HTTP Probe Timing
Action
Total 1548 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
166 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
167 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
172 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
962 ms
Total Time Total request time from DNS lookup through full response.
1.55 s

Connection waterfall

DNS Lookup 166 ms TCP Connect 167 ms TLS Handshake 172 ms Server Processing 457 ms Content Transfer 587 ms
B
TLS Certificate Expiry & Recommendations
183 days until leaf cert expires — 5 issues to address
REVIEW

Certificate validity

183
days left
0d 30d 60d 90d+

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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
4 A records, 163 ms lookup
PASS
4 A records, 163 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 18.161.6.10, 18.161.6.14, 18.161.6.57, 18.161.6.20
Info::
No IPv6 (AAAA) records
Info::
8 nameserver(s) configured
Got: ns2.ohio.gov, ns6.ohio.gov, ns1.ohio.gov, ns3.ohio.gov, ns7.ohio.gov, ns8.ohio.gov, ns5.ohio.gov, ns4.ohio.gov
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: 163 ms
Got: 163 ms
A18.161.6.10, 18.161.6.14, 18.161.6.57, 18.161.6.20
AAAA
CNAME
NSns2.ohio.gov, ns6.ohio.gov, ns1.ohio.gov, ns3.ohio.gov, ns7.ohio.gov, ns8.ohio.gov, ns5.ohio.gov, ns4.ohio.gov
MX
0 ohio-gov.mail.protection.outlook.com
TXT
google-site-verification=XWpgI0ZSGIBlkHlPClqzC04xK1XYOWr-YKnbDwZb2gQ
tgq5mliv7b8jiof3l2ip35kost
google-site-verification=-CFZyK9vinw282OG4WebmXDMOseSJ328H7QVD5tFjF8
google-site-verification=rgWpvBFfwsaBdpyOboaBiWb64T1DCDSAPfOvZU9KLEo
google-site-verification=gDg2kmpHT3AQ9_Cd5rFD-6kV9jz-DDx3qS-rP3ryDwg
r69e2htbu60csjjvpc4nritj5s
knowbe4-site-verification=8e61546b0e01922553c8cdf4c2a9b3bf
SPF v=spf1 include:spf-a.em.ohio.gov include:spf.workfront.com include:amazonses.com...
MS=ms22042845
k5npql1tt27j4726u9djbhbgtu
google-site-verification=NPnJO9lv02ILiXwQzCSURoeR0rYopN8Pol41Z69dT9k
b1tlbni8a8r1at7plngro4bg2n
apple-domain-verification=um1JOBmUJiuX4Ck3
1apguurmfhlre92ss35l9h0a0o
cisco-ci-domain-verification=6f35a2dcd4356721f5094056fdedd2aca537182f583afb648c9...
nvmstnoakt3rba1dovtrqprpav
dkdc7265e1vb8njsbrvgtc0p48
658mgu7aicn0vn9vgd1q85k4pr
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+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://ohio.gov

https://ohio.gov

510 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ohio.gov200510 msHTTP/1.1nginx
A+
Crawlability
robots.txt present, sitemap with 383 URLs
PASS
robots.txt present, sitemap with 383 URLs
Info::
robots.txt is present
Got: 330 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 383 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 330 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /wps/wcm/connect/gov/ohio+content+english/
Disallow: /wps/wcm/connect/gov/Ohio+Content+English/
Disallow: /wps/wcm/connect/gov/ohio%20content%20english/
Disallow: /wps/wcm/connect/gov/Ohio%20Content%20English/
Disallow: /wps/portal/gov/site/search/
Disallow: /search/
Sitemap: https://ohio.gov/sitemap.xml

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.ohio.gov/
200https://ohio.gov/

Preferred variant: non-www

HTTP → HTTPS

301http://ohio.gov/ https://ohio.gov/

Consistent

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

25 days

August 11, 2026

SSL certificate

183 days

Issued by Amazon

Domain age

28 years, 11 months

Registered October 2, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

18.161.6.57

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 2, 1997 (28 years, 11 months ago)
Expires August 11, 2026 (3 months)
Last Updated August 16, 2025
Name Servers ns5.ohio.gov, ns6.ohio.gov, ns7.ohio.gov, ns8.ohio.gov
DNSSEC Not enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 18.161.6.57
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.5s)

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
CDN & Delivery
AWS CloudFront (Miss from cloudfront)
PASS
AWS CloudFront (Miss from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: HIO52-P1)
Got: x-amz-cf-id: cwrXlR3aIbx395JNGlV5WfQ2sYt7Okwj1Pi7IaqVKYFhzrcuCVVdug==
Info::
CDN cache status: Miss from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status Miss from cloudfront Evidence x-amz-cf-id: cwrXlR3aIbx395JNGlV5WfQ2sYt7Okwj1Pi7IaqVKYFhzrcuCVVdug==
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback