For developers, trust teams, growth operations, and researchers
Use the suite to improve form handling, prioritize manual review, enrich organizations, and connect website-declared assets.
Identity and Verification
Assess digital identity inputs without turning signals into proof
Normalize submitted identifiers, inspect relevant public evidence, and preserve uncertainty for risk, routing, and enrichment decisions.
Verify the input, then enrich only what the workflow needs
Begin with the submitted email, phone, domain, company, or social identifier and request additional relationship evidence only when it affects the decision.
Inputs
UsernameEmail addressPhone numberDomainCompanyURL
Outcomes
VerifyDiscoverAssessEnrichCollect
Validation, risk, enrichment, and legal identity are different
Choose a focused validator for input quality, Company Lookup for organization context, and identity products for public website-declared relationships. None provides KYC.
Social Handle Availability
Check if a username is available across major social media platforms.
Choose this when: Choose this to classify supported public profiles or resources. Blocked, rate-limited, timeout, or ambiguous checks remain unknown and never prove claimability.
- Inputs
- Username
- Outcomes
- Verify, Discover
- Credits
- 0-2
SynchronousBulkRESTMCPSDKInteractive tool
Email Verification
Assess email syntax, domain mail setup, disposable-address signals, and delivery risk without claiming mailbox existence.
Choose this when: Choose this for syntax, domain mail setup, disposable-address, risk, and limitation signals. It does not prove mailbox existence.
- Inputs
- Email address
- Outcomes
- Verify, Assess
- Credits
- 2
SynchronousBulkRESTMCPSDKInteractive tool
Phone Number Intelligence
Parse, validate, classify, and format global phone numbers, then add offline location, time zone, original prefix carrier, dialing, short-code, and regulator allocation context when available.
Choose this when: Choose this to parse, format, and assess public numbering and line-type signals. It does not prove reachability, ownership, or user identity.
- Inputs
- Phone number
- Outcomes
- Verify, Enrich
- Credits
- 1
SynchronousBulkRESTMCPSDKInteractive tool
Company Lookup
Look up company information associated with a domain.
Choose this when: Choose this to enrich an organization from its domain or company identifier using available public business and website evidence.
- Inputs
- Domain, Company
- Outcomes
- Enrich, Verify
- Credits
- 3
SynchronousRESTMCPSDKInteractive tool
Website Identity Assets
Extract source-backed logos, favicons, preview assets, theme colors, and declared profiles from public websites.
Choose this when: Choose this to collect public identity assets declared by a website, such as icons, profiles, and organization-oriented links.
- Inputs
- Domain, URL, Company
- Outcomes
- Collect, Enrich, Verify
- Credits
- 2
SynchronousBulkRESTMCPSDK
Internet Identity Resolution
Resolve a company domain into public identities explicitly declared by its website.
Choose this when: Choose this to connect website-declared identity signals into an evidence graph, not to establish legal or private-person identity.
- Inputs
- Domain, Company
- Outcomes
- Discover, Enrich, Verify
- Credits
- 2
SynchronousBulkRESTMCPSDK
Workflows
Validate the email and phone inputs, preserve unknown outcomes, and send high-risk or conflicting signals to review.
Signup risk and routing
Validate the email and phone inputs, preserve unknown outcomes, and send high-risk or conflicting signals to review.
Website to company context
Start from a company domain, request company context, then collect declared identity assets and relationships that support the research task.
Assess a business contact without claiming identity
Submit an email and phone number, then enrich the company domain when the form or research workflow requires organization context.
Example Request
curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/company?domain=stripe.com"Example Response
{
"domain": "stripe.com",
"company": {
"name": "Stripe",
"industry": "Financial technology"
},
"confidence": 0.92
}Single checks and bounded bulk validation
Validate one identifier synchronously. Email and phone bulk endpoints accept up to 100 items, while Social Handle Check accepts up to 10 handles per bulk request.
SynchronousBulkRESTMCPSDKInteractive tool
Digital signals are not identity proof
Public website and network evidence can support a workflow, but it cannot establish ownership, legal identity, consent, or mailbox existence.
Related solutions
Investigate whether a suspicious domain is presenting as your brand
Move from a reported indicator to connected public evidence without treating any single signal as proof.
Build a repeatable public evidence record for competitor domains
Collect public pages and connect them with domain, company, technology, DNS, and infrastructure context.
Give agents current web context with explicit boundaries
Let an agent collect a page, understand the domain behind it, and request deeper evidence only when the task requires it.
Enrich a company record from its public website and domain
Combine collected page evidence with company, category, technology, domain, and website-declared identity signals.
Assess whether digital identity inputs are consistent enough for the next step
Combine input validation, public-domain context, social classification, company evidence, and website-declared relationships for risk-aware routing.
Assess email risk and sending-domain posture before you act
Combine address-level signals with domain-level mail authentication, compliance, DNS, and blacklist evidence.
Use the signal that matches the decision
Start with an email, phone, company, or social check, then add public relationship evidence only when needed.