Enter a domain such as example.com. You can include https:// or www. if you prefer, we normalise the hostname before querying.
Queries A, AAAA, CNAME, MX, NS, TXT, SOA and CAA records. No account required.
Querying each record type separately. This usually takes a few seconds.
Resolver snapshot
DNS translates names like example.com into addresses and service locations mail servers, nameservers, and verification strings use. WebFixer's lookup queries eight record types for the hostname you enter: A, AAAA, CNAME, MX, NS, TXT, SOA and CAA. Each type is requested separately so one failure does not hide the others.
example.com, www.example.com, or _dmarc.example.com).| Type | Purpose | Example use |
|---|---|---|
| A | IPv4 address for the name. | 203.0.113.10 points www.example.com at a web server. |
| AAAA | IPv6 address. | 2001:db8::1 for dual-stack hosting. |
| CNAME | Alias to another hostname. | www CNAME to a CDN hostname (often not on the zone apex). |
| MX | Mail exchanger with priority. | 10 mail.example.com (lower number = preferred). |
| NS | Authoritative nameservers for the zone. | Must match nameservers set at your registrar. |
| TXT | Free-form text. | SPF (v=spf1 ...), domain verification, DKIM records. |
| SOA | Start of authority: serial, refresh, retry, expire, minimum TTL. | Useful after delegation or zone migration. |
| CAA | Which certificate authorities may issue TLS certs. | 0 issue "letsencrypt.org" |
Each DNS answer has a TTL (time to live). Resolvers cache records until TTL expires. After you change DNS at your provider, WebFixer may still show old values until caches refresh. This tool shows one resolver snapshot (WebFixer's), not a global propagation map. It does not query multiple worldwide resolvers.
An empty section usually means no records of that type at the name you queried, which is normal for CAA or AAAA on many sites. Multiple A or AAAA records can indicate load balancing. MX priorities explain mail routing order. If the whole lookup fails, check spelling, rate limits, or temporary resolver errors and try again.
Website shows wrong host after migration. Compare A/AAAA with your hosting panel. Update records at the DNS provider (or registrar if DNS is hosted there), wait for TTL, then look up again.
Mail bounces or goes to the wrong provider. Inspect MX priorities and targets. Changes belong in DNS; mail software itself is outside this tool.
Certificate issuance fails. Check CAA records allow your chosen CA. Remove overly strict CAA if you intentionally use that CA.
Domain verification stuck. Compare the TXT token your SaaS vendor gave you with the TXT section for the exact hostname they specify (often _acme-challenge or root).
Registrar: nameserver delegation, domain locks. DNS host: record values (A, MX, TXT, etc.). Web host or CDN: target IPs or CNAME destinations they provide. WebFixer only reads public DNS; it cannot change records for you.
No DNSSEC validation, no trace of full delegation from root, no historical data, and no multi-resolver comparison. Subdomain lookups require entering the full hostname.
Each record type is queried separately so you can spot missing mail records, wrong nameservers, or stale addresses without digging through a single raw dump.
IPv4 and IPv6 addresses that tell browsers where the site is hosted. Compare these after a migration or CDN change.
Mail exchanger hosts and priorities that control where email for the domain is delivered.
Authoritative nameservers plus zone timing in the SOA record, helpful when DNS was recently delegated.
Canonical name records that point one hostname at another, common for www, CDNs, and third-party services.
Verification strings and policies such as SPF, DKIM-related entries, and domain ownership proofs.
Certificate Authority Authorization rules that restrict which CAs may issue TLS certificates for the domain.
DNS maps human-readable domain names to infrastructure, IPs, mail servers, nameservers, and policy text. This tool runs live queries from WebFixer's resolver and groups answers by record type so you can confirm configuration, not worldwide propagation.
Common questions about reading DNS lookup results on WebFixer.
DNS answers depend on the resolver making the query. Use these results to confirm configuration, not as proof of global propagation.
Record types are independent - If one type fails or is empty, the others still appear.
No records is not always an error - Many domains omit AAAA, CAA, or apex CNAME records by design.
Compare before and after - Re-run a lookup after TTL changes to see updated answers from this resolver.
Pair with a site audit - After DNS looks right, check on-page SEO and links on the live URL.
WebFixer's free SEO audit complements DNS lookups with metadata, link, and crawlability checks.
Copyright 2026 WebFixer.dev. All Rights Reserved