Skip to Content
Platform.Ontology

TCP/IP passive OS fingerprint (p0f, JA4T)

The TCP handshake reveals the operating system through TTL, window size, MSS and option order.

Used to track youNetwork and connectionTCPWeb browsersWhen the page loads

In one line

Can guess your operating system from how your device opens a connection

The TCP handshake reveals the operating system through TTL, window size, MSS and option order.

p0f (Zalewski) and JA4T read SYN fields: initial TTL (64 or 128), window size, MSS, window scale and option order. Windows, Linux, iOS and macOS differ, and a mismatch with the User-Agent signals spoofing or a proxy.

What it can and can't do

What the user does: Nothing. It happens when your device first connects to the server

It can

  • Guess whether you run Windows, Mac, Linux, Android or iPhone from connection details
  • Catch visitors whose claimed system does not match their real one
  • Filter attack traffic that has odd connection patterns

It cannot

  • See your name, account or files
  • Tell the exact version or device model
  • Be hidden by clearing cookies or using private browsing
  • Work well through a proxy or relay, since it only sees the last hop

Browser support

BrowserStatusFirst versionReleasedNote
ChromeSupported12008-12-11None
EdgeSupported792020-01-15None
FirefoxSupported12004-11-09None
SafariSupported12003-06-23None
Safari on iPhoneSupported12007-06-29None
Chrome on AndroidSupported1Not listedNone
Samsung InternetSupported5.02016-12-15None

How a site asks for it

APISYN packet capture (p0f v3, JA4T, Zeek)
How access is grantednone
What the user seesNot listed
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsNot listed
How to take it backNot listed
Inside an iframeNot listed

Typical flow

  1. Capture the SYN
  2. Compute signature
  3. Compare OS guess to User-Agent

Data you get

What comes back: Signature such as 4:64:0:1460:mss*10,6:mss,sok,ts,nop,ws:df,id+:0
Shape: string

FieldTypeUnitRangePrecision
ttlintegerNone1 to 255initial TTL inferred

Technical limits

  • Altered by load balancers, VPNs and proxies
  • Reveals the network stack, not the browser

The story

What it is

The very first network packets from your device reveal what kind of operating system it runs.

For you

You never see it. Every device opens a connection in a slightly different way. A server can read that pattern and guess if you are on Windows, Mac, Linux or a phone.

For makers

Makers use it to catch visitors who say one thing and are another, such as a bot claiming to be an iPhone while running on Linux. It needs no code in the browser and cannot be changed by a page.

Where you see it

TypeExampleApps
securityA ticket site sees a visitor claiming to be an iPhone, but the connection pattern looks like a Linux server. It blocks the request as a bot.None named
adsAn ad fraud service compares the claimed device with the network pattern and drops mismatches from billing.None named
gamesA browser game blocks sign ups from servers pretending to be Windows players, which stops bot farms and cheat tools.None named
bankingA bank compares the system seen at login with the customer's usual one and asks for more proof if it changes.None named
analyticsA traffic report separates real phone visits from automated ones that spoof phone browsers.None named
enterpriseA firewall flags an unexpected system type on a company login and steps up checks.None named
shoppingA retailer ties repeated suspicious orders to the same network pattern, and slows them for review.None named

Risks

  • Hard to see or avoid
  • Misreads VPNs and routers

Good uses and abuse

Legitimate uses

  • OS vs User-Agent mismatch detection, DDoS filtering

Known abuse

  • Silent OS identification

Scores

ScoreValueMeaning
Sensitivity2 of 5How revealing the data is
Utility4 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bits3Rough identifying entropy, when known

Sources

How well checked: Based on official documentation.

On this page