DNS translates names into network addresses. Enter a hostname only—without a path—to check whether the LumaProbe server can retrieve public A or AAAA records.
A successful result confirms public resolution from this server, not every resolver worldwide. A failure may be temporary, local to a DNS provider, or caused by a misspelled or unpublished domain.
The checker validates a public domain name, then asks the LumaProbe server resolver for its A and AAAA records. It reports up to eight distinct IPv4 or IPv6 addresses and the time taken by that server-side lookup. It does not query private names or display every DNS record type.
Because resolution happens on the server, the test answers “does this name resolve from LumaProbe’s resolver?” It does not directly test the DNS cache in your browser, device, router or provider. That distinction makes comparison with your affected device important.
Enter only a public hostname such as example.com. Do not include a path, account name, internal host or router address. If you are diagnosing one affected device, first copy the exact hostname that fails rather than relying on memory or a search result.
Run the check once, then compare the same hostname using the affected device and a known working public domain. Pausing downloads or changing from Wi-Fi to Ethernet will not normally repair a DNS record; those comparisons belong to connection testing, not to this server-side lookup.
A returned address confirms that public address records were available to the server at that moment. Different resolvers can return different addresses because of caching, geographic routing, load balancing or a record change. A failed lookup may reflect an invalid name, missing records, propagation or a temporary resolver problem.
If LumaProbe resolves a name while one device does not, focus on that device’s cache, configured resolver, VPN, filtering or router. If multiple independent resolvers fail, the domain owner or authoritative DNS configuration may be involved.
The result comes from the resolver used by the LumaProbe server. It does not read the DNS cache in your browser, router or provider and it does not show worldwide propagation. A result can therefore differ from another resolver without either result being fabricated.
This quick checker returns public A and AAAA address records only. It does not validate DNSSEC, mail delivery, authoritative delegation or every record type. Domain administrators should confirm important changes with their authoritative DNS provider and a specialist resolver.
Check the spelling and try a known working domain. Restarting the browser or device can clear some transient state; operating systems also provide documented DNS-cache commands. Avoid copying unknown resolver addresses from forums.
A reputable public resolver can be used as a controlled comparison, but changing DNS affects privacy and filtering. Save the original automatic settings so they can be restored. Domain owners should inspect authoritative records and DNSSEC with specialist tools.
Read the complete LumaProbe test methodology and privacy notes →
This quick tool returns public A and AAAA address records. It does not display mail, TXT, DNSSEC or every authoritative record.
No. The lookup is made by the LumaProbe server resolver. A different result on your device helps identify a local cache, resolver, VPN or filtering difference.
No. Resolver caches and geographic answers differ. Domain owners should confirm important changes with authoritative and multi-resolver tools.