Email terms,
explained clearly

The identifier a sender uses to address a message, usually made up of a username, @ and a domain. An address is not an inbox, and knowing it alone does not prove you can access the mail.

Example:nestpilot42@fwdnest.com , nestpilot42 is the local part, and fwdnest.com is the domain. All addresses on this page are examples, not inbox addresses assigned to you.

A temporary email address you can use for a limited time, such as for one-time verification or software testing. FwdNest temporary email requires no signup; read messages on the homepage. It does not automatically forward them to your real inbox.

How to use it: Copy the address actually generated in the homepage inbox and paste it into the signup form. Use an email address you can access long-term for payments, assets or account recovery.

A one-time code sent by a website to confirm you can receive email. It may contain digits or a mix of letters and numbers. The sender decides how long it works, what it can be used for and whether disposable email is accepted.

Don't mix them up: Enter the code on the website that requested verification. Requesting a new code may invalidate the old one. If an email hasn't arrived, check email delivery troubleshooting before requesting more codes in quick succession.

The sender name and address shown in an email's headers. Display names can be spoofed; labels like “Support” or “Security” don't prove an email is official.

How to check: Check the full sender address and the email's context. If you receive an unexpected sign-in alert, open the official app yourself to verify it. Don't click email links based only on the display name.

The line in your inbox that summarizes an email, such as “Confirm your signup.” Subjects aren't unique, and some emails have none, so don't rely on this line alone to identify an action.

How to check: Compare the sender, arrival time and instructions in the message. If multiple verification emails have the same subject, check which one matches your most recent request.

The content you see when you open an email. HTML messages can include formatting, images and buttons; plain-text messages consist mainly of text. An email may include both versions.

Reading tip: Missing images don't necessarily mean the email is incomplete. Look for the text code and instructions first; use caution with external images, attachments and links.

How long a temporary address can receive and provide access to email. New FwdNest temporary inboxes last 3 hours by default, and each successful extension adds another 3 hours. Check the countdown shown in the tool for the current expiry.

Time matters: An address having two hours left doesn't mean a verification code you just received will work for two hours. Codes can expire in minutes. See our expiry guide.

Email routing information published in a domain's DNS. It tells sending servers which receiving services should handle mail for that domain. An MX record typically points to a mail server hostname, not an individual inbox.

The limits: Having MX records doesn't mean every address exists or that a verification code will definitely arrive. Address status, sender policies, spam filtering and the forwarding destination can all affect delivery. The diagram below shows the delivery path and how its steps fit together.

Another address linked to your real inbox. When a FwdNest alias receives a message, it attempts to forward it to the email address you used to log in. You usually read it in your own inbox rather than logging in to the alias as a separate email account.

Example: Enter an alias like maplecove@fwdnest.com on a subscription website instead of your real email address. Create the alias in the dashboard first. This doesn't mean you can send or reply from it.

The email account you control long-term and where forwarded messages ultimately arrive. It's also where you receive FwdNest sign-in codes. Hiding your real address can reduce exposure, but doesn't guarantee anonymity.

Good practice: Set up reliable recovery options and two-step verification for your real email account. Make sure you can always access the destination mailbox for long-term accounts instead of relying on a temporary address that is about to expire.

The setting that controls whether an alias receives mail. When enabled, it accepts incoming messages and attempts to forward them. When disabled, new messages are discarded, not forwarded or delivered later.

The limits: Re-enabling an alias only affects future mail. It can't recover messages discarded while the alias was disabled. If you still use the alias for account recovery, update the email address on the website before disabling it.

A status indicating that the receiving service couldn't deliver a message to the forwarding destination. The destination may have rejected it, the service may be temporarily unavailable, or another delivery issue may have occurred. It doesn't necessarily mean the sending website never sent the email.

Troubleshooting steps: First check the logs and status in the dashboard, then check your real inbox's spam folder. If you contact support, provide the time and describe what happened. Don't include verification codes, access tokens or authenticator secrets.

A dashboard window for viewing records and contents of forwarded messages from the last 30 days. It's not a permanent backup or a list of temporary inbox messages. Save anything important yourself in good time.

Don't confuse the two:30 days is the archive window, not the alias lifetime. Long-term aliases don't expire with the three-hour countdown on the homepage temporary inbox. Disabling or deleting an alias and account status are separate matters.

A credential a service uses to identify access permissions. It's not an email address to enter in a form. A temporary inbox credential grants access to messages in that inbox; a sign-in credential grants access to an account and dashboard. Don't confuse the two.

How to protect it: Don't share browser storage, requests containing credentials or full screenshots of debug information. Clearing browser data may remove access to a temporary inbox; knowing its email address won't restore the credentials.

A six-digit code FwdNest sends to your sign-in email to confirm you control that inbox before accessing your email forwarding account. It's a different verification flow from signup codes sent to temporary inboxes by other websites.

How to protect it: Enter it only in a FwdNest sign-in flow you initiated. If you receive an unexpected code, don't forward it to anyone. Support staff will never need it.

A six-digit code generated by an authenticator app from a secret key and the current time. It changes periodically and serves as the second factor in two-step verification. It isn't sent by email, and requesting another email code won't give it to you.

How to get one: During setup, scan the QR code with Google Authenticator, Microsoft Authenticator or 1Password, then enter the six-digit code shown in the app in the setup flow on this page. When signing in to an account with two-step verification enabled, get the code from the same app.

A two-step verification setup QR code contains configuration for your authenticator app, including the secret key used to generate codes. The key is a long-term secret. Codes change, but if the key is exposed, someone else may be able to keep generating valid codes.

How to protect them: Don't paste a setup QR code screenshot, manual secret key or authenticator code into a support request. Store your setup securely using the backup options provided by your authenticator app. Don't keep it only in a public photo album or shared document.