Subnet calculator:
the mask is the seam.
Type 192.168.1.0/24, a dotted netmask, or an IPv6 prefix and get the whole picture: network and broadcast, first and last usable host, the mask in every notation, class and scope, the seam in binary, splits, and a real VLSM planner. One tool for both address families — and the maths never leaves this tab.
The seam lands mid-octet.
203.0.113.64/26 runs from 203.0.113.65 to 203.0.113.126: 62 usable addresses out of 64. 203.0.113.64 names the block and 203.0.113.127 calls everyone in it, which is the famous −2.
The seam, in binary
bit 26 of 32The subnet
The mask, in every form
same seam, five spellingsAround this subnet
grow it · split itIt travels only if you copy it and send it — opening it is the one thing that does reach our access log. What you type in the box never enters the address bar.
What we computed
arithmetic, not discoveryCopy as text
Subnet: 203.0.113.64/26 Netmask: 255.255.255.192 = /26 Wildcard: 0.0.0.63 Network: 203.0.113.64 Broadcast: 203.0.113.127 HostMin: 203.0.113.65 HostMax: 203.0.113.126 Hosts: 62 usable of 64 Class: C (historic) · Documentation (TEST-NET-3) -- calculated at status.uptimia-dev.ovh/subnet-calculator
One number, four consequences.
Most calculators make you pick a page — IPv4 here, IPv6 elsewhere. Addresses stopped working like that years ago, so this one takes either.
Where the network ends
The network address and the broadcast are not configured anywhere — they fall out of the seam. All host bits zero names the block; all host bits one calls everyone in it.
network · broadcastHow many devices fit
Host bits set the size: 232−n addresses, minus the two the block spends on itself. The famous −2 — and the /31 and /32 exceptions where it does not apply.
2^(32−n) − 2Who needs a router
Two hosts compare networks with one AND. Same result and they talk directly; different and everything goes via the gateway. A wrong mask here is why two machines on the same wire cannot see each other.
the AND testHow to grow
Every block splits into two halves, four quarters — or unequal pieces sized to real needs. That is VLSM, and it is the difference between fitting and buying more space.
split · right-sizeSix subnet mistakes people keep making
Much of subnetting folklore is a habit from 1993. What the numbers actually mean.
"No usable hosts"? Not since RFC 3021: on a link with exactly two ends, both addresses are usable. No network address, no broadcast, nothing wasted. The old habit says /30 and burns half of it.
Inside a /20, yes, and a perfectly normal one. Broadcast means all host bits set, which only the top address of the whole block has. Ending in .255 means nothing without the mask.
Not a mask. Mask bits have to be contiguous — ones, then zeros, no gaps. This tool rejects it, and so does essentially all real equipment. If a config accepts it, worry.
It is not. RFC 1918's middle range is 172.16.0.0/12, which ends at 172.31.255.255. 172.32.x.x belongs to someone on the public internet — and one day your traffic will find them.
The mask, inverted — Cisco ACL notation, where 0 means "must match" and 1 means "don't care". Same /26 boundary, opposite spelling. We print both, and accept either as input.
Classes stopped mattering in 1993 when CIDR shipped. 10.0.0.0/8 is "class A" only in exam questions — what routes is the prefix length, nothing else. We print the class because interviews still ask.
IPv4 counts hosts, IPv6 counts networks
The mental model flips between families, which is exactly why a calculator that takes both in one box beats two separate pages.
- IPv4 — "how many devices fit?" Total, minus two, watch the seam. Scarcity thinking, because v4 is scarce.
- IPv6 — "how many /64 LANs do I get?" A /64 is the standard LAN and hosts inside one are effectively unlimited. Nobody counts them; count subnets.
- VLSM — when equal splits do not fit, size each subnet to its real need, largest first. The planner does the alignment for you.
What the maths can and cannot prove
the no-overclaim tableFour things most calculators leave out.
Subnet maths is exact — but some of what tools print around it is convention, history, or marketing.
Classes are history
Address classes stopped mattering in 1993, when CIDR shipped. We print the class because exams and old configs still ask — routing has not looked at it in thirty years.
post-1993 world−2 is a convention
The usable-hosts subtraction is IPv4 custom with real exceptions: /31 links (RFC 3021) use both addresses, /32 is a host route, and IPv6 dropped the idea entirely. We label the exceptions instead of hiding them.
convention ≠ physicsMaths, not discovery
Nothing here proves what is deployed. The numbers are exact; your network is whatever someone configured. A calculator that implies otherwise is selling something.
exact ≠ deployedNothing leaves this tab
Parsing, maths, VLSM — all of it runs in your browser. Calculating makes no request, and what you type is never logged or written into the address bar. Check the network tab.
0 requestsThe same maths, from your shell
Every number on this page is reproducible in one command. We just draw the seam. There is deliberately no API here — an endpoint would be a reason to send us your addressing, and these do not phone home either.
The subnets people actually look up
Worked answers for the blocks that turn up in real networks, each with a note on why it matters.
Common subnet calculator questions
Every IPv4 subnet spends its lowest address as the network identifier: all host bits zero, the name routing tables use. It spends its highest as the broadcast: all host bits one, which addresses everyone in the block at once. Neither can be assigned to a device, so a /24's 256 addresses yield 254 usable. Two exceptions are worth knowing. A /31 point-to-point link (RFC 3021) has no broadcast and uses both addresses; a /32 is a single-host route. IPv6 dropped the whole scheme — there is no broadcast address to subtract.
No. RFC 1918 defines exactly three private ranges: 10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16. The /12 is the trap: it covers 172.16.0.0 through 172.31.255.255 only. 172.32.x.x is public address space that belongs to someone else, and traffic you meant to keep internal will eventually route toward them. The calculator prints the scope for every address, so this shows up before deployment rather than after.
A wildcard mask is the subnet mask with every bit flipped: a /26's mask 255.255.255.192 becomes wildcard 0.0.0.63. Cisco access-control lists and OSPF network statements use this inverted spelling: 0 means "this bit must match", 1 means "don't care". It describes the same boundary as the mask, from the opposite direction. We print both, and you can paste either into the box above.
Variable-Length Subnet Masking gives each network the smallest block that fits, instead of splitting the parent into equal pieces. A 500-host department gets a /23, a point-to-point link gets a /30, and both live in the same /22. The largest-first rule is about alignment: a block can only start on a multiple of its own size (a /23 on a 512 boundary, a /24 on 256). Allocate big to small and every block lands exactly where the previous one ended, gap-free. Allocate small to big and the later large blocks must skip ahead to their next legal boundary, stranding addresses in between. The planner does the sorting and the alignment and shows what is left over.
Because SLAAC is specified to work with a 64-bit interface identifier, full stop. SLAAC is the mechanism that lets IPv6 hosts configure their own addresses without a DHCP server. Make the subnet smaller and autoconfiguration breaks. So the practical unit of IPv6 planning is the /64 LAN. An allocation is measured in how many /64s it cuts into: a /56 gives 256, a /48 gives 65,536. The exceptions are deliberate: /127s on router-to-router links (RFC 6164) and /128 loopbacks — places where no host will ever autoconfigure.
Not to any router built in the last three decades. Classes (A/B/C by the first bits of the address) were how space was allocated before 1993, and they wasted it badly. The smallest classful unit an organisation could get was a /24, and the next step up was a /16. CIDR replaced the whole scheme with explicit prefix lengths, which is what every routing table uses today. We still print the class because certification exams, interview questions and thirty-year-old configs keep the vocabulary alive — but nothing about how your traffic moves depends on it.
Nowhere. The parser and all the maths run as JavaScript in your browser, so calculating makes zero network requests. Confirm it in your browser's network tab. Your internal addressing is exactly what should not be pasted into a random web tool, so this one never receives it. What you type is never written into the URL either, because a URL carrying your addressing would reach our access log through the Referer header the moment you clicked a link. And there is no JSON API, because an endpoint would be a standing invitation to send it to us. The shareable link under each result is assembled locally and only travels if you copy it.
Free tools are just the start.
Uptimia keeps your sites healthy.
Uptime, SSL, domain expiry, page speed, transactions — monitored from 171+ locations worldwide. Free for 30 days.