Enter a domain, URL, IP, email, or record and get a focused result without setup.
Detect hosting provider, CDN, WAF, DNS provider, and email infrastructure for any domain.
GET /v1/hosting?domain=example.com
Use the browser tool for a fast answer, then move the same logic into scripts, monitoring, or product flows when it becomes repeatable.
Enter a domain, URL, IP, email, or record and get a focused result without setup.
Outputs highlight statuses, risks, records, and next actions instead of raw provider noise.
Use the request and response examples to turn a one-off check into an API call or recipe.
Used by people at amazing companies
Each page is shaped around a practical operational question, not just a raw lookup.
See the current DNS, registration, security, pricing, or reputation evidence.
Compare the result with related checks so the next move is easier to trust.
Copy examples, open linked tools, or move into API documentation when you need scale.
Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.
OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.
Authenticated endpoints use API keys with clear credit costs before you call them.
Start with 10,000 monthly credits and upgrade only when usage grows.
Start from the curl and HTTP samples, then map the parameters into your application code.
Identify the origin platform serving the website.
See whether a CDN or web application firewall is in front of the site.
Surface the providers handling nameservers and mail services.
GET /v1/hosting?domain=example.com
{
"domain": "example.com",
"hosting": { "provider": "Vercel", "confidence": 0.96 },
"cdn": { "detected": true, "provider": "Cloudflare", "confidence": 0.82 },
"dns_provider": { "provider": "Azure DNS" }
}
The browser experience previews DomScan's structured endpoints, so teams can validate a use case before writing code.
We combine DNS records, HTTP response headers, and known infrastructure fingerprints to identify hosting, CDN, WAF, DNS, and email providers.
Yes. A site can be hosted on one platform, protected by another CDN or WAF, and use a separate DNS or email provider.
Some setups hide infrastructure details or use generic responses, so the detector may only return partial signals.