/browserleaks/fingerprints/tls

POST /api/browserleaks/fingerprints/tls

Price: 1 credit

Report the TLS fingerprint a server observes on a connection opened from this API — JA4 and JA3 hashes plus the full ClientHello: offered cipher suites, extensions and their advertised values

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. Compare two calls on `ja4` or `ja3n_hash`, both of which ignore ordering: the TLS client reshuffles its extensions on every connection, so the raw JA3 and the order inside `extensions` differ between two calls of an unchanged client and prove nothing about it.

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: "BrowserleaksTlsFingerprint")
• ja4 string required
• ja4_raw string nullable
• ja4_original_order string nullable
• ja4_original_order_raw string nullable
• ja3_hash string nullable
• ja3_text string nullable
• ja3n_hash string nullable
• ja3n_text string nullable
• user_agent string nullable
• tls_version string nullable
• record_version string nullable
• handshake_version string nullable
• cipher_suite string nullable
• key_exchange string nullable
• signature_scheme string nullable
• cipher_suites array (default: [])
  • @type string (default: "BrowserleaksTlsCipherSuite")
  • id integer required
  • name string required
• extensions array (default: [])
  • @type string (default: "BrowserleaksTlsExtension")
  • id integer required
  • name string required
• alpn array (default: [])
• supported_versions array (default: [])
• supported_groups array (default: [])
• key_share_groups array (default: [])
• signature_algorithms array (default: [])
• psk_key_exchange_modes array (default: [])
• certificate_compression array (default: [])
• ec_point_formats array (default: [])
• application_settings array (default: [])
• is_ech_offered boolean (default: false)
• is_ech_accepted boolean (default: false)

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.