HemerolabBot
Run by Hemerolab
How to detect HemerolabBot
HemerolabBot signs its requests, so you detect it by verifying the cryptographic signature on each request. A valid signature proves the request came from Hemerolab; 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 HemerolabBot
HemerolabBot 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 HemerolabBot
How do you detect HemerolabBot?
HemerolabBot signs its requests, so you detect it by verifying the cryptographic signature on each request. A valid signature proves the request came from Hemerolab; a copied user agent without the signature does not.
What is HemerolabBot?
HemerolabBot is a crawler run by Hemerolab that signs its requests.
Does HemerolabBot identify itself?
Yes. HemerolabBot signs its requests cryptographically, which is the strongest way an agent can identify itself.
Can a bot pretend to be HemerolabBot?
Not convincingly. A bot can copy HemerolabBot's user agent, but without Hemerolab signing keys its requests fail verification and it is not labeled HemerolabBot.
How common is HemerolabBot?
Very uncommon. Rare, brand new, or not seen on Verisoul traffic yet.
What does the Verisoul API return for HemerolabBot?
Every session Verisoul identifies as HemerolabBot carries an agent block with id "hemerolabbot", name, provider, type "crawler", detection_method "signed" and the detection_signals used (cryptographic, behavioral). Build rules on the id, type and detection method.