Destination verification confirms that an AliasFleet account holder controls the inbox that will receive forwarded mail. This page covers the verification email, entry of the 6-digit code or use of the verification link, and confirmation that the destination shows as verified and forwarding can start.
An AliasFleet account and access to the destination inbox are required. The destination must already exist in the account; adding one is covered in Adding a destination. An unverified destination cannot receive forwarded mail, so verification takes place before any alias mapped to that destination is used.
Why verification exists#
Without verification, an account holder could direct aliases to an inbox belonging to another person, and mail intended for the account holder would arrive in that inbox. The check applies once per destination. Once it passes, aliases mapped to that destination forward normally, and no fresh check is required for each additional alias.
How verification works#
Adding a destination sends a verification email to that address. The email contains two methods for completing the same check: a 6-digit code for entry on the verification screen, and a verification link that completes the check without code entry. Both methods confirm the same fact, control of the inbox, and only one method is needed.
The code expires after 15 minutes. A code entered after expiry does not complete verification, and a fresh code must be requested instead.
How do I verify a destination?#
- Add the destination. Adding a destination sends the verification email to that address automatically. The steps for the form itself are in Adding a destination.
- Open the verification email. Open the destination inbox and locate the message from AliasFleet. If the message is not in the inbox within a couple of minutes, check the spam or junk folder first.
- Complete the check by one method. Enter the 6-digit code from the email on the verification screen, or click the verification link in the email. Both methods produce the same verified state.
- Confirm the verified state. After a successful check, the destination shows as verified on the Destinations page. Forwarding to that destination is then active for aliases mapped to it.
If the code has expired before entry, use Resend email to request a fresh code. A 30-second cooldown applies between resend requests, so a second request immediately after the first is refused until the cooldown passes.
Confirming verification worked#
How do I confirm a destination is verified?#
The verified state on the Destinations page is the confirmation. A further check is to send a message to an alias mapped to that destination and confirm arrival in the destination inbox. Arrival through the alias proves the full chain, alias, forwarding, and destination, works end to end. The setup guide How to Set Up an Email Alias describes where destination verification fits in first-time setup.
When the email does not arrive#
What if the verification email is missing?#
A missing verification email is generally a filtering issue rather than a failed check. Strict corporate filters in particular sometimes route system mail to spam or junk. Check the spam or junk folder first, then use Resend email for a fresh message. Adding the sending address to the contacts or safe senders list prevents the same filtering on future verifications.
Failure detail is kept brief here by design. Every failure mode, including expired codes, lockouts, and repeated delivery failures, is covered in Can't verify a destination, which owns troubleshooting for this check.
Re-verifying a destination#
How do I re-verify an existing destination?#
Verification can lapse in rare cases. Re-verification repeats the original process with a fresh code:
- Open the Destinations page. Find the destination in the list.
- Open the destination menu. Choose Reverify from the menu for that destination.
- Complete the fresh check. A new code is sent to the destination address. Enter the code on the verification screen or click the verification link, as in the first verification.
- Confirm the verified state. The destination shows as verified again, and forwarding resumes for aliases mapped to it.
Related guides#
- What is a destination?: how destinations, aliases, and forwarding fit together.
- Adding a destination: the form and steps that start verification.
- Can't verify a destination: every failure mode for this check, including lockouts and missing mail.