Infrastructure - https://brian.fraval.org BeaverCheck Audit

F

IPv6 Readiness

Action

IPv6 records exist but unreachable

FIX

IPv6 records exist but unreachable

IPv6 DNS records exist but server is not reachable

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Got: 2001:41d0:301::30

IPv6 connection error

Got: dial tcp6 [2001:41d0:301::30]:443: connect: network is unreachable

IPv6 Misconfigured

AAAA Records 2001:41d0:301::30 Connection UNREACHABLE

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Why this matters

Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.

Learn more ▾

Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.

Source: RFC 8305 (Happy Eyeballs)

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

DNSSEC

Action

Zone signed but parent has no DS record

REVIEW

Zone signed but parent has no DS record

DNSSEC keys published but parent zone has no DS record

The zone publishes DNSKEY records but the registry has not been updated with the corresponding DS record. From a validating resolver's perspective the domain is unsigned. Submit the DS record to your registrar to complete the delegation.

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.

B

Reverse DNS

0/2 IPs match cert SAN

REVIEW

0/2 IPs match cert SAN

PTR for 145.239.37.162 does not match any cert SAN: cluster030.hosting.ovh.net

Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.

PTR lookup failed for 2001:41d0:301::30: lookup 2001:41d0:301::30: 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.

B

Crawlability

no robots.txt, no sitemap

REVIEW

no robots.txt, no sitemap

No robots.txt found

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

No sitemap.xml found

A sitemap helps search engines discover and index your pages more efficiently.

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

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

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 No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

C

TLS Certificate Expiry & Recommendations

Action

29 days until leaf cert expires — 4 issues to address

REVIEW

Certificate validity

29

days left

0d 30d 60d 90d+

Renew soon — under 30 days remaining

Recommended actions

Renew certificate — 29 days remaining
Submit your domain to hstspreload.org to be added to the Chrome preload list
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

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, 172 ms lookup

PASS

1 A records, 172 ms lookup

Resolves to 1 IPv4 address(es)

Got: 145.239.37.162

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

Has 1 IPv6 (AAAA) record(s)

Got: 2001:41d0:301::30

CNAME record at zone apex

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Got: fraval.org

3 nameserver(s) configured

Got: ns-93-b.gandi.net, ns-94-a.gandi.net, ns-191-c.gandi.net

2 mail exchanger(s) configured

SPF record present in TXT

DNS resolution time: 172 ms

Got: 172 ms

A	145.239.37.162
AAAA	2001:41d0:301::30
CNAME	fraval.org
NS	ns-93-b.gandi.net, ns-94-a.gandi.net, ns-191-c.gandi.net
MX	10 spool.mail.gandi.net 50 fb.mail.gandi.net
TXT	SPF v=spf1 include:_mailcust.gandi.net ?all
CAA	Lookup not available with standard resolver

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

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

A+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

CNAME does not point at a known takeover-able service

A+

Multi-Resolver DNS Speed

Mean 16ms across 3 resolvers (spread 22ms)

PASS

Mean 16ms across 3 resolvers (spread 22ms)

Cloudflare: 4ms

Got: 4ms via 1.1.1.1:53

Google: 18ms

Got: 18ms via 8.8.8.8:53

Quad9: 26ms

Got: 26ms via 9.9.9.9:53

A+

Redirect Chain

No redirects — direct access

PASS

No redirects — direct access

Got: https://brian.fraval.org

https://brian.fraval.org

610 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://brian.fraval.org	200	610 ms	HTTP/1.1	OVHcloud

A

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

PASS

www/non-www, trailing slash, HTTP→HTTPS

HTTP→HTTPS redirect uses 302 instead of 301

Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

https://www.brian.fraval.org/

200https://brian.fraval.org/

HTTP → HTTPS

302http://brian.fraval.org/ → https://brian.fraval.org/

Use 301 (permanent) instead of 302 (temporary)

A+

Domain Intelligence

fraval.org — via Gandi SAS, 25 years, 11 months old, hosted on OVH

PASS

fraval.org — via Gandi SAS, 25 years, 11 months old, hosted on OVH

Domain registered until Sep 21, 2026 (4 months 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: Gandi SAS

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: OVH

Got: AS16276

Domain expiry

97 days

September 21, 2026

SSL certificate

29 days

Issued by Let's Encrypt

Domain age

25 years, 11 months

Registered September 21, 2000

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

OVH

ASN AS16276

145.239.37.162

Registrar

Gandi SAS

Unlocked 3 NS records

Expiry timeline

Today

+1 year

Domain expiry SSL expiry Danger zone (≤30 days)

Recommended actions

Renew the TLS certificate or verify auto-renewal is working
Enable DNSSEC to protect visitors from DNS spoofing
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar Gandi SAS

Created September 21, 2000 (25 years, 11 months ago)

Expires September 21, 2026 (4 months)

Last Updated September 13, 2025

Name Servers ns-191-c.gandi.net, ns-93-b.gandi.net, ns-94-a.gandi.net

DNSSEC Not enabled

Hosting

IP Address 145.239.37.162

ASN AS16276 (OVH, FR)

Provider OVH

Data source: rdap (0.2s)

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

PASS

DNS Lookup

177 ms

TCP Connect

144 ms

TLS Handshake

148 ms

Time to First Byte

619 ms

Total Time

619 ms

Connection waterfall

DNS Lookup 177 ms TCP Connect 144 ms TLS Handshake 148 ms Server Processing 150 ms Content Transfer 0 ms