How Codynet Limits Query Analytics

This note originally described Codynet’s June 2026 no-retention architecture. Codynet now discloses limited 90-day operational query analytics in Microsoft Application Insights. The current policy is on the Privacy page.

The boundary remains narrow: full result payloads are not retained, the user-controlled History drawer stays in the browser, and sensitive HTTP URL components, credentials, malformed input, and raw User-Agent strings are excluded.

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.
• Limited 90-day analytics. A validated normalized target and request metadata may be retained in Application Insights.
• History stays on your device. Your user-controlled recent-lookup list lives in browser local storage and can be cleared whenever you like.
• Full results are excluded. Query analytics do not retain full DNS/RDAP responses, certificate payloads, or HTTP response headers.
• 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.