What is the difference between this category and Network Operations Lab?

Infrastructure Hub covers the foundational mechanics (basic subnetting, DNS lookup, MAC addressing) that Network Operations Lab's more advanced tools (CIDR aggregation, ASN lookup, reverse DNS) build on top of.

Does Wake-on-LAN work over the public internet?

Not by default — it's fundamentally scoped to the local broadcast domain, since it relies on a broadcast frame. Reaching a remote network typically requires a VPN or a router configured to forward a directed broadcast, which many routers don't support by default.

How do I calculate a subnet's broadcast address?

It's the network address with every host bit set to 1, determined by the subnet mask — the IPv4 Subnet Calculator computes this directly rather than requiring manual binary math.

Should I generate a random MAC address or use a real one for testing?

Generate one deliberately for any test or virtual machine configuration — reusing a real device's MAC address risks an address collision if both are ever active on the same network segment.

What does the OUI portion of a MAC address tell me?

The first three bytes are assigned by the IEEE to a specific hardware manufacturer, meaning a MAC address's first half often reveals which company made the network interface.

Is a DNS lookup failure the same as a routing failure?

No — they're different failure domains. See the DNS vs IP Routing comparison: if a hostname doesn't resolve at all, it's a DNS problem; if it resolves but the connection still fails, the problem has moved to routing or the destination server.

Which hub should I read to go deeper on this category's tools?

The DNS hub covers DNS Lookup in depth; the Networking & Infrastructure hub covers the IPv4 Subnet Calculator, MAC Address Generator, and Wake-on-LAN Packet Generator.

Why does this category have only 4 tools?

It's scoped deliberately narrow, covering only the foundational addressing/resolution mechanics — more advanced or specialized networking tools belong to the separate, larger Network Operations Lab category instead.

Infrastructure Hub

The smallest lab by tool count with the tightest possible hub fit: subnetting, DNS, and hardware addressing basics.

Runs entirely in your browser

This tool executes locally using standard browser APIs (for example window.crypto.getRandomValues or crypto.subtle where applicable). Your input is not transmitted to or stored on a ScriptPulse server. See How Calculations Work.

No data uploaded

Overview

Infrastructure Hub's 4 tools — the IPv4 Subnet Calculator, DNS Lookup, MAC Address Generator, and Wake-on-LAN Packet Generator — cover the foundational networking mechanics that sit beneath almost every higher-level network operation on this site: subnet math, name resolution, hardware addressing, and one classic, specific protocol built directly on that addressing (Wake-on-LAN).

Despite its small size, this is one of only two categories (alongside Security Lab) with complete, tight hub coverage — every tool here maps cleanly to either the DNS or Networking & Infrastructure hub, with no ambiguous or orphaned members.

Why Infrastructure Hub Matters

Subnetting, DNS resolution, and MAC addressing are the literal foundation every higher-level network or infrastructure task in this site's Network Operations Lab category builds on — you can't reason correctly about CIDR aggregation, reverse DNS, or ASN lookups without first being comfortable with the basic mechanics this smaller, foundational category covers.

Common Workflows

Calculating a subnet's mask, host range, and broadcast address with the IPv4 Subnet Calculator before allocating IP ranges for a new network segment.
Resolving a domain's DNS records with the DNS Lookup tool to confirm a hostname's actual current A, AAAA, MX, and TXT records.
Generating a randomized or vendor-prefixed MAC address with the MAC Address Generator for testing or virtual machine configuration.
Building a Wake-on-LAN magic packet with the Wake-on-LAN Packet Generator to remotely power on a machine on the local network.

Learning Roadmap: Beginner

Calculate a subnet mask and host range by hand for a simple /24 network, then verify your work against the IPv4 Subnet Calculator.
Run a DNS lookup against a domain you're familiar with and identify each record type returned (A, MX, TXT) and what it's actually for.
Learn the structure of a MAC address (the OUI manufacturer prefix plus the device-specific remainder) before generating one for a test scenario.

Learning Roadmap: Professional

Read the Networking & Infrastructure and DNS hubs' full Core Concepts sections before troubleshooting a production connectivity issue — knowing whether a failure is DNS-side or routing-side is the single most useful first diagnostic step.
Understand exactly what a Wake-on-LAN magic packet requires (the target's correct MAC address, and typically same-broadcast-domain reachability or a configured directed broadcast) before relying on it for remote infrastructure management.
Cross-reference the DNS vs IP Routing comparison when a connectivity issue's actual layer (application vs network) isn't immediately obvious from the symptom alone.

Tool Selection Strategy

Reach for the IPv4 Subnet Calculator specifically when planning address allocation for a new segment; for more advanced CIDR aggregation or splitting across multiple blocks, the Network Operations Lab category's dedicated tools go further.
Use DNS Lookup as the first diagnostic step for any domain-resolution issue before assuming a routing or server-side problem — confirming DNS resolves correctly rules out an entire class of failure immediately.
Generate a MAC address deliberately (not by copying a real device's) for any test or virtual configuration, to avoid an accidental collision with a real hardware address on the same network.

Tools in Infrastructure Hub

IPv4 Subnet Calculator

Calculate subnet masks, host ranges, and broadcast addresses for IPv4.

Open tool

DNS Lookup

Resolve DNS records using DNS over HTTPS from your browser.

Open tool

MAC Address Generator

Generate randomized MAC addresses with optional unicast/local bits.

Open tool

Wake-on-LAN Packet Generator

Generate Wake-on-LAN magic packets in hexadecimal and binary forms.

Open tool

Developer Guide

Go deeper than the tool list — these Developer Hubs cover the concepts behind Infrastructure Hub's tools in full depth.

Domain Name System (DNS)Networking & Infrastructure

Comparative Guides

Decide between the technologies and formats Infrastructure Hub's tools work with:

DNS vs IP Routing

DNS and IP routing solve two completely different problems that happen to run back-to-back during every web request — DNS answers 'what address does this name point to,' while routing answers 'how does a packet actually get from here to that address' — and correctly diagnosing a connectivity failure depends entirely on knowing which of the two actually failed.

Read Guide

DNS A vs CNAME records

An A record points a name directly at an IP address; a CNAME points a name at another name instead — a small difference in mechanism that produces one genuinely important, frequently-violated restriction (no CNAME at a domain's root) and a whole category of provider-specific workarounds that exist purely to get around it.

Read Guide

DNS A vs AAAA records

Publishing both an A and an AAAA record for the same hostname (dual-stack) is standard modern practice, but the real engineering problem it creates — a client racing to figure out which protocol actually works, quickly, without a slow timeout on a broken path — was significant enough to need its own dedicated IETF algorithm, Happy Eyeballs, which is the part of this story most A-vs-AAAA comparisons skip entirely.

Read Guide

IPv4 vs IPv6

IPv4 and IPv6's real difference isn't just address space — IPv6's simplified header and native autoconfiguration reflect two decades of learning from IPv4's operational pain points, though one commonly-repeated claim about IPv6 (that it mandates IPsec) has actually been out of date since 2011 and is worth correcting directly.

Read Guide

MAC Address vs IP Address

A MAC address identifies a specific physical network interface and never changes; an IP address identifies a device's logical position in a network and routinely does — the protocol that bridges the two, letting an IP-addressed packet actually reach the right physical hardware on a local network, is exactly what most comparisons of these two addressing systems skip over.

Read Guide

Common Mistakes

Assuming a connectivity failure is a routing problem without first confirming DNS actually resolved correctly — the two are entirely separate failure domains that happen to run back-to-back.
Miscalculating a subnet's broadcast address by hand and accidentally overlapping two supposedly-separate network segments.
Assuming Wake-on-LAN works across the public internet without a properly configured directed broadcast or VPN — it's fundamentally a local-network-scoped mechanism by default.
Using a real device's MAC address in a test configuration instead of a generated one, risking an address collision on a shared network.

Standards Landscape

RFC 1035 defines core DNS resolution mechanics; RFC 4632 defines CIDR, the addressing scheme this category's subnet calculator implements.
IEEE assigns the Organizationally Unique Identifier (OUI) portion of every MAC address to specific hardware manufacturers.
Wake-on-LAN itself has no single IETF RFC — it's an industry convention originating from network interface card vendors, most notably formalized by AMD's Magic Packet Technology specification.

Glossary

CIDR: Classless Inter-Domain Routing — the notation (like /24) expressing how many bits of an IP address represent the network portion versus the host portion.
Broadcast address: The address within a subnet reserved to reach every host on that subnet simultaneously, calculated from the network address and subnet mask.
OUI: Organizationally Unique Identifier — the first three bytes of a MAC address, assigned by the IEEE to a specific hardware manufacturer.
Magic Packet: The specific broadcast frame format (containing a target's MAC address repeated 16 times) that triggers a Wake-on-LAN-capable network card to power on its host machine.

Troubleshooting

If two hosts that should be on separate subnets can reach each other unexpectedly, recheck the subnet mask calculation — an incorrectly sized subnet can silently overlap address ranges.
If Wake-on-LAN doesn't power on a target machine, confirm the NIC's WoL feature is actually enabled in the machine's BIOS/firmware, not just that the magic packet was sent correctly.
If a domain's DNS lookup returns unexpected results, check whether you're seeing a cached (stale) value versus the record's actual current, authoritative state.

References

RFC 4632 — Classless Inter-domain Routing (CIDR)RFC 1035 — Domain Names, Implementation and Specification

Browse the full Standards & References library →

Frequently Asked Questions

What is the difference between this category and Network Operations Lab?: Infrastructure Hub covers the foundational mechanics (basic subnetting, DNS lookup, MAC addressing) that Network Operations Lab's more advanced tools (CIDR aggregation, ASN lookup, reverse DNS) build on top of.
Does Wake-on-LAN work over the public internet?: Not by default — it's fundamentally scoped to the local broadcast domain, since it relies on a broadcast frame. Reaching a remote network typically requires a VPN or a router configured to forward a directed broadcast, which many routers don't support by default.
How do I calculate a subnet's broadcast address?: It's the network address with every host bit set to 1, determined by the subnet mask — the IPv4 Subnet Calculator computes this directly rather than requiring manual binary math.
Should I generate a random MAC address or use a real one for testing?: Generate one deliberately for any test or virtual machine configuration — reusing a real device's MAC address risks an address collision if both are ever active on the same network segment.
What does the OUI portion of a MAC address tell me?: The first three bytes are assigned by the IEEE to a specific hardware manufacturer, meaning a MAC address's first half often reveals which company made the network interface.
Is a DNS lookup failure the same as a routing failure?: No — they're different failure domains. See the DNS vs IP Routing comparison: if a hostname doesn't resolve at all, it's a DNS problem; if it resolves but the connection still fails, the problem has moved to routing or the destination server.
Which hub should I read to go deeper on this category's tools?: The DNS hub covers DNS Lookup in depth; the Networking & Infrastructure hub covers the IPv4 Subnet Calculator, MAC Address Generator, and Wake-on-LAN Packet Generator.
Why does this category have only 4 tools?: It's scoped deliberately narrow, covering only the foundational addressing/resolution mechanics — more advanced or specialized networking tools belong to the separate, larger Network Operations Lab category instead.

Related Categories

Other categories whose tools share a Developer Hub with Infrastructure Hub:

Network Operations Lab