IP Parser
Parse, validate, and analyze IPv4 and IPv6 addresses — CIDR calculator, classification, conversions, batch mode, all local to your browser.
Loading tool…
What is an IP address?
An IP address identifies a network interface. IPv4 addresses are 32 bits written as four decimal octets, giving about 4.3 billion possibilities — long since exhausted, which is why IPv6 exists with 128 bits written as eight hexadecimal groups, usually abbreviated with a double colon where a run of zeros is omitted.
Addresses are rarely used alone. CIDR notation appends a prefix length, so 192.168.1.0/24 means the first 24 bits are the network and the remaining 8 identify hosts — 256 addresses, of which 254 are usable. Certain ranges are reserved and never routed on the public internet: 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 for private networks, plus loopback and link-local ranges. Parsing an address means resolving all of this into readable facts: the network and broadcast addresses, the usable host range, and whether the address is public or private.
Why we built this tool
Network work needs this arithmetic constantly — planning subnets, writing firewall rules and security-group entries, reading server logs, and diagnosing why two machines cannot see each other.
The addresses involved describe your internal network topology, which is precisely the information an attacker would like to have. Sending it to a third-party calculator to do binary maths is an unnecessary leak. Ours computes everything in your browser with plain JavaScript, so the addresses never leave your machine and nothing is logged. It also works offline — genuinely useful when you are configuring a network that has no working internet connection yet.
Tips and common mistakes
- A
/24holds 256 addresses but only 254 usable hosts, once the network and broadcast addresses are excluded. - Private ranges are never routed on the public internet, so a public-looking problem may just be a private address.
- Plan subnets with room to grow; renumbering a live network later is far more work than allocating generously now.
- IPv6 abbreviation with a double colon may appear only once in an address.
Open IP Parser with a link
IP Parser can be handed its input by the link that opens it, so the page arrives with the work already done. This is meant for assistants and scripts: if a chatbot, an editor extension, or a command-line agent already holds your content, it can build a link instead of asking you to copy and paste into a box.
The payload rides in the fragment — the part of a URL after the #. Browsers never send the fragment to a server, so anything handed over this way stays on your device exactly as a dropped file would. A link that uses the query string instead is rewritten into the fragment by the page before any analytics or ad script can read the address.
Prefix any field with gz — #gztext= — to pass it as gzip-compressed base64url, which fits roughly five to ten times more into the same link. Links stay reliable up to about 8,000 characters; past that, chat apps and address bars start truncating them, and the page says so rather than loading half a document.
One exception to the privacy rule: ?url= tells the page to download the input from an address. That request goes from your browser straight to that server — not through ours — but it does leave your device, and it only works if the server allows cross-origin requests.
#text=— the text to work on
Example: https://mygadgets.ink/tools/ip-parser/#text=...
Quick start: using IP Parser
- Enter an IP address, with a CIDR prefix if you have one.
- Read the parsed output: version, network address, and prefix length.
- Check the usable host range and total address count for the subnet.
- Note whether the address falls in a private, loopback, or reserved range.
- Copy the values into your firewall rule, route table, or documentation.
Working on URLs rather than addresses? URL Parser breaks those apart the same way.