1. Home
  2. Scanning policy

Scanning policy

What our scanner does, how to recognise it, and how to ask us to stop.

How we identify ourselves

Our scanners send a User-Agent that names Secrabbit and points to this page: SecrabbitScanner/<version> (+https://secrabbit.cloud/scanner). If you see it in your logs, this page explains what it is.

Two kinds of checks

Passive checks: public information only

For the free check and for monitoring we read public sources about a domain. We do not connect to your servers to do this.

  • DNS records of the domain.
  • Certificate transparency logs, which list certificates issued for the domain.
  • Email authentication records such as SPF, DMARC and MTA-STS.
  • Hosting information, meaning who runs the network an address belongs to.
  • Domain registration data (RDAP).

Active checks: only with authorisation

We run active checks only against systems of a client who has authorised them in a signed agreement. They are light-touch:

  • a few light HTTP requests per run: a GET of the home page / and of /.well-known/security.txt;
  • TLS handshakes, to read the certificate and the protocol settings: up to five per host and port in one run;
  • TCP connections to ports 80 and 443 only.

What we do not do

  • No attempts to log in, guess passwords or exploit anything.
  • No crawling of your site, no fuzzing, and no scanning of other ports.
  • No load or denial-of-service testing.
  • No active scanning of hosts that belong to someone else, even when a client's domain points at them. Those get passive checks only.

How often

Each client is scanned on a regular schedule, with a full scan about once a week. A client can also ask for a rescan of an asset, and we limit those to one every ten minutes per asset. Every run is small: the requests listed above and nothing more.

Tell us to stop

If you are not our client and you see our requests, or if you want us to stop checking a domain, write to hello@secrabbit.cloud with the host, domain, IP address or address range. We add it to our opt-out list. A domain on the list covers its subdomains. Nothing on the list is sent to any of our scanners, active or passive, so we stop scanning those addresses altogether.

A person adds each entry by hand, so it is not instant and there is no self-service form yet. Security researchers can also reach us through our security.txt.