Temporary email for magic-link login testing: a manual guide
Updated 6 November 2026.
Use a temporary email inbox to manually test a magic-link login in an application you own or are authorised to test. Check the email, the browser session and the signed-in account separately. A delivered login email does not prove that the passwordless sign-in flow works, and a temporary address is unsuitable for an account you need to keep.
Start with a controlled test account
Open an active 1hemail inbox and copy the address into your staging application's passwordless login form. Record the time and keep the original login tab open. Use an account with no real customer data or production privileges. Choose a mailbox lifetime long enough for the test using the temporary email lifetime guide. The mailbox timer and the login link's expiry are independent.
Inspect the message before following the link
Confirm that the subject, sender and sign-in explanation match the application you are testing. Check that the destination belongs to your intended test environment, rather than a production account or unrelated domain. Treat the complete link as a credential: do not paste it into public bug reports, analytics tools or shared screenshots. Your private 1hemail inbox link is a separate credential and also needs protection.
Preserve the browser context required by your app
Some passwordless implementations require the link to open in the same browser and device used to request it. A link opened on a phone or in a separate browser profile can therefore fail even when mail delivery succeeded. Follow your authentication provider's documented flow. For example, Okta's magic-link overview discusses browser and device context. Do not assume every authentication product applies identical rules.
Verify the resulting identity and destination
After using the link, check that the application signed in the intended test identity and opened the expected page. Test in a clean session so an existing login cannot hide a failure. A success message is insufficient if the account identifier or organisation is wrong. Record the outcome without publishing active session cookies or tokens. If your application has roles, confirm the test account receives only its expected access.
Check expiry, reuse and replacement requests
In staging, test an unused link after its configured expiry and compare the result with your specification. Test reuse if the design calls for a single-use link. Request a replacement and establish whether the earlier link should remain valid according to your provider's rules. Keep the messages distinguishable by request time. Do not infer a security defect solely because two providers implement replacement links differently.
Separate mail problems from login problems
If nothing arrives, inspect your sender's logs and the active inbox address before requesting repeated messages. If the email arrives but login fails, inspect the redirect configuration, expiry and browser context. See the two-timer troubleshooting guide for the expiry distinction. 1hemail is receive-only and has no public testing API; for unattended regression suites, choose a dedicated email testing service. Use a durable mailbox for real passwordless accounts.
See also: Temporary email for team invitation testing: access and roles.