;; status: NOERROR · free · no sign-up · runs in your browser
Free DNS & Network Tools
Powerful, free tools for DNS lookup, nameserver checks, WHOIS, IP geolocation, SSL verification, and more.
;; tools section · 10 records
All Tools
Every lookup is free and needs no account. Results come straight from public DNS, RDAP and your own browser.
Nameserver Lookup
Check NS records for any domain
Run check →DNS Lookup
Full DNS record lookup (A, AAAA, MX, TXT, CNAME, SOA)
Run check →WHOIS Lookup
WHOIS domain registration information
Run check →IP Lookup
IP address geolocation and details
Run check →SSL Checker
Check SSL certificate details and validity
Run check →HTTP Headers
View HTTP response headers for any URL
Run check →Speed Test
Test website response time and performance
Run check →Domain Availability
Check if a domain name is available
Run check →Blacklist Checker
Check if IP/domain is on DNS blacklists
Run check →Email Validator
Validate email addresses (syntax + MX check)
Run check →;; workflow
Check the domain
Look up its nameservers, DNS records, WHOIS, SSL certificate or HTTP headers in one click.
Read the answer
Results show record types and TTLs the way a resolver returns them, so you see exactly what the internet sees.
Fix it with a guide
Step-by-step guides cover nameserver changes, propagation, SPF/DKIM, DNSSEC and common DNS errors.
;; guides
Latest Posts
View all guides →
How to Point a Domain to Vercel, Netlify or GitHub Pages (A vs CNAME vs ALIAS)
The exact DNS records for Vercel, Netlify and GitHub Pages: an A or ALIAS record for the apex, a CNAME for www, the records to delete, and how to check it all with dig.

DKIM Record Lookup: Find Your Selector and Verify the Key
Find the DKIM selector in a message header, look up selector._domainkey with dig, nslookup or PowerShell, read the key tags, and fix the failures that break DKIM and DMARC.

DNS Server Not Responding: What It Means and How to Fix It
A six-step order of checks for the DNS server not responding error: prove it is DNS, find the resolver you use, test 1.1.1.1 and 8.8.8.8, then fix it on Windows, macOS, Linux or the router.