Documentation
Email Blackhole gives you a throwaway inbox for testing email. Your app sends a signup, password-reset or receipt email; you read it in the browser, or your test reads it through an API. Nothing is ever delivered to a real person.
There are two ways in, and both end up in the same live inbox:
- A dummy SMTP server. Point your app's SMTP settings at it. Whatever your app sends is caught, whoever it was addressed to.
- A public address. Anyone on the internet can send mail to it (for example a real service you are testing, such as a signup form). You also see whether the sender passed SPF, DKIM and DMARC.
No account, no signup and no card are needed. Open the sandbox and you have working settings within a second.
Where to go next
- Getting started: connect your app in a minute, in Node.js, Python or from the shell.
- Test email in CI: wait for an email in a pipeline and read the link or code from it, without polling loops.
- Webhooks: have every received message sent to your own URL as signed JSON.
- Limits and plans: what the free sessions allow, and what a permanent inbox adds.
- API reference: every call, with the machine-readable description at /api/openapi.yaml.
Good to know
- Nothing is delivered onward. The SMTP server never relays: it only receives. Mail to
anyone@gmail.comthrough the sandbox lands in your inbox and goes nowhere else. - Free sessions are anonymous and temporary. They live in memory and end 60 minutes after you last use them. For anything that must survive, use a permanent inbox (plans).
- Email content is treated as hostile. HTML is shown in a sandbox with scripts disabled and remote images blocked until you allow them.
- Rules and privacy: Terms, Privacy and Report abuse.