USER-AGENT TOKENS, CLIENT HINTS & BROWSER ARCHITECTURE
Comprehensive guide to HTTP User-Agent header structure, Mozilla compatibility tokens, and privacy client hints.
1. Legacy User-Agent Token Structure
Historical browser compatibility wars created the modern User-Agent convention where almost every mainstream browser claims compatibility with Mozilla and Apple:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36
Mozilla/5.0: General legacy token inherited from Netscape Navigator.Windows NT 10.0; Win64; x64: OS family, NT kernel version, and 64-bit architecture.AppleWebKit/537.36: KHTML/WebKit rendering engine foundation, forked by Blink.Safari/537.36: WebKit legacy compatibility indicator.
1. Zero-Server Privacy
Pure client-side regex parsing. Your hardware fingerprints and telemetry strings never leave your local session.
2. Bot / Crawler Recon
Instantly identifies search crawlers (Google, Bing), AI training spiders (GPTBot, ClaudeBot), and headless scrapers.
3. Native Client Hints
Reads active screen color depth, pixel ratio, and processor concurrency directly from the DOM window API.