Real-Time User-Agent
& Device Inspector

Inspect raw User-Agent strings, extract browser builds, detect hardware platforms, identify search engine crawlers, and audit bot footprints in real time.

Google Chrome

Desktop

Windows 10 / 11 · 64-bit (x86_64)

Standard Client

Browser Application

Browser Name: Google Chrome

Version: 124.0.0.0

Rendering Engine: Blink Core

Platform & Hardware

Operating System: Windows 10 / 11

Form Factor: Desktop

Architecture: 64-bit (x86_64)

Traffic Classification

Crawler / Bot: No (Human Client)

Client Hints Target: Sec-CH-UA Ready

Audit Engine: Cloaker Sub-15ms Core

Data Definitions

Key User-Agent & Hardware Metrics

Every request header contains essential client signatures required for traffic filtering, cloaking protection, and device routing.

Browser & Build

Client Identification

Identifies the core browser engine and exact release versions to detect feature compatibility and headless automation scripts.

Rendering Engine

Layout Core

Exposes underlying layout engines (Blink, WebKit, Gecko) to uncover mismatched rendering layers used by ad crawlers.

Platform & OS

Host Environment

Verifies the operating system and architecture (x86_64, ARM64) to validate authentic mobile and desktop devices.

Bot Signatures

Automated Traffic Audit

Instant token detection for search bots, social media crawlers, and headless testing suites in under 15ms.

Precision Device Routing

Review bots spoof mobile User-Agents.
Filter fake devices with edge fingerprinting.

Automated ad review crawlers frequently broadcast mobile strings from datacenters. Cloaker.net pairs User-Agent evaluation with TLS JA3/JA4 ciphers, IP ASN classification, and touch API verification in under 15ms.

Granular OS & Device Rules

Sub-15ms Redirection Latency

Pre-Filtered Meta & Google Crawlers

Safe Page / Money Page Splitting

Start Free Trial Instant Setup · Zero SDK Required

Support & Guidance

Frequently asked questions

Everything you need to know about User-Agent parsing, Client Hints, and bot identification.

What is a User-Agent Parser?

A User-Agent Parser decomposes the raw HTTP 'User-Agent' request header into structured metadata: browser name and major/minor version, rendering engine (Blink, Gecko, WebKit), operating system, CPU architecture, and device category.

Why is User-Agent parsing critical for ad cloaking and traffic filtering?

Ad networks and automated scrapers often use headless or dated User-Agent strings. Cloaker.net analyzes User-Agent strings alongside client-side hardware signals and edge TLS fingerprints to reliably detect bots and route traffic accordingly in under 15ms.

Why do all modern User-Agent strings start with 'Mozilla/5.0'?

During the early browser wars, Netscape (code-named Mozilla) supported advanced features. To ensure web servers delivered full modern HTML content instead of stripped legacy layouts, competitor engines (IE, Safari/WebKit, Chrome) added 'Mozilla/5.0' compatibility tokens.

What is User-Agent Client Hints (UA-CH)?

User-Agent Client Hints is the modern privacy-preserving standard replacing legacy monolithic UA strings. It provides structured HTTP request headers (Sec-CH-UA, Sec-CH-UA-Platform, Sec-CH-UA-Mobile) for accurate browser and device detection.

Works seamlessly with your favorite ad networks, trackers, and traffic sources