Why DNS lookup needs a network request
DNS records are not stored inside the browser page. To check records such as A, AAAA, MX, TXT, CNAME, NS, or SOA, the browser has to ask a DNS resolver.
That means DNS Lookup cannot be fully local in the same way as a formatter, compressor, or file viewer.
A local tool can process an input on your device. A lookup tool has to request information from the network.
What is sent
For Utilio’s DNS Lookup workflow, the request includes the domain you enter and the DNS record type you choose.
For example, if you check TXT records for a domain, the lookup provider needs to know:
- the domain name;
- the requested record type;
- enough request metadata to return the DNS answer.
Utilio’s DNS Lookup uses DNS over HTTPS for the lookup request. This changes how the DNS query is transported, but it does not make the queried domain invisible to the DNS provider.
What Utilio does not proxy or store
Utilio does not proxy the DNS lookup through its own server for this workflow. The lookup is made from your browser to the external DNS-over-HTTPS provider shown by the tool.
Utilio does not need to store the lookup result to display it in the page.
This is different from a server-side lookup tool where the site’s backend receives the domain, performs the lookup, and returns the result.
For the broader model, see When a tool needs a network lookup and Privacy Policy.
How this differs from local tools
A local tool works with data already available in the browser. Examples include formatting text, compressing an image, or previewing a file.
DNS Lookup works differently because the answer has to come from DNS infrastructure. The tool can still avoid sending the query through Utilio’s server, but it cannot avoid sending the domain to a DNS resolver.
That is why Utilio labels DNS Lookup separately from local browser tools.
For other developer utilities, see Utilio developer tools.
Privacy checklist
Before using a DNS lookup tool, consider:
- whether the domain is public or sensitive;
- whether the lookup itself reveals internal naming;
- whether you are on a shared or monitored network;
- whether the DNS provider is acceptable for your use case;
- whether you should use an internal resolver for private infrastructure.
Avoid looking up private internal hostnames in public tools if the domain or naming pattern is sensitive.
Common questions
What does DNS Lookup send over the network?
It sends the domain name and selected DNS record type to the DNS-over-HTTPS provider used by the tool. The provider needs that information to return the DNS records.
Does Utilio proxy DNS lookups?
For this workflow, Utilio does not proxy the DNS lookup through its own server. The lookup is made from your browser to the external DNS-over-HTTPS provider shown by the tool.
Can DNS lookup be fully local?
Not for public DNS records. The browser needs to ask a resolver to get current DNS information. That requires a network request.
What is DNS-over-HTTPS?
DNS-over-HTTPS sends DNS queries over HTTPS instead of traditional DNS transport. It can protect the query from some network observers, but the DNS provider still receives the domain being queried.
What should I avoid looking up on shared networks?
Avoid sensitive internal hostnames, private infrastructure names, or domains that could reveal confidential projects. Use an internal resolver for private systems.