IP, DNS, network and privacy tools.

Use focused IP, DNS, subnet, TLS, browser, and privacy utilities that explain what each live result measures, how to verify it, and where its limits begin.

14focused utilitiesEvery tool states what it measures and what it cannot conclude.

Identity

Read the public address and the network information attached to it.

IP address lookup

Inspect any public IPv4 or IPv6 address, including its network owner and approximate region.

Network

Resolve names, calculate ranges, and isolate connection clues.

DNS record lookup

Read the A, AAAA, MX, NS, TXT, and CNAME records currently published for a hostname.

Reverse DNS lookup

Ask the DNS system whether an IP address has an associated PTR hostname.

Hostname to IP lookup

Resolve a domain name to the IPv4 and IPv6 addresses returned by DNS.

CIDR and subnet calculator

Normalize an IPv4 or IPv6 CIDR block into its network, mask, inclusive range, address count, and conventional usable range.

Internet latency test

Measure repeated request latency to this server without presenting the result as download or upload speed.

Web

Inspect public HTTPS metadata without crawling page content.

SSL/TLS certificate checker

Check the SSL/TLS certificate for a public hostname, including its identity, issuer, and expiry.

HTTP response header checker

Make a safe HTTPS HEAD request and display the response metadata returned by a public site.

Privacy

Review visible signals and strengthen everyday credentials.

Secure random password generator

Create a random password locally on the server with the operating system's secure random source.

Password strength checker

Check estimated character-space entropy for a test password; submitted values are processed for the response and never stored.

Email header analyzer

Extract public relay addresses and reported SPF, DKIM, and DMARC outcomes from raw headers.

Browser fingerprint test

Test which browser, screen, language, time-zone, and platform signals ordinary JavaScript can observe.

VPN and proxy IP check

Compare the public IP reaching this server with the exit expected from a VPN, browser proxy, or company gateway.

Developer

Create safe example data for tests and documentation.

Random IPv4 and IPv6 generator

Produce syntactically valid random public IPv4 or IPv6 examples for fixtures and documentation.

Choose a diagnostic tool by the evidence you need

A toolbox is useful only when each instrument has a narrow job. These utilities are organized around address context, naming, ranges, web connections, local generation, and browser-visible signals. They do not simulate deep scans or turn one response into a security verdict. Begin with the smallest observable question, preserve the input and time, and combine results only when the underlying mechanisms genuinely connect.

Address and naming questions

Use IP lookup when the input is an address or hostname and the goal is address family, scope, reverse name, network owner, or approximate region. Use DNS lookup when the question is what records a resolver returns for a domain. Reverse DNS starts from an address and asks for a published pointer name. These outputs can disagree without either being broken because forward and reverse records are administered separately, caches have lifetimes, and a hosting platform can serve many names from one address.

Ranges and routing boundaries

Subnet and CIDR calculators perform address mathematics. They normalize a network, expose the prefix, and show the inclusive boundaries covered by a rule or route. That helps review allowlists, VPN pools, cloud subnets, and documentation. It does not show whether an address is assigned, reachable, safe, or authorized for testing. Compare calculated ranges with the actual configuration and keep IPv4 conventions separate from IPv6 behavior. When ownership matters, corroborate the range through the appropriate public registry or routing source.

Web and encrypted-connection checks

The TLS certificate checker examines the certificate presented by one public hostname from this environment. The HTTP header inspector makes a deliberately limited HEAD request. Both are snapshots of a particular endpoint, not site-wide audits. A valid certificate protects a named connection but does not certify a business. A header can be present yet ineffective on other paths. Test representative URLs with authorized browser tools and deployment records before making a material security or reliability decision.

Browser, privacy, and generated output

Browser signals describe values exposed to this origin during this visit. VPN and proxy pages report the connection that reaches this server. Neither view can inspect every application or certify anonymity. Password and random-address generators have different safety boundaries: a generated password should be stored in a reputable manager, while a generated IP can belong to a real system and is never permission to connect. The email-header reader should receive only redacted routing lines because raw headers may contain names, addresses, and internal details.

A practical reading sequence

Define the questionChoose

Run one focused checkObserve

Confirm elsewhereVerify

The sequence prevents a large collection of unrelated outputs from obscuring the one observation needed to answer the original question.

Page-specific evidence and interpretation guide
Starting point	Reasonable use	Important boundary
Name resolution	DNS or reverse DNS	Resolver, record type, cache time
Network range	Subnet or CIDR calculator	Normalized boundaries and policy
Web endpoint	TLS or header check	Hostname, path, method, and time

Continue through the site

Start with the address lookup, inspect a name through DNS records, or calculate a boundary with the subnet tool. The learning desk explains DNS, CIDR, and TLS certificates before the output is used in a larger investigation.