STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

shopify.com

shopify.com's public homepage, certificate and DNS checked against 31 practices and compared with 5,718 E-Commerce & Marketplaces sites.

Readiness index
81/100

E-Commerce & Marketplaces median 71

Ahead of
88%

of measured E-Commerce & Marketplaces sites

Practices observed
23/30

1 of 31 could not be measured

Popularity band
Top 1K

Chrome UX Report top-sites list

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

Readiness by lane

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

Enable

95/100

Peers 86

Harden

63/100

Peers 60

Accelerate

100/100

Peers 69

Recover

100/100

Peers 11

Priority fixes for shopify.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: Strict-Transport-Security was sent with a max-age of 180 days, below the one-year benchmark.

    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.

  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 Cloudflare: Add the header with a response header transform rule.

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

  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 Shopify: this setting is largely controlled by the platform. Check the platform's settings and documentation, or ask its support team whether it can be changed for your domain.

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

  4. Priority 4 · Harden

    CAA records limit who can issue certificates

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

What shopify.com already does well

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

  • security.txt publishedsecurity.txt with a contact found.7.6% of peers
  • Nameservers spread across providersNameservers spread across more than one operator.11% of peers
  • DMARC policy enforces quarantine or rejectDMARC policy p=reject.39% of peers

What we saw

Homepage checked
https://shopify.com/
Homepage response
HTTP 200, after 1 redirect
TLS
TLSv1.3, HTTP/2
Certificate
Google Trust Services, 90-day validity, expiring 2027-01-06
CDN or edge
Cloudflare
Platform or framework
Shopify
DNS operators
3 self-run or other nameserver domains
HSTS
max-age 180 days, includeSubDomains, preload
DMARC policy
p=reject
Homepage HTML
658 KB, br
Images on homepage
56 (jpg 111, png 48, webp 16, svg 11)

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 23

  • HTTP requests move to HTTPS
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • Certificate lifetime of 100 days or less
  • security.txt published
  • DMARC policy enforces quarantine or reject
  • X-Content-Type-Options: nosniff
  • 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
  • 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
  • Nameservers spread across providers

Not measured 1

  • Static files cached for 30 days or more

Own shopify.com?

Re-run the checks after a change, keep a private action plan in a free workspace, or report a mistake.

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

Compare with other E-Commerce & Marketplaces sites