Skip to content
https://mn.gov

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
302 Found
Checks
9
5 PASS 3 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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 524 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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

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 524 B Sitemaps referenced 0 User-agents *, Ultraseek, VSE/1.0 Blocking No — crawling allowed
# Disallow everything until we want to expose the site to external search
# engines.
# 0000-1200 GMT is 6PM to 6AM here
# 4/14/14 Updated for DataExplorer to crawl all state sites.

User-agent: *
Disallow: /cgi-bin
Disallow: /cgi-sys
Disallow: /cd_upload/Search
Disallow: /law-library-stat/archive/
Disallow: /law-library-stat/briefs/
Visit-time: 0000-1200
Request-rate: 10

User-agent: Ultraseek
Disallow: /cgi-bin
Disallow: /cgi-sys
Disallow: /cd_upload/Search

User-agent: VSE/1.0
Disallow: /cgi-bin
Disallow: /cgi-sys



sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

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

Recommended actions

  • 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
1 A records, 125 ms lookup
PASS
1 A records, 125 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 66.225.237.206
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ns3.state.mn.us, ns2.state.mn.us, ns1.state.mn.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: 125 ms
Got: 125 ms
A66.225.237.206
AAAA
CNAME
NSns3.state.mn.us, ns2.state.mn.us, ns1.state.mn.us
MX
0 state-mn-us.mail.protection.outlook.com
10 mn365.mail.protection.outlook.com
TXT
facebook-domain-verification=0gpzo34l7gvdtz4j6thk47fbmjfpxs
SPF v=spf1 include:spf.protection.outlook.com ip4:151.111.174.40/30 ip4:151.111.145....
google-site-verification=YSZiyt0oJNs7rgOx3uQLI3AgmHIYWr1aeMHEB6oMUMg
cisco-ci-domain-verification=18272bbdcb6d1bb8938ea4f34ffa41f40fcad47d684bf90d7fb...
CAALookup not available with standard resolver
Resolved in 125 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://mn.gov

https://mn.gov

584 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://mn.gov200584 msHTTP/1.1rdwr
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)
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

302https://www.mn.gov/
200https://mn.gov/

Preferred variant: non-www

HTTP → HTTPS

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

Use 301 (permanent) instead of 302 (temporary)

A+
Domain Intelligence
mn.gov — via get.gov, 20 years, 11 months old, hosted on RADWARE-CLOUD-SERVICES - RADWARE INC., US
PASS
mn.gov — via get.gov, 20 years, 11 months old, hosted on RADWARE-CLOUD-SERVICES - RADWARE INC., US
Info::
Domain registered until Aug 11, 2026 (3 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: RADWARE-CLOUD-SERVICES - RADWARE INC., US
Got: AS25773
Domain expiry

59 days

August 11, 2026

SSL certificate

172 days

Issued by Sectigo Limited

Domain age

20 years, 11 months

Registered September 8, 2005

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

RADWARE-CLOUD-SERVICES - RADWARE INC., US

ASN AS25773

66.225.237.206

Registrar

get.gov

Unlocked 3 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 September 8, 2005 (20 years, 11 months ago)
Expires August 11, 2026 (3 months)
Last Updated December 16, 2025
Name Servers ns1.state.mn.us, ns2.state.mn.us, ns3.state.mn.us
DNSSEC Enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 66.225.237.206
ASN AS25773 (RADWARE-CLOUD-SERVICES - RADWARE INC., US)
Provider RADWARE-CLOUD-SERVICES - RADWARE INC., US
Data source: rdap (0.6s)

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

Connection waterfall

DNS Lookup 126 ms TCP Connect 137 ms TLS Handshake 142 ms Server Processing 265 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