Diagnostics run on our own network · BDIX-peered · Dhaka & Miami Engine operational Docs
MyDCHub Workspace Check a domain
Home / Privacy

Privacy

What MyDCHub collects, how long it keeps it, and who else sees it. Written to describe what the software actually does, not what a template says it might.

The short version

The tools need no account. We do not sell data, we do not build advertising profiles, and we do not publish or index the reports you run.

Two things do leave our servers, because the checks cannot work otherwise: the domain or address you are checking goes to the public DNS system and to the blocklists being asked, and a speed test fetches the page you named from our probe nodes. Both are set out below.

What we collect when you use a tool

The domain or IP address you type, so the check can run. Your IP address, kept in memory to apply rate limits and the daily allowance on the speed test, and to recognise addresses exempted from those limits. Ordinary web server logs.

No account is created, and nothing you check is tied to a person.

Reports and shareable links

A report link is not listed, indexed or advertised. It is also not secret: anyone holding the link can read the report, so treat the link the way you would treat the result.

Site previews expire on their own after seven days. A preview affects only a device whose owner has deliberately pointed it at our resolver, and no site traffic passes through us.

Mail check, which receives a real message

The mail check gives you a single-use address and reads the message you send to it, so it can report what your mail server actually did rather than what your records claim.

That message is deleted after one hour, by a sweeper that runs continuously — not a promise to delete on request. One message per address; after that the address is dead. Messages over 2 MB are refused at the SMTP conversation rather than accepted and truncated. Addresses are unguessable and the result is only reachable with the token. Nothing is indexed and nothing is kept beyond the hour.

Send test messages, not real correspondence. A message you send here is a message you have chosen to place on our server, and anyone with the link can read it for that hour.

Monitoring, if you subscribe

Monitoring stores the domains you asked us to watch, the results of each scheduled check so we can tell you what changed, and the email address alerts go to.

An address is confirmed before anything is sent to it, so nobody can sign somebody else up for mail from us. Stop paying and monitoring stops; the tools carry on working and existing report links keep resolving.

Who else sees what, and why

These are the third parties involved in running a check. Each one sees only what its part of the check requires.

Public DNS resolversThe name being looked up. Unavoidable: a DNS checker works by asking the DNS.
Blocklist operatorsThe IP address or domain being checked, sent to each list asked. That is what a blocklist check is.
SpamhausThe address being checked, through their Data Query Service, so the answer comes from them rather than from a rate-limited guess.
The site you testA speed test or SSL check connects to the address you named, from our nodes in Dhaka or Miami. It appears in that site's logs as a visit from us.
GoogleChrome UX Report field data for a speed test, which means the origin URL is sent to Google. reCAPTCHA, where a check needs to confirm you are a person. Tag Manager and analytics on our own pages.
CloudflareSits in front of this site, so it handles the connection and sees your IP address.
JetsNextOrders, invoices and payment are handled by the store, not here. MyDCHub never sees card details.

Cookies

The tools set no cookie to work. A workspace session sets one, so the browser stays signed in. Google Tag Manager and reCAPTCHA set their own on the pages that load them.

Asking us about your data

Write to [email protected] and say what you would like removed. Most of what this page describes deletes itself on a timer, so in many cases there is nothing left to remove by the time a request arrives — which is the intended design rather than an evasion.

Changes

If this page changes in a way that affects what we keep or who sees it, subscribers are told by email before it takes effect.