Labels inferred from traffic
- Label fingerprints from monitored traffic or crowdsourced submissions.
- Need independent evidence to verify software, version, and OS.
- Need revalidation as clients update.
Database
One database for everything that speaks TLS.
Browsers, HTTP libraries, bots, AI agents, malware: if it opens a TLS connection, it belongs in here. Every entry names the exact software, version, and operating system that produced it.
The difference
Captured, not collected.
Byteprint's approach
- Runs the real software in the factory, long tail included.
- Stores product, version, OS, and TLS stack with every fingerprint.
- Reruns clients on new releases and keeps the history.
Shared fingerprints
When clients share a fingerprint, we say so.
Many programs ship the same TLS stack, so their fingerprints can be identical. Byteprint keeps every known producer attached to a fingerprint instead of forcing one label onto it: you get the full list of candidates with a confidence for each, not false certainty.
Private beta
Search it yourself when the beta opens.
Explore further