IPv4 Converter

Convert an IPv4 address between dotted decimal, unsigned integer, hexadecimal, and 32-bit binary representations.

What IPv4 Converter helps you do

Convert an IPv4 address between dotted decimal, unsigned integer, hexadecimal and 32-bit binary representations. Different systems store addresses in different forms, and this moves between them instantly. The hex output uses a 0x prefix and eight uppercase digits, while the binary output is grouped into four octets separated by dots.

Conversion runs entirely in your browser. No addresses are sent to Haivix.

How it works

Most tools here are offline calculators: the address math, RAID capacity, permission bits, TCP window sizing and transfer-time estimate all run in your browser with no request. The RDAP lookup is the exception, because registration data lives in public registries and the domain must be sent to a lookup service. Unit conventions matter throughout: a megabyte may mean 1,000,000 or 1,048,576 bytes, and a megabit is always one eighth of a megabyte. These are reference models, not live checks, so a port can be listed without a service running, a permission mode can be valid without being appropriate, and a RAID estimate can differ from formatted capacity.

How to use IPv4 Converter

  1. Enter an address in any supported notation.
  2. Run the conversion and check the rounded-trip value.
  3. Read the equivalent in the other three forms.
  4. Copy the representation your system expects.

When to use it

  • Find the integer form of an IP for a database or API.
  • Read a hexadecimal IP from a log or a hex dump.
  • Check the binary form of an address or subnet boundary.
  • Convert an address for a bitmask calculation.
  • Verify that two notations refer to the same host.
  • Prepare a value for a firewall or routing rule.

When not to use it

  • Do not use it for IPv6 addresses; only 32-bit IPv4 is handled.
  • Do not expect prefix or subnet calculations; use the subnet calculator for that.
  • Do not assume a bare integer input is always decimal; leading zeros and format matter.

Example

The address 192.168.1.10 is 3232235786 as an unsigned integer, 0xC0A8010A in hexadecimal and 11000000.10101000.00000001.00001010 in binary. The binary groups are separated by dots for readability, not by spaces. A decimal input above 4,294,967,295 is rejected.

What you can do with IPv4 Converter

  • Accept dotted decimal, decimal integer, 0x hex or 32-bit binary.
  • Show all four representations at once.
  • Pad hex and binary to their full width.
  • Reject values outside the 32-bit range.
  • Copy every representation in one go.
  • Run the conversion locally in the browser.

Example: check the model against the live system

Note the unit convention before comparing figures. Mbps and MB/s differ by a factor of eight, and MB and MiB differ by about 5 percent.

Treat a lookup as a starting point. A port reference, a permission mode and a RAID calculation all describe expectations, not the state of a running host.

Confirm on the system itself where it matters: ss or netstat for listeners, ls -l for permissions, the controller utility for array status.

Keep RAID in perspective. It protects against a disk failure, not against deletion, corruption, ransomware or a lost site.

Record the inputs alongside the result so a later comparison uses the same assumptions.

Check the time unit on latency. A round-trip time is usually milliseconds, and entering seconds changes the bandwidth-delay product by a factor of a thousand.

Treat registry data as a snapshot. RDAP records can be redacted, cached or updated after a transfer, so confirm ownership and expiry with the registrar.

What to know before you start

  • It handles IPv4 only and not IPv6 addresses.
  • It shows a single address and does not compute subnet ranges.
  • Binary groups are dot-separated rather than a plain 32-character string.
  • It does not validate whether an address is public, private or reserved.

Common mistakes

  • Pasting a hex value without the 0x prefix.
  • Expecting the binary output to be a continuous 32-digit string.
  • Using an address with a port suffix such as :443.
  • Assuming the tool also computes the network address.

Troubleshooting

If the value is rejected, check for a valid octet count or an out-of-range integer.

If the hex looks short, leading zeros may have been dropped in the source.

If the dotted form is wrong, the input may have been read in the wrong base.

If a binary input fails, confirm it has exactly 32 bits.

Related standards and documentation

  • RFC 791 defines IPv4 addressing and packet format.
  • RFC 9293 defines TCP, including the receive window and its scale option.
  • IANA maintains the Service Name and Transport Protocol Port Number Registry.
  • POSIX and the Single UNIX Specification define the permission bits behind chmod.
  • RFC 9082 and RFC 9083 define the RDAP query and response formats.
  • IEEE 802.3 defines the Ethernet frame sizes behind the common 1500-byte MTU.
Models, not monitors
  • Check bits versus bytes.
  • Verify on the host.
  • RAID is not backup.
  • Keep the inputs.