Privacy

Scan data

We do not store scanned domains in a database. A scan request uses the domain you enter to look up public DNS records and return a result in the browser.

Result pages use query strings so you can refresh or share a scan state. Query-driven result pages are marked `noindex` so search engines should not index arbitrary scanned-domain URLs.

DNS resolvers and public records

DNS lookups are made against public DNS infrastructure, with Cloudflare DNS-over-HTTPS as the primary resolver and Google DNS-over-HTTPS as a fallback. DNS records such as MX, TXT, CNAME, A, and AAAA are public by design.

Analytics

Analytics are configured to avoid sending scanned-domain query strings. Result and fix page views are tracked using sanitized paths such as `/result` and `/fix`, and product events use broad categories instead of domains, email addresses, DNS values, or free-text feedback.

Paid reviews, assisted help and optional tips

The optional US$29 written review and US$99 assisted-fix intake send a normalized domain and your selected mail service, DNS host and problem category to our server. When you continue to checkout, we send those fields, the fixed offer ID and an opaque checkout reference to Stripe as order metadata. The intake has no email or free-text field. Stripe’s hosted Checkout collects your buyer email and payment information under Stripe’s privacy policy.

Stripe retains the order and payment information. We use Stripe Dashboard as the operational record for paid orders, and use your checkout email to deliver a written review or coordinate a working session manually. The optional US$5 tip does not request a domain or DNS intake and does not purchase a service. There is no order database or automatic fulfillment in this app. Our webhook application logs contain only a fixed event type and opaque checkout reference, never your domain, email, Stripe session or customer IDs, or payment details.

Your validated intake and a signed checkout intent are kept in this browser tab’s session storage to restore a cancelled checkout and avoid duplicate Sessions on retry. They are cleared on a verified successful return. Closing the tab clears this storage. The success link contains a Stripe session identifier so our server can verify payment; it is not sent to analytics or third-party referrers. Hosting providers may retain request/access logs under their own retention settings.

Payment analytics use only the fixed offer, CTA location, an allowlisted public guide or provider-page source where available, and the fixed offer amount (US$29, US$99 or US$5), USD and an opaque transaction reference for a verified purchase. We do not send intake values, domains, emails, Stripe identifiers, free text or URL query strings to Google Analytics. Manual assisted help never asks you to share passwords, API tokens, private keys, backup codes or inbox access. Optional self-service DNS connectors have separate credential entry and per-record approval flows.

Support and feedback

If you choose to email us or use an external feedback/support link, the information you submit goes through that action. Do not send passwords, private DKIM keys, recovery codes, or provider account access.

Contact: support@domainemaildoctor.com