Infrastructure - https://www.eemeli.ee BeaverCheck Audit

D

CDN & Delivery

Action

No CDN (document or assets)

FIX

No CDN (document or assets)

Neither the HTML document nor the page's subresources are served through an edge network. A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.

No CDN (document or assets)

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.

B

Reverse DNS

0/1 IPs match cert SAN

REVIEW

0/1 IPs match cert SAN

PTR for 217.146.69.52 does not match any cert SAN: sn-69-52.tll07.zoneas.eu

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.

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

URL Variants

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 correctly redirects to HTTPS permanently

Got: HTTP 301

www / non-www

200https://www.eemeli.ee/

200https://eemeli.ee/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://www.eemeli.ee/ → https://www.eemeli.ee/

Consistent

B

TLS Certificate Expiry & Recommendations

44 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

44

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

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

PASS

1 A records, 39 ms lookup

Resolves to 1 IPv4 address(es)

Got: 217.146.69.52

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

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: eemeli.ee

3 nameserver(s) configured

Got: ns2.zone.ee, ns3.zonedata.net, ns.zone.eu

1 mail exchanger(s) configured

SPF record present in TXT

DNS resolution time: 39 ms

Got: 39 ms

A	217.146.69.52
AAAA	—
CNAME	eemeli.ee
NS	ns2.zone.ee, ns3.zonedata.net, ns.zone.eu
MX	10 zonemx.eu
TXT	SPF v=spf1 a mx include:_spf.zone.eu include:_spf.smaily.com -all
CAA	Lookup not available with standard resolver

Resolved in 39 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 23ms across 3 resolvers (spread 49ms)

PASS

Mean 23ms across 3 resolvers (spread 49ms)

Quad9: 1ms

Got: 1ms via 9.9.9.9:53

Google: 20ms

Got: 20ms via 8.8.8.8:53

Cloudflare: 50ms

Got: 50ms via 1.1.1.1:53

A

Redirect Chain

1 redirect(s), 459 ms total

PASS

1 redirect(s), 459 ms total

Single redirect

Got: https://www.eemeli.ee → https://eemeli.ee/ (301)

WWW normalization redirect

https://www.eemeli.ee

199 ms · HTTP/1.1

301

https://eemeli.ee/

260 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://www.eemeli.ee	301	199 ms	HTTP/1.1	Apache / ZoneOS
2	https://eemeli.ee/	200	260 ms	HTTP/1.1	Apache / ZoneOS

See the visual redirect chain in the HTTP Probe tab →

A+

Crawlability

robots.txt present, sitemap with 6 URLs

PASS

robots.txt present, sitemap with 6 URLs

robots.txt is present

Got: 1610 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 6 entries

Sitemap index with 6 child sitemaps

robots.txt references sitemap

robots.txt 200 OK

Size 1610 B Sitemaps referenced 1 User-agents dotbot/1.0, Gigabot, PerplexityBot, Bytespider, GPTBot, MJ12bot, ClaudeBot, SemrushBot, *, TikTokSpider, Baiduspider, CazoodleBot, Claude-Web, anthropic-ai, Amazonbot, AhrefsBot, DotBot Blocking No — crawling allowed

# Production robots.txt for eemeli.ee (staging keeps Disallow: / in robots.txt).
# Deploy: cp public/robots.txt.production eemeli-web/public/robots.txt
# rollback: restore from backup. Tag before-robots-extend.

User-agent: *

Sitemap: https://eemeli.ee/sitemap-index.xml

Disallow: /et/cart
Disallow: /en/cart
Disallow: /ru/cart
Disallow: /et/checkout
Disallow: /en/checkout
Disallow: /ru/checkout
Disallow: /et/account
Disallow: /en/account
Disallow: /ru/account
Disallow: /et/paymentlink
Disallow: /en/paymentlink
Disallow: /ru/paymentlink
Disallow: /et/sr/
Disallow: /en/sr/
Disallow: /ru/sr/
Disallow: /*?*min_price=
Disallow: /*?*max_price=
Disallow: /*?*manufacturer=
Disallow: /*?*stock_status=
Disallow: /*?*stock_supplier=
Disallow: /*?*in_stock=
Disallow: /*?*sort=
Disallow: /*?*product_category=

# Crawl-delay/Request-rate removed 2026-10-20 (Google ignores them; Bing/Yandex crawled ~100k products at 1 page / 5 s). rollback: git checkout before-google-fixes -- public/robots.txt.production

User-agent: CazoodleBot
Disallow: /

User-agent: MJ12bot
Disallow: /

User-agent: dotbot/1.0
Disallow: /

User-agent: Gigabot
Disallow: /

# 2026-10-25: AI/SEO crawlers that only generate image cache load (Google, Bing, Apple, Yandex, Meta stay allowed). rollback: ~/backups/imgcache-fix-live-20261025-2325/restore.sh
User-agent: ClaudeBot
User-agent: Claude-Web
User-agent: anthropic-ai
User-agent: PerplexityBot
User-agent: Amazonbot
User-agent: Bytespider
User-agent: TikTokSpider
User-agent: AhrefsBot
User-agent: SemrushBot
User-agent: DotBot
User-agent: Baiduspider
User-agent: GPTBot
Disallow: /

sitemap.xml 200 OK

Type Sitemap Index URLs 6 entries Valid XML Yes

Child Sitemaps:

A

Domain Intelligence

eemeli.ee — via Zone Media OÜ, hosted on ZONE Zone Media OU, EE

PASS

eemeli.ee — via Zone Media OÜ, hosted on ZONE Zone Media OU, EE

Domain expires in 56 days

Consider enabling auto-renewal to prevent accidental expiration.

Got: Expires Dec 24, 2026

Registrar: Zone Media OÜ

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: ZONE Zone Media OU, EE

Got: AS49604

Domain expiry

45 days

December 24, 2026

SSL certificate

44 days

Issued by Let's Encrypt

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

ZONE Zone Media OU, EE

ASN AS49604

217.146.69.52

Registrar

Zone Media OÜ

Unlocked 3 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 Zone Media OÜ

Expires December 24, 2026 (1 months)

Name Servers ns2.zone.ee, ns3.zonedata.net, ns.zone.eu

Hosting

IP Address 217.146.69.52

ASN AS49604 (ZONE Zone Media OU, EE)

Provider ZONE Zone Media OU, EE

Data source: whois (1.0s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

PASS

DNS Lookup

107 ms

TCP Connect

63 ms

TLS Handshake

67 ms

Time to First Byte

300 ms

Total Time

300 ms

Connection waterfall

DNS Lookup 107 ms TCP Connect 63 ms TLS Handshake 67 ms Server Processing 64 ms Content Transfer 0 ms