What is Browser Fingerprinting?

Also known as: Device Fingerprinting, TLS Fingerprinting, JA3 Fingerprinting

Identifying a client by the unique characteristics of its software/hardware.

Browser fingerprinting identifies and tracks a client by combining attributes such as the user-agent, screen size, installed fonts, canvas and WebGL rendering, and TLS handshake details into a unique signature. The TLS handshake alone yields a distinct fingerprint — often captured as a JA3/JA4 hash derived from the client's cipher suites, extensions, and their ordering — and because scripting libraries negotiate TLS differently from real browsers, anti-bot systems can flag automation even when the IP and User-Agent look normal. They correlate these fingerprints with IP behavior to spot automation even when IPs rotate. Robust scraping therefore pairs clean residential proxies with consistent, realistic browser fingerprints — often via anti-detect browsers or real browser engines (headless browsers) that produce authentic TLS fingerprints.