DevTools Logo

DNS Lookup Tool

DNS Lookup: Check DNS Records

Query DNS records and resolve domain names to IP addresses

DNS Query

Enter hostname and select record type

Quick Examples

    Examples

    A record for a public domain

    Input
    Domain:      example.com
    Record type: A
    Output
    Status:    success
    Query time: ~30 ms
    Records:   example.com. 86400 IN A 93.184.216.34

    The IPv4 address that the resolver returns for the apex. The result card shows the name, TTL (in seconds), the IN class, the A type, and the resolved address — a useful sanity check before you point a record at a new host.

    MX records for an email domain

    Input
    Domain:      gmail.com
    Record type: MX
    Output
    Status:    success
    Records:
      gmail.com. 300 IN MX 5  gmail-smtp-in.l.google.com.
      gmail.com. 300 IN MX 10 alt1.gmail-smtp-in.l.google.com.
      gmail.com. 300 IN MX 20 alt2.gmail-smtp-in.l.google.com.
      …

    Mail exchange records sorted by priority. Lower numbers are preferred; here Google returns priority 5, 10, 20 and so on, so a sending MTA will try `gmail-smtp-in.l.google.com` first.

    Reverse DNS (PTR) for an IPv4

    Input
    IP:         8.8.8.8
    Record type: PTR
    Output
    Status:    success
    Records:   8.8.8.8.in-addr.arpa. 86400 IN PTR dns.google.

    Reverse lookup translates an IP back into a hostname using the in-addr.arpa zone. Confirming that the PTR for your mail server's IP matches your sending domain is one of the easiest ways to improve deliverability.

    About this tool

    Enter a domain, choose a record type and this tool resolves it against DNS. Results list each record's name, TTL and data value — plus priority for MX — along with the query time. Recent lookups stay in a list, and a copy button exports them in zone-file style.

    Email debugging is the classic use: MX records show which servers accept mail, while TXT records carry SPF, DKIM and DMARC settings. Domain moves are the other — compare A or AAAA records before and after a change to see where a name points.

    This page queries one record type at a time. Use the NS lookup tool for name-server details, the reverse DNS lookup to map an IP back to a hostname, the DNS propagation checker to watch changes spread, and the whois lookup for registration data.

    What this tool does not do

    • A successful lookup here is one resolver's view. Clients in other regions may still see the old record until TTLs expire.
    • The tool is not an authoritative nameserver and does not replace dig +trace or your registrar's zone editor.

    How to use this tool

    1. Enter the domain

      Type a name, or pick one of the common domains shown.

    2. Choose a record type

      Select A, AAAA, CNAME, MX, TXT, NS, SOA or PTR.

    3. Run the lookup

      Press the lookup button and wait for the records and query time.

    4. Read or copy the results

      Check TTLs, priorities and values, then copy them as text.

    Use cases

    Verifying that a DNS change has propagated

    After updating an A or CNAME record, run a lookup from the tool to see the new value and the resolver's TTL — useful before tearing down the old infrastructure or rolling out a migration.

    Debugging mail delivery

    Check the MX, SPF (TXT) and PTR records for your sending domain in one place. A missing PTR or an MX that points at a stale host is the most common reason mail ends up in spam.

    Confirming a domain's nameservers

    Query the NS record type to see which nameservers the registry delegates to — and confirm those are the nameservers your hosting provider actually expects.

    Auditing SPF, DKIM and DMARC TXT records

    Look up the TXT records for the apex and the common `_dmarc` and selector subdomains to verify that your email-authentication policy is published correctly.

    DNS record types you can query

    RecordWhat it answers
    ADomain name to IPv4 address
    AAAADomain name to IPv6 address
    CNAMEAlias to the canonical domain name
    MXMail servers that accept email, with priority
    TXTText data: SPF, DKIM, DMARC policies
    NSAuthoritative name servers for the zone
    SOAZone authority data: primary server, serial, timings
    PTRReverse DNS: IP address back to hostname

    Common mistakes

    Mistake:Looking up a domain that doesn't exist and reading the error as a network failure.

    Fix:An NXDOMAIN result is a valid DNS response — the record type `no_records` is what the tool surfaces for an empty answer set. Always check the Status field before assuming the service is down.

    Mistake:Expecting a CNAME at the apex of a zone to work.

    Fix:The DNS specification forbids a CNAME at the apex when other records (NS, MX, SOA) coexist — that's the `no_records` error you'll see if you try it. Move the CNAME to a subdomain like `www` and use the apex for the A/AAAA record instead.

    Mistake:Reading the resolver's TTL as a cache lifetime you control.

    Fix:The TTL is the *remaining* time a resolver is allowed to cache the record. The authoritative TTL is set in the zone file; what you see here is whichever resolver the tool used and how long since it last refreshed.

    Mistake:Treating the lookup as authoritative for the user's perspective.

    Fix:DNS is hierarchical and cached: a record that resolves to one value here may resolve to a different value for a client in another region until propagation completes. Combine this tool with a public DNS checker (e.g. `dig +trace`) for a fuller picture.

    Frequently asked questions

    Which DNS record types can I look up?

    Eight types: A and AAAA for IPv4 and IPv6 addresses, CNAME for aliases, MX for mail servers, TXT for SPF and other text records, NS for name servers, SOA for zone authority data, and PTR for reverse lookups.

    What does TTL mean?

    Time to live — the number of seconds another DNS server may cache a record before fetching a fresh copy. Short TTLs make changes take effect quickly; long TTLs cut down on query traffic.

    How do I check SPF and DMARC records?

    Run a TXT lookup on the domain: the SPF policy is the string starting with v=spf1. DMARC lives on a subdomain — run a TXT lookup on _dmarc.example.com, using your own domain.

    Why do results differ from my local DNS?

    This tool resolves from its own server, while your computer asks a caching resolver — your ISP's or a public one such as 8.8.8.8. That resolver may hold an older answer until the TTL expires, so values can differ briefly after a change.

    References & standards