What is TLS Fingerprint?
An identifier derived from how a client opens a TLS connection, which distinguishes real browsers from HTTP libraries before any request is read.
The first message of a TLS handshake lists the client's supported versions, cipher suites and extensions in an order that is specific to each TLS library. Formats such as JA3 and JA4 condense that message into a short fingerprint.
A proxy does not change it. For HTTPS the proxy only tunnels the connection, so the website sees the proxy's IP combined with your client's fingerprint — and a Python or Node default fingerprint looks nothing like Chrome's.
Bot-management systems use it to block or rate-limit clients regardless of how many IPs they rotate through. Real browsers, or clients that impersonate a browser handshake, avoid the mismatch.
Related terms
WAF (Web Application Firewall)
A security layer that filters and blocks suspicious web traffic. Residential proxies and realistic request patterns help pass WAF checks.
Web Scraping
The automated collection of publicly available data from websites, commonly used for price monitoring, SEO, research and AI training datasets.
CAPTCHA
A challenge designed to tell humans from bots. Clean residential IPs and good request hygiene reduce how often CAPTCHAs are triggered.
Anti-Detect Browser
Software that creates isolated browser profiles with unique fingerprints, paired with proxies to manage multiple accounts without linking them.