Our probe
The probe is the program that runs our audits. It always identifies itself by name, goes slowly and never forces its way in.
How to recognize it
User-Agent
The name it sends with every request:
AttackScout-Probe/0.1.0 (+https://attackscout.com/sonde)How fast
At most one request per second, per host name. A public audit only sends a few requests to the home page.
The methods it uses
GET and HEAD, reading files only partially (Range header). During an in-depth check, a single OPTIONS request on the root “/”, to read the methods your server advertises. Never POST, PUT, DELETE or TRACE.
The /attackscout-… path
During an in-depth check, the probe requests a random path once, in the form /attackscout-<random string>. It doesn't exist: your server should answer 404, and that's intended. This baseline response helps us rule out false positives, such as a site that answers “200” to every address.
During a public audit
The probe reads DNSThe internet's directory: it links your domain name to your servers. records, the certificate, the home page and, if they exist, the files your domain publishes for mail services (MTA-STSA rule that makes mail services encrypt the emails they send you. policy, BIMIYour logo shown next to your emails, in some mail services. logo). Nothing beyond these public reads: no other page, no subdomain. These are the 115 checks of the public audit.
During an in-depth check
Only if the domain owner has authorized it with the proof of ownership. The probe then checks whether known sensitive files are public, such as “/.env”, starting with the most serious, and then explores up to 50 pages while respecting your robots.txt. The in-depth check thus adds 33 checks to the public audit.
What it never does
No port scans, no login attempts, no forms submitted, no flaws exploited, nothing written on your systems or anyone else's. No key we find is ever tested or kept.
What you see in your logs
Requests to “/” with our User-Agent. For a domain that has authorized us, also requests to well-known paths, one request to an /attackscout-… path that returns 404, and one OPTIONS request on “/”: we only check what is public.
Why did it visit my site?
Someone ran a public audit of your domain on our website, or the domain owner has authorized us to monitor it. The public audit only reads what any visitor can read.
Its limits
- At most 70 requests per host name per audit, 15 of them reserved for exploring pages.
- On top of that, at most 3 TLSThe encryption that protects exchanges with your site: the browser padlock. handshakes per audit to check encryption, without any request: the connection is closed as soon as the server answers.
- At most one request per second, per host name.
- At most 4 KiB read per file checked. Explored pages and your site's JavaScript files (8 at most, 2 MiB each) are read the way a browser reads them. No script from another domain is ever requested.
- No content kept: only “present” or “absent”, the address, the type and the announced size.
- Your robots.txt is respected.
Stop the probe
Two ways, no reason needed: the exclusion form for your domain, or an email to [email protected]. You can also block our User-Agent or our addresses; our audits will then show “couldn't be checked”.
Contact us
A question about the probe, or unexpected behavior? Email [email protected].