Methodology
Nothing is listed here without a source record you can open yourself. This page says what that means, and what it rules out.
What a record is
An incident on this site is one breach event at one organization. It exists because at least one source record does: a regulator filing or an entry in the Have I Been Pwned catalog. Each incident, on its organization’s page, lists every source record behind it, with its date and a link.
When a new filing’s dates match an incident already on record, it is added to that incident as an update rather than listed as a new one. The matching follows fixed rules about dates and can be wrong; if it is, please tell us.
The three tiers
Every incident shows how firmly it is established.
- Official record
- A regulator filing or the organization's own disclosure exists. The strongest tier. The record is a filing with a regulator, such as a state attorney general or the SEC, or a statement the organization published itself.
- Cataloged
- Listed in the Have I Been Pwned catalog. No regulator filing found. The incident rests on an entry in the Have I Been Pwned catalog, and no regulator filing has been matched to it. Only entries that Have I Been Pwned marks as verified are used. That mark is not always a finding that the organization named was breached: an entry whose text says the data was scraped, or only alleged to come from the organization, is described that way on every page.
- Reported
- Named press reporting only. Awaiting an official record. Reserved for incidents known only from named press reporting. This tier is not in use yet: nothing on the site carries it today.
Rules every page follows
Wording follows the record
Summaries are assembled from the fields of the source records, not written freely. A filing is described as what it is: “reported a data breach to the California Attorney General”. The site does not say an organization “was hacked” on the strength of a filing alone, because the organization that files is sometimes a vendor or a customer of the firm whose systems were affected.
A company’s SEC filing is described as a Form 8-K under Item 1.05 (Material Cybersecurity Incidents) disclosing a cybersecurity incident, and an amendment to one as a Form 8-K/A. When an amendment adds Item 1.05 to a Form 8-K first filed under another item (Stryker filed under Item 8.01, Other Events), that first filing is on record too, named by its own item, because it is the company’s first disclosure of the incident. The item’s title is not a finding: many such filings say the incident has not had a material impact, and an organization on record only through such filings is not described as having a data breach. A data set that Have I Been Pwned describes as scraped from an organization’s service is called a scraped data set, not a breach, and “allegedly scraped” when the source only alleges it. When Have I Been Pwned says only that a data set is alleged to come from an organization, often on a threat actor’s claim, and nothing in its text affirms a breach, the data set is described with that hedge and not as the organization’s breach. A catalog entry is left out when its text shows the data did not come from the organization named, or when where it came from is unestablished and the organization denies it was taken from it.
A report its own record says was not a breach is left out
HHS keeps a breach report on its list after closing the case, and some closing summaries say no breach occurred: the Office for Civil Rights, or the organization that filed, found that the incident did not constitute a breach or that no health information was breached, or the report was filed by mistake about an incident at another organization. Such a report is left out of this site, its API and its MCP server, because no source on record then shows a breach. A summary that finds only a low probability that data was compromised says no such thing, so that report stays, with the summary quoted as HHS gives it; so does one where people were notified anyway, or where the Office for Civil Rights disagreed. A person reads every such summary before its report is left out, and a report stays on this site until then.
No fact without a source
If no source record gives a cause, a count or a kind of data, the page says so instead of filling the gap.
Figures are never added together
A state filing counts that state’s residents. A catalog entry counts accounts. They measure different things, so each figure is shown with who it counts and which source gives it, and no totals are made from them.
Addresses are not handed out again
Once an organization’s page is published, its address is never handed out again: an address that is retired or taken down never comes to name another organization. When two organizations on record are found to be one and merged, the old address redirects to the one that stays. When one is split, its address stays with one of the parts and the other parts get new addresses. A page that is taken down, as the corrections page describes, is no longer found at its address and does not redirect. When names are merged or corrected, the other names are listed on the page as “also filed as”.
A failing source never deletes data
If a source cannot be read, the last good copy stays in place and the sources page shows when it was last read successfully.
Thin pages stay out of search engines
A page with little on it, such as a name, a date and a small figure, is still published, so the record is complete, but it is marked so that search engines leave it out until there is more to say: a description from the source, a second independent source, or an affected figure of 1,000 or more.
Some pages are never offered to search engines
Two kinds of page are published but always kept out of search engines: a breach that Have I Been Pwned marks as sensitive, such as one at a dating or therapy service, where being linked to it can harm the people in it; and a practice named for a person, such as a doctor’s or a lawyer’s office.
Private individuals are not named
Regulators list whoever filed a notice, and sometimes that is a private person rather than an organization. Every filing with a state attorney general or with HHS is screened for this before it is published (a Form 8-K comes from a company registered with the SEC), and a filing found to come from a private person is left out of this site, its API and its MCP server. When a source adds a person’s name in parentheses after an organization’s name, the name is removed, there and in that filing’s description. A person’s name that a reviewer finds in the description of a breach at another organization, such as a doctor’s, is removed the same way. Screening can miss a name. If an entry names a private person, write to corrections@whogothacked.com and the name will be taken down, as described on the corrections page.
What is never used
- Claims by criminal groups. A threat actor naming a victim is never a source. Such claims are sometimes invented.
- Ransomware leak-site trackers. They repeat those claims, so they are not read.
- Leaked or stolen data. The site does not host it, link to it, or link to anywhere that does.
- Anything a reader cannot open. An incident needs a source record you can check for yourself.
What the record cannot tell you
- Whether your own details were involved. Records here are about organizations. The notice letter you received is the authority on your data.
- That an organization is safe. A name with no record here has no record here. Many breaches are never filed with the sources this site reads.
- The full size of an incident. A figure covers only the group its source counts.
How names are matched
Filings for the same organization often use different names. Records are merged only when the match is clear, and the names seen in filings are listed on the page. If two organizations have been merged wrongly, or one has been split in two, please say so: how to dispute an entry, or corrections@whogothacked.com.