Email testing use cases
Perenmail gives you private, registered-only inboxes on real domains, built for manually testing the email your own product sends. Point a signup, OTP, password-reset, transactional or scheduled send at an address you control, and inspect exactly what arrives — live, in one place, on an inbox that stays put until you archive it. These are the jobs developers reach for it most.
Test OTP & 2FA email flows
Catch one-time codes as they arrive and copy them in one tap.
Read the guideTest password-reset email flows
Receive the reset mail, open the tokenized link, retest expiry.
Read the guideTest email verification & signup confirmation
Verify the "confirm your email" step end to end.
Read the guideQA email in staging
Durable private mailboxes for verifying staging mail without spamming real users.
Read the guideCatch delayed, cron & scheduled email
Mail that fires hours or days later is still waiting for you.
Read the guideTest webhook-triggered email
Confirm the email your webhooks and async jobs kick off actually sends.
Read the guideTest transactional email
Check receipts, order confirmations and account notices arrive and render.
Read the guideWant the concepts behind the workflows? The Learn guides cover email testing and deliverability from the ground up, and the FAQ answers how persistence, live delivery, and the free versus Personal+ plans work.
Pick a flow and watch the mail land.
Create a private inbox on a real domain, point your app's email at it, and inspect exactly what arrives. Free forever, no credit card.