Site owners
Moving hosts or adding a CDN.
Ҧ
FREE TOOL
DNS Lookup: Check A, MX, TXT, NS and CNAME Records
A DNS lookup queries the Domain Name System to find the records stored for a domain, such as its IP address, mail servers and name servers. The WritoryBuzz DNS lookup tool lets you check A, AAAA, MX, NS, TXT, CNAME, SOA, CAA and SRV records using real DNS over HTTPS queries to Google DNS (8.8.8.8) or Cloudflare DNS (1.1.1.1).
Enter a domain, pick a resolver, choose a record type or All, and click Lookup. Results appear in seconds with no signup and nothing to install.
Run a DNS lookup aboveQuick start
1Type the domain
2Choose a resolver
3Select a record type
4Click Lookup
DNS Record Lookup
Results
Querying DNS over HTTPS...
Enter a domain above to begin.
Domain: -
Records found: 0
Resolver: Google
| Type | Name | Value | TTL |
|---|
A Record Across Independent Public Resolvers
This compares four genuinely independent public resolvers so you can see whether their caches agree. It is not a simulation of global geographic propagation, which would require querying from servers physically located in different regions.
sends a DNS over HTTPS query from your browser to Google DNS or Cloudflare DNS and shows the answer. What it does not do: it is not a worldwide propagation map. It compares what two major public resolvers return. Does not do WHOIS. For domain ownership data, use a WHOIS tool. Privacy: the page states that queries go from your browser directly to the resolver and not through WritoryBuzz servers.
What Is DNS, in Plain English?
DNS is the internet's phone book. People type names like example.com, but computers connect using IP addresses. DNS turns the name into the numbers. It also tells the world where to send email for the domain and which servers are responsible for it.
Behind each lookup, a resolver such as Google DNS or Cloudflare DNS asks the domain's authoritative name servers for the answer, then caches it for the time set in the record's TTL, which stands for time to live. Caching is why DNS changes do not appear everywhere at once.
¶”
How to Use This DNS Lookup Tool
-
1STEP 1 Type the domain, for example example.com, with no https:// and no path.
-
2STEP 2 Choose a resolver. Google DNS (8.8.8.8) or Cloudflare DNS (1.1.1.1).
-
3STEP 3 Select a record type, or All to see every supported type at once.
-
4STEP 4 Click Lookup and read the records, values and TTLs.
-
5STEP 5 Switch the resolver and look up again. If the two answers differ, one resolver may still hold an older cached record.
DNS Record Types Explained
| Type | Stores | Typical TTL | Common use |
|---|---|---|---|
| A | An IPv4 address | 300 to 3600 s | Points a hostname to a server. The first record to check when a site will not load. |
| AAAA | An IPv6 address | 300 to 3600 s | Same as A, for IPv6. |
| MX | Mail server and priority | 3600 to 86400 s | Routes email for the domain. Lower priority numbers are tried first. |
| NS | Authoritative name servers | 86400 s or more | Says which servers hold the domain's DNS records. |
| TXT | Free-form text | 300 to 3600 s | SPF, DKIM and DMARC email policies, plus ownership verification for Google and others. |
| CNAME | An alias to another hostname | 300 to 3600 s | Points a subdomain such as www to another name, often a CDN or hosted platform. |
| SOA | Zone administration data | Varies | Shows the primary name server, serial number and refresh timers. |
| CAA | Allowed certificate authorities | 3600 to 86400 s | Restricts which authorities may issue SSL certificates for the domain. |
| SRV | Host, port and priority for a service | 300 to 3600 s | Locates services such as SIP or some Microsoft 365 features. |
TTL values shown above are typical conventions. Your provider can set any value.
Citable definition
A DNS lookup is a query to the Domain Name System that returns the records published for a domain name, such as A records for IP addresses and MX records for mail servers. Results can differ between resolvers while cached copies expire.
A Record vs CNAME
An A record maps a name directly to an IPv4 address. A CNAME maps a name to another name, which then resolves further. A CNAME cannot sit on the bare root domain (example.com) because the root already needs other records such as NS and SOA. Use an A record, or your DNS provider's alias feature if it has one, for the root, and CNAME for subdomains like www.
How to Read Your Results
- Name: the hostname the record belongs to.
- Type: the record type.
- Value (data): what the record points to, such as an IP or a mail server name.
- TTL: the number of seconds a resolver may cache the answer. A TTL still counting down means you are seeing a cached copy.
- Empty result: the record may not exist, the name may be misspelled, or the domain may not be delegated. Check the NS records.
Checking Email Records: MX and TXT
Email problems often trace to DNS. Look up MX records first: they should list your mail provider's servers, such as Google Workspace or Microsoft 365, with the priorities your provider gave you. Then look up TXT records for the three common email authentication policies:
- SPF is a TXT record starting with v=spf1 that lists the servers allowed to send mail for your domain.
- DKIM is a TXT record published at a selector name, such as selector1._domainkey, that holds a public key for signing mail. You need to know the selector name to query it.
- DMARC is a TXT record at _dmarc.yourdomain.com that tells receivers what to do when SPF or DKIM checks fail.
Only one SPF record should exist per domain. Two SPF records is a common mistake that causes SPF checks to fail.
DNS Propagation, Honestly Explained
"DNS propagation" is the period after a change during which different resolvers return old or new values because of caching. It usually ends within minutes to 48 hours, depending mainly on the old record's TTL. A TTL of 3600 means a resolver may serve the old value for up to an hour after you change it.
This tool cannot show a true global propagation map. A real worldwide check needs servers in many physical locations. A browser-based tool cannot do that. What this tool can do is query two independent public resolvers, Google and Cloudflare. If one returns the new value and the other returns the old value, you have spotted stale caching at one provider.
To speed up a planned change, lower the record's TTL to around 300 seconds 24 to 48 hours beforehand, make the change, then raise the TTL again once things settle.
Who Uses a DNS Lookup
Marketers
Verifying a domain for Google Search Console or an email platform.
Developers and sysadmins
Debugging a site that will not load or an email that bounces.
Security teams
Reviewing CAA and TXT records.
SEO professionals
Checking that a domain points where it should after a migration.
Common DNS Mistakes
- Editing records at the wrong provider. Check the NS records to see where the zone is actually hosted.
- CNAME at the root domain. It is not allowed by the DNS rules and can break other records.
- Two SPF records. Merge them into one.
- Copy and paste errors in TXT values, such as stray quotes or line breaks.
- Testing before the TTL has expired. If you changed a record minutes ago, an old answer is expected.
- Confusing DNS with hosting. DNS points to a server. It does not host your site.
Honest Limits of This Tool
- It queries two public resolvers. It does not show what every ISP or country sees.
- It does not run WHOIS, so it will not show who registered a domain.
- It does not show your local computer's DNS cache or your router's settings.
- Results from public resolvers can differ from the authoritative answer while caches expire.
- It is a lookup tool. It does not change DNS, and it cannot fix a record for you.
Privacy
The tool sends a DNS over HTTPS query from your browser to dns.google or cloudflare-dns.com, depending on your choice. The page states that no query passes through WritoryBuzz servers. Google and Cloudflare, as the resolvers you choose, see the domain name you query under their own privacy policies.
Want to see where a domain's server is hosted? Copy the A record into the IP Address Lookup to find the network and approximate location. Slow site? Test it with the PageSpeed Checker.
Frequently Asked Questions
What is a DNS lookup?
A DNS lookup queries the Domain Name System to translate a domain name into IP addresses, mail servers and other records. It is how browsers and email systems find the right server.
Which resolvers does this DNS lookup tool use?
You can choose Google DNS (8.8.8.8) or Cloudflare DNS (1.1.1.1). Queries are sent over HTTPS from your browser to the chosen resolver.
How long does DNS propagation take?
Typically from a few minutes to 48 hours, depending on the old record's TTL. A TTL of 3600 seconds lets resolvers serve the old value for up to an hour.
Can this tool check DNS propagation across the world?
Not in the geographic sense. It compares answers from two public resolvers, Google and Cloudflare, which can reveal stale caching at one of them. A true global check needs servers in many locations.
What is the difference between an A record and a CNAME?
An A record points a name straight to an IPv4 address. A CNAME points a name to another name. CNAMEs cannot be used on the bare root domain.
How do I check MX records for a domain?
Enter the domain, select MX and click Lookup. The result lists mail servers with priority numbers. The lowest number is tried first.
How do I check SPF, DKIM or DMARC records?
Look up TXT records. SPF starts with v=spf1 and sits on the domain. DMARC sits at _dmarc.yourdomain.com. DKIM sits at a selector name that you need to know.
Does this tool store my queries?
The page states that no query passes through WritoryBuzz servers. Your browser talks directly to Google DNS or Cloudflare.
Is this the same as nslookup?
It answers the same kind of question as nslookup, but it runs in your browser using DNS over HTTPS instead of a command line. Results should match a command-line query to the same resolver. Look up a domain's DNS records now and compare both resolvers after any change.
“#
Ready to try the DNS Lookup?
Free to use. Open the tool and get your result in seconds.
Run a DNS lookup above