DNS Lookup

Overview

Check the DNS records for any domain from your browser. Pick a record type (A, AAAA, MX, TXT, NS, CNAME, SOA or CAA) and a resolver, and you get each record with its TTL and value. The domain you type goes to Cloudflare or Google over HTTPS, never through a server of ours. It's a quick stand-in for dig when you're checking DNS or mail settings.

Check DNS changes went liveCompare A or CNAME records on both resolvers after an update to see whether the new values are live.
Debug email deliveryCheck MX and TXT (SPF, DKIM, DMARC) records to make sure your mail setup is right.
Audit a domain's setupRead NS, SOA and CAA records to see who runs a domain's DNS and who may issue its certificates.

Key features

A, AAAA, MX, TXT, NS, CNAME, SOA and CAA records
Cloudflare (1.1.1.1) or Google (8.8.8.8) as resolver
DNS-over-HTTPS, straight from your browser
TTL and values in a clear table
Plain messages for NXDOMAIN and resolver errors
No server of ours in between

Set

Network Tools 03

Neighbours

01 What Is My IP Address 02 Internet Speed Test 03 Audio Transcriber 04 Run AI in the browser 05 Invoice Builder 06 Markdown Editor & Live Preview

Specification

Command: network.dns_lookup
Set: Network
Input: text
Output: —
Max file: no limit
Batch: single file

Runtime

Engine: DoH · LibreSpeed
Threads: single
Isolated: —
WebGPU: —
Memory: —

Transport 0 B

Network use: needed to take the measurement.

Keys

Search: ⌘K
Panels: ⌘1 · ⌘2
Full width: F
All keys: ⌘/

How it works

Enter a domain

Type a domain like example.com and pick a record type.

Pick a resolver

Choose Cloudflare or Google; your browser asks it directly over HTTPS.

Read the records

Records appear with their type, TTL and value; switch types to check mail, text or nameserver records.

Frequently asked

Does this send my query to your server?

No. Your browser sends the domain straight to the resolver you pick (Cloudflare or Google) over HTTPS. We never see what you look up.

What does NXDOMAIN mean?

The domain doesn't exist in DNS. Check the spelling first, since a typo is the usual cause.

Why do I see different results from different resolvers?

Resolvers cache records for their TTL, so one may still give the old answer after a change. Comparing Cloudflare and Google shows whether a change has spread.

Keys

Search: ⌘K
Panels: ⌘1 · ⌘2
Full width: F
All keys: ⌘/