DNS records and worldwide DNS propagation checker
  • DNS Check

    Refresh: sec.
    Resolved DNS: --
    Unresolved DNS: --
caMarkham, Canada
Ravand Cybertech
caBurnaby, Canada
Fortinet Inc
caKelowna, Canada
Shaw Communications
caQuébec, Canada
Cogeco Peer 1
Note: Complete DNS Resolution may take up to 48 hours.


Whether you have recently changed your DNS records, switched web host, or started a new website - checking whether the DNS records are propagated globally is essential. DNS Checker provides a free DNS propagation check service to check Domain Name System records against a selected list of DNS servers in multiple regions worldwide. Perform a quick DNS propagation lookup for any hostname or domain, and check DNS data collected from all available DNS Servers to confirm that the DNS records are fully propagated.

DNS Propagation Checker - How to Check DNS Propagation Globally?

Perform a quick DNS propagation lookup for any domain. Our DNS Propagation Test tool features a comprehensive list of 100+ global DNS servers, which makes global DNS checks more effortless than ever. It is designed to collect, parse, and display all the DNS propagation results on the map, going beyond text-based propagation reports.

It visually represents how your DNS changes are propagated across different DNS servers in different regions globally. This enhances your understanding and makes identifying any regional variations or issues easier. Now monitor and manage your DNS records effectively.

Here’s how you can use our tool for performing a free DNS Propagation Test online:

Enter The Domain or Hostname

Get started by providing the website domain name for which you want to carry out a DNS propagation test.

Select DNS Record for Propagation Status Check

Select the DNS record whose propagation status you would like to check. Click on the drop-down menu right next to the search bar and choose any of the following records:

  • A record: contains the IPv4 address info of the hostname.
  • AAAA record: contains the IPv6 address info of the hostname.
  • CNAME record: also known as alias record. It points the sub-domain to its domain, like pointing www.dnschecker.org to dnschecker.org. Get comprehensive insights about the domain’s CNAME records with CNAME record lookup.
  • MX record: contains the info where the domain's email should be routed to and mail servers priority. Lookup MX record for more info about the domain’s MX records.
  • NS record: contains information about the authoritative nameservers of a domain. NS Checker will provide you with all the name servers associated with a domain.
  • PTR record: used in reverse IP lookup to map an IP address to a domain name, allowing the identification of the host associated with a particular IP address.
  • SRV record: specifies the location and configuration of a particular service, such as email or voice over IP (VoIP), allowing clients to discover and connect to the appropriate server.
  • SOA record: the start of authority is responsible for holding and specifying information about the DNS zone.
  • TXT record: is commonly used for other DNS records configurations like SPF, DKIM, or DMARC records.
  • CAA record: used to assist in SSL validation by highlighting which authorities can issue certificates for a domain.
  • DS record: acts as a delegation signer, maintaining a chain of trust between the parent zone and child zone. Use the DS record Lookup tool to dig deeper.
  • DNSKEY record: contains the public signing keys like Zone Signing Key (ZSK) and Key Signing Key (KSK). Check the DNSKEY record for more info.

Perform Quick DNS Propagation

Once everything is set, click “Search” to run our DNS propagation check tool. It will take a moment to display the results, highlighting all server locations with their respective propagation statuses.

Here are a few things to keep in mind while checking DNS propagation status:

  • ✔️ indicates that the DNS records have been propagated.
  • ❌ shows that the DNS records haven’t been propagated.

More clearly - the green tick shows that the requested DNS record is available in the DNS server, and the cross shows that it is not. The green tick may also mean that the DNS record matches the updated value that the user has set in the expected value field. In contrast, the cross may denote that the value does not match the expected or updated value (the user expects it to be).

How to Add a Custom DNS Server?

If you want to add a  DNS Server, do it easily with our tool. Simply click on the “+” button and enter the following information:

  • DNS Name
  • DNS IP
  • DNS Provider
  • DNS Map Latitude
  • DNS Map Longitude

The DNS Name and DNS IP address are compulsory to specify, or else it will not work.

Our tool will also allow you to add the custom DNS server to the public DNS list as required.

How to Add Expected Value of IP Address?

If your IP Address has been changed now, then leverage the smart controls to specify the expected value of the new IP address by highlighting its “regular expressions,” “containing numbers,” or “exact match number.”

Here's What Else You Can Do…

If required, you can go to the “DNS Lists” section to leverage our tool’s smart search capabilities. It will enable you to check the DNS propagation status of your website with respect to a specific:

  • IP Address
  • Continent
  • Country

Simply click on the respective IP address type, continent name, or country name (server location). Our DNS status checker will reload, allowing you to enter the hostname or IP and validate its propagation status accordingly.

Let’s say you would like to check the DNS propagation status of a website in Asia (continent). Click on it and then proceed as guided earlier. It will show you whether the given hostname DNS has been propagated in the Asia continent or not. The same goes for IPv4, IPv6, and all countries worldwide.

Frequently Asked Questions

Here’s the insider scope you need to know all about DNS!

What is Domain Name System?

Domain Name System (DNS) is a hierarchical decentralized system that maps domain names to IP addresses. It is the internet's equivalent of a phone book, mapping human-readable domain names to IP addresses.

What is DNS resolution?

DNS resolution translates the domain name into its server IP address. You need a site's IP address to know where it’s on the Internet.

The four DNS Servers work together (in a chain) to convert a domain name to its IP address, enabling the requested web resource to load on the user screen.

Here is how the DNS resolution process works:

  • Recursive DNS server (DNS resolver): These servers are the first in the DNS check process. Receive DNS queries from clients and resolve the human-readable domain name to an IP address. That server tracks the IP address for the searched domain or hostname.
  • Root DNS servers: These servers are at the top of the DNS hierarchy and provide a list of top-level domain (TLD) servers to resolvers.
  • TLD Name Servers: These servers return the authoritative name servers for each domain. These are responsible for handling the requests for specific top-level domains like .com, org, etc. The .com TLD name servers will return results for abc.com but not abc.org.
  • Authoritative DNS servers: These servers are the last stop in the DNS resolution process. The authoritative nameservers for the searched domain hold the actual DNS records and respond to queries with the correct IP addresses.

How does the DNS process work?

Suppose you request to open the URL https://xyz.com in your web browser's bar. Here’s how it works:

  1. Your browser sends a DNS query to a DNS resolver (recursive Server), usually provided by your Internet Service Provider (ISP).
  2. The recursive resolver checks its cache to see if it already has the requested DNS information for the domain name. If it does, it returns to your computer, and the process ends.
  3. If the recursive resolver doesn't have the DNS information in its cache, it sends a query to the root DNS servers. These servers maintain a database of all the top-level domain names, such as .com, .org, .net, etc.
  4. The recursive resolver then contacts the root DNS servers that respond to the query with the IP of appropriate TLD (Top-Level Domain) DNS servers.
  5. The TLD DNS servers respond to the query by referring to the authoritative DNS servers for the domain name. These servers are responsible for maintaining the DNS records for the domain.
  6. The authoritative DNS servers respond to the query with the requested DNS records for the domain name.
  7. The DNS resolver caches the updated/latest fetched DNS records and returns them to your computer, which can now be used for whatever purpose those records were requested.

What is DNS propagation?

DNS propagation is the time DNS changes take to be updated across the internet over the globe. It can take up to 48 hours to propagate worldwide. Use our Global DNS Propagation Checker for free to get a quick report on your DNS propagation status.

How do DNS records propagate?

When you update your DNS records, the changes may take up to 48 hours. During this period, ISPs worldwide update their DNS cache with new DNS information for your domain.

However, DNS records may take some time to propagate due to different DNS cache levels. Thus, some visitors might be directed to the old server’s IP until the DNS propagation process finishes worldwide. However, most visitors see updated DNS records shortly after they change. You can look up A, AAAA, CNAME, and additional DNS records lookup from our DNS lookup tool.

Why DNS propagation takes time?

Suppose you changed your domain's nameservers and requested to open your domain on the web browser. Your request will not go to the hosting directly. Each ISP node first checks its DNS cache, whether it has the DNS information for that domain. If it is not there, it will look it up by fetching DNS information from the authoritative DNS server of the domain to serve the user’s request. It also saves that info for future use to speed up the DNS lookup process. Thus, the new nameservers will not propagate instantly. ISPs have different cache refreshing levels resulting in some still having the old DNS information in their cache.

Why is DNS not propagating?

The ISPs across the world have different caching levels. The DNS client or the server may cache the information of the DNS records in its DNS cache. That information is temporarily cached, and DNS servers will go for the updated DNS information when TTL (Time to Live) expires.

Note: If your new DNS changes are still not reflecting, you can go for a DNS health check to ensure that your DNS changes are up to the mark and following the standards. You can also flush your DNS cache.

What will happen if the domain name does not exist?

The DNS server will return a name error, also known as an NXDomain response (for a non-existent domain), to symbolize that the query's domain name does not exist.

What is the port used by DNS?

DNS uses both TCP and UDP port 53. However, the most frequently used port for DNS is UDP 53. That is used when the client's computer communicates with the DNS server to resolve the domain name. When using the UDP 53 for DNS, the maximum size of the query packet is 512 bytes.

TCP 53 is used primarily for Zone Transfers and when the query packet exceeds 512 bytes. That is true when DNSSEC is used, which adds extra overhead to the DNS query packet. You can test all the server ports using a port scanner online.

What is DNS failure?

DNS failure means that the DNS server cannot convert the domain name into an IP address in a TCP/IP network. That failure may occur within the company's private network or the internet.

Which are the best DNS servers?

Some of the best Global DNS servers are as follows:

  1. Google Public DNS:
    • IPv4:
      • Primary:
      • Secondary:
    • IPv6:
      • Primary: 2001:4860:4860::8888
      • Secondary: 2001:4860:4860::8844
  2. OpenDNS:
    • IPv4:
      • Primary:
      • Secondary:
    • IPv6:
      • Primary: 2620:119:35::35
      • Secondary: 2620:119:53::53
  3. Quad9 (Malware Blocking Enabled):
    • IPv4:
      • Primary:
      • Secondary:
    • IPv6:
      • Primary: 2620:fe::fe
      • Secondary: 2620:fe::9
  4. DNS.Watch:
    • IPv4:
      • Primary:
      • Secondary:
    • IPv6:
      • Primary: 2001:1608:10:25::1c04:b12f
      • Secondary: 2001:1608:10:25::9249:d69b
  5. Comodo Secure DNS:
    • IPv4:
      • Primary:
      • Secondary:
  6. Cloudflare:
    • IPv4:
      • Primary:
      • Secondary:
    • IPv6:
      • Primary: 2606:4700:4700::1111
      • Secondary: 2606:4700:4700::1001

Public DNS Servers by country provide a complete list of all DNS servers, including the world's best IPv4 and IPv6 public DNS servers.