About this dns lookup
The Domain Name System turns names such as example.com into the numbers and instructions computers need. This tool asks for the eight record types that matter most: A and AAAA give the IPv4 and IPv6 addresses of the site, CNAME names an alias, MX lists the mail servers and their priority, NS shows which name servers are in charge, TXT holds text such as SPF and domain verification, SOA describes the zone, and CAA says which certificate authorities may issue certificates.
The lookup is made by our server, not by your browser. When you press the button, the domain you typed is sent to our small API at /api/dns-lookup.php, which resolves it and returns the records as JSON. We do not keep a history of searches. Like any web page, the request can appear in the standard access log of the web server. Nothing else from your device is sent.
Use it after changing hosting or email: compare the records you set with what the world sees, check that an MX record points to the right provider, or read a TXT record to confirm a verification code. Answers can differ from your own computer because resolvers cache records for the TTL shown, so a fresh change may take time to appear. Only public names are looked up; private and internal addresses are refused.
Which controls should I check first?
The DNS Lookup form labels its controls as Domain name. Use those labels to keep the source and settings separate. A sample argument that selects a mode is not additional source text. Choose the setting matching your intended operation before copying a result, and change it explicitly when comparing another mode. The labels describe what this form accepts; the worked examples below demonstrate only the stated supplied values.
How should I interpret this specific operation?
A, AAAA, MX, TXT and nameserver records answer different questions. An address record can point to a proxy, while a mail-exchanger record names a mail route. A missing record type does not imply that all DNS for the domain is broken. Begin with the record relevant to your symptom and compare it with the authoritative configuration. Cached answers can persist after a change, and a resolver's view is not a measurement of every visitor's answer.
Worked helper values
These values come from the reproducible calculation examples supplied with this tool. Each row identifies the complete supplied arguments and the returned value. A visible ↵ denotes a line break and ⇥ denotes a tab in text examples. Settings appear alongside source data so that a different mode is not mistaken for an identical input. These are helper calculations, not observations of a live device, fetched target, image decoder, browser preview or downloaded file. Use the stated method above to relate the returned fields to the actual operation.
| Supplied values | Calculated return value |
|---|---|
| dns-lookup; a b.com | /api/dns-lookup.php?q=a%20b.com |
| example.com ; x | example.com |
Whose network view does this result represent?
A server-side check observes the target from the checking service's network location. Your browser, a mobile connection and another resolver can see different answers because of caching, geolocation, routing, filtering or load balancing. Keep the exact queried target and the time of your check when comparing observations. A timeout means this attempt did not obtain a result within its limit; it does not prove the target is unavailable everywhere. To investigate a discrepancy, compare the same target and protocol from the relevant client environment as a separate step.
How should I prepare a target?
Use a public target whose spelling and scope you can explain. A hostname, an IP address and a complete URL carry different information. A URL includes a scheme, path and possibly a query string, while a hostname identifies a host without those request details. Follow this page's stated input convention and omit credentials or confidential query values from demonstration targets. Correct an invalid-target message before retrying. The address is sent to the checking service for processing, so this workflow is different from a local parser that merely splits the supplied text into components.
What can I infer from missing fields?
A missing field can reflect the target, the available response or the check's scope. It should not be replaced with a guessed value. Read any status or explanation beside the output and distinguish an empty answer from an error. Compare the same type of evidence across repeated checks rather than treating every field as an independent verdict. A registration record, resolver result and HTTP response describe different layers and can disagree without any of them being fabricated. Follow a discrepancy to the layer it concerns before changing DNS, application settings or certificate configuration.
What is a TTL in a DNS record?
TTL is the time to live, in seconds, for which a resolver may keep a record before asking again. A low value such as 300 means changes spread within minutes; 86400 means a day.
Why do I see no AAAA or CAA record?
Those records are optional. A domain without an IPv6 address has no AAAA record, and most domains publish no CAA record. The tool only lists records that exist.
Does this show records from my own computer's cache?
No. The query is sent from our server to public DNS, so you see what other people on the internet see, within the cache time of each record.
Is my search stored?
The app keeps no search history. The web server access log may contain the request, as for every web page.