Try
BROWSER TOOLS TCP uses todaySince 2026-11-07

TCP/IP fingerprint

When a TCP connection opens, the first SYN carries the sender’s initial TTL, window size, MSS and a list of options. Operating systems differ in those values and in option order, so a site can tell which kind of system opened the connection and compare it with the system the browser reports, which reveals a relaying proxy. This page connects straight to our probe and shows the first packet it captured plus kernel connection state.

This connection

Peer seen by the probe
 
TCP stack class
 
MTU
 
Distance
 
  • Testing

    The probe classes the TCP stack by SYN option order and initial TTL, then compares it with the system the browser reports. A mismatch means the TCP connection was not opened by your device directly: a proxy node or gateway relayed it. Linux and Android share one class and are not told apart.

  • Testing

    The probe times the round trip to its TCP peer; the browser times a whole request. They agree on a direct or layer-3 tunnelled connection. When the peer is a proxy node, the browser’s extra time is the leg from you to that node.

  • Testing

    MTU is the MSS in the SYN plus IP and TCP header sizes. PPPoE, mobile networks and every kind of tunnel lower it, so a reduced value shows encapsulation on the path without proving a VPN.

TCP/IP fingerprints

Computed from the first SYN
JA4Twindow_options_mss_scale
 
p0f-style signaturever:ttl:olen:mss:win:layout:quirks
 
Option orderThe main input to the class
 

JA4T is window size, option order, MSS and window scale. The fingerprint belongs to whichever system opened this TCP connection: your device when connecting directly or through a layer-3 tunnel (WireGuard, OpenVPN), the proxy node when traffic is relayed by SOCKS, an HTTP proxy or a Clash-style client.

Reference: SYN traits of common systems

Default settings
SystemInitial TTLOption order
Windows
128mss,nop,ws,nop,nop,sackOK
macOS / iOS
64mss,nop,ws,nop,nop,ts,sackOK,eol
Linux / Android
64mss,sackOK,ts,nop,ws

The estimate uses only option order and initial TTL. It is a broad class, not identification: Linux and Android look alike, as do macOS and iOS, and tuned kernels, routers or firewalls may match none of them.

First SYN packet

IP version
 
TTLObserved → estimated initial
 
Packet lengthIP header + TCP header
 
Don’t FragmentDF
 
IP ID
 
DSCP / ECNIP traffic class byte
 
TCP flagsECE with CWR requests ECN
 
Window size
 
MSSMaximum segment size
 
Window scaleEffective window = window × 2ⁿ
 
TimestampsTSval
 
SACKSelective acknowledgement
 

TCP options

#KindOption
1
2
3
4
5
6

Connection state

Kernel TCP_INFO on the probe
Round-trip timeSmoothed ± variation
 
Minimum RTT
 
Round trip in the browserFastest request on the reused connection
 
Send MSS12 less than the SYN MSS with timestamps
 
Path MTUCurrent value on the probe side
 
ECNNegotiated by both ends
 
RetransmissionsSegments the probe retransmitted
 
Segments in / out
 
HTTP protocol
 

How to use this tool

How this works

See the TCP/IP fingerprint of this connection: JA4T, a p0f-style signature and the SYN’s TTL, window, MSS and option order, with the implied MTU, link type, distance and system class.

Steps

  • The test runs when the page opens. Keep the proxy or VPN state you want to inspect.
  • Start with “This connection”: stack class, MTU, distance and three comparisons.
  • Copy JA4T to compare fingerprints; use the first-packet fields and option table when investigating a proxy.

What the result tells you

The fingerprint belongs to the system that opened the TCP connection: your device when direct or in a layer-3 tunnel, the proxy node when relayed.

The class uses only option order and initial TTL. Linux and Android look alike, as do macOS and iOS.

A reduced MTU shows encapsulation on the path. PPPoE and mobile networks lower it too, so it does not prove a VPN.

Common questions5

Why does the class differ from my computer?

A proxy node opened the TCP connection on your behalf, so the probe sees the node’s system, usually Linux. Layer-3 tunnels such as WireGuard and OpenVPN do not rewrite TCP and still show your own device.

How do I make the first packet match Windows behind a proxy?

The first packet comes from the machine that actually connects to the site, so changing settings on your Windows PC has no effect. Use a full-tunnel VPN such as WireGuard so the packet is your own, or use a Windows server as the exit. Setting TTL to 128 and turning off timestamps on a Linux node still leaves its option order and window scale, and a half-changed stack looks more like spoofing. A large gap between TCP round-trip time and the round-trip time the page measures also reveals the relay.

What is JA4T?

A TCP fingerprint defined by FoxIO: window size, option order, MSS and window scale. Systems of the same version usually share one; it is not a unique device identifier.

How is the hop distance derived?

Systems start packets with a TTL of 64, 128 or 255, and every router subtracts one. The nearest initial value minus the observed value is the number of hops to the probe.

Why is first-packet data sometimes missing?

The first packet is obtained by packet capture, which occasionally misses one. Only kernel connection state is shown then; testing again usually captures it.

mimetic
mimetic
mimetic