Subnet Splitter & Merger

Divide, merge, and validate IPv4 and IPv6 subnets

/

Quick Examples

About This Tool

Split a larger IPv4 or IPv6 subnet into smaller, equal-sized subnets. Useful for network planning and IP address management. Supports both address families with automatic detection.

100% Client-Side Analysis

This tool runs 100% in your browser. No data is sent to any server.

How to Divide Subnets

Subnet division (splitting) takes a larger network block and breaks it into smaller, equal-sized subnets. This is one of the most common tasks in network planning — whether you're allocating address space in a data centre, setting up VLANs in an office, or designing cloud VPC architectures.

The process works by borrowing bits from the host portion of an IP address and using them as subnet bits. Each additional bit you borrow doubles the number of subnets while halving the number of hosts per subnet. For example, splitting a /24 (256 addresses) into /25s gives you two subnets of 128 addresses each. Splitting further into /26s gives four subnets of 64 addresses.

Example: Splitting 10.0.0.0/24 into /26 subnets

10.0.0.0/26    → 10.0.0.0 – 10.0.0.63    (62 usable hosts)

10.0.0.64/26   → 10.0.0.64 – 10.0.0.127   (62 usable hosts)

10.0.0.128/26 → 10.0.0.128 – 10.0.0.191 (62 usable hosts)

10.0.0.192/26 → 10.0.0.192 – 10.0.0.255 (62 usable hosts)

At NetOz, we use subnet splitting to allocate address space across our Adelaide hosting infrastructure. A /24 block like 151.158.22.0/24 might be split into /28 subnets, giving each customer rack its own 14-host network segment with proper isolation.

When splitting subnets, remember that each subnet loses two addresses — the network address (first) and the broadcast address (last). A /28 has 16 total addresses but only 14 usable hosts. For very small subnets like /30 (used for point-to-point links), you get just two usable addresses, and /31 subnets (RFC 3021) can use both addresses by eliminating the broadcast.

VLSM Explained

Variable Length Subnet Masking (VLSM) is a technique that allows you to use different subnet sizes within the same network, rather than dividing everything into equal-sized blocks. This dramatically reduces IP address waste by matching the subnet size to the actual number of hosts needed.

Before VLSM, classful networking required all subnets within a network to use the same mask. If you had a department with 5 hosts and another with 200, both would get the same size subnet — wasting hundreds of addresses for the smaller department. VLSM, defined in RFC 1009 and widely adopted with CIDR (RFC 4632), solved this by allowing subnets of varying sizes.

Example: VLSM allocation for 10.0.0.0/24

Server VLAN (50 hosts)

10.0.0.0/26 → 62 usable

Staff Wi-Fi (25 hosts)

10.0.0.64/27 → 30 usable

Guest Wi-Fi (10 hosts)

10.0.0.96/28 → 14 usable

Management (4 hosts)

10.0.0.112/29 → 6 usable

Router link

10.0.0.120/30 → 2 usable

Remaining

10.0.0.124 – 10.0.0.255 free

The key to VLSM planning is to allocate the largest subnets first, then fill in smaller ones from the remaining space. Always start from the beginning of the address block and work forwards, ensuring subnets don't overlap. This tool's overlap checker helps you verify that your VLSM allocations are conflict-free.

VLSM requires routing protocols that carry subnet mask information — OSPF, EIGRP, IS-IS, and BGP all support VLSM. Older protocols like RIPv1 and IGRP do not, but these are rarely used in modern networks.

Network Segmentation Examples

Network segmentation divides a larger network into isolated segments, improving security, performance, and manageability. By splitting subnets, you create boundaries that control traffic flow between segments and limit the blast radius of security incidents.

Small Office Network

A typical small office with 30 employees, servers, and guest access. Starting with 192.168.1.0/24:

192.168.1.0/26    → Staff workstations (62 hosts)

192.168.1.64/27   → Servers and printers (30 hosts)

192.168.1.96/27   → Guest Wi-Fi (30 hosts, isolated)

192.168.1.128/30 → WAN uplink to router

Web Hosting Environment

A hosting provider allocating a /22 (1,024 addresses) across services. This is similar to how NetOz segments its Adelaide data centre infrastructure:

151.158.20.0/24   → Shared hosting customers

151.158.21.0/24   → VPS instances

151.158.22.0/25   → Dedicated servers

151.158.22.128/26 → Management and monitoring

151.158.22.192/26 → Infrastructure (DNS, mail, load balancers)

Cloud VPC Architecture

A three-tier application in a cloud VPC using 10.0.0.0/16, split across availability zones:

10.0.0.0/20    → AZ-1 public subnets (web tier)

10.0.16.0/20   → AZ-1 private subnets (app tier)

10.0.32.0/20   → AZ-1 data subnets (database tier)

10.0.48.0/20   → AZ-2 public subnets

10.0.64.0/20   → AZ-2 private subnets

10.0.80.0/20   → AZ-2 data subnets

Effective segmentation relies on firewall rules or access control lists between subnets. Simply placing devices on different subnets doesn't provide security unless you also control routing and filtering between them. Combine subnetting with VLANs at layer 2 for complete isolation.

Need to calculate subnet details for a single IP? Try our Subnet Calculator. For DNS-related queries, use the DNS Lookup tool, or check network paths with our Looking Glass.