tozlu.com

Readiness by lane

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

Priority fixes for tozlu.com

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.

   What to do: Send Strict-Transport-Security on HTTPS responses. Start with a short max-age (for example 300 seconds), confirm every subdomain works over HTTPS, then raise it in steps to 31536000. Add includeSubDomains only when all subdomains are HTTPS. HSTS preload is optional and hard to undo; hstspreload.org itself does not recommend it by default.

   On Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.

   32% of E-Commerce & Marketplaces peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · 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.

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

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

3. Priority 3 · Enable

   Structured data present

   Observed: The homepage had no JSON-LD structured data.

   What to do: Add JSON-LD for your organization and main content types, then test it with Google's Rich Results Test.

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

   Guide: Structured Data Basics for Website Owners

4. Priority 4 · Harden

   CAA records limit who can issue certificates

   Observed: No CAA record was found for tozlu.com, so any public certificate authority may issue for it.

   What to do: Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.

   On Cloudflare: Cloudflare documents which CAs its managed certificates need; include them in your CAA records.

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

   Guide: HTTPS and TLS Guide for Website Owners

What tozlu.com already does well

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

• Referrer-Policy setReferrer-Policy present.20% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=reject.39% of peers
• Reachable over IPv6IPv6 address published.40% of peers

What we saw

Homepage checked

https://www.tozlu.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 90-day validity, expiring 2027-01-10

CDN or edge

Cloudflare

DNS operators

Cloudflare

DMARC policy

p=reject

Homepage HTML

773 KB, br

Images on homepage

518 (png 231, webp 115, svg 28, jpg 5)

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

• theindusvalley.in82
• tonies.com82
• toolstation.com82
• vitapur.hr82
• xcite.com82

E-Commerce & Marketplaces readiness benchmark