tcgmatch.cl

Readiness by lane

Green: tcgmatch.cl. Thin bar: E-Commerce & Marketplaces peer median.

Priority fixes for tcgmatch.cl

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 tcgmatch.cl 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 Next.js: Add it in next.config.js headers().

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

   Guide: A Practical Website Health Check for Owners

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

4. Priority 4 · Accelerate

   HTTP/3 advertised

   Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.

   What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.

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

   Guide: CDN Guide for Website Owners

What tcgmatch.cl already does well

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

• CAA records limit who can issue certificatesCAA limits issuance to letsencrypt.org, pki.goog, sectigo.com.16% of peers
• HSTS kept for at least a yearHSTS with a 730-day max-age.32% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.44% of peers

What we saw

Homepage checked

https://tcgmatch.cl/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2026-12-11

CDN or edge

Vercel

Platform or framework

Next.js

DNS operators

Vercel DNS

HSTS

max-age 730 days

DMARC policy

p=none

Homepage HTML

60 KB, br

Images on homepage

14 (webp 23, png 3, svg 1)

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

• suta.in77
• systembolaget.se77
• taburetka.ua77
• tecsox.com77
• telemart.ua77

E-Commerce & Marketplaces readiness benchmark