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