STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

ingles.com

ingles.com's public homepage, certificate and DNS checked against 31 practices and compared with 492 Web Tools sites.

Readiness index
91/100

Web Tools median 67

Ahead of
99%

of measured Web Tools sites

Practices observed
26/30

1 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 11:54:33 UTC from one location. How we measure

Readiness by lane

Green: ingles.com. Thin bar: Web Tools peer median.

Enable

100/100

Peers 84

Harden

85/100

Peers 55

Accelerate

100/100

Peers 69

Recover

0/100

Peers 6

Priority fixes for ingles.com

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

  1. Priority 1 · Harden

    Content Security Policy present

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

    Why it matters: A CSP limits where scripts, styles and frames can load from, which reduces the impact of injected or compromised third-party code.

    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.

    15% of Web Tools peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

  2. Priority 2 · Harden

    CAA records limit who can issue certificates

    Observed: No CAA record was found for ingles.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.

    14% of Web Tools peers do this.

  3. Priority 3 · Harden

    Referrer-Policy set

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

    What to do: Send Referrer-Policy: strict-origin-when-cross-origin unless you have a reason to share more.

    30% of Web Tools peers do this.

  4. Priority 4 · Recover

    Nameservers spread across providers

    Observed: All nameservers for ingles.com belong to Cloudflare.

    What to do: Treat this as an advanced step. Add a secondary DNS provider through zone transfers or a multi-provider setup, then test changes carefully, since both providers must stay in sync.

    On Cloudflare: Cloudflare supports zone transfers for primary or secondary DNS setups on eligible plans.

    6.1% of Web Tools peers do this.

What ingles.com already does well

Practices fewer than half of Web Tools peers use.

  • security.txt publishedsecurity.txt with a contact found.4.8% of peers
  • DNSSEC signedDNSSEC delegation (DS record) present.9.3% of peers
  • DMARC policy enforces quarantine or rejectDMARC policy p=reject.23% of peers

What we saw

Homepage checked
https://www.ingles.com/
Homepage response
HTTP 200
TLS
TLSv1.3, HTTP/2
Certificate
Let's Encrypt, 89-day validity, expiring 2027-01-15
CDN or edge
Cloudflare
DNS operators
Cloudflare
HSTS
max-age 365 days
DMARC policy
p=reject
Homepage HTML
194 KB, br
Images on homepage
45 (svg 53, gif 1, avif 1, webp 1, jpg 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

Observed 26

  • HTTP requests move to HTTPS
  • HSTS kept for at least a year
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • Certificate lifetime of 100 days or less
  • DNSSEC signed
  • security.txt published
  • DMARC policy enforces quarantine or reject
  • X-Content-Type-Options: nosniff
  • Framing restricted
  • HTTP/2 negotiated
  • HTTP/3 advertised
  • HTML compressed
  • Modern image formats in use
  • Offscreen images lazy-loaded
  • No render-blocking scripts in <head>
  • robots.txt published
  • XML sitemap discoverable
  • Reachable over IPv6
  • Canonical URL declared
  • Meta description written
  • Mobile viewport configured
  • Structured data present
  • Social preview image set
  • Page language declared
  • At most one redirect to the homepage

Not measured 1

  • Static files cached for 30 days or more

Own ingles.com?

Re-run the checks after a change, or verify the site in a free workspace to save reports with history, compare against similar sites and competitors, and track a private action plan. What owners get.

Live status for this site: Status Is Down: ingles.com. This profile covers configuration only.

Compare with other Web Tools sites