Proxy Mail QA

Proxy Mail QA gives ChatGPT and Codex disposable email addresses for testing the emails your app sends. Ask things like:

• "Give me a test email for my staging sign-up and tell me the code when it arrives."
• "Why isn't my app's verification email arriving?"
• "Check the password-reset email my app sent to my test address."
• "Sign up on localhost:3000 with a new test account and confirm the email." (Codex, or an agent with a browser)

It creates an address with a fictional name, username and, if the form needs one, a strong password. You sign up with it, or the agent does when it can use a browser, and you get the verification code or link as soon as it arrives. It works the same for login codes, magic sign-in links, password resets and invites, and it can check the email itself: SPF, DKIM and DMARC, links that point at localhost, the stated expiry and how it fits on a phone. When nothing arrives, it shows what reached the address, anything refused, and the likely cause. It can also fill a whole sign-up form's values (a username with rules, a date of birth, a country), suggest awkward names and passwords to test a form's validation, and look up how something works in Proxy Mail QA's docs.

Results contain only the code or link, the service that sent it and when it expires, never the email's text, so an email can't pass instructions to your agent. Proxy Mail QA never opens links, so single-use links still work. Addresses last up to 30 days and only you can read their mail. Addresses are receive-only: nothing is ever sent from them.

When you connect, you sign in to Proxy Mail QA (or create an account and your first project on the way) and choose one project; the agent works only in that project and can't read passwords saved earlier. Disconnect it any time in Project settings → API keys.