IP Tools
Convert an IPv4 address to integer, hex and binary, and identify private, loopback or public ranges.
Dotted decimal
Unsigned 32-bit integer
Hexadecimal
Binary (per octet)
Address type:
| CIDR | Subnet mask | Usable hosts |
|---|---|---|
| /8 | 255.0.0.0 | 16,777,214 |
| /12 | 255.240.0.0 | 1,048,574 |
| /16 | 255.255.0.0 | 65,534 |
| /20 | 255.255.240.0 | 4,094 |
| /22 | 255.255.252.0 | 1,022 |
| /23 | 255.255.254.0 | 510 |
| /24 | 255.255.255.0 | 254 |
| /25 | 255.255.255.128 | 126 |
| /26 | 255.255.255.192 | 62 |
| /27 | 255.255.255.224 | 30 |
| /28 | 255.255.255.240 | 14 |
| /29 | 255.255.255.248 | 6 |
| /30 | 255.255.255.252 | 2 |
| /31 | 255.255.255.254 | 2 |
| /32 | 255.255.255.255 | 1 |
/31 and /32 are point-to-point and single-host prefixes (RFC 3021) — the usual “minus 2” rule does not apply.
How to use it
- Type an IPv4 address such as
192.168.1.10— strictly four dot-separated numbers from 0 to 255. - The four representation cards update as you type: dotted decimal, unsigned 32-bit integer, hexadecimal and binary.
- Below the cards, the address type is classified using a built-in range table.
- The second panel is a static reference of common CIDR prefixes, masks and usable host counts.
- Invalid input shows a clear error; the previous results stay untouched.
Common use cases
- Reading firewall logs — converting an integer like
3232235786back into a readable address. - Configuring access rules — confirming whether an address is RFC 1918 private, loopback or public.
- Learning networking — seeing the same address in binary to understand masks and prefixes.
- Checking documentation — using the prefix table to look up
/22,/26masks and host counts.
Why it stays private
All conversions are bit operations in your browser; nothing is looked up online and no address is stored.
FAQ
Q: Does it accept IPv6? A: No — this tool is IPv4 only. IPv6 has different notation and ranges that would not fit the four cards.
Q: Why is 192.0.2.1 not called public? A: The built-in table classifies the major ranges from RFC 791, RFC 1918, RFC 6598 and multicast. Some small special-purpose blocks (such as TEST-NET documentation ranges) are not separately labelled, so a few unusual addresses may show as public.
Q: Are zero-padded octets like 010.1.1.1 accepted? A: No. Zero-padded forms are ambiguous across systems (some treat them as octal), so they are rejected with an error message.
Your data stays on this device
IP Tools runs 100% locally. Everything you paste or drop is processed by your own browser and never transmitted. Nothing is stored on our servers — close the tab and it is gone.
Nothing you type is sent to a server, logged, or used for analytics. The page works even with your network disconnected after first load.