STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

qrfy.com

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

Readiness index
69/100

Web Tools median 67

Ahead of
58%

of measured Web Tools sites

Practices observed
20/29

2 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 12:13:51 UTC from one location. How we measure

Readiness by lane

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

Enable

77/100

Peers 84

Harden

68/100

Peers 55

Accelerate

67/100

Peers 69

Recover

0/100

Peers 6

Priority fixes for qrfy.com

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

  1. Priority 1 · Accelerate

    Static files cached for 30 days or more

    Observed: A same-site stylesheet or script was cacheable for no max-age, short of the 30-day benchmark.

    Why it matters: Returning visitors and later page views reuse cached files instead of downloading them again.

    What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.

    On Cloudflare: Use Cache Rules to set edge and browser TTLs for static file paths.

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

  2. Priority 2 · Enable

    XML sitemap discoverable

    Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

    What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.

    73% of Web Tools peers do this.

  3. Priority 3 · Harden

    HSTS kept for at least a year

    Observed: Strict-Transport-Security was sent with a max-age of 0 days, below the one-year benchmark.

    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.

    30% of Web Tools peers do this.

  4. Priority 4 · Enable

    Canonical URL declared

    Observed: The homepage did not declare a canonical URL.

    What to do: Add a self-referencing canonical link to every indexable page, using the final https:// URL.

    74% of Web Tools peers do this.

What qrfy.com already does well

Practices fewer than half of Web Tools peers use.

  • DNSSEC signedDNSSEC delegation (DS record) present.9.3% of peers
  • CAA records limit who can issue certificatesCAA limits issuance to comodoca.com, digicert.com, letsencrypt.org and others.14% of peers
  • Referrer-Policy setReferrer-Policy present.30% of peers

What we saw

Homepage checked
https://qrfy.com/
Homepage response
HTTP 200
TLS
TLSv1.3, HTTP/2
Certificate
Google Trust Services, 90-day validity, expiring 2026-11-27
CDN or edge
Cloudflare
DNS operators
Cloudflare
HSTS
max-age 0 days
DMARC policy
p=none
Homepage HTML
8 KB, br
Images on homepage
0

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 20

  • HTTP requests move to HTTPS
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • Certificate lifetime of 100 days or less
  • CAA records limit who can issue certificates
  • DNSSEC signed
  • X-Content-Type-Options: nosniff
  • Framing restricted
  • Referrer-Policy set
  • HTTP/2 negotiated
  • HTML compressed
  • No render-blocking scripts in <head>
  • robots.txt published
  • Reachable over IPv6
  • 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 2

  • Modern image formats in use
  • Offscreen images lazy-loaded

Own qrfy.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: qrfy.com. This profile covers configuration only.

Compare with other Web Tools sites