DNS lookup and dig-style record search

Query public DNS records for any domain—A, AAAA, MX, TXT, NS, CNAME, or SOA—with tab-separated output similar to dig. Choose Cloudflare or Google public resolvers over DNS-over-HTTPS from your browser.

Lookup DNS Now helps administrators, site owners, and students verify that a domain publishes the records they expect before cutover or troubleshooting. Enter an apex or subdomain, pick a record type, and read TTL plus_rdata in a copy-friendly block. The tool does not perform authoritative zone transfers, reverse DNS for arbitrary IPs, or DNSSEC chain validation—it mirrors what a public resolver returns at query time, which is what most browsers and mail systems use in practice. Use it when you need a quick public record check without installing dig: compare nameservers after a migration, confirm MX before sending mail, or copy TXT values for domain verification. Results stay in this browser session; nothing is written to a server-side account. Prefer authoritative lookups when you are diagnosing propagation delays, and treat any cached answer as a snapshot in time rather than a guarantee for every resolver worldwide. [batch-a-home-pass-2026-11-13]

Quick start

1. Type a domain name (example.com or mail.example.com) without a path.
2. Choose the record type you need—A/AAAA for web, MX for mail, TXT for verification strings.
3. Pick a public resolver (Cloudflare or Google DNS-over-HTTPS).
4. Press Look up DNS and copy the dig-style lines for tickets or runbooks.

When to use something else

• Check web host: Look up A and AAAA for www.example.com after changing hosting.
• Verify email: Query MX and TXT to confirm mail routing and SPF/DMARC presence.
• Delegation audit: Compare NS answers against your registrar glue before a migration.

Limitations

• Results reflect the selected public resolver, not hidden authoritative-only views.
• Some resolvers rate-limit or truncate large responses; retry or switch resolver if needed.

FAQ

Is this the same as running dig on my laptop?

It is similar in intent: you pick a name and record type and read RDATA with TTL. The difference is the transport—this page asks a public DNS-over-HTTPS resolver instead of whatever recursive server your OS uses. That makes it useful on locked-down networks where a terminal dig is unavailable, and for comparing answers when you suspect local resolver cache.

Do you store the domains I look up?

This static app does not keep a server-side query log or account history. The public resolver you select still sees the query under its own privacy policy, just as dig against 1.1.1.1 would. Prefer example.com-style names when you are only testing the UI.

Why do I get no answers?

The name may not exist (NXDOMAIN), the type may be empty for that label, or the resolver may be filtered on your network. Try another record type, switch between Cloudflare and Google DoH, and confirm the spelling without a URL path or scheme.

Can I look up reverse DNS (PTR)?

Not in this version—enter hostnames only. For PTR checks, use dig against an in-addr.arpa name or a dedicated reverse-lookup utility. Forward A/AAAA, MX, TXT, NS, CNAME, and SOA checks cover most cutover and mail-verification workflows.

Publisher: SBFChoice. This free browser utility is maintained by the publisher. No ad units are shown in this configuration. The homepage may include Google AdSense publisher verification (ads.txt and an account script only on this page). See the Privacy Policy.