Website health check

Know your website.
Improve what matters.

Free website audit tool for security headers, technical SEO and a page resource sample. See evidence, limitations and practical fixes.

No plugins · No registration · Clear limits

Free checks for public websites. Active checks require domain verification.

Authorize my domain for active checks

Generate a code and publish that exact text at /.well-known/siteauditcheck.txt on the final domain. Keep the code for later audits. Remove the file to revoke authorization. This public file authorizes limited read-only checks; it does not sign you in.

Your code will appear here

Only run active checks on domains you administer or have permission to audit.

Choose a focused check

How scores work

Conclusive checks are weighted equally within each group. The overall score averages groups with data. Unknown results and measurements without a pass/fail judgement are excluded from the score and displayed separately. Coverage is shown beside the score. A high score with low coverage does not certify security.

Guides

Frequently asked questions

Is this a complete security audit?

No. It is a bounded external diagnostic. It does not execute exploits, guess passwords or certify a website as secure.

How long does it take?

Response time depends on the target and resources. A cached standard report can be returned faster, but no worldwide latency or three-second audit is guaranteed.

Can I audit any website?

Standard checks accept public HTTP/HTTPS websites. Private-network destinations are blocked. Active checks require a domain authorization file. Some websites block automated requests.

Are my reports indexed or shared?

Reports are not published as indexable pages. Changing the browser title does not create a shareable report URL. You can download the JSON or print to PDF.

Are reports cached?

When KV is available, standard reports may be reused for up to five minutes. The original scan time and cache status are shown. Active checks with an authorization code bypass the cache.