--- title: "How to Check Your Website's DNS Records and What They Mean" description: "Learn how to look up DNS records for any domain. Understand A, AAAA, CNAME, MX, TXT, NS, and SOA records, what each one does, and how to troubleshoot common DNS issues." canonical_url: "https://webaloha.co/how-to-check-dns-records/" markdown_url: "https://webaloha.co/how-to-check-dns-records.md" date_published: "2026-04-02T00:00:00.000Z" date_modified: "2026-04-02T00:00:00.000Z" author: "Lucky Oleg" --- # How to Check Your Website's DNS Records and What They Mean Author: [Lucky Oleg](https://webaloha.co/authors/lucky-oleg/) | Published Apr 2, 2026 ![How to Check Your Website's DNS Records and What They Mean](https://webaloha.co/_astro/blog-how-to-check-dns-records.C0MCHPgJ_Z1kj9VS.webp?dpl=dpl_8RvAS1xqmRGEQGx5EyHZ5bsuaJhu) Every website runs on DNS. When someone types your domain name into a browser, DNS (Domain Name System) translates that name into the server IP address where your site actually lives. It’s the phone book of the internet. Most website owners never look at their DNS records until something breaks. Then it’s a scramble to figure out which record does what, whether it’s set correctly, and why emails stopped arriving or the site went down. This guide teaches you how to look up DNS records for any domain, what each record type means, and how to spot and fix common problems. ## How to Check DNS Records: 3 Methods ### Method 1: DNS lookup tool (fastest) Use a [DNS lookup tool](https://webaloha.co/tools/dns-lookup/) to check any domain instantly: 1. Enter the domain name (e.g., `example.com`) 2. The tool queries the domain’s authoritative name servers 3. View all DNS records: A, AAAA, CNAME, MX, TXT, NS, and more This is the fastest way to see your complete DNS configuration without any technical setup. ### Method 2: Command line (for developers) If you prefer the terminal, use `dig` (macOS/Linux) or `nslookup` (all platforms): Check all DNS records via terminal ``` # macOS / Linux dig example.com ANY # Check specific record type dig example.com A dig example.com MX dig example.com TXT # Windows Command Prompt nslookup -type=ANY example.com nslookup -type=MX example.com ``` ### Method 3: Domain registrar dashboard Your domain registrar (GoDaddy, Namecheap, Cloudflare, etc.) has a DNS management panel where you can view and edit all records. Log in, find your domain, and look for “DNS Settings” or “DNS Management.” **Which method to use:** - **Quick check of any domain** → DNS lookup tool - **Debugging with full technical output** → command line - **Editing your own records** → domain registrar dashboard ## Every DNS Record Type Explained Here’s what each DNS record does, when you need it, and what a typical value looks like: ### The Essential Records (Every Website Needs These) | Record | Name | What It Does | Example Value | | --- | --- | --- | --- | | A | Address | Maps your domain to an IPv4 address (your server’s location) | 93.184.216.34 | | AAAA | IPv6 Address | Maps your domain to an IPv6 address (modern internet protocol) | 2606:2800:220:1::248 | | NS | Name Server | Points to the DNS servers that manage your domain’s records | ns1.cloudflare.com | ### Website Routing Records | Record | Name | What It Does | Example Value | | --- | --- | --- | --- | | CNAME | Canonical Name | Creates an alias pointing one domain to another domain | www → example.com | | SOA | Start of Authority | Administrative info: primary server, admin email, zone serial number | ns1.example.com admin.example.com | | PTR | Pointer | Reverse DNS: maps an IP address back to a domain name | 93.184.216.34 → example.com | ### Email Records | Record | Name | What It Does | Example Value | | --- | --- | --- | --- | | MX | Mail Exchange | Routes incoming email to the correct mail server | 10 aspmx.l.google.com | | TXT (SPF) | Sender Policy | Specifies which servers can send email from your domain | v=spf1 include:\_spf.google.com ~all | | TXT (DKIM) | Email Signing | Cryptographic signature proving emails are authentic | v=DKIM1; k=rsa; p=MIGfMA0… | | TXT (DMARC) | Email Policy | Tells receiving servers what to do with emails that fail SPF/DKIM | v=DMARC1; p=quarantine; rua=mailto:… | ### Verification and Service Records | Record | Name | What It Does | Common Use | | --- | --- | --- | --- | | TXT | Text | Stores arbitrary text for verification and policies | Google Search Console verification, domain ownership | | SRV | Service | Defines location of specific services (port, weight, priority) | VoIP, Microsoft 365, SIP protocols | | CAA | Certificate Authority | Specifies which CAs can issue SSL certificates for your domain | SSL/TLS security policy | ## How DNS Records Work Together: A Real-World Example When someone visits your website and sends you an email, multiple DNS records work together. Here’s what happens behind the scenes: What Happens When Someone Visits example.com 1 Browser asks: where is example.com? The browser queries a DNS resolver for the domain Record used: NS record points to the authoritative name server 2 DNS resolver finds the server The authoritative name server returns the IP address Record used: A record returns 93.184.216.34 3 Browser checks for www If the user typed www.example.com, DNS resolves the alias Record used: CNAME record points www to example.com 4 SSL certificate is verified The browser establishes a secure HTTPS connection Record used: CAA record confirms which CA issued the certificate 5 Website loads The browser connects to the server and displays the page Record used: All records resolved in ~50-200ms total What Happens When Someone Emails [you@example.com](mailto:you@example.com) 1 Sender's server looks up mail server The sending mail server queries DNS for the mail handler Record used: MX record returns aspmx.l.google.com (priority 10) 2 Authentication check Receiving server checks if the sender is authorized Record used: SPF (TXT) record lists authorized sending servers 3 Signature verification Receiving server verifies the email signature Record used: DKIM (TXT) record provides the public key 4 Policy enforcement Receiving server applies the domain's email policy Record used: DMARC (TXT) record specifies reject/quarantine/none 5 Email delivered If all checks pass, the email reaches the inbox Record used: All email records validated in sequence ## Understanding TTL (Time to Live) Every DNS record has a TTL value measured in seconds. It tells DNS resolvers how long to cache the record before checking for updates. | TTL Value | Duration | When to Use | | --- | --- | --- | | 300 | 5 minutes | Before or during DNS changes (fast propagation) | | 3600 | 1 hour | Standard for most records (good balance) | | 14400 | 4 hours | Stable records that rarely change | | 86400 | 24 hours | NS records and very stable configurations | **Pro tip for DNS migrations:** Before changing DNS records (like moving to a new host), lower your TTL to 300 seconds 24-48 hours in advance. This ensures the old TTL expires, so when you make the actual change, it propagates quickly. After the migration is complete and verified, raise the TTL back to a normal value. Once you have made a change, track how far it has rolled out worldwide with our [DNS Propagation Checker](https://webaloha.co/tools/dns-propagation-checker/). ## Common DNS Problems and How to Fix Them ### Website not loading **Symptoms:** Browser shows “This site can’t be reached” or “DNS\_PROBE\_FINISHED\_NXDOMAIN” **Check:** Run a [DNS lookup](https://webaloha.co/tools/dns-lookup/) for your domain and verify the A record points to the correct IP address. **Common causes:** - A record points to an old server IP after migration - Nameservers haven’t been updated at the registrar - Domain expired (check with a [WHOIS lookup](https://webaloha.co/tools/whois-domain-lookup/)) - DNS propagation still in progress after recent changes ### Emails not being delivered **Symptoms:** Emails bounce, go to spam, or never arrive **Check:** Look up your MX records and TXT records (SPF, DKIM, DMARC). **Common causes:** - MX records point to the wrong mail server - Missing SPF record (receiving servers can’t verify your sending authority) - Missing or incorrect DKIM record (emails fail signature verification) - No DMARC record (no policy for handling failed authentication) ### www version not working **Symptoms:** `example.com` loads but `www.example.com` doesn’t (or vice versa) **Check:** Verify you have either a CNAME record for `www` pointing to your root domain, or a separate A record for `www`. **Common causes:** - Missing CNAME record for `www` subdomain - CNAME points to the wrong domain - SSL certificate doesn’t cover the `www` variant (check with an [SSL certificate checker](https://webaloha.co/tools/ssl-certificate-checker/)) ### Slow DNS resolution **Symptoms:** Website takes longer than usual to start loading **Check:** Look at your TTL values and NS records. **Common causes:** - NS records point to slow or overloaded name servers - TTL values are too low (causing excessive DNS queries) - Too many DNS records creating large zone files ## DNS Records and SEO: What Matters DNS configuration affects your website’s [SEO](https://webaloha.co/seo-services/) in several ways: - **Site speed:** DNS resolution adds 50-200ms to every page load. Fast, reliable name servers reduce this. CDN providers like Cloudflare and Vercel have some of the fastest DNS resolution times. - **Uptime and availability:** If your DNS goes down, your entire website goes down. Use at least two NS records pointing to different name servers for redundancy. - **www vs non-www:** Pick one canonical version and redirect the other. Inconsistent handling splits your SEO authority between two URLs. Your DNS setup (A record vs CNAME for www) determines how this works. - **Email deliverability:** SPF, DKIM, and DMARC records are TXT records in your DNS. Without them, your outreach emails and contact form notifications may land in spam. - **SSL/HTTPS:** Your DNS configuration determines how [SSL certificates](https://webaloha.co/tools/ssl-certificate-checker/) are validated. CAA records specify which certificate authorities can issue certificates for your domain. ## DNS Records Checklist Use this to verify your DNS configuration is complete: A record points to your current server's IP address AAAA record set if your server supports IPv6 CNAME record for www pointing to your root domain (or separate A record) NS records point to your DNS provider's name servers (minimum 2) MX records point to your email provider's mail servers SPF (TXT) record lists all authorized email sending servers DKIM (TXT) record is set up for your email provider DMARC (TXT) record defines your email authentication policy Sitemap is accessible to crawlers (DNS resolves correctly for your robots.txt and sitemap URLs) SSL certificate covers both root domain and www (verify with SSL checker) TTL values are appropriate (3600 for most records, lower before changes) No stale records pointing to old servers or services you no longer use ## Next Steps - **Look up your DNS records now** with our [DNS Lookup Tool](https://webaloha.co/tools/dns-lookup/) - **Check domain ownership** with our [WHOIS Domain Lookup](https://webaloha.co/tools/whois-domain-lookup/) - **Verify your SSL certificate** with our [SSL Certificate Checker](https://webaloha.co/tools/ssl-certificate-checker/) - **Test your robots.txt** to make sure crawlers can [access your site properly](https://webaloha.co/how-to-check-robots-txt/) - **Check your sitemap** with our [Sitemap Checker](https://webaloha.co/tools/sitemap-checker-and-validator/) - **Audit your full SEO setup** including DNS, schema, and more with our [SEO services](https://webaloha.co/seo-services/) ## Frequently Asked Questions How do I check my website's DNS records? Enter your domain name into a DNS lookup tool. It queries the domain's authoritative name servers and returns all records. You can also use the command line: 'dig example.com ANY' on macOS/Linux or 'nslookup example.com' on Windows. What is an A record in DNS? An A record maps your domain to an IPv4 address. It tells browsers which server to connect to when someone visits your website. Without an A record, your website won't load. What is the difference between A and CNAME records? An A record points a domain directly to an IP address. A CNAME record points a domain to another domain name, creating an alias. CNAMEs are useful for subdomains because if the IP changes, you only update one A record. What are MX records and why do they matter? MX records tell email systems which server handles email for your domain. Without correct MX records, emails sent to your domain won't be delivered. They include priority numbers for setting backup mail servers. What are TXT records used for? TXT records store text information about your domain. Their most important uses are email security (SPF, DKIM, DMARC), domain verification (Google Search Console), and site verification for analytics platforms. How long does it take for DNS changes to take effect? Typically 15 minutes to 48 hours, depending on the TTL value. Lower the TTL to 300 seconds before making changes for faster propagation. What does TTL mean in DNS records? TTL (Time to Live) tells DNS resolvers how long to cache a record before checking for updates. A TTL of 3600 means the record is cached for one hour. Why is my website not loading after changing DNS records? Most likely DNS propagation hasn't completed yet. Verify your A record points to the correct IP using a DNS lookup tool, then check propagation status. Wait up to 48 hours for full global propagation. * * * ## Check Your DNS Records Now Look up A, AAAA, CNAME, MX, TXT, NS, and more for any domain. Free, instant results. [DNS Lookup Tool →](https://webaloha.co/tools/dns-lookup/)[WHOIS Lookup →](https://webaloha.co/tools/whois-domain-lookup/) Recommended tools ## Recommended tools for this guide Use these free tools to apply the ideas from this guide to your own website. [![DNS Lookup Online Tool](https://webaloha.co/_astro/tool-dns-lookup.C2XPbYYk_ZI9pmG.webp?dpl=dpl_8RvAS1xqmRGEQGx5EyHZ5bsuaJhu) DNS Lookup Tool ](https://webaloha.co/tools/dns-lookup/)[![DNS Propagation Checker Tool Online](https://webaloha.co/_astro/tool-dns-propagation.CckoBCnG_xX9Tc.webp?dpl=dpl_8RvAS1xqmRGEQGx5EyHZ5bsuaJhu) DNS Propagation Checker ](https://webaloha.co/tools/dns-propagation-checker/)[![Domain Hosting and Server Checker Tool Online](https://webaloha.co/_astro/tool-domain-hosting.DtBcJFkN_zPdxD.webp?dpl=dpl_8RvAS1xqmRGEQGx5EyHZ5bsuaJhu) Domain Hosting Checker ](https://webaloha.co/tools/domain-hosting-checker/) Useful info? Spread the Aloha: [![Lucky Oleg](https://webaloha.co/_astro/lucky-oleg.EPOIIvwX_ZX2S03.webp?dpl=dpl_8RvAS1xqmRGEQGx5EyHZ5bsuaJhu)](https://webaloha.co/authors/lucky-oleg/) [Lucky Oleg](https://webaloha.co/authors/lucky-oleg/)[](https://www.linkedin.com/in/luckyoleg/) Lucky Oleg is the founder of Web Aloha, a web design & SEO agency helping businesses ride the digital wave. With years of experience in WordPress, technical SEO, and web performance, he writes about what actually works in the real world. #### Related guides from Web Aloha [![Technical SEO Audit: What to Check and How to Fix It](https://webaloha.co/_astro/blog-technical-seo-audit.DBRDzgnk_KFMKo.webp?dpl=dpl_8RvAS1xqmRGEQGx5EyHZ5bsuaJhu) Technical SEO Audit: What to Check and How to Fix It ](https://webaloha.co/technical-seo-audit-guide/)[![Google Search Console Guide for Business Owners](https://webaloha.co/_astro/blog-google-search-console-guide.m54ACdZc_Z2nnvvA.webp?dpl=dpl_8RvAS1xqmRGEQGx5EyHZ5bsuaJhu) Google Search Console Guide for Business Owners ](https://webaloha.co/google-search-console-guide/)[![Internal Linking Strategy: How to Build Topic Authority](https://webaloha.co/_astro/blog-internal-linking-strategy.Xh_J897b_Z1sydAb.webp?dpl=dpl_8RvAS1xqmRGEQGx5EyHZ5bsuaJhu) Internal Linking Strategy: How to Build Topic Authority ](https://webaloha.co/internal-linking-strategy-topic-authority/)