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.
Try a product, outcome, endpoint path, or API topic.
Security and Trust
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.
Convert punycode and Unicode domains and detect lookalike characters.
Choose this when: Choose this to convert a domain between Unicode and punycode and check each label for mixed scripts and lookalike characters. A low risk is a signal, not proof of safety.
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.
Inspect one public page for software and security-configuration signals, then compare supported versioned components with package advisories and exploitation data. Results show evidence and coverage for the checks completed; a clean result does not prove the application is vulnerability-free.
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.
Grade HSTS, CSP, frame protection and other HTTP security headers.
Choose this when: Choose this to grade the HTTP security headers and cookie flags a page sends. It reads response headers only and does not test for vulnerabilities.
Validate security.txt contacts, expiry and RFC 9116 fields.
Choose this when: Choose this to confirm a domain publishes a valid, unexpired security.txt with contacts for reporting vulnerabilities.
Grade a domain's security posture from A to F.
Choose this when: Choose this to grade a vendor's or your own domain security from A to F.
Find the privacy policy, terms, imprint, consent manager and trackers on a website.
Choose this when: Choose this to see a site's legal pages, consent manager and trackers.
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.
Learn moreMove from a reported indicator to connected public evidence without treating any single signal as proof.
Learn moreCombine current records, security-control evidence, resolver comparisons, certificates, and email authentication into an operational review.
Learn moreCombine input validation, public-domain context, social classification, company evidence, and website-declared relationships for risk-aware routing.
Learn moreCombine address-level signals with domain-level mail authentication, compliance, DNS, and blacklist evidence.
Learn moreStart with one domain or host, collect current resolution evidence, and pivot through observed relationships that matter to the investigation.
Learn moreChoose a focused security product or follow the threat-assessment workflow across related signals.