Technology
An autonomous fingerprint factory.
Byteprint does not observe fingerprints. It manufactures them: the factory installs real software, runs it, and captures what it sends, with no human in the loop.
The problem
Claims are easy to fake.
A client can claim to be anything. Its TLS handshake is far harder to disguise, and JA4 condenses that handshake into a fingerprint. A fingerprint only means something if you know which software produces it. That takes a database.
The process
How a fingerprint is made.
- 01
Discover
Catalog network-capable software from registries, indexes, and security sources.
- 02
Run
Execute each client autonomously in a contained environment, malware included.
- 03
Capture
Record the handshake and extract the JA4 with exact product, version, and OS attached.
- 04
Reverify
Reproduce every fingerprint before admission, recapture when the software changes.
Why Byteprint
Built to stay correct.
Monitoring and crowdsourced databases decay: labels are guesses, updates silently invalidate them, and nobody can rerun the evidence.
The factory reruns clients when they update, reproduces every fingerprint before accepting it, and keeps the raw capture for audit. This database gets better with time while the others fall behind.
Private beta