When should I contact Domain Atlas?
Contact Domain Atlas when you need usage-based Enterprise pricing, higher-volume API usage, security review, privacy support, or help importing a proprietary domain dataset.
Talk to the team behind Domain Atlas.
Start with a free account. Write to us when you need volume pricing, a security review, or help importing your own domain dataset.
- Discuss usage-based Enterprise pricing, higher-volume API usage, custom rate limits, SLAs, and team workflows.
- Route security review, procurement questions, and vulnerability reports through a dedicated contact path.
- Tell us which coming capabilities matter to you, or ask about importing your own domain dataset.
- Access model: Session access for the console, hashed customer API keys for data endpoints, and revocation from the key workspace. Route: Security review.
- Operational controls: Request IDs on every response, rate-limit responses with retry hints, uncached account responses, browser security headers, and health endpoints that report status without exposing secrets. Route: Sales and support.
- Data lineage: Visible endpoint, field path, source family, cache state, and coverage status for domain profile sections. Route: Sales and support.
- Data handling: Internal credentials stay server-side, customer keys are shown once, and lookup activity is described in the privacy model. Route: Privacy and data.
Questions
What should I include in a platform access request?
Include the domains or workflow you want to operationalize, expected lookup volume, API needs, team controls, and any coverage requirements.
Can security teams review Domain Atlas before rollout?
Yes. Security and procurement teams can review API access, session controls, browser boundaries, customer API keys, and source coverage behavior before rollout.