Your All‑In‑One Online Tool Hub
Instantly query DNS records for any domain or IP address — A, AAAA, MX, TXT, CNAME, NS, SOA, PTR, SRV, and CAA. Check across Google, Cloudflare, Quad9, OpenDNS, and authoritative nameservers. Includes automatic SPF and DMARC analysis.
| Type | TTL | Value |
|---|
| Type | TTL | Value |
|---|
A DNS lookup is a query sent to a DNS (Domain Name System) server to retrieve records associated with a domain name. DNS records map human-readable domain names to machine-readable information such as IP addresses (A records), mail servers (MX records), and domain ownership verification strings (TXT records). Every time you visit a website, send an email, or connect to any internet service, a DNS lookup happens automatically in the background.
A records map a domain to an IPv4 address (e.g. 192.0.2.1 — the traditional 4-number format). AAAA records map a domain to an IPv6 address (e.g. 2001:db8::1 — the newer, longer format). Most modern websites have both — the A record serves visitors on IPv4 networks and the AAAA record serves visitors on IPv6 networks. Having both is considered best practice for compatibility and future-proofing.
TTL stands for Time to Live — it is the number of seconds a DNS record can be cached by resolvers and clients before they must re-query the authoritative server for a fresh copy. A TTL of 3600 means the record is cached for one hour. If you are about to make a DNS change, lowering the TTL to 300 (5 minutes) beforehand means the change will propagate faster. After the change is stable, raise the TTL back to 3600 or higher to reduce DNS query load.
Different resolvers may return different results when DNS changes are still propagating. When you update a DNS record, the change starts at the authoritative nameserver but cached copies at other resolvers must expire before those resolvers fetch the new value. During this window, some resolvers return the old record while others already have the new one. Use "✦ Check All DNS Resolvers" mode to see exactly which resolvers are serving the current record and which are still serving a cached version.
A PTR record (Pointer record) maps an IP address back to a hostname — the reverse of what an A record does. This is called reverse DNS. PTR records are stored in a special zone called in-addr.arpa for IPv4 addresses. They matter most for email deliverability — many mail servers check that the sending IP has a valid PTR record matching the sending domain's forward DNS. Enter an IP address in this tool to perform a reverse DNS lookup automatically.
SPF (Sender Policy Framework) is a TXT DNS record that lists the mail servers authorized to send email on behalf of your domain. Receiving mail servers check SPF to verify that incoming email claiming to be from your domain actually comes from an authorized server. The -all mechanism (hard fail) tells receivers to reject unauthorized senders outright. ~all (soft fail) marks them as suspicious. A missing or permissive SPF record makes your domain easier to spoof in phishing attacks.
DMARC (Domain-based Message Authentication, Reporting, and Conformance) is a TXT DNS record published at _dmarc.yourdomain.com. It tells receiving mail servers what to do with messages that fail SPF or DKIM checks: p=none means monitor only, p=quarantine sends failing messages to spam, and p=reject blocks them entirely. DMARC also enables aggregate reporting so domain owners can see authentication failures and detect spoofing attempts.
Not sure what a DNS record type means? These definitions explain every record type this tool queries — what it does, when it matters, and what to look for in the results.
dig command — the tool network engineers and sysadmins use in a terminal. Each line shows: domain name, TTL, record class (IN), record type, and value. IT professionals use this format to copy results directly into documentation, support tickets, or configuration comparisons. If you are not a sysadmin, you do not need this — the regular results table shows the same information in a more readable layout.Disclaimer: QuickITTools.com and EnterPlanet LLC strive to make our tools as accurate as possible. DNS data is retrieved in real time and reflects each resolver's current state at the moment of the query. Results may differ between resolvers due to caching and propagation. We do not store or log DNS query data.