Verify your receiving email
Sign in without a password using the code sent to your real inbox. The code only proves that you control the receiving address.
Use a different alias for each website. Messages still reach your usual inbox, while the signup site never sees your real address. If one source gets noisy, disable just that alias.
Enter your receiving email and we’ll send a 6-digit verification code. Once verified, you can view aliases, forwarding history, and sender rules.
An alias isn’t a new email account. It’s a controllable route between the signup site and your real inbox.
Sign in without a password using the code sent to your real inbox. The code only proves that you control the receiving address.
Create separate addresses for shopping, communities, subscriptions, or projects. Isolating sources makes it easier to identify who exposed or misused your address.
Aliases can be enabled or disabled individually. Once disabled, new messages to that address are discarded without affecting your real inbox or other active aliases.
See each alias’s status, successful forwards, spam classifications, and failures, then decide whether to keep, disable, or delete it. Deletion cannot be undone; if an account still uses that alias, change the email on that site first.
Add trusted senders to an allowlist to reduce false positives, or put clear sources of unwanted mail on a blocklist. An allowlist is not a security guarantee, so still treat unknown links and attachments with caution.
The console archive is for short-term delivery tracking, not permanent backup. Normal-sized messages are forwarded and retained for 30 days; after that, rely on the copy in your receiving inbox.
When you no longer want the messages, disable the alias instead of unsubscribing across multiple marketing systems.
Keep a password-reset route while isolating the data exposed to different websites.
Close the entry point when the project ends instead of abandoning the real email your team uses every day.
An alias can’t hide personal information in the email body or prevent phishing. Protect sensitive accounts with strong passwords and two-factor authentication.
Forwarding is not a black box. Every message moves along the same reviewable route.
The sender delivers to alias@tmpone.com. They only ever see the alias — your real address appears nowhere in the exchange.
Each message is scored on sender reputation and content signals. Blacklisted senders are blocked outright; suspicious mail is flagged as spam and held in the archive for your verdict.
Mail that passes screening is relayed to your verified receiving address within seconds, attachments included (up to 50MB per message).
The forwarding record stays in your console for 30 days — review it, retry failed deliveries, or report misclassifications — then it clears automatically.
One source, one alias is the easiest policy to keep: when an address leaks, the alias name tells you exactly who leaked it.
One alias per marketplace. If promotions get out of hand, disable that alias and move order notifications to a fresh one — other stores are untouched.
Newsletters and podcast updates funnel into topic aliases. When an unsubscribe link doesn't work, disabling the alias in the console does — reliably.
Use a dedicated alias per application or project, then disable it when it ends. You keep the correspondence without leaving recruiters a permanent way in.
Unsure how a site handles data? Use a clearly labelled alias. The moment unrelated mail arrives on it, you know the data was shared.
An alias proves its worth after things go wrong: you respond surgically instead of abandoning a whole mailbox.