Peakhour.IO - Cisco Mercury

What an Open Network Fingerprint Database Should Publish

AC — Sun, 06 Sep 2026 09:00:00 +1000

A useful open fingerprint database needs provenance, competing labels, raw evidence, format versions and licences—not another unexplained hash list.

Does TLS Fingerprint Canonicalisation Hide Attacker Variation? How to Test It

AC — Sun, 16 Aug 2026 09:00:00 +1000

Sorting makes TLS fingerprints more stable, but it also removes ordering evidence. Here is how to test whether the discarded variation matters.

A Network Fingerprint Is a Cohort, Not a Client

AC — Sun, 09 Aug 2026 09:00:00 +1000

TLS fingerprints group similar protocol implementations. They do not prove which application, device or person made a request.

From Joy to Mercury and EVE: Following Cisco's Network Fingerprinting Work

AC — Sun, 02 Aug 2026 09:00:00 +1000

Cisco's open-source collectors, fingerprinting research and Encrypted Visibility Engine form a clear lineage, but they are not interchangeable parts of one public system.

Two Lineages of TLS Fingerprinting: JA3, JA4 and Cisco Mercury

AC — Sun, 26 Jul 2026 09:00:00 +1000

JA4 did not descend from Cisco Mercury. The two projects come from different strands of TLS fingerprinting research and solve different operational problems.

One ClientHello, Three Fingerprints: JA3, JA4 and Mercury

AC — Sun, 12 Jul 2026 09:00:00 +1000

A reproducible lab runs JA3, JA4 and Cisco Mercury against the same TLS ClientHello and compares what each fingerprint preserves.