Skip to content
https://mt.gov

Infrastructure

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

C
URL Variants
Action
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
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.mt.gov/
200https://mt.gov/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://mt.gov/ → https://mt.gov/

Use 301 (permanent) instead of 302 (temporary)

B
HTTP Probe Timing
Total 1279 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
198 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
176 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
534 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.28 s
Total Time Total request time from DNS lookup through full response.
1.28 s

Connection waterfall

DNS Lookup 198 ms TCP Connect 176 ms TLS Handshake 534 ms Server Processing 370 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
46 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

46
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, 516 ms lookup
PASS
1 A records, 516 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 161.7.35.25
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: mtdnspri.mt.gov, mtdnstri.mt.gov, mtdnssec.mt.gov
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
Warning::
DNS resolution is slow (516 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 516 ms
A161.7.35.25
AAAA—
CNAME—
NSmtdnspri.mt.gov, mtdnstri.mt.gov, mtdnssec.mt.gov
MX
10 mxb-003c7b01.gslb.pphosted.com
10 mxa-003c7b01.gslb.pphosted.com
TXT
intersight=2639c13f8866a428279e55dbd43b9d36c0fc44b8c954860f11895a3b938b6d1f
SPF v=spf1 ip4:161.7.5.0/27 ip4:161.7.130.240/28 ip4:161.7.28.23 ip4:161.7.28.21 inc...
dkftrk6tsbq5eujhl3d6vlqufl
MS=ms39950531
vmware-cloud-verification-b95d2959-681f-4bc4-8f16-df7f87b4d24d
formstack-domain-verification=be0f50b2742ec86520a2949d4718230e
adobe-idp-site-verification=dcfdf658-ffe9-4345-8f1d-e37a3ee33e7b
YaAultTuSHeluUHRv3JFOWpdIJjD19RIEuFkVtC9+95yT359ZWgA38pyFX4LGH+mjZwt09w9+G/eTrHR...
dtm-domain-verification=Ny0YibD824TU4a1wcM0q1tU9kulhURBKwjr55Tnqa20
tevpioh34icl235jitf8olfahf
atlassian-domain-verification=miA4TIKOEcHgG9Lsj1V2zcOp/Z5/YrGfoFRNEMgEjGCidSJ6Ml...
remarkable-domain-verification=69ca19e9-8548-4deb-bb5a-32200ca02cc3
apple-domain-verification=YYLsIdpRvDCe43Rn
canva-site-verification=41Ujt_Y62xB9Ba1ZcSzirw
rRNE6z9MmNfEvuRt8h+0wZj9hDy/WQ73Qar7USw5z84gJ7d6ymRQ9jRdccpx3SHkVUOjzzAfix9H3Iol...
CAALookup not available with standard resolver
Resolved in 516 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+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://mt.gov

https://mt.gov

1072 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://mt.gov2001072 msHTTP/1.1
A
Crawlability
no robots.txt, sitemap with 45 URLs
PASS
no robots.txt, sitemap with 45 URLs
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 45 entries

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

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 200 OK
Type URL Set URLs 45 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
mt.gov — via get.gov, 25 years, 1 months old, hosted on MTSTGOV - State of Montana, US
PASS
mt.gov — via get.gov, 25 years, 1 months old, hosted on MTSTGOV - State of Montana, US
Info::
Domain registered until Sep 22, 2026 (5 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: MTSTGOV - State of Montana, US
Got: AS3482
Domain expiry

99 days

September 22, 2026

SSL certificate

46 days

Issued by Sectigo Limited

Domain age

25 years, 1 months

Registered July 30, 2001

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

MTSTGOV - State of Montana, US

ASN AS3482

161.7.35.25

Registrar

get.gov

Unlocked 3 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar get.gov
Created July 30, 2001 (25 years, 1 months ago)
Expires September 22, 2026 (5 months)
Last Updated September 27, 2025
Name Servers mtdnspri.mt.gov, mtdnssec.mt.gov, mtdnstri.mt.gov
DNSSEC Not enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 161.7.35.25
ASN AS3482 (MTSTGOV - State of Montana, US)
Provider MTSTGOV - State of Montana, 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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback