DNS Cache Check

Our DNS Cache Checker tool enables you to instantly inspect what DNS records are currently cached across global resolvers, ensuring your domain is serving the correct and most up-to-date information to users worldwide.

About DNS Cache Checker

HasheTool's DNS Cache Checker lets you quickly look up what DNS data is currently stored in the cache of major DNS resolvers around the world. When you update a DNS record, the old data doesn't disappear immediately; it stays cached on resolvers until the TTL (Time To Live) expires. Our tool helps you see exactly what cached records are being served to your users right now, how much TTL is remaining, and which resolvers have already picked up your latest changes.

Whether you're troubleshooting a slow DNS update, investigating email delivery issues, or verifying a recent migration, HasheTool's free DNS Cache Checker gives you real-time visibility into cached DNS data, no technical setup required.

DNS Cache Checker: Inspect Cached DNS Records Across Global Resolvers

DNS caching is a fundamental part of how the internet works, but it can also be the source of confusing problems. When your website loads an outdated IP address, your emails bounce unexpectedly, or your DNS changes seem to be "stuck," cached DNS data is often the culprit. HasheTool's DNS Cache Checker tool gives you instant insight into what DNS records are currently cached and how long they will remain cached before refreshing.

This free tool is used by developers, system administrators, IT teams, and domain owners who need fast and accurate visibility into the current state of their DNS cache across multiple global resolvers.

How to Use the DNS Cache Checker on HasheTool

Getting started with HasheTool's DNS Cache Checker is quick and straightforward:

1. Enter your domain name or hostname (e.g., example.com or mail.example.com).
2. Select the DNS record type you want to inspect (A, MX, CNAME, TXT, etc.).
3. Click "Check DNS Cache."
4. Review the results to see the currently cached record values, TTL remaining, and which resolvers are returning different data.

Our tool queries multiple major DNS resolvers, including Google (8.8.8.8), Cloudflare (1.1.1.1), and regional resolvers across North America, Europe, Asia, and beyond to give you a comprehensive global picture.

What Is DNS Caching?

DNS caching is the process of temporarily storing DNS query results on a resolver or device so that future requests for the same domain can be answered faster without repeating the full lookup process.

When a user visits your website for the first time, their device asks a recursive DNS resolver for the IP address associated with your domain. The resolver fetches this information from the authoritative nameserver and stores it locally for a set period of time. This stored copy is called a DNS cache entry.

Every DNS record has a TTL (Time To Live) value, a number measured in seconds that tells resolvers how long to keep the cached record before fetching a fresh copy. Until that TTL expires, resolvers will continue serving the cached data, even if you have already updated the record at the source.

What Is a DNS Cache Checker?

A DNS Cache Checker is a diagnostic tool that queries DNS resolvers directly to retrieve the currently cached version of a DNS record for a given domain. Unlike a standard DNS lookup that fetches live data from the authoritative nameserver, a cache checker shows you the data that real-world resolvers are actively serving to users, including any outdated or stale records still within their TTL window.

This makes it an essential tool for:

• Verifying whether a DNS update has been picked up by major resolvers
• Diagnosing why some users see old content after a migration
• Identifying how much TTL time remains before a cached record expires
• Comparing cached values across different geographic regions

How DNS Caching Works (Technical Breakdown)

Understanding the DNS caching process helps explain why cached records sometimes confuse updates:

Step 1: User makes a request: A visitor's browser tries to load your website and needs to resolve your domain to an IP address.

Step 2: Local cache check: The device checks its own local DNS cache first. If a valid cached entry exists, it uses it immediately without any further lookup.

Step 3: Recursive resolver query: If no local cache exists, the request goes to a recursive DNS resolver (typically your ISP or a public resolver like Google or Cloudflare). The resolver checks its own cache.

Step 4: Full resolution if needed: If the resolver has no cached entry, it performs a full DNS resolution, querying root servers, TLD servers, and finally the authoritative nameserver for your domain.

Step 5: Cache is stored: The resolved record is cached by the resolver for the duration of the TTL value on that record.

Step 6: TTL countdown: Every second, the TTL counts down. Once it reaches zero, the cached entry is discarded, and a fresh lookup is performed on the next request.

This entire chain is why DNS changes do not take effect instantly everywhere; each resolver in the chain must wait for its cached copy to expire before fetching the updated record.

What Is TTL and Why Does It Matter?

TTL, or Time To Live, is a value set on every DNS record that controls how long resolvers are allowed to cache that record. It is measured in seconds.

Common TTL values and what they mean:

A high TTL means resolvers cache the record for longer, reducing DNS query load but slowing down propagation of any changes. A low TTL means resolvers refresh more frequently, speeding up propagation but increasing query volume to your nameserver.

HasheTool's DNS Cache Checker displays the remaining TTL on cached records so you know exactly how long before a resolver fetches a fresh copy of your updated record.

DNS Record Types You Can Check

HasheTool's DNS Cache Checker supports all major DNS record types:

A Record: Cached IPv4 address mapping for your domain, the most commonly checked record during website migrations.

AAAA Record: Cached IPv6 address mapping, important for modern infrastructure and IPv6-enabled networks.

CNAME Record: Cached alias records pointing one hostname to another, frequently used for subdomains and CDN configurations.

MX Record: Cached mail exchange records, critical for diagnosing email delivery issues after switching email providers.

TXT Record: Cached text records, including SPF, DKIM, and DMARC, are essential for email authentication troubleshooting.

NS Record: Cached nameserver records, important to check after changing DNS providers or nameservers.

SOA Record: Cached Start of Authority records containing zone serial numbers and administrative data.

CAA Record: Cached Certificate Authority Authorization records controlling SSL certificate issuance.

Common Reasons to Check DNS Cache

After updating a DNS record: Verify whether major resolvers have already picked up your change or are still serving the old cached value.

During a website migration: Confirm which regions are being directed to your new server and which are still hitting the old one due to cached A records.

Email delivery problems: Check whether MX or SPF records are being cached correctly or if outdated values are causing mail failures.

After changing nameservers: Inspect whether NS records have updated across resolvers and whether the new nameservers are being served correctly.

Investigating regional inconsistencies: Understand why users in one country see your site correctly while users in another location experience issues.

Verifying TTL changes: Confirm that your TTL reduction has taken effect before making major DNS changes.

How to Clear or Flush DNS Cache

While you cannot force third-party resolvers to clear their cache, you can flush the DNS cache on your own device and browser to ensure you are seeing the freshest available data.

Windows:

ipconfig /flushdns

macOS:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Linux:

sudo systemd-resolve --flush-caches

Google Chrome Browser: Navigate to chrome://net-internals/#dns and click Clear host cache.

Cloudflare Resolver (1.1.1.1): Visit https://1.1.1.1/purge-cache/ to request a cache purge for a specific domain on Cloudflare's resolver.

Google Public DNS: Visit https://developers.google.com/speed/public-dns/cache to flush a record from Google's public DNS cache.

Flushing your local cache is useful for personal troubleshooting, but keep in mind that other users and resolvers around the world will still serve cached data until their own TTLs expire.

Why Use HasheTool's DNS Cache Checker?

• Real-time cache lookup from multiple global resolvers, including Google, Cloudflare, and regional ISPs
• TTL display so you know exactly how long before cached records expire
• Supports all major DNS record types for complete coverage
• Beginner-friendly interface with clear, easy-to-read results
• No sign-up required — completely free with unlimited checks
• Trusted by developers, IT teams, and domain administrators worldwide

Common Use Cases

• Diagnosing why DNS changes are not visible to all users after an update
• Verifying cached MX records during email provider migrations
• Confirming TTL expiry timing before making major DNS changes
• Checking whether CDN or load balancer CNAME records are cached correctly
• Investigating inconsistent website behavior across different geographic regions
• Pre-launch DNS verification for new domains and servers

Check Your DNS Cache Instantly

Stop guessing what DNS data your users are actually receiving. Use HasheTool's free DNS Cache Checker to inspect cached records, monitor TTL countdowns, and ensure your domain is serving the correct information to users everywhere.