D.PRO has no accounts and no sign-in. This page describes what happens when you use it.
Cookies and tracking
D.PRO runs no analytics of its own: no Google Analytics, no first-party tracking pixel, no profiling of visitors by the site. Your last-used target is kept in your browser's local storage so the form is pre-filled next time, and it never leaves your device. D.PRO's own code sets no cookies.
Two third parties set cookies through this page. Cloudflare, which hosts the site and runs the bot check, may set functional cookies and processes standard request metadata (IP address, user agent, timestamps) under its own privacy policy. Google sets cookies to serve the ads on the page, described under Advertising below.
Running a check
When you start a monitor, your browser opens a WebSocket to the backend and sends the domain, record type, TTL, and the OLD / NEW values you entered. Those values are used to perform the DNS lookups for that session. A copy of the same fields is also written, with the time of the check, to a private database (Convex) so the maintainer can see how the tool is used — for example whether traffic is real checks or automated homepage loads. The homepage starts a demo check on its own; those rows are marked as demos.
Alongside the form values we store a coarse location that Cloudflare already attaches to the request: country, region, city, continent, and the network's organisation name (for example an ISP or cloud provider). Your IP address is not stored with that record. This is not sold and is not used to personalize ads. The lookups themselves go to public resolvers (Cloudflare, Google, Quad9, OpenDNS, AdGuard, DNS.SB, IIJ) over DNS-over-HTTPS.
Rate limiting
To stop abuse, the backend limits how many concurrent sessions one client can open. Your IP address is hashed (SHA-256) and held only in memory for the life of the counter; it is never written to disk and is never sent to the component that runs your lookups, so no stored record links an IP to a watched domain.
Bot check
When traffic is high, Cloudflare Turnstile may run a lightweight browser check before a session starts. Turnstile is privacy-focused and does not use tracking cookies for advertising; see Cloudflare's policy linked above.
Advertising
D.PRO is free and supported by ads served through Google AdSense. Google and
its ad-technology partners set cookies in your browser: some as first-party cookies on
dnspropagation.pro (for example __gads and __gpi, which
cap how often an ad is shown and measure its performance), and some as third-party cookies
from Google's ad domains. Google may also use your prior activity to personalize the ads you
see.
Visitors in the UK, EEA and Switzerland are shown a consent choice before any advertising cookie is set, and can decline personalized ads. Anywhere, you can review or turn off ad personalization in Google Ad Settings. For how Google uses data from sites that use its services, see Google's privacy policy and its partner-sites notice.
Logs
Cloudflare keeps short-lived edge logs for security and reliability. The application keeps the per-check records described under "Running a check" until they are no longer useful for understanding usage, then they can be deleted. We do not keep a log that ties an IP address to a watched domain.
Changes
If this notice changes materially, the "last updated" date above will change. Continued use after a change means you accept the update.
Contact
For any question about this notice or the data described here, email hello@dnspropagation.pro.