Privacy controls
CyberFurl can load analytics only after you opt in. Core product features work without analytics consent.
Check DNS cache status across global resolvers. See which resolvers have cached your records, what TTL values they report, and how long until cache expires.
DNS caching is the mechanism by which DNS resolvers store responses to queries for a period specified by the TTL (Time To Live) value in the DNS record. When a resolver receives a query, it first checks its cache. If the record is present and the TTL hasn't expired, it returns the cached response instantly without querying authoritative name servers. This dramatically speeds up repeated lookups and reduces load on authoritative servers. However, caching also means changes to DNS records won't be visible until cached entries expire across all resolvers that have previously queried the domain.
Understanding cache status helps predict propagation time, diagnose why some users see old records, optimize TTL values for planned changes, and verify that DNS changes are actually taking effect.
Not checking cache before planned changes, setting TTL too high, expecting instant global updates, not understanding that each resolver maintains its own independent cache, and not using TTL as a planning tool.
Type the domain to check cache status for.
We query DNS resolvers across multiple global locations.
We inspect whether responses come from cache or fresh lookups.
Remaining TTL values are reported per resolver and record type.
Checks whether each queried resolver returned a cached response or performed a fresh lookup. A cached response indicates the resolver has recently queried your domain.
Reports the remaining TTL (Time To Live) for cached entries. Shows how many seconds remain until the cache expires and a fresh lookup will be performed.
Tests cache status across resolvers in North America, Europe, Asia, and other regions. Cache state varies by resolver and location — some may be fresh, others cached.
Separates cache results by record type (A, AAAA, MX, TXT, NS, CNAME). Different record types may have different TTLs and cache states across resolvers.
Calculates the percentage of resolvers that returned cached responses versus fresh lookups. A high cache hit ratio indicates efficient DNS caching.
By showing which resolvers still have old cached data, you can estimate how long until DNS changes are globally visible. Essential for migration planning.
Automate DNS cache checks, track TTL expiration across global resolvers, monitor cache hit ratios, and get alerted when propagation is incomplete.