Skip to main content
Every connection from a Stat Proxies IP carries the TCP/IP fingerprint of a Windows 11 PC unless you ask for something else. To send a macOS, iOS or Linux fingerprint instead, add -os-macos, -os-ios or -os-linux to the end of your proxy username. Your password stays the same. It is included free on every plan and works over HTTP, HTTPS and SOCKS5.

What it is

The first packet of every TCP connection (the SYN) carries values that depend on the operating system that sent it: the TTL, the window size, the order of the TCP options, whether timestamps are on, and the source port. A website can read those values and tell Windows, macOS and Linux apart. Through a proxy, the website sees the proxy server’s packets, not yours. Proxy servers usually run Linux, so proxy traffic usually reads as Linux even when your browser says Windows or Mac. Our servers send the values of the OS you pick.

Pick a profile

Add the profile name to the end of the username from your dashboard. Everything else (host, port, password) stays as it is. Profile names are lowercase. The profile applies per connection, so you can run Windows, macOS and Linux traffic through the same IP at the same time by using different usernames.
Android is not available yet. A username ending in -os-android, or any name not in the table, is rejected with HTTP 407 (SOCKS5: authentication failure). No traffic is sent with the wrong fingerprint.

Examples

How the profile is chosen

Our server picks the profile for each connection in this order:
  1. A profile in the username. -os-<name> always wins.
  2. The User-Agent. With no profile in the username, an HTTP or HTTPS request whose User-Agent header clearly names an OS gets that OS.
  3. Windows. Everything else gets the Windows 11 profile.
The User-Agent check reads the header your client sends to the proxy. For HTTPS that is the User-Agent on the CONNECT request, which browsers send and many HTTP libraries do not. The User-Agent check never rejects a request. If it can’t tell, you get Windows. SOCKS5 has no User-Agent, so SOCKS5 connections get Windows unless the username has a profile.
For scrapers and API clients, put the profile in the username. It is explicit, works the same over HTTP and SOCKS5, and doesn’t depend on which headers your library sends.

What each profile sends

These are the SYN values our servers send to the website for each profile. macOS and iOS share the same network stack, so they send the same SYN. Either name works. For comparison, a stock Linux proxy server sends TTL 64, window 64240, window scale 7 and timestamps on. That is why unconfigured proxy traffic reads as Linux.

Check it

tls.peet.ws echoes back the fingerprint of whatever connects to it. Send one request through your proxy and read tcpip.tcp_syn.
You should see: The TTL a website sees is the sent TTL minus one for each network hop, so it is always a little under 128 or 64. The mss value depends on the network path and is the same for every profile. If a flagged username returns 407, check the spelling against the table above. If the values don’t match, check that your client is actually using the proxy, then contact support.

What it covers

Set by our servers

Every TCP connection our servers open to a website: HTTP and HTTPS proxy traffic, and TCP over SOCKS5 (WebSockets, SSH, email and so on).

Comes from your client

Your TLS fingerprint (JA3, JA4), HTTP/2 settings, headers, User-Agent and browser fingerprint. UDP over SOCKS5 has no TCP handshake, so it has no TCP fingerprint.
Anti-bot systems compare the TCP fingerprint with the OS in your User-Agent and TLS handshake. Pick the profile that matches the browser or device you are presenting. A Chrome-on-Mac User-Agent should use -os-macos. A Chrome-on-Windows User-Agent can use the default.

FAQ

No. Every profile is included on every IP on every plan, the same as SOCKS5.
No. Add -os-<name> to your existing username and keep your password. Our server removes the suffix before it checks your login.
No. Usage is recorded under your normal username, whichever profile you use.
Yes. The profile is chosen per connection. Open one connection as USERNAME-os-macos and another as USERNAME-os-windows and each gets its own fingerprint.
Yes. Use the same username suffix on port 1080. SOCKS5 has no User-Agent, so without a suffix it uses Windows.
Your browser sent a macOS User-Agent, so our server matched it. Add -os-windows if you want Windows regardless of the User-Agent.
It is turned off until we have verified captures from real Android phones. Until then, Android User-Agents get the Linux profile, which is the closest match, and -os-android returns 407.
No measurable latency. Our servers set the values inside their network stack as each connection opens.
It removes one signal: a browser claiming one OS while arriving on another OS’s TCP stack. Anti-bot systems also score IP history, TLS fingerprint, browser environment and behavior. See Blocked Requests for the rest.
For background, read What is TCP/IP fingerprinting? on our blog. Using the API? See TCP fingerprint profiles in the API.