User Agent

The User-Agent is an HTTP request header where the client declares what it is — for example a Chrome version on Windows, a mobile Safari build, or a scripting library. Servers read it to serve the right layout, enable features or gather analytics. It is trivially self-reported, so it is easy to set to anything, which is exactly why it is weak as a lone identity signal: a script can claim to be Chrome in one line. Sites therefore cross-check it against harder-to-fake signals rather than trusting it alone.

Because the User-Agent is easy to spoof, anti-bot systems compare it with your TLS fingerprint, browser fingerprint and behaviour. A request claiming to be Chrome but presenting a Python JA3 handshake is an obvious contradiction that gets flagged. For clean automation, keep the story consistent: if you set a Chrome User-Agent, the rest of your client should look like Chrome too. A proxy changes your IP but never your User-Agent, so the header is entirely under your control — set it honestly and consistently rather than pairing a browser string with a scripting-tool handshake.

Because the header is entirely under your control, set it honestly and keep it aligned with the rest of your client. If you present a Chrome User-Agent, your TLS fingerprint and behaviour should look like Chrome too, since anti-bot systems flag the contradiction rather than the header alone. A proxy changes only your exit IP, so pair a consistent client identity with an exit whose location matches your declared timezone and language for a coherent overall profile.