Last updated: Oct 07, 2026
Who signed in with your email, two-factor authentication, your sessions and the export of the account data, in one screen.
Security is where you review and protect your own access to the console. It is in the account menu: Account → Security.
Almost everything on this screen is about you as a person, not about the account: your sign-ins, your devices, your sessions and your two-factor authentication. Every member manages their own, whatever their role. The one exception is the last block, the export of the account data, which needs a permission.
The screen is a column of blocks.
You need an authenticator app on your phone, such as Google Authenticator, 1Password or Authy.
The recovery codes are not shown again. The dialog does not close until you press I have saved them.
Nothing changes until step 4: if you close the dialog before confirming, two-factor authentication stays off.
Without your phone, press I do not have my phone: use a recovery code and enter one of your recovery codes. That code stops working after that sign-in, and you receive an email saying how many you have left.
Do it when you have few left, or if you think someone else has seen them.
The previous codes stop working at that moment, including the ones you had not used.
From then on you sign in with the email code only. Your recovery codes stop working, and you receive an email confirming the change. If you turn it on again later, you scan a new QR code and get new recovery codes.
A device you do not remove leaves the list on its own after 30 days.
Signing out on every device also removes all your trusted devices: the next sign-in on each of them will ask for the emailed code.
All your sessions end, including this one, and you are taken to the sign-in page. It only affects your sessions, not those of the other members.
The file contains:
Data is always included. If the reports together are too large, the ones that do not fit are left out and the manifest lists them.
The code from the app changes every 30 seconds. Check that it is the one showing right now, and that you are looking at the entry for this console in your app, then try again. If it keeps failing, check that the date and time of your phone are set automatically.
A code from the app is accepted only once. If you have just used it, for example to turn on two-factor authentication, wait for the app to show the next one. A recovery code also works only once.
When you sign in, you have 5 attempts for the second factor; the message tells you how many are left. After the fifth wrong one, the code sent by email is cancelled too. Ask for a new email code and start again.
At sign-in, press I do not have my phone: use a recovery code and enter one of your recovery codes. Once inside, you can turn two-factor authentication off with another recovery code, and turn it on again with your new phone.
Ask an Owner of your account to reset your two-factor authentication. They do it from Team, with the Reset 2-factor button in your entry of the member list. See Team. You receive an email saying who did it, and from then on you sign in with the email code only.
An Owner cannot reset their own. If you are the only Owner of the account, the console gives you no way to recover access by yourself: write to us from your account email.
The warning appears with 3 unused codes or fewer. Press Generate new codes to get 10 new ones before you run out. See Security.
If Recent sign-ins shows a successful sign-in that was not you, press Sign out everywhere to end every session, and turn on two-factor authentication if it is off. A failed attempt is one that did not get in.
The message shows a code in parentheses. Try again in a minute. If the block Two-factor authentication did not load, press Retry. If it keeps happening, send us that code with your account email.
Domain stabilization: DMARC, SSL, DNS, MX, blacklists and uptime — exact fixes and evidence of the work.
© 2026 Domain Stabilizer. All rights reserved.