99.99%
Uptime
Production-ready endpoints are designed for 99.99% uptime and documented status handling.
Category
OSINT
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
200400402429500502503504
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.
Uptime
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
City, region, country, postal code, and coordinates.
ISP Detection
Identify the Internet Service Provider.
Organization Lookup
Find the company or organization owning the IP.
ASN Information
Autonomous System Number for network analysis.
Hosting Detection
Detect if IP belongs to a hosting provider or data center.
Proxy Detection
Identify VPN, proxy, or Tor exit nodes.
Timezone Lookup
Determine the timezone for the IP location.
Reverse DNS
Get the hostname associated with the IP address.
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": "CA",
"region_name": "California",
"city": "Mountain View",
"postal": "94035",
"latitude": 37.386,
"longitude": -122.0838,
"timezone": "America/Los_Angeles"
},
"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": "ip-api.com+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": "ip-api.com+enrichment"
}
}Frequently Asked Questions
How accurate is geolocation?
Country-level accuracy is typically 95-99%. City-level accuracy varies by region but is generally 70-85%. IP geolocation should be used for approximate location, not precise positioning.
Can I look up IPv6 addresses?
Yes, we support both IPv4 and IPv6 address lookups with the same comprehensive data.
How do you detect proxies?
We maintain databases of known VPN providers, proxy services, and Tor exit nodes. Detection is based on IP range matching and behavioral analysis.
Is the data real-time?
Geolocation and organization data is updated daily. Proxy/VPN databases are updated multiple times per day.
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
Payment Required
402
Not enough credits to run this request.
Too Many Requests
429
Rate limit exceeded
Server Error
500
Internal error
Bad Gateway
502
Upstream RDAP error
Service Unavailable
503
Upstream service unavailable or temporarily rate limited.
Gateway Timeout
504
Upstream lookup timed out.
Look Up IP Address