Temporary Email in Telegram
By Denis · Published 2026-09-15.
Verification codes have a habit of arriving when you are nowhere near a browser tab. The Tempx bot brings the disposable inbox to where you already are: message @TempxEmailBot on Telegram and you have a working address in one tap, and the bot pushes a message the instant an email lands, so codes come to you instead of you going to check.
How it fits together
Start in one tap
- Open @TempxEmailBot in Telegram and press Start (that is
/start). - The bot replies with your address, a real, working inbox, no account, no password.
- Paste the address into whatever form is asking for an email.
- A 📩 New Email message arrives in the chat the moment mail lands, with the sender and subject; tap ✉️ Open Email to read it.
Everything also works from the inline buttons (🔄 Refresh, ✨ New Email) so you never have to remember a command.
The commands
| Command | Button | What it does |
|---|---|---|
/new | ✨ New Email | Generate a fresh address (the old one stays until it expires) |
/email | , | Show your current address, ready to copy |
/inbox | 🔄 Refresh | List the messages waiting in the inbox |
/qr | , | Send a QR code of the address, handy to scan into another device |
/help | , | The cheat sheet |
Notifications that behave
The push is the point: you hand the address to a sign-up form, switch back to whatever you were doing, and Telegram buzzes when the mail arrives, with the sender and subject in the notification and a one-tap open. If an inbox gets flooded, a built-in flood guard caps the messages (and you can always tap 🔕 Mute on any notification; the menu's 🔔 Unmute reverses it).
The Mini App: the full inbox, in-chat
Tap 📂 Open Inbox and the complete Tempx inbox opens as a Telegram Mini App (message list, full email view, attachments) without leaving the chat. Per-message ✉️ Open Email buttons deep-link straight to that email. It is the same inbox, the same sanitised HTML rendering and the same auto-deletion as the website, delivered where your thumb already is.
Longer memory than the anonymous inbox
A plain anonymous inbox on the website keeps mail for a short retention window. An inbox linked to your Telegram keeps messages for up to 7 days, long enough for order updates and slow verifications, still short enough that nothing piles up forever. /new swaps in a fresh address whenever you want a clean slate.
What the bot knows about you
Deliberately little: your Telegram user id, your @username, which inbox is linked and whether notifications are on. No phone number, no real name, no chat history, no message bodies stored beyond the inbox's own lifetime. Email content is treated as untrusted input everywhere (rendered through the same sanitizer the website uses) and the usual rule applies: never link an inbox you rely on for password resets on accounts you care about.
Related: Ask AI to test your email · Testing email with SMTP and MCP · How Tempx works
How long the address lives, and what expires when
An inbox created through the bot follows the same retention rules as the web product: mail ages out on a fixed clock (the same windows the site states, a short window for the default kind, seven days for named inboxes created from an account), and the address stops receiving after its lifetime ends. Practically, that means a bot-born address is for the mail you are expecting now (a login code, a wifi password, a one-off confirmation) not a channel you come back to next week. The bot's /new command exists for the rhythm: when the next form needs a fresh handshake, tap it and the new address arrives instantly, with the previous one quietly running out its clock.
Nothing is archived. A message that expires is gone from the bot chat's underlying inbox too, the push message in Telegram remains as a notification artifact, but re-opening it cannot summon deleted mail. If a code arrived and you have used it, that is the intended lifecycle, completed.
What the bot knows, the honest privacy picture
Two systems are involved in every bot interaction, and each sees its half. Telegram sees your chat with the bot: the commands, the pushed notifications, and (depending on your settings) your Telegram identity. Tempx sees the inbox side: the address, the messages, and their automatic deletion. The mail content itself travels the ordinary email network to reach the inbox, like any email to any provider. The convenience trade is explicit: push notifications mean new-mail events (sender and subject) pass through Telegram's delivery; if a particular signup's mail is sensitive, the browser inbox with its controllable remote images is the more conservative reader for the same address.
The bot inbox is guarded the way the product guards random inboxes generally: the address contains enough randomness that guessing it is impractical, and reading it requires knowing it. It is not a secrecy tool (same honesty as the rest of the product) but for verification codes and one-off handshakes, the model fits the job.
Same address, two readers: the QR bridge
The /qr command sends a QR code of the current address, scan it on another device and the address is there without typing a single character. The more interesting bridge is the reverse: an address you created in the browser can be opened on mobile by using its name, and the bot's /inbox refresh reads any inbox the bot session holds. The web reader and the bot reader are two windows onto one mailbox, each with its strengths: the browser renders full HTML with per-message image control; the bot pushes arrival the second it happens.
That split covers the two moments verification mail matters: "I am at a desktop, mid-signup" (browser tab, copy-paste) and "I am on my phone, the code landed" (push notification, already in my pocket). The address does not care which reader you use, pick per moment, not per inbox.
What still lives on the website only
The bot covers the high-frequency loop (create, receive, read, refresh) and the website covers the rest deliberately: attachments you want to handle carefully render with per-message image controls in the browser reader; the account features (named inboxes, SMTP credentials, API and MCP connections) live on the site because they are configuration, not messaging; and the inspection tools (MIME decoder, header analyzer) are web pages by nature. Knowing the split saves the "why can't the bot do X" moment: the bot is the fast lane for codes and confirmations, the site is the workshop.
Deep links keep the two close: from the bot you can jump to the web inbox for the same address when a message deserves the full reader. The rule of thumb is sensory, not technical, codes and links by push, anything you want to look at in the browser.
Your next code, delivered to your chat
One tap to an inbox that pings you when the mail arrives.
Open @TempxEmailBot Use the web inbox