How Codynet Avoids Query Retention

A lot of lookup sites promise that your searches “never leave your browser.” For a DNS or RDAP tool that is simply not true: to resolve a name you have to send it to a resolver or registry, and that request leaves the browser by definition. Codynet resolves lookups server-side, so rather than make a claim the architecture cannot honor, we describe what actually happens and what we choose not to keep.

The honest summary is no query retention: the query is used to perform your lookup and is not stored in a database afterward.

When you run a lookup, the value you type — a hostname, a domain, an IP — is sent to Codynet's server. The server makes the corresponding request on your behalf: a DNS query to a resolver, an RDAP call to the registry, an HTTPS request to a host, or a TLS handshake to read a certificate. The result comes back, gets formatted, and is shown to you.

This server-side model is deliberate: it keeps the tools consistent, avoids exposing your browser directly to arbitrary endpoints, and lets the same lookup paths stay guarded against unsafe server-side requests.

• No account. There is nothing to sign into, so nothing ties a lookup to an identity.
• No query database. The value is processed to perform the request and is not written into a store of “who looked up what.”
• History stays on your device. Your recent-lookup list lives in your browser's local storage, not on a server, and you can clear it whenever you like.
• Ads do not receive your queries. Ads are off entirely today; if shown later, they are not handed your query content.

You do not have to take this on faith. Every result panel includes the equivalent dig or curl command, so you can run the exact same lookup yourself from your own machine and compare. The privacy page states the same commitments in policy form, and the lookup paths are the same SSRF-guarded code for every tool. If something here is ever inaccurate, the contact page is the way to call it out.