Check your website.

A simple score, clear priorities, and the evidence behind them.

Assessment status

Ready when you are

Enter a website URL to start an assessment.

An external assessment has limits. A high score cannot certify site safety or protection against AI attacks.

Your assessment

Report

Public protection score

This score measures publicly observed protections, not your website’s overall security. Encryption scrambles data during a connection to help keep it private.

Score details and limits

Website settings score:

Protected connections and proof of website identity each contribute 30 points; protection for identified sign-in cookies contributes 20. Cookies are small pieces of browser data that can remember a signed-in visitor. Extra browser rules contribute 20 points: limits on page code 10, keeping future visits encrypted 5, preventing deceptive embedding 3, and treating files correctly 2. If no sign-in cookies are found, their points move to the connection checks. Missing evidence produces a score range. Deeper encryption checks can subtract up to half a point. Verified connection failures, affected software or scam-list entries can limit the score. Suspicious content patterns need investigation and do not automatically lower it. This measures the public checks completed, not the chance of being attacked.

What needs attention

Review the observed settings and qualified warnings below. Published severity describes a warning; it does not establish an attack on this website.

Optional improvements

Additional defenses for your developer to consider after observed issues. Missing one does not prove a security flaw. Together, these settings contribute at most 2 points.

Protections we found

Passing checks cover only the pages and settings tested; they do not prove the entire website is safe.

Is there harmful content or a scam warning?

We check for known harmful code, suspicious page content and warning-list entries. A clear result only covers what we could check.

How does the site protect visitors?

Is the connection securely encrypted?

We check how one publicly reachable server encrypts visitors’ connections. TLS and older SSL are names for connection-encryption methods. These checks can reveal outdated settings. Confirmed weaknesses reduce the score by at most half a point.

What other browser protections are available?

These checks look at privacy, browser-feature access and code loaded from other websites on the first page. They do not change your score.

Which website and services did we reach?

What can search engines discover?

We look at instructions for search engines and lists of public pages. These settings control discovery, not access: they do not keep information private or affect your score.

What people can discover about your site

Public pages can reveal the website-building tool, its add-ons and outside services a site uses. Revealing a name alone is not a security flaw. We do not check domain ownership or personal contact details.

Which software does the site appear to use?

What we could not verify

Technical findings and evidence

All retained observations

Want an agent readiness check?

Find out how easily AI agents can read and navigate your website, and how your site handles agent traffic.

A separate tool is coming soon.