Editing Ancestry.com (section)

==Incidents==

===Data Breach (2015)===
RootsWeb, an Ancestry service, suffered a significant data breach: a file containing the access data of 297.8 thousand users has been publicly accessible on their server from November 2015 to December 2017.<ref>{{Cite web |title=Ancestry |url=https://haveibeenpwned.com/breach/Ancestry |access-date=9 Aug 2025 |website=haveibeenpwned.com}}</ref><ref>{{Cite web |date=22 Feb 2024 |title=What happened in the Ancestry data breach? |url=https://www.twingate.com/blog/tips/ancestry-data-breach |access-date=9 Aug 2025 |website=Twingate}}</ref><ref>{{Cite web |last=Spring |first=Tom |date=27 Dec 2017 |title=Leaky RootsWeb Server Exposes Some Ancestry.com User Data |url=https://threatpost.com/leaky-rootsweb-server-exposes-some-ancestry-com-user-data/129248/ |access-date=9 Aug 2025 |website=threatpost}}</ref> The company published a security update on the official website, now unavailable, stating that they temporarely shut down RootsWeb and locked all the compromised Ancestry accounts, requiring users to change their passwords.<ref>{{Cite web |last=Blackham |first=Tony |date=23 Dec 2017 |title=RootsWeb Security Update |url=https://blogs.ancestry.com/ancestry/2017/12/23/rootsweb-security-update/ |archive-url=https://web.archive.org/web/20171227232406/https://blogs.ancestry.com/ancestry/2017/12/23/rootsweb-security-update/ |archive-date=27 Dec 2017 |access-date=9 Aug 2025 |website=[[Ancestry]]}}</ref> Below is part of the full statement:<blockquote>We want to share an important security update with you.

Last Wednesday, December 20, Ancestry’s Information Security Team received a message from a security researcher indicating that he had found a file containing email addresses/username and password combinations as well as user names from a RootsWeb.com server. Our Information Security Team reviewed the details of this file, and confirmed that it contains information related to users of Rootsweb’s surname list information, a service we retired earlier this year. For those of you who are unfamiliar, RootsWeb is a free community-driven collection of tools that are used by some people to host and share genealogical information. Ancestry has been hosting dedicated RootsWeb servers as a favor to the community since 2000. Importantly, RootsWeb does not host sensitive information like credit card numbers or social security numbers, and is not supported by the same infrastructure as Ancestry’s other brands. We are in the process of informing all impacted customers and will also be working with regulators and law enforcement as appropriate.

We also reviewed the RootsWeb file to see if any of the account information overlapped with existing accounts on Ancestry sites. We did confirm that a very small number of accounts – less than one percent of our total customer group – used the same account credentials on both Rootsweb and an Ancestry commercial site. We are currently contacting these customers.

In all cases, any user whose account had its associated email/username and password included on the file has had their accounts locked and will need to create a new password the next time they visit.

'''What We’ve Done'''

As a result of this discovery, we have taken two immediate corrective actions.

First, for the approximately 55,000 customers who used the same credentials at RootsWeb’s surname list and Ancestry – whether currently active or not – we have locked their Ancestry accounts and will require that they create a new password the next time they visit. We have also sent them emails to alert them to the situation. Though we have seen no activity that indicates these accounts have been compromised, we believe taking this additional measure is the right step to ensure the security of these customers. If you have not received an email or a notice requiring you to change your password, you have not been affected. Again, this issue involves less than one percent of our users, so there is a very good chance your account wasn’t involved.

Second, we have temporarily taken RootsWeb offline, and are working to ensure that all data is saved and preserved to the best of our ability. As RootsWeb is a free and open community that has been largely built by its users, we may not be able to salvage everything as we work to resolve this issue and enhance the RootsWeb infrastructure.

'''What You Should Do'''

If you are a customer whose account was impacted, you will receive an email telling you that you need to change your password. In that case, you will be required to create a new password the next time you visit Ancestry.

For the vast majority of customers who are not impacted by this, there is nothing you need to do as a result of this incident. However, we always recommend that you take the time to evaluate your own security settings. Please, never use the same username and password for multiple services or sites. And it’s generally good practice to use longer passwords and to change them regularly.</blockquote>