Look up A, AAAA, MX, TXT, NS, and CNAME records for any domain, straight from live DNS. Free, no signup, one domain at a time.
Free plan · 1 domain check at a timeThis tool shows how a domain is configured. Pair it with our Whois Lookup to see who registered it and when it expires.
Run Free Website AuditDNS records are the instructions that tell the internet how to find and handle your domain — which server hosts your website, which servers accept your email, which nameservers are authoritative for your zone, and more. This tool queries live DNS for a domain and returns its A and AAAA records (IPv4/IPv6 addresses your domain resolves to), MX records (mail servers), TXT records (including SPF, often used for email authentication and domain verification), NS records (authoritative nameservers), and CNAME records (aliases pointing to another hostname). Every record is shown exactly as returned, along with a summary score covering whether the domain resolves, how many nameservers are delegated, whether mail is configured, and whether an SPF record protects against email spoofing.
This is a read-only diagnostic, not a DNS management tool — it can't add, edit, or fix records for you, only show what's currently published. A domain missing MX or CNAME records isn't necessarily a problem (many domains simply don't send email or use aliases), so read those results in the context of what the domain is actually meant to do. DNS results can also vary briefly by location during propagation after a change, typically resolving fully within 48 hours. For ownership and registration details (registrar, creation and expiry dates), use this alongside our Whois Lookup tool.
Domain Name System (DNS) records act as the authoritative instruction manual for your domain across the global internet. They dictate which web server hosts your website, which mail servers process incoming email, which nameservers manage your DNS zone, and how third-party services verify domain ownership.
In technical SEO and web infrastructure management, properly configured DNS records are essential for uptime, security, and deliverability. Misconfigured address (A) records can render a site completely inaccessible to users and search engine crawlers, while missing or invalid TXT and MX records can cause legitimate transactional emails to land directly in spam folders.
This utility—combining a Real-Time DNS Query Engine and a Domain Health Auditor—is designed to give webmasters, network administrators, and digital marketers instant visibility into published DNS configurations across global resolvers.
To perform a thorough DNS audit, technical administrators must understand the specific role each record type plays in domain routing and email security:
┌─────────────────────────────────────────┐
│ DNS Zone Architecture │
└────────────────────┬────────────────────┘
│
┌──────────────────────────────┬───────┴───────┬──────────────────────────────┐
│ │ │ │
┌───────┴────────┐ ┌────────┴────────┐─────┴──────────┐ ┌────────┴────────┐
│ Address │ │ Mail Routing │ Domain Validation│ │ Delegation │
│ Records │ │ (MX) │ (TXT / SPF) │ │ (NS / CNAME) │
└───────┬────────┘ └────────┬────────┘──────────────────┘ └────────┬────────┘
│ │ │
• A (IPv4) • MX Records • NS Records
• AAAA (IPv6) • CNAME Aliases
A Records (IPv4): Maps your domain name (e.g., example.com) to a 32-bit IPv4 address (e.g., 192.0.2.1). This tells web browsers and search bots where your web server physically resides.
AAAA Records (IPv6): Maps your domain to a 128-bit IPv6 address, supporting modern dual-stack network architecture for global connectivity.
Purpose: Specifies the mail servers responsible for accepting incoming email messages on behalf of your domain.
Priority Routing: MX records include preference numbers (e.g., Priority 10, 20). Lower values indicate primary mail servers, while higher numbers serve as backup or fallbacks.
Purpose: Stores arbitrary text-based data within your DNS zone.
Email Security & Verification: TXT records carry critical email security policies such as SPF (Sender Policy Framework), DKIM (DomainKeys Identified Mail), and DMARC. They are also used by services like Google Search Console to verify domain ownership.
NS Records (Nameservers): Identifies the authoritative DNS servers delegated to manage and serve DNS records for your domain zone.
CNAME Records (Canonical Name): Creates an alias pointing one domain name to another canonical hostname (e.g., pointing [www.example.com](https://www.example.com) to example.com or a CDN distribution endpoint).
This tool acts as a read-only live query client, parsing raw DNS responses directly from authoritative servers without serving cached or outdated database records.
| Feature | Technical Implementation | Administrator Benefit |
| Live Resolver Query | Executes real-time DNS queries for A, AAAA, MX, TXT, NS, and CNAME records. | Confirms live server configuration without local cache bias. |
| SPF & Email Audit | Checks TXT records specifically for valid SPF format and mail rules. | Helps prevent email spoofing, phishing, and delivery failures. |
| Nameserver Redundancy Check | Evaluates the number and distribution of delegated NS records. | Ensures domain resilience against single points of DNS failure. |
| Health Summary Scoring | Summarizes DNS health parameters into a quick diagnostic score. | Highlights critical configuration issues at a glance. |
| Clean Syntax Output | Formats raw DNS strings into clean, readable tables and values. | Simplifies record verification for client reporting. |
When reviewing your domain's live DNS records, keep the following contextual factors in mind:
Missing Records Are Not Always Errors: Not every domain requires all record types. A domain used exclusively for web hosting may not need MX records if it does not send or receive email. Similarly, root domains using direct A records will not have CNAME records at the apex level.
DNS Propagation Window: When you modify or add DNS records at your registrar or host, changes do not take effect globally instantly. Due to Time-to-Live (TTL) caching across global ISPs, DNS propagation can take anywhere from a few minutes up to 48 hours to fully resolve worldwide.
Read-Only Inspection: This utility is a diagnostic reader, not a DNS control panel. It reveals what records are currently published to the world. To modify, add, or delete records, you must log into your authoritative DNS provider (such as Cloudflare, Route 53, Namecheap, or GoDaddy).
Complementary Tooling: For domain ownership verification, administrative contact details, registration dates, and domain expiration tracking, pair this tool with a dedicated Whois Lookup utility.

Type your apex domain name (e.g., yourdomain.com) into the search field and initiate the live query.
Review the A and AAAA record outputs to ensure your domain resolves to the correct IP addresses assigned by your web hosting or CDN provider.
If your domain handles email, confirm that your MX records point to your email provider (e.g., Google Workspace, Microsoft 365). Next, audit your TXT records to ensure a valid SPF record (e.g., v=spf1 include:_spf.google.com ~all) is present.
Check the NS section. A healthy domain architecture should have at least two redundant, authoritative nameservers listed to guarantee continuous uptime and zone availability.

Implement Email Authentication (SPF, DKIM, DMARC): Protecting your domain with SPF, DKIM, and DMARC TXT records prevents spammers from forging your email address, safeguarding your inbox deliverability and domain reputation.
Set Lower TTLs Before Migration: When migrating servers or changing web hosts, lower the TTL (Time-to-Live) values on your A/AAAA records 24 to 48 hours prior. This reduces local caching times and ensures faster global cutovers.
Maintain Dual Nameserver Redundancy: Always ensure your domain relies on at least two geographically distributed authoritative nameservers to maintain high availability during network outages.
DNS records are cached globally based on their Time-to-Live (TTL) setting. If you recently updated a record, local DNS resolvers and ISPs may continue serving the cached old record until the TTL expires, which can take up to 48 hours during full propagation.
According to official DNS specifications (RFC 1912), a canonical name (CNAME) record cannot coexist with another record type (like an A or MX record) for the exact same hostname. This is why root domains (example.com) typically use A/AAAA records or specialized DNS flattening mechanisms rather than traditional CNAMEs.
Without an SPF record in your DNS TXT entries, receiving mail servers cannot verify whether incoming emails claiming to be from your domain actually originated from an authorized server. This significantly increases the risk of your business emails being flagged as spam or rejected altogether.
A well-configured DNS infrastructure is the backbone of web performance, security, and communication deliverability.
For Uninterrupted Web Access: Ensure your A and AAAA records point accurately to your server or CDN endpoints with redundant NS delegation.
For Maximum Email Deliverability: Configure authoritative MX records alongside strong TXT (SPF/DMARC) policies to protect your domain reputation against spoofing and spam filters.
Use the DNS Record Lookup & Health Diagnostic Tool above to inspect your live DNS zone, pinpoint missing authentication rules, and verify domain propagation in real time!