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