Start with the live form
Enter a domain, URL, IP, email, or record and get a focused result without setup.
Validate and format phone numbers, then inspect the offline intelligence available for their prefix. No paid telecom lookup or live reachability check is performed.
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.
POST /v1/phone/validate
Use the browser tool for a fast answer, then move the same logic into scripts, monitoring, or product flows when it becomes repeatable.
Enter a domain, URL, IP, email, or record and get a focused result without setup.
Outputs highlight statuses, risks, records, and next actions instead of raw provider noise.
Use the request and response examples to turn a one-off check into an API call or recipe.
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.
Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.
OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.
Authenticated endpoints use API keys with clear credit costs before you call them.
Start with 10,000 monthly credits and upgrade only when usage grows.
Start from the curl and HTTP samples, then map the parameters into your application code.
Check length and digit patterns against full numbering-plan metadata, not length alone.
Return E.164, international, national and RFC 3966 formats, including parsed extensions.
Separate numbers with a plausible length from ranges recognized by the numbering plan.
Identify number type, numbering-plan location, possible time zones, original prefix carrier, and portability support when metadata has them.
Parse national numbers with a country, generate origin-specific dialing formats, and recognize regional short codes and emergency numbers.
Validate up to 100 numbers per request with an individual result for every input.
Use offline metadata and public regulator snapshots on DomScan infrastructure. Matching results include source, licence, update date, and original allocation context.
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"}'{
"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
}
}The browser experience previews DomScan's structured endpoints, so teams can validate a use case before writing code.
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.
No. Numbering-plan validation cannot confirm that a number is assigned, active, reachable, or able to receive calls or SMS.
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.
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.
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.
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.