HomeDocsBlogSupport
OverviewWhat is AliasFleet?Creating an AliasEmails Not ArrivingContact Support

Getting Started

Getting Started
  • What is AliasFleet?
  • Your First Alias
  • Understanding Forwarding
  • Your Dashboard at a Glance
  • Using the Browser Extension

Account & Billing

Account & Billing
  • Your Plan and Usage Limits
  • Upgrading to Pro
  • Managing Your Subscription
  • Downloading Invoices
  • Support Ticket Limits
  • Membership Tier
  • Billing Cycle and Renewal
  • API Rate Limits by Plan

Billing Support

Account & Billing
  • Cancelling Your Subscription
  • Downgrading Your AliasFleet Plan
  • Understanding Proration and Plan Changes
  • Updating Your Payment Method
  • Handling Failed Payments and Account Suspension
  • AliasFleet Refund Policy

Email Aliases

Email Aliases
  • How to Set Up an Email Alias
  • Activating and Deactivating an Alias
  • How to Delete an Email Alias
  • Sorting, Filtering and Searching Aliases
  • Grid View vs List View
  • Grouping Aliases
  • Alias Categories
  • Copying an Alias Address
  • Per-Alias Email Banner Settings
  • Alias Permission Mode: Strict vs Open
  • Sending Outbound Emails (Quick Send)

Custom Domains

Custom Domains
  • Adding a Custom Domain
  • DNS Verification
  • Domain Status and Health Indicators
  • Subdomains
  • Removing a Domain
  • Using Your Domain on Aliases

Destinations

Destinations
  • What Is a Destination?
  • Adding a Destination
  • Verifying a Destination
  • Setting a Default Destination
  • Reply from Aliases
  • Send New Emails from Aliases
  • Understanding Email Threading & Replies
  • One-Click Enable from Bounce Email
  • Removing a Destination
  • PGP Encryption for Destinations
  • WKD Auto-Encryption for Replies & Sends

Security & Privacy

Security & Privacy
  • Security Best Practices
  • Two-Factor Authentication (2FA)
  • Active Sessions
  • Changing Your Password
  • What Data AliasFleet Stores
  • Reporting a Security Issue
  • Browser Extension Sessions
  • How to Use Vault Lock in the Extension

Rate Limiting

Security & Privacy
  • Rate Limiting and Account Protection

Settings

Settings
  • General Settings
  • Profile Settings
  • Alias Settings
  • Destinations in Settings
  • Notification Settings
  • Security Settings
  • Deleting Your Account

Analytics

Analytics
  • Analytics Overview
  • Alias Performance
  • Top Senders
  • Trends
  • Bounces
  • Bandwidth Usage
  • Category Breakdown
  • Exporting Analytics Data
  • Understanding Alias Statistics
  • How Monthly Trends Work

Sender Rules

Sender Rules
  • Using Sender Rules
  • Blacklist vs Deactivating an Alias
  • Using Allowlist Rules to Allow Senders
  • Blocked Emails Explained

Troubleshooting

Troubleshooting
  • Emails Not Arriving
  • Can't Verify a Destination
  • DNS Not Verifying
  • Can't Log In
  • Replies Not Going Through Alias
  • Alias Not Forwarding
  • Payment Failed
  • Browser Extension Issues
  • Too Many Requests Error
  • Page Not Loading or Showing an Error

Developers

Developer API
  • Identity & Token Introspection API
  • Aliases API
  • Alias Destinations & Batch Operations API
  • Domains API
  • Destinations API
  • Quick-Send API
  • Sender Rules API
  • Activity & Audit Logs API
  • Fleet Analytics API
  • Rules API
  • Security & Threat Intelligence API
  • Webhooks API
  • Categories & Tags API
  • User Profile & Account API
PrivacyTermsCookies
Article Navigation
OverviewWhat is AliasFleet?Creating an AliasEmails Not ArrivingContact Support

Getting Started

Getting Started
  • What is AliasFleet?
  • Your First Alias
  • Understanding Forwarding
  • Your Dashboard at a Glance
  • Using the Browser Extension

Account & Billing

Account & Billing
  • Your Plan and Usage Limits
  • Upgrading to Pro
  • Managing Your Subscription
  • Downloading Invoices
  • Support Ticket Limits
  • Membership Tier
  • Billing Cycle and Renewal
  • API Rate Limits by Plan

Billing Support

Account & Billing
  • Cancelling Your Subscription
  • Downgrading Your AliasFleet Plan
  • Understanding Proration and Plan Changes
  • Updating Your Payment Method
  • Handling Failed Payments and Account Suspension
  • AliasFleet Refund Policy

Email Aliases

Email Aliases
  • How to Set Up an Email Alias
  • Activating and Deactivating an Alias
  • How to Delete an Email Alias
  • Sorting, Filtering and Searching Aliases
  • Grid View vs List View
  • Grouping Aliases
  • Alias Categories
  • Copying an Alias Address
  • Per-Alias Email Banner Settings
  • Alias Permission Mode: Strict vs Open
  • Sending Outbound Emails (Quick Send)

Custom Domains

Custom Domains
  • Adding a Custom Domain
  • DNS Verification
  • Domain Status and Health Indicators
  • Subdomains
  • Removing a Domain
  • Using Your Domain on Aliases

Destinations

Destinations
  • What Is a Destination?
  • Adding a Destination
  • Verifying a Destination
  • Setting a Default Destination
  • Reply from Aliases
  • Send New Emails from Aliases
  • Understanding Email Threading & Replies
  • One-Click Enable from Bounce Email
  • Removing a Destination
  • PGP Encryption for Destinations
  • WKD Auto-Encryption for Replies & Sends

Security & Privacy

Security & Privacy
  • Security Best Practices
  • Two-Factor Authentication (2FA)
  • Active Sessions
  • Changing Your Password
  • What Data AliasFleet Stores
  • Reporting a Security Issue
  • Browser Extension Sessions
  • How to Use Vault Lock in the Extension

Rate Limiting

Security & Privacy
  • Rate Limiting and Account Protection

Settings

Settings
  • General Settings
  • Profile Settings
  • Alias Settings
  • Destinations in Settings
  • Notification Settings
  • Security Settings
  • Deleting Your Account

Analytics

Analytics
  • Analytics Overview
  • Alias Performance
  • Top Senders
  • Trends
  • Bounces
  • Bandwidth Usage
  • Category Breakdown
  • Exporting Analytics Data
  • Understanding Alias Statistics
  • How Monthly Trends Work

Sender Rules

Sender Rules
  • Using Sender Rules
  • Blacklist vs Deactivating an Alias
  • Using Allowlist Rules to Allow Senders
  • Blocked Emails Explained

Troubleshooting

Troubleshooting
  • Emails Not Arriving
  • Can't Verify a Destination
  • DNS Not Verifying
  • Can't Log In
  • Replies Not Going Through Alias
  • Alias Not Forwarding
  • Payment Failed
  • Browser Extension Issues
  • Too Many Requests Error
  • Page Not Loading or Showing an Error

Developers

Developer API
  • Identity & Token Introspection API
  • Aliases API
  • Alias Destinations & Batch Operations API
  • Domains API
  • Destinations API
  • Quick-Send API
  • Sender Rules API
  • Activity & Audit Logs API
  • Fleet Analytics API
  • Rules API
  • Security & Threat Intelligence API
  • Webhooks API
  • Categories & Tags API
  • User Profile & Account API
PrivacyTermsCookies
Security & Privacy
Docs
Security & Privacy
Two-Factor Authentication (2FA)

Two-Factor Authentication (2FA)

How to set up two-factor authentication on an AliasFleet account with an authenticator app, store recovery codes, and disable 2FA.

4 min read
Updated October 30, 2026
What is two-factor authentication?How is 2FA set up with an authenticator app?What if email codes are preferred instead?How is sign-in completed with 2FA turned on?How is 2FA disabled?How is access recovered after a lockout?Related guides

This page covers two-factor authentication (2FA) for an AliasFleet account: setup with an authenticator app, sign-in with a code, storage of recovery codes, and removal of 2FA. Two-factor authentication adds a second sign-in step, so a password on its own does not open the account.

What is two-factor authentication?#

Sign-in under two-factor authentication requires two separate items: the account password and a code that changes with time. The password is entered first, and a 6-digit code is then requested. That code is produced by an authenticator app on a phone, or, where the email method is selected, sent as a one-time passcode to the account email. The authenticator app is the more secure method, because it does not rely on the security of an inbox. A password that is exposed does not by itself open the account, because the second item is still required.

Before starting

An authenticator app must be installed on a phone before setup starts. The recovery codes shown at the end of setup must also be saved before that screen is left, because they provide the backup route back into the account if the authenticator app is lost.

How is 2FA set up with an authenticator app?#

Setup has five steps, completed in Settings, and ends with recovery codes that must be saved before the setup screen is closed.

  1. Open Security settings. Go to Settings → Security and select Enable 2FA.
  2. Choose the authenticator app method. Select Authenticator App and then select Continue.
  3. Scan the QR code. Scan the QR code shown on screen with the authenticator app. The app then generates a 6-digit code that changes every 30 seconds.
  4. Confirm the code. Enter the current 6-digit code from the app to confirm that setup works.
  5. Save the recovery codes. Save the set of one-time recovery codes shown, in a password manager or printed and kept in a secure physical location, before leaving the screen.

Recovery codes can be replaced at any time from Settings → Security if the existing set is believed to be compromised. Regeneration replaces the old set in full.

What if email codes are preferred instead?#

At setup, email one-time passcode is offered as an alternative. Under that method, a code is sent to the account email at every sign-in. Sign-in then depends on access to that inbox, which makes the method less convenient and less secure than an authenticator app. The authenticator app method is therefore the recommended choice where a phone app is available.

How is sign-in completed with 2FA turned on?#

Sign-in with 2FA follows the same two steps every time: the account password is entered, and then the current code is entered.

  1. Enter the password. Sign in with the account email address and password as usual.
  2. Enter the 2FA code. Open the authenticator app and enter the current 6-digit code. If the authenticator app is unavailable, enter one of the saved recovery codes instead. Each recovery code works once.

If a code is rejected, the phone clock should be set automatically, because time-based codes depend on an accurate clock. Trying the code at the start of its 30-second window also helps. Full lockout steps are covered in Can't Log In.

How is 2FA disabled?#

Disabling 2FA removes the second sign-in step and invalidates all existing recovery codes. After disabling, sign-in requires only the password.

  1. Open Security settings. Go to Settings → Security and select Disable 2FA.
  2. Confirm with a code. Enter a current 2FA code to confirm the change.

New recovery codes are issued if 2FA is enabled again later.

How is access recovered after a lockout?#

Recovery depends on what is still available. If recovery codes were saved, one recovery code signs in, and 2FA can then be disabled and set up again on the new device. If the authenticator app and the recovery codes are both lost, the remaining route is support: contact support and be prepared to verify identity as the account owner. The detailed lockout steps, including clock-sync fixes for rejected codes, are in Can't Log In.

Related guides#

  • Can't Log In: fixes for failing 2FA codes, lost authenticators, and lost recovery codes.
  • Security Best Practices: the wider account security setup, including 2FA alongside password and alias habits.
  • How to Secure Your Email Account: why two-factor authentication comes before other account security steps.

Frequently Asked Questions

Yes. Any TOTP-compatible app works, including Google Authenticator, Authy, 1Password, Bitwarden, and Microsoft Authenticator.

Use one of the recovery codes saved during setup to log in. Once logged in, disable the old 2FA setup and set it up again with the new device.

Store recovery codes in a password manager, or printed and kept in a secure physical location. Recovery codes are one-time use, so each code works once.

Yes. Disabling 2FA invalidates all existing recovery codes. New recovery codes are issued if 2FA is enabled again later.

Was this article helpful?

PreviousSecurity Best PracticesNextActive Sessions

Related in Security & Privacy

Security Best Practices

Email alias security tips: one alias per service, a strong unique password, two-factor authentication, and active session checks.

Active Sessions

Review every device signed in to AliasFleet, revoke sessions you do not recognise, and secure the account after an unfamiliar login.

Changing Your Password

Change an AliasFleet password from Settings, or reset a forgotten password from the sign-in page, and check that the new password works.

What Data AliasFleet Stores

The complete list of data AliasFleet stores on your account, what it never keeps, and how to export or delete your data.

Reporting a Security Issue

How to report a security vulnerability in AliasFleet, what to include in the report, and what happens after the report is sent.

On this page

What is two-factor authentication?How is 2FA set up with an authenticator app?What if email codes are preferred instead?How is sign-in completed with 2FA turned on?How is 2FA disabled?How is access recovered after a lockout?Related guides

Still need help?

Cannot find the answer you are looking for? Our support team is ready to assist.

Contact Support