DNS Lookup

Query A, AAAA, CNAME, MX, TXT, NS, SOA, PTR, SRV and CAA records for any domain

100% free. This tool needs our server to do the work, so what you submit is sent there, processed and then discarded - it is never stored.

language

Jump to the next useful tool without leaving your flow.

See more

About this tool

DNS records control how a domain name resolves - which server it points to, how email is routed, and more. This tool queries all the common DNS record types (A, AAAA, CNAME, MX, TXT, NS, SOA, PTR, SRV, CAA) for any domain, useful for debugging domain configuration, verifying DNS changes have propagated, or investigating how a domain is set up.

Workflow

Diagnose a slow or unreachable website

Work outwards: is the host answering, is the page slow, and is the certificate still valid.

  1. 1Ping the hostLatency, jitter and packet loss.Open
  2. 2Run a speed testReal browser-rendered performance audit.Open
  3. 3Check the certificateAn expired one blocks every visitor.Open
  4. 4Inspect DNSConfirm the records point where you expect.You are here
Workflow

Fix email that is not being delivered

Confirm the server answers and your credentials work before blaming DNS.

  1. 1Test the SMTP serverConnectivity, TLS, certificate and AUTH.Open
  2. 2Check reverse DNSA missing PTR record is a common cause.Open
  3. 3Inspect DNS recordsVerify SPF and MX are published.You are here

How to use this tool

  1. Enter domain nameQuery target hostname you want to diagnose or verify.
  2. Select record typesCheck A/AAAA/CNAME/MX/TXT/NS and other records as needed.
  3. Review DNS responsesInspect values, priorities, TTL, and delegation consistency.
  4. Validate propagation/configCompare expected setup with returned records and fix mismatches.

Which DNS record does what

A and AAAA records point a name to an IPv4 or IPv6 address. CNAME makes one name an alias of another. MX lists the servers that receive email. TXT holds text such as SPF, DKIM, DMARC and domain verification codes. NS lists the name servers responsible for the domain, and CAA limits which authorities may issue its certificates.

After changing a record, old values can be cached for up to the record’s TTL - often an hour or less, sometimes a day. If the new value shows here but not on your computer, your local cache has not expired yet.

Key features

  • Speeds up troubleshooting for domain and email routing issues.
  • Provides one place to inspect major DNS record families.
  • Helpful for propagation checks after DNS changes.
  • Useful for security and deliverability verification workflows.

Common uses

  • Debugging website pointing to wrong server IP.
  • Verifying MX/TXT records for email provider setup.
  • Checking SPF/DKIM/DMARC text records quickly.
  • Auditing nameserver and CAA policies for domain control.

Tips for better results

  • Check TTL before expecting immediate global propagation.
  • Validate both apex and subdomain records separately.
  • Use TXT lookups to confirm SPF and verification tokens.
  • Document final DNS values to prevent accidental future drift.

Mistakes to avoid

  • Assuming local resolver cache reflects global propagation state.
  • Editing wrong DNS zone while expecting immediate fix.
  • Forgetting AAAA record when IPv6 traffic matters.
  • Overlooking MX priority order during mail migration.

Frequently asked questions

A records point a domain to an IPv4 address. AAAA records point to an IPv6 address - modern domains often have both to support visitors on either type of network.

They specify which mail servers handle email for a domain, and in what priority order - essential for verifying email is routed to the correct provider (like Google Workspace or a custom mail server).

DNS changes take time to propagate globally due to caching (TTL - time to live) at various points across the internet - it can take anywhere from minutes to 24-48 hours depending on the record's TTL setting and caching along the way.

They are TXT records that help mail servers trust your email: SPF lists servers allowed to send for your domain, DKIM publishes the key used to sign messages, and DMARC says what to do with mail that fails both.

Add the TXT record they give you at your DNS provider, wait for it to appear in a lookup here, then click verify. Leave the record in place afterwards.

Time to live - how many seconds resolvers may cache a record. Lower it to a few minutes a day before a planned change so the switch spreads quickly, then raise it again afterwards.