Query DNS records for any domain
DNS Lookup queries the Domain Name System for a hostname and returns its published records, letting you inspect A and AAAA address records, MX mail routing, NS delegation, CNAME aliases, TXT strings (SPF, DKIM, DMARC, domain verification), SOA zone data, and PTR reverse entries. Enter a domain, choose the record type, and see the raw values along with each record's TTL.
It is used by system administrators verifying a new zone, email deliverability engineers checking SPF and DKIM alignment, developers debugging a stale CNAME after a migration, and anyone confirming that a domain resolves correctly before pointing traffic at it.
DNS is a hierarchical, distributed database. A resolver starts at the root servers, is referred to the top-level domain servers (for example .com), then to the authoritative name servers listed in the domain's NS records, which return the final answer. This tool performs a recursive query so you receive the resolved record set directly rather than a chain of referrals.
Every record carries a TTL (time to live) measured in seconds, which tells caches how long they may reuse the answer before re-querying. A common gotcha during migrations: an old A or CNAME value with a 3600-second TTL can linger in resolver caches for up to an hour after you change it. Record types serve distinct roles: A maps a name to an IPv4 address, AAAA to IPv6, CNAME aliases one name to another, MX lists mail exchangers with priority values, NS delegates the zone, SOA holds serial and refresh timers, and TXT stores free-form text used for SPF, DKIM, DMARC, and ownership verification.
Because different resolvers may cache different answers, a value shown here can occasionally differ from what your local network returns until propagation completes.
Yes, it is free to use with no account required. The lookup runs from our server against public DNS resolvers; we only send the domain name you enter, and we do not sell or publish your query history. Note that the domains you look up are public information visible to any DNS resolver.
This usually means caching or propagation. A recently changed record may still be cached by your local resolver until its TTL expires, while our resolver may hold a fresher or staler copy. Waiting out the TTL and re-checking normally resolves the discrepancy.
An A record points a name directly to an IPv4 address, while a CNAME points one name to another name (an alias) that is then resolved. You cannot have a CNAME at the zone apex (the bare domain) alongside other records like MX or NS.
Select the TXT record type. SPF appears as a string beginning with v=spf1, DMARC lives at the _dmarc subdomain and begins with v=DMARC1, and DKIM keys are published at a selector subdomain such as selector._domainkey. Query those specific hostnames to see each value.
MX records include a preference value where a lower number is tried first. If two records share the same value, mail servers balance between them; higher-numbered hosts act as fallbacks when the preferred server is unreachable.
Yes. Choose the PTR type to find the hostname associated with an IP address. Reverse records live in the in-addr.arpa (IPv4) or ip6.arpa (IPv6) zones and are configured by whoever controls the IP block, so not every address has one.
A single DNS TXT string is limited to 255 characters, so long values such as DKIM public keys are split into multiple quoted chunks that clients concatenate. This tool shows the chunks as published; joined together they form the complete value.