37AuditsBot
Run by 37 Audits
How to detect 37AuditsBot
37AuditsBot signs its requests, so you detect it by verifying the cryptographic signature on each request. A valid signature proves the request came from 37 Audits; a copied user agent without the signature does not.
- Detection method
- SignedThe agent signs its requests, so its identity is verified cryptographically.
- Signals that identify it
- CryptographicA signed request verified cryptographically
- BehavioralHow the session clicks, types, moves and navigates, checked after the signature is verified
Every signal Verisoul checks for 37AuditsBot
37AuditsBot signs its requests, so we verify who it is cryptographically, then check the rest of the session.
- Used
Cryptographic
A signed request verified cryptographically
- Not used
Network
Not needed to identify it
- Not used
Device
Not needed to identify it
- Used
Behavioral
How the session clicks, types, moves and navigates, checked after the signature is verified
How often you'll see it
Very uncommon
Rare, brand new, or not seen on Verisoul traffic yet
Questions about 37AuditsBot
How do you detect 37AuditsBot?
37AuditsBot signs its requests, so you detect it by verifying the cryptographic signature on each request. A valid signature proves the request came from 37 Audits; a copied user agent without the signature does not.
What is 37AuditsBot?
37AuditsBot is an automated service from 37 Audits that signs its requests.
Does 37AuditsBot identify itself?
Yes. 37AuditsBot signs its requests cryptographically, which is the strongest way an agent can identify itself.
Can a bot pretend to be 37AuditsBot?
Not convincingly. A bot can copy 37AuditsBot's user agent, but without 37 Audits signing keys its requests fail verification and it is not labeled 37AuditsBot.
How common is 37AuditsBot?
Very uncommon. Rare, brand new, or not seen on Verisoul traffic yet.
What does the Verisoul API return for 37AuditsBot?
Every session Verisoul identifies as 37AuditsBot carries an agent block with id "37auditsbot", name, provider, type "other", detection_method "signed" and the detection_signals used (cryptographic, behavioral). Build rules on the id, type and detection method.