Infrastructure - https://vermont.gov BeaverCheck Audit

D

CDN & Delivery

Action

No CDN detected

FIX

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

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

Both www and non-www versions serve content

Got: Both variants return 200 Expected: One variant 301-redirects to the other

HTTP→HTTPS redirect uses 302 instead of 301

Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.vermont.gov/

200https://vermont.gov/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://vermont.gov/ → https://www.vermont.gov/

Use 301 (permanent) instead of 302 (temporary)

B

TLS Certificate Expiry & Recommendations

183 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

183

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 OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy

A+

DNS Records

1 A records, 179 ms lookup

PASS

1 A records, 179 ms lookup

Resolves to 1 IPv4 address(es)

Got: 199.107.32.183

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

2 nameserver(s) configured

Got: ns1.f5clouddns.com, ns2.f5clouddns.com

1 mail exchanger(s) configured

CAA records not checked

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

SPF record present in TXT

DNS resolution time: 179 ms

Got: 179 ms

A	199.107.32.183
AAAA	—
CNAME	—
NS	ns1.f5clouddns.com, ns2.f5clouddns.com
MX	10 vermont-gov.mail.protection.outlook.com
TXT	P9wd1pAFUhqx5FAcg60eNwPDQS8AdNw9aRF9P49gIYY= s8nqgr3e3g9r00279t0svmquqe google-site-verification=ckgHE-3N1t3sVfYEmWuVQLN7bKJZrAkTcgImQuhoDQQ MS=ms65455399 wrike-verification=NjI1NzY1ODozMjIwMWI5NzdkZDQ0ZWQ4MzgxMzYyYjYwNzE4ZDBjMmMyNDZjM... google-site-verification=owVp35akPa0awk7ixQ3-mgIGWOAr0iK4QhxAR3MJUNE zrzYGWGwHWYfFZ+RfcE9SoFoHKv2l6ioyRzsHGceIAlmHWtDPhoIB10xmrVGWSeGw99hnjDf0Ksyzj3q... bRzQ+cmsPtUo9agtLg6rfHNzGpgtxCg+fPIsBgQIBHs= 6creq1cm2ssj9275vrn9a6p5eb globalsign-domain-verification=2EA4E5D6B8D85A86DFD870D4D9650E19 docusign=ead83d79-8806-4d6d-855f-3df86633a0c7 docusign=f9857486-48f2-4d99-bc38-2229a93744e7 google-site-verification=I69Wx7YuXh_tp9n0jix5zIUj4DoOriPuiHDAGF6VHgA o0YoMzLbEClFc/A7+dZAeLTLYey1ILxkZtZDYvF7thU= ZzrWnEGJ6y2XBlvIz5uEil0TDTm2j6mhU2faF/s75uY= ssrggort8jcu8h24duudojhond qgubti5ja6rj3nq10feg0l8j19 _globalsign-domain-verification=wFsj4Kc2wD4vVBiqbzT2ls_I-WuE16kNlC_b77gjHy SPF v=spf1 ip4:52.227.25.43 ip4:216.243.148.66 ip4:159.105.0.0/16 ip4:170.222.64.128... vmware-cloud-verification-fe481b46-1bda-41fd-b5e4-db613ab16922 F41A7FC79068DC2DD7F7686BF58887AA173E9B890177777AF71550CD0B4927F3 paloaltonetworks-site-verification=f52d0ab8c7de5692d85cfbe0002d5fb9334be47281443... f2kca52jhj2oiib5q049qu77k 8m93g63b8e366v5gu479kvol51 tedmdhpq7vj085589v9bgg69at google-gws-recovery-domain-verification=58530958 Ox/roeqf9DqWoNlVGAV5D+RdJM2d9bJe14dFsDSLDsI= google-site-verification=ckgHE-3N1t3sVfYEmWuVQLN7bKJZrAkTcglmQuhoDQQ
CAA	Lookup not available with standard resolver

Resolved in 179 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

1 redirect(s), 865 ms total

PASS

1 redirect(s), 865 ms total

Single redirect

Got: https://vermont.gov → https://www.vermont.gov/ (302)

WWW normalization redirect

Uses 302 (temporary) redirect

If permanent, use 301 instead.

Got: https://vermont.gov

Redirect overhead: 865 ms total

Got: 865 ms

https://vermont.gov

505 ms · HTTP/1.0

302

https://www.vermont.gov/

360 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://vermont.gov	302	505 ms	HTTP/1.0	BigIP
2	https://www.vermont.gov/	200	360 ms	HTTP/1.1	nginx

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

A+

Crawlability

robots.txt present, sitemap with 1 URLs

PASS

robots.txt present, sitemap with 1 URLs

robots.txt is present

Got: 3202 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 1 entries

robots.txt does not reference a 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 3202 B Sitemaps referenced 0 User-agents Omgilibot, Diffbot, DuckAssistBot, AI2Bot, Webzio-Extended, ChatGPT-User, Omgili, Timpibot, Claude-Web, GPTBot, anthropic-ai, Bytespider, Kangaroo Bot, cohere-training-data-crawler, YouBot, OAI-SearchBot, Applebot-Extended, PanguBot, ImagesiftBot, PerplexityBot, cohere-ai, *, CCBot, ClaudeBot Blocking No — crawling allowed

#
# robots.txt
#
# This file is to prevent the crawling and indexing of certain parts
# of your site by web crawlers and spiders run by sites like Yahoo!
# and Google. By telling these "robots" where not to go on your site,
# you save bandwidth and server resources.
#
# This file will be ignored unless it is at the root of your host:
# Used:    http://example.com/robots.txt
# Ignored: http://example.com/site/robots.txt
#
# For more information about the robots.txt standard, see:
# http://www.robotstxt.org/robotstxt.html

User-agent: *
# CSS, JS, Images
Allow: /core/*.css$
Allow: /core/*.css?
Allow: /core/*.js$
Allow: /core/*.js?
Allow: /core/*.gif
Allow: /core/*.jpg
Allow: /core/*.jpeg
Allow: /core/*.png
Allow: /core/*.svg
Allow: /profiles/*.css$
Allow: /profiles/*.css?
Allow: /profiles/*.js$
Allow: /profiles/*.js?
Allow: /profiles/*.gif
Allow: /profiles/*.jpg
Allow: /profiles/*.jpeg
Allow: /profiles/*.png
Allow: /profiles/*.svg
# Directories
Disallow: /core/
Disallow: /profiles/

# Files
Disallow: /README.md
Disallow: /composer/Metapackage/README.txt
Disallow: /composer/Plugin/ProjectMessage/README.md
Disallow: /composer/Plugin/Scaffold/README.md
Disallow: /composer/Plugin/VendorHardening/README.txt
Disallow: /composer/Template/README.txt
Disallow: /modules/README.txt
Disallow: /sites/README.txt
Disallow: /themes/README.txt
Disallow: /web.config
# Paths (clean URLs)
Disallow: /admin/
Disallow: /comment/reply/
Disallow: /filter/tips
Disallow: /node/add/
Disallow: /search/
Disallow: /user/register
Disallow: /user/password
Disallow: /user/login
Disallow: /user/logout
Disallow: /media/oembed
Disallow: /*/media/oembed
Disallow: /calendar/*
Disallow: /*/calendar/*
Disallow: /calendar-field_event_date/*
Disallow: /*/calendar-field_event_date/*
Disallow: /calendar_field_event_date/*
Disallow: /*/calendar_field_event_date/*
Disallow: /calendar-field_date/*
Disallow: /*/calendar-field_date/*
Disallow: /documents/*
Disallow: /*/documents/*
# Paths (no clean URLs)
Disallow: /index.php/admin/
Disallow: /index.php/comment/reply/
Disallow: /index.php/filter/tips
Disallow: /index.php/node/add/
Disallow: /index.php/search/
Disallow: /index.php/user/password
Disallow: /index.php/user/register
Disallow: /index.php/user/login
Disallow: /index.php/user/logout
Disallow: /index.php/media/oembed
Disallow: /index.php/*/media/oembed

# Bots
User-agent: CCBot
Disallow: /

User-agent: ChatGPT-User
Disallow: /

User-agent: GPTBot
Disallow: /

User-agent: Applebot-Extended
Disallow: /

User-agent: anthropic-ai
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: Omgilibot
Disallow: /

User-agent: Omgili
Disallow: /

User-agent: Diffbot
Disallow: /

User-agent: DuckAssistBot
Disallow: /

User-agent: AI2Bot
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: Kangaroo Bot
Disallow: /

User-agent: PanguBot
Disallow: /

User-agent: ImagesiftBot
Disallow: /

User-agent: PerplexityBot
Disallow: /

User-agent: cohere-ai
Disallow: /

User-agent: cohere-training-data-crawler
Disallow: /

User-agent: Timpibot
Disallow: /

User-agent: Webzio-Extended
Disallow: /

User-agent: YouBot
Disallow: /

User-agent: OAI-SearchBot
Disallow: /

User-agent: Claude-Web
Disallow: /

sitemap.xml 200 OK

Type URL Set URLs 1 entries Valid XML Yes

Sample URLs:

https://www.vermont.gov/

A+

Domain Intelligence

vermont.gov — via get.gov, 25 years, 1 months old, hosted on TYLERTECH-NIC1 - Tyler Technologies, Inc., US

PASS

vermont.gov — via get.gov, 25 years, 1 months old, hosted on TYLERTECH-NIC1 - Tyler Technologies, Inc., US

Domain registered until Aug 11, 2026 (3 months remaining)

DNSSEC is enabled

Registrar: get.gov

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.

Hosting: TYLERTECH-NIC1 - Tyler Technologies, Inc., US

Got: AS394572

Domain expiry

25 days

August 11, 2026

SSL certificate

183 days

Issued by GlobalSign nv-sa

Domain age

25 years, 1 months

Registered July 30, 2001

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

TYLERTECH-NIC1 - Tyler Technologies, Inc., US

ASN AS394572

199.107.32.183

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 registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar get.gov

Created July 30, 2001 (25 years, 1 months ago)

Expires August 11, 2026 (3 months)

Last Updated August 16, 2025

Name Servers ns1.f5clouddns.com, ns2.f5clouddns.com

DNSSEC Enabled

Registrant REDACTED FOR PRIVACY

Hosting

IP Address 199.107.32.183

ASN AS394572 (TYLERTECH-NIC1 - Tyler Technologies, Inc., US)

Provider TYLERTECH-NIC1 - Tyler Technologies, Inc., US

Data source: rdap (0.5s)

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 575 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

PASS

DNS Lookup

46 ms

TCP Connect

105 ms

TLS Handshake

318 ms

Time to First Byte

575 ms

Total Time

576 ms

Connection waterfall

DNS Lookup 46 ms TCP Connect 105 ms TLS Handshake 318 ms Server Processing 106 ms Content Transfer 0 ms