One inbox per test
Create separate email addresses for test users and parallel runs. Match each message to the inbox your test created.
A Mailinator alternative for email and SMS testing.
Private inboxes, real phone numbers and message APIs in one workspace. Test the code, the link and the complete customer journey with MailSlurp.
Trusted by teams at
Follow the message all the way to the inbox.
Trigger a signup, password reset or order confirmation in your app. Receive the actual email in MailSlurp and inspect its subject, sender, body, headers and attachments. A successful API response is only the start of the journey.
Explore end-to-end email testing
Wait for the right message
Use wait APIs and message filters to retrieve the expected email within a defined timeout.
Finish the customer journey
Extract the verification code or reset link, return to your app and check the next screen.
Email and SMS. One complete test.
A customer can sign up by email and verify a phone number in the same session. Give your test an inbox and a phone number, receive both messages and check the code before continuing.
Use MailSlurp with Playwright, Cypress, Selenium or your existing test runner. Keep the received message available when a failed run needs investigation.
Explore SMS testing
Make sure the email works for the person opening it.
An automated assertion can confirm the link exists. Device previews show how the delivered email looks, and Email Audit checks for broken links, missing images and content issues before a release.
See real-client previews
How to run your first end-to-end check
Create a test identity
Create an inbox for the test user, then enter its address in your application's signup or password-reset form. Use a separate inbox for each parallel run.
Receive and inspect the message
Wait for the expected email. Check the recipient, subject and content, then extract the code or URL your customer needs. The email testing guide covers the workflow.
Complete the action and repeat
Submit the code or open the link in your test session. Assert the application outcome, retain useful failure evidence and add the check to your normal test suite. Start with our Playwright email testing guide.
Try the flows your team cannot afford to miss.
Start with the received message
Run an account signup, a password reset and a phone verification. Give each test its own inbox or number, retrieve the correct message and complete the action in your application.
Investigate the email behind a failed run
MailSlurp adds real-client previews and Email Audit when the message itself needs review. Use a failed run to evaluate how easily a teammate can find the received content and identify what broke.
Questions before you switch?
Can I test email confirmation and SMS verification together?
Yes. Give the test user a MailSlurp inbox and a supported phone number. Complete the email link or code step, trigger the SMS and retrieve its code, then assert the final application screen. Keep each identity associated with its run so concurrent tests remain separate and failures can be traced to the relevant message. Explore email and SMS testing.
Can I use my existing test runner?
Yes. Use MailSlurp APIs or SDKs to create inboxes, wait for messages and retrieve codes or links from Playwright, Cypress, Selenium or another test runner. Complete the action in your application and assert the final state.
Can I use my own domain for test email addresses?
Yes. Use MailSlurp domains or connect a domain you control, then create dedicated inboxes for your test users. Configure the required DNS records and verify delivery before adding the addresses to your suite. Keep each inbox associated with its test run so replies, codes and links stay with the right user. Set up a custom email domain.
Make the next release a checked one.
Create a test inbox and complete your first email journey.