zeeman.com

Readiness by lane

Green: zeeman.com. Thin bar: E-Commerce & Marketplaces peer median.

Priority fixes for zeeman.com

Ordered by impact and by how common each practice is among peers.

1. Priority 1 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for zeeman.com was p=none, which asks receivers to take no action on failing mail.

   Why it matters: An enforcing DMARC policy helps receiving mail systems reject email that falsely claims to come from your domain, a common route for phishing your customers.

   What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.

   39% of E-Commerce & Marketplaces peers do this. Limit: Read from public DNS at the time of the check; records may have changed since.

   Guide: A Practical Website Health Check for Owners

2. Priority 2 · Harden

   Framing restricted

   Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.

   What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.

   On Amazon CloudFront: Set frame options in a response headers policy.

   70% of E-Commerce & Marketplaces peers do this.

   Guide: A Practical Website Health Check for Owners

3. Priority 3 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 1 external script without async or defer.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   On Next.js: Use the next/script component with an appropriate loading strategy.

   44% of E-Commerce & Marketplaces peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

4. Priority 4 · Harden

   Content Security Policy present

   Observed: The homepage response did not include a Content-Security-Policy header.

   What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.

   On Next.js: Next.js documents nonce-based CSP with middleware.

   48% of E-Commerce & Marketplaces peers do this.

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

What zeeman.com already does well

Practices fewer than half of E-Commerce & Marketplaces peers use.

• Referrer-Policy setReferrer-Policy present.20% of peers
• HSTS kept for at least a yearHSTS with a 365-day max-age.32% of peers
• Reachable over IPv6IPv6 address published.40% of peers

What we saw

Homepage checked

https://www.zeeman.com/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

Amazon, 394-day validity, expiring 2027-03-10

CDN or edge

Amazon CloudFront

Platform or framework

Next.js

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 365 days

DMARC policy

p=none

Homepage HTML

486 KB, gzip

Images on homepage

47 (png 342, jpg 38, svg 12)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

Stack and providers

Seen in the homepage response, certificate and DNS. Provider pages compare how their customers configure the same checks.

All 31 checks

Select a gap for the method and fix. How each check works

Compare with other E-Commerce & Marketplaces sites

• 32degrees.com73
• 4fizjo.pl73
• wearfigs.com74
• zalando-lounge.cz74
• zalando-lounge.de74

E-Commerce & Marketplaces readiness benchmark