Skip to content
https://nebraska.gov

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
76
GRADE
C
FIX
2
REVIEW
3
PASS
4
INFO
0
Probed from Madrid, Spain
302 Found
Checks
9
4 PASS 3 REVIEW 2 FIX
D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
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
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 302 Expected: 301 redirect to HTTPS

www / non-www

200https://www.nebraska.gov/
200https://nebraska.gov/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://nebraska.gov/ http://www.nebraska.gov/

HTTP version does not redirect to HTTPS

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), 1455 ms total
REVIEW
1 redirect(s), 1455 ms total
Info::
Single redirect
Got: https://nebraska.gov → https://www.nebraska.gov/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://nebraska.gov
Warning::
Redirect overhead: 1455 ms total
Got: 1455 ms

https://nebraska.gov

467 ms · HTTP/1.0

302

https://www.nebraska.gov/

988 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://nebraska.gov302467 msHTTP/1.0BigIP
2https://www.nebraska.gov/200988 msHTTP/1.1Apache

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

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

Certificate validity

170
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, 423 ms lookup
PASS
1 A records, 423 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 206.16.212.82
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: dns1.doc.state.ne.us, dns2.doc.state.ne.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
Warning::
DNS resolution is slow (423 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 423 ms
A206.16.212.82
AAAA
CNAME
NSdns1.doc.state.ne.us, dns2.doc.state.ne.us
MX
0 nebraska-gov.k-v1.mx.microsoft
TXT
adobe-idp-site-verification=ce5c0285c8e095888bcb53049e55e627795913a23696468ebf8f...
twilio-domain-verification=b397f3aee93fe7518ab7c340b750b279
apple-domain-verification=9Dlfvvg9XROmB7OX
apple-domain-verification=yXNq75tildotDSCG
e2ma-verification=dvrgb
webexdomainverification.HDSE=dd72fe58-358d-40b4-8e1a-3326314f5e29
MS=ms70597234
SPF v=spf1 include:spf-a1.nebraska.gov include:spf-b1.nebraska.gov include:spf-c1.ne...
amazonses:W31G6zesV0jOsf8+DLsyux+tY0qSaTBziPbxO/M1zEE=
MS=ms63935092
Pz5vOseO8J27J0ASnfqfd8C_BbOaT1L2BOr2G8tHjWA
ciscocidomainverification=5edd2744c9ab117d648590b27c629583781bf8c97ff02cd662011b...
amazonses:r5aDOpNqrCKxHosL7r7xZEggY6tBfWLNtpzewtRZQUo=
google-site-verification=MWIuYd8IxhT57PU2TJgHxraZGTlqShqRtG6wDgwjk3c
42Ok6Np8rZdvFlF561tFPD63VweeErNyB0vgsHkRvgmH7D0/EhoqrtVnzAcLL48Cx3U22IT83r68bmjV...
Dynatrace-site-verification=51d0a582-4a7b-4e78-911f-42c1590a7e67__l1rl5hn5rkqfo6...
google-site-verification=Pz5vOseO8J27J0ASnfqfd8C_BbOaT1L2BOr2G8tHjWA
atlassian-domain-verification=rU294KDF3EoKPzNH3tyBgPmoGjxqTHiVWHjS9X1aMEFO7K31/H...
CAALookup not available with standard resolver
Resolved in 423 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.

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
Crawlability
robots.txt present, sitemap with 56 URLs
PASS
robots.txt present, sitemap with 56 URLs
Info::
robots.txt is present
Got: 97 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 56 entries
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 97 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: /demo/billtrack/

Disallow: /app-fsp/

Allow: /

Allow: /sitemap.xml



A+
Domain Intelligence
nebraska.gov — via get.gov, 25 years old, hosted on TYLERTECH-NIC1 - Tyler Technologies, Inc., US
PASS
nebraska.gov — via get.gov, 25 years old, hosted on TYLERTECH-NIC1 - Tyler Technologies, Inc., US
Info::
Domain registered until Aug 20, 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: TYLERTECH-NIC1 - Tyler Technologies, Inc., US
Got: AS394572
Domain expiry

68 days

August 20, 2026

SSL certificate

170 days

Issued by DigiCert Inc

Domain age

25 years

Registered August 3, 2001

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

TYLERTECH-NIC1 - Tyler Technologies, Inc., US

ASN AS394572

206.16.212.82

Registrar

get.gov

Unlocked 2 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 August 3, 2001 (25 years ago)
Expires August 20, 2026 (3 months)
Last Updated August 25, 2025
Name Servers dns1.doc.state.ne.us, dns2.doc.state.ne.us
DNSSEC Not enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 206.16.212.82
ASN AS394572 (TYLERTECH-NIC1 - Tyler Technologies, Inc., US)
Provider TYLERTECH-NIC1 - Tyler Technologies, Inc., 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 560 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
151 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
101 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
208 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
561 ms
Total Time Total request time from DNS lookup through full response.
561 ms

Connection waterfall

DNS Lookup 151 ms TCP Connect 101 ms TLS Handshake 208 ms Server Processing 100 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