# Check if an e-mail address has an X (Twitter) account

> Check in bulk whether an e-mail address is associated with an X (formerly Twitter) account. Yes, no or unknown; no usernames or profiles; unknowns free.

Canonical: https://mobilevalidate.com/services/x-twitter-email-check · Last updated: 2026-09-25

![An e-mail envelope routed to mail servers found in DNS; two mailboxes are confirmed and one answer is unknown.](https://mobilevalidate.com/images/email-mailbox-verification.svg)

*E-mail checks look up the domain's mail servers, then whether the mailbox exists.*


The X e-mail check answers whether an e-mail address is associated with an X account (the service was called Twitter until 2023). It runs in bulk jobs and returns `registered: true`, `false` or `null` (unknown) for each address, with the time we checked. Nothing is sent to the address, and no username, handle or profile is returned.

## What does the X e-mail check tell you?

It tells you whether X has an account that uses this e-mail address. X accounts can be registered with an e-mail address or a phone number. For numbers, use the [X number check](/services/x-twitter-number-check). Accounts created before the 2023 rename are the same accounts, so the name makes no difference to the answer.

- `registered: true`: an X account is associated with the address.
- `registered: false`: a conclusive "no account".
- `registered: null`: no conclusive answer (`status` and `reason` explain it). Not charged.

## Who uses it, and why?

- **Sign-up review in batches.** A periodic job over new registrations uses an account at a large public platform as one signal that an address is in real use, next to the [mailbox check](/services/email-verification). See [OTP and sign-up fraud](/use-cases/otp-and-signup-fraud).
- **Lead data quality.** It works together with the [LinkedIn e-mail check](/services/linkedin-email-check) when cleaning older contact records.

## What do you get back?

| Field | Type | Meaning |
|---|---|---|
| `email`, `email_status` | string, enum | Normalized address; `valid`, `invalid_email`, `duplicate` or `suppressed` |
| `checks["x.email"].registered` | boolean or null | `true` account exists, `false` none, `null` unknown |
| `…status`, `…reason` | enum, string | Outcome, and why an answer is not conclusive |
| `…confidence`, `…checked_at` | enum, timestamp | How sure the answer is, and when it was obtained |
| `…cached`, `…billed` | boolean | Cache hit, and whether it was charged |

## How is it billed?

You pay the bulk price per address with a conclusive answer, shown on [pricing](/pricing). You're not charged for inconclusive results (unknown, unsupported country, timeout, invalid, duplicate). The free `POST /v1/jobs/estimate` call shows the maximum cost first, and cache hits are free.

## What are the limits?

The check is **bulk only**. `POST /v1/lookup` answers `403 service_disabled` ("The check 'x.email' is available in bulk jobs only (POST /v1/jobs)."). Use the code `x.email`. The aliases `x` and `twitter` mean the phone-number check. A job takes up to 50,000 numbers and e-mails, and a request up to 20 checks. Requests that look like sequential number ranges or generated e-mail lists are rejected: 20 or more addresses in one request on one domain that differ only by digits or separators, or, with live keys, 50 or more of one such pattern per account per UTC day.

## How do I use it responsibly?

Check addresses your users and customers gave you, for fraud prevention and data quality. We never read mailboxes or send e-mail to the address, and the answer is only yes, no or unknown. Don't use it to find someone's social media account or to build audiences. The [acceptable use policy](/legal/acceptable-use) forbids both. People can object through the [opt-out form](/opt-out).

## Example request

```bash
curl https://api.mobilevalidate.com/v1/jobs \
  -H "Authorization: Bearer $MOBILEVALIDATE_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: x-email-demo-001" \
  -d '{"emails": ["registered@test.mobilevalidate.com", "not-registered@test.mobilevalidate.com", "unknown@test.mobilevalidate.com"], "checks": ["x.email"]}'
# then: GET /v1/jobs/{id}?wait=30 and GET /v1/jobs/{id}/results
```

Response of `GET /v1/jobs/{id}/results` (excerpt, test mode: the first item of `data`):

```json
{
  "kind": "email",
  "input": "re•••@test.mobilevalidate.com",
  "email": "registered@test.mobilevalidate.com",
  "email_status": "valid",
  "e164": null,
  "country": null,
  "checks": {
    "x.email": {
      "service": "x.email",
      "status": "completed",
      "registered": true,
      "attributes": null,
      "confidence": "high",
      "confidence_score": 0.99,
      "checked_at": "2026-09-25T14:25:55.285Z",
      "cached": false,
      "age_seconds": 0,
      "billed": false,
      "reason": null,
      "poll_after_ms": null
    }
  },
  "test": true
}
```

## Frequently asked questions

### Does the check return the X username or profile?

No. It only answers whether an X account is associated with the address: yes, no or unknown. No username, handle, photo or profile is returned.

### Is X the same as Twitter?

Yes. Twitter was renamed X in 2023. Accounts created under either name are covered.

### Why is the X e-mail check only in bulk jobs?

It is offered in bulk jobs only for now. POST /v1/lookup refuses it with service_disabled; use POST /v1/jobs.

### What does an unknown answer cost?

Nothing. Inconclusive answers are never charged.

## Service code and modes

- Code: `x.email` (input: e-mail address)
- Modes: bulk only · worldwide

## Price (live)

- Realtime: not available (bulk only)
- Bulk (POST /v1/jobs): $0.00015 per check ($0.15 per 1,000)
- You're not charged for inconclusive results (unknown, unsupported country, timeout, invalid, duplicate).

## Response fields (from the public catalog)

| Field | Type | Meaning |
|---|---|---|
| registered | boolean or null | true = found, false = not found, null = unknown (not charged) |
| status | enum | completed, pending, unknown, unsupported_country, failed |
| checked_at | timestamp | When the answer was obtained |

_Platform and brand names are used only to describe which service a check refers to. MobileValidate is not affiliated with, endorsed by or sponsored by any of these companies; all trademarks belong to their owners._