IGRSIGRS
Runs In Browser · No Login · No Data Sent · IGRS 2026

> USER-AGENT PARSER_

10 free tools for investigators and security professionals. All computation runs locally — nothing is transmitted to any server.

HashBase64PasswordCIDRJWTRegexEpochUser-AgentHexURLAll tools
🖥 User-Agent Parser
Parse browser User-Agent strings — identify OS, browser, device type, bot detection. Useful for log analysis.

User-Agents as evidence

Web server logs, login histories and platform responses to legal notices often include the User-Agent string of the device that made a request. Parsing it gives the browser, version, operating system and device class — useful for linking sessions to a suspect's device, spotting automated tools, and separating mobile from desktop activity.

User-Agents are self-reported and trivially spoofed, so treat them as corroborating evidence alongside IP addresses, device identifiers and timing rather than as proof on their own.

Frequently Asked Questions

Can a User-Agent be faked?
Yes. Any client can send any User-Agent string, so use it only as supporting evidence.
Is the string sent anywhere?
No. Parsing is done in your browser.

More free tools: Hash · Base64 · Password · CIDR · JWT · Regex · Epoch · Hex · URL · UPI ID · IFSC · GSTIN

Why Investigators Use Browser-Based Forensic Tools

Every utility on this page runs entirely inside your browser. Nothing you paste — no hash, no token, no extract of evidence — is ever uploaded to a server. For an investigator handling sensitive or legally protected material, that distinction matters: client-side processing preserves the integrity of the artefact, avoids exposing case data to a third party, and supports the compartmentalisation that operational security demands.

When each tool fits an investigation

Cryptographic hashing (MD5, SHA-1, SHA-256, SHA-512) is used to verify that a seized file has not changed and to match a sample against known-good or known-bad reference sets. Base64 and hex decoders unwrap obfuscated payloads, configuration strings, and email attachments. The CIDR calculator scopes a network range when you are mapping an organisation’s address space. The JWT decoder exposes the claims inside a session token during application analysis. The regex extractor — tuned for Indian identifiers such as Aadhaar, PAN, IFSC, and mobile numbers — pulls structured entities out of bulk text for identification or redaction, and the epoch converter aligns log timestamps when reconstructing a timeline.

A note on evidence handling

Record the hash values you generate directly in your case notes; a documented hash is the simplest way to prove later that an exhibit is unaltered. Because these tools never transmit data, they are well suited to work that must remain on a single controlled device. Where your findings may support an FIR or court submission, pair them with a certificate under Section 63 of the Bharatiya Sakshya Adhiniyam, 2023, which governs the admissibility of electronic evidence in India.

Worked example

A string containing Android 14, Mobile and Chrome/1xx indicates Chrome on an Android 14 phone; one with Windows NT 10.0 indicates Windows 10 or 11, because Windows 11 still reports itself as NT 10.0. Automation tools often leave tell-tale strings such as HeadlessChrome, python-requests or curl.

Good practice

Frequently asked questions

Where do I find a user-agent string?

In web server and application logs, in platform responses to legal notices, and in your own browser's developer tools under the network tab.

Can a user-agent reveal the exact phone model?

Sometimes. Some Android browsers include the model code in the string, but many now reduce or freeze the user-agent to protect privacy, so the model may be missing.

▸ RELATED READING
Password Security in 2026 →Email Header Analysis for Investigations →OSINT: Phone Number Investigation →