- Can I receive verification codes and confirmation links?
- Yes. Receiving low-risk one-time codes and sign-up confirmations is what TmpKit is built for. Delivery time depends on the sender, DNS, SMTP queues, and inbox polling, so no fixed arrival time is guaranteed. If a code is delayed, check the sender's status and resend controls before the sender's own expiry window closes.
- How long does my address and inbox last?
- Each address is short-lived by design and expires after the countdown shown in the app. When it expires, the session stops returning its messages and old records enter the cleanup process. If you need the address a little longer, use the one-time extension when offered and grab the code before the window closes.
- Can I reply to emails or send messages from a temp address?
- No. tmpkit is a receive-only service, so you can read incoming mail but not compose, reply to, or forward anything from the temporary address. If a workflow requires you to send email, you will need a real mailbox you control.
- Are attachments supported?
- Yes, you can usually open and download attachments that arrive with a message, such as PDFs or images. Very large files may be rejected by mail-size limits, and like everything else in the inbox, attachments disappear when the address expires. Download anything you want to keep before that happens.
- Is it really anonymous, and what data do you keep?
- No account, name, or password is required for an inbox, but the service and its infrastructure still process the temporary address, message, session ID, IP, request, and security data needed to operate. Messages stop being available at session expiry and old records enter cleanup; limited technical logs may be retained for security, reliability, debugging, or legal duties. This reduces the data footprint but is not guaranteed anonymity.