What to prepare
The public URL, domain, IP address, record type, or audit option requested by the checker.
DNS records connect a domain with web, mail and verification services. Results can differ during propagation because recursive resolvers cache records according to their time-to-live values.
The public URL, domain, IP address, record type, or audit option requested by the checker.
A point-in-time observation from the public target and the checks available on this page.
It can help when you need to run a fresh diagnostic after a hosting, DNS, certificate, redirect, content or performance change. Start with a representative input, inspect the first result, then adjust one setting at a time if you need a different outcome.
The checker uses the public target you enter to make a diagnostic request. Do not place credentials or private access tokens in a URL.
Trace URL redirects and final destination.
TraceCheck domain registration and expiry dates.
CheckScan a page and find broken internal or external links.
ScanGenerate a clean robots.txt file for your website.
GenerateGenerate a simple XML sitemap from your URLs.
GenerateType the domain name you want to lookup.
We query DNS servers to fetch all available records.
DNS records are organized by type for easy viewing.
Use the information for troubleshooting or setup.
DNS lookup queries name servers to retrieve information about a domain — IP addresses, mail servers, etc.
For troubleshooting connectivity, verifying email setup, configuring services, or checking propagation after changes.
DNS records are cached based on their TTL — changes can take from minutes to 48 hours to propagate globally.
A maps to IPv4, AAAA to IPv6, MX for mail, TXT for verification/SPF, CNAME for aliases, NS for name servers.