Live
Service status
Check live service health and documented failure responses before you integrate.
Category
Web Intelligence
Endpoints
2
Key Features
6
Frequently Asked Questions
5
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
url
Example Response
requested_urlfinal_urlstatustitlecanonical_urlopen_graphstructured_datastructured_data.typesstructured_data.itemsstructured_data.parse_errorsmetameta.cached
HTTP Status Codes
200400401402429500502503504
Endpoints
GET
/v1/url-intelligence
POST
/v1/url-intelligence/bulk
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
Normalized Page Metadata
Extract title, description, language, content type, final URL, and canonical URL.
Link Preview Fields
Build preview cards from normalized images, favicons, Open Graph tags, and Twitter Cards.
Structured Data Summary
Identify JSON-LD types and report malformed blocks without returning unbounded page data.
Robots and Security Signals
Read indexability directives and an allow-listed set of public security headers.
Contacts and Public Profiles
Extract declared email, telephone, social, developer, and creator links.
Bulk URL Metadata
Inspect up to 10 URLs per request with bounded concurrency and per-item errors.
Example Request
curl -G -H "X-API-Key: $DOMSCAN_API_KEY" --data-urlencode "url=https://example.com" https://domscan.net/v1/url-intelligencecurl -X POST -H "X-API-Key: $DOMSCAN_API_KEY" -H "Content-Type: application/json" \
-d '{"urls":["https://example.com","https://github.com/about"]}' https://domscan.net/v1/url-intelligence/bulkExample Response
{
"requested_url": "https://example.com/",
"final_url": "https://example.com/",
"status": 200,
"title": "Example Domain",
"canonical_url": "https://example.com/",
"open_graph": {},
"structured_data": { "types": [], "items": 0, "parse_errors": 0 },
"meta": { "cached": false, "fetch_transport": "worker" }
}Frequently Asked Questions
What is the difference between a URL metadata API and an Open Graph API?
An Open Graph API focuses on social tags. DomScan also returns canonical, redirect, robots, structured-data, security, contact, and identity signals.
What happens when Open Graph tags are missing?
Open Graph fields remain empty while standard title, description, icons, structured data, and other available signals are still returned.
Does the API execute JavaScript?
No. The initial version inspects bounded public HTML responses and does not claim metadata that only appears after client-side JavaScript runs.
Does the API follow redirects safely?
Yes. Redirects are bounded and every destination is checked to prevent access to private or internal network targets.
Can I inspect several URLs at once?
Yes. The bulk endpoint accepts up to 10 public URLs and preserves their input order.
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
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.
Build with URL Intelligence