--- title: "Getting started: how to use Proxy Mail QA · Proxy Mail QA" description: "Step by step: create an account, make a disposable test address, use it in the app you're testing, and copy the code or click the link the moment the email lands." url: https://proxymail.qa/getting-started --- 1. [Home](https://proxymail.qa/) # How to use Proxy Mail QA From a new account to a verified test sign-up in a few minutes. Everything below happens in the app at app.proxymail.qa. Updated October 12, 2026 ## 1\. Create your account Open [app.proxymail.qa](https://app.proxymail.qa/?mode=signup) and choose **Create account**. Sign up with your email and a password, or **Continue with Google**. If you used email, confirm it from the message we send you. This is your login, so use your real work email here. The test addresses come next. ## 2\. Set up your project Your account starts with a project called **My project**, ready to use. Projects keep each client or app separate, so you might have one for Client A’s staging site and another for your own app. To change a project, open the project switcher at the top left and choose **Edit project**, or **New project** to add one. You can set: - **Website**: the site you’re testing, one click away from the app. - **Email prefix**: a short tag such as `cnn`, so every new address in the project starts with `cnn-`. - **Mail domain**: whether new addresses use @mailclub.dev or @enable.li. - **Environments**: labels such as staging and production. ## 3\. Create a test address On the **Accounts** page, choose **Add account**. In the dialog: - **How many**: one address, or up to 50 at once. - **Lasts**: from 1 to 7 days. - **Address**: **Random** (12 characters), **Custom name** (checked as you type, with free alternatives if it’s taken) or **Persona username**. - **Domain**: the picker at the end of the address switches between @mailclub.dev and @enable.li. - **Label** (optional): what the address is for, such as “Checkout test”. - **Generate persona**: a fictional first name, last name and username for forms that ask for them. Choose **Create address**. The new address is copied, ready to paste. ## 4\. Use it in the app you’re testing Paste the address into the form you’re testing: sign-up, magic-link sign-in, password reset, an invite or an order. Submit it. Most mail arrives within seconds. ## 5\. Copy the code or click the link You don’t need to open the email. The address’s row on **Accounts** updates by itself and moves to the top: - A **code** appears with a **Copy** button, and a countdown when the email says how long the code lasts. - A **link** becomes one button named for what it does, such as **Activate account**, **Sign in**, **Accept invite** or **Reset password**. - Until something arrives, the row says **Waiting for mail…** We never open links ourselves, so single-use links still work when you click them. To find a row quickly, use the **Codes**, **Links** and **Expired** filters, the tag filters, or search by email or service. ## 6\. Read the full email when you need to Choose **Open inbox** on a row to see every message for that address: who sent it, when it arrived, which service it came from, and every code and link found in it. HTML email is shown in a locked-down view with scripts off. Remote images stay blocked, so tracking pixels don’t fire, until you choose **Load remote images**. If the row picked the wrong code or link, choose **Use this instead** on the right one, and the row switches to it. ## 7\. Keep the details of each test account Click an address on its row to open its details: - **Saved password**: save the password you signed up with, or **Generate** one. It’s encrypted and hidden, and every reveal is logged. The row’s password column copies it in one click. - **Persona**: copy any field or **Copy all**, or get a **New persona**. - **Notes and tags**: write what the account was for, such as “youth account on staging”. Tags become filters on the Accounts page. - **Lifetime**: see when the address expires and **Extend 1 day** at a time, up to 7 days from when it was created. ## 8\. Clean up, or let addresses expire Delete an address from its details with **Delete address**, or tick several rows and choose **Delete**. When an address expires, new mail to it is rejected, and the address, its mail and any saved password are deleted within an hour. Deleted and expired names are never given to anyone else. Keep test accounts test-only: no personal email, real people’s data, or passwords you use anywhere else. ## 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) ## Questions ### No email has arrived. What should I check? Copy the address from its row rather than retyping it, and check it hasn't expired (expired addresses reject mail). Then check the app really sent the email, in its logs or its email provider's dashboard. Most mail lands within seconds; rows update live, and the Refresh button checks again. ### The app I'm testing rejects @mailclub.dev. What now? Some sign-up forms block domains they think are disposable. Switch the domain picker on the address to @enable.li, or set enable.li as the project's mail domain so every new address uses it. ### The verification link points to localhost:3000\. Is that a bug? Usually it's the app's configuration: it is sending its local address instead of the site's real one. Such links are flagged on the row and in the inbox. If you are deliberately testing a local build, mark the host as your dev environment and it stops being flagged. The localhost links guide has fixes for Supabase, Firebase and other stacks. ### Can I use one address for several test runs? Yes. Mail sent to name+run2@mailclub.dev arrives in the inbox for name@mailclub.dev, so you can tell runs apart without creating new addresses. For separate accounts in the app you're testing, create one address each; up to 50 at once. ### Can my teammates see my addresses? Not yet. Every address is private to the account that created it. Shared team workspaces come with the Team plan. ### Can I send email from an address? No. Test inboxes are receive-only: they never send, reply to or forward mail. ## 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) - [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) [See every email testing problem we solve →](https://proxymail.qa/solve)