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