DNS lookup

Query DNS records, domain registration (RDAP), and IP geolocation — enter a domain or IP and get the full picture.

Type

Resolver

—

Enter a domain or IP above and click Lookup

DNS records

Name	TTL	Type	Value

Registration (RDAP / WHOIS)

Loading…

IP / network info

Loading…

Running your own DNS? Pi-hole blocks ads and trackers at the DNS level for your whole network. A Raspberry Pi makes an ideal always-on host — low power, silent, and more than capable for DNS workloads. See Raspberry Pi kits →

What this tool actually queries

DNS record lookups go through Cloudflare and Google's public DNS-over-HTTPS resolvers, domain/IP registration data comes from rdap.org, and IP geolocation comes from ipwho.is — all three are real network requests to third-party services, which is why this is the one tool on the site marked makes a network request rather than fully local. There's nothing to hide here: that's simply what looking up DNS/WHOIS/geolocation data requires.

Reading the results

A record returns an IPv4 address; AAAA returns IPv6; MX shows mail routing with priority (lower number = higher priority); TXT often holds SPF/DKIM/domain-verification strings; NS shows the authoritative nameservers actually answering for the domain. RDAP replaced the old WHOIS protocol as the modern registration-lookup standard and is what this tool queries for ownership/registration data.

Why does this tool need to make a network request?

DNS records, domain registration data, and IP geolocation all live on external servers by definition — there's no way to look them up without a real request to a resolver, registry, or geolocation service. This is the one tool on the site that can't run fully offline, and it's disclosed as such.

What's the difference between DNS and RDAP/WHOIS?

DNS resolves a domain name to its actual records (IP address, mail servers, etc.) for live traffic; RDAP/WHOIS looks up who registered the domain and when. They answer completely different questions about the same domain.

Why would a domain have multiple A records?

Multiple A records is standard practice for load balancing or redundancy — DNS returns all of them and the client (browser, app) picks one, often rotating between requests. It's normal, not a misconfiguration.

Related tools

Networking

CIDR Aggregator

Paste a list of IP addresses or CIDR blocks and get the minimal set of CIDR ranges that covers them all. Useful for firewall ACLs and route summarization.

Open →

Networking

HTTP Status Code Reference

Searchable HTTP status code reference with descriptions, common causes, and usage notes. Filter by category: 2xx, 3xx, 4xx, 5xx.

Open →

Networking

MAC Address Vendor Lookup

Look up the manufacturer of any network device by MAC address. Queries the IEEE OUI database to identify the vendor from the first 3 octets.

Open →

Networking

PoE Budget Calculator

Add your PoE devices and check total draw against your switch's power budget — with common PoE class presets for APs, cameras, and phones.

Open →

Networking

Port Number Reference

Searchable reference of well-known TCP and UDP port numbers with service names and descriptions. Filter by protocol or port range.

Open →

Networking

IPv4 Subnet Calculator

Enter any IPv4 address and prefix length to instantly see network address, broadcast, usable hosts, subnet mask, wildcard mask, and a bit-level breakdown. Works for any /0–/32.

Open →

From the blog: The First Thing I Look At When a Network Is “Slow”

DNS via Cloudflare/Google DoH · RDAP via rdap.org · Geo via ipwho.is · Pi-hole and split-horizon zones won’t appear