Live
Service status
Check live service health and documented failure responses before you integrate.
Category
DNS & Network
Endpoints
1
Key Features
8
Frequently Asked Questions
4
Used by people at amazing companies
Trust signals before you integrate
Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.
OpenAPI
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.
10,000
Free allowance
Start with 10,000 monthly credits and upgrade only when usage grows.
What this API helps you ship
Use this page as a production brief: endpoints, examples, response shape, and the workflow pieces needed to plug DomScan into your own product.
Embed domain checks, DNS intelligence, risk signals, or enrichment into onboarding, search, and internal tools.
Replace repeated manual lookups with scheduled jobs, alerting, and reproducible investigation steps.
Use predictable fields, documented status codes, and credit costs instead of scraping provider pages.
Feed agents, dashboards, SOAR playbooks, and CRMs through OpenAPI, SDK, Postman, or MCP.
Integration workflow
A simple path from first request to repeatable production usage.
Authenticate once
Send your API key with the documented header and keep requests consistent across services.
Query with examples
Start from the curl and HTTP samples, then map the parameters into your application code.
Operate and monitor
Use status codes, credit costs, and response fields to build retries, logs, and alerts.
Developer kit
Jump from this page into machine-readable docs, request collections, SDKs, or agent tooling.
OpenAPI schema
Generate clients or inspect every request and response shape.
Postman collectionImport ready-made requests for manual testing and team handoff.
SDKs and CLIUse maintained packages and command-line workflows instead of writing boilerplate.
MCP integrationExpose domain intelligence to AI agents and internal assistant workflows.
Parameters and response map
Scan the inputs, output fields, and status codes before wiring the endpoint into your client.
Parameter
ip
Example Response
ipdomaingeolocationgeolocation.countrygeolocation.country_namegeolocation.regiongeolocation.region_namegeolocation.citygeolocation.postalgeolocation.latitudegeolocation.longitudegeolocation.timezone
HTTP Status Codes
200400401402429504
Endpoints
GET
/v1/ip
ip
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
Geolocation
Provider-supplied city, region, country, postal code, and coordinates, which are approximate and may be incomplete.
ISP Information
View the Internet service provider reported for the IP.
Organization Lookup
View the provider-supplied organization associated with the network.
ASN Information
Inspect the reported Autonomous System Number and network details.
Hosting Context
Use provider data and IPv4-focused cloud-range enrichment to assess hosting or data-center context.
Scoped Security Signals
Review the provider's proxy flag, a curated Tor exit list, and coarse VPN-suspected ASN hints.
Timezone Lookup
View the timezone supplied for the approximate IP location when available.
Reverse DNS
For IPv4, inspect PTR and forward-confirmed reverse DNS (FCrDNS) results when available.
Example Request
curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/ip?ip=8.8.8.8"Example Response
{
"ip": "8.8.8.8",
"domain": null,
"geolocation": {
"country": "US",
"country_name": "United States",
"region": null,
"region_name": null,
"city": null,
"postal": null,
"latitude": null,
"longitude": null,
"timezone": null,
"precision": "country"
},
"network": {
"asn": 15169,
"asn_name": "AS15169",
"asn_org": "Google LLC",
"isp": "Google LLC",
"connection_type": "hosting"
},
"security": {
"is_proxy": false,
"is_vpn": false,
"is_tor": false,
"is_tor_exit": false,
"is_datacenter": true,
"is_cloud": true,
"cloud_provider": "Google Cloud",
"threat_score": 0,
"type_classification": {
"type": "datacenter",
"confidence": "high"
},
"fcrdns": {
"ptr": "dns.google",
"fcrdns_valid": true
}
},
"intelligence_summary": {
"query_type": "ip",
"domain_resolved": false,
"cache_status": "miss",
"data_source": "cloudflare-intel+enrichment",
"confidence": "high",
"confidence_score": 100,
"asn_present": true,
"organization_present": true,
"country_present": true,
"security_signal_count": 2,
"risk_flags": [
"cloud",
"datacenter"
],
"hosting_category": "cloud"
},
"meta": {
"query_time_ms": 118,
"cached": false,
"source": "cloudflare-intel+enrichment"
}
}Frequently Asked Questions
How accurate is geolocation?
IP geolocation is provider-supplied and approximate. Coverage and granularity vary by address and region, so it should not be used to identify a precise physical location or person.
Can I look up IPv6 addresses?
Yes. The primary provider may return basic IPv6 network and location data, but PTR/FCrDNS checks and cloud-range enrichment are currently focused on IPv4, so the result is not identical to an IPv4 lookup.
What security signals are included?
Results may include the primary provider's proxy flag, matches against a curated Tor exit list, and coarse hints for VPN-suspected ASNs. These signals do not use behavioral analysis and are not a comprehensive proxy or VPN verdict.
Is the data real-time?
Not necessarily. Primary provider data and DomScan enrichment can be cached for up to 24 hours, and upstream sources update on their own schedules. No fixed daily refresh cadence is guaranteed.
Related Tools & Resources
HTTP Status Codes
We document the HTTP status codes you should handle so you can distinguish successful responses, auth issues, credits, rate limits, missing data, and upstream failures.
OK
200
Request successful
Bad Request
400
Invalid parameters
Unauthorized
401
Missing or invalid API key/session.
Payment Required
402
Not enough credits to run this request.
Too Many Requests
429
Rate limit exceeded
Gateway Timeout
504
Upstream lookup timed out.
Look Up IP Address