See an IP address in every form at once.

Paste an IP address in any common form — dotted decimal (192.168.1.10), an integer (3232235786), hexadecimal with or without the 0x prefix, binary, or an IPv6 literal (2001:db8::1) — and it shows every other representation at once, plus the PTR name and the address type. A bulk mode converts a whole list, one address per line. Everything is computed in your browser.

No. Detection and conversion run 100% client-side in your tab. There is no server, no account and no logging, so internal and private addresses are safe to paste.

A value with colons is read as an IPv6 literal; a 0x-prefixed value as hexadecimal (more than 8 hex digits means IPv6); bare hexadecimal without the 0x is accepted when it is exactly 8 or 32 digits and contains at least one letter; a string of 0s and 1s totalling 32 or 128 bits is binary, with dots, colons, underscores or spaces allowed as separators; a plain run of digits is an integer; and a dotted value is IPv4. A %zone suffix is stripped and shown as its own row, and a /prefix is ignored with a warning. You do not pick the format — the converter infers it and tells you what it read.

An IPv4 address is a 32-bit unsigned integer. The decimal value is octet1 x 256^3 + octet2 x 256^2 + octet3 x 256 + octet4, so 192.168.1.10 becomes 3232235786. Paste the dotted address into the converter and it computes the integer instantly using exact BigInt arithmetic.

An integer takes 4 bytes versus up to 15 for a dotted string and makes sorting and range or CIDR checks simple numeric comparisons — which is why GeoIP tables and allow/deny lists store IPs as integers. The converter moves between the integer and dotted forms exactly, removing the risk of hand-calculation errors.

Each octet becomes a two-digit hex value, concatenated and 0x-prefixed, so 192.168.1.10 is 0xC0A8010A. The tool always outputs zero-padded hex — 8 digits for IPv4 and 32 for IPv6 — and accepts bare hex without the 0x when it is exactly 8 or 32 digits. For IPv4 it also shows the byte-swapped form (0x0A01A8C0) that little-endian sources such as /proc/net/tcp print.

Yes. IPv6 is converted with full 128-bit precision: you get the RFC 5952 compressed form, the fully expanded form, the decimal integer and the padded 32-digit hexadecimal. Embedded IPv4 (for example ::ffff:192.168.1.1) is parsed too.

Reverse DNS stores the hostname for an address under a special domain: IPv4 octets are reversed under in-addr.arpa (192.168.1.10 becomes 10.1.168.192.in-addr.arpa) and IPv6 nibbles are reversed under ip6.arpa. The converter derives the PTR name for every address; to build the matching PTR record and reverse zone, open the Reverse DNS / PTR Helper.

Each of the four octets is written as an 8-bit binary number, giving 192.168.1.10 as 11000000.10101000.00000001.00001010. The converter accepts binary back too — with or without the dot separators — so its own output round-trips, and IPv6 addresses get a colon-grouped 128-bit binary view.

Browsers and operating systems accept an IPv4 address written as its raw integer or as hex, so http://3232235786 and http://0xC0A8010A both resolve to 192.168.1.10. This is useful for testing and explains why these alternate forms appear in logs and security scans. The converter lets you move quickly between the forms without manual arithmetic.