codynet
DNSDIGRDAPAll toolsGuidesNotesHow it worksAbout

Privacy

Privacy

Last updated: August 2026.

Codynet is built around a simple idea: keep our own data collection minimal, and disclose every third party clearly. This page describes exactly what does and doesn’t happen when you use the site.

What we collect

Standard server logs, kept short-term for operational health: timestamp, route name (e.g. /api/dns), HTTP status, and request latency.

We also use Microsoft Application Insights for cookie-free traffic, operational, and product analytics. This includes pageviews, session counts, broad browser and geographic information, tool usage, request outcomes, and performance. For validated tool requests, Codynet may retain the normalized domain, hostname, IP address, or sanitized HTTP host and port; the user-facing tool and operation; record type or resolver when applicable; result count; status; duration; an opaque request correlation ID; and an anonymous per-tab session ID. Codynet does not add the client IP address to these server-side query events, so it does not derive query-event geography from that address. Telemetry is retained for 90 days and is processed by Microsoft as a subprocessor in the United States. See Microsoft’s Application Insights data & privacy notice for details.

Query-data limits

Codynet does not retain full lookup result bodies, DNS or RDAP response payloads, certificate contents, or HTTP response headers in query analytics. For HTTP Header checks, analytics retain only the scheme, normalized hostname, and port — never the URL path, query string, fragment, username, password, or credentials. Malformed input that fails validation is not added to query analytics. We do not attach a name, email, account identity, authentication data, or payment information to these anonymous tool events, and we do not retain the raw User-Agent string.

Where your history goes

Your lookup history is stored in your browser’s localStorage under keys prefixed codynet:. That user-controlled History drawer remains on your device and is separate from the limited server-side operational analytics described above. You can clear local history any time from the History drawer (top-right) or by clearing site data in your browser. Disabling history stops the site from writing new local entries.

Outbound calls we make on your behalf

  • DNS lookups reach the resolver you choose — your operating system default, or one you pick (Cloudflare 1.1.1.1, Google 8.8.8.8, Quad9 9.9.9.9, OpenDNS, or a custom public IP). That resolver sees the query.
  • RDAP lookups reach IANA’s public bootstrap service and the relevant domain registry or regional internet registry.
  • HTTP and TLS inspections reach only the host you tell us to inspect.

Advertising

Codynet may display advertisements served by Google AdSense and other Google ad partners. Ads help fund the site’s hosting and let it remain free with no accounts and no paywall. We do not pass your query content to Google or to advertisers.

Google and its partners may use cookies, web beacons, IP addresses, device identifiers, and similar technologies to serve and measure ads, including personalized advertising based on your prior visits to this and other sites. Where required by law (for example, in the EEA, the United Kingdom, and Switzerland), Google’s consent management platform presents a prompt before personalized ads are served.

For details on how Google uses data when you use partner sites, see Google’s “How Google uses information from sites or apps that use our services” and the Google advertising policies. You can manage personalized advertising preferences at Google Ads Settings and opt out of third-party advertising cookies via the DAA (US) or EDAA (EU) opt-out pages.

Cookies

Codynet itself does not set tracking cookies. Application Insights runs without cookies and uses an anonymous random per-tab session ID held in session storage, which is normally cleared when you close the tab. When ads are displayed, Google ad partners may set their own cookies and similar identifiers as described above. You can manage or block cookies in your browser settings without affecting any of the site’s tools.

Third parties

The site is hosted on Microsoft Azure App Service, which has its own platform-level telemetry on infrastructure health. We use Microsoft Application Insights (also part of Azure) for the cookie-free analytics described above. Access to that telemetry is restricted through Azure authentication and role-based access controls. Public network access to Azure’s query endpoint does not make the records public. Google AdSense and its ad partners may serve ads as described in “Advertising.” No chat widgets, no other third-party SaaS.

Children

Codynet is a developer utility and is not directed at children under 13.

Contact

Privacy questions: networkutility@codynet.com.

codynetNetwork tools that just answer the question.

Explore

ToolsGuidesNotes

Project

How it worksAboutContact

Legal

PrivacyTerms

Email networkutility@codynet.com

© 2026 Codynet