RealtimeBulkE-mail input

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.

$0.004 per check real-time, $0.0025 in bulk ($4.00 / $2.50 per 1,000). Unknowns are free. Try 10 e-mail addresses for real, free, after sign-up.

Start free

Last updated

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. 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.
  • Consumer lead quality. Next to the mailbox check, it helps tell real consumer addresses from invented ones.

What do you get back?

FieldTypeMeaning
email, email_statusstring, enumNormalized address; valid, invalid_email, duplicate or suppressed
checks["netflix.email"].registeredboolean or nulltrue account exists, false none, null unknown
…status, …reasonenum, stringOutcome, and why an answer is not conclusive
…confidence, …checked_atenum, timestampHow sure the answer is, and when it was obtained
…cached, …billedbooleanCache 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. 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 forbids both. People can object through the opt-out form.

Example request

curl https://api.mobilevalidate.com/v1/lookup \
  -H "Authorization: Bearer mv_test_publicSandboxn9ZgneuhR1B9CRfKG3fulym" \
  -H "Content-Type: application/json" \
  -d '{"emails":["registered@test.mobilevalidate.com"],"checks":["netflix.email"]}'

Runs as pasted with the public sandbox key, which answers the test values only. In the SDKs, omit the key to use MOBILEVALIDATE_API_KEY.

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
}

Try it now

Run it here with a test value: the console calls the live API from your browser with the public sandbox key and shows the real JSON and a plain-English verdict.

POST /v1/lookup

Public sandbox key · test values only · never billed

The sandbox answers the test values below. To check your own numbers for real, create a free account: your first 20 phone numbers and 10 e-mail addresses are free.

Test numbers
Test e-mails
Checks · e-mail · 1 selected

Pick a test value or press Run

Press Run or pick a test value above: the console sends a real request to the API with the public sandbox key and shows the answer here.

Check your own addresses: 20 phone numbers and 10 e-mail addresses are checked for real, free, after sign-up. Start free

checks: ["netflix.email"] · Realtime lookup via POST /v1/lookup. Every example runs as pasted: it uses the public sandbox key, which answers the test values for free. In the SDKs, omit the key to use MOBILEVALIDATE_API_KEY.

curl https://api.mobilevalidate.com/v1/lookup \
  -H "Authorization: Bearer mv_test_publicSandboxn9ZgneuhR1B9CRfKG3fulym" \
  -H "Content-Type: application/json" \
  -d '{"emails":["registered@test.mobilevalidate.com"],"checks":["netflix.email"]}'

Real test-mode result for this check

checks["netflix.email"]
{
  "service": "netflix.email",
  "status": "completed",
  "registered": true,
  "attributes": null,
  "confidence": "high",
  "confidence_score": 0.99,
  "checked_at": "2026-09-25T14:25:29.021Z",
  "cached": false,
  "age_seconds": 0,
  "billed": false,
  "reason": null,
  "poll_after_ms": null
}

What you get

Fields of checks["netflix.email"], generated from the public service catalog.

FieldTypeMeaning
registeredboolean | nulltrue = found, false = not found, null = unknown (not charged).
statusenumcompleted, pending, unknown, unsupported_country or failed.
checked_attimestampWhen the answer was obtained.

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.

Is there a free netflix account check by e-mail?

Yes, to try it on your own data: create a free account and check up to 10 e-mail addresses for real on the dashboard's Try it page, at no cost. Test mode with documented test values is free and unlimited. After that, a netflix account check by e-mail costs $0.004 per check in real time ($4.00 per 1,000) and $0.0025 in bulk jobs ($2.50 per 1,000), paid from prepaid credit. Unknown and other inconclusive results are always free.

Add Netflix account check by e-mail to your stack

Create a free MobileValidate account: approved automatically, usually within 10–15 minutes. Netflix account check by e-mail: $0.004 per check real-time, $0.0025 in bulk ($4.00 / $2.50 per 1,000).

Free to start: check 20 phone numbers and 10 e-mail addresses for real on your account, plus an unlimited test mode. You pay only for conclusive answers, from $20.