Infrastructure - https://bavovna.ai BeaverCheck Audit

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 185.214.126.192: lookup 185.214.126.192: Temporary failure in name resolution

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

B

HTTP Probe Timing

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

REVIEW

DNS Lookup

28 ms

TCP Connect

76 ms

TLS Handshake

85 ms

Time to First Byte

690 ms

Total Time

1.17 s

Connection waterfall

DNS Lookup 28 ms TCP Connect 76 ms TLS Handshake 85 ms Server Processing 501 ms Content Transfer 476 ms

B

TLS Certificate Expiry & Recommendations

34 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

34

days left

0d 30d 60d 90d+

Recommended actions

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

C

CDN & Delivery

Action

Assets on Cloudflare (host cdnjs.cloudflare.com, 4 assets); document served directly from origin

REVIEW

Assets on Cloudflare (host cdnjs.cloudflare.com, 4 assets); document served directly from origin

Document not behind existing CDN (Cloudflare serves the assets)

The page's subresources are delivered by Cloudflare (cdnjs.cloudflare.com, 4 assets), but the HTML document itself comes straight from the origin. Routing the document through the CDN already in use is the cheapest latency win available here -- the provider relationship, the certificate and the config already exist. A short edge TTL with stale-while-revalidate suits HTML that changes often; if the response is genuinely per-user, edge TLS termination alone still removes a full round trip from every visitor's first byte.

Got: cf-ray: a3e29fad4c0f7a20-SJC

Assets on Cloudflare: cdnjs.cloudflare.com (assets: 4), cache BYPASS

Got: cf-ray: a3e29fad4c0f7a20-SJC

Assets on Cloudflare: cdn.jsdelivr.net (assets: 3), cache HIT

Got: delegation cdn.jsdelivr.net.cdn.cloudflare.net

Assets on a CDN, document is not: Cloudflare

Document origin not attributed

Asset hosts on a CDN

cdnjs.cloudflare.com — Cloudflare · assets: 4 · Cache Status: BYPASS
cdn.jsdelivr.net — Cloudflare · assets: 3 · Cache Status: HIT

Other asset hosts

www.googletagmanager.com — assets: 4 · Google
fonts.googleapis.com — assets: 2 · below probe threshold
www.google.com — assets: 2 · below probe threshold
www.gstatic.com — assets: 2 · below probe threshold
accounts.google.com — assets: 1 · below probe threshold
googleads.g.doubleclick.net — assets: 1 · below probe threshold
sc.lfeeder.com — assets: 1 · below probe threshold
scripts.clarity.ms — assets: 1 · below probe threshold
snap.licdn.com — assets: 1 · below probe threshold
www.clarity.ms — assets: 1 · below probe threshold

The heavy static files already ride an edge network, but every visitor still waits on the origin for the HTML itself. Routing the document through the same CDN is usually a config change rather than a migration: a short edge TTL with stale-while-revalidate for cacheable HTML, or edge TLS termination alone when the response is per-user.

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: connection error.

A

DNS Records

1 A records, 26 ms lookup

PASS

1 A records, 26 ms lookup

Resolves to 1 IPv4 address(es)

Got: 185.214.126.192

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: carl.ns.cloudflare.com, wren.ns.cloudflare.com

5 mail exchanger(s) configured

No SPF record found in TXT records

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

DNS resolution time: 26 ms

Got: 26 ms

A	185.214.126.192
AAAA	—
CNAME	—
NS	carl.ns.cloudflare.com, wren.ns.cloudflare.com
MX	1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 aspmx3.googlemail.com 10 aspmx2.googlemail.com
TXT	atlassian-domain-verification=kSHSE8Rr9axenkXy5blSGajaUH1PSmADTlIv0SeD282VrIqEYG... google-site-verification=LFkrcfoMjhSXEG9OaF33IAtaWXX0mjeZweuqT5oGjLw google-site-verification=UV17aqtE0akklfOohPotxA5xI0Oypbl9QF4BT1QQKEg
CAA	Lookup not available with standard resolver

Resolved in 26 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 18ms across 3 resolvers (spread 22ms)

PASS

Mean 18ms across 3 resolvers (spread 22ms)

Cloudflare: 5ms

Got: 5ms via 1.1.1.1:53

Google: 22ms

Got: 22ms via 8.8.8.8:53

Quad9: 27ms

Got: 27ms via 9.9.9.9:53

A+

Redirect Chain

No redirects — direct access

PASS

No redirects — direct access

Got: https://bavovna.ai

https://bavovna.ai

617 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://bavovna.ai	200	617 ms	HTTP/1.1	LiteSpeed

A+

Crawlability

robots.txt present, sitemap with 8 URLs

PASS

robots.txt present, sitemap with 8 URLs

robots.txt is present

Got: 168 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 8 entries

Sitemap index with 8 child sitemaps

robots.txt references sitemap

robots.txt 200 OK

Size 168 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed

# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:

Sitemap: https://bavovna.ai/sitemap_index.xml
# ---------------------------
# END YOAST BLOCK

sitemap.xml 200 OK

Type Sitemap Index URLs 8 entries Valid XML Yes

Child Sitemaps:

A+

URL Variants

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

PASS

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

www/non-www redirect configured correctly (preferred: non-www)

HTTP correctly redirects to HTTPS permanently

Got: HTTP 301

www / non-www

301https://www.bavovna.ai/

200https://bavovna.ai/

Preferred variant: non-www

HTTP → HTTPS

301http://bavovna.ai/ → https://bavovna.ai/

Consistent

A+

Domain Intelligence

bavovna.ai — via NameCheap, Inc., 4 years, 1 months old, hosted on Hostinger

PASS

bavovna.ai — via NameCheap, Inc., 4 years, 1 months old, hosted on Hostinger

Domain registered until Aug 23, 2028 (1 years, 11 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: NameCheap, Inc.

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

Got: AS47583

Domain expiry

702 days

August 23, 2028

SSL certificate

34 days

Issued by Let's Encrypt

Domain age

4 years, 1 months

Registered August 23, 2022

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Hostinger

ASN AS47583

185.214.126.192

Registrar

NameCheap, Inc.

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 NameCheap, Inc.

Created August 23, 2022 (4 years, 1 months ago)

Expires August 23, 2028 (1 years, 11 months)

Last Updated August 11, 2026

Name Servers carl.ns.cloudflare.com, wren.ns.cloudflare.com

DNSSEC Not enabled

Registrant Redacted for Privacy Purposes

Hosting

IP Address 185.214.126.192

ASN AS47583 (AS-HOSTINGER - Hostinger International Limited, CY)

Provider Hostinger

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