About us
Mailcraft — email mailboxes on our own domains
We run the domains, the mail server and everything in between, so that the message with your confirmation code arrives and you can read it.
- Domains in the pool
- 28
- Mailboxes ready to issue
- 164,217
- Messages delivered
- 1,389,665
These come from the service's own database and refresh hourly. Current state, not a marketing number.
Mailcraft rents email mailboxes on a pool of domains we own. Unlike public temp mail, every domain belongs to the project, is configured properly (MX, SPF, DKIM, DMARC) and is maintained: its reputation is watched, and a domain with something wrong with it is taken off sale rather than sold on.
You choose a plan, a term and a quantity, and the finished list is there as soon as payment clears — the mailboxes come from stock prepared in advance, so there is nothing to wait for. Every mailbox is reachable through webmail and over IMAP, its password is visible to its owner in the dashboard, and the whole list exports in four formats.
The service receives mail only: sending is not supported, neither as a feature nor as a workaround. Bulk mail, spam and any unlawful activity are expressly forbidden by the Terms.
What we do to keep mailboxes working
A mailbox stops being useful not when it breaks, but when a sign-up form refuses its address or a message fails to arrive. Nearly all of our work is about that.
- 01
Every domain serves a real website
A domain that accepts mail and shows nothing at all at its own address looks odd — and it is cheap for a filter to check. So the root of every pool domain serves its own separate site: not a placeholder, and not a copy of its neighbour, because repetition is exactly what gets spotted.
- 02
Reputation is re-checked daily
Every domain in the pool is checked against Spamhaus each day. A listed domain is pulled from issuance rather than sold on, even when warm stock still sits on it. A domain carries the reputation its previous holder earned, so one check at purchase is not enough.
- 03
The mail route is verified continuously
A domain that announces where its mail should go and then stops accepting it is taken out of circulation automatically. An address a form accepted but that never receives anything is the worst possible outcome: you find out late, after you have already used it.
- 04
A mailbox cannot outlive its domain
Each mailbox's life is capped by its domain's registration, and that date is reconciled with the registrar daily. A domain with less than two months left is not used for new orders — so nobody is handed a mailbox that will vanish before the term they paid for ends.
- 05
An order is spread across domains
A batch is not drained out of a single domain. Nobody can guarantee a domain's reputation forever, but it can be arranged so that one bad outcome takes out part of an order rather than all of it.
- 06
If we cannot deliver, the money comes back
When stock did not cover the full quantity, the undelivered part is refunded automatically — no support request, no correspondence. The order keeps a record of how much was ordered in the first place.
Infrastructure and data
Our own domains
Domains are registered and maintained by the project, with DNS on Cloudflare. A domain is checked before it enters the pool and stays under daily observation afterwards.
Our own infrastructure
The mail server runs on our own hardware in Europe. There is no third-party mail service between your message and us that would have to be trusted.
Encryption and privacy
Mailbox passwords are stored encrypted and account passwords as hashes. Access to mail is isolated per account: nobody can see someone else's mailbox. Buying requires no documents and no selfie.
Terms you can read
A public offer, a refund policy in plain words, payment by card or cryptocurrency. No hidden charges and no automatic renewal billing.
Support
Requests are handled in the dashboard: a ticket with attachments, the whole exchange in one place, statuses visible to both sides. Every new request and every customer reply raises a notification immediately, and once a day a digest arrives carrying the number of tickets still awaiting an answer — built after one request sat unnoticed for four days. We deliberately do not promise a response time: a promise nobody can honour around the clock is marketing, not support. Here is what we do promise: a request will not get lost.
Questions? Email us at contact@mailcraft.org .