Infrastructure - https://www.henrycountyva.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.

B

DNSSEC

Unsigned (DNSSEC not deployed)

REVIEW

Unsigned (DNSSEC not deployed)

DNSSEC is not deployed

The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).

B

CAA Records

No CAA records (any CA may issue certificates)

REVIEW

No CAA records (any CA may issue certificates)

No CAA records published

Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.

C

Reverse DNS

Action

0/1 IPs match cert SAN

REVIEW

0/1 IPs match cert SAN

PTR lookup failed for 207.38.78.46: lookup 207.38.78.46: no such host

No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

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.henrycountyva.gov/

200https://henrycountyva.gov/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Use 301 (permanent) instead of 302 (temporary)

B

HTTP Probe Timing

Total 917 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

REVIEW

DNS Lookup

35 ms

TCP Connect

129 ms

TLS Handshake

263 ms

Time to First Byte

789 ms

Total Time

918 ms

Connection waterfall

DNS Lookup 35 ms TCP Connect 129 ms TLS Handshake 263 ms Server Processing 363 ms Content Transfer 129 ms

B

TLS Certificate Expiry & Recommendations

84 days until leaf cert expires — 4 issues to address

REVIEW

Certificate validity

84

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

B

CDN Cache Observability

No CDN cache-status headers in the response

REVIEW

No CDN cache-status headers in the response

Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.

B

Operational Status Page

No status page link detected

REVIEW

No status page link detected

No operational status page link detected

Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.

B

Health Check Endpoint

No conventional health endpoint found

REVIEW

No conventional health endpoint found

Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.

A

DNS Records

1 A records, 35 ms lookup

PASS

1 A records, 35 ms lookup

Resolves to 1 IPv4 address(es)

Got: 207.38.78.46

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

No NS records found

No MX records — email not configured via DNS

No SPF record found in TXT records

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

DNS resolution time: 35 ms

Got: 35 ms

A	207.38.78.46
AAAA	—
CNAME	—
NS	—
MX	—
TXT	—
CAA	Lookup not available with standard resolver

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

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

A+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

No CNAME record present

A+

Multi-Resolver DNS Speed

Mean 24ms across 3 resolvers (spread 14ms)

PASS

Mean 24ms across 3 resolvers (spread 14ms)

Cloudflare: 17ms

Got: 17ms via 1.1.1.1:53

Google: 26ms

Got: 26ms via 8.8.8.8:53

Quad9: 31ms

Got: 31ms via 9.9.9.9:53

A+

Redirect Chain

No redirects — direct access

PASS

No redirects — direct access

Got: https://www.henrycountyva.gov

https://www.henrycountyva.gov

735 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://www.henrycountyva.gov	200	735 ms	HTTP/1.1

A+

Crawlability

robots.txt present, sitemap with 257 URLs

PASS

robots.txt present, sitemap with 257 URLs

robots.txt is present

Got: 816 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 257 entries

robots.txt references sitemap

robots.txt 200 OK

Size 816 B Sitemaps referenced 1 User-agents Baiduspider, Yandex, *, Siteimprove, Siteimprovebot, Siteimprovebot-crawler Blocking No — crawling allowed

user-agent: Baiduspider

Disallow: /

User-agent: Yandex

Disallow: /

User-agent: *

Disallow: /activedit

Disallow: /admin

Disallow: /common/admin/

Disallow: /OJA

Disallow: /support

Disallow: /currenteventsview.asp

Disallow: /search.asp

Disallow: /currenteventsview.aspx

Disallow: /search.aspx

Disallow: /currentevents.aspx

Disallow: /Support

Disallow: /CurrentEventsView.asp

Disallow: /Search.asp

Disallow: /CurrentEventsView.aspx

Disallow: /Search.aspx

Disallow: /Search

Disallow: /CurrentEvents.aspx

Disallow: /Currentevents.aspx

Disallow: /map.aspx

Disallow: /map.asp

Disallow: /Map.aspx

Disallow: /Map.asp

Sitemap: /sitemap.xml

Disallow: /RSS.aspx

User-agent: Siteimprove

Crawl-delay: 20
User-agent: Siteimprovebot

Crawl-delay: 20
User-agent: Siteimprovebot-crawler

Crawl-delay: 20

sitemap.xml 200 OK

Type URL Set URLs 257 entries Valid XML Yes

Sample URLs:

A+

Domain Intelligence

henrycountyva.gov — via get.gov, 18 years, 11 months old

PASS

henrycountyva.gov — via get.gov, 18 years, 11 months old

Domain registered until Aug 21, 2027 (1 years remaining)

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.

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.

Domain expiry

369 days

August 21, 2027

SSL certificate

84 days

Issued by Let's Encrypt

Domain age

18 years, 11 months

Registered December 17, 2007

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

ASN AS36489 393775

207.38.78.46

Registrar

get.gov

Unlocked 2 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 December 17, 2007 (18 years, 11 months ago)

Expires August 21, 2027 (1 years)

Last Updated July 27, 2026

Name Servers pdns01.domaincontrol.com, pdns02.domaincontrol.com

DNSSEC Not enabled

Registrant REDACTED FOR PRIVACY

Hosting

IP Address 207.38.78.46

ASN AS36489 393775 ()

Data source: rdap (0.5s)

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