check-host.net

Readiness by lane

Green: check-host.net. Thin bar: Web Tools peer median.

Priority fixes for check-host.net

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

1. Priority 1 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 2 external scripts without async or defer.

   Why it matters: A plain <script src> in the head stops the browser from showing anything until that file has downloaded and run.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   69% of Web Tools peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

   Guide: Control Third-Party Scripts Before They Control Your Page

2. Priority 2 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 30 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.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Accelerate

   Modern image formats in use

   Observed: The homepage had 27 images and none used WebP or AVIF.

   What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.

   On Cloudflare: Cloudflare Polish can convert images to WebP.

   37% of Web Tools peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

4. Priority 4 · Accelerate

   Offscreen images lazy-loaded

   Observed: The homepage had 27 images and none used loading="lazy".

   What to do: Add loading="lazy" to images below the fold. Do not lazy-load the main hero image, because that delays the largest visible element.

   59% of Web Tools peers do this.

   Guide: Lazy Loading Without Broken Pages

What check-host.net already does well

Practices fewer than half of Web Tools peers use.

• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.23% of peers
• X-Content-Type-Options: nosniffnosniff header present.44% of peers

What we saw

Homepage checked

https://check-host.net/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 90-day validity, expiring 2026-12-03

CDN or edge

Cloudflare

DNS operators

Cloudflare

HSTS

max-age 30 days, preload

DMARC policy

p=quarantine

Homepage HTML

19 KB, br

Images on homepage

27 (svg 14, png 13)

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 Web Tools sites

• 192-168-1-1ip.mobi64
• bahesab.ir64
• downringtone.com64
• gigacalculator.com64
• vclock.com65

Web Tools readiness benchmark