Why Account Recovery Is the Weak Spot in Your Security
You can use a 20 character password, a passkey and an authenticator app, and still lose an account in four minutes.

You can use a 20 character password, a passkey and an authenticator app, and still lose an account in four minutes. All it takes is a recovery email you have not opened since 2019, sitting there as a permanent side door that your careful password never guards.
Account recovery is the part of security almost nobody audits. I checked mine last spring expecting it to be tidy, and found a dead university address listed as the backup for my main Google account, plus a phone number I gave up when I changed carriers. This piece covers how that gap gets used, how to audit every recovery path you own in about forty minutes, and the one piece of standard advice I think is wrong.
Why the recovery path is the cheapest way in
Nobody attacking a normal person's account sits there guessing passwords. Guessing is slow and most services lock you out after a handful of tries. The recovery flow is faster because it is designed to help a confused, locked-out customer, and that design goal pulls against security by nature.
Three things make it work in an attacker's favour. The first is abandoned mailboxes. Free providers reclaim addresses after long inactivity, and plenty of small company domains lapse and get bought. If your backup address lives on a domain someone else now owns, they receive your reset links.
The second is your phone number. A SIM swap, where someone talks or bribes a carrier rep into moving your number to their SIM, takes a motivated person maybe an hour. Numbers also get recycled: in the United States, a disconnected mobile number can be reissued to a new customer after roughly 45 days to a year depending on the carrier. The new owner is not hunting you, but they can receive your codes by accident, and some of them look at what arrives.
The third is the human on the support desk. Recovery questions about your mother's maiden name or your first school were designed in an era before anyone posted their biography online. Half the answers sit in public records or an old social media bio.
Audit every recovery path in one sitting
Do this once, properly, and it stays done for a year or two. Start with your email account, because every other reset passes through it. Then do your bank, then anything that holds money or identity documents.
- List the accounts that matter. Mine came to nine: two email accounts, a bank, a payment app, the phone platform account, a cloud storage account, a domain registrar, a tax portal and the password manager. Nine, not ninety. Recovery hygiene on a forum login is not worth an evening.
- Open the security page of your main email first. On a Google account that is myaccount.google.com, Security. On Microsoft it sits under Security, Advanced security options. Read the recovery email and recovery phone fields out loud. If either one surprises you, that is the finding.
- Replace dead addresses with a live one you control. Point recovery at an address on a provider you expect to keep, and sign in to it at least twice a year so it never goes dormant. A second address at the same provider as the primary is weaker than one somewhere else, since one provider lockout takes both.
- Remove phone numbers you no longer hold. Then check whether you can remove the number entirely. Several services now let you keep a number for alerts without allowing it to authorise a password reset. That setting is worth hunting for.
- Generate backup codes and store them somewhere physical. Most services give you eight or ten single use codes. Print them or write them out and put them with your passport, not in a note on the phone that is itself the second factor.
- Check active sessions and app passwords while you are there. Old app specific passwords for a mail client you stopped using in 2021 are live credentials that skip two factor checks entirely.
- Add a trusted contact or recovery key where it exists. Apple's account recovery contact and legacy contact both take two minutes and mean a locked account can be opened with help from someone you actually know.
Keep a note of the date you did this. Mine lives in my password manager as a reminder set for every January. If you do not have one yet, the comparison in how to choose a password manager you will keep using covers which ones store notes and recovery codes properly.
The counter-take: lie on your security questions
The usual advice says to answer security questions honestly and keep them consistent so you do not get confused. I think that is backwards for anyone who has ever had a public social media account.
The honest answer to "what city were you born in" has maybe a few hundred realistic options and is often on your profile. Treat these questions as what they are: a second password with a prompt attached. Generate a random phrase for each one, store it in the password manager alongside the login, and never try to remember it. My answer to a first pet question on one bank is a 14 character string that has never been a pet.
The one caution worth stating plainly: some banks and government portals verify answers by phone with a human reading them out. Random hex strings get awkward there. For those accounts I use three random dictionary words instead, which are easy to read down a line and still useless to someone researching me.
If this feels like extra work for little gain, bear in mind that security questions are the most common route around a strong second factor. The patterns in why two-factor authentication often fails for regular users show how often the recovery flow quietly undoes the protection people just finished setting up.
What to do when you are already locked out
Recovery works differently once you are the one locked out, and the main lesson is that speed is not your friend here. Submitting four recovery requests from four devices in one hour makes you look more like an attacker, and some automated systems then slow your case down.
Use the device and the network you normally use. Providers weigh familiar signals heavily: a known browser, a known home IP address, a location that matches your usual pattern. This is one of the few situations where a VPN actively hurts you. Turn it off for the recovery attempt, then switch it back on afterwards.
Fill in the recovery form with the information you are certain about and leave the rest blank rather than guessing. Approximate dates are fine. Old passwords you genuinely used help a lot, which is a quiet argument for keeping password history in your manager rather than overwriting it.
Then wait. Google's form often responds within minutes but can take several days. Expect a queue, and expect the first answer to be no if your details were thin.
Recovery for accounts you share
Shared accounts break every tidy plan. A household streaming login, a joint bank app, a business account with one owner who left the company. In each case the recovery path belongs to one person, and the other people find out at the worst moment.
The fix is boring and it works: write down who holds the recovery for each shared login, and give at least one other person a sealed copy of the backup codes. For small businesses, point account recovery at a role address like billing@ rather than a named person's mailbox, so the account does not leave with the employee. I have watched a small studio lose control of its own domain for eleven weeks because the registrar account recovered to a developer who had moved on and stopped answering.
Frequently asked questions
Is SMS recovery really that risky for an ordinary person?
For most people it is acceptable but not ideal. SIM swap attacks are usually aimed at accounts with obvious value, such as crypto holdings or a public username. The more common problem is dull: you change number, forget to update the account, and the code goes to a stranger. Keep the number current and add an authenticator app or passkey as the stronger option.
Should I use the same recovery email for everything?
One well protected recovery address is easier to maintain than five scattered ones, so yes for most people, with one exception. Do not let that address be the recovery for itself or for your password manager. Those two need a separate path, usually backup codes on paper.
How often should I check my recovery settings?
Once a year for the accounts that matter, plus any time you change phone number, job or email provider. Those three events cause nearly every broken recovery path I see. More guides on locking down everyday accounts sit in the security section.
More in Security
Security
How to Check Which Devices Are Signed Into Your Accounts
I checked my own Google account in February expecting a tidy list of four devices. It showed nine.
Security
Why Browser Extensions Are a Quiet Security Risk
A friend asked me to look at her laptop because search results had started redirecting to a site she had never heard of.
Security
How to Check If Your Email Was in a Data Breach
You got an email saying a company you barely remember "experienced a security incident," and now you are wondering if your...