recetasnestle.com.mx

Readiness by lane

Green: recetasnestle.com.mx. Thin bar: Literary & Knowledge peer median.

Priority fixes for recetasnestle.com.mx

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

1. Priority 1 · Accelerate

   HTTP/3 advertised

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

   Why it matters: HTTP/3 runs over QUIC, which copes better with lossy mobile networks and recovers faster when a connection changes.

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

   47% of Literary & Knowledge peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: CDN Guide for Website Owners

2. Priority 2 · Harden

   CAA records limit who can issue certificates

   Observed: No CAA record was found for recetasnestle.com.mx, 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.

   13% of Literary & Knowledge peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Harden

   security.txt published

   Observed: No valid /.well-known/security.txt with a Contact field was returned.

   What to do: Publish /.well-known/security.txt with at least Contact and Expires fields, as RFC 9116 requires, and review it before it expires.

   5% of Literary & Knowledge peers do this.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · Harden

   DNSSEC signed

   Observed: No DS record was found for recetasnestle.com.mx at its parent zone, so its DNS answers are not DNSSEC-signed.

   What to do: Enable DNSSEC at your DNS provider, then add the DS record at your registrar. Plan provider moves carefully: a stale DS record can make the domain fail to resolve.

   5.7% of Literary & Knowledge peers do this.

   Guide: Website Uptime Readiness: Prepare Before Traffic Arrives

What recetasnestle.com.mx already does well

Practices fewer than half of Literary & Knowledge peers use.

• Content Security Policy presentContent-Security-Policy present.18% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=reject.22% of peers
• HSTS kept for at least a yearHSTS with a 365-day max-age covering subdomains.28% of peers

What we saw

Homepage checked

https://www.recetasnestle.com.mx/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2027-01-11

CDN or edge

Fastly, Pantheon

Platform or framework

Drupal

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 365 days, includeSubDomains, preload

DMARC policy

p=reject

Homepage HTML

416 KB, gzip

Images on homepage

146 (webp 328, png 76, jpg 19, svg 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 Literary & Knowledge sites

• a-z-animals.com86
• azorafly.com86
• fischipedia.org88
• mangadex.org88
• worldhistory.org90

Literary & Knowledge readiness benchmark