# Subnet and CIDR Calculator (`mangudai/subnet-cidr-calculator`) Actor Calculate subnet masks, CIDR blocks and host ranges offline for IPv4 and IPv6. Get the netmask, wildcard mask, network and broadcast address, first and last usable host, and address counts. Split networks into subnets, list hosts, test if an IP is in range, or turn an IP range into CIDR blocks. - **URL**: https://apify.com/mangudai/subnet-cidr-calculator.md - **Developed by:** [MangudΓ€i](https://apify.com/mangudai) (community) - **Categories:** Developer tools, Automation, Open source - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $0.01 / 1,000 results This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README ## Subnet and CIDR calculator Work out subnet masks, host ranges, broadcast addresses and CIDR blocks for IPv4 and IPv6, as a clean table you can export to CSV, JSON or Excel. Give it a network like `192.168.1.0/24` and it returns the subnet mask, wildcard mask, network and broadcast address, first and last usable host, total and usable address counts, address class, private or global status, and the reverse DNS pointer. It can also split a network into smaller subnets, list every host address, test whether an IP falls inside a network, and turn a start and end IP into the smallest set of CIDR blocks that cover it. Everything runs offline on the Python standard library. No API key, no third-party service, nothing that can go stale or break. ### What it does Five operations, mixed freely in one run: `info` returns full details for a network. Accepts `192.168.1.0/24`, `192.168.1.0 255.255.255.0`, `192.168.1.5/255.255.255.0` or a bare address. Host bits are tolerated and normalised to the network address. `subnets` splits a network into equal blocks at a new prefix length. Give `network` and `newPrefix`, for example `10.0.0.0/16` at `/20` returns 16 rows. `hosts` lists every usable host address in the network, one row each, capped at 5,000 rows. `contains` checks whether an address sits inside a network. Give `network` and `ipAddress`, and the row carries the network details plus a true or false `contains` column. `range` takes `startIp` and `endIp` and returns the minimal set of CIDR blocks covering that range, one row per block. Useful for firewall rules and allowlists. ### Input One field, `calculations`, an array of objects: ```json { "calculations": [ { "operation": "info", "network": "192.168.1.0/24" }, { "operation": "info", "network": "2001:db8::/32" }, { "operation": "subnets", "network": "10.0.0.0/16", "newPrefix": 20 }, { "operation": "hosts", "network": "192.168.1.0/29" }, { "operation": "contains", "network": "192.168.1.0/24", "ipAddress": "192.168.1.42" }, { "operation": "range", "startIp": "192.168.1.10", "endIp": "192.168.1.100" } ] } ``` A bad network or a missing field produces an error row instead of stopping the run, so one typo never costs you the rest of the batch. ### Output One row per result with these columns: `input`, `operation`, `cidr`, `version`, `networkAddress`, `prefixLength`, `netmask`, `wildcardMask`, `broadcastAddress`, `firstHost`, `lastHost`, `totalAddresses`, `usableHosts`, `ipClass`, `isPrivate`, `isGlobal`, `isMulticast`, `isLoopback`, `isLinkLocal`, `isReserved`, `reversePointer`, `index`, `ipAddress`, `contains`, `error`. Sample row for `192.168.1.0/24`: | cidr | netmask | wildcardMask | broadcast | firstHost | lastHost | usableHosts | class | private | | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 192.168.1.0/24 | 255.255.255.0 | 0.0.0.255 | 192.168.1.255 | 192.168.1.1 | 192.168.1.254 | 254 | C | true | IPv6 rows leave `broadcastAddress`, `wildcardMask` and `ipClass` empty, since those concepts do not apply. ### Who uses it Network engineers planning address space. DevOps and cloud teams sizing VPC and subnet CIDRs before a Terraform run. Security teams converting IP ranges into firewall rules. Anyone who needs subnet math in a spreadsheet or piped into another tool through the Apify API. ### Notes /31 networks return both addresses as usable, following RFC 3021. /32 returns the single address. The `hosts` operation is capped at 5,000 rows and `subnets` and `range` at 5,000 blocks, so a `/8` split into `/24` will stop early rather than run away. Pricing is pay per event: you pay per result row, nothing else. # Actor input Schema ## `calculations` (type: `array`): List of calculations. Each item needs an operation. info returns full subnet details for a network. subnets splits a network into smaller blocks of newPrefix. hosts lists every usable host address. contains checks whether ipAddress falls inside the network. range turns startIp and endIp into the smallest set of CIDR blocks. ## Actor input object example ```json { "calculations": [ { "operation": "info", "network": "192.168.1.0/24" }, { "operation": "info", "network": "10.0.0.0/8" }, { "operation": "info", "network": "2001:db8::/32" }, { "operation": "subnets", "network": "192.168.1.0/24", "newPrefix": 26 }, { "operation": "contains", "network": "192.168.1.0/24", "ipAddress": "192.168.1.42" }, { "operation": "range", "startIp": "192.168.1.10", "endIp": "192.168.1.100" } ] } ``` # Actor output Schema ## `results` (type: `string`): No description # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "calculations": [ { "operation": "info", "network": "192.168.1.0/24" }, { "operation": "info", "network": "10.0.0.0/8" }, { "operation": "info", "network": "2001:db8::/32" }, { "operation": "subnets", "network": "192.168.1.0/24", "newPrefix": 26 }, { "operation": "contains", "network": "192.168.1.0/24", "ipAddress": "192.168.1.42" }, { "operation": "range", "startIp": "192.168.1.10", "endIp": "192.168.1.100" } ] }; // Run the Actor and wait for it to finish const run = await client.actor("mangudai/subnet-cidr-calculator").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`πŸ’Ύ Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // πŸ“š Want to learn more πŸ“–? Go to β†’ https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "calculations": [ { "operation": "info", "network": "192.168.1.0/24", }, { "operation": "info", "network": "10.0.0.0/8", }, { "operation": "info", "network": "2001:db8::/32", }, { "operation": "subnets", "network": "192.168.1.0/24", "newPrefix": 26, }, { "operation": "contains", "network": "192.168.1.0/24", "ipAddress": "192.168.1.42", }, { "operation": "range", "startIp": "192.168.1.10", "endIp": "192.168.1.100", }, ] } # Run the Actor and wait for it to finish run = client.actor("mangudai/subnet-cidr-calculator").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"πŸ’Ύ Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # πŸ“š Want to learn more πŸ“–? Go to β†’ https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "calculations": [ { "operation": "info", "network": "192.168.1.0/24" }, { "operation": "info", "network": "10.0.0.0/8" }, { "operation": "info", "network": "2001:db8::/32" }, { "operation": "subnets", "network": "192.168.1.0/24", "newPrefix": 26 }, { "operation": "contains", "network": "192.168.1.0/24", "ipAddress": "192.168.1.42" }, { "operation": "range", "startIp": "192.168.1.10", "endIp": "192.168.1.100" } ] }' | apify call mangudai/subnet-cidr-calculator --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,mangudai/subnet-cidr-calculator" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/EfOSVREb6d0ayzt0e/builds/47FDT2YKTgeLUN3jo/openapi.json