Skip to content
toolsbox

DNS Lookup

Query A, AAAA, MX, NS, TXT, SOA and CAA records on Cloudflare and Google DNS — plus SPF and DMARC checks.

  • Free
  • No sign-up

What is a DNS lookup?

A DNS lookup asks the Domain Name System what records a domain publishes: which IP addresses it points to, which servers handle its email, which name servers are authoritative and which text records prove ownership or define email policy. This tool queries the main record types in one pass and shows each answer with its TTL, the number of seconds resolvers may cache it.

Records are resolved through two large public resolvers, Cloudflare (1.1.1.1) and Google (8.8.8.8). Querying both lets you compare their answers side by side. When you have just changed a record, the two may disagree for a while, because each holds the old value until its cached TTL runs out. Seeing that difference is usually the quickest way to tell a propagation delay from a configuration mistake.

The lookup covers A (IPv4), AAAA (IPv6), CNAME, MX sorted by priority, NS, TXT, SOA and CAA. TXT records are labeled so you can tell SPF, DMARC and common verification tokens apart, and a short set of email checks confirms that MX records exist, that an SPF record is present with valid syntax, and that a DMARC record is published at _dmarc.yourdomain.

How to run a DNS lookup

  1. 1

    Enter the domain

    Type a domain or subdomain such as example.com or shop.example.com, without https:// or a path. Subdomains often have their own records, so query the exact hostname you are troubleshooting.

  2. 2

    Run the lookup

    The tool queries every supported record type through 1.1.1.1 and 8.8.8.8 and groups the answers by type.

  3. 3

    Check the core records

    Confirm A and AAAA point to your current host, that a CNAME is not sitting on a name that also needs other records, and that NS lists the provider you expect.

  4. 4

    Review the email checks

    Look at MX priority order, the labeled SPF record and the DMARC result. Fix any syntax warning before relying on the record.

  5. 5

    Compare resolvers

    If the two resolvers return different values, note the TTL. The mismatch should clear on its own once the cached record expires.

When to use a DNS lookup

Moving to a new host

After updating an A record, confirm both public resolvers return the new IP before you shut down the old server.

Fixing email deliverability

Missing or malformed SPF and DMARC records are a frequent reason mail lands in spam. Gmail and Yahoo require SPF, DKIM and DMARC for bulk senders, so verify all three are in place.

Verifying domain ownership

Google Search Console, Microsoft 365 and many SaaS tools verify ownership with a TXT record. Check that the token is published exactly as issued.

Auditing certificate authority rules

CAA records limit which certificate authorities may issue for your domain. If a certificate renewal fails, a CAA record that omits your CA is a likely cause.

Checking a domain before buying or linking

NS and SOA records show who runs DNS for a domain and when the zone last changed, which is useful context when evaluating a site.

Record types and common mistakes

MX records carry a priority number, and lower numbers are tried first. SOA holds the primary name server, the responsible contact and a serial number that increments when the zone changes. CAA records name the certificate authorities allowed to issue certificates, for example 0 issue "letsencrypt.org".

A CNAME cannot coexist with other records on the same name, which is why a bare apex domain such as example.com cannot normally be a CNAME. Providers work around this with flattening or ALIAS records that return A records to resolvers. Each domain should publish exactly one SPF record beginning with v=spf1; two SPF records cause a permanent error. SPF evaluation is also limited to 10 DNS-querying mechanisms such as include, a, mx and redirect, and exceeding that limit fails the check.

Propagation is not a broadcast. Resolvers simply cache answers for the TTL they received. Lowering a TTL to 300 seconds a day before a planned change shortens the window in which visitors see the old value, and you can raise it again afterward.

Frequently asked questions

Is the DNS lookup tool free?

Yes, the DNS lookup is free and requires no sign-up. You can query any public domain for A, AAAA, CNAME, MX, NS, TXT, SOA and CAA records, with email checks and resolver comparison included. Lookups are rate-limited per visitor to keep the service responsive for everyone.

What does the tool query, and is anything stored?

The tool queries only DNS records for the domain you enter, using the public resolvers 1.1.1.1 and 8.8.8.8. It does not contact your web server or mail server. Results are displayed to you and not stored, and lookups are rate-limited to prevent abuse.

Why do 1.1.1.1 and 8.8.8.8 show different results?

Different results almost always mean one resolver still has an older answer cached. Each resolver keeps a record until its TTL expires, so after a change one may update before the other. If the difference persists well beyond the TTL, check that your registrar points to the correct name servers.

How long does DNS propagation take?

DNS propagation takes as long as the TTL on the old record, plus any time for changes to reach your provider's name servers. A 300-second TTL clears within minutes, while an 86400-second TTL can take a full day. Changing name servers at the registrar can take longer because parent zone NS records often carry 48-hour TTLs.

What should a DMARC record look like?

A DMARC record is a TXT record at _dmarc.yourdomain that starts with v=DMARC1 and includes a policy, for example v=DMARC1; p=none; rua=mailto:reports@yourdomain. Start with p=none to collect reports, then move to quarantine or reject once SPF and DKIM pass for all legitimate senders.

Why is DKIM not shown in the email checks?

DKIM records live at a selector-specific name such as selector1._domainkey.yourdomain, and the selector is chosen by your email provider. Without knowing the selector, no tool can reliably list a domain's DKIM keys. Find the selector in your provider's settings or in the DKIM-Signature header of a sent message.