Skip to content
https://flsenate.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
5
PASS
3
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
3 PASS 5 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: 32 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 32 B Sitemaps referenced 0 User-agents Blocking No — crawling allowed
User-agent: *
crawl-delay: 1
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Use 301 (permanent) instead of 302 (temporary)

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

Connection waterfall

DNS Lookup 146 ms TCP Connect 126 ms TLS Handshake 390 ms Server Processing 474 ms Content Transfer 379 ms
B
TLS Certificate Expiry & Recommendations
227 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

227
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, 158 ms lookup
PASS
1 A records, 158 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 207.126.31.19
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: ns2.mfn2.myflorida.com, ns3.mfn2.myflorida.com, ns1.mfn2.myflorida.com
Info::
4 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: 158 ms
Got: 158 ms
A207.126.31.19
AAAA—
CNAME—
NSns2.mfn2.myflorida.com, ns3.mfn2.myflorida.com, ns1.mfn2.myflorida.com
MX
5 smtpa.leg.state.fl.us
5 smtpb.leg.state.fl.us
50 cluster1.us.messagelabs.com
60 clusterla.us.messagelabs.com
TXT
6D5A1C084152D3AA2B2E3994F066037C34AA3C3292A1FF8248709880E6D45C40
xsz0ok7GC5NlnsCL/QcKeXcZdYonLg31+KzzZMzNWEPnjhM3KYEAY+4qfWhR6TAJb0IpcU5cfvN3b6b4...
MS=ms62027184
SPF v=spf1 a:smtpa.leg.state.fl.us a:smtpb.leg.state.fl.us a:webmail.flsenate.gov ip...
+XKlkFQXTUzssaNYPAMXFhoBUCe+iMhdDXtw3860HnFBKmxg385QVGpMwc3pQlRPnVuS6dkZZeNZu/A3...
google-site-verification=TWthQvL-qwkb4hDlzj5h0AWe-xOaQDwTp_eL3Kqmt1Y
CAALookup not available with standard resolver
Resolved in 158 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://flsenate.gov

https://flsenate.gov

1248 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://flsenate.gov2001248 msHTTP/1.1Microsoft-IIS/10.0
A+
Domain Intelligence
flsenate.gov — via get.gov, 23 years, 9 months old, hosted on STATE-OF-FLA - Florida Department of Management Services - Division of Telecommunications, US
PASS
flsenate.gov — via get.gov, 23 years, 9 months old, hosted on STATE-OF-FLA - Florida Department of Management Services - Division of Telecommunications, US
Info::
Domain registered until Oct 7, 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: STATE-OF-FLA - Florida Department of Management Services - Division of Telecommunications, US
Got: AS8103
Domain expiry

116 days

October 7, 2026

SSL certificate

227 days

Issued by DigiCert Inc

Domain age

23 years, 9 months

Registered October 30, 2002

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

STATE-OF-FLA - Florida Department of Management Services - Division of Telecommunications, US

ASN AS8103

207.126.31.19

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 October 30, 2002 (23 years, 9 months ago)
Expires October 7, 2026 (5 months)
Last Updated October 12, 2025
Name Servers ns1.mfn2.myflorida.com, ns2.mfn2.myflorida.com, ns3.mfn2.myflorida.com
DNSSEC Not enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 207.126.31.19
ASN AS8103 (STATE-OF-FLA - Florida Department of Management Services - Division of Telecommunications, US)
Provider STATE-OF-FLA - Florida Department of Management Services - Division of Telecommunications, 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

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

Send Feedback