How to test email sending without spamming real users
Set up an SMTP test server that accepts any recipient and never delivers. Step-by-step setup for Laravel, plain PHP, Python and Node, plus what to check before you go live.
Catch messages sent over SMTP and inspect any HTTP request in real time. Perfect for staging and local development: no real inboxes, no surprises for your customers.
Three steps from your application to the sandbox.
Sign up and generate SMTP credentials for an inbox, or a catch-all URL for webhooks.
Put the host, port, username and password into your application, or send an HTTP request to the webhook URL.
Emails and requests appear instantly with full headers, body, attachments and metadata.
Everything you need to test mail and integrations safely.
Point any SMTP client at it. Messages are parsed and stored — HTML, text, headers and attachments.
One URL that accepts any method and content type, capturing method, URL, headers, body, IP and time.
Share results with a link that can expire and can be revoked instantly.
Find messages by sender, recipient or subject, and requests by method, URL or body.
Lists refresh themselves, so new emails and requests show up without reloading.
Captured data is deleted automatically after a configurable retention window.
English and Russian interface, switchable any time from the header or your profile.
All timestamps are shown in the timezone of the visitor, automatically detected.
See the exact request your provider sends: query string, headers, JSON body and the originating IP. Then delete it, search it or share it.
Step-by-step articles: set up an email sandbox, debug webhooks and keep your test data private.
Set up an SMTP test server that accepts any recipient and never delivers. Step-by-step setup for Laravel, plain PHP, Python and Node, plus what to check before you go live.
Give every integration a stable catch-all URL, inspect method, headers, query and JSON body, then replay the payload. Works without opening ports on your laptop.
An honest comparison of hosted email sandboxes and a self-hosted one: price, data privacy, noindex guarantees, offline work, maintenance and when hosted still wins.
Hand a read-only share link to your AI assistant: the same token answers as JSON or plain text, so a model can review subject, headers, links and body of every captured email.
Correct. The SMTP server only accepts the message, stores it and shows it in your dashboard. It never relays or delivers mail to a real mailbox — any recipient address is accepted and discarded.
You get a unique URL. Any HTTP request sent to it (GET, POST, PUT, PATCH, DELETE, OPTIONS, HEAD) is captured with its method, path, query string, headers, body, IP and time.
Yes. Create a read-only link to an inbox or a webhook, choose how long it stays valid, and revoke access at any time.
Yes, it is a free self-hosted tool. There are no plans or hidden limits — you run it on your own server.
No. Every shared link, captured request and app page sends noindex directives, so search engines never store your test data.
Create an inbox, copy the SMTP credentials and stop worrying about accidentally emailing real customers.
