LogoTools
Uses a small server-side call for part of this tool - see below for what's sent

Looks up a domain's A, AAAA, CNAME, MX, TXT, NS, and SOA DNS records. Browsers have no DNS API at all. A page can't ask "what are this domain's MX records" the way it can make an HTTP request, which makes this one of the few tools on WebSync that's structurally impossible without a server.

When you'd use this

Confirming a domain's mail setup (MX records, SPF/DKIM/DMARC in TXT records) after changing email providers, checking that a DNS change has propagated before troubleshooting further, or verifying a CNAME/A record points where you expect after updating DNS.

A result here doesn't mean it's propagated everywhere

This queries whatever DNS resolver WebSync's server uses at the moment of the request. Changes reach resolvers around the world at wildly different speeds, depending on each record's TTL and on local caching. Seeing the new value here is a good sign. It is no guarantee that every visitor's resolver has picked it up yet.

Frequently asked questions

Why can't this run entirely in my browser like most tools here?

Browsers have no built-in way to make a DNS query. JavaScript can request a URL over HTTP(S), but nothing equivalent exists for asking a DNS resolver about A/MX/TXT records directly. A server-side lookup is the only way to get this data at all, not a workaround for a browser limitation.

Why do I see no CNAME record for a domain that has one in my DNS panel?

A domain can have an A record or a CNAME record at its root, but not both, and many domain registrars silently flatten a root CNAME into an A record for you. If you set a CNAME on a subdomain instead (like www), search that subdomain specifically.

Is the domain I look up sent anywhere?

It goes to WebSync's own server, which performs the DNS query and returns the results. Every DNS lookup tool has to work this way, since none of it can happen client-side.