Enter a domain, URL, IP, email, or record and get a focused result without setup.
Phishing Investigation
Investigate suspected phishing domains with an evidence package. It collects DNS records, WHOIS data, and SSL certificates, and creates a timestamped report for takedown requests.
What's included
Run the check, then ship the workflow
Use the browser tool for a fast answer, then move the same logic into scripts, monitoring, or product flows when it becomes repeatable.
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 these companies
What this tool helps you decide
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.
Trust signals before you integrate
Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.
Check live service health and documented failure responses before you integrate.
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.
Example request
curl -s "https://domscan.net/v1/recipes/phishing-investigation?suspicious_domain=examp1e.com" -H "X-API-Key: $DOMSCAN_API_KEY"
Example response
{
"success": true,
"data": {
"risk_level": "high",
"evidence": [
"recent registration",
"mismatched hosting",
"suspicious typosquatting"
],
"registrant": "privacy protected"
},
"meta": {
"recipe_name": "phishing-investigation",
"credits_used": 12,
"credits_saved": 10,
"duration_ms": 952
},
"errors": []
}
Built on the same API
The browser experience previews DomScan's structured endpoints, so teams can validate a use case before writing code.
Results
Frequently asked questions
Yes, the report is designed to provide evidence for abuse reports to registrars, hosting providers, and brand protection services.
Not always. Because of GDPR, many registrations are now privacy-protected. We collect whatever public information RDAP provides.
Phishing sites are often short-lived. Run this investigation immediately upon discovery and submit takedown requests as soon as possible.
Need more from DomScan?
Get API access for automation, higher limits, and custom integrations.

