DNS Lookup — Check DNS Records Online

How DNS Works

When you type a domain name into your browser, your device sends a DNS query to a resolver (usually your ISP's DNS server or a public resolver like Google's 8.8.8.8). The resolver checks its cache first. If the record isn't cached, it queries the root nameservers, then the TLD nameservers (.com, .org), and finally the domain's authoritative nameservers. The authoritative server returns the IP address, and your browser connects to that server to load the website. This entire process takes milliseconds.

DNS Record Types Explained

A Record: Maps a domain to an IPv4 address (e.g. example.com → 93.184.216.34). This is the most fundamental DNS record — it tells browsers where to find your website's server.

AAAA Record: Maps a domain to an IPv6 address (e.g. example.com → 2606:2800:220:1:248:1893:25c8:1946). Same as A record but for the newer IPv6 protocol.

MX Record: Specifies the mail server responsible for receiving email for the domain. Each MX record has a priority value — lower numbers are tried first. Example: for Gmail, MX records point to google mail servers with priorities 1, 5, 10, etc.

NS Record: Identifies the authoritative nameservers for the domain. These are the servers that hold the "master copy" of your DNS records. Typically provided by your domain registrar or DNS hosting provider.

TXT Record: Stores text strings used for domain verification, SPF (email sender policy), DKIM (email signing), DMARC (email fraud protection), and other purposes. One domain can have multiple TXT records.

CNAME Record: Creates an alias from one domain to another (e.g. www.example.com → example.com). The browser follows the CNAME to find the final A record. Cannot be used on the root domain.

SOA Record: Start of Authority — contains admin email, zone serial number, refresh intervals, and TTL defaults. Every DNS zone has exactly one SOA record. Useful for checking when DNS was last updated.

How to Check DNS Records Online

Enter any domain name in our free DNS lookup tool above and click Lookup. The tool queries live DNS servers and returns all records grouped by type. You can check specific record types (just A records, just MX records) or look up everything at once. Results include the record value, TTL (cache duration), and type. This is useful for verifying DNS changes, debugging email issues, or auditing a domain's configuration.

DNS Propagation — Why Changes Take Time

When you change DNS records (e.g. point your domain to a new server), the old records are still cached by DNS resolvers worldwide. The TTL value determines how long resolvers hold the cache. A TTL of 3600 means resolvers cache the record for 1 hour before checking for updates. To speed up propagation before making changes: lower your TTL to 300 (5 minutes) at least 24 hours in advance. After the change, resolvers will pick up the new record within 5 minutes.

Common DNS Problems and How to Fix Them

Website not loading: Check if the A record points to the correct server IP. If you recently changed hosts, the old IP may still be cached — wait for propagation or flush your local DNS cache.

Email not working: Check MX records. They must point to your email provider's servers (e.g. Google Workspace, Microsoft 365). Also verify SPF and DKIM TXT records are present — missing email authentication records cause deliverability issues.

www not working but root domain works: You likely need a CNAME record for www pointing to your root domain, or a separate A record for www pointing to the same IP.

Domain verification failing: Services like Google Search Console and Microsoft 365 require a specific TXT record. Use a DNS lookup to verify the TXT record exists and matches exactly what the service expects.

SPF, DKIM, and DMARC — Email DNS Records

SPF (Sender Policy Framework): A TXT record that lists which servers are authorized to send email from your domain. Prevents spammers from spoofing your domain. Example: v=spf1 include:_spf.google.com ~all

DKIM (DomainKeys Identified Mail): A TXT record containing a public key used to verify that emails were actually sent by your server and weren't tampered with in transit.

DMARC: A TXT record that tells receiving servers what to do with emails that fail SPF/DKIM checks (reject, quarantine, or accept). Also provides reporting. All three records together give strong email authentication.