# XposedOrNot

> Check whether an email address or a password has been exposed in a known data breach, with XposedOrNot's free, open breach index. Get an address's full breach history with a risk score, see how exposed a company's email domain is, look up and list breaches, follow breach news, and run a workflow whenever a new breach is added. Passwords are checked without ever leaving Lodol. No account or API key required.

App · 8 actions. Web page: https://docs.lodol.com/docs/integrations/xposedornot

## Actions

### Check a password

Find out whether a password has been leaked in a data breach, and how often it was seen. The password never leaves Lodol: it is hashed here and only the first 10 characters of its hash are sent, which match many passwords. Useful for refusing leaked passwords at sign-up. No API key required.

**Inputs**

- Password (`password`, text, required): The password to check. Only the first 10 characters of its Keccak-512 hash are sent to XposedOrNot, never the password itself. Pass it from an earlier step rather than typing a real password here, since a typed value is saved with the workflow.

**Outputs**

- `exposed` (true/false): True when the password appears in leaked password lists.
- `hash_prefix` (text): The only thing sent to XposedOrNot: the first 10 characters of the password's Keccak-512 hash.
- `summary` (text): One sentence with the answer, ready for a message.
- `times_seen` (number): How many times it was seen in breaches. 0 when not found.

**Example output**

```json
{
  "exposed": true,
  "hash_prefix": "aa77c1b9b7",
  "summary": "This password has been exposed in data breaches, seen 62,703 times. Don't use it.",
  "times_seen": 62703
}
```

### Check an email for breaches

Find out whether an email address appears in any known data breach, and in which ones by name. An address in no breach comes back with 'breached' set to false rather than failing the step. XposedOrNot allows 25 email checks an hour from Lodol. No API key required.

**Inputs**

- Email address (`email`, text, required): The email address to look up, such as name@example.com. Spaces and capitals don't matter.

**Outputs**

- `breach_count` (number): How many known breaches the address appears in.
- `breached` (true/false): True when the address appears in at least one known breach.
- `breaches` (list): The names of those breaches, A to Z. Empty when there are none.
- `email` (text): The address checked, trimmed and in lower case.
- `summary` (text): One sentence with the answer, ready for a message.

**Example output**

```json
{
  "breach_count": 3,
  "breached": true,
  "breaches": [
    "Adobe",
    "LinkedIn",
    "MyFitnessPal"
  ],
  "email": "test@example.com",
  "summary": "test@example.com appears in 3 known data breaches."
}
```

### Get a breach

Get one data breach by its name: what happened, when, the website, how many records and what kinds of data were exposed, how passwords were stored, and a news report about it. Takes the names 'Check an email for breaches' returns. A name XposedOrNot does not have fails the step. No API key required.

**Inputs**

- Breach (`breach`, text, required): The breach's name in XposedOrNot, such as Adobe or LinkedIn. Pick one, or pass a name from an earlier step. Capitals don't matter.

**Outputs**

- `added_at` (text): When XposedOrNot added the breach, as an ISO 8601 date and time.
- `breach_type` (text): What kind of leak it was: 'Data breach', 'Combo list' (credentials gathered from many leaks), 'Stealer logs' or 'Scrape'.
- `breached_on` (text): When the breach happened, as a date (YYYY-MM-DD). XposedOrNot records the month, so this is the first day of it.
- `breached_year` (number): The year the breach happened.
- `description` (text): What happened and what was exposed, in a few sentences.
- `domain` (text): The website that was breached, such as 'adobe.com'.
- `exposed_data` (list): The kinds of data exposed, such as 'Email addresses' and 'Passwords'.
- `industry` (text): The breached organisation's industry, such as 'Finance'.
- `logo_url` (text): The breached organisation's logo.
- `name` (text): The breach's name in XposedOrNot, such as 'Adobe'. Get a breach takes it.
- `password_risk` (text): How the breached passwords were stored: 'plaintext', 'easytocrack', 'hardtocrack' or 'unknown'.
- `password_risk_label` (text): The same in words, such as 'Easy to crack'.
- `records_exposed` (number): How many accounts or records were exposed.
- `reference_url` (text): A news report or announcement about the breach, when there is one.
- `searchable` (true/false): True when an email check can find addresses in this breach.
- `sensitive` (true/false): True for a breach whose membership is itself sensitive, such as a dating site. Email checks don't name these.
- `verified` (true/false): True when XposedOrNot has confirmed the breach is genuine.

**Example output**

```json
{
  "added_at": "2023-11-08T06:30:03+00:00",
  "breach_type": "Data breach",
  "breached_on": "2013-10-01",
  "breached_year": 2013,
  "description": "Adobe, the multinational software company, suffered a major data breach in October 2013 that eventually affected about 150 million accounts.",
  "domain": "adobe.com",
  "exposed_data": [
    "Usernames",
    "Passwords",
    "Email addresses"
  ],
  "industry": "Information Technology",
  "logo_url": "https://xposedornot.com/static/logos/Adobe.png",
  "name": "Adobe",
  "password_risk": "easytocrack",
  "password_risk_label": "Easy to crack",
  "records_exposed": 152403035,
  "reference_url": "https://krebsonsecurity.com/2013/10/adobe-breach-impacted-at-least-38-million-users/",
  "searchable": true,
  "sensitive": false,
  "verified": true
}
```

### Get a domain's breach exposure

Find out how exposed a company's email domain is: how many addresses at it appear in known breaches, in how many breaches, how many pastes, and when the latest breach happened. Counts only; no addresses are returned. A domain with nothing exposed comes back with 'exposed' set to false. No API key required.

**Inputs**

- Domain (`domain`, text, required): The email domain to check, such as adobe.com. A link or an email address at the domain works too.

**Outputs**

- `breach_count` (number): How many different breaches those addresses appear in.
- `domain` (text): The domain checked, such as 'adobe.com'.
- `exposed` (true/false): True when any address at the domain appears in a known breach.
- `exposed_addresses` (number): How many addresses at the domain appear in breaches.
- `exposed_addresses_capped` (true/false): True when XposedOrNot stopped counting at 10,000 addresses, so there are at least that many.
- `exposure_count` (number): Every appearance of an address in a breach, added up.
- `latest_breach_on` (text): When the most recent of those breaches happened (YYYY-MM-DD, the first of its month). Empty when there are none.
- `paste_count` (number): How many pastes mention addresses at the domain.
- `paste_count_capped` (true/false): True when XposedOrNot stopped counting pastes at 50.
- `summary` (text): One sentence with the answer, ready for a message.

**Example output**

```json
{
  "breach_count": 113,
  "domain": "adobe.com",
  "exposed": true,
  "exposed_addresses": 10000,
  "exposed_addresses_capped": true,
  "exposure_count": 16447,
  "latest_breach_on": "2026-08-01",
  "paste_count": 20,
  "paste_count_capped": false,
  "summary": "At least 10,000 addresses at adobe.com appear in 113 known data breaches, the latest from 2026-08-01."
}
```

### Get an email's breach analytics

Get the full picture for an email address: every breach it appears in, with what happened, when, how many records and what kinds of data were exposed, plus a risk score from 0 to 100, the kinds of data exposed across all of them, a count by industry and by year, and how the breaches stored its password. An address in no breach comes back with 'breached' set to false. No API key required.

**Inputs**

- Email address (`email`, text, required): The email address to look up, such as name@example.com. Spaces and capitals don't matter.

**Outputs**

- `breach_count` (number): How many known breaches the address appears in.
- `breached` (true/false): True when the address appears in at least one known breach.
- `breaches` (list): Every breach the address appears in, most recently added first.
- `breaches_by_year` (list): How many of the breaches happened each year, earliest first.
- `email` (text): The address checked, trimmed and in lower case.
- `exposed_data_types` (list): Every kind of data exposed across those breaches, the most often exposed first.
- `industries` (list): The industries of the breached organisations, the most breaches first.
- `password_storage` (object): How the breaches stored the address's password.
- `paste_count` (number): How many pastes (dumps posted on sites like Pastebin) the address appears in.
- `risk_label` (text): The risk in a word, such as 'Low', 'Medium', 'High' or 'Critical'.
- `risk_score` (number): XposedOrNot's risk score for the address, from 0 to 100. Empty when it is in no breach.
- `summary` (text): One sentence with the answer and the risk, ready for a message.

**Example output**

```json
{
  "breach_count": 1,
  "breached": true,
  "breaches": [
    {
      "added_at": "2026-10-02T12:15:46+00:00",
      "breached_year": 2026,
      "description": "McKesson, a healthcare and pharmaceutical company, was targeted in August 2026, exposing 6.8M unique email addresses.",
      "domain": "mckesson.com",
      "exposed_data": [
        "Email addresses",
        "Names",
        "Phone numbers"
      ],
      "industry": "Health Care",
      "logo_url": "https://xposedornot.com/static/logos/Mckesson.png",
      "name": "McKesson",
      "password_risk": "unknown",
      "password_risk_label": "Unknown",
      "records_exposed": 6832822,
      "reference_url": null,
      "searchable": true,
      "verified": true
    }
  ],
  "breaches_by_year": [
    {
      "breach_count": 0,
      "year": 2025
    },
    {
      "breach_count": 1,
      "year": 2026
    }
  ],
  "email": "test@example.com",
  "exposed_data_types": [
    {
      "breach_count": 1,
      "category": "Communication and Social Interactions",
      "data_type": "Email addresses"
    },
    {
      "breach_count": 1,
      "category": "Personal Identification",
      "data_type": "Names"
    }
  ],
  "industries": [
    {
      "breach_count": 1,
      "industry": "Health Care"
    }
  ],
  "password_storage": {
    "easy_to_crack": 0,
    "plain_text": 0,
    "strong_hash": 0,
    "unknown": 1
  },
  "paste_count": 0,
  "risk_label": "Critical",
  "risk_score": 100,
  "summary": "test@example.com appears in 1 known data breach, risk Critical (100 out of 100)."
}
```

### Get breach statistics

Get totals across every breach XposedOrNot knows: how many breaches and records, when the latest was added, how many happened each year and in each industry, and the ten largest and ten most recently added breaches. No API key required.

**Inputs**: None.

**Outputs**

- `breach_count` (number): How many breaches XposedOrNot has loaded.
- `breaches_by_industry` (list): How many breaches each industry has had, the most first.
- `breaches_by_year` (list): How many breaches happened each year, earliest first.
- `largest_breaches` (list): The ten largest breaches, the largest first.
- `last_breach_added_at` (text): When the latest breach was added, as an ISO 8601 date and time.
- `recently_added_breaches` (list): The ten breaches added most recently, the newest first.
- `records_exposed` (number): How many records those breaches exposed in all.

**Example output**

```json
{
  "breach_count": 794,
  "breaches_by_industry": [
    {
      "breach_count": 223,
      "industry": "Entertainment"
    },
    {
      "breach_count": 136,
      "industry": "Information Technology"
    }
  ],
  "breaches_by_year": [
    {
      "breach_count": 36,
      "year": 2025
    },
    {
      "breach_count": 83,
      "year": 2026
    }
  ],
  "largest_breaches": [
    {
      "description": "A credential collection found in 2017 with more than 1.4B username and password combinations.",
      "logo_url": "https://xposedornot.com/static/logos/combolist.png",
      "name": "1.4BillionRecords",
      "records_exposed": 1114303554
    }
  ],
  "last_breach_added_at": "2026-10-14T10:52:13+00:00",
  "recently_added_breaches": [
    {
      "description": "Zoosk, an online dating platform, was breached in January 2020.",
      "logo_url": "https://xposedornot.com/static/logos/Zoosk.png",
      "name": "Zoosk-2020",
      "records_exposed": 37378434
    }
  ],
  "records_exposed": 11717004638
}
```

### List breach news

List XposedOrNot's data breach news, newest first: who was breached, when, a short summary and a link to the report. Narrow it to items posted since a date. No API key required.

**Inputs**

- Posted since (`published_since`, date): Only news posted on or after this date.
- How many to return (`limit`, number): The most news items to return, newest first. From 1 to 1000. Default: `20`.

**Outputs**

- `articles` (list): The news items, newest first.
- `count` (number): How many items are listed.
- `more_available` (true/false): True when more matched than the limit let through.
- `total_matching` (number): How many items matched, including any past the limit.

**Example output**

```json
{
  "articles": [
    {
      "published_on": "2026-10-01",
      "summary": "Japanese car-sharing service Times Car has confirmed a data breach impacting 6.6M current and former users.",
      "title": "Times Car",
      "url": "https://www.bleepingcomputer.com/news/security/times-car-confirms-data-breach-affecting-66-million-user-accounts/"
    }
  ],
  "count": 1,
  "more_available": true,
  "total_matching": 713
}
```

### List known breaches

List the data breaches XposedOrNot knows about, most recently added first, with what happened, when, how many records and what kinds of data were exposed. Narrow it to one website, an industry, how passwords were stored, or breaches added or happening since a date. A scheduled workflow watching for new breaches can run on the 'added since' date. No API key required.

**Inputs**

- Website (`domain`, text): Only breaches of this website, such as adobe.com. A link or an email address at the domain works too. Leave empty for every website.
- Industry (`industry`, text): Only breaches of organisations in this industry. Leave empty for every industry.
- Password storage (`password_risk`, list): Only breaches whose passwords were stored this way. Leave everything unticked for every breach. One or more of: `plaintext` (Stored in plain text), `easytocrack` (Easy to crack), `hardtocrack` (Hard to crack), `unknown`.
- Added since (`added_since`, date): Only breaches XposedOrNot added on or after this date.
- Happened since (`breached_since`, date): Only breaches that happened on or after this date. XposedOrNot records the month a breach happened.
- How many to return (`limit`, number): The most breaches to return, newest first. From 1 to 2000. Default: `50`.

**Outputs**

- `breaches` (list): The matching breaches, most recently added first.
- `count` (number): How many breaches are listed.
- `more_available` (true/false): True when more matched than the limit let through.
- `total_matching` (number): How many breaches matched, including any past the limit.

**Example output**

```json
{
  "breaches": [
    {
      "added_at": "2026-10-14T10:52:13+00:00",
      "breach_type": "Data breach",
      "breached_on": "2020-01-01",
      "breached_year": 2020,
      "description": "Zoosk, an online dating platform, was breached in January 2020, exposing 37M unique email addresses.",
      "domain": "zoosk.com",
      "exposed_data": [
        "Email addresses",
        "Names",
        "Dates of birth"
      ],
      "industry": "Entertainment",
      "logo_url": "https://xposedornot.com/static/logos/Zoosk.png",
      "name": "Zoosk-2020",
      "password_risk": "easytocrack",
      "password_risk_label": "Easy to crack",
      "records_exposed": 37378434,
      "reference_url": null,
      "searchable": false,
      "sensitive": true,
      "verified": true
    },
    {
      "added_at": "2023-11-08T06:30:03+00:00",
      "breach_type": "Data breach",
      "breached_on": "2013-10-01",
      "breached_year": 2013,
      "description": "Adobe, the multinational software company, suffered a major data breach in October 2013 that eventually affected about 150 million accounts.",
      "domain": "adobe.com",
      "exposed_data": [
        "Usernames",
        "Passwords",
        "Email addresses"
      ],
      "industry": "Information Technology",
      "logo_url": "https://xposedornot.com/static/logos/Adobe.png",
      "name": "Adobe",
      "password_risk": "easytocrack",
      "password_risk_label": "Easy to crack",
      "records_exposed": 152403035,
      "reference_url": "https://krebsonsecurity.com/2013/10/adobe-breach-impacted-at-least-38-million-users/",
      "searchable": true,
      "sensitive": false,
      "verified": true
    }
  ],
  "count": 2,
  "more_available": true,
  "total_matching": 794
}
```
