/browserleaks/fingerprints/tcp

POST /api/browserleaks/fingerprints/tcp

Price: 1 credit

Report the TCP/IP fingerprint a server observes on a connection opened from this API — JA4T, the Satori and Zardaxt operating-system estimates, the observed network path characteristics and the raw IPv4 and TCP header fields

How to use it

This describes the connection this call itself opens; there is no address or filter to aim it at something else, and it says nothing about your own client. Passive TCP fingerprinting reads the network stack that terminated the connection rather than the software that built the request, so the operating-system estimates are a statement about neither client. Inside `ip_header` and `tcp_header` the port, sequence and identification numbers plus the two checksums are minted per connection and carry nothing between calls, and `time_to_live` tracks the hop distance rather than the stack. The rest of those header fields describe the terminating stack itself and mostly repeat between calls: `window_size` and the option kind order are the first two components of the `ja4t` in the same record, so they are the part worth comparing.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)

Response

• @type string (default: "BrowserleaksTcpFingerprint")
• ja4t string required
• satori_fingerprint string nullable
• satori_signatures array (default: [])
• link_type string nullable
• os_scores array (default: [])
  • @type string (default: "BrowserleaksOsScore")
  • os string required
  • score integer required
• user_agent string nullable
• mtu integer nullable
• initial_ttl integer nullable
• distance_hops integer nullable
• tcp_rtt_seconds number nullable
• tcp_rtt_deviation_seconds number nullable
• ip_header object nullable
  • @type string (default: "BrowserleaksIpv4Header")
  • header_length_bytes integer nullable
  • type_of_service string nullable
  • total_length integer nullable
  • identification string nullable
  • flags string nullable
  • time_to_live integer nullable
  • protocol string nullable
  • header_checksum string nullable
• tcp_header object nullable
  • @type string (default: "BrowserleaksTcpHeader")
  • source_port integer nullable
  • sequence_number integer nullable
  • data_offset_bytes integer nullable
  • flags string nullable
  • window_size integer nullable
  • checksum string nullable
  • urgent_pointer integer nullable
  • options array (default: [])
• tcp_options array (default: [])
  • @type string (default: "BrowserleaksTcpOption")
  • name string required
  • kind integer nullable
  • length integer nullable
  • details array (default: [])
    • @type string (default: "BrowserleaksKeyValue")
    • name string required
    • value string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.