Your Domain Migration Starts Here
You’re moving your app from AWS to Vercel. Before you touch anything, you need to know exactly what DNS records exist on your domain. An A record pointing to the old server. MX records routing email through Google Workspace. Three TXT records for SPF, DKIM, and domain verification. A CNAME aliasing www to the root domain. Miss any of these during migration and something breaks — your website, your email, or your domain verification with a third-party service.
Type your domain name and get all six major record types in one shot: A, AAAA, MX, NS, TXT, and CNAME, complete with TTL values. Works for subdomains too — api.example.com, staging.example.com, whatever you need to check.
Reading the Results
A records map your domain to IPv4 addresses. Multiple A records usually mean load balancing — traffic gets distributed across several servers.
AAAA records are the IPv6 equivalent. If your hosting provider supports IPv6 (most modern ones do), you’ll see these alongside A records.
MX records tell the internet where to deliver email for your domain. They include a priority number — lower priority means higher preference. If your MX records are wrong, your email stops working. Period.
NS records identify your authoritative nameservers. These are the DNS servers that hold the master copy of your domain’s records. If you just transferred your domain to a new registrar, these should point to the new registrar’s nameservers.
TXT records are the Swiss Army knife of DNS. SPF records (which IPs can send email for your domain), DKIM public keys, DMARC policies, Google Search Console verification, Stripe domain verification — they’re all TXT records.
CNAME records create aliases. www.example.com pointing to example.com via CNAME is the classic setup.
Troubleshooting Scenarios
Your site went down after changing nameservers. Look up the domain — if the A record still points to the old server’s IP, your DNS changes haven’t propagated yet. Check the TTL on the old records; that’s roughly how long you’ll wait.
Email stopped working. Check the MX records. If they’re missing or pointing to the wrong mail server, that’s your problem. If they look correct, check TXT records for SPF alignment — a misconfigured SPF record can cause receiving servers to reject your email.
Domain verification failing. Services like Google, GitHub, and Stripe ask you to add a specific TXT record. Look up your domain here to confirm the record actually exists. DNS caching can delay visibility, so check the TTL.
For checking the hostname behind an IP address, use the Reverse DNS Lookup. For registration and ownership details, the WHOIS Lookup has that data. The SSL Certificate Checker tells you if your HTTPS cert is valid or expiring.
DNS propagation takes anywhere from a few minutes to 48 hours, depending on the TTL of the old records and how aggressively resolvers cache.