{{ result.summaryTitle }}
{{ result.primaryDisplay }}
{{ result.secondaryText }}
{{ result.statusLabel }} {{ result.poolBadge }} {{ result.subnetBadge }} {{ result.leaseBadge }}
Use CIDR or dotted mask notation, for example 192.168.40.0/24 or 192.168.40.0 255.255.255.0.
Keep the router outside the assignable pool unless your DHCP platform explicitly reserves it.
Use start-end pairs such as 192.168.40.20-192.168.40.240. Leave blank to use the full usable subnet.
One IP, CIDR block, or start-end range per line. Only overlaps with the DHCP pool reduce capacity.
Use the busiest observed active lease count, not total devices if many are rarely online.
clients
Pair with the reservation policy below so capacity matches how your server treats fixed leases.
leases
Choose whether the reserved lease count should reduce the dynamic pool capacity.
Use the near-term device growth percentage for this VLAN or access segment.
%
Keep below 100% so abandoned leases, bursts, and audits do not exhaust the scope.
%
Use hours. The calculator reports capacity, not a replacement for DHCP server lease-state cleanup.
hours
Optional human-readable scope name for the configuration artifact.
Choose a familiar output format for handoff notes.
Leave 0 when no temporary client surge is planned.
clients
Leave 0 unless the server shows unavailable addresses that are not active clients.
leases
Leave 0 for neutral math; raise it when a standby or split policy withholds part of the scope.
%
MetricValueDetailCopy
{{ row.metric }}{{ row.value }}{{ row.detail }}
KindRangeCount in poolCount in subnetStatusCopy
{{ row.kind }}{{ row.range }}{{ row.poolCount }}{{ row.subnetCount }}{{ row.status }}
CheckVerdictActionWhy it mattersCopy
{{ row.check }}{{ row.verdict }}{{ row.action }}{{ row.reason }}
{{ result.configSnippet }}
Tags: IP Addressing, Networking, Sysadmin
Export to PDF Fullscreen
Customize
Advanced
:

A Dynamic Host Configuration Protocol (DHCP) scope is the planned address inventory for clients on an IPv4 subnet. It is not just the subnet size. The usable host range, dynamic pool boundaries, exclusions, reservations, held leases, and growth allowance all change how many clients can receive an address before the scope becomes tight.

Scope planning matters because DHCP failure usually appears as a user problem before it appears as a tidy capacity number. A laptop may join Wi-Fi but fail to get an address. A point-of-sale terminal may keep an old lease longer than expected. A guest VLAN may look fine during a quiet day and then run out during onboarding or an event.

Diagram showing usable subnet space reduced by pool boundaries, exclusions, reservations, and projected demand.

Good scope sizing separates address arithmetic from operational judgement. A subnet may contain 254 normal usable host addresses, but a DHCP server may be allowed to hand out only a smaller range. Some addresses are held for routers, printers, controllers, static blocks, or reserved clients. Lease duration then affects how quickly unused addresses return during churn.

A capacity result is a planning signal, not proof that a DHCP server is healthy. It does not query a live server, inspect current lease state, or verify that options are correct on the network. It helps turn a proposed subnet and pool policy into a defensible address plan before clients start failing to renew.

Technical Details:

IPv4 scope capacity begins with a network prefix. CIDR notation such as 192.168.40.0/24 defines how many bits identify the network and how many bits remain for addresses inside that network. Dotted-mask notation such as 192.168.40.0 255.255.255.0 expresses the same idea when the mask is contiguous.

For ordinary IPv4 LAN scopes, the network address and broadcast address are not client leases, so the usable range is the network boundary plus one through the broadcast boundary minus one. A /31 or /32 is still modeled arithmetically, but those prefixes are rarely valid DHCP client scopes because they leave no normal broadcast LAN host inventory.

After the usable range is known, the dynamic pool is clipped to that range and overlapping pool entries are counted once. Exclusions subtract only where they intersect the dynamic pool. Reservations reduce capacity only when the selected reservation policy says fixed leases consume pool addresses.

Pgross = unique usable addresses inside the selected pool ranges Pavailable = Pgross-exclusions inside pool Peffective = max(0,Pavailable-reservation impact-held leases-failover reserve) D = active clients+⌈active clients×growth percent100⌉+temporary burst Starget = ⌊Peffective×target utilization100⌋-D

The final target spare value compares projected demand with a planned ceiling, not with absolute exhaustion. A scope can still have physical spare leases and be marked short when it exceeds the target utilization ceiling.

Capacity and Status Rules:

Rule Boundary Meaning
Usable host range For prefixes below /31, exclude network and broadcast addresses. The dynamic pool is intersected with addresses that can normally be leased to clients.
Pool overlap Overlapping pool ranges are merged before counting. The same address cannot add capacity twice.
Exclusions Only excluded addresses inside the current pool reduce capacity. A static block outside the dynamic pool is reported but does not shrink the pool.
Within target Target spare is greater than max(5, 10% of effective pool). Projected demand has a comfortable cushion against the selected utilization ceiling.
Tight target Target spare is non-negative but at or below max(5, 10% of effective pool). The scope stays within the ceiling, but a small client surge can erase the margin.
Target short Target spare is negative. Projected demand exceeds the selected utilization ceiling and the result shows how many effective lease slots are missing.

Accepted Inputs and Bounds:

Input Accepted rule Effect on the model
Subnet CIDR IPv4 CIDR or IPv4 plus contiguous dotted mask. Defines network, mask, broadcast, and usable host range.
DHCP pool range(s) One range, single IP, or CIDR per line; blank means the full usable subnet. Defines the raw dynamic address inventory after clipping to the usable subnet.
Excluded/static ranges One range, single IP, or CIDR per line. Subtracts addresses only where exclusions intersect the pool.
Active clients, Reserved leases, Temporary burst, and Held leases Whole numbers at or above 0. Builds demand and practical capacity reductions.
Growth headroom 0% to 500%, rounded into whole clients. Adds projected client growth on top of active clients.
Target utilization 1% to 100%. Sets the planned ceiling used for status and target spare leases.
Failover reserve 0% to 90% of capacity before reservations. Withholds extra leases for split-scope, failover, or policy buffer planning.
Lease time At least 0.25 hours. Appears in guidance and generated configuration snippets, but does not by itself add addresses.

Everyday Use & Decision Guide:

Start with the subnet and the pool range that the DHCP server is actually allowed to lease. For a VLAN where the router, switches, printers, or static devices sit at the low end of the subnet, enter the dynamic range rather than assuming the whole subnet is available. Leave the pool blank only when the server should use the full normal host range.

Use exclusions for addresses the server must never hand out. Count reservations according to your platform policy. Some DHCP platforms reserve addresses from inside the dynamic range, while others keep fixed leases outside the range. The Reservation policy setting changes the capacity math without changing the visible address ledger.

  • Use the busiest expected active lease count in Active clients, not a device inventory where many devices are rarely connected.
  • Set Growth headroom for near-term onboarding, device refresh, or extra access points that will add clients to the same scope.
  • Add Temporary burst for events, guest traffic, failover, or migration windows that do not represent normal daily demand.
  • Use Held leases when the server shows abandoned, declined, quarantined, or administratively held addresses that cannot be assigned.
  • Check Address Exclusion Ledger when a line is clipped, outside the usable subnet, or overlaps another range.

The result is a good fit for scope reviews, VLAN build sheets, guest network planning, and change tickets where the question is whether the address plan has enough room. It is a poor fit for proving that clients are renewing correctly, that relay agents are forwarding requests, or that DHCP options match the network design.

After the summary shows a stable status, use Scope Sizing Brief to decide whether to expand inside the current subnet, reduce demand, move reservations, shorten long leases during churn, or plan a larger prefix. Use DHCP Config Snippet only after the ledger matches the policy you intend to deploy.

Step-by-Step Guide:

Work from address ownership first, then add demand and operating reserves.

  1. Enter Subnet CIDR as CIDR or dotted-mask notation. A valid subnet updates the summary with the normalized prefix and usable host range.
  2. Enter Gateway IP. If it sits inside the dynamic pool, the Scope Sizing Brief flags Gateway in pool so you can exclude it or move the pool boundary.
  3. Add one or more DHCP pool range(s). If the range extends beyond the usable subnet, the address ledger reports that it was clipped before capacity is counted.
  4. Add Excluded/static ranges for routers, infrastructure, manual static blocks, or addresses the server should not lease. Review Pool exclusions and Available before reservations in Scope Capacity Ledger.
  5. Enter Active clients, Reserved leases, Reservation policy, Growth headroom, Target utilization, and Lease time. Watch Effective dynamic pool, Projected demand, and Target headroom.
  6. Open Advanced for a Scope label, Snippet style, Temporary burst, Held leases, or Failover reserve. The reserve and held lease fields reduce effective capacity immediately.
  7. Open Lease Pressure Curve when growth is the uncertain part. The chart compares projected utilization against the selected target utilization.
  8. If an input is blocked, fix the listed issue first. A non-contiguous mask, malformed IP, invalid range line, or pool with no usable addresses should not be carried into a capacity decision.

Interpreting Results:

Target headroom is the strongest first read because it compares projected demand with your own utilization ceiling. A positive value means the scope stays under the ceiling. A negative value means the plan needs that many more effective lease slots or less demand. Physical spare leases is a harder exhaustion check and can be positive even when the target is already short.

Do not treat a green result as proof that the DHCP service is correctly configured. Address math can be healthy while a relay, firewall, option set, failover peer, or stale lease database causes client failures. Use the result to size the scope, then compare it with live DHCP server data before a production change.

Output cue What it means Useful follow-up
Target short Projected demand is above the selected utilization ceiling. Expand the pool, reduce exclusions or reservations, lower demand, or plan a larger prefix.
Tight target The plan is under the ceiling but the cushion is small. Check growth, burst clients, held leases, and the next change window before approving the scope.
Gateway in pool The router address overlaps the dynamic pool. Exclude the gateway or move the dynamic pool boundary before deployment.
Consider /23 or another prefix The current subnet cannot provide enough effective slots after modeled reductions. Treat the prefix as a planning recommendation, then confirm routing, VLAN, and firewall impact separately.

Worked Examples:

Office Wi-Fi scope runs past the target ceiling

A 192.168.40.0/24 subnet with a pool of 192.168.40.20-192.168.40.240, exclusions at 192.168.40.50-192.168.40.59 and 192.168.40.200, 145 active clients, 18 reservations inside the pool, and 20% growth produces 192 effective leases. The Projected demand is 174 leases and Projected utilization is 90.6%. With an 80% target, Target headroom is -21 leases, so the status is Target short.

A larger subnet creates enough planning room

Moving the same plan to 192.168.40.0/23 with a pool of 192.168.40.20-192.168.41.240 keeps the same exclusions, active clients, reservations, and growth assumption. The result becomes 448 effective leases, 174 projected clients, 38.8% utilization, and 184 target spare. The Scope Sizing Brief reports No expansion required for that modeled demand.

A near-full /24 needs a watchful review

A 192.168.40.0/24 scope with pool 192.168.40.20-192.168.40.254, no exclusions, 160 active clients, and 10% growth has 235 effective leases. The Projected demand is 176 leases, Projected utilization is 74.9%, and Target headroom is 12 leases. That remains within an 80% ceiling, but the status is Tight target because the margin is small relative to the pool.

Invalid mask blocks the result

Entering 192.168.40.0 255.0.255.0 as the subnet produces Input blocked because the dotted mask is non-contiguous. The Scope Capacity Ledger shows Input issue and the sizing brief asks you to fix the listed input issue before trusting capacity, chart, or snippet output.

FAQ:

Can I leave the pool range blank?

Yes. A blank DHCP pool range(s) field uses the full usable subnet range. Enter explicit ranges when infrastructure, static addresses, or policy boundaries mean the DHCP server should lease only part of the subnet.

Why is the result short when spare leases still exist?

Physical spare leases counts addresses left before total exhaustion. Target headroom compares demand with the selected Target utilization ceiling, so a scope can have a few spare leases and still be marked Target short.

Do reservations always reduce the dynamic pool?

No. The Reservation policy control decides that. Choose Reservations consume pool addresses when fixed leases sit inside the dynamic range. Choose Reservations live outside the pool when they are documented outside the dynamic range.

What causes an input blocked result?

A malformed IPv4 address, non-contiguous dotted mask, invalid range line, or pool with no usable addresses can block the calculation. Fix the line named in the notice before using Scope Capacity Ledger, Lease Pressure Curve, or DHCP Config Snippet.

Does this check a live DHCP server?

No. The calculation runs from the values entered on the page. It does not query a DHCP server, read lease databases, test relay agents, or verify live options, so compare the plan with server data before making a production change.

Glossary:

DHCP scope
The address plan a DHCP server can lease for a subnet, usually with related gateway and option settings.
CIDR prefix
The slash notation that states how many IPv4 bits belong to the network portion, such as /24.
Dynamic pool
The address range the server may assign automatically to clients.
Exclusion
An address or range the server should not hand out as a dynamic lease.
Reservation
A fixed DHCP assignment tied to a client identifier or hardware address.
Target utilization
The planned maximum percentage of the effective pool that projected clients should consume.

References: