Technology
An autonomous fingerprint factory.
Byteprint is developing software fingerprint intelligence for security investigations. The public product overview describes the intended outcomes; technical specifications will accompany beta access.
The problem
Claims are easy to fake.
An HTTP client can choose its User-Agent text. TLS characteristics provide another signal, but a fingerprint needs software context before it can support an identity decision. That is where reference data matters.
The process
How a fingerprint is made.
- 01
The handshake
TLS clients exchange handshake messages to establish a connection. Observable characteristics can provide context about the client software and its configuration.
- 02
Real execution
Byteprint installs the actual software on real hardware and lets it connect: browsers, libraries, bots, malware. No guessing from someone else's traffic.
- 03
Full capture
Everything the client sends is recorded, so each fingerprint enters the database with the exact product, version, and operating system that produced it.
- 04
Reverification
A fingerprint is only admitted once it reproduces, and it is recaptured whenever the software updates.
Why Byteprint
Built to stay correct.
Monitoring and crowdsourced databases decay: labels are guesses, updates silently invalidate them, and nobody can rerun the evidence.
Byteprint produces every fingerprint itself on real hardware and captures everything the software sends. That is the edge: a database where every entry is ground truth, kept current by rerunning clients whenever they update.
Private beta
See it before general availability.
Explore further