Skip to content
https://ct.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
3
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
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.

B
Redirect Chain
1 redirect(s), 1458 ms total
REVIEW
1 redirect(s), 1458 ms total
Info::
Single redirect
Got: https://ct.gov → https://portal.ct.gov (301)
Warning::
Redirect overhead: 1458 ms total
Got: 1458 ms
Info::
Cross-domain redirect detected

https://ct.gov

418 ms · HTTP/1.0

301

https://portal.ct.gov

1040 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ct.gov301418 msHTTP/1.0LB
2https://portal.ct.gov2001040 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

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
317 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

317
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, 534 ms lookup
PASS
1 A records, 534 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 159.247.0.240
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: ns1.cen.ct.gov, ns2.cen.ct.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 (534 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 534 ms
A159.247.0.240
AAAA
CNAME
NSns1.cen.ct.gov, ns2.cen.ct.gov
MX
10 mxa-005c2f01.gslb.pphosted.com
10 mxb-005c2f01.gslb.pphosted.com
TXT
google-site-verification=Z_ikq_dyrSor6GMc9f87n6IihZHej_lZN9iAPPBB9gY
7g5sPZ28I75H+B/ZVxx4t25nY+JU2smsjtlrc0Vc0TOpqtMg1xMIF/6r6HeOse8VfRYakXpfhzxKqoTx...
google-site-verification=h43ZnoS4XQOaXeiamwZXX1LPMCHWwXpafm32q7c-D80
cisco-ci-domain-verification=6dae9307abcadbf2f104396e6aaefbefa546a056ad131e2aad0...
logmein-verification-code=Cik22PhYbROkHlIAzem4PNiRU
twilio-domain-verification=1aff3068aff1ec93abf8242773399ebf
google-site-verification=CgHOAQV1tTMl1HlrIoxEvC8TV1Vce7pX70NUnUcC5DU
nbglpqkwlv6qfsh9m6h3xbw1zs44glmz
hy1qjnhlwcfz2mlzsln1zqstrn92mg7q
onx=208a6c22-ba29-4fed-a369-3502605d0e31
MS=ms883543743600
z40f3klt6my4x9xq153st3tzxtxkrt0n
ms-domain-verification=40325171-c7c7-4c24-9ffd-7220b3b2ae7f
google-site-verification=dqPi8vi1HccsOl63B6PkXFUuRCp6KaRuF9rNhVvLuNo
6515da28-e3b2-4956-b655-9ced73845bcf
apple-domain-verification=nZNBrAgF80pdqTRR
ms-domain-verification=cfe42a4f-6006-4fcc-a13d-940cede592cf
7hv3er340v84rcvs4o2ahhb8fa
atlassian-domain-verification=Sd7SuLqdxLLpCBZ7rT6yhL7I6HDbNnDDDAiSasRL5F5RAIXDsn...
yahoo-verification-key=X7SubEDOTRJzlhlYGYT/k/Uf0oqjOy8WJ68XyRaO/rI=
google-site-verification=3gihAs_bQ9H47M2LkdX4thrJeVSoM19DAX1e9hqkr5U
SPF v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.valigov.email ~all
_9ns7feuq63xrhser15fa64glvrtqg9a
7501E673B77D8777FFF12142F8ECC249026529CF9E7F778C6ED093B33D610688
google-gws-recovery-domain-verification=59718382
rgk69s96rzxk2v7r4w31cnt76t85jjn5
in0h4kmdrti6r7lrp61rfmto7o
dtm-domain-verification=vzF2vklGBZtiYc77WxUcCdX_MeJqSYI5rSlIiWHaDjU
onx=3d60921c-660a-4d55-856e-e3bc213addb9
CAALookup not available with standard resolver
Resolved in 534 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 0 URLs
PASS
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 239 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

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 239 B Sitemaps referenced 0 User-agents Blocking No — crawling allowed

        <html>
        <head>
        <title>Information Page</title>
        </head>
        <body>
            The URL is invalid or the pointer does not exist, Clear browser cache and try again.
        </body>
        </html>
        
sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML Yes
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.ct.gov/
200https://ct.gov/

Preferred variant: non-www

HTTP → HTTPS

301http://ct.gov/ https://portal.ct.gov

Consistent

A+
Domain Intelligence
ct.gov — via get.gov, 25 years, 1 months old, hosted on STOFCT-DOIT - State of Connecticut, US
PASS
ct.gov — via get.gov, 25 years, 1 months old, hosted on STOFCT-DOIT - State of Connecticut, US
Info::
Domain registered until Aug 28, 2026 (4 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: STOFCT-DOIT - State of Connecticut, US
Got: AS3481
Domain expiry

74 days

August 28, 2026

SSL certificate

317 days

Issued by Sectigo Limited

Domain age

25 years, 1 months

Registered July 25, 2001

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

STOFCT-DOIT - State of Connecticut, US

ASN AS3481

159.247.0.240

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 July 25, 2001 (25 years, 1 months ago)
Expires August 28, 2026 (4 months)
Last Updated September 2, 2025
Name Servers ns1.cen.ct.gov, ns2.cen.ct.gov
DNSSEC Not enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 159.247.0.240
ASN AS3481 (STOFCT-DOIT - State of Connecticut, US)
Provider STOFCT-DOIT - State of Connecticut, US
Data source: rdap (0.6s)

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 507 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
101 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.
205 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
508 ms
Total Time Total request time from DNS lookup through full response.
508 ms

Connection waterfall

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