Subdomains and forgotten hosts
Hostnames tied to your domain, found through public sources and certificate records, so old test, staging and campaign sites come into view.
Every domain, server and service your business exposes to the internet, found and checked for weaknesses.
Then a plain-language report on what to fix first.
Attackers rarely start with your front door. They start with everything else you have online.
A test server nobody switched off. A subdomain still pointing at a cancelled service. A database port opened for one afternoon. An admin login on the default path. Each one is visible to anyone who looks, and automated attackers look all the time.
We find them the way they do: from the outside, with no access, passwords or software installed on your side.
Outside-in, the way an attacker would look
Twelve kinds of checks, run across your domain and the hosts we discover behind it.
Hostnames tied to your domain, found through public sources and certificate records, so old test, staging and campaign sites come into view.
What answers from the internet, which software and version it runs, and which services should never be public, such as databases or remote desktop.
Detected software versions checked against public vulnerability databases, plus thousands of checks for known exposures and misconfigurations.
Misconfigurations, default files and outdated components on your web servers, and a passive review of the live application as we crawl it.
Backups, database dumps, configuration and source-control files, and login pages that are reachable when they shouldn't be.
API keys, tokens and credentials accidentally shipped in the JavaScript your site sends to every visitor.
Certificate validity and expiry, protocol versions and cipher strength on every service that uses encryption.
Whether your sites tell browsers to enforce HTTPS, restrict scripts and refuse to be framed: protections many sites still lack.
SPF, DKIM and DMARC on your domain and its subdomains. Can someone send email that looks like it came from you?
DNS records still pointing at services you no longer use, which an attacker could claim and serve content from under your name.
Storage buckets named after your brand that are open for anyone to list, read or write.
A read-only, AI-assisted pass over your web application to catch logic and configuration issues that fixed checks miss.
Written for the person who has to fix things, and the person who has to approve the work.
One security score and an A to F grade for your whole external surface, so you can see where you stand and measure progress after fixes.
Each issue rated from critical to informational, with where we found it and the evidence behind it.
Plain-language remediation for each finding, and a prioritised list of recommendations for the whole surface.
The free scan shows you where you stand. A full assessment covers everything.
Four steps, and nothing to install.
Fill in the form below. Using an email address at the domain you want scanned speeds things up.
We only scan domains you own or have permission to test. We reply within one business day to confirm, usually through an address at that domain.
No access, passwords or installs. The checks detect weaknesses; they don't exploit them, change data or try to take anything down.
We send it to you and only you. Ask us anything about it, with no obligation to buy.
The domain you name and the subdomains we discover from public sources.
Confirm you own the domain or are authorised to have it tested. We check before we start.
The report goes to you. We don't publish findings or share them with anyone else.
No newsletter and no follow-up campaign. If you want more, you ask.
What people usually ask before their first scan.
Yes. The checks are built for production systems and their request rates are capped. They look for weaknesses rather than exploiting them, and they don't change data or try to take services down. If you have a fragile system or a maintenance window, say so in the form and we'll plan around it.
No. External scanning looks only at what anyone on the internet can already reach. You don't give us credentials and nothing is installed on your systems.
Scanning systems without permission can be unlawful, and the domain in a form might not belong to the person filling it in. So we only scan domains you own or are authorised to have tested, and we confirm that with you before we start.
No. A scan finds and checks your exposed systems at scale. A penetration test goes further: people manually try to exploit what they find. A scan is the sensible first step, and its results show where deeper testing is worth paying for.
They might. Firewalls and security services can log or block scanning traffic, which is a good sign that they're watching. If you'd like us to coordinate with your IT provider or host first, tell us in the form.
You keep the report. If you want help fixing what we found, or a full assessment, reply and we'll scope it with you. If not, that's the end of it.
One domain, outside-in, free. Start with a short form.