Skip to content
// how it works

Check. Watch. Fix. You only do the first one.

Start with a free passive check. If you'd like us to keep watching, we do it only with your proof of ownership and written permission. When something needs fixing, a web developer fixes it.
$ check

Check: the free, passive look

You type your domain into the free website security check. In about 30 seconds you get a grade from A to F, the top three things to fix, and a plain-English explanation of each, with the technical detail alongside for your developer.

The check only looks at what any browser visitor can already see: public DNS records, your padlock certificate, whether http:// redirects to https://, the security headers and cookies on your home page, your SPF and DMARC email records, any software versions your site advertises, and anything on the home page that loads without encryption.

  • One request to your home page (following up to five redirects), one plain http:// request, one TLS handshake and a few DNS lookups. That's all.
  • No crawling, no guessing at hidden pages, no port scanning, no logins, no attack payloads.
  • Nothing is stored. The result lives in your browser until you close the page, unless you ask us to email it.
$ watch

Watch: ongoing monitoring, with your permission

If you want us to keep an eye on things, get in touch and we'll have a short call. Once you're onboarded as a client, we record what your site runs (its content management system, plugins, server software and their versions). When a significant flaw is published, we compare it against that list and tell you: affected, possibly affected, or you're fine, with what to do next.

Monitoring also includes scheduled, deeper checks from outside your site, and a monthly plain-English report with a technical appendix. These checks go further than the free one, so they only ever happen after two things are in place.

  1. 01

    You prove you own the site

    By adding a DNS TXT record, uploading a small file to /.well-known/, or adding a meta tag, the same way Google Search Console verifies ownership.

  2. 02

    You give written permission

    A short authorisation to test agreement records who signed, their role, the date, exactly which domains are in scope, which tests are allowed, the testing window and an expiry date.

This is a service run by a person, not an app: there's nothing to install and no account to manage. You get a monthly report and someone to call. See pricing, or book a call to get started.

$ fix

Fix: a human does the work

Every report ends with an offer to fix what we found, with a clear, fixed quote per job. Nothing starts until you say yes. A web developer does the work (usually configuration changes, updates or clean-ups) and then checks again to confirm each issue is closed.

You're never obliged to use us. Every report includes enough technical detail for your own developer or host to make the fixes. See website security fixes for the kinds of work we do.

$ man limits

The honest limits of automated testing

Automated checks are good at spotting known, visible problems quickly and consistently. They are not good at judging business logic, finding flaws nobody has published yet, or seeing behind a login. Even a deeper authorised scan can miss things, and can occasionally flag something that turns out to be fine. A person reviews every finding before it reaches you.

So we never say your site is "secure". We tell you what was checked, when, and what a check can't see. Good security is strategy, not panic: a steady routine of checking, updating and fixing, rather than a single test and a certificate.

// questions

Common questions

How long does the free check take?

Usually 5 to 30 seconds. It has a hard 20-second budget for the network work, so a slow or unreachable site can't keep you waiting.

Will the check slow down or break my site?

No. It makes about the same requests as one person opening your home page in a browser, plus a few public DNS lookups.

What do you need from me to start monitoring?

Proof that you own the site (a DNS record, a file or a meta tag) and a signed authorisation that sets out what we may test and when. We guide you through both; it takes about ten minutes.

Can I cancel monitoring?

Yes, any time. When you cancel, the authorisation ends and no further scans are run. We delete your monitoring data in line with our privacy policy.

Do you need access to my hosting or admin login?

Not for checks or monitoring. For fix work we agree exactly what access is needed, for how long, and remove it afterwards.

Start with the first step.

Run the free check now. It takes about 30 seconds and you don't need an account.

Talk to a human