Website readiness profile · Snapshot 23 October 2026
kio.ac
kio.ac's public homepage, certificate and DNS checked against 31 practices and compared with 118 Cloud Storage & File Transfer sites.
- Readiness index
- 87/100
- Ahead of
- 97%
- Practices observed
- 24/29
- Popularity band
- Top 50K
Cloud Storage & File Transfer median 57
of measured Cloud Storage & File Transfer sites
2 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: kio.ac. Thin bar: Cloud Storage & File Transfer peer median.
Enable
100/100
Peers 68
Harden
78/100
Peers 55
Accelerate
87/100
Peers 56
Recover
100/100
Peers 5
Priority fixes for kio.ac
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
Framing restricted
Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.
Why it matters: Without it, another site can load your pages in a hidden frame and trick visitors into clicking buttons (clickjacking).
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.
53% of Cloud Storage & File Transfer peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.
Priority 2 · Accelerate
HTTP/3 advertised
Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.
What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.
On Cloudflare: Enable HTTP/3 (with QUIC) under Speed > Optimization > Protocol Optimization.
44% of Cloud Storage & File Transfer peers do this.
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.
24% of Cloud Storage & File Transfer peers do this.
Guide: Payment Security and PCI DSS: What Website Owners Need to Know
Priority 4 · Harden
security.txt published
Observed: No valid /.well-known/security.txt with a Contact field was returned.
What to do: Publish /.well-known/security.txt with at least Contact and Expires fields, as RFC 9116 requires, and review it before it expires.
On Cloudflare: Cloudflare Security Center can serve a security.txt file for the zone.
5.3% of Cloud Storage & File Transfer peers do this.
What kio.ac already does well
Practices fewer than half of Cloud Storage & File Transfer peers use.
- Nameservers spread across providersNameservers spread across more than one operator.5.1% of peers
- DNSSEC signedDNSSEC delegation (DS record) present.10% of peers
- CAA records limit who can issue certificatesCAA limits issuance to comodoca.com, digicert.com, letsencrypt.org and others.12% of peers
What we saw
- Homepage checked
- https://kio.ac/
- Homepage response
- HTTP 200, after 1 redirect
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Google Trust Services, 90-day validity, expiring 2026-12-05
- CDN or edge
- Cloudflare
- DNS operators
- 3 self-run or other nameserver domains
- HSTS
- max-age 365 days, includeSubDomains, preload
- DMARC policy
- p=reject
- Homepage HTML
- 65 KB, gzip
- 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
Not observed 5
Observed 24
- 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
- CAA records limit who can issue certificates
- DNSSEC signed
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- HTTP/2 negotiated
- HTML compressed
- Static files cached for 30 days or more
- 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
- Nameservers spread across providers
Not measured 2
- Modern image formats in use
- Offscreen images lazy-loaded
Own kio.ac?
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: kio.ac. This profile covers configuration only.