Fake Phone Number Generator

Plausible phone numbers in the officially-reserved test ranges. Per-country formats. Never dial a real line.

Country
Format
How many
Press Generate

Pick a country and hit Generate.

All numbers are drawn from officially-reserved fictional ranges (NANP 555-01xx, UK 07700 900xxx, AU 02 5550 xxxx, FR 01 99 00 xx xx) — safe to use in form QA without calling anyone.

01 — Overview

How the Fake Phone Number Generator works

Generate test phone numbers that look real but live in officially-reserved fictional ranges — US/CA 555-01xx, UK 0700 900 xxxx, AU 02 7010 xxxx, etc. Safe for form QA, demo fixtures, and screenshots without any risk of calling a real person.

02 — Use cases

When to use the Fake Phone Number Generator

  1. 01

    QA a signup form's phone-number validation

  2. 02

    Seed a CRM demo with safe, never-dialable numbers

  3. 03

    Add phone-shaped data to a screenshot without redacting

  4. 04

    Test SMS verification flows in dev without sending real texts

03 — Examples

Fake Phone Number Generator examples

5 × US, formatted

ex 01

(555) 0123-4567\n(555) 0198-7654\n...

Drawn from the 555-01xx range reserved by NANP for fictional use.

3 × UK, international format

ex 02

+44 7700 900123\n+44 7700 900456\n+44 7700 900789

Ofcom's 07700 900000–999999 range reserved for drama and demos.

3 × Australian, national format

ex 03

(02) 7010 1234 · (02) 7010 5678 · (02) 7010 9012

The 02 7010 range is set aside by ACMA for use in drama and advertising.

5 × US, E.164 format

ex 04

+12025550143 · +12025550178 · +12025550122 · …

The storage format — no punctuation, country code included.

04 — FAQ

Phone — frequently asked questions

Why these specific number ranges?

Telecom regulators in many countries reserve specific ranges for fictional use (drama, demos, documentation). Those numbers are guaranteed to never be assigned to real subscribers — so they never accidentally call anyone.

Will real phones accept these as input?

Yes — the formats are standards-compliant and most validators will accept them. They'll just fail to actually dial through.

Will an SMS or a call actually reach these numbers?

No, and that's the point. Every range used here is reserved by the relevant national regulator for fiction and testing, so the numbers are never allocated to a subscriber. A call fails and an SMS silently goes nowhere — which is the correct behaviour for seed data.

How should phone numbers be stored?

In E.164: a plus sign, the country code, and the national number, with no spaces or punctuation — +442079460123. It's unambiguous, sorts predictably, and is what every telephony API expects. Format for display at render time rather than storing the pretty version.

Do these pass libphonenumber validation?

They're structurally valid, so parsing and formatting work correctly. Strict validity checks are less predictable: some reserved ranges are flagged as not-in-service because that's exactly what they are. If your tests assert on isValidNumber, check the specific range you're using first.

What if I need a number that receives real messages?

Use a test number from your SMS provider — Twilio, MessageBird, and Vonage all issue numbers that accept traffic in a sandbox without delivering it onward. These generated numbers can't do that; they exist so that nothing is delivered at all.

05 — Reference

Specs and further reading

The primary sources this tool follows. Where behaviour is defined by a specification, we link the specification rather than a summary of it.

  • ITU-T E.164

    ITU — The international numbering plan that defines country codes and maximum length.

  • RFC 3966: The tel URI

    IETF — The correct format for telephone numbers in links and structured data.

  • 555 (telephone number)

    Wikipedia — The North American range reserved for fiction, which never connects to a real subscriber.

07 — More

Tools that pair with Phone

Last updated .