A pure-JS module for Node.js environments, `read-tls-client-hello` provides robust functionality to intercept and parse TLS Client Hello messages from incoming socket connections before the full TLS handshake commences. This library, currently at version 2.0.0, is distinguished by its zero runtime dependencies and its capability to unshift the parsed data back into the socket, allowing the connection to proceed normally after analysis. It enables the calculation of TLS fingerprints (JA3/JA4), offering insights into the type of client initiating the connection, such as browsers or specific tools, independent of request content. While there isn't a strict release cadence, updates are typically driven by feature enhancements or necessary maintenance. Its core differentiator lies in its minimal overhead and its unique ability to pre-process TLS handshakes without disrupting the connection flow, making it ideal for proxying, security analysis, or custom server logic that requires early client identification. It succeeds the deprecated `read-tls-fingerprint` package, expanding its scope beyond just fingerprinting.
npm install read-tls-client-helloVerified import paths — ran on the pinned version, not inferred.
This quickstart demonstrates how to set up an HTTPS server using Node.js's `https` module and integrate `read-tls-client-hello` to automatically track and access TLS Client Hello information, including JA3/JA4 fingerprints, on incoming request sockets.
Update `package.json` to `"read-tls-client-hello": "^2.0.0"` and change all `import` or `require` paths accordingly.
Upgrade your Node.js runtime to version 20.0.0 or later.
Combine TLS fingerprint data with other client identification techniques (e.g., User-Agent headers, IP reputation, behavioral analysis) for more robust and reliable client classification.
Update your `package.json` to depend on `read-tls-client-hello` and adjust `import`/`require` paths.
Ensure you are using `import { trackClientHellos } from 'read-tls-client-hello';` for named exports, or verify module type configuration in your `package.json`.Ensure the input stream is an initial socket connection containing a raw TLS Client Hello message and no other data has been consumed from it prior to calling `readTlsClientHello`.
No dependency data recorded yet.