Check if a phone number has a Netflix account

The Netflix check indicates whether a Netflix account is associated with a phone number. It runs in real time and in bulk jobs, for numbers from any country, and answers registered: true, false or null (unknown) with the time of the check. It never returns profiles, viewing history or plan details.

Can you look up a Netflix account by phone number?

You can check whether a Netflix account is associated with a phone number, and nothing more. Send the number with the check netflix and you get registered: true, false or null (unknown, free) with the time of the check. The answer never identifies the account: no e-mail address, member name, profile, plan or viewing history.

Netflix lets members add a phone number for sign-in and recovery, and "only one account can have your verified phone number on it": verifying a number removes it from any other account it was tied to (Netflix Help Center). Our answer stays the same either way: whether an account is associated with the number, not which one.

What does the Netflix check tell you?

It tells you whether a phone number is linked to a Netflix account. Netflix accounts are paid subscriptions held by one member and shared within a household. A phone number can be added for sign-in and account recovery, but most accounts are created with an e-mail address.

• registered: true: a Netflix account is associated with the number.
• registered: false: a conclusive "no". Common, because many accounts have no phone number and many people use someone else's account.
• registered: null: no conclusive answer. Not charged.

Netflix reported 301.63 million paid memberships at the end of 2024 in its fourth-quarter shareholder letter (Netflix Q4 2024 letter, January 2025), and said it would stop reporting the count every quarter from 2025. Accounts are spread across most countries, but one account usually covers a whole household. So true says something about the account holder's number, not about each person who watches.

Who uses it, and why?

A paid subscription is harder to fake than a free sign-up, so a number linked to one is a useful signal that the number is established and in everyday use.

• Trial and promotion abuse. Subscription businesses see repeated free-trial sign-ups from freshly obtained numbers. A number with no history on large consumer services can be routed to extra verification, and one with history can pass straight through. See OTP and sign-up fraud.
• Account security. When a recovery number changes, history on other paid services is one mild reassurance.

Netflix tightened account-sharing rules in 2023, which pushed more people to hold their own accounts. That trend may make the signal slightly more useful over time, but it is not a reason to rely on it alone.

What do you get back?

Each number gets one result under checks["netflix.registered"], with no extra attributes.

How is it billed?

You pay per number checked, only for conclusive answers. You're not charged for inconclusive results (unknown, unsupported country, timeout, invalid, duplicate). Real-time and bulk checks are priced separately. See pricing. Cache hits are free, and max_age: 0 forces a fresh, billed check.

What are the limits?

• Real time (POST /v1/lookup, up to 100 identifiers) and bulk jobs (POST /v1/jobs, up to 50,000 per job), for numbers from every country.
• Up to 20 checks per request. Numbers × checks is capped at 2,000 per lookup and 100,000 per job.
• Requests that look like sequential number ranges or generated e-mail lists are rejected.
• A daily cap per account applies (GET /v1/limits).

How do I use it responsibly?

Use the answer to protect sign-ups and offers, only for numbers you have a lawful basis to process. Don't use it to infer how people spend their money or to decide on eligibility for anything. The acceptable use policy forbids profiling and unsolicited messaging. People can object at /opt-out.

Example request

With a test key, +447700900001 answers "registered". See test mode.

curl https://api.mobilevalidate.com/v1/lookup \
  -H "Authorization: Bearer mv_test_publicSandboxn9ZgneuhR1B9CRfKG3fulym" \
  -H "Content-Type: application/json" \
  -d '{"numbers":["+447700900001"],"checks":["netflix"]}'

// npm install mobilevalidate · Node.js 20+ · save as check.mjs and run: node check.mjs
import { MobileValidate } from "mobilevalidate";

// Omit apiKey to read MOBILEVALIDATE_API_KEY from the environment.
const mv = new MobileValidate({ apiKey: "mv_test_publicSandboxn9ZgneuhR1B9CRfKG3fulym" });
const { data, error } = await mv.lookup({
  numbers: ["+447700900001"],
  checks: ["netflix"],
});
if (error) console.error(error.code, error.message);
else console.dir(data.results, { depth: null });

// Node.js 18+, Deno, Bun or the browser console (ES module: save as .mjs or use "type": "module").
const res = await fetch("https://api.mobilevalidate.com/v1/lookup", {
  method: "POST",
  headers: {
    Authorization: "Bearer mv_test_publicSandboxn9ZgneuhR1B9CRfKG3fulym",
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    numbers: ["+447700900001"],
    checks: ["netflix"],
  }),
});
console.log(res.status, res.headers.get("x-request-id"));
console.dir(await res.json(), { depth: null });

# pip install mobilevalidate-sdk
from mobilevalidate import MobileValidate

# Omit api_key to read MOBILEVALIDATE_API_KEY from the environment.
mv = MobileValidate(api_key="mv_test_publicSandboxn9ZgneuhR1B9CRfKG3fulym")
result = mv.lookup(numbers=["+447700900001"], checks=["netflix"])
print(result)

<?php
$ch = curl_init('https://api.mobilevalidate.com/v1/lookup');
curl_setopt_array($ch, [
    CURLOPT_POST => true,
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER => [
        'Authorization: Bearer mv_test_publicSandboxn9ZgneuhR1B9CRfKG3fulym',
        'Content-Type: application/json',
    ],
    CURLOPT_POSTFIELDS => json_encode([
        'numbers' => ['+447700900001'],
        'checks' => ['netflix'],
    ]),
]);
$response = curl_exec($ch);
echo curl_getinfo($ch, CURLINFO_RESPONSE_CODE), PHP_EOL, $response, PHP_EOL;

package main

import (
	"fmt"
	"io"
	"net/http"
	"strings"
)

func main() {
	body := strings.NewReader(`{"numbers":["+447700900001"],"checks":["netflix"]}`)
	req, err := http.NewRequest("POST", "https://api.mobilevalidate.com/v1/lookup", body)
	if err != nil {
		panic(err)
	}
	req.Header.Set("Authorization", "Bearer mv_test_publicSandboxn9ZgneuhR1B9CRfKG3fulym")
	req.Header.Set("Content-Type", "application/json")
	res, err := http.DefaultClient.Do(req)
	if err != nil {
		panic(err)
	}
	defer res.Body.Close()
	out, _ := io.ReadAll(res.Body)
	fmt.Println(res.Status, string(out))
}

require "net/http"
require "json"

uri = URI("https://api.mobilevalidate.com/v1/lookup")
req = Net::HTTP::Post.new(uri)
req["Authorization"] = "Bearer mv_test_publicSandboxn9ZgneuhR1B9CRfKG3fulym"
req["Content-Type"] = "application/json"
req.body = JSON.generate({
  "numbers" => ["+447700900001"],
  "checks" => ["netflix"]
})

res = Net::HTTP.start(uri.host, uri.port, use_ssl: true) { |http| http.request(req) }
puts res.code, res.body

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

{
  "kind": "phone",
  "input": "+447700900001",
  "e164": "+447700900001",
  "country": "GB",
  "number_status": "valid",
  "checks": {
    "netflix.registered": {
      "service": "netflix.registered",
      "status": "completed",
      "registered": true,
      "attributes": null,
      "confidence": "high",
      "confidence_score": 0.99,
      "checked_at": "2026-09-25T14:25:31.231Z",
      "cached": false,
      "age_seconds": 0,
      "billed": false,
      "reason": null,
      "poll_after_ms": null
    }
  },
  "test": true
}