Product support (<24h reply)
Bugs, unexpected results, questions about how a specific tool works. Use the contact form on this page or write to [email protected].
Contact DomainScan — support, feature requests, security disclosure and partnerships in one place.
Every message is read by a human. Use the form below for general inquiries, send security findings to [email protected] (PGP key in /.well-known/security.txt), or route partnership and press requests via /contact?topic=partnership. We typically respond within one business day, often faster.
01 · CHANNELS
Pick the right channel — get a faster reply
Four routes, each with a different SLA and a different team behind it:
API & developer support (Engineering)
Authentication, rate limits, response schemas, SDK integration help. Include code samples and request IDs — speeds triage dramatically.
Security disclosure (security@)
Vulnerabilities, account takeover, abuse, data exposure. Email [email protected] (encrypt with our PGP key for sensitive findings). Acknowledged within one business day.
Sales & partnerships (Business tier)
Custom enterprise pricing, dedicated capacity, MSA paperwork, integration partnerships, agency referrals, press inquiries — /contact?topic=partnership or [email protected].
02 · WHAT TO INCLUDE
How to write a message that gets resolved quickly
Most support roundtrips happen because the initial message is missing one critical detail. Cover these four things up front and we can usually close the loop in one reply:
- Exact endpoint and inputs Which tool or API endpoint, and the exact input(s) that produced the issue. For UI tools, include the URL bar contents.
- Request ID(s) For API issues, the requestId from the error payload. For UI issues, the time (with timezone) and which browser/device. We can usually find the trace from there.
- Expected vs actual What you expected, what actually happened. Even one screenshot or a JSON snippet helps massively — much faster than going back and forth in prose.
- What you've tried Saves us suggesting the obvious. If you've already tried with a different domain, different network, different account, or different browser — say so.
03 · COMMUNITY
Other ways to reach us
We're active in a few places outside of the inbox:
- Status page status.domainscan.in for live incidents, scheduled maintenance and historical uptime.
- Blog Engineering deep-dives, AI-readiness explainers and product updates at /blog.
- X / Twitter @domainscan_in for product launches and occasional shitposting about TLS misconfigurations.
- GitHub Open-source helpers, SDK examples and issue templates at github.com/domainscan.