Status
Every domain you can create an alias on, and whether it can receive mail right now.
Checked , and refreshed automatically. Everything here is read from public DNS — you can run the same check yourself on Grade your domain.
Cloqd itself
Database reachableOur database answered when this page was last built, which means signing in and reading your inbox were working then. This reading is only as fresh as the timestamp above — it can predate an outage happening right now, so treat it as evidence rather than a guarantee.
Read at . Measured from the database query this page already makes, so watching it costs no extra load on the system it is watching.
While our database is unreachable, mail sent to any alias is refused with a temporary failure rather than accepted and lost. The sending server retries on its own schedule — typically for two to five days — and then bounces the message back to its author. An outage shorter than that delays your mail; one longer than that loses it, and the person who wrote to you is told so.
Encryption tiers on this deployment
A tier is only a promise if the server can keep it. This list is read from the configuration the mail pipeline itself checks, not typed here.
- StandardLive. Always available. Mail is stored readable, which is what full-text search runs on.
- Encrypted at restNot yet. No server-side encryption key is configured on this deployment, so this tier cannot be applied yet: choosing it is refused, and mail for an account that chose it earlier is stored readable with a downgrade marker rather than silently labelled as encrypted.
- Zero-knowledgeLive. Needs nothing from our side: mail is sealed to the public key on your account, whose private half is generated in your browser or imported by you.
discord.llc
Receiving mailMX: inbound-smtp.us-east-1.amazonaws.com
do.co.ke
Receiving mailMX: inbound-smtp.us-east-1.amazonaws.com
hackd.lol
Receiving mailMX: inbound-smtp.us-east-1.amazonaws.com
pooron.me
Receiving mailMX: inbound-smtp.us-east-1.amazonaws.com
starving.africa
Receiving mailMX: inbound-smtp.us-east-1.amazonaws.com
What this page can and cannot tell you
It reflects DNS as published. A domain shown as receiving has working MX records — which is a necessary condition for your mail arriving, never a sufficient one. It cannot see a provider throttling us, a signing key that has stopped matching, or mail that is accepted and then filed as spam.
“Could not check” means exactly that. It is shown as its own state rather than being rounded to a pass, because a reading from a check that did not run is not a measurement.
A domain we no longer offer for new aliases is not listed here. Addresses already created on one keep receiving mail, and we keep checking it.