How US Phone Validation Works — Carrier, Line Type & DNC

US phone validation checks carrier and numbering data — not just the format. Here is exactly what happens when you validate a number, and how to build it into a TCPA-aware calling workflow.

The Technical Process

Step 1 — Number Normalisation

The input number is cleaned up — dashes, parentheses, spaces, dots and a leading 1 or +1 are removed — so it can be matched regardless of how it was entered. (The API takes 10-digit numbers.)

Step 2 — Carrier & Numbering Data Check

The number is checked against carrier and numbering data sources that are updated daily. The number is never called or texted. The check determines:

• Whether the number is Valid — correctly formed and assigned to a carrier (active)
• Or Invalid — badly formed or not assigned (inactive)
• Which carrier currently holds the number
• The carrier’s network type and domain — ported numbers show their new carrier
• The line type (mobile, landline, VoIP, toll-free)

Step 3 — DNC & TCPA Litigator Check (DNC Lookup)

With DNC Lookup (or Phone + DNC Lookup), US numbers are screened against the Federal (National) DNC list, the state DNC lists of Texas, Florida, Pennsylvania, Indiana, Colorado and Wyoming, and the TCPA Litigator list. Each number comes back as Cleaned Number, TCPA Litigator, Federal (National) DNC or Invalid Number; a state-list hit also names its state.

Step 4 — Location Data

City, state, ZIP code, country and time zone are returned for each number. Note: for ported numbers, location reflects the number’s original area, not where the person lives now.

Step 5 — JSON Response

Results come back as JSON. Shortened examples:

Phone Lookup (shortened):
{
  "status": "success",
  "512*******": {
    "status": "Valid",
    "phone_number": "+1512*******",
    "national_format": "(512) ***-****",
    "number_type": "Mobile",
    "zip": "78701",
    "city": "AUSTIN",
    "state": "TX",
    "country": "US",
    "timezone": "CST (America/Chicago)",
    "network_name": "CELLCO PARTNERSHIP DBA VERIZON",
    "network_type": "WIRELESS",
    "network_domain": "512*******@vtext.com"
  }
}

DNC Lookup:
{
  "status": "success",
  "cleaned_number": ["908*******"],
  "tcpa_litigator": ["757*******"],
  "federal_dnc": ["989*******", "561*******"],
  "state_dnc": {"561*******": "Florida-DNC"},
  "invalid": ["1234567890"]
}

Building a TCPA-Aware Calling Workflow

The Decision Tree

Use the validation response to gate every outbound contact decision:

1. status = Invalid → Remove from list. Do not dial — the number is badly formed or not assigned to a carrier.
2. federal_dnc (Federal or state DNC list) → Suppress from telemarketing. Tag the record in your CRM. Do not call without a valid exemption, such as prior express written consent on file.
3. tcpa_litigator → Escalate to compliance review before any contact. High litigation risk.
4. number_type = VoIP → Flag for review. May be valid, but evaluate against your lead quality criteria.
5. Valid + Mobile + cleaned_number → Can go to your SMS or calling workflow, subject to the consent the TCPA requires for autodialed calls and texts.
6. Valid + Landline + cleaned_number → Suitable for voice calls. Not for SMS.

Integration Points

• Web form — call the API at form submission, before the lead is saved
• CRM automation — trigger validation when a new contact is created (GoHighLevel and Zapier connections are available); write results to custom fields
• Pre-campaign check — batch-validate your segment before export to your dialer
• Dialer list upload — run CSV through the batch validator; filter before loading into your platform

Accuracy & Data Sources

Phone Validator US is powered by RealValidito. Phone Lookup data is updated daily and reflects number porting; numbers ported very recently may still show the previous carrier for a short time. DNC data is refreshed regularly, but numbers are added to DNC lists all the time — scrub again before every campaign. DNC Lookup is a compliance-assistance tool, not legal advice or a guarantee of compliance.