Live
Service status
Check live service health and documented failure responses before you integrate.
Category
Security & Email
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
domainlimit
Example Response
domainpermutations_generatedpermutations_checkedregistered_typosthreat_levelrisk_summaryrisk_summary.criticalrisk_summary.highrisk_summary.mediumrisk_summary.low
HTTP Status Codes
200400401402429
Endpoints
GET
/v1/typos
domainlimit
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
Typo Detection
Find common typing mistakes like missing/swapped letters.
Homoglyph Analysis
Detect lookalike character attacks (rn→m, l→I, 0→O).
Letter Repetition
Catch domains with doubled letters (gooogle, amazzon).
Adjacent Keys
Detect keyboard proximity typos (foogle, hoogle).
Risk Scoring
Critical, high, medium, and low risk classifications.
Registration Status
Check which typo domains are actually registered.
Threat Summary
Get an overall threat level and risk breakdown.
Permutation Types
Omission, addition, replacement, transposition, and more.
Example Request
curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/typos?domain=google.com&limit=50"Example Response
{
"domain": "google.com",
"permutations_generated": 50,
"permutations_checked": 50,
"registered_typos": [
{
"domain": "gooogle.com",
"type": "repetition",
"description": "Letter repetition: o → oo",
"risk": "high",
"registered": true
},
{
"domain": "googIe.com",
"type": "homoglyph",
"description": "Lookalike character: l → I",
"risk": "critical",
"registered": true
},
{
"domain": "gogle.com",
"type": "omission",
"description": "Missing letter: o",
"risk": "high",
"registered": true
}
],
"threat_level": "critical",
"risk_summary": {
"critical": 2,
"high": 8,
"medium": 15,
"low": 12
}
}Frequently Asked Questions
What is typosquatting?
Typosquatting is when someone registers domains that are misspellings or visual lookalikes of popular brands. These are often used for phishing, ad fraud, or brand impersonation attacks.
What types of typo variations do you detect?
We detect: character omission (gogle), addition (googgle), substitution (goggle), transposition (googel), adjacent key errors (foogle), homoglyphs (googIe with capital I), and bitflip domains.
How are risk levels determined?
Critical: homoglyphs and highly deceptive typos. High: common misspellings likely to catch users. Medium: less common errors. Low: unlikely typos but still worth monitoring.
Can I use this for brand monitoring?
Absolutely! Run regular typosquatting scans to detect new registrations that might be targeting your brand. Take action on critical and high-risk domains.
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
Scan for Typosquatting Threats