IP and network calculations
Is this large log integer an IP address?
Tools to use
A log or database column may contain a large integer rather than a dotted IP address. It could be a device identifier, or an IPv4 address stored as a 32-bit value. IP Integer Converter checks the representation locally, without querying a network. First establish the column's meaning: not every large integer is an address.
Decode an IPv4 integer and check the reverse
3221225994
192.0.2.10
0xc000020aSelect IPv4 for numeric input and enter 3221225994. The result is 192.0.2.10. Enter that address to obtain integer 3221225994 and hexadecimal 0xc000020a; the prefixed hex also converts back. Matching the original integer checks that this conversion preserved its digits.
These are calculation examples, not checks of a live host or owner. Producing a plausible address does not prove it was the actual client address. Confirm the field's origin and encoding with the system that produced the log.
Read the octets as base-256 positions
192 × 256³ + 0 × 256² + 2 × 256 + 10
= 3221225994
bytes: c0 00 02 0aEach IPv4 octet is one byte from 0 to 255. The converter places the leftmost octet in the highest position. It does not concatenate the strings into 1920210. In hex, two digits per byte make c0, 00, 02 and 0a easy to match with the four original octets.
Do not assume a proprietary packed format or an undelimited shorthand follows this convention. Establish whether the source is an unsigned integer, four bytes or text before interpreting a successful conversion. Knowing the source type separates representation mistakes from arithmetic mistakes.
The integer 1 does not identify an address family
1 → 0.0.0.1 (IPv4)
1 → ::1 (IPv6)
4294967295 → 255.255.255.255 (IPv4)Decoding requires an address family. Integer 1 becomes 0.0.0.1 for IPv4 and ::1 for IPv6. Guessing IPv6 only when a number is large misreads small IPv6 values. Preserve any family field in the source; the integer alone cannot restore lost metadata.
IPv4 stops at 4294967295, so 4294967296 is rejected for that family. IPv6 uses 128 bits; routing its integer through floating-point software can lose low digits. Transfer the decimal digits as exact text and round-trip them, rather than substituting a rounded scientific-notation display.
A plausible but wrong address may indicate byte order
c0 00 02 0a → 192.0.2.10
0a 02 00 c0 → 10.2.0.192
0x0a0200c0 = 167903424For raw memory or binary files, stored byte order matters. Reversing the same four bytes produces a different IP. The converter does not detect the original order. Verify the producing program's specification or a known record instead of swapping until the result looks plausible.
A negative IPv4 log value can result from signed 32-bit interpretation, but this tool does not automatically correct negatives. Resolve signedness only after confirming the source type. A negative value might instead be an error code; do not force every value into an address.
Conversion is not a connectivity test
After decoding, use IP/CIDR Comparison if you need to test range membership. Neither tool queries DNS, connects to ports or infers location. Valid representation, range membership and real reachability are different checks.
Record the original integer, address family, decoded form and reverse-check result. Mark unknown byte order or signedness as unknown. A readable address helps compare logs, but its appearance must not fill gaps in the source definition.