99.99%
Uptime
Production-ready endpoints are designed for 99.99% uptime and documented status handling.
Category
Web Intelligence
Endpoints
3
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
urldomain
Example Response
urltechnologiessummarysummary.cdnsummary.frameworksummary.analyticsheadersheaders.serverheaders.x-nextjs-cachesslssl.enabledtotal_time_ms
HTTP Status Codes
200400402429500502503504
Endpoints
GET
/v1/tech
url
GET
/v1/hosting
domain
GET
/v1/parking
domain
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
CDN Detection
Identify Cloudflare, Fastly, AWS CloudFront, Akamai, and more.
Framework Detection
Detect Next.js, React, Vue, Angular, Svelte, and others.
CMS Detection
Identify WordPress, Shopify, Wix, Squarespace, Webflow, etc.
Analytics Tracking
Find Google Analytics, GTM, Mixpanel, Segment, and more.
Server Software
Detect nginx, Apache, IIS, LiteSpeed web servers.
Confidence Levels
Know how confident each detection is (high/medium/low).
Header Analysis
Raw HTTP headers included in response.
Security Research
Useful for vulnerability assessment and competitive analysis.
Example Request
curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/tech?url=https://example.com"Example Response
{
"url": "https://example.com",
"technologies": [
{"name": "Cloudflare", "category": "cdn", "confidence": "high", "evidence": "Header: server"},
{"name": "Next.js", "category": "framework", "confidence": "high", "evidence": "Header: x-nextjs-cache"},
{"name": "Google Analytics", "category": "analytics", "confidence": "medium", "evidence": "HTML content"}
],
"summary": {
"cdn": "Cloudflare",
"framework": "Next.js",
"analytics": ["Google Analytics"]
},
"headers": {
"server": "cloudflare",
"x-nextjs-cache": "HIT"
},
"ssl": {"enabled": true},
"total_time_ms": 523,
"_meta": {"analysis_status": "ok", "response_status": 200}
}Frequently Asked Questions
How accurate is the detection?
Detection accuracy depends on the technology. Header-based detections are highly accurate. HTML-based detections may have false positives if sites use similar patterns.
What technologies can you detect?
We detect CDNs, web servers, JavaScript frameworks, CMS platforms, analytics tools, fonts, security tools, and common JavaScript libraries.
Do you fetch the full page?
Yes, we make a GET request to fetch the page HTML for analysis. Some technologies can only be detected by examining the page content.
Can I use this for competitive analysis?
Yes, this API is commonly used to understand what technologies competitors use, identify market trends, and inform technology decisions.
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.
Detect Website Technologies