What are HTTP/3 fingerprints?

They're hashed strings from settings frames and pseudo-header orders in QUIC traffic—unique per client, like Chrome vs curl.

How to check my HTTP/3 fingerprint?

Hit the API they built—send a request, snag your perk_hash. Dead simple.

Yep, unless you mimic a browser perfectly. Bots die first, users next.

🌐 Frontend & Web

QUIC was the great equalizer, right? Wrong. HTTP/3 fingerprints nail clients harder than ever, from Chrome's GREASE tricks to curl's dead giveaway.

theAIcatchup Apr 10, 2026 3 min read

HTTP/3 fingerprints work just like HTTP/2, using settings and pseudo-headers for client ID. 𝕏
Chrome's GREASE adds quirkiness, making evasion tougher. 𝕏
Privacy hits hard—bots busted, browsers next in the crosshairs. 𝕏

Published by

Ship faster. Build smarter.

#Fingerprinting #HTTP/3 #QUIC #Web Protocols #browser privacy #client identification

Get the best Developer Tools stories of the week in your inbox — no noise, no spam.

Originally reported by dev.to