/dns

DNS Lookup Online - A, AAAA, MX, TXT, CNAME, NS

Look up DNS records (A, AAAA, MX, TXT, CNAME, NS) for a domain via Cloudflare DNS-over-HTTPS.

Requires network access. This tool sends your request to a third-party service to fetch the result. What you enter leaves your browser.

About the DNS lookup

The lookup is performed via Cloudflare’s DNS-over-HTTPS (DoH), so it works directly from the browser. The domain you enter is sent to Cloudflare (1.1.1.1), which returns the records.

  • A / AAAA, IP addresses (IPv4 and IPv6)
  • MX, mail servers
  • TXT, free text (e.g. SPF and verification)
  • CNAME, alias to another domain
  • NS, name servers for the domain

About this tool

DNS lookups translate a domain name into the IP addresses, mail servers and other records that make the internet work. This tool queries A, AAAA, MX, TXT, NS, CNAME and other record types directly in your browser through an open DoH (DNS over HTTPS) service. It is useful for troubleshooting email that does not arrive, checking SPF/DKIM/DMARC records, verifying that a domain really points to your hosting provider, or discovering which CDN a site is using. Queries run against public resolvers, so you can compare what actually gets returned to your users.

How to use it

  1. Enter the domain you want to look up, for example verktoy.dev.
  2. Choose record type (A for IPv4, AAAA for IPv6, MX for email, TXT for SPF/DKIM/DMARC, etc.).
  3. Click "Lookup", the answer appears within a second.
  4. Copy the value you need, or run several record types in sequence for a full picture.

Examples

A record
Inputverktoy.dev A
Output104.21.10.42 172.67.150.11
MX record
Inputgoogle.com MX
Output10 smtp.google.com.
An MX value consists of priority + mailserver. A low priority number is the highest rank.
TXT (SPF)
Inputverktoy.dev TXT
Output"v=spf1 include:_spf.mx.cloudflare.net ~all"

Common use cases

  • Debug email that fails to deliver or lands in spam.
  • Verify SPF, DKIM and DMARC after a migration.
  • Check that a domain now points to the new IP after a server move.
  • Find CNAME targets for CDN or SaaS services.
  • Confirm DNSSEC or new TXT verifications for services like Google Search Console.

Frequently asked questions

What is DNS over HTTPS (DoH)?
DoH sends DNS queries encrypted over HTTPS instead of the traditional UDP 53. This prevents network operators and ISPs from easily seeing which domains you resolve.
Why do I get different answers from different resolvers?
DNS answers are cached for anything from seconds to days. Just after a change some resolvers see the new value while others still serve the old one. The record’s TTL controls how long a cache entry lives.
What is a TTL?
Time-To-Live is the number of seconds a resolver is allowed to cache the answer. Short TTL means fast changes but more DNS traffic, long TTL gives slower rollout but better performance.
Can I look up internal domains?
No. The tool uses a public resolver that only sees global DNS records. Internal domains like "server.corp" must be looked up from inside the corporate network.

Technical background

DNS is hierarchical: the root servers know .no, .com, .dev and so on, and delegate to the nameservers registered on each domain. A full resolution starts at a recursive resolver (like 1.1.1.1 or 8.8.8.8) which asks the root, then the TLD, then the authoritative nameservers for the domain, and finally hands the answer back to you. Common record types: A (IPv4), AAAA (IPv6), CNAME (alias), MX (mail exchanger), TXT (free text, used for SPF/DKIM/DMARC and domain validation), NS (delegation), SOA (start-of-authority), SRV (services like SIP and XMPP) and CAA (which certificate authorities may issue for the domain). SPF lists the IPs allowed to send email for the domain, DKIM signs outgoing messages with a public key, and DMARC tells receivers what to do when SPF or DKIM fail. With DNSSEC enabled, answers are cryptographically signed so the resolver can verify nobody tampered with them on the way.