Overview
Enter an IPv4 address in dotted-decimal form and see each of its four octets converted to base-8 (octal) individually - for example, 192.168.1.1 becomes 300.250.1.1 in octal, octet by octet. This mirrors an older but still-encountered IP notation convention: some systems and historical Unix tools accept or display IPv4 octets in octal, and a leading zero on a number (like 010) is sometimes misinterpreted as octal rather than decimal by parsers that follow C-style number literal rules, which is a real source of IP-parsing bugs and even a known SSRF/validation-bypass technique. The IPv4 address is validated with the same rules used across this site's other IP tools - exactly four dot-separated octets, each 0-255, no leading or trailing dots. Runs entirely client-side.
Best for: Understanding how an IP address parser might misread a leading-zero octet as octal
How to use this tool
- Enter an IPv4 address. Standard dotted-decimal form, like 192.168.1.1.
- The address is validated. Exactly four octets, each 0-255 - anything else produces a specific error message.
- See each octet in octal. Every octet is converted to base-8 individually and shown alongside its decimal value.
Frequently asked questions
Some legacy tools and parsers that follow C-style numeric literal rules treat a number with a leading zero (like 010) as octal rather than decimal, which means an IP address like 192.168.0.010 could be silently parsed as a different address than expected. This has historically been exploited as a validation-bypass or SSRF technique against systems that don't normalize IP octets consistently, so understanding the octal equivalent of an address is useful for security review as much as for working with genuinely octal-based legacy systems.
No - that's the octal representation of 192.168.1.1's octets, not a second valid dotted-decimal address. Octal digits only use 0-7, so "300" in octal equals 192 in decimal (3×64 + 0×8 + 0), and it isn't meant to be typed back into a normal IPv4 field as if it were decimal.
Anything that isn't a well-formed IPv4 address: fewer or more than four octets, a non-numeric octet, an octet outside 0-255 (like 256), or leading/trailing dots. Each of these produces a clear error rather than a partial or incorrect conversion.