Enterprise IPAM Health Auditor

NetBox API: subnet utilisation trending, duplicate IP detection, stale DHCP leases, DNS A/PTR mismatch, top subnets by growth rate, exhaustion prediction and HTML report.

NetBox

Infoblox

BIND/ISC DHCP

Open in Generator Open in Platform

You're viewing a preview

The full script, parameters, and execution console are available with a free account.

Already have access? Sign in →

Capabilities

NetBox prefix utilisation
Duplicate IP detection
Stale DHCP lease scan
DNS A/PTR mismatch
Top growth subnets
Exhaustion prediction
HTML report

Required inputs

Parameters the script accepts. Defaults shown; some are vendor- or context-gated.

Parameter	Type	Default	Notes
Utilisation warning (%) util_warn_pct	number	80	—
Exhaustion horizon (days) exhaust_days	number	90	—
Check DNS A/PTR check_dns	bool	true	—

Hint 1 — Name your vendors and OS versions

Mention the exact platforms you run (NetBox, Infoblox, BIND/ISC DHCP) so the generated operations logic uses the right CLI/NETCONF syntax.

Hint 2 — State your real thresholds

Provide concrete values for Utilisation warning (%), Exhaustion horizon (days), Check DNS A/PTR instead of the defaults — they shape what counts as a fault.

Hint 3 — Prioritize the checks you need

This tool can netBox prefix utilisation and duplicate IP detection. Ask for the subset relevant to your incident to keep output focused.

Hint 4 — Describe your inventory format

Tell the assistant whether your device list is CSV, YAML, or JSON and which columns it has, so parsing matches your data.

Sample inventory schema

Authoritative shape of the device/policy data this script consumes.

No bundled inventory sample. The script accepts standard device lists (CSV/YAML) with hostname, mgmt IP, vendor, and credentials.

Expected output

Reference terminal output the script should produce — used as a stylistic and structural target.

terminal

[2026-06-12] INFO  NetBox: analysing 412 prefixes...
PREFIX             UTIL%  GROWTH/wk  EXHAUST   STATUS
10.10.0.0/24       96%    +3        ~14 days  CRITICAL ←
10.20.0.0/23       62%    +1        ~280 days OK
Duplicate IP: 10.10.0.5 on 2 interfaces ←
DNS: 4 A records without matching PTR ←
Summary: 1 critical · 1 duplicate · 4 DNS mismatch