IPv4 Address to Integer
Example
Input:
192.168.0.1
Output:
3232235521
About this converter
An IPv4 address is four bytes wearing a dotted costume; as an integer it is just those bytes in order — which is why databases store IPs as INT UNSIGNED (fast comparisons, natural range queries: "all addresses between X and Y" becomes BETWEEN on one column) and why GeoIP lookups are range tables. This converter validates each octet (0–255, no leading-zero tricks — some parsers read 010 as octal, an ambiguity behind real SSRF bugs; this one reads decimal and says so). IPv6 has no single-integer convention in everyday tooling and is out of scope here.
Frequently Asked Questions
Why store IPs as integers?
Comparison, sorting and range queries become single-number operations, and indexes work on one compact column.
Is 192.168.001.1 valid here?
It is read as decimal octets (1), but beware: other systems read leading zeros as octal — a classic parser-difference security bug.