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
domain
Example Response
domainorganization_nameassetsassets.logo_urlassets.favicon_urlassets.theme_colorassets.candidatesconfidenceevidence
HTTP Status Codes
200400401402429500502503504
Endpoints
GET
/v1/identity-assets
POST
/v1/identity-assets/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
Source-Backed Logo Discovery
Find logo candidates declared through structured data and public website metadata.
Favicons and App Icons
Extract favicons, Apple touch icons, mask icons, and web manifest references.
Preview and Theme Assets
Return Open Graph preview images and declared theme colors alongside identity assets.
Asset Provenance
Each candidate identifies the source, asset kind, MIME type, and declared size when available.
Declared Social Profiles
Include normalized public profiles linked by the website, with source and confidence.
Bulk Brand Asset Lookup
Process up to 10 domains in one request with ordered results and per-item errors.
Example Request
curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/identity-assets?domain=example.com"curl -X POST -H "X-API-Key: $DOMSCAN_API_KEY" -H "Content-Type: application/json" \
-d '{"domains":["example.com","github.com"]}' https://domscan.net/v1/identity-assets/bulkExample Response
{
"domain": "example.com",
"organization_name": "Example",
"assets": {
"logo_url": "https://example.com/logo.svg",
"favicon_url": "https://example.com/favicon.ico",
"theme_color": "#111827",
"candidates": []
},
"confidence": 0.8,
"evidence": ["organization_name", "structured_logo", "declared_icon"]
}Frequently Asked Questions
How does DomScan choose a company logo?
DomScan prioritizes logos explicitly declared in Organization structured data and keeps other website icons and preview images as separate candidates.
What is the difference between a logo and a favicon?
A logo represents the organization, while a favicon is a small website icon. The API reports them separately so your application can choose the right asset.
Does the API host or transform the returned images?
No. The API returns the original public asset URLs and their provenance. Your application remains responsible for permitted use, caching, and presentation.
What happens when a website has no usable logo?
The logo field remains null. Other declared icons or preview images can still appear as separate candidates without being mislabeled as logos.
Can I fetch company logos in bulk?
Yes. Send up to 10 domains to the bulk endpoint. Results preserve input order and individual failures do not hide successful items.
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 Website Identity Data