IP Subnet Calculator — CIDR & Subnet Mask Tool

What Is an IP Subnet Calculator?

An IP subnet calculator is a tool that takes an IPv4 address plus a prefix length (CIDR notation or a dotted subnet mask) and computes every derived value a network engineer needs: the network address, the broadcast address, the usable range of host addresses, the wildcard mask, and how many total and usable addresses the block contains. It automates arithmetic that's entirely mechanical but tedious and error-prone to do by hand — binary math on 32-bit numbers, bit borrowing, and boundary alignment — the same skills tested on the CCNA exam and used daily by network engineers, DevOps teams, and cloud architects.

What Is an IPv4 Address?

An IPv4 address is a 32-bit number that uniquely identifies a device on a network, conventionally written as four decimal numbers from 0–255 separated by dots — 192.168.1.1, for example. Each of those four numbers, called an octet, represents 8 bits, so the full address is really just a 32-digit binary number split into readable chunks. Because it's only 32 bits, IPv4 provides roughly 4.3 billion possible addresses — a number that felt enormous in 1981 and has been under pressure ever since the public internet scaled past it, which is part of why private addressing (RFC 1918), NAT, and eventually IPv6 all exist.

What Is CIDR?

CIDR (Classless Inter-Domain Routing), introduced in 1993 by RFC 1518/1519, replaced the original rigid "classful" addressing scheme with a flexible notation: an IP address followed by a slash and a number, like 192.168.1.0/24, where the number states how many of the 32 bits form the network portion. This single change let network designers create subnets of any size instead of being locked into fixed Class A/B/C boundaries, and it's the reason the internet's routing tables didn't collapse under their own growth in the 1990s.

What Is a Subnet Mask?

A subnet mask expresses the exact same information as a CIDR prefix, just in dotted-decimal form: 255.255.255.0 is mathematically identical to /24. Both describe a 32-bit pattern of contiguous 1s (network bits) followed by contiguous 0s (host bits) — a subnet mask is only valid if its binary form never has a 0 followed later by a 1. This calculator accepts either format and treats them as fully interchangeable.

How Subnetting Works

Subnetting works by "borrowing" bits from the host portion of an address and reassigning them to the network portion, which shrinks each individual subnet's size but creates more of them. Borrowing one bit from a /24 doubles the number of subnets (to 2) while halving each one's size (to /25, 128 addresses); borrowing two bits quadruples the subnet count (to 4) at /26 (64 addresses each), and so on. The relationship is always a clean power of two: borrowing n bits creates 2ⁿ subnets, each with 2^(32−prefix) total addresses.

Binary Representation Explained

Every IPv4 calculation ultimately reduces to binary arithmetic on 32 bits. The subnet mask is ANDed with the IP address to isolate the network address; the mask is bitwise-inverted (giving the wildcard mask) and ORed with the network address to compute the broadcast address. This calculator's live bit visualization shows exactly which of the 32 bits are network bits (fixed, shared by every device on the subnet) versus host bits (variable, unique per device) — dragging the CIDR slider moves that boundary in real time so the relationship becomes visually obvious rather than abstract.

Network Bits vs. Host Bits

Network bits are the leading bits shared by every address in a subnet — they define which subnet an address belongs to. Host bits are the remaining trailing bits, and every possible combination of them (except all-zeros and all-ones, which are reserved) identifies a specific usable device address within that subnet. A /24 has 24 network bits and 8 host bits, giving 2⁸ = 256 total combinations, 254 of them usable.

Network Address

The network address is the subnet's own identity — the address with every host bit set to 0. It's never assigned to a device; routers use it to refer to the subnet as a whole in routing tables. For 192.168.1.0/24, the network address is 192.168.1.0 itself.

Broadcast Address

The broadcast address is the subnet's last address, with every host bit set to 1, used to send a single packet to every host on that local segment at once. For 192.168.1.0/24, that's 192.168.1.255. Like the network address, it's reserved and can't be assigned to a device (except in the /31 special case covered below).

Usable Host Range

The usable host range is every address between the network and broadcast address, excluding both — for 192.168.1.0/24, that's 192.168.1.1 through 192.168.1.254. Two well-known exceptions matter for exam questions and real configuration alike: a /31 (RFC 3021) has no reserved network or broadcast address and offers both its addresses as usable, standard for point-to-point WAN links; a /32 identifies exactly one address, used for host routes and loopback interfaces.

Public vs. Private IP Addresses

RFC 1918 reserves three ranges — 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 — for private use inside organizations; routers on the public internet never forward traffic to or from these ranges directly, which is why home and office networks reuse them freely alongside Network Address Translation (NAT). Every other IPv4 address (outside private, loopback, link-local, multicast, and other reserved ranges) is potentially publicly routable. This calculator flags which category any address you enter falls into.

Classes of IPv4 Networks

Before CIDR, addresses were divided into classes purely by their first octet: Class A (1–126, implying a /8), Class B (128–191, implying a /16), Class C (192–223, implying a /24), Class D (224–239, reserved for multicast), and Class E (240–255, reserved for experimental use). Classful addressing is obsolete for routing purposes — CIDR lets any prefix apply to any address — but the class labels are still commonly referenced in documentation and certification exams, so this calculator reports both the legacy class and the modern CIDR-based classification.

CIDR Prefix Chart

The full reference table above lists every prefix from /0 to /32 with its subnet mask, wildcard mask, total address count, and usable host count. A few are worth memorizing for quick mental math: /24 (254 hosts), /25 (126 hosts), /26 (62 hosts), /27 (30 hosts), /28 (14 hosts), /29 (6 hosts), /30 (2 hosts) — each step halves the previous host count, which is the fastest way to sanity-check a subnetting answer without a calculator at all.

VLSM Explained

Variable Length Subnet Masking assigns a different prefix length to each subnet based on its actual host requirement, instead of forcing every subnet in a network to share one uniform mask. A department needing 100 hosts gets a /25; a point-to-point link needing 2 addresses gets a /30 — allocated correctly, VLSM can turn a network that would only support a handful of equally-sized subnets into dozens of appropriately-sized ones. The standard allocation strategy (and the one this tool's VLSM planner implements) is to sort requirements largest-first and allocate each into the smallest block that fits, which avoids fragmenting the address space with wasted gaps.

Supernetting Explained

Supernetting is the inverse of subnetting: combining multiple contiguous, equally-sized networks into one larger block that can be advertised as a single route — the mechanism behind CIDR route aggregation across the entire public internet's routing tables. Two adjacent /24s that share the same /23 parent (differing only in their lowest network bit) can be summarized as one /23 route, halving the number of routes a router needs to track for that address space.

Network Planning Examples

A typical small office might allocate 192.168.1.0/24 for general staff (254 hosts), 192.168.2.0/26 for a guest Wi-Fi network isolated by VLAN (62 hosts), and 192.168.2.64/30 for a router-to-firewall link (2 hosts) — three subnets, three different sizes, planned with VLSM instead of wasting a /24 on a 2-address link.

Enterprise Network Design and VLANs

Larger networks pair subnetting with VLANs (Virtual LANs) — each VLAN typically maps to its own subnet, letting a single physical switch infrastructure logically separate departments, guest traffic, VoIP, and server segments without separate cabling. Getting the subnet sizes right during design (using VLSM rather than one-size-fits-all) is what keeps the address plan from needing a disruptive re-architecture as the organization grows.

Subnetting in Cloud and Container Networking

Cloud platforms didn't replace subnetting — they just moved it into a console. An AWS VPC is defined by a CIDR block (commonly a /16), subdivided into smaller subnets per availability zone; AWS additionally reserves 5 addresses in every subnet for internal networking purposes, on top of the standard network/broadcast reservation. Azure Virtual Networks and subnets work almost identically, also reserving 5 addresses per subnet. Google Cloud VPC networks use a similar CIDR-based subnet model, though GCP subnets can span multiple zones within a region. Container orchestration adds another layer: Kubernetes clusters need distinct, non-overlapping CIDR ranges for the cluster network, pod network, and service network, and Docker's default bridge network allocates its own private subnet for container-to-container communication. In every case, the underlying math this calculator performs — network address, broadcast, usable range — is exactly what you're planning when you type a CIDR block into any of these consoles.

Subnetting for CCNA and CCNP Exams

Subnetting is one of the highest-value topics on the CCNA exam because it's tested constantly across multiple question formats — fill-in-the-blank, drag-and-drop, and embedded inside larger scenario questions — and because real speed matters under exam time pressure. The fastest path to fluency is memorizing the power-of-two host counts per prefix (covered above) and practicing the "magic number" method: subtract the interesting octet's mask value from 256 to get the block size, then count in that increment to find subnet boundaries. Use this calculator to check your manual answers while you build that speed, not as a permanent substitute for doing the math yourself — exams don't allow calculators, so the mental shortcuts are the actual skill being tested. CCNP-level design questions build on the same foundation with VLSM and route summarization across multi-router topologies, which is exactly what the VLSM planner and supernet view above are built to illustrate.

Common Subnetting Mistakes

• Forgetting the network and broadcast reservation. A /24 has 256 total addresses but only 254 usable — a very common off-by-two error.
• Misaligning subnet boundaries. Subnets must start on a multiple of their own block size; picking an arbitrary starting address instead of a valid boundary produces overlapping or invalid ranges.
• Assuming /31 and /32 follow the "minus 2" rule. They don't — /31 has 2 usable addresses and /32 has exactly 1.
• Confusing a subnet mask with a wildcard mask. They're bitwise inverses of each other; using one where the other is expected (a frequent ACL misconfiguration) silently matches the wrong addresses.
• Overlapping VPC or VLSM ranges. Always verify new subnet ranges don't intersect existing ones before deploying — a mistake that's easy to make by hand and easy to catch with a generated subnet list.

Security Best Practices for Subnetting

Segment by function and trust level, not just by convenience — put guest Wi-Fi, IoT devices, servers, and staff workstations in separate subnets so a firewall or ACL can enforce which segments may talk to which, containing a compromise instead of letting it spread laterally across a flat network. Use the smallest subnet that reasonably fits each segment's growth plan rather than defaulting every VLAN to a /24; oversized subnets waste address space and, more importantly, put more devices inside a single broadcast domain and a single blast radius than necessary.

IP Subnet Calculator — Frequently Asked Questions