Network & web tools
Subnet maths, URL parsing and header inspection in the browser.
Network work is arithmetic that is easy to get wrong by one bit and awkward to redo. How many usable addresses does a /27 hold, where does the next non-overlapping block start, which parts of a long URL are actually query parameters, what is a response header telling you about caching. These tools do that arithmetic and that parsing locally, which keeps internal addressing plans and private URLs off other people's servers.
Tools in this category
12About these tools
Subnets and CIDR, without the off-by-one
A /24 gives 256 addresses but only 254 usable ones, because the first is the network address and the last is broadcast. That subtraction is where most planning errors start. A calculator that shows the network, broadcast, first and last usable host and the total count for any prefix removes the guesswork, and makes it obvious when two ranges you intended to keep separate actually overlap.
Reading a URL precisely
A long URL packs scheme, host, port, path, query and fragment into one string, and percent-encoding hides the boundaries. Parsing it into labelled parts shows which parameters are duplicated, which values were double-encoded, and where a tracking tag was appended twice — all things that are invisible when you are reading the raw string.
Headers explain behaviour
When a page will not cache, a request is blocked by CORS, or a redirect loops, the answer is almost always in the headers rather than the body. Decoding them into plain statements about caching lifetime, allowed origins, content type and security policy turns a wall of key-value pairs into an explanation you can act on.