What This DNS Lookup Tool Checks
Digital Domain Kit's DNS Lookup tool checks common public DNS records for a domain name or URL and returns the results as grouped cards. It is built for quick domain troubleshooting: confirm where a hostname points, see which mail exchangers are published, review nameservers, inspect TXT entries such as SPF or site-verification values, and copy the returned data for a ticket, migration note, or configuration checklist.
The production implementation uses a browser form for the interface, then sends the submitted domain to a Digital Domain Kit endpoint. The server normalizes the submitted value, extracts the host when a full URL is entered, and uses PHP's dns_get_record() function to request selected record types from the server environment's configured DNS resolver. That means the lookup reflects what the Digital Domain Kit server can resolve at the time of the query. It is not a browser-only DNS client, a full propagation map, or a replacement for checking the authoritative DNS provider directly.
How To Use The DNS Lookup Tool
- Enter a domain name, hostname, or full URL in the field labeled Domain DNS.
- Use a public hostname such as
example.comorwww.example.com. If you paste a URL, the tool extracts the host portion before looking up records. - Select Query DNS to run the lookup.
- Wait for the DNS Query Output panel to appear. The page may show A, AAAA, MX, NS, SOA, and TXT sections depending on what exists for that domain.
- Use the copy icon beside an individual record when you need one value, or use Copy JSON Records to copy the grouped result data.
- If an error appears, check the spelling, remove unsupported characters, or test whether the domain actually publishes the requested DNS records.
Supported Records And Output
The tool does not request every possible DNS type. It is focused on the record groups most people need while moving a website, setting up mail, checking verification text, or confirming a domain's basic DNS posture.
| Record type | What the tool displays | Common use |
|---|---|---|
| A | IPv4 addresses, plus TTL and class from the first returned record group. | Confirming which IPv4 address a domain or hostname resolves to. |
| AAAA | IPv6 addresses, plus TTL and class when AAAA records exist. | Checking whether a site has IPv6 DNS configured. |
| MX | Mail exchanger targets and priorities. | Verifying email routing after setting up a mail provider. |
| NS | Nameserver hostnames for the domain. | Confirming which DNS provider is authoritative for the domain. |
| SOA | Administrative email, serial number, refresh, retry, expiry, minimum TTL, class, and TTL. | Reviewing zone authority details and whether a DNS change has a newer serial value. |
| TXT | Text values such as SPF, provider verification strings, and other published TXT records. | Checking email authentication setup, search-console verification, and service ownership records. |
Example Lookup
For a tested lookup on digitaldomainkit.com on September 15, 2026, the endpoint returned a successful JSON response that included an A record pointing to 34.235.188.101, nameservers under dnsowl.com, Zoho MX records, an SOA record with hostmaster@dnsowl.com, and TXT records for Google verification, Zoho verification, and SPF. DNS answers can change at any time, so treat this as a sample of the tool's output style rather than a permanent record of the domain.
A useful workflow is to run a lookup before and after a DNS change. For example, when moving email to a new provider, check the MX section first, copy the full JSON records, then compare the result after the DNS provider saves the new values. If the old MX target still appears, the change may not have been published, the domain may still be delegated to old nameservers, or the resolver may still be returning cached data until the relevant TTL expires.
Inputs, Validation, And No-Record Behavior
The input accepts a domain-style value or a URL-style value. The helper used by the live tool trims surrounding slashes, adds a temporary scheme when one is missing, removes a leading www. from the host, and validates the remaining value as a URL-shaped host. A pasted URL such as https://digitaldomainkit.com/tool/dns-lookup is therefore looked up as digitaldomainkit.com, not as the full page path.
| Input situation | Observed behavior | What to do next |
|---|---|---|
| Valid domain with records | Returns type: success and shows whichever supported record groups are present. |
Copy individual values or the JSON output for documentation. |
| Full URL | Extracts the host and checks DNS for that host. | Use this when copying directly from a browser address bar. |
| Invalid text | Returns errors_invalid_url_unknown from the endpoint. |
Remove spaces, unsupported characters, paths you do not need, or accidental punctuation. |
| Valid-looking domain with no supported records | Returns errors_no_dns_records_found with HTTP 200. |
Check spelling, delegation, record type, and whether the domain actually exists. |
Important Limitations
DNS Lookup is intentionally narrow. It does not perform a zone transfer, enumerate hidden subdomains, check DNSSEC, validate SPF syntax, test DKIM selectors, inspect DMARC policy, or query arbitrary record types such as CAA, SRV, CNAME, PTR, DS, or HTTPS/SVCB. It also does not let you choose a resolver, country, or nameserver. Results come from the production server's DNS resolution path, so another resolver may show a different answer during caching, propagation, split-horizon DNS, or provider outage situations.
TTL values are shown as returned in the query response, but DNS caching can make TTLs tricky to interpret. A low TTL does not guarantee every recursive resolver worldwide has already updated, and a high TTL does not always mean a value is wrong. If you need regional visibility, pair this page with the DNS Propagation Check tool to compare results from more than one location or resolver source.
Because the lookup is performed by the Digital Domain Kit server, do not use the page to test private-only DNS names, internal network hostnames, or confidential infrastructure labels. The tool is best suited to public internet domains and routine public DNS troubleshooting.
Troubleshooting DNS Results
| Problem | Likely cause | Suggested check |
|---|---|---|
| No records found | The domain may not exist, may not be delegated, or may not publish A, AAAA, MX, NS, SOA, or TXT records visible to the resolver. | Recheck spelling, confirm registration, and verify nameserver delegation at the registrar. |
| Old IP address still appears | A recursive DNS cache may still have the previous value. | Compare TTL timing and use DNS Propagation Check for a wider view. |
| Email still goes to the wrong provider | MX priorities, old MX records, or nameserver delegation may not match the new provider's instructions. | Review the MX list and check that the NS section points to the DNS provider you edited. |
| TXT verification is missing | The record may be added to the wrong zone, placed on a subdomain, or still waiting for cache expiry. | Check whether the service asked for the root domain, a prefixed host, or a specific TXT value. |
| A full URL returns unexpected records | The tool looks up the host only and ignores the page path. | Enter the exact hostname you want to inspect, such as app.example.com. |
Related Tools For Domain Troubleshooting
Use Hostname to IP Lookup when you only need the IP address for a hostname without the rest of the DNS record groups. Use IP to Hostname when you have an address and want to check whether reverse DNS returns a hostname. Use IP Information to review public IP ownership and location-style context after an A record points to an address. Use DNS Propagation Check when you need to compare whether a recent DNS change is visible beyond one lookup path.
Review Notes
This page is maintained by Digital Domain Kit and was last reviewed on September 15, 2026. The implementation verified for this article uses a browser form, a server endpoint at /dnsLookup, host normalization helpers, and PHP dns_get_record() queries for A, NS, MX, SOA, TXT, and AAAA records. The no-record path was retested with a nonexistent .example domain and returned a clean JSON error with HTTP 200. To report a mismatch between this documentation and the live DNS Lookup tool, use the contact page.