$ Quick DNS Record Lookup Tool_

DNS.fish

Every record, one request away.

A fast and reliable DNS lookup tool. Check DNS records for any domain.

RESOLUTION PATH · example.comQUERYING

01 ask
02 root
03 .com
04 authority
05 answer

> About DNS.fish

DNS.fish: Powerful tool for quick DNS record lookups.

The alternative to nslookup.io. Built for devs, sysadmins, and curious minds.

Simple curl commands.Fast results.No BS.

> Features

Small tool, deep answers.

Fast Lookups

Fast and live DNS record lookups

All Record Types

All common DNS record types supported

API Support

Zero install, supports CLI(API) usage

Blazing Fast

Blazing fast response times

Clean Output

Clean, parsable output

Export Options

Export & Download DNS records

> Domain DNS Lookup API Usage

No key. No SDK. Just curl.

Replace DOMAIN with target domain, TYPE with DNS record type (A, AAAA, MX, etc.).

zsh — 80×24

$ curl dns.fish/example.com/MX▍

{
  "data": [
    {
      "name": "example.com",
      "type": "MX",
      "ttl": 3600,
      "data": "10 mail.example.com"
    }
  ]
}

$ Get all DNS records:curl dns.fish/DOMAIN

$ Get specific type records:curl dns.fish/DOMAIN/TYPE

> What to look up, and when

Start from the symptom.

Most DNS trouble shows up as something else: lost email, a site that works for you but not your client. Here is which record to check first.

Email isn't arriving

curl dns.fish/DOMAIN/MXcurl dns.fish/DOMAIN/TXT

Look for MX hosts that exist and resolve, and exactly one SPF record. Two SPF records is a common, silent failure.

You just moved hosts

curl dns.fish/DOMAIN/Acurl dns.fish/DOMAIN/AAAA

Check the new IP, then the TTL: it is the longest anyone may still see the old server. A forgotten AAAA record often still points to the old host.

A service asks you to verify

curl dns.fish/DOMAIN/TXT

Confirm the token is published exactly as given. Some DNS panels add the domain name to the host field again, so the record ends up at the wrong name.

Works for some, not others

curl dns.fish/DOMAIN/NScurl dns.fish/DOMAIN/SOA

The name servers should all agree. A server with an older SOA serial than the others is serving stale data.

> Coming from dig or nslookup?

The same lookups, side by side.

dns.fish needs only curl, so it also works on CI runners, containers and locked-down machines that don't ship dig.

To find	dig	nslookup	dns.fish
All records	dig example.com ANY	nslookup -type=any example.com	curl dns.fish/example.com
Mail servers	dig example.com MX +short	nslookup -type=mx example.com	curl dns.fish/example.com/MX
IPv6 address	dig example.com AAAA +short	nslookup -type=aaaa example.com	curl dns.fish/example.com/AAAA
Name servers	dig example.com NS +short	nslookup -type=ns example.com	curl dns.fish/example.com/NS
Zone authority	dig example.com SOA +short	nslookup -type=soa example.com	curl dns.fish/example.com/SOA

> Record types at a glance

What each record tells you

Pick a type to look it up for your domain.

> Why your change isn't live yet

It's not propagation. It's caching.

Every answer carries a TTL. A resolver that cached the old answer keeps serving it until that TTL runs out, so the same change can look live to you and stale to someone else.

01Lower the TTL a day before a migration, then raise it again afterwards.
02Name server changes follow the parent zone's TTL, which is often 48 hours for .com.
03dns.fish asks the authoritative servers directly, so you see the new value as soon as it is published.

A RECORD · TTL 300192.0.2.1 → 192.0.2.9

> FAQ

DNS, answered.

What is a DNS record?

A DNS record is a database entry in the Domain Name System that maps a domain name to specific information, such as IP addresses or other data related to the domain.

Why is it important to check DNS records?

Checking DNS records is crucial for several reasons:

—Troubleshooting: Helps identify and resolve website accessibility issues
—Security: Verifies proper configuration to prevent DNS-based attacks
—Email delivery: Ensures correct MX records for smooth email flow
—Performance: Confirms optimal DNS settings for fast website loading
—Migrations: Validates DNS changes during website or server migrations
—Compliance: Assists in maintaining required security standards

Regular DNS record checks help maintain a healthy, secure, and efficient online presence.

What are the most common types of DNS records?

The most common types of DNS records include:

—A (Address) record: Maps a domain to an IPv4 address
—AAAA record: Maps a domain to an IPv6 address
—CNAME (Canonical Name) record: Aliases one domain to another
—MX (Mail Exchanger) record: Specifies mail servers for the domain
—TXT (Text) record: Stores text-based information, often used for SPF, DKIM, etc.
—NS (Name Server) record: Specifies authoritative name servers for the domain

What is the difference between A and AAAA records?

A records map a domain to an IPv4 address (e.g., 192.0.2.1), while AAAA records map a domain to an IPv6 address (e.g., 2001:0db8:85a3:0000:0000:8a2e:0370:7334).

What is a CNAME record used for?

A CNAME record is used to create an alias for a domain. It points one domain name to another, allowing multiple domains to resolve to the same IP address without duplicate A or AAAA records.

How do MX records work?

MX records specify the mail servers responsible for handling email for a domain. They include a priority value to determine the order in which mail servers should be tried.

What is a TTL in DNS records?

TTL stands for Time To Live. It specifies how long (in seconds) a DNS record should be cached by resolving name servers before requesting a fresh copy from the authoritative name server.

> Recent DNS Lookups

Note: Only domains with more than 3 DNS records are displayed here. CURL requests are not shown.

/blog

DNS Knowledge Hub

Expert guides and best practices for DNS management, troubleshooting, and security