Calculate IPv4 subnets with network, broadcast, usable host range, wildcard mask, and CIDR sliders for planning LANs and cloud VPCs accurately offline.
Part of our Developer Tools collection — Explore more Developer Tools tools · See also: JSON Formatter, Base64 Encode / Decode.
Quick answer: Subnet Calculator — IPv4 network calc Free, no signup, runs in your browser. See below for the interactive tool, 4-step guide and FAQs.
| IP Address | 192.168.1.10 /24 |
|---|---|
| Network | 192.168.1.0 |
| Broadcast | 192.168.1.255 |
| Subnet Mask | 255.255.255.0 (11111111.11111111.11111111.00000000) |
| Wildcard Mask | 0.0.0.255 |
| First Usable | 192.168.1.1 |
| Last Usable | 192.168.1.254 |
| Usable Hosts | 254 |
| Total Addresses | 256 |
Reviewed by the Tool4SaaS Editorial Team — In-house reviewers who build and test every tool locally for accuracy across current Chrome, Edge, Firefox, and Safari. Last updated: . See our authors, methodology or contact us.
It derives mask, network, broadcast, first and last host, usable count and wildcard through bitwise arithmetic. For illustration, 192.168.1.0/24 yields 254 hosts from dot 1 to dot 254. A slash 16 yields 65534 hosts. Results suit LAN sizing and cloud VPC segmentation with immediate copyable tables.
Yes. Bitwise computation executes solely inside this tab, so 10 dot 0 dot 0 dot 0 slash 8 plans never traverse networks. For instance, VPC schemes remain resident. All processing is local, so anything typed here is not sent to a server. No schemes leave this environment for external inspection.
IPv4 only with 0 through 32 CIDR; for example, 192.168.1.0/24 yields 254 hosts. IPv6 demands 128-bit logic and compressed notation, so consult cloud VPC planners for v6. Slash 31 suits point links with two addresses, 32 marks single host. Domain parsing lives at /url-parser for naming work.
Reserve large supernets for regions, allocate slash 24 blocks per availability zone, and document each assignment centrally. For example, 10 dot 0 dot 0 dot 0 slash 8 splits into 256 slash 16 campuses. Audit route tables for collisions, stagger expansion space, and peer only intentional ranges to prevent asymmetric routing and security gaps.
Slash 31 provides two usable addresses with no broadcast for point-to-point links per RFC 3021, while slash 32 marks a single host route. For illustration, 192.168.1.0 slash 31 links routers without wasting space, and 10 dot 0 dot 0 dot 5 slash 32 pins a loopback. Confirm peer support before deploying.
Calculation divides IPv4 space into mask, network, broadcast, host range, wildcard and count via bitwise logic. Example 1: 192.168.1.0/24 gives network dot 0, broadcast dot 255, hosts dot 1 to dot 254 totalling 254. Example 2: slash 16 gives 65534 hosts for campus backbones. Planners size office LANs and cloud VPCs, avoiding collisions. Masks define network bits, wildcards invert them for access lists, and counts guide DHCP scopes. Accurate carving prevents overlap, simplifies routing, and reserves growth headroom across availability zones with documented allocations.
Reference mask table: slash 24 is 255 dot 255 dot 255 dot 0 | slash 16 is 255 dot 255 dot 0 dot 0 | slash 30 gives 2 usable hosts | slash 31 suits links | slash 32 single host | wildcard inverts mask for ACLs. Enter IP like 192 dot 168 dot 1 dot 0, slide CIDR to view transformations. Edge case: network and broadcast addresses remain unusable except slash 31 and 32 specials. Copy tables into docs, verify DHCP pools exclude gateway addresses, and confirm cloud reserves first four addresses automatically in many VPC implementations. Workshops validating slash 30 link nets and slash 31 specials rehearse gateway exclusions through table drills that avert addressing collisions across projects while updating diagrams quarterly now daily.
Type 10 dot 0 dot 0 dot 0 slash 8 to see sixteen million hosts, then carve slash 24 blocks of 254 for teams. Second trial: evaluate 192.168.1.0/24 for branch office with printer range and guest VLAN. Limitation: IPv4 only, no IPv6, and overlapping assignments still possible without central tracking. For permission planning after addressing, see the tool at /chmod-calculator for file modes. For hostname structure, see the parser at /url-parser for DNS breakdowns.