DNS Lookup

Look up DNS records for any domain name. Find A, AAAA, MX, CNAME, TXT and NS records.

What is DNS?

DNS (Domain Name System) is the internet's "phone book." When you type a domain name like "example.com" into your browser, DNS translates it into an IP address that your computer can use to find the right server.

Common DNS record types

A record
Points a domain to an IPv4 address (e.g. 93.184.216.34)
AAAA record
Points a domain to an IPv6 address
MX record
Specifies which mail server receives email for the domain
CNAME record
Alias that points one domain name to another
TXT record
Text information, often used for verification and email security (SPF, DKIM)
NS record
Specifies which name servers are authoritative for the domain

How to use DNS lookup

  1. Enter the domain name you want to check in the search field (e.g. example.com without www)
  2. Select which record types you want to see β€” or leave all selected for a full overview
  3. Click "Look up" to fetch the DNS records
  4. Review the results β€” each record type is shown in its own section
  5. Use the information for troubleshooting, verification or documentation

Tip: For subdomains (e.g. mail.example.com) enter the full address. Remember that DNS lookup shows what is currently configured β€” changes can take up to 48 hours to propagate (depending on TTL).

Why perform a DNS lookup?

DNS lookup is an invaluable tool for developers, IT administrators and everyday users alike. Here are some practical use cases:

  • Website troubleshooting β€” Check if A and AAAA records point to the correct server. If a site won't load, incorrect DNS configuration may be the cause.
  • Email issues β€” MX records tell you which server receives email. TXT records show SPF, DKIM and DMARC setup for email security.
  • Domain migration β€” When switching web hosting or providers: verify that NS records point to the correct name servers and that all necessary records have been copied.
  • Security checks β€” Confirm that TXT records for verification (e.g. Google Search Console) are in place, and that no unexpected CNAME aliases exist.

Common DNS problems and solutions

Website shows old content after migration
TTL (Time To Live) determines how long DNS responses are cached. Lower TTL to 300–600 seconds before migrating, wait for propagation, make the change, then raise TTL again.
Email lands in spam or doesn't deliver
Check MX records and ensure they point to the correct mail server. Verify SPF, DKIM and DMARC in TXT records β€” missing or incorrect configuration is a common cause.
"Server not found" or DNS errors
Confirm that NS records are correct at your domain registrar. Check that A/AAAA records exist for the root domain and www subdomain.
Subdomain doesn't work
Add explicit A, AAAA or CNAME records for the subdomain. CNAME cannot be used on the root domain β€” only A/AAAA.

Frequently asked questions about DNS

What if the DNS lookup returns no results?
This can mean the domain doesn't exist, hasn't been configured with DNS records yet, or the name servers aren't responding. Try checking if the domain is registered, and wait a few minutes in case of temporary network issues.
How long does it take for DNS changes to take effect?
Typically 15 minutes to 48 hours, depending on the TTL (Time To Live) set on the records. With low TTL (e.g. 300 seconds) changes propagate faster. Global DNS propagation can take up to 24–48 hours.
What is TTL in DNS?
TTL (Time To Live) specifies how many seconds a DNS record can be cached by resolvers and clients. Low TTL (300–600) makes changes propagate faster but increases load on DNS servers. High TTL (3600+) reduces load but makes changes take longer to take effect.
Can I change my DNS server?
Yes. You change NS records at your domain registrar (e.g. Namecheap, GoDaddy) to point to different name servers. This transfers control of DNS configuration to the new provider. The change can take up to 48 hours to propagate.
What's the difference between authoritative and recursive DNS servers?
Authoritative DNS servers hold the official DNS information for a domain and answer directly for it. Recursive DNS servers (like 8.8.8.8 or 1.1.1.1) query other servers on behalf of the user and cache responses. Our tool uses recursive servers to fetch information.
Why is DNS important for email security?
DNS is used for SPF (Sender Policy Framework), DKIM and DMARC β€” all stored as TXT records. SPF specifies which IP addresses can send email for the domain, DKIM cryptographically signs messages, and DMARC tells recipients how to handle failed checks. Without these, email can easily be spoofed.

Related Articles