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