Where is this visitor, really?
Compare the device clock with the IP country, and check Tor exits, hosting ranges and your own blocklists.
SignalsvpntordatacenterIp
Step 4 of 4torBlock
Device clock
UTCmismatch
IP location
Tor exittor
How it plays out
The attack, what the verified event shows, and what your code does about it.
01 · The attack
How it usually goes
- Region hoppingPrices, content or offers from another country.
- Hidden originFraud from high-risk regions through a VPN.
- TorAnonymous traffic on sensitive flows.
02 · What Trace sees
Fields on the verified event
- vpnDevice offset that no zone of the IP country has.
"vpn": { "detected": true, "details": { "methods": ["timezoneMismatch"] }} - torRequest IP in your Tor exit list.
"tor": { "detected": true } - datacenterIpHosting and cloud ranges most VPNs exit from.
"datacenterIp": { "detected": true }
03 · What you do
Decide, with your own thresholds
- AllowConsistent
- Challengevpn: timezone mismatch
- Blocktor
Decision lab
Switch signals on and off. The score is a plain sum of weights.
Signals
Weights are the defaults in scoring.default.json. The cut-offs at 25 and 60 are examples; your app sets its own.
20suspectScore / 100
AllowLet the action through.
20/ 100
reasons
vpn+20
Implementation
One browser call, one server check.
01IdentifyCall the SDK on the action and send the eventId with it.
02VerifyYour server reads the event with a secret key.
03DecideAllow, challenge or block, with your own thresholds.
identify.ts
const trace = createClient({ apiKey: 'pk_...', endpoint: 'https://id.example.com' });
// On the action (signup, login, checkout), then send eventId with the form.
const { eventId } = await trace.get();Example response, illustrative
{ "eventId": "evt_example"}Start in shadow mode. Block later.
Log the decision for a week, check who it would have stopped, then turn it on.