Start with the live form
Enter a domain, URL, IP, email, or record and get a focused result without setup.
Free Tool
Phone Number Intelligence Tool
Validate and format phone numbers, then inspect the offline intelligence available for their prefix. No paid telecom lookup or live reachability check is performed.
Analyzing phone number...
Phone Number Result
Numbering-Plan Validation, Not Live Verification
DomScan checks format, documented ranges, and offline metadata. A location is a numbering-plan area, not a physical position. A carrier or allocation holder is the original range association, not necessarily the current carrier after porting. The result does not confirm assignment, activity, reachability, SMS delivery, or subscriber identity.
API Endpoint
POST /v1/phone/validate
Validate first. Pay for live telecom data only when needed.
DomScan handles the first pass with numbering-plan validation, standard formats, offline metadata, and official range or prefix evidence where available. Filter and route numbers first, then add a separate live service only when a decision depends on current-carrier or porting data, reachability, authorized identity verification, or provider-specific fraud signals.
One Credit per Number
Run routine numbering-plan checks across every number before deciding which records justify a live network lookup.
No Per-Number Telecom Query
DomScan checks format, documented ranges, and offline metadata. A location is a numbering-plan area, not a physical position. A carrier or allocation holder is the original range association, not necessarily the current carrier after porting. The result does not confirm assignment, activity, reachability, SMS delivery, or subscriber identity.
Official Allocation Context
Where coverage exists, see the matching range status and original allocation holder with source and snapshot details. It describes a range and does not identify the current carrier or subscriber.
Interactive intelligence tool
Run the check, then ship the workflow
Use the browser tool for a fast answer, then move the same logic into scripts, monitoring, or product flows when it becomes repeatable.
Review decision-ready signals
Outputs highlight statuses, risks, records, and next actions instead of raw provider noise.
Automate the winning workflow
Use the request and response examples to turn a one-off check into an API call or recipe.
Used by people at amazing companies
What this tool helps you decide
Each page is shaped around a practical operational question, not just a raw lookup.
See the current DNS, registration, security, pricing, or reputation evidence.
Compare the result with related checks so the next move is easier to trust.
Copy examples, open linked tools, or move into API documentation when you need scale.
Trust signals before you integrate
Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.
Service status
API artifacts
OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.
API keys
Protected access
Authenticated endpoints use API keys with clear credit costs before you call them.
Free allowance
Sign Up for Free
Start with 10,000 monthly credits and upgrade only when usage grows.
Active
Example Request
Start from the curl and HTTP samples, then map the parameters into your application code.
Key Features
Strict Numbering-Plan Validation
Check length and digit patterns against full numbering-plan metadata, not length alone.
Standardized Formats
Return E.164, international, national and RFC 3966 formats, including parsed extensions.
Possible Versus Valid
Separate numbers with a plausible length from ranges recognized by the numbering plan.
Number Type and Prefix Intelligence
Identify number type, numbering-plan location, possible time zones, original prefix carrier, and portability support when metadata has them.
Country-Aware Dialing and Short Codes
Parse national numbers with a country, generate origin-specific dialing formats, and recognize regional short codes and emergency numbers.
Bulk Validation
Validate up to 100 numbers per request with an individual result for every input.
Offline Sources and Official Allocations
Where coverage exists, see the matching range status and original allocation holder with source and snapshot details. It describes a range and does not identify the current carrier or subscriber.
Example Request
curl -X POST https://domscan.net/v1/phone/validate \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"phone":"+34 612 345 678","expected_country":"ES","dialing_from_country":"US","language":"en"}'Example Response
{
"valid": true,
"possible": true,
"status": "valid",
"recommendation": "accept",
"validation_level": "numbering_plan",
"number": {
"e164": "+34612345678",
"international": "+34 612 34 56 78",
"national": "612 34 56 78",
"rfc3966": "tel:+34612345678",
"country": "ES",
"country_calling_code": "34",
"type": "mobile"
},
"intelligence": {
"status": "available",
"location": {
"country_name": "Spain",
"country": "ES",
"granularity": "country",
"current_physical_location": false
},
"possible_time_zones": {
"values": ["Europe/Madrid"],
"current_location": false
},
"original_prefix_carrier": {
"name": null,
"current_carrier": false,
"portability_may_change_carrier": true
},
"dialing": {
"from_country": "US",
"international": "011 34 612 34 56 78",
"internationally_diallable": true
},
"regulator_allocations": [{
"authority": "CNMC",
"category": "mobile",
"status": "assigned",
"original_assignee": "FOOTBALLERISTA MOBILE SPAIN, S.A. UNIPERSONAL",
"assigned_on": "2023-11-03",
"current_operator": false
}],
"sources": [{
"name": "Google libphonenumber metadata",
"license": "Apache-2.0"
}, {
"name": "Comisión Nacional de los Mercados y la Competencia (CNMC)",
"type": "official_regulator_snapshot"
}]
},
"privacy": {
"upstream_requests": 0,
"telecom_provider_queried": false,
"persisted": false,
"domscan_edge_relay_used": true,
"third_party_requests": 0
}
}Built from the same API surface
The browser experience previews DomScan's structured endpoints, so teams can validate a use case before writing code.
Frequently Asked Questions
What does a valid phone number mean?
Valid means the number matches the documented length and digit patterns of a recognized numbering-plan range. It does not mean the number is assigned to a subscriber.
Does validation prove that the number is active or reachable?
No. Numbering-plan validation cannot confirm that a number is assigned, active, reachable, or able to receive calls or SMS.
Does the API return the current carrier or phone owner?
The API may return an original prefix carrier or regulator allocation holder. Neither field is the current carrier after number porting, and neither identifies the subscriber or phone owner.
Do national phone numbers require a country?
Yes. Provide a default country or region when the number does not start with an international calling code. A country is also required to interpret regional short codes and emergency numbers.
Where does the intelligence data come from?
Global metadata comes from Google libphonenumber. Official range and prefix evidence can also come from public snapshots published by CNMC, ARCEP, Bundesnetzagentur, MIC Japan, RTR Austria, Nkom, UKE Poland, MODA Taiwan, NANPA for the United States, and CNA/CNAC for Canada. US and Canadian records describe NPA-NXX central office code status and original code holders, not the current carrier of a ported number. Each result names its sources, snapshot dates, and coverage level. Location and time zones describe the numbering-plan prefix, not the phone’s current position.
Can I validate phone numbers in bulk?
Yes. The bulk endpoint accepts up to 100 numbers and returns results in input order. If offline enrichment is unavailable, the local validation still completes and intelligence.status reports the fallback.