Global DNS Lookup
Inspect DNS records across global authoritative nameservers with high-precision results.
Querying Authoritative Servers...
No Records Found
The nameservers answered, but published none of the record types we ask for. That usually means the domain is registered and not yet configured.
Check the registry recordLookup Failed
What is a Global DNS Record Lookup?
The Domain Name System (DNS) is often described as the phonebook of the internet. A DNS lookup is the process of querying authoritative nameservers to discover the exact DNS records (like IP addresses and mail routes) associated with a specific domain name.
Our free online DNS lookup tool allows you to perform real-time queries against authoritative servers. Whether you are troubleshooting email delivery issues, verifying domain ownership for third-party tools, or auditing your digital infrastructure for security vulnerabilities, our Global DNS Checker provides the raw technical data you need instantly.
- Enter the domain or hostname (e.g., example.com) into the search field and hit Lookup.
- Our tool queries global authoritative servers to retrieve all active records including A, MX, NS, and TXT.
- Compare the returned records against your intended configuration to ensure everything is pointing correctly.
Why DNS Monitoring Matters
- Email Deliverability: Incorrect MX or TXT (SPF/DKIM) records cause emails to bounce or land in spam.
- Website Uptime: If your A or AAAA records point to an offline server, your website goes down.
- Security Protection: Hackers use DNS hijacking to silently redirect your traffic. Monitoring DNS changes prevents this.
DNS Record Types Explained
These are the record types this tool queries, in the order it returns them. Understanding the different types is essential for effective IT management.
| Record | Role | What it does | When it breaks |
|---|---|---|---|
| A | Essential | Address record. Maps a domain name to an IPv4 address (e.g., 192.0.2.1). This is the record that decides which server answers when someone types your name into a browser. | Site unreachable |
| AAAA | Common | IPv6 Address record. The same job as an A record, for IPv6. Absent on plenty of healthy domains, but if you publish one it has to point somewhere that answers. | IPv6 visitors fail |
| CNAME | Common | Canonical Name record. Points one name at another name rather than at an address. Widely used for subdomains handed to a CDN or SaaS provider. | Subdomain dead-ends |
| MX | Essential for mail | Mail Exchange record. Specifies the mail servers responsible for receiving email for the domain, in priority order. No MX record means no inbound mail, silently. | Inbound mail bounces |
| NS | Essential | Name Server record. Identifies the authoritative servers that store the DNS records for a domain. A change here is the single highest-signal event in DNS: it means control of the zone moved. | Whole zone lost |
| TXT | Common | Text record. Used for SPF, DKIM, and site verification for services like Google Search Console. One malformed entry here is the most common cause of mail landing in spam. | Mail marked as spam |
| SOA | Essential | Start of Authority record. One per zone. Names the primary nameserver and the refresh timings other resolvers follow. You rarely edit it, but its absence means the zone is not properly delegated. | Zone not authoritative |
| CAA | Optional | Certification Authority Authorization record. Names which certificate authorities are allowed to issue certificates for the domain. Nothing breaks without it; with it, nobody else can quietly get a certificate for your name. | Certificate issued by anyone |
| SRV | Optional | Service record. Points a named service and protocol at a host and port. Mostly seen with VoIP, XMPP and Microsoft 365 autodiscovery. | Service discovery fails |
How to Read Your Results
Four patterns worth recognising in the output above, and what each one means for the domain.
No MX records at all
The domain cannot receive email, and nobody gets an error about it. Senders see the message accepted and then discarded upstream. If you expect mail here, this is the first thing to fix.
Several A records for one name
Normal, and usually deliberate. Resolvers rotate between them, which is how simple load balancing and failover are done. It becomes a problem only when one of the addresses stops answering.
A TXT record starting v=spf1
Your sender policy. There must be exactly one, and every service that sends on your behalf has to be listed in it. Two SPF records is the same as none, because receivers reject the ambiguity.
Nameservers you do not recognise
The most serious result on this page. Either someone moved the zone, or your DNS provider changed its hostnames. Both are worth confirming before anything else on the list.
Why DNS Monitoring is Critical for Business Continuity
While a one-time DNS lookup is useful for setup, continuous DNS monitoring is what protects businesses from catastrophic failure. DNS hijacking, unauthorized record changes, or registry-level errors can redirect your traffic to malicious sites or break your email flows without warning.
Domainyze provides automated DNS change detection that monitors your records around the clock. If an MX record is dropped or an A record points to a new IP, you'll receive an instant alert, allowing you to mitigate risks before they impact your users.
Understanding DNS Propagation
When you update a DNS record, it takes time for the changes to spread across the internet, a process known as DNS propagation. This can take anywhere from a few minutes to 48 hours, depending on the TTL (Time to Live) settings of your records.
Our Global DNS Lookup tool helps you verify if your changes have hit authoritative servers, which is the first step in successful propagation. If you've updated your records but don't see them here, it might be time to check your registrar's configuration.
The Results That Trip People Up
A DNS answer is only useful if you read it the way the resolvers do. The four cases where the output means something other than it first appears:
- Two TXT records both starting v=spf1, a misconfiguration, not redundancy. Receivers treat two SPF records as permanently invalid, which is worse than none. Merge them into one.
- No records vs a failed lookup: nameservers answering with nothing usually means a registered-but-unconfigured domain; a failed query means we could not reach them. The two need completely different fixes, so we report them separately.
- What you see vs what visitors see: this queries authoritative servers, so it shows what your provider publishes now. A resolver elsewhere may serve the old answer until its cache expires.
- Unfamiliar nameservers, the highest-signal result on the page. Either you migrated the zone or someone else redirected it. Confirm with your registrar before anything else, and consider change detection so the next move is not silent.
Why the Zone Is Worth Watching
Email that silently vanishes
A missing MX record or a broken SPF entry does not raise an error, senders see the message accepted, then discarded. Reading the zone is how you catch mail failures nobody bounces back to you.
A site that goes dark
If an A or AAAA record points to a server that stopped answering, the site is down for everyone whose resolver has the new answer. The record is the first place that failure shows.
A hijack you would not see
DNS hijacking redirects your traffic and mail by quietly changing records. A one-off lookup catches it only if you happen to look; continuous <a href="/features/dns-change-detection" class="font-semibold text-primary-emphasis hover:underline">change detection</a> catches it the moment it happens.
Certificates issued behind your back
Without a CAA record, any certificate authority can issue a certificate for your name. With one, only the authorities you name can, a control that lives entirely in the zone. Pair it with an <a href="/tools/ssl-certificate-checker" class="font-semibold text-primary-emphasis hover:underline">SSL check</a>.
Who Runs a DNS Lookup
The same query serves a different job depending on what you are protecting.
Site & Infra Operators
Verify a migration landed, confirm records point where they should, and catch a stale entry before it becomes an outage.
DNS monitoringEmail Administrators
Read the SPF, DKIM and DMARC records that decide whether your mail is trusted, and spot the duplicate SPF that quietly breaks it.
Email auth monitoringAgencies
Audit a client's zone before and after a handover so nothing points at the previous host once the project is live.
For agenciesSecurity Teams
Baseline the records that matter, nameservers, mail, CAA, and know the instant one of them moves without a change request.
For brand protectionWhere to Go From Here
A lookup answers the zone. These pick up what sits either side of it.
See who is authoritative
The registration record shows which nameservers the registry was told to delegate to, the level above the records themselves.
WHOIS lookupCheck the certificate
The zone routes the traffic; the certificate secures it. Confirm the name it resolves to is serving a valid, in-date certificate.
SSL checkerCatch the next change
A lookup is one snapshot. Change detection watches the zone around the clock and alerts you the moment a record is added, altered or removed.
DNS change detectionWatch your mail auth
Keep SPF, DKIM and DMARC under continuous watch so a broken record never quietly sends your mail to spam.
SPF/DKIM/DMARC monitoringFrequently Asked Questions
Common questions about DNS lookups, records, propagation, and monitoring.
What is a DNS lookup?
A DNS lookup queries Domain Name System servers to find the active DNS records (such as A, AAAA, MX, NS, TXT, or CNAME records) configured for a domain. It translates human-friendly domain names (like example.com) into machine-readable IP addresses and routing instructions.
How long does DNS propagation take?
When you update DNS records, it takes time for the changes to spread across global nameservers, a process called DNS propagation. While some updates take effect in minutes, complete propagation typically takes between 24 and 48 hours depending on the TTL (Time to Live) settings.
What does "TTL" mean in DNS?
TTL stands for Time to Live. It is a value (measured in seconds) that tells DNS resolvers and browsers how long to cache the record before checking the authoritative nameserver for a fresh update. A lower TTL (e.g., 300 seconds) enables faster updates during migrations.
Can I look up hidden or private DNS records?
No. DNS records are public by design, as they are required for routing traffic, email, and web services. While you cannot hide them, some records (like internal TXT or subdomains) are only discoverable if you query the exact hostname.
What is the difference between a lookup and continuous monitoring?
A lookup checks your DNS records at a single point in time. Continuous DNS monitoring (offered in our Pro and Business plans) actively checks your records at regular intervals and alerts you immediately if any records are modified, deleted, or point to unauthorized IPs, protecting you from DNS hijacking.
What are the most common DNS record types?
The most common records are A (points to an IPv4 address), AAAA (points to an IPv6 address), MX (routes email), NS (identifies nameservers), TXT (used for verification like SPF/DKIM), and CNAME (aliases one name to another).
Can I use this tool to verify my domain for Google Search Console?
Yes. You can use our DNS lookup to verify that your TXT verification records are correctly published and visible to Google's crawlers.
How do I know if my DNS is working correctly?
Your DNS is working correctly if the A and AAAA records point to your web server's IP and your MX records point to your mail provider. If these queries fail or return unexpected IPs, your site or email may go offline.
Why do I see multiple A records for some domains?
Many large websites use multiple A records for load balancing and redundancy. This allows traffic to be distributed across several servers, improving performance and uptime.
Does a DNS lookup show my personal contact information?
No. DNS records only contain technical routing data (IPs, hostnames, and text strings). Personal information like your name or address is stored in WHOIS records, not DNS.
Can I check subdomains with this DNS checker?
Yes. You can enter any valid hostname (e.g., api.example.com or blog.example.com) to inspect the specific DNS records for that subdomain.
Which record types does this tool check?
Nine: A, AAAA, CNAME, MX, NS, TXT, SOA, CAA and SRV. That covers where a name points, where its mail goes, who is authoritative for the zone, and the text records that carry sender policy and site verification. The reference table on this page lists exactly the same nine, in the same order.
The lookup returned no records. Does that mean the domain is broken?
Not necessarily, and it is a different answer from a failed lookup. Nameservers answering with nothing usually means the domain is registered and not yet configured. We report the two cases separately, because a zone that answered empty and a zone we could not reach need completely different fixes.
Why do I have two TXT records that both start with v=spf1?
That is a misconfiguration, and a common one. The specification allows exactly one SPF record per domain; receivers that find two treat the result as permanently invalid, which is worse than having none at all. Merge the two into a single record with all your sending services listed in it.
What should I do if the nameservers are not the ones I expect?
Treat it as urgent. A change of nameservers means control of the whole zone moved, which is either a migration you made or someone else redirecting your traffic and mail. Check with your registrar first, because the registrar is where a delegation is changed.
Does this tool show my records or the ones my visitors see?
It queries authoritative servers, so it shows what your DNS provider is currently publishing. Visitors may see something older for as long as their resolver caches the previous answer, which is why a change you can see here can take hours to reach everyone.
Start Monitoring & Catching Domains Today
Join founders, agencies, and domainers already protecting their portfolio. Your first 5 domains are free.
No credit card required • Cancel anytime
Guides for domain operators
Deep dives on domain names, DNS, SSL, acquisitions and portfolio management.
All guides →
Do All Pending Delete Domains Go Through Auctions?
Learn why not all pending delete domains go to auction. Explore pre-release sales, dropcatching mechanics, and multi-backorder bidding rules across registrars.
Domain Flipping 101: The Step-by-Step Guide for Beginners (2026)
Learn how to flip domains for profit. This beginner's guide covers buying and selling domains, valuation strategies, and the tools you need to succeed.
Maximizing ROI with Expired Domain Flipping in 2026
To maximize ROI with expired domain flipping in 2026, focus on predictive analytics, emerging industries, voice-search optimization, and leveraging tools like Domainyze.