DNS Lookup

Look up A, AAAA, CNAME, MX, and TXT records for any domain. Queries live DNS — no caching on our end — so you see exactly what's published right now.

Where this actually gets used: verifying DNS propagation after pointing a domain at a new host or CDN (confirm the A/AAAA record actually resolves to the new IP before you cut over); troubleshooting email delivery (check the MX records point to the right mail provider, and that a TXT lookup shows the SPF record you expect — a missing or wrong SPF entry is a common cause of mail landing in spam or bouncing outright); confirming a CNAME setup for a subdomain pointed at a third-party service (a docs site, a landing-page builder, a CDN edge); and checking domain-verification TXT records (Google Search Console, Facebook Business, and most SaaS onboarding flows ask you to add a TXT record — this confirms it actually saved and propagated before you click "verify" on their end).

ℹ️ About this lookup

DNS (the Domain Name System) is the lookup layer that turns a domain name into the information other systems actually need — an IP address to connect to, a mail server to deliver to, or a text value to prove ownership. Every domain publishes these as records, held on its authoritative nameservers; this tool queries them directly and shows exactly what's live right now.

A / AAAA — the IPv4 / IPv6 address(es) the domain points to.
CNAME — an alias to another hostname; only present when the domain itself is defined as an alias (most domains with A/AAAA records directly won't have one).
MX — mail servers responsible for the domain, each with a priority (lower is preferred).
TXT — arbitrary text records, commonly used for domain verification (Google, Facebook, etc.) and email authentication (SPF, DKIM policy hints).
Each record type is looked up independently — one missing or erroring type never blocks the others.
Changed a record and it's not showing here yet? DNS changes propagate on the domain's TTL (time-to-live) — anywhere from a few minutes to 48 hours depending on what was set before the change, plus caching by resolvers along the way.

💻 Show API usage example (cURL)

curl -sS "https://devops.majbase.com/dns-lookup/api?domain=example.com"

Returns JSON: {"domain": "example.com", "results": {"A": {"records": [...], "error": null}, "AAAA": {...}, "CNAME": {...}, "MX": {...}, "TXT": {...}}}. Each type's error is null on success, or a short message (e.g. no records found, NXDOMAIN, timeout) — it never blocks the other types from resolving.