Anonymity Signals

Each anonymity signal answers one question: is this visit masked — relayed, tunneled, spoofed, or coming from infrastructure rather than a genuine, unmasked visitor? When a signal fires, it becomes a stable slug in the webhook’s data.signals array (name + weight) and a matching boolean in data.detection_flags. Branch on name, detection_flags, and the score band in code. ShieldLabs surfaces these signals; your own code owns the decision: allow, challenge, review, or block. Risk Scoring explains how the points roll up.

Network and anonymity

These signals indicate the connection is relayed, tunneled, or coming from infrastructure rather than a genuine, unmasked visitor.

Signal	What it indicates	Why it matters
Tor	The connection exits through the Tor network.	The strongest single anonymity signal: ordinary visitors rarely use Tor, and it is built to hide where a visit comes from.
VPN	The connection runs through a VPN.	Common and often legitimate (corporate or privacy use), so a lighter signal on its own.
Privacy Relay	iCloud Private Relay or a similar relay.	Mainstream and privacy-driven, so it is surfaced on its own and treated more gently than a deliberate proxy.
Proxy	The connection is routed through a proxy.	A common masking tool; weigh it together with the datacenter and abuser signals.
Browser VPN/Proxy	An in-browser VPN or proxy extension is in use.	An extension-level mask, a deliberate choice to hide the connection.
Datacenter IP	The IP belongs to a datacenter or hosting network, not a residential ISP.	Ordinary people rarely browse from datacenters, so it points to automation or relayed traffic.
Abuser Flag	The IP or device is on an abuse reputation list (a blocklist of addresses or devices tied to past abuse).	Prior abuse history alongside other masking signals.

Consistency and mismatch

These signals indicate two readings of the same visit disagree, which is what spoofed or relayed visits leave behind.

Signal	What it indicates	Why it matters
OS Mismatch	The operating system the browser reports is inconsistent with other evidence about the device.	A strong spoofing tell: an honest device does not contradict itself.
Timezone Mismatch	The device timezone does not match the IP geolocation.	A lighter location-spoofing tell; it can be innocent (travel), so weigh it with the rest.

Environment

These signals indicate the runtime is spoofed, stripped, or could not be fully verified.

Signal	What it indicates	Why it matters
Anti-detect Browser	Anti-detect or fingerprint-spoofing tooling is present.	A deliberate, sophisticated attempt to evade identification — a strong tell.
Browser Automation	The browser is driven by an automation framework rather than a person.	Automation-controlled browsers are near-certain non-human traffic — a strong tell that scores independently of the connection.
JavaScript Disabled	The page ran without the scripting a real browser provides.	Near-certain automation or a headless client, not an ordinary visitor — one of the strongest tells.
OS not Detected	The operating system could not be derived from the available evidence.	A stripped or unusual environment; treated as precautionary.
Stun not checked	The network check did not complete (`stun_not_checked`).	The visit’s network path could not be fully verified.

Surfaced, not currently scored

These are detected and returned on the webhook in detection_flags, but they add no points to the Risk Score today:

Signal	What it indicates
Incognito	The visit is in a private / incognito browsing mode (`incognito`).
IP Mismatch	The public `public_ip` differs from `local_ip` (`ip_mismatch`). A raw difference can be benign — mobile networks route over different paths — so compare `public_ip.country` with `local_ip.country` if location matters.
Suspicious paid click	A request that arrived on a paid channel and scored high (`suspicious_paid_click`). See Traffic Quality.
Search bot	The visit comes from a known search-engine crawler IP such as Googlebot or Bingbot (`search_bot`). It is not a masking signal: it adds no points and instead reclassifies the visit into the Search bot traffic channel so crawlers do not distort your analytics.

Signal weights

Each anonymity signal adds to the Risk Score by a fixed weight, listed in the full weight table on Risk Scoring. Signals sum into the score and the total is capped at 100. The strongest anonymity signal (Tor, then Privacy Relay, then VPN) takes priority over the others.

Connection type

Every visit also resolves to a single connection type, the headline label for how the visit reaches you. It is surfaced as connection_type on the webhook and as ConnectionType on each History API snapshot. The per-visit connection_type on the webhook and API is one of: Direct, Mobile, VPN, Proxy, Tor, Privacy Relay, Browser VPN/Proxy, or Unknown (when the type could not be resolved). The dashboard Connection Types breakdown uses the same buckets and rolls Browser VPN/Proxy into Proxy for the chart.

Connection type	What it indicates	Webhook / API (`connection_type`)	Dashboard breakdown
Direct	Ordinary connection, no masking signal. Home Wi-Fi without a VPN is typically this.	`direct`	Yes
Mobile	Cellular carrier, including tethering or hotspot.	`mobile`	Yes
VPN	Traffic runs through a system-wide VPN.	`vpn`	Yes
Proxy	Connection routed through a proxy.	`proxy`	Yes (includes Browser VPN/Proxy in the chart)
Tor	Connection exits through the Tor network.	`tor`	Yes
Privacy Relay	Relayed through iCloud Private Relay.	`privacy_relay`	Yes
Browser VPN/Proxy	In-browser VPN or proxy extension (not a system VPN).	`browser_vpn_proxy`	Rolled up under Proxy in the chart
Unknown	Type could not be resolved.	`unknown`	Yes

The connection type is a summary. The signals array on the Risk Score is the full breakdown: one visit can carry a proxy connection type along with a datacenter and abuser flag underneath it.

A masked visit is not always abuse

A legitimate visitor can carry these signals. A corporate VPN, iCloud Private Relay, or a privacy-focused browser all raise the score without any wrongdoing.

The connection type alone is not a verdict. Take the Risk Score, the anonymity signals, and the sensitivity of the action into account together — the same masked visit can warrant no friction on a low-stakes page and a challenge at a withdrawal, so match the response to the stakes.

Because every signal is explainable, your code can treat a Privacy Relay differently from a Tor exit or a datacenter IP. All are masking, but they carry different intent, and you decide which action each one warrants.

Example

A visit on an anti-detect browser running through a proxy returns both reasons in signals:

{
  "request_id": "13f84f05-3b2a-4f1e-9c7d-2a4b6e8f0a11",
  "device_id": "5eb7fd5c-8c2e-4a91-b0f3-1d7c9e2a4b55",
  "visitor_id": "161dfbad-2f4a-4c81-9e0b-7a3c5d8f1e22",
  "public_ip": {
    "ip": "203.0.113.42",
    "country": "NL"
  },
  "os": "Windows",
  "user_hid": "u_7f3c9a2b",
  "connection_type": "proxy",
  "risk_score": 70,
    "signals": [
    { "name": "antidetect_browser", "weight": 60 },
    { "name": "proxy", "weight": 10 }
  ],
  "observed_at": "2026-06-16T18:00:45Z"
}

The two signals add 60 and 10, landing at 70 in the High band.

Webhook signals[].name is a stable slug (antidetect_browser, proxy). Branch on that slug or on detection_flags (anti_detect_browser for the flag). Display labels such as “Anti-detect Browser” appear on the dashboard and in History Details.Description — do not treat those as webhook name values.

Because both reasons are visible, your code can require verification before a withdrawal while letting a low-stakes action through with no friction.

Next steps

Risk Scoring

How signal weights roll up into the 0-100 score and the Clean, Low, Medium, and High bands.

Patterns

The dashboard patterns that grade an identity over time, distinct from these per-request signals.

Getting started

Features

Frontend

Backend

Billing and usage

Security and privacy

Troubleshooting

Resources

Support

Legal

Network and anonymity

Consistency and mismatch

Environment

Surfaced, not currently scored

Signal weights

Connection type

A masked visit is not always abuse

Example

Next steps

Risk Scoring

Patterns

​Network and anonymity

​Consistency and mismatch

​Environment

​Surfaced, not currently scored

​Signal weights

​Connection type

​A masked visit is not always abuse

​Example

​Next steps

Risk Scoring

Patterns

Network and anonymity

Consistency and mismatch

Environment

Surfaced, not currently scored

Signal weights

Connection type

A masked visit is not always abuse

Example

Next steps