STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

msha.ke

msha.ke's public homepage, certificate and DNS checked against 31 practices and compared with 38 Website Builders sites.

Readiness index
86/100

Website Builders median 64

Ahead of
92%

of measured Website Builders sites

Practices observed
24/30

1 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 12:21:00 UTC from one location. How we measure

Readiness by lane

Green: msha.ke. Thin bar: Website Builders peer median.

Enable

95/100

Peers 81

Harden

77/100

Peers 58

Accelerate

100/100

Peers 63

Recover

0/100

Peers 5

Priority fixes for msha.ke

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

  1. Priority 1 · Harden

    Content Security Policy present

    Observed: The homepage response did not include a Content-Security-Policy header.

    Why it matters: A CSP limits where scripts, styles and frames can load from, which reduces the impact of injected or compromised third-party code.

    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.

    26% of Website Builders peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

  2. Priority 2 · 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.

    16% of Website Builders peers do this.

  3. Priority 3 · Harden

    CAA records limit who can issue certificates

    Observed: No CAA record was found for msha.ke, 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 Website Builders peers do this.

  4. Priority 4 · Harden

    DNSSEC signed

    Observed: No DS record was found for msha.ke at its parent zone, so its DNS answers are not DNSSEC-signed.

    What to do: Enable DNSSEC at your DNS provider, then add the DS record at your registrar. Plan provider moves carefully: a stale DS record can make the domain fail to resolve.

    On Cloudflare: Enable DNSSEC in DNS > Settings and add the DS record at the registrar.

    7.9% of Website Builders peers do this.

What msha.ke already does well

Practices fewer than half of Website Builders peers use.

  • HSTS kept for at least a yearHSTS with a 365-day max-age.26% of peers
  • HTTP/3 advertisedHTTP/3 advertised.29% of peers
  • Referrer-Policy setReferrer-Policy present.29% of peers

What we saw

Homepage checked
https://msha.ke/
Homepage response
HTTP 200, after 1 redirect
TLS
TLSv1.3, HTTP/2
Certificate
Google Trust Services, 90-day validity, expiring 2026-12-08
CDN or edge
Cloudflare
Platform or framework
Astro
DNS operators
Cloudflare
HSTS
max-age 365 days
DMARC policy
p=reject
Homepage HTML
501 KB, br
Images on homepage
418 (webp 412, svg 6)

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 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
  • DMARC policy enforces quarantine or reject
  • X-Content-Type-Options: nosniff
  • Framing restricted
  • Referrer-Policy set
  • 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

Not measured 1

  • Static files cached for 30 days or more

Own msha.ke?

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: msha.ke. This profile covers configuration only.

Compare with other Website Builders sites