Safety and limitations

Responsible use

GetPhoneNum is a test-data tool. It does not provide telecommunications service or permission to contact any generated value.

Appropriate uses

  • Local development and automated tests
  • Input masks and form validation
  • Product demos, screenshots and documentation
  • Non-production seed data

Prohibited uses

  • Calling or texting generated values
  • Bypassing verification or platform rules
  • Impersonation, harassment or fraud
  • Marketing, lead generation or outreach

What “valid” means

A value may match a country's structural rules without being assigned. GetPhoneNum does not verify reachability, carrier ownership, SMS capability or subscriber identity.

Real-number risk: only some countries publish reserved fictional ranges. A format-accurate result outside those ranges could coincide with a real subscriber, so never attempt contact.

Report a safety concern

If a page appears to encourage unsafe use or a fixture should be replaced with an officially reserved example, use the contact page and cite the relevant regulator or numbering-plan source. Do not include a real subscriber's personal information in a public report.

Safe testing workflow

  1. Keep generation in non-production environments. Use local development, staging or documentation examples rather than customer-facing messaging systems.
  2. Disable outbound delivery by default. Automated tests should not be able to place calls, send SMS or trigger WhatsApp, RCS or voice workflows to generated values.
  3. Record the test purpose. Store the selected country, expected format and scenario name beside a fixture so future maintainers understand why it exists.
  4. Separate format from consent. A parser can say a string fits a country pattern; only a consent-based verification flow can show that a user controls a destination.

This workflow protects real subscribers and makes QA results easier to debug. A generated number that passes a structural check should still have empty reachability, ownership and marketing-consent fields in your test records.

For screenshots and docs

Prefer documented fictional ranges when a country publishes them. If only a structural example is available, add a note that the value is a test fixture and must not be contacted.

For automated tests

Use provider sandbox credentials, internal allowlists and mocked delivery services. Treat any accidental attempt to contact a fixture as a test failure, not as a normal validation step.

For imports and demos

Do not mix generated fixtures with production contacts. If you need a large demo dataset, keep it clearly labelled, versioned and isolated from CRM, lead-generation and notification tools.

Why this policy is part of the product

Phone-number tools sit near sensitive workflows: account recovery, identity checks, messaging and support. Clear limits make the utility safer and more useful. They also help reviewers understand that GetPhoneNum is a developer reference, not a service for obtaining contactable numbers or bypassing verification systems.

When in doubt, choose the safer fixture

If a test can be completed with a documented fictional range, use that option. If no protected range is available, keep the value structural, local and clearly labelled. The extra note may feel small, but it prevents a future teammate from mistaking QA data for a reachable contact list. Safer fixtures also make public demos easier to review because the warning travels with the example.