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