One of my old email addresses was involved in the recent Whitepages breach disclosure.

I don't remember on which websites I used that email address for registration, but I would like to reset my password everywhere possible. Websites could include: Facebook, Google, Amazon, eBay, Paypal, etc.—basically the top N commonly-used or sensitive web applications/platforms.

This is particularly important as I was not using a password manager at the time and may have reused passwords.

Is there an existing way to automate initiating password resets, mainly by requesting password reset emails on common platforms, given a single email address that I have access to?

  • 10
    I don't see how that could work so easily as all that. You have way, way more passwords than you think. I thought I had "maybe 20" until I made a spreadsheet and came to discover I had 130. And I'm not a "signer-up" and actively try to keep that number down. Further to that, I don't agree with your idea of "top sites", you forgot Amazon, eBay and Paypal, see how it is? There are so many sites. Commented Mar 27, 2019 at 20:21
  • 1
    @Harper Indeed, the number of registered sites is likely to be much bigger than anticipated. Even if not on all, my concern is how to automate password resets on at least the top N popular or critical websites. And yes, Amazon and eBay would/should be included in those - I don't claim to have that list ready or that it contains only the 5 entries I mentioned in the question (hence the "etc.")
    – Islay
    Commented Mar 27, 2019 at 20:33
  • 2
    Related: API to change passwords?, and cross-site duplicate: What's an efficient way to change my 200+ account passwords? Commented Mar 29, 2019 at 0:15
  • Automating them would only be worthwhile if you changed them regularly. You would get more security for less effort by changing them once and (continuing) using a password manager. Commented Mar 30, 2019 at 3:42
  • 1
    I would think having an tool to automate the process would be a horrible risk. Now the hacker will be highly motivated to hack to the tool rather than the sites.
    – MaxW
    Commented Mar 30, 2019 at 5:36

6 Answers 6


No, not really - they all have different processes for verifying your identity for password reset requests, and there isn't any standard for bulk password resets. For example, Apple may use a device which is registered to the account as a confirmation that it's you sending the request, while Facebook uses different schemes depending on whether you're changing your password from a device where you've previously logged in, or from a completely unrelated one.

Easiest way is probably to go through common websites (e.g. work through a list like https://en.wikipedia.org/wiki/List_of_most_popular_websites, ignoring any which you are sure don't apply) providing the email address you want to reset, and watching for reset emails. It's not perfect, but if you're changing the ones you know are sensitive (e.g. ones which have credit card details associated, or email accounts, or government systems), that's ok - you know that those accounts will have unique passwords, even if an attacker may be able to log into your abandoned MySpace (or other defunct social network) account with an old password.

  • 8
    I'd add to this that while you're in the process of doing this, I would invest a bit more time into adding these sites to a password manager (e.g. LastPass, 1Password, KeePass, Bitwarden, ...). This allows you to keep track of the accounts you have, allows you to use unique passwords for each site (which will prevent a password leaked on site A being used to login on site B) and some even monitor your account's appearance in the HIBP database).
    – BlueCacti
    Commented Mar 28, 2019 at 10:53
  • @BlueCacti: Definitely. That's my current setup since the past few years already.
    – Islay
    Commented Mar 28, 2019 at 21:01
  • And this is one more reason why using a password manager is good practice. You "change" the password on those sites by letting the manager give them a unique password in the first place. Then, the breach comes (and it will come; it comes for all of us eventually) and most of the work is already done. You only need to change the failed site, because the others already used a unique password. Even better, close the account at the site that failed if you can. Commented Mar 29, 2019 at 13:53

This is a known problem without an existing solution. Some password management tools are working on it, but it is not complete or fool-proof.

For example: https://helpdesk.lastpass.com/generating-a-password/

Auto-Password Change will change a site’s password with a single-click. This feature currently supports 75 of the most popular websites. You can see the full list of supported websites below.

In general, though, when you use a password manager for all your accounts, 90% of the work you need to do is already done. You know which sites use that username/email, and you can avoid re-using passwords in the first place (or know which accounts use a shared password).

  • 3
    @emory I'm not sure that is true. An authenticated process would not expose a DoS threat to the process.
    – schroeder
    Commented Mar 27, 2019 at 14:00
  • 2
    As I understand it, OP wants to send a message to a bunch of sites - facebook, google, spotify, netflex, etc - saying "hey, I am pretty sure I have an account with you guys and my username is [email protected]. This account has been compromised. Please lock me out." Why couldn't I do the same with all the email addresses that I know @schroeder to use?
    – emory
    Commented Mar 27, 2019 at 14:10
  • 7
    @emory .... because that would be silly. And no one is talking about that. And that has nothing to do with anything I said or what the OP said.
    – schroeder
    Commented Mar 27, 2019 at 14:14
  • 2
    @emory I still have access to the old email account, so schroeder's idea of an authenticated process to trigger the requests seems to mitigate the issue IMO.
    – Islay
    Commented Mar 27, 2019 at 20:08
  • 1
    I wonder if anyone attempted to use AI to solve this problem: teach a program how reset processes look like, where to find them looking at a webpage and how to submit the username/email to reset. If we are lucky this might work for a majority of websites and not an hardcoded list of less than 100.
    – Bakuriu
    Commented Mar 28, 2019 at 18:29

One tip to help you out on your journey is that multiple sites have implemented the well-known password change URL, provisionally a part of the IANA well-known-uri list. This is something you can plug in to any (supporting) website. It redirects to the page that lets you change your password.

Take the homepage of the site and add /.well-known/change-password to the end. Clickable examples:

Base URL + well-known Redirect Destination
accounts.google.com https://myaccount.google.com/signinoptions/password
github.com https://github.com/settings/security
twitter.com https://twitter.com/settings/password
meta.discourse.org https://meta.discourse.org/my/preferences/account
  • Apple first implemented it in Safari, and LastPass picked it up next. There's a draft but it isn't published as an RFC yet.
    – Riking
    Commented Mar 31, 2019 at 5:47

One alternative solution to identify sites that you used your email address on is to look into your browser's saved passwords.

This will allow you to see every site you have saved passwords for in your browser which might help you identify ones that need to be changed.

Obviously, this only works if you use the browser's "save password" feature.

  • 2
    So, in other words, look in your password manager. And sometimes, your password manager is your browser.
    – schroeder
    Commented Mar 27, 2019 at 13:57
  • 6
    True, although I think most people would not consider their browser a true "password manager". This is just another suggestion that could be easy to overlook for others who are trying to find websites they forgot they registered on
    – Jacob
    Commented Mar 27, 2019 at 14:18
  • 1
    I would say "almost allways, your browser is your password manager."
    – ThoriumBR
    Commented Mar 27, 2019 at 14:18

It's a hard problem because the top list of websites is so personal... And what you have to lose is in no way proportional to the site's popularity on any index of popular sites.

And only you know where you might have accounts.

For instance, I consider gaming sites to be more critical than banking sites. Because there are much fewer controls and less legal peril involved in hacking MMO gaming accounts, so they are the darlings of crackers. On the other hand, if you're done with Maplestory, you may not care.

But you certainly don't need to care about your Eve Online account if you definitely never played it. Only you know this sort of thing.

If you think you might have used a site in the past, why not just try your old credential?

Why not just spam every website with password reset requests?

They're not going to cooperate with large scale automated requests of this type.

First, the website acknowledging whether an email has an account, would empower spear phishing. Scammer gets a billion emails (easy enough), they start banging the website's password reset to learn "does this email have an account here, or not?" Now they have a list of 1 million emails that do. Now they start spear-phishing those known account holders. Put them on a daily newsletter where unsubscribe requires a login, that kind of thing. This is a "many email addresses against a single site" attack. The site's best defense is to add friction to the password reset process, e.g. a CAPTCHA, or simply design the password-reset process so it tells the inquirer nothing about whether an account exists. This is even more important for sites like Ashley Madison or Furries where having an account there could be embarrassing.

Second, if a cracker managed to gain control of an email, they could simply do exactly what you're trying to do - ascertain which websites this email has an account on. With a full dossier, they can then attack those sites or simply sell the credentials for more than they could otherwise. This is a "single email vs many sites" attack. In this case, the site needs to control one-off access to the password reset function - something like a CAPTCHA is called for. And 2-factor authentication - but again, this 2FA must not disclose to the casual inquirer whether an account here exists.

Because of this, I don't see a probability of anyone writing an app to do this. The writer would find herself in a hacking "arms race" with many companies trying to stop her automation from working.

  • Lol...You made me google Furries and Ashley Madison...
    – Aganju
    Commented Mar 27, 2019 at 22:28
  • The spear phishing/email enumeration isn't an issue if the mass password reset process itself requires email verification. However, good point re if a cracker managed to gain control of an email.... But then, in the case of a determined attacker, whether the manual nature of the process is enough of a deterrent - compared to the convenience afforded by its automation to genuine users - is debatable.
    – Islay
    Commented Mar 28, 2019 at 21:09

You can absolutely reset passwords automatically if your password manager supports it (I use LastPass) -- even retroactively. You don't have to have created the site using LastPass in order for it to be able to reset your passwords for you. You simply have to load the credentials into it and ask it to perform the password reset function.

In LastPass, simply allow LastPass to remember your credentials for the site (typically by logging in), and then on the Edit Site window of your vault, simply select Auto Change Password below the password field.

  • One may not have the old password(s) anymore to load into LastPass.
    – Islay
    Commented Mar 27, 2019 at 20:11
  • Lastpasses feature also only works on some of the biggest sites, and even then not reliably. (facebook, battle.net....) Commented Mar 27, 2019 at 22:51
  • This is all covered in another answer (along with the weaknesses)
    – schroeder
    Commented Mar 28, 2019 at 9:27
  • 1
    Do not use proprietary, nonfree, closed-source password managers. Commented Mar 30, 2019 at 3:46

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .