Reading DNS Records
A DNS answer only makes sense with its record type and resolver in view. Choose the record that matches the question you are trying to answer.
Choose the record type for the question
A returns IPv4 addresses and AAAA returns IPv6 addresses. CNAME aliases one DNS name to another; it is not an IP address. MX names mail exchangers, often with priorities, and NS identifies authoritative nameservers for a zone or delegation.
TXT carries text used for verification, SPF, and other policies. CAA states which certificate authorities may issue certificates for a domain; it is not itself the site's TLS certificate. Utilook DNS Lookup supports exactly A, AAAA, CNAME, MX, TXT, NS, and CAA.
TTL describes caching, not a global deadline
A record's TTL tells a resolver how long the answer may be cached. It does not promise that a DNS change will be visible worldwide within that time. Different resolvers may have cached an earlier value at different moments; negative answers may be cached too.
Rather than imagining a single worldwide propagation process, compare the queried type and name, then recheck after caches have had time to expire. A single lookup is a view from one resolver at one moment.
An empty answer is not necessarily an outage
A domain can exist without the selected record type. Utilook reports no matching answer as a no-answer error; a name that does not exist is reported separately. Neither by itself proves that the whole website or mail service is down.
Try the record type that matches your question and check the exact hostname. For example, no MX answer for a subdomain does not by itself diagnose the parent domain's mail setup.
How this lookup is performed
The browser sends the entered domain and record type to the Utilook backend. The backend asks Cloudflare's DNS-over-HTTPS resolver and returns up to 100 matching records with their TTL values; a request can time out after four seconds. The domain and type are therefore also sent to that external resolver.
This feature does not save the queried domain or answers in its database. Successful runs are counted separately. The result reflects Cloudflare's resolver, not a direct query to every authoritative server.