STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

blockaway.net

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

Readiness index
58/100

Web Tools median 67

Ahead of
20%

of measured Web Tools sites

Practices observed
14/27

4 of 31 could not be measured

Popularity band
Top 5K

Chrome UX Report top-sites list

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

Readiness by lane

Green: blockaway.net. Thin bar: Web Tools peer median.

Enable

56/100

Peers 84

Harden

45/100

Peers 55

Accelerate

100/100

Peers 69

Recover

0/100

Peers 6

Priority fixes for blockaway.net

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

  1. Priority 1 · Harden

    TLS 1.3 negotiated

    Observed: The TLS connection negotiated TLSv1.2.

    Why it matters: TLS 1.3 removes legacy cipher suites and completes the handshake in fewer round trips, so it is both safer and faster for new connections.

    What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.

    On Cloudflare: Turn on TLS 1.3 under SSL/TLS > Edge Certificates.

    92% of Web Tools peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

  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 183 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 blockaway.net already does well

Practices fewer than half of Web Tools peers use.

  • Content Security Policy presentContent-Security-Policy present.15% of peers
  • X-Content-Type-Options: nosniffnosniff header present.44% of peers

What we saw

Homepage checked
https://www.blockaway.net/
Homepage response
HTTP 200
TLS
TLSv1.2, HTTP/2
Certificate
Google Trust Services, 90-day validity, expiring 2027-01-03
CDN or edge
Cloudflare
DNS operators
Cloudflare
HSTS
max-age 183 days, includeSubDomains
Homepage HTML
321 KB, br
Images on homepage
1 (png 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 14

  • HTTP requests move to HTTPS
  • Certificate has more than 14 days left
  • Certificate lifetime of 100 days or less
  • X-Content-Type-Options: nosniff
  • Content Security Policy present
  • HTTP/2 negotiated
  • HTTP/3 advertised
  • HTML compressed
  • No render-blocking scripts in <head>
  • Reachable over IPv6
  • Meta description written
  • Mobile viewport configured
  • Page language declared
  • At most one redirect to the homepage

Not measured 4

  • Static files cached for 30 days or more
  • Modern image formats in use
  • Offscreen images lazy-loaded
  • robots.txt published

Own blockaway.net?

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: blockaway.net. This profile covers configuration only.

Compare with other Web Tools sites