---
title: "An email address for checking my registration form · Proxy Mail QA"
description: "Why each registration test needs a new, real email address, and how to get one for every try without using your own inbox."
url: https://proxymail.qa/solve/email-for-checking-my-registration-form
---

1. [Home](https://proxymail.qa/)
2. [What we solve](https://proxymail.qa/solve)

# An email address for checking my registration form

A registration form can only be tested properly with a new address each time. Here is why, and how to get one for every try without filling your own inbox.

Updated 5 November 2026

> **Our recommendation, up front.** We make Proxy Mail QA, so we’re not neutral. For testing a registration form, we recommend it when you need a new, real email address for every try, sent to through your app’s actual email provider, and you want the verification code or link without digging through your own inbox. If you only want to see the emails your app sends while you develop on your own machine, without them going anywhere, a local mail catcher such as Mailpit, or Mailtrap’s testing inbox, fits better. If you need SMS codes as well, look at Mailosaur or MailSlurp. Proxy Mail QA is email only, and its addresses expire after 1 to 30 days, so it isn’t for accounts you mean to keep.

## Why each try needs a new address

- **A registration works once per address.** The second try with the same address tests “You already have an account”, not registration.
- **Shared inboxes mix codes.** When two people or two tests use one inbox, one picks up the other’s code, and the test fails for no reason in your app.
- **Your own address isn’t test data.** It mixes test mail with real mail, can’t be handed to a teammate or a test suite, and ends up in your app’s database as a fake customer.

## The options, honestly

| Option                                                     | Good for                                                                                      | Watch out for                                                                                                                    |
| ---------------------------------------------------------- | --------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| Your own Gmail with plus tags (you+test1@gmail.com)        | One or two quick checks                                                                       | Every try lands in your personal inbox. Some forms refuse plus tags. Hard to automate                                            |
| A shared team inbox                                        | A handful of manual checks                                                                    | Codes from different tests mix. [Why that breaks tests](https://proxymail.qa/solve/shared-test-inbox)                            |
| A local mail catcher (Mailpit) or Mailtrap’s testing inbox | Seeing your app’s emails during development, without sending them                             | Mail never goes through your real provider, so sandbox mode, SPF, DKIM and DMARC aren’t tested. Your app has to be pointed at it |
| Public throwaway inbox sites                               | Nothing in a real project                                                                     | Anyone can read the inbox, and many forms block their domains                                                                    |
| Proxy Mail QA                                              | A new private address for each try, on staging or locally, by hand or from a test or an agent | Email only. Your provider must be out of sandbox mode. Addresses expire                                                          |

## What Proxy Mail QA gives you

- **A new address in one click**, in the [app](https://app.proxymail.qa/?mode=signup), from [Proxy Mail QA for Chrome](https://proxymail.qa/chrome-extension) in the form’s email field, or from the API, the npm package or an AI agent. Addresses are on `mailclub.dev`. If a form blocks that domain, use `enable.li` or `valida.te.it`.
- **A test persona to go with it**: a fictional first and last name, a username, a date of birth for the age you choose, a country, and a password if you ask for one.
- **The code or link, pulled out.** It shows on the address’s row in the app, in a card on the page with the extension, or comes back from `wait_for_code` and `wait_for_link`. Proxy Mail QA never opens links, so single-use links stay valid.
- **Private and receive-only.** Nobody outside your project can read the inbox, and it can’t send. When an address expires, mail to it is refused, everything is deleted within an hour, and the name is never used again.
- **Checks on the email** (`check_email`): SPF, DKIM and DMARC, links to `localhost` or plain `http`, where the link goes, whether it says when it expires, and a plain-text part.

## Testing the email field itself

Every address comes with variants that still land in its inbox, so you can check your form doesn’t refuse valid addresses:

| Your form should                      | Examples                                                                                                |
| ------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| Accept, and the email arrives         | Capitals, +signup, +o'brien, +r&d, +team/50%, the 64-character maximum before the @                     |
| Accept, though no inbox can take them | "john doe"@mailclub.dev, josé@mailclub.dev (useful for checking what your app does when delivery fails) |
| Refuse before sending anything        | No @, two @ signs, a space, two dots in a row                                                           |

Get them with `get_address_variants` from an agent, `GET /v1/addresses/{address}/variants` from the REST API, or `qa.variants(address)` in a test. The full list is in [unusual email addresses](https://proxymail.qa/docs/unusual-addresses). To check a form accepts a domain with three parts, make the address on `valida.te.it`.

## When the email doesn’t arrive

Usually it’s the sending side, not the form:

- **The email provider is in sandbox or test mode** and only sends to addresses you’ve verified: Amazon SES before production access, Resend without a verified domain, a Mailgun sandbox, Postmark before approval, or Supabase’s built-in email, which only sends to your team, and only 2 emails an hour.
- **The mail was refused**, for example for failing DMARC. The address’s row shows mail Proxy Mail QA refused, with the reason, and `check_delivery` explains the likely cause.
- **It’s from a blocked site.** Mail from a few big consumer services, such as Google, Instagram and Amazon, is refused: Proxy Mail QA is for testing your own app.

The **email-delivery-troubleshooting** skill in the Proxy Mail QA plugin for Qoder goes through these with your agent and fixes the cause. More in [troubleshooting](https://proxymail.qa/troubleshooting).

## What it costs

Free covers 500 addresses in total (up to 50 a day) and about 500 incoming emails a day, with the extension, the API and the MCP server included. Team is US$5 a month for a whole organisation, with no address limit.

## What it isn’t for

- **Accounts you mean to keep.** Addresses last 1 to 30 days.
- **Real people’s data.** Test personas are fictional; keep it that way.
- **Your own domain.** Receiving at an address on your company’s domain isn’t available yet.
- **Sending email, or SMS.** It only receives email.

## Try it on your next sign-up test

Free plan, no credit card. Create an address and watch the code or link arrive.

[Create a free account](https://app.proxymail.qa/?mode=signup&from=site-solve-email-for-checking-my-registr)

## Related guides

- [Test sign-up and email verificationA fresh, private address for every sign-up test, with the verification link or code ready the moment it lands.](https://proxymail.qa/solve/email-verification-testing)
- [Test OTP and one-time login codesCodes pulled out of the email with a Copy button and a countdown when the email says how long they last.](https://proxymail.qa/solve/otp-code-testing)
- [Test magic links and passwordless sign-inSingle-use links that are never opened or prefetched on our side, so they still work when you click them.](https://proxymail.qa/solve/magic-link-testing)
- [Test password reset emailsRequest, receive and use reset links, and keep the new password saved next to the test account.](https://proxymail.qa/solve/password-reset-testing)
- [Stop sharing one Gmail inbox for QAPrivate, disposable addresses for every tester instead of one shared mailbox and a pile of plus-addresses.](https://proxymail.qa/solve/shared-test-inbox)
- [Take QA notes by voice with Wispr FlowDictate what each test account is for, its state and what you found, straight into its notes, in seconds.](https://proxymail.qa/solve/voice-notes-wispr-flow)
- [Verification link points to localhost:3000Why emails from staging link to localhost, how to fix it in Supabase, Firebase and other stacks, and how we flag it.](https://proxymail.qa/solve/localhost-links)
- [Common Supabase sign-up and login problemsEmails that never arrive, links that expire or sign nobody in, and sign-ups that fail, with the fix for each.](https://proxymail.qa/solve/supabase-auth-problems)
- [Common Firebase sign-up and login problemsMissing verification and reset emails, verified users who still look unverified, failing links and sign-up limits, with the fix for each.](https://proxymail.qa/solve/firebase-auth-problems)
- [Sign-up and login problems in vibe-coded appsThe login bugs AI-built apps usually ship with: emails only you receive, links to the preview, missing pages, and what to ask the builder.](https://proxymail.qa/solve/vibe-coded-login-problems)
- [Test sign-up emails in PlaywrightA complete Playwright test for sign-up codes and links, from a fresh inbox to the report on the pull request.](https://proxymail.qa/solve/playwright-email-tests)
- [Test sign-up emails in CypressA complete Cypress test for sign-up links and codes, with the email waits running as Cypress tasks.](https://proxymail.qa/solve/cypress-email-tests)
- [Test sign-up emails with pytestA complete pytest test for sign-up codes and links, with Playwright for Python or Selenium and a one-file helper.](https://proxymail.qa/solve/pytest-email-tests)
- [Test coupon codes and welcome offersThe coupon with its discount, end date and arrival time, what checkout did with it, and a failure when an expired or reused one is accepted.](https://proxymail.qa/solve/coupon-code-testing)
- [Test unsubscribe links and one-click unsubscribeThe unsubscribe headers and link checked on every marketing email, and a watch that flags any marketing after unsubscribing, with no time limit.](https://proxymail.qa/solve/unsubscribe-testing)
- [Test that a welcome offer can't be claimed twiceVersions of one address that reach the same inbox, and a check that fails when the same person got the offer more than once.](https://proxymail.qa/solve/welcome-offer-abuse)
- [AI sign-up page reviewLet an agent check the sign-up through to the email: delivery, the link, how it was sent, and that only one arrives.](https://proxymail.qa/solve/ai-sign-up-page-review)
- [AI registration page reviewAn agent tries every field with values made for it, then finishes the registration through the email.](https://proxymail.qa/solve/ai-registration-page-review)
- [Review a sign-up page by handA checklist for your browser and phone, in the order that finds the most problems.](https://proxymail.qa/solve/how-to-review-my-sign-up-page)
- [Review a simple sign-up form12 checks for a form with an email, a password and perhaps a name.](https://proxymail.qa/solve/review-a-simple-sign-up-form)
- [Review a multi-page sign-up formOne test account across every screen, and the verification email wherever it comes.](https://proxymail.qa/solve/review-a-multi-page-sign-up-form)
- [Review a financial sign-up formThe emails, age and country rules and awkward values in a financial sign-up, and what needs other tools.](https://proxymail.qa/solve/review-a-financial-website-sign-up-form)
- [An email address for testing sign-inTest accounts with saved passwords and an inbox for codes, magic links and resets.](https://proxymail.qa/solve/email-for-checking-my-sign-in-form)
- [How long should a password be?NIST's numbers for password length and rules, and test passwords to check yours.](https://proxymail.qa/solve/how-long-should-my-registration-form-password-be)
- [No error for a password that breaks the rulesThe eight usual causes of a silent password field, and how to tell which one it is.](https://proxymail.qa/solve/why-is-my-registration-form-not-showing-password-errors)
- [Help me check my websiteA whole-site check in an afternoon, in the order that finds the costliest problems first.](https://proxymail.qa/solve/help-me-check-my-website)
- [Tools to build and check a websiteA toolkit by area, most of it free and none of it ours, except for account emails.](https://proxymail.qa/solve/tools-to-help-build-and-check-my-website)
- [What tools do I need for a website?The full list, then which parts a simple site can skip.](https://proxymail.qa/solve/what-tools-do-i-need-when-building-a-website)

[Built your app with an AI tool? Pick yours](https://proxymail.qa/built-with)