What is an HTTP/3 fingerprint?

It's a hash of your client's settings frame and pseudo-header order, unique per browser or tool like Chrome vs. curl.

Does GREASE stop HTTP/3 fingerprinting?

Nope — it adds noise, but stable values like window sizes and header sequences still ID you reliably.

Can I test my HTTP/3 fingerprint?

Yes, hit the researchers' API — paste your perk_text, get the hash, compare to known browser sigs.

HTTP/3 Fingerprints Betray Browsers — Even in QUIC's Fast Lane

Wireshark sniffs Chrome's GREASE-stuffed settings frame, and bam — instant browser ID. HTTP/3 fingerprinting is here, turning QUIC's speed into a tracking goldmine.

theAIcatchup Apr 10, 2026 4 min read

Wireshark screenshot showing HTTP/3 settings frame with Chrome fingerprint

⚡ Key Takeaways

HTTP/3 fingerprints use settings and pseudo-headers, MD5-hashed into unique perk_hashes for Chrome, Firefox, curl. 𝕏
QUIC doesn't kill tracking — it evolves it, aiding CDNs in bot detection amid 35% web traffic share. 𝕏
Browsers' GREASE helps little; expect regulatory scrutiny as privacy claims clash with reality. 𝕏

Published by

theAIcatchup

Community-driven. Code-first.

#HTTP/3 #HTTP/3 fingerprints #QUIC #QUIC protocol #browser detection #browser fingerprinting #fingerprinting #perk hash #web security

Worth sharing?

Get the best Open Source stories of the week in your inbox — no noise, no spam.

Originally reported by Dev.to

⚡ Key Takeaways

The 60-Second TL;DR

theAIcatchup

Share this article

Worth sharing?

Related Stories

GoWasp: Hack Your Own Web App to Master OWASP Vulnerabilities

localStorage JWTs: XSS's Free Lunch – Cookies Shut the Door

Home Lab Hack: SQL Injection Meets Its Match in Real Time

React Server Components' Perfect-Score RCE Flaw Exposes Millions of Apps

Stay in the loop