Analisador de User Agent
Analise strings de user agent para identificar navegador, SO, dispositivo e informações do motor
Cole uma string de user agent ou use a do seu navegador atual...
Proximos passos sugeridos
Ferramentas Relacionadas
Calculadora de Sub-rede IP
Calcule sub-redes, CIDR e intervalos de rede
Calculadora Chmod
Calcule permissões de arquivos Unix em notação simbólica e numérica
Conversor de Endereço IPv4
Converta endereços IPv4 entre formatos decimal, binário, hexadecimal e inteiro
Gerador de QR Code WiFi
Gere QR codes para credenciais de rede WiFi
Gerador de Endereço MAC
Gere endereços MAC aleatórios para teste e desenvolvimento
Códigos de Status HTTP
Referência rápida para todos os códigos de status HTTP e seus significados
Como Usar
Cole ou Digite
Insira seu texto, código ou dados na área de entrada.
Escolha as Opções
Selecione a transformação ou formato que deseja aplicar.
Copie o Resultado
Copie a saída para sua área de transferência com um clique.
Por Que Usar Esta Ferramenta
100% Gratuito
Sem custos ocultos, sem planos premium — todos os recursos são gratuitos.
Sem Instalação
Funciona inteiramente no seu navegador. Nenhum software para baixar ou instalar.
Privado e Seguro
Seus dados nunca saem do seu dispositivo. Nada é enviado a nenhum servidor.
Funciona no Celular
Totalmente responsivo — use no seu celular, tablet ou desktop.
User Agent Strings: Browser and Device Identification
Key Takeaways
- User agent strings identify the browser, operating system, and device type — but their format is notoriously inconsistent and often misleading.
- User agent parsing is essential for analytics, content negotiation, and debugging browser-specific issues.
- All parsing happens in your browser — your user agent data is never sent to any external server.
Every HTTP request includes a User-Agent header that identifies the client software. What started as a simple browser identifier has evolved into a complex string carrying browser, engine, OS, and device information — with decades of legacy compatibility quirks. Parsing user agents is essential for web analytics, responsive design debugging, and understanding your audience's technology profile.
Chrome's User-Agent string contains 'Mozilla/5.0' and 'Safari' — a legacy of browser compatibility hacks dating back to the 1990s.
Historical Quirk
Key Concepts
User Agent String Components
A typical UA string contains: Mozilla compatibility token, platform/OS info (Windows NT 10.0, Macintosh, Linux), rendering engine (AppleWebKit, Gecko), and browser name/version (Chrome/120, Firefox/121).
User-Agent Client Hints
The new Client Hints API (Sec-CH-UA headers) provides structured, opt-in device information instead of the bloated UA string. It offers browser, platform, and architecture data in clean, parseable format.
Bot and Crawler Detection
Search engine crawlers (Googlebot, Bingbot) and other bots identify themselves via user agent strings. Detecting these helps serve appropriate content and manage server resources.
UA Freezing and Reduction
Chrome is gradually freezing and reducing user agent string information for privacy. Many fields now contain fixed values. Developers should migrate to Client Hints for detailed device information.
Pro Tips
Never rely on user agent strings for security decisions — they can be trivially spoofed by any client.
Use feature detection (Modernizr, CSS @supports) instead of user agent sniffing for browser capability checks.
When analyzing user agents for analytics, use a maintained parsing library rather than custom regex — the format is too inconsistent for manual parsing.
Test your site with various user agents to ensure you are not accidentally blocking legitimate traffic from non-standard clients.
All user agent parsing is performed entirely in your browser. Your user agent string and browsing information are never transmitted to any external server.