HTTP Headers Checker
Check the HTTP response headers of any URL: status code, server, caching, Last-Modified, redirects and security headers like HSTS and CSP. Free.
Check any domain's DNS records online: A, AAAA, CNAME, MX, NS, TXT, SOA and CAA. See where a domain points, its mail servers and its nameservers.
This tool asks our server for public information only. Nothing you enter is stored.
Enter a domain name and see its DNS records: A and AAAA (the IP addresses of the website), CNAME, MX (mail servers), NS (nameservers), TXT (SPF, DKIM, DMARC and verification codes), SOA and CAA, each with its TTL. Our server does the lookup, not your computer, so an old answer cached on your PC or router doesn't get in the way. That makes it handy right after you move hosting or connect a new domain.
DNS turns names into the numbers computers use. A DNS lookup asks a domain's nameservers for its records: the A record gives the IPv4 address of the website, MX says which servers receive its email, and TXT holds text such as SPF rules and Google or Microsoft verification codes. Every visit to a website starts with one, and the answer is cached for the record's TTL.
Windows has nslookup built in. Open cmd and type the commands below; add a resolver such as 8.8.8.8 (Google Public DNS) or 1.1.1.1 at the end to ask it instead of your own. PowerShell has Resolve-DnsName, which gives tidier output.
nslookup example.com
nslookup -type=mx example.com
nslookup -type=txt example.com 8.8.8.8
Resolve-DnsName example.com -Type MX
ipconfig /all # the DNS servers your PC uses
ipconfig /flushdns # clear the Windows DNS cache A reverse lookup asks which name belongs to an IP address, using a PTR record. On Windows, run nslookup with the IP, for example nslookup 8.8.8.8, which answers dns.google. Mail servers check this: email sent from an IP without a matching PTR record often lands in spam. Our What is my IP tool shows the reverse name of your own connection.
On Linux and Mac, dig shows the same records, and dig +trace follows the lookup from the root servers down to the domain's own nameservers. Use it when a domain answers differently in different places, for example halfway through a nameserver change.
dig example.com A +short
dig example.com MX
dig @8.8.8.8 example.com TXT
dig +trace example.com Google Public DNS has a web page at dns.google that shows what its resolver returns for a name, and the Google Admin Toolbox has a Dig tool. They answer from Google's resolver only. This page answers from our server, so comparing the two tells you whether a change has spread.
GuideHow to Connect a Domain to Hosting (GoDaddy, Namecheap, Hostinger and Your Own Server)
Asking the DNS for a domain's records: which IP address the website is on, which servers take its email, and so on. Browsers do it on every visit; this tool shows you the answers.
Choose NS above to see the nameservers a domain uses. To see the DNS servers your own computer uses, run ipconfig /all on Windows.
For a quick check from any device, an online tool like this one. For detail, dig on Linux and Mac or Resolve-DnsName on Windows. Checking from two places helps while a change is spreading.
Run dig +trace example.com on Linux or Mac. It shows each step from the root servers to the domain's nameservers and which server gave the final answer.
Resolvers keep the old answer until its TTL runs out, often up to a few hours. Clear your own cache with ipconfig /flushdns and compare with this tool.
No. We fetch public DNS records and show them; nothing you enter is saved.
Check the HTTP response headers of any URL: status code, server, caching, Last-Modified, redirects and security headers like HSTS and CSP. Free.
Trace every redirect of a URL: each hop's status code (301, 302, 307, 308), its Location, the server and meta refresh. Find redirect chains and loops.
See your public IP address (IPv4 or IPv6), its reverse host name, and what your browser tells websites. Works on phones and computers.