THE NETWORK FIELD GUIDE
Choose the Tool. Understand the Answer.
Start with the question you need to answer. These tools explain address space and resolver responses without pretending to measure more than they do.
01 / ADDRESS SPACE
Read the Prefix. Find the Range.
Understand CIDR boundaries, host counts, membership and exact range coverage.
5 min read02 / RESOLVER VIEWSKnow Why DNS Answers Differ.
Read status, TTL, DNSSEC and PTR records without mistaking a snapshot for proof.
5 min read03 / IPv6Make a Long Address Readable.
Understand compression, scopes and exact 128-bit address arithmetic.
4 min read04 / CONNECTIONSEstimate the Transfer, Honestly.
Separate bits from bytes and overhead assumptions from real throughput.
4 min readYour Question → Your Tool
| If You Need To… | Start Here | Keep in Mind |
|---|---|---|
| Find a network boundary or host count | Subnet Calculator | The example prefix is illustrative, not discovered. |
| Normalize or convert an address | IP Inspector | A broad scope label is not a live assignment or security verdict. |
| Check whether an address falls in a block | CIDR Membership | Membership includes the block boundaries; it does not grant access. |
| Represent an exact inclusive range | Range to CIDR | Aligned blocks cover the range, with nothing extra. |
| Read a public domain’s records | DNS Lookup | The answer comes from a recursive resolver, not directly from every authority. |
| Check a second recursive view | Resolver Comparison | Different answers do not automatically mean a fault. |
| Look for a published IP hostname | Reverse DNS | No PTR is possible; a name is not proof of identity. |
| Estimate a file transfer duration | Transfer Time | An estimate is not a measured speed test. |
Five Local Tools. Three Live Lookups.
Subnet, inspector, membership, range and transfer calculations run in your browser. DNS, comparison and reverse DNS send a query to this service, which asks the selected public resolver over HTTPS. No ping, port scan, login or device configuration takes place.
A Small Field Checklist
- Use the actual address, prefix or record type relevant to the issue.
- Read status and limitations before treating an empty result as an error.
- Cross-check important results with your authoritative configuration or a second independent method.
- Keep customer data and internal network plans out of shared screenshots and support messages.
- Record what you tested and when. DNS and network conditions can change.