# Check if an e-mail address has a Netflix account

> Find out in real time whether an e-mail address is used for a Netflix account. Yes, no or unknown per address; no account details; unknowns are free.

Canonical: https://mobilevalidate.com/services/netflix-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 Netflix e-mail check answers whether an e-mail address is used for a Netflix account. It runs in real time and in bulk jobs, and returns `registered: true`, `false` or `null` (unknown), with the time we checked. Nothing is sent to the address, and no plan, payment or viewing information is returned.

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

It tells you whether Netflix has an account that uses this address. Netflix accounts are created with an e-mail address, and a phone number can be added for sign-in and recovery. For numbers, use the [Netflix number check](/services/netflix-number-check). A "yes" says nothing about whether the account is paid, paused or cancelled. It only shows that the address was used to create an account. Netflix reported more than 300 million paid memberships in its Q4 2024 shareholder letter, so a "no" for a consumer address is common and is not a warning sign by itself.

- `registered: true`: a Netflix account is associated with the address.
- `registered: false`: a conclusive "no account".
- `registered: null`: no conclusive answer (`status` and `reason` say why). Not charged.

## Who uses it, and why?

- **Subscription and trial businesses.** Services that fight repeated free-trial sign-ups use a "yes" at a large consumer subscription service as a sign that an address is in real, long-term use. See [OTP and sign-up fraud](/use-cases/otp-and-signup-fraud).
- **Consumer lead quality.** Next to the [mailbox check](/services/email-verification), it helps tell real consumer addresses from invented ones.

## What do you get back?

| Field | Type | Meaning |
|---|---|---|
| `email`, `email_status` | string, enum | Normalized address; `valid`, `invalid_email`, `duplicate` or `suppressed` |
| `checks["netflix.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 per address with a conclusive answer. Real-time and bulk have separate prices, shown on [pricing](/pricing). You're not charged for inconclusive results (unknown, unsupported country, timeout, invalid, duplicate). Cache hits inside the freshness window are free.

## What are the limits?

The check runs in real time (`POST /v1/lookup`, up to 100 numbers and e-mails) and in bulk jobs (`POST /v1/jobs`, up to 50,000). Use the code `netflix.email`. The alias `netflix` means the phone-number check. A request can hold 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 of your own users and customers, 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 out what services a specific person subscribes to, and don't use it for unsolicited marketing. 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/lookup \
  -H "Authorization: Bearer $MOBILEVALIDATE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"emails": ["registered@test.mobilevalidate.com"], "checks": ["netflix.email"]}'
```

Response (excerpt, test mode: the first item of `results`):

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

## Frequently asked questions

### Does the check reveal the subscription or plan?

No. It only answers whether a Netflix account is associated with the address: yes, no or unknown. No plan, payment status, profile or viewing data is returned.

### Does a yes mean the address belongs to a paying subscriber?

No. It means an account uses the address. The account may be active, paused or cancelled.

### Can I check phone numbers as well?

Yes. Netflix accounts can also have a phone number for sign-in and recovery. Use the Netflix number check for numbers.

### What does an unknown answer cost?

Nothing. Inconclusive answers are never charged.

## Service code and modes

- Code: `netflix.email` (input: e-mail address)
- Modes: realtime and bulk · worldwide

## Price (live)

- Realtime (POST /v1/lookup): $0.002 per check ($2.00 per 1,000)
- Bulk (POST /v1/jobs): $0.0015 per check ($1.50 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._