For security, trust, abuse, and brand-protection teams
Use bounded passive checks to enrich triage and investigation, not to replace authorized testing or human review.
Find suspicious naming patterns, inspect trust and email controls, and prioritize evidence without treating a clean check as proof of safety.
Use bounded passive checks to enrich triage and investigation, not to replace authorized testing or human review.
Generate or compare suspicious names, establish whether they are registered, then inspect certificate, reputation, email, and website evidence.
Use similarity and typosquatting for names, certificate and reputation products for trust context, email products for mail posture, and vulnerability intelligence for passive public-response findings.
Find domains similar to a given domain based on name patterns and keywords.
Choose this when: Choose this for name, text, keyboard, and homoglyph similarity. It does not compare website meaning or visual design.
Detect typosquatting threats and similar domains that could be used for phishing or brand abuse.
Choose this when: Choose this to generate likely lookalike variants and check their domain status without treating unknown as safe.
Get SSL certificate information including issuer, validity, and security grade.
Choose this when: Choose this to inspect public TLS certificate evidence, validity, names, and chain-related signals where available.
Find exposed software, risky configurations, and known affected versions across a public website. Every result explains what was checked, why it matched, and how strong the evidence is.
Choose this when: Choose this for passive exposed-version and configuration evidence. It does not exploit the target or prove the site is vulnerability-free.
Check domain reputation across multiple threat intelligence sources.
Choose this when: Choose this for a combined reputation view with evidence, coverage, and unknown results kept visible.
Analyze email authentication records including SPF, DKIM, and DMARC.
Choose this when: Choose this to inspect SPF, DKIM, DMARC, and related email-authentication posture for a domain.
Analyze email authentication records including SPF, DKIM, and DMARC.
Choose this when: Choose this for a policy-oriented review of public email controls and published compliance signals.
Check if a domain or IP is listed on email blacklists.
Choose this when: Choose this to check supported blacklist evidence at a point in time. A clean result is not a universal reputation guarantee.
Start from the reported domain, compare it with the protected name, then add registration, DNS, certificate, reputation, and website evidence.
Start from the reported domain, compare it with the protected name, then add registration, DNS, certificate, reputation, and website evidence.
Detect exposed technologies, correlate exact versions with public advisories, and keep partial or unavailable checks explicit.
Compare a suspicious domain with the protected name, check its registration status, then request trust evidence for registered findings.
curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/reputation?domain=example.com"
{
"domain": "example.com",
"reputation_score": 92,
"grade": "A",
"risk_level": "low",
"recommendations": []
}
Call individual products for known indicators, batch supported GET requests, or use a documented recipe when the investigation spans several suites.
Findings reflect completed public checks. Blocked, incomplete, unsupported, and inconclusive evidence remains unknown.
Combine similarity, typosquatting generation, domain status, trust evidence, and monitoring into a repeatable review path.
Move from a reported indicator to connected public evidence without treating any single signal as proof.
Combine current records, security-control evidence, resolver comparisons, certificates, and email authentication into an operational review.
Combine input validation, public-domain context, social classification, company evidence, and website-declared relationships for risk-aware routing.
Combine address-level signals with domain-level mail authentication, compliance, DNS, and blacklist evidence.
Start with one domain or host, collect current resolution evidence, and pivot through observed relationships that matter to the investigation.
Choose a focused security product or follow the threat-assessment workflow across related signals.