TLS fingerprinting

Guides

Encrypted Client Hello: what ECH hides and what proxies see

Encrypted Client Hello (ECH) hides the hostname in the TLS handshake. How it works, what stays visible, 2026 support, and why it often stops behind a proxy.10 min read
Guides

HTTP/2 fingerprinting: the frames and what a proxy changes

HTTP2 fingerprinting reads the SETTINGS, WINDOW_UPDATE, PRIORITY and pseudo-header order a client sends first. Real values from Chrome, Firefox and Go.8 min read
Guides

How anti-bot systems work, and where a proxy tier fits

How anti-bot systems work, from vendor docs: IP reputation, TLS fingerprints, browser checks and behaviour feed one score, then a policy picks the challenge.11 min read
Comparisons

JA3 vs JA4 TLS fingerprinting, and what a proxy changes

JA3 vs JA4 TLS fingerprints compared field by field: why Chrome's extension shuffle broke JA3, how JA4 stays stable, and what a proxy changes.10 min read
Best Practices

Why proxies trigger captchas, and what reduces them

Why proxies trigger captchas: the risk score behind each challenge, the inputs your proxy tier changes, and what a legitimate client can fix first.12 min read
Guides

How do websites detect proxies? Every layer, in order

Websites detect proxies by IP and ASN, TCP stack, TLS, headers, browser leaks and behaviour: what each layer sees, and a self-test you can run.13 min read
Guides

Mobile proxies in 2026: what platforms actually check

Mobile proxy detection runs in layers: carrier ASN, CGNAT, TCP stack, TLS and behaviour. What a real carrier pool changes, what the client owns, how to check.11 min read