Your DNS server is what converts domain names (google.com) into IP addresses (142.250.80.46) so your browser can connect. Every internet request uses DNS.
Most people use their ISP's DNS servers automatically. But you might be using Google DNS (8.8.8.8), Cloudflare (1.1.1.1), or custom DNS if you changed it.
Check Your DNS Server Now
Use our tool to instantly see which DNS servers your device is using:
Shows your primary and secondary DNS, location, and provider.
Why Check Your DNS Server
Slow browsing but good speed test? Your DNS server might be slow. Switch to Cloudflare (1.1.1.1) or Google (8.8.8.8).
Some sites blocked? ISPs sometimes block sites via DNS. Changing DNS servers bypasses this.
Privacy concerns? Your DNS provider sees every website you visit. Cloudflare and Quad9 don't log queries.
Troubleshooting? Knowing your DNS helps diagnose connection issues.
Manual Methods
Windows:
ipconfig /all
Look for "DNS Servers" under your network adapter.
Mac:
scutil --dns | grep 'nameserver'
Linux:
cat /etc/resolv.conf
Router DNS: Login to router (usually 192.168.1.1), check WAN or DHCP settings for DNS servers.
Common DNS Servers
- 8.8.8.8 / 8.8.4.4 - Google DNS (fast, reliable)
- 1.1.1.1 / 1.0.0.1 - Cloudflare (fastest, privacy-focused)
- 9.9.9.9 - Quad9 (blocks malicious sites)
- Your ISP's DNS - Usually works but often slower
If you see your ISP's DNS and want better performance, consider switching to Cloudflare or Google.
When DNS Matters
- Normal browsing: Automatic DNS works fine. No need to change.
- Problems with specific sites: DNS might be blocking or slow. Try alternate DNS.
- Privacy concerned: Switch from ISP DNS to privacy-focused provider.
- Tech troubleshooting: Knowing DNS helps isolate connection issues.
Bottom Line
Your DNS server handles all domain lookups. Check which one you're using with our tool above.
Most people use ISP DNS by default. Switching to Cloudflare (1.1.1.1) or Google (8.8.8.8) often improves speed and privacy.
Device DNS vs Router DNS
Users often confuse these:
- Router DNS: default resolver for devices via DHCP
- Device DNS: per-device override (manual or app/VPN set)
You can have Cloudflare set on your laptop while other devices still use ISP DNS through the router.
Why DNS Leaks Happen
Even if you think you changed DNS, traffic can still leak to ISP resolvers because of:
- VPN client misconfiguration
- browser secure DNS override
- IPv6 resolver path not matching IPv4 config
- split tunneling rules
If privacy is your goal, verify both IPv4 and IPv6 resolver paths.
DNS Security Modes Worth Knowing
- Plain DNS (port 53): no encryption
- DoH (DNS over HTTPS): encrypted DNS over HTTPS
- DoT (DNS over TLS): encrypted DNS over TLS
Encryption improves privacy on untrusted networks but does not magically make all browsing anonymous.
Quick Validation Workflow
- Check current resolver with your OS command.
- Run a DNS leak test.
- Query a known domain and confirm which resolver answered.
- Repeat on IPv6-enabled networks.
Without validation, many users think they changed DNS when they actually did not.
When You Should Not Change DNS
If you are on enterprise/school networks, custom DNS policies may be required for security filtering and internal host resolution. Changing DNS manually can break access to internal services.
Bottom Line (Practical)
Knowing your DNS server is useful for speed, troubleshooting, and privacy checks. Just make sure to validate resolver behavior after changes, especially with VPNs and dual-stack (IPv4/IPv6) networks.