User agent and IP inspector

User agent parses the string your browser sends (or any you paste) into browser and version, rendering engine, operating system, and device type. It recognises the common crawlers and bots. The samples cover desktop, mobile, embedded, and bot strings. User-Agent strings are frozen and unreliable: Chrome reports a fixed Windows NT 10.0 and Android K version, and macOS has reported 10_15_7 since Big Sur. The notes explain which parts to trust.

Client hints reads navigator.userAgentData and, on request, its high-entropy values: full version list, platform version, architecture, bitness, and model. This is the replacement for User-Agent parsing in Chromium browsers. Firefox and Safari do not implement it, and the tab says so.

IP converter accepts the forms inet_aton accepts — 192.168.1.1, 3232235777, 0xC0A80101, 0300.0250.1.1, and short forms such as 127.1 — and shows decimal, hex, octal, binary, IPv4-mapped IPv6, 6to4, NAT64, and the in-addr.arpa name. Those odd forms are why URL filters that only compare dotted strings are bypassable. IPv6 addresses are expanded and compressed to the RFC 5952 canonical form. The converter also shows the ip6.arpa name, the address type (loopback, link-local, ULA, multicast, documentation), and any embedded IPv4 address (mapped, NAT64 64:ff9b::/96, 6to4, or Teredo). Zone IDs such as fe80::1%eth0 are kept.

Nothing is sent anywhere; your own IP address is not shown because finding it would need a server.