---
title: "An email address for checking my sign-in form · Proxy Mail QA"
description: "Test accounts for a sign-in form whose email you can read: saved passwords, sign-in codes, magic links and the password reset."
url: https://proxymail.qa/solve/email-for-checking-my-sign-in-form
---

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

# An email address for checking my sign-in form

Testing a sign-in form sounds simple: type the email and password, press the button. But you need an account that exists, in a known state, with a password you know, and, for codes, magic links and resets, an inbox you can read. Your own email address can only be one account, mixes the test mail with your real mail, and can't be handed to a teammate or a test suite.

Updated 5 November 2026

> **Our recommendation, up front.** We make Proxy Mail QA, so we’re not neutral. For testing a sign-in (log-in) form, we recommend it for test accounts whose email you can read: each has its password saved with it, sign-in codes and magic links arrive in a real inbox, and the password-reset email can be followed all the way through. It doesn’t test social sign-in (Google, Apple, Microsoft), SMS codes, authenticator apps or passkeys, and it doesn’t fill in or submit the form for an AI agent or a test: they do that.

## What a sign-in form test covers

1. The right email and password sign in.
2. A wrong password gets a clear message that doesn’t say whether the email has an account. An email with no account gets the same message.
3. The email typed in capitals, or with a space at the end, signs in to the same account.
4. A sign-in code or magic link arrives, works once, and stops working when it expires or a newer one is sent.
5. **Forgot password** sends an email whose link works once. Afterwards the old password fails and the new one works.
6. After too many wrong passwords, the account is locked or slowed down, and any unlock email arrives.
7. Password managers fill the form: the fields have `autocomplete="username"` (or `email`) and `autocomplete="current-password"`.
8. After signing in, the person lands where they were going, not always on the home page.

## Test accounts you can sign in as again

- **Make one** with a saved password. In the API or from an agent, create an address with a password (`password: true`). In the app, use **Generate a test password** on the address and save it. With Proxy Mail QA for Chrome, sign up as usual: after you submit, it asks whether to save the password you used to that test address. Saved passwords are encrypted, and every time one is read it’s logged.
- **Sign in as it again, by hand.** On a sign-in form, the extension’s button offers your project’s test accounts, the ones used on that site first, and fills the email and its saved password.
- **Sign in as it again, from an agent or a test.** `get_sign_in` (MCP) or `signInAccount` (npm) returns the account used on that site and its password in one call. Both need an API key created with **Can read saved passwords**, and every read is logged. An agent connected through the Qoder Marketplace signs in to Proxy Mail QA with your browser instead of a key, and can’t read passwords saved earlier: it uses the password of an account it made in the same session, or you connect it with such a key ([MCP server setup](https://proxymail.qa/docs/mcp)).
- **After the password changes**, save the new one with `set_password` (MCP) or `setPassword` (npm), so the next test signs in with the right one.
- **When tests run in parallel**, borrow accounts from the account pool: `check_out_account` gives a test an account in a known state (by tags such as `verified`, or by age, country or having a saved password) that no other test has until it’s returned.

TypeScript

```ts
import { ProxyMailQA } from 'proxymail-qa';

const qa = new ProxyMailQA(); // a key with "Can read saved passwords", in PROXYMAIL_QA_API_KEY

await qa.withAccount({ tags: ['verified'] }, async (account) => {
  const { secret } = await qa.savedPassword(account.address);
  await signIn(page, account.address, secret); // your own sign-in steps
});

```

## Sign-in codes and magic links

For a form that emails a code or link instead of asking for a password:

- `wait_for_code` waits up to 30 seconds and returns the code; `unused: true` skips one already used, so a second request gets the second code.
- `wait_for_link` returns the magic sign-in link. Proxy Mail QA never opens it, so it’s still unused when you get it.
- `check_email` checks the email: SPF, DKIM and DMARC, that the link goes to the site you’re testing (`expect_host`), and whether it says when the code stops working.

The server’s `test_sign_in_code` prompt borrows a verified account and signs in with the code or link the app emails. More in [testing one-time codes](https://proxymail.qa/solve/otp-code-testing) and [testing magic links](https://proxymail.qa/solve/magic-link-testing).

## Capitals and plus tags

`get_address_variants` gives versions of a test address that still reach its inbox. Two matter at sign-in:

- **Capitals** (`K7F2X9AB12CD@MAILCLUB.DEV`). Signing in with them should reach the same account as the plain address. If it fails, people who type their email with a capital letter can’t sign in.
- **A plus tag** (`k7f2x9ab12cd+work@mailclub.dev`). To most apps that’s a different account. Decide whether yours treats it as the same one, and test that it does what you decided.

## Password reset

The `test_password_reset` prompt borrows a verified account, resets its password through your app, checks the reset email, saves the new password on the account and returns it to the pool. Then check the old password no longer signs in. More in [testing password resets](https://proxymail.qa/solve/password-reset-testing).

## Ask your agent

With Proxy Mail QA connected in Qoder ([Marketplace](https://qoder.com/en/marketplace/connector?id=proxymail-qa)):

Prompt

```text
Test the sign-in form at https://staging.acme.dev/login with Proxy Mail QA. Start a run.
Create a test address with a password (create_address, password: true), sign up with it
at https://staging.acme.dev/signup and finish the verification. Sign out.
Sign in with it. Then try a wrong password, an email with no account, and the address
in capitals, and compare the messages.
Use "Forgot password", finish the reset with the link from the email, save the new
password with set_password, and check the old one fails.
Finish the run and give me the report.

```

The agent keeps the password from `create_address` for the session, so this works with the Marketplace connection, which can’t read passwords saved earlier.

## What it doesn’t cover

- **Social sign-in.** Sign in with Google, Apple or Microsoft uses accounts at those services, which Proxy Mail QA doesn’t make. Use each provider’s test accounts.
- **SMS codes, authenticator apps and passkeys.** It receives email only.
- **Rate limits and lockouts at scale.** You can check that a lockout email arrives, but load testing needs a load-testing tool.
- **Your live site.** It’s for staging or local copies of apps you build or are allowed to test.

## 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-sign-in)

## 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 registrationA new, real address for every registration try, with the code or link ready to use.](https://proxymail.qa/solve/email-for-checking-my-registration-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)