Privacy Policy
Last updated: 2 July 2026
Summary
DNScope is a browser-based tool. There is no DNScope backend, no user accounts, and no personal data collected by us directly. When you use a tool, your browser calls public third-party APIs (listed below) on your behalf. We use Google Analytics 4 for aggregated usage statistics without sending any of your input (domains, IPs, etc.).
Who we are
DNScope is operated by Circlelink (circlelink.eu). Circlelink is the data controller for the analytics data described below. For questions about this policy, contact us via the Circlelink website.
What we collect ourselves
Nothing directly. DNScope is served as static files. We do not run application servers, databases, or logging infrastructure that receives your queries.
Your DNS lookups, WHOIS queries, port scans, email-authentication checks and everything else you type into the tools stay in your browser and are sent from there directly to the third-party APIs that answer them.
Third-party services called from your browser
The following services receive HTTP requests from your browser when you use the corresponding tool. Each has its own privacy policy — check theirs if you have concerns about a specific service:
- Google Public DNS (dns.google) — DNS lookups, subdomain scans, most record queries.
- Cloudflare DNS (cloudflare-dns.com) — Propagation checks, resolver benchmark, some DoH queries.
- Quad9, AdGuard, Mullvad, OpenDNS — Resolver benchmark (optionally via corsproxy.io).
- rdap.org — WHOIS / RDAP lookups.
- crt.sh — Certificate Transparency search.
- Shodan InternetDB (internetdb.shodan.io) — Port scan / exposure data.
- ipwho.is — IP geolocation and ASN information.
- api.ipify.org / api4.ipify.org / api6.ipify.org — Detecting your own public IP address.
- raw.githubusercontent.com — Fetching the StevenBlack hosts blocklist for the Tracker Check tool.
- corsproxy.io — Public CORS proxy used automatically when a target site blocks direct browser access (HTTP Headers, Sitemap Fetcher, CT search fallback, benchmark fallback for CORS-blocked resolvers).
- Google Fonts (fonts.googleapis.com / fonts.gstatic.com) — Loading the Inter and JetBrains Mono web fonts.
Analytics: Google Analytics 4
We use Google Analytics 4 (measurement ID G-ZMNJL8P9SK) to understand aggregate usage — which tools are visited, how often, from which country, and on what device. GA4 uses cookies and collects a truncated IP address by default.
What we deliberately do NOT send to Analytics:
- Domain names you look up
- IP addresses you inspect
- Private keys pasted into the DKIM matcher
- Any other user input
Our custom analytics events only send booleans, counts and status codes (e.g. "a DNS lookup happened, returning 6 records in 24 ms") — never the input that produced them.
Legal basis (GDPR): Legitimate interest in understanding aggregate usage of a free public tool. To opt out, use any browser-level Do Not Track setting, a tracking-blocking extension (uBlock Origin, Privacy Badger), or a DNS-based blocker — DNScope will continue to work perfectly without analytics.
Local storage on your device
DNScope stores three things in your browser's localStorage, on your own device only:
- Theme preference (light or dark)
- Lookup history — up to 100 recent DNS-lookup snapshots (domain + result + timestamp)
- DNS blueprints — saved "known-good" baselines you explicitly create for drift detection
This data never leaves your browser and is not synced to any server. Clearing browser data removes it. The lookup history and blueprints can also be cleared or exported from within the tools themselves.
Cookies
DNScope itself sets no cookies. Google Analytics 4 sets its own cookies (typically _ga and _ga_<measurement-id>) with a default 2-year expiry. Google Fonts may set no cookies depending on your browser configuration.
Your rights under GDPR
Because DNScope does not collect personally identifiable information server-side, most GDPR rights (access, rectification, portability, erasure) apply to the third parties listed above rather than to us directly. For the aggregate Analytics data, Google is the processor — see the Google Privacy Policy for details on requesting deletion.
Changes to this policy
We may update this policy when we add or remove third-party services. Material changes will bump the "Last updated" date at the top of this page. There is no notification system since we don't have your email address.