DNS Lookup
Check DNS A records for a domain through DNS over HTTPS and inspect returned addresses directly in your browser.
Your result will appear here.
DNS Lookup online
Look up a domain's A records — the IPv4 addresses the name resolves to — through Google's public DNS-over-HTTPS resolver, straight from your browser.
How to use this tool
- Enter a domain name such as example.com (a trailing dot is trimmed for you).
- Click Run Tool. The query goes to Google's DNS-over-HTTPS JSON API and the A records come back.
- Read the addresses and their TTLs in the result.
Common uses
Checking that a DNS change has propagated, confirming which server a hostname currently points at, comparing the answer you get against your registrar's settings, and diagnosing "site works for some people" reports that are usually stale caches.
How it works
The tool sends your query to dns.google/resolve — the same resolver data that 8.8.8.8 serves — and displays the A records in the answer, each with its TTL (how many seconds other resolvers may cache it). This is one resolver's view from one moment: DNS is a cached, distributed system, so a record changed five minutes ago can legitimately answer differently here, at your ISP and on your phone for a while.
Worked example
Look up example.com and the answer is a short list of IPv4 addresses (the exact addresses rotate; the domain is anycast and multi-homed) each with a TTL in the hundreds-to-thousands of seconds. If you changed your own A record an hour ago and the TTL says 3600, the old address can keep answering from caches for up to that hour — the TTL counts down from when each cache learned it, not from when you edited it.
Privacy and browser processing
The lookup is sent to Google's public DNS-over-HTTPS resolver over HTTPS; nothing is stored by this site.
Frequently asked questions
Why does this show a different address than my phone?
Different resolvers cache independently and some networks answer with their own nearby edge address (CDN anycast). Both answers can be correct for their location and moment. Propagation is complete when the old TTL has expired everywhere, not when any one resolver updates.
Can I look up MX, TXT or other record types here?
This page queries A records; mail records have their own page (MX Lookup, in Related tools). For the full record set, a resolver's web interface or dig gives every type.
What does TTL actually control?
How long a resolver may reuse an answer before asking again. Low TTLs (60–300) make changes take effect quickly at the cost of more queries; high TTLs (86400) are stable and slow to change. Lower the TTL a day before a planned migration, then raise it after.
Is my query private?
The lookup is sent over HTTPS to Google's public resolver, which logs queries under its own privacy policy. The domain you look up is visible to that service — that is inherent to asking any public resolver.
Why did a brand-new subdomain return nothing?
Either it does not exist (NXDOMAIN or an empty answer) or caches are still serving the pre-creation negative answer, which is also cached, typically for the zone's negative TTL. Wait it out; the absence you see may be yesterday's cached "no".