Skip to content
Calixo

CIDR Calculator

Find subnet details from a single CIDR block like 192.168.1.0/24 — parsing the compact notation networking professionals use to describe IP address ranges.

Inputs

Paste this into any page — the widget stays live and updates automatically as this calculator improves. Using WordPress or Notion? See the embed guide.

Saved Scenarios

— select 2+ to compare
Inputs updated · Results recalculated · Just now

Network Address

192.168.1.0

Broadcast Address

192.168.1.255

Subnet Mask

255.255.255.0

First Usable Host

192.168.1.1

Last Usable Host

192.168.1.254

Total Addresses

256

Usable Hosts

254

Spark says

From below of long thin blue cables connected to row of small white connectors on system block in data center
Photo by Brett Sayles on Pexels
Close-up of a modern server unit in a blue-lit data center environment.
Photo by panumas nikhomkhai on Pexels

Formula

CIDR Block=IP/PrefixCIDR\ Block = IP/Prefix
Prefix
— The number of network bits, e.g. 24 in a /24

What is the CIDR Calculator?

CIDR (Classless Inter-Domain Routing) notation combines an IP address and prefix length into a single string — this calculator parses that notation directly and returns the subnet's key boundaries.

Use this when reading a network configuration or firewall rule that specifies a CIDR block and want to understand its actual address range, planning IP address allocation for a new network segment, or verifying a subnet's boundaries before configuring a router or firewall rule.

How to use it

  1. 1 Enter a CIDR block in the form IP/prefix, e.g. 10.0.0.0/16.

Understanding CIDR Calculator

CIDR (Classless Inter-Domain Routing) notation solved a genuinely important scaling problem in how the internet allocates and routes IP addresses, and understanding the problem it solved makes the notation itself much more intuitive than memorizing it as an arbitrary format.

Before CIDR, IP address allocation used a rigid 'classful' system that divided all possible networks into a small number of fixed-size categories (Class A, B, and C networks, each with a predetermined, non-negotiable size). This rigidity was a serious practical problem: an organization needing slightly more addresses than a Class C network (256 addresses) provided had to be allocated an entire Class B network (65,536 addresses), wasting the vast majority of that allocation on addresses the organization would never use. As the internet grew through the 1980s and 1990s, this waste became a genuine crisis, threatening to exhaust the available IPv4 address space far faster than actual usage justified.

CIDR's solution was to abandon the fixed-size class system entirely in favor of a flexible, arbitrary-length prefix — the '/N' notation, where N specifies exactly how many bits of the 32-bit IP address are reserved for the network portion, with the remaining bits available for host addresses within that network. This flexibility meant an organization needing exactly 500 addresses could be allocated something close to that size (a /23 subnet, providing 510 usable addresses) rather than being forced into an oversized classful allocation — a much more efficient use of the finite IPv4 address space, and the approach that ultimately extended the practical lifespan of IPv4 considerably beyond what continued classful allocation would have allowed.

The notation itself packs a genuinely elegant amount of information into a compact string. The IP address portion identifies any address within the subnet (not necessarily its first address), while the prefix length after the slash determines the subnet's total size — critically, in an inverse relationship that trips up many newcomers to networking: a smaller prefix number means more host bits are available, meaning a larger subnet with more addresses, while a larger prefix number means fewer host bits, a smaller subnet with fewer addresses. A /8 network (24 host bits) contains over 16 million addresses; a /30 network (2 host bits) contains only 4. This inverse relationship — smaller number, bigger network — is genuinely counterintuitive at first encounter but becomes second nature with enough practice, and it's exactly the kind of relationship a calculator like this one helps make concrete through real, computed examples rather than abstract memorization.

Within any standard subnet (from /24 down through /30), two addresses are conventionally reserved and unavailable for host assignment: the network address (the very first address in the range, with all host bits set to zero, used to identify the network itself rather than any specific device on it) and the broadcast address (the very last address, with all host bits set to one, used to send a single message to every device on that subnet simultaneously). This is why usable host count is always exactly two less than the subnet's total address count for standard subnets — a detail this calculator handles automatically, but one that's genuinely useful to understand conceptually, since it explains why a /24 subnet's oft-cited '256 addresses' translates to only 254 addresses actually assignable to real devices.

Worked examples

Advantages

  • Parses standard CIDR notation directly, matching exactly how network engineers write and communicate subnets.
  • Instantly returns all the key subnet boundaries (network, broadcast, usable range) from one compact input.
  • Works for any valid CIDR block, from small /30 point-to-point links to large /8 allocations.
  • Useful for both learning subnetting concepts and quick professional reference.

Limitations

  • Assumes standard subnet conventions (network and broadcast addresses reserved) — doesn't cover the special conventions used for /31 point-to-point links or /32 single-host routes.

Common mistakes

  • ⚠️ Assuming the IP address portion of a CIDR block must be the network's first address — any address within the range works as input, and the calculator finds the containing subnet regardless.
  • ⚠️ Confusing a subnet's total address count with its usable host count, forgetting that the network and broadcast addresses within a subnet aren't assignable to hosts.
  • ⚠️ Misreading the prefix length — a common error is confusing a smaller prefix number (like /16, a large subnet) with a smaller subnet, when in CIDR notation a smaller number actually means more addresses, not fewer.

Tips

  • 💡 Remember the CIDR prefix relationship is inverse to subnet size — a smaller prefix number (/16) means a larger subnet with more addresses, while a larger prefix number (/28) means a smaller subnet with fewer addresses.
  • 💡 When troubleshooting a network configuration, use this calculator to independently verify a device or firewall's reported subnet boundaries match your expectations.
  • 💡 For network planning, work out the required number of hosts first, then find the smallest CIDR prefix that comfortably covers that count with room for growth.
  • 💡 Double-check whether a given context requires network/broadcast reservation (standard subnets) or uses special /31 or /32 conventions before assuming the usable host count applies.

Real-life uses

  • Reading a network configuration or firewall rule that specifies a CIDR block
  • Planning IP address allocation for a new network segment
  • Verifying a subnet's boundaries before configuring a router or firewall rule
  • Learning and practicing IP subnetting concepts with real address examples

Frequently asked questions

Does the IP address in the CIDR block need to be the network address itself?

No — any IP address within the subnet works; this calculator finds the containing network's boundaries regardless of which specific address you enter.

Why does a smaller prefix number mean a bigger network?

The prefix number specifies how many bits are reserved for the network portion of the address — fewer network bits means more remaining host bits, and each additional host bit doubles the number of possible addresses, so a smaller prefix number always means more total addresses.

What problem did CIDR actually solve?

It replaced a rigid, fixed-size 'classful' address allocation system that wasted enormous numbers of addresses on organizations that needed only slightly more than one class size provided — CIDR's flexible prefix length allowed much more efficient, right-sized allocation.

Why are two addresses always subtracted from a subnet's total?

The first address (all host bits zero) is reserved as the network address identifying the subnet itself, and the last address (all host bits one) is reserved as the broadcast address for reaching every device on the subnet — neither is assignable to an individual host.

Is CIDR notation used for IPv6 as well as IPv4?

Yes — CIDR-style prefix notation is used for IPv6 addressing too, though IPv6's vastly larger address space means the specific prefix lengths and subnetting considerations differ meaningfully from IPv4 practice.