IP Utility

IP Address Converter

Back to Toolkit

Input IP Address

Enter an IPv4 address to see its different representations.

Binary (Dotted)

11000000.10101000.00000001.00000001

Decimal (Long)

3232235777

Hexadecimal

0xC0.0xA8.0x01.0x01

Octal

0300.0250.01.01

Regex Generator

Generated pattern for strict validation including CIDR & Port.

^(?:(?:25[0-5]|2[0-4][0-9]|1[0-9][0-9]|[1-9]?[0-9])\.){3}(?:25[0-5]|2[0-4][0-9]|1[0-9][0-9]|[1-9]?[0-9])(?::[0-9]{1,5})?(?:/(?:3[0-2]|[12]?[0-9]))?$

This pattern validates CIDR prefixes (0-32) and port numbers (1-65535). Use it in languages like JavaScript, Python, or Java for robust string validation.

Did You Know?

Dotted-Octal IPs: Linux tools sometimes accept IPs in octal format (e.g., 0300.0250.001.001), but this is often considered a security risk as it can bypass some simple filtering systems.

Hex IPs: Some browsers will resolve dotted-hex IP addresses like 0xC0.0xA8.0x01.0x01 just as they would decimal ones.

Was this tool helpful?

About the IP Format Converter

An IPv4 address is just a 32-bit integer wearing dotted-decimal clothing. This converter translates between the representations you actually meet in the wild: dotted decimal (192.168.1.1), pure decimal (3232235777), binary (for subnetting work), hex (packet dumps and PCAP analysis), and octal.

The conversions are routine until they are security-relevant: URL parsers accept decimal and hex IP forms, log pipelines store integers, and firewall bypass attempts exploit exactly these alternate encodings — being fluent in them is part of reading network data correctly.

Frequently asked questions

Why would an IP appear as a plain number like 3232235777?

Databases and log systems often store IPv4 as a 32-bit integer for compact indexing and range queries (network containment becomes a BETWEEN). 3232235777 is 192.168.1.1: each octet contributes its value × 256 raised to its position. GeoIP databases and netflow records use the same representation.

How are alternate IP formats used to bypass security filters?

A filter blocking the string "169.254.169.254" (the cloud metadata endpoint) can be bypassed with its decimal (2852039166), hex (0xa9fea9fe), or mixed forms — most URL parsers accept all of them. This is a standard SSRF technique, and it is why allowlists must compare parsed addresses, never raw strings.

Why does binary representation matter for subnetting?

Subnet operations are bitwise: the network address is IP AND mask, broadcast is IP OR wildcard, and "is this IP in that CIDR" is a prefix comparison. Seeing addresses in binary makes visible why a /26 boundary falls at .64 and why 10.0.0.0/22 contains 10.0.2.5 — facts that dotted decimal actively obscures.

Need this managed for you, not just automated?

We're also a hands-on DevOps consultancy — Kubernetes, CI/CD, and cloud infrastructure.

Explore Our Services