Test the email your app actually sends.
Test signup and recovery on a subdomain we host. Your app uses its normal sender; PigeonProbe shows what arrived in your browser, CI or read-only agent tools.
From $19/month for 3 people.
14-day trial. No card or automatic subscription.
Read the video steps
- Create a fresh PigeonProbe address for this test.
- Receive the signup email and follow its confirmation link.
- Request a password reset and check the recovery email.
- Change the password, then sign in again to check that it works.
- Both email flows passed. Clean up the test account and address.
Include the inbox in the journey
From signup to received message
Finish the test your customer depends on. Submit the form, receive the email through your normal sender, and check its content and delivery evidence.
Give the test a recipient
Create a test address on a subdomain PigeonProbe hosts. Keep one for a recurring flow or use a fresh address for each run.
reset@acme.pigeonprobe.netTrigger your normal sender
Use that address in your staging signup or reset flow. Your app sends through the provider it already uses, so the sending path stays in the test.
Check what arrived
Open the received message with your team. CI can check its recipient, link, code or body text; an AI agent can inspect the same permitted inbox.
Start free trial14 days. No card.
A successful send is the start of the test. The inbox shows the received message, its content and the checks recorded at delivery.
Staging
ReceivingInspect test mail and its delivery evidence.
reset@acme.pigeonprobe.netDelivery evidence
See what reached your test inbox
Read the received message and the checks recorded when it arrived.
Received: from mail.acme.example.com
by mx1.in.pigeonprobe.com; 19 Sep 2026 09:41 UTC
From: no-reply@acme.example.com
To: reset@acme.pigeonprobe.net
Subject: Reset your Acme password
Use the code below within 15 minutes.
418-207Checks recorded on arrival
- SPF
- pass
- mail.acme.example.com
- DKIM
- fail
- no key for s=mail
- DMARC
- pass
- on SPF alignment
- TLS
- yes
- ESMTPS on delivery
See which check needs attention alongside the ones that passed.
The same evidence for everyone
Let an AI agent check the same inbox
A connected agent can wait for the message, pull out a link or code, and continue the test. Your team can open that same email to review the result. Agent access is limited to the mailboxes you allow, and its tools are read-only.
Find your workflow
Make email part of the test
Email testing with Playwright
Complete signup and reset tests through your normal sender. Wait for the received email, then check its link or code in Playwright.
Test signup and password-reset email
Take signup and password-reset tests past the “email sent” screen. Check the received link, code and recipient, then finish the journey in your app.
Test email-domain allowlists
Keep a stable hosted domain for allowlist tests and give each run a fresh address. Exercise both accepted and rejected signups.
Email QA for agency client projects
Give each client project a test inbox its team can review. Keep access and ownership clear as work moves between agency and client.
Start with the runnable local Node.js and Playwright example →
Try a real flow
Put your next signup email to the test
Use your existing sender and a PigeonProbe test address.