IP Address Converter

IP Address Number Systems

An IPv4 address is fundamentally a 32-bit unsigned integer. The familiar dotted-decimal notation (like 192.168.1.1) is just one way to represent that number — chosen for human readability. The same address can be represented in binary, hexadecimal, octal, or as a plain decimal integer, all with the same underlying value. Understanding these representations is essential for network programming, low-level packet analysis, and working with routing tables and firewall rules.

Decimal representation: 192.168.1.1 in dotted notation converts to the integer 3,232,235,777. This single 32-bit integer form is used in some network APIs and programming contexts where the dotted notation would require parsing. Network masks are often applied using bitwise AND operations on these integer representations.

Binary and Hexadecimal IP Representations

Binary representation exposes the underlying bit structure of IP addresses, which is essential for understanding subnet masks and CIDR notation. The IPv4 address 192.168.1.1 in binary is:11000000.10101000.00000001.00000001. Each octet is an 8-bit binary number between 0 (00000000) and 255 (11111111).

When you apply a /24 subnet mask, you are saying the first 24 bits (the first three octets) identify the network, and the remaining 8 bits identify the host. In binary, the subnet mask 255.255.255.0 is11111111.11111111.11111111.00000000. Performing a bitwise AND between the IP address and the subnet mask gives the network address — this is the fundamental operation of IP routing.

Hexadecimal representation is commonly used in network programming, packet captures (Wireshark displays IPs in hex in packet details), and some routing protocol configurations. The address 192.168.1.1 in hex is C0.A8.01.01 or written as a single hex value 0xC0A80101. MAC addresses are always displayed in hex, and working with both IP and MAC addresses in the same context makes hex the natural common format.

IPv6 and the Address Space Challenge

IPv4's 32-bit address space provides only 4.29 billion unique addresses — far fewer than the number of internet-connected devices today. IPv6 was designed to solve this exhaustion. IPv6 uses 128-bit addresses, providing 340 undecillion (3.4 × 10³⁸) unique addresses — enough to assign billions of addresses to every atom on the surface of the Earth.

IPv6 addresses are written in hexadecimal groups separated by colons (e.g., 2001:0db8:85a3:0000:0000:8a2e:0370:7334). Leading zeros in each group can be omitted, and one consecutive sequence of all-zero groups can be replaced with:: (e.g., 2001:db8::1). Our converter handles IPv6 address formatting and normalization, useful when comparing addresses from different sources that may use different abbreviation conventions.

Network engineers and security professionals encounter multiple IP address formats daily — in logs, routing tables, firewall rules, scripts, and network diagrams. Quickly converting between these formats eliminates manual calculation errors and speeds up analysis workflows significantly.

Octal Representation and Practical Applications

Octal (base-8) IP representation is less common but appears in certain Unix and Linux contexts. An IP address in octal format uses the prefix 0 before each octet (e.g., 192.168.1.1 becomes 0300.0250.01.01). Historically, some Unix network configuration tools interpreted IP addresses with leading zeros as octal, which caused subtle bugs when addresses like 010.0.0.1 (meaning 8.0.0.1 in octal, not 10.0.0.1 in decimal) were used. Modern systems typically treat all octets as decimal regardless of leading zeros, but awareness of octal notation remains important for legacy system administration and security research.

Converting between IP address formats is also important in penetration testing and security research. Web application firewalls and input validation routines sometimes block IP addresses in decimal but fail to account for equivalent binary, hex, or integer representations. Security researchers use alternate IP notations to test whether validation logic covers all representations of the same address. For example, the decimal integer 2130706433, the hex 0x7F000001, and the dotted-decimal 127.0.0.1 all refer to the loopback address, but naive string-based filters may only block one form.

For developers working with network programming in languages like Python, JavaScript, or C, the ability to convert IP addresses between representations is a fundamental skill. Socket libraries commonly require IP addresses as 32-bit integers in network byte order (big-endian). Our IP converter handles all these conversions instantly, making it a practical daily-use tool for anyone working at the network layer.