Negotiated security
TLS version and cipher suite describe a completed secure connection when the hosting path exposes them.
Inspect the secure connection details visible to Localtonet and compare its request signature.
Checking HTTPS, TLS and HTTP details visible to the application.
The comparison signature is generated from application-visible request details. It is not a JA3 or JA4 TLS handshake fingerprint.
TLS protects an HTTPS connection. The negotiated TLS version and cipher suite describe that connection when the hosting path makes them available to the application.
This tool combines available TLS details, the HTTP protocol and selected request headers into a comparison signature. Open the detected details to copy it, then compare after a browser or proxy change. For properties exposed by page scripts instead, use the browser fingerprint test.
TLS version and cipher suite describe a completed secure connection when the hosting path exposes them.
A CDN or reverse proxy can terminate TLS before the request reaches Localtonet. Missing application values do not mean your browser connection is insecure.
Use the app- signature to compare request shapes after a browser or configuration change. It cannot identify a person.
Those fingerprint families require details from the TLS ClientHello. This application signature uses a different source of evidence.
Waiting for the test…Run the test to see its detected details.
No. It is an application-layer HTTP/TLS request signature and does not inspect a raw ClientHello.
The TLS connection may terminate at a reverse proxy or CDN that does not forward the negotiated details to the application.
HTTP negotiation, headers, browser updates and intermediary behavior can all change the application-visible request.