What Is My DNS Server
Your DNS resolver
Detecting…
Probed via DNS-over-HTTPS from your browser. Secure DNS settings may show your DoH provider instead of your ISP.
How to use
- Open the page — a DNS-over-HTTPS probe runs automatically in your browser.
- The resolver IP and detection method appear below the headline.
- Click Copy to save the resolver address for troubleshooting or support tickets.
FAQ
What DNS server am I using?
The headline shows the IP of the recursive resolver that answered a test DNS query from your browser. Below it, the method row explains whether Google DoH, Cloudflare DoH, or another path was used to reach it.
Why might this differ from my router DNS?
Browsers with Secure DNS (DNS-over-HTTPS) enabled bypass your router and query a provider like Cloudflare (1.1.1.1) or Google (8.8.8.8) directly. The result here reflects your browser's DNS path, not necessarily your router's DHCP setting.
What is DNS-over-HTTPS (DoH)?
DoH encrypts DNS queries inside HTTPS requests instead of sending them in plain UDP to port 53. It prevents local network snooping but routes queries to the DoH provider configured in your browser or OS.
Is this a full DNS leak test?
No. This page runs one in-browser DoH probe. A comprehensive DNS leak test checks all resolver paths — including system-level and VPN-provided resolvers. Use this page for a quick browser-level answer.
Why did detection fail?
Corporate firewalls, ad blockers, privacy extensions, or offline Secure DNS providers can block the probe endpoints. Try disabling extensions or checking your browser's Secure DNS settings, then refresh.
Can I change my DNS server?
Yes — in your browser's Secure DNS settings, your OS network panel, or your router's DHCP DNS fields. After changing, refresh this page to see whether the resolver IP updated.
Introduction
What Is My DNS Server probes the DNS resolver your browser actually uses when it resolves domain names, and shows the resolver IP front and center with a one-click copy button. Below it, the method and notes explain whether the result came from Google DoH, Cloudflare DoH, or another encrypted DNS path.
DNS is easy to overlook until something breaks — a wrong resolver can block sites, leak your browsing to an ISP, or bypass a VPN's DNS protection. Knowing which server answers your browser's queries should not require digging through about://settings or router admin panels. This page answers in one load.
What is a DNS server?
A DNS server (resolver) translates human-readable domain names like example.com into IP addresses your browser can connect to. When you type a URL or click a link, a resolver somewhere on your network path handles that lookup.
| Layer | Typical resolver | Who configures it |
|---|---|---|
| Browser (DoH) | Cloudflare 1.1.1.1, Google 8.8.8.8, NextDNS | Browser Secure DNS setting |
| Operating system | ISP DNS, router DNS | OS network preferences |
| Router (DHCP) | ISP-assigned or custom (for example 1.1.1.1) | Router admin panel |
This page probes via DNS-over-HTTPS from your browser, so the result reflects Secure DNS settings more than a raw router configuration.
How the probe works
The page sends a special query for o-o.myaddr.l.google.com — a Google test domain that embeds the resolver's IP in the TXT response. The browser's DoH path handles the query; we read back whichever resolver answered. If Google DoH is blocked, a Cloudflare DoH fallback is tried.
Common use cases
- Troubleshooting blocked sites — confirm whether your browser uses ISP DNS, a public resolver, or a filtering service.
- VPN DNS check — verify your browser is not still using an ISP resolver outside the VPN tunnel.
- After changing Secure DNS — refresh to confirm the new provider took effect.
- Support tickets — paste the resolver IP when an IT team asks which DNS you use.
Best practices
- Treat this as a browser-level answer — your phone, smart TV, or other apps may use different resolvers.
- If you use a VPN, also run a dedicated DNS leak test; VPNs can protect traffic while leaving system DNS exposed.
- Corporate networks may force an internal resolver that this probe cannot reach — a failed result does not always mean no DNS is configured.
- To look up records for any domain, use DNS lookup; for your public IP and ISP, see what is my IP.