Fake email generator with a private inbox

Create a free MailSlurp account, generate a real email address for testing, and receive signup confirmations, OTP codes, password-reset links, invitations, notifications, and attachments without using a personal inbox.

Create your free account, then generate and open private inboxes in the MailSlurp dashboard.

Create a free test inbox See how it works

Signup test inbox

signup-4821@mailslurp.com

Receiving

Messages0 received

Fresh address, real delivered messages

Trusted by top companies worldwide

Generate a new email address for every test

Create an account-owned inbox in the MailSlurp dashboard and copy its address into any signup form, checkout, contact form, staging environment, or QA workflow. Use a separate identity whenever you need a clean starting point.

Generate an address

Gmail, Outlook, and MailSlurp inboxes available for email testing

An email delivered successfully to a private test inbox

Real address, real delivery

Use the generated address with a real application and receive the message it actually sends.

Email protected by a blue security shield and padlock

Private by default

Keep messages inside your MailSlurp account instead of exposing them through a public shared inbox.

A temporary email identity with a controlled expiry

Clean identities on demand

Create another inbox whenever a form, test account, or customer journey needs a fresh address.

Use each inbox from code or the webapp

Create and inspect inboxes from code, connect with standard mail protocols, ask AI to extract the details you need, or work visually in the MailSlurp webapp.

Connect with API, IMAP, SMTP, or AI

Use the REST API and SDKs, connect an existing mail client, send through SMTP, or extract structured data from a delivered email.

Choose how you work with an inbox

// Create an inbox, send to itself, and wait for the latest received email.
const inbox = await api.createInbox();
expect(inbox.emailAddress).toContain('@' + defaultDomain);
expect(inbox.id).not.toBeNull();
const body = 'test' + Date.now();
await api.sendEmail(inbox.id, { to: [inbox.emailAddress], subject, body });
const email = await api.waitForLatestEmail(inbox.id);
expect(email).not.toBeNull();
expect(email.body).toContain(body);

Create and inspect inboxes in the webapp

Create inboxes, open delivered messages, inspect content and attachments, and move between manual checks and deeper email analysis without writing code.

Receive the email your application actually sends

Open the delivered message in MailSlurp and check the sender, subject, HTML, text, links, codes, headers, and files. You see the final email after your application and email provider have processed it.

Start receiving email

Email and SMS messages flowing through the MailSlurp messaging pipeline

app.example.com/verify

Enter the email verification code

MailSlurp received the email and extracted its one-time code.

846201

The browser test fills this field with the code MailSlurp captured.

Verification and OTP codes

Confirm that signup and sign-in messages arrive with the correct one-time code.

Verification email with a secure link ready to open

Password reset and magic links

Open the delivered link and complete the account-recovery or passwordless-login journey.

PDF attachment received in a private test email inbox

Receipts and attachments

Receive PDFs, images, CSV exports, spreadsheets, and other files sent by the workflow.

How MailSlurp connects your messaging workflows

Use one platform to create email and SMS, test complete journeys, preview delivery, and turn incoming messages into structured actions.

MailSlurp

Email and SMS on demand

Create real inboxes and phone numbers, connect external mailboxes, and control messages from code or AI agents.

JavaScript
Gmail
Outlook
Claude

Device preview and placement

Review delivered email across major clients and see whether campaigns reach the inbox, promotions, or spam.

HubSpot
Salesforce
Mailchimp
Gmail

End-to-end QA testing

Test signup, OTP, password reset, and notification journeys from the frameworks your team already runs.

Cypress
Playwright
Postman
Selenium

Extract and automate

Turn emails and attachments into structured data, then route the result into downstream workflows.

Google Drive
ChatGPT
Zapier
Google Sheets

How to generate a fake email inbox with MailSlurp

Create the address, use it in the workflow you want to test, and open the delivered message. The same pattern works for manual checks and automated QA.

A new private MailSlurp inbox ready to receive email

Create a free account and inbox

A generated test email address entered into an account form

Use the address in your application

Enter it into a signup form, password-reset request, checkout, contact form, staging app, or email send.

A delivered test email with a link and attachment inside a private inbox

Receive and inspect the message

Open the inbox to read the delivered email, follow its link, copy its code, or download its attachment.

Use a fresh inbox wherever email changes the journey

Generate separate addresses for the customer, support, and operational workflows you need to check. Each inbox keeps the delivered result easy to identify and revisit.

Test signups without reusing accounts

Create a new identity for every registration check and confirm that each account receives the correct activation message.

Submit contact, demo, and trial forms

A generated email address used to submit a lead form

Use a generated work address to test lead forms, confirmation messages, routing, and follow-up email without a personal mailbox.

Check invitations and team onboarding

A team invitation delivered to a new private test inbox

Invite a fresh address, open the delivered email, and confirm that new users can join the right team or workspace.

Validate order, billing, and status notifications

Order, billing, and delivery notifications received by email

Receive purchase confirmations, invoices, delivery updates, and account notices exactly as your application sends them.

Automate the same inbox workflow when you are ready

Create a private inbox at the start of a Playwright, Cypress, Selenium, API, or CI test. Wait for the expected message instead of using fixed delays, extract the link or code, and keep parallel test runs isolated.

Explore the disposable email API

Parallel email and SMS test traffic running through MailSlurp

Playwright, Cypress, and Postman tests connected to a fresh inbox

One inbox per test worker

Give parallel runs separate addresses so one test never consumes another test's message.

Verification email code copied into a six-digit OTP form

Wait for the expected email

Match sender, subject, unread state, or timing instead of pausing the suite with a fixed sleep.

A sequence of retained test emails fading as their retention period ends

Expire or retain evidence

Clean up successful runs automatically and keep the message ID when a failed test needs investigation.

Fake email addresses built for real testing

MailSlurp combines a generated address with a working, private inbox. That makes it useful for checking delivered email manually today and automating the same journey later.

What does a fake email generator with an inbox do?

It creates an email address that can receive real messages without using your personal mailbox. With MailSlurp, the generated address belongs to your account and opens into an inbox where you can read HTML and text, inspect headers, follow links, copy verification codes, and download attachments.

Why use a private test inbox instead of public temp mail?

Public temporary inboxes are often shared by anyone who knows the address. A MailSlurp inbox is controlled through your account or API credentials, so test messages, reset links, codes, and customer-like data are not exposed on a public mailbox page.

Can a generated address test real application email?

Yes. Use the address in the same form or application flow a customer would use. The email is delivered through the normal sender and provider path, allowing you to check the final message produced by signup, authentication, billing, ordering, support, and notification workflows.

Can I generate a random email address for testing?

Yes. MailSlurp can generate a unique address automatically whenever you create an inbox. Use that random address for a clean manual check, create another for the next test identity, or choose a custom domain and inbox name when the address itself must follow a predictable format.

How does manual testing become an automated email test?

Replace the manual create, wait, and open actions with the MailSlurp API. Your test creates the inbox, enters the generated address, waits for a matching message, extracts the required link or code, and continues the browser or API journey. See the disposable email API for framework examples and CI patterns, or start with the inbox documentation.

Frequently asked questions

Answers about generated addresses, private inboxes, real email delivery, attachments, and test automation.

Do I need an account to generate a fake email address?

Yes. Create a free MailSlurp account, then generate and open private test inboxes from the dashboard. Signing in keeps each address and its messages controlled by your account instead of exposing them through a public mailbox page.

Is this a temporary email generator or fake Gmail inbox?

MailSlurp gives you a private generated email address for testing instead of a public shared mailbox or personal Gmail account. Create a short-lived inbox with an expiry for temporary work, or keep it as a repeatable test identity. The inbox can receive real messages from Gmail, Outlook, your application, or any other sender.

What happens after I create my account?

Open Inboxes in the MailSlurp dashboard, create a new inbox, and copy the generated address. Use it in the application or form you want to test, then return to the inbox to open the delivered message. Read the inbox documentation.

Can the generated address receive real email?

Yes. Send email to the generated MailSlurp address from your application, website form, email service provider, or any normal sender. The delivered message appears in the MailSlurp inbox with its sender, subject, HTML, text, headers, links, and attachments.

How long can I keep a generated inbox?

You can keep an inbox available for later testing or create it with an expiry for short-lived work. Retention and expiry controls let you preserve useful evidence while cleaning up addresses that are no longer needed.

Can I use my own domain or choose the email address?

Yes. MailSlurp can generate a random address automatically, and verified custom domains let you create addresses that follow your own naming and domain conventions. Set up a custom email domain.

Can fake email inboxes receive attachments?

Yes. MailSlurp inboxes receive normal email attachments including PDFs, images, text files, CSV exports, and spreadsheets. You can inspect attachment metadata and download the file for manual or automated checks.

Can I automate generated inboxes with Playwright, Cypress, or Selenium?

Yes. Create an inbox at the start of a Playwright, Cypress, Selenium, or CI test, enter its generated address into the application, wait for the expected message, extract the link or code, and continue the same browser journey. Read the Playwright email guide. Read the Cypress email guide.

Does MailSlurp also provide phone numbers for SMS testing?

Yes. MailSlurp provides real phone numbers for receiving SMS messages and testing OTP and MFA flows. You can use email inboxes and phone numbers together from the dashboard or API. Explore programmable phone numbers for SMS testing.

Create a private inbox for your next email test

Generate a real email address, receive the message your application sends, and keep every test away from your personal inbox. Start manually in the dashboard and automate through the API whenever you need to scale.

Create a free test inbox View the email API

A private MailSlurp inbox receiving a delivered test email