<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Peakhour.IO - Security Research</title><link>https://www.peakhour.io/</link><description></description><lastBuildDate>Sun, 06 Sep 2026 09:00:00 +1000</lastBuildDate><item><title>What an Open Network Fingerprint Database Should Publish</title><link>https://www.peakhour.io/blog/open-network-fingerprint-database-schema/</link><description>&lt;p&gt;A useful open fingerprint database needs provenance, competing labels, raw evidence, format versions and licences—not another unexplained hash list.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">AC</dc:creator><pubDate>Sun, 06 Sep 2026 09:00:00 +1000</pubDate><guid isPermaLink="false">tag:www.peakhour.io,2026-09-06:/blog/open-network-fingerprint-database-schema/</guid><category>Security</category><category>Network Fingerprinting</category><category>TLS Fingerprinting</category><category>JA4</category><category>Cisco Mercury</category><category>Security Research</category></item><item><title>Does TLS Fingerprint Canonicalisation Hide Attacker Variation? How to Test It</title><link>https://www.peakhour.io/blog/tls-fingerprint-canonicalisation-attacker-variation/</link><description>&lt;p&gt;Sorting makes TLS fingerprints more stable, but it also removes ordering evidence. Here is how to test whether the discarded variation matters.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">AC</dc:creator><pubDate>Sun, 16 Aug 2026 09:00:00 +1000</pubDate><guid isPermaLink="false">tag:www.peakhour.io,2026-08-16:/blog/tls-fingerprint-canonicalisation-attacker-variation/</guid><category>Security</category><category>TLS Fingerprinting</category><category>JA4</category><category>Cisco Mercury</category><category>Network Fingerprinting</category><category>Security Research</category></item><item><title>Before JA3: How TLS Handshakes Became Fingerprints</title><link>https://www.peakhour.io/blog/before-ja3-tls-fingerprinting-history/</link><description>&lt;p&gt;JA3 made TLS fingerprints easy to log and share, but the technical ideas behind it had already been tested in SSL Labs experiments, a p0f patch and FingerprinTLS.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">AC</dc:creator><pubDate>Sun, 19 Jul 2026 09:00:00 +1000</pubDate><guid isPermaLink="false">tag:www.peakhour.io,2026-07-19:/blog/before-ja3-tls-fingerprinting-history/</guid><category>Security</category><category>TLS Fingerprinting</category><category>JA3</category><category>FingerprinTLS</category><category>p0f</category><category>Network Fingerprinting</category><category>Security Research</category></item><item><title>One ClientHello, Three Fingerprints: JA3, JA4 and Mercury</title><link>https://www.peakhour.io/blog/one-clienthello-ja3-ja4-mercury-lab/</link><description>&lt;p&gt;A reproducible lab runs JA3, JA4 and Cisco Mercury against the same TLS ClientHello and compares what each fingerprint preserves.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">AC</dc:creator><pubDate>Sun, 12 Jul 2026 09:00:00 +1000</pubDate><guid isPermaLink="false">tag:www.peakhour.io,2026-07-12:/blog/one-clienthello-ja3-ja4-mercury-lab/</guid><category>Security</category><category>TLS Fingerprinting</category><category>JA3</category><category>JA4</category><category>Cisco Mercury</category><category>Network Fingerprinting</category><category>Security Research</category></item></channel></rss>