Architecture, launch or migration
Share your customer-domain volume, current HTTPS destination and the experience you want customers to have.
hello@subdomain.to →One direct route for each request
Tell us what you need to route.
There is no decorative contact form in front of these inboxes. Choose the subject that matches your request and write to the team directly.
For account-specific support, include the organization and domain ID—not an API key or webhook secret.
Send the request to the right place.
Separate product, operational, security and privacy conversations so the first response can start with the relevant context.
An account or customer domain needs attention
Include the domain ID, current lifecycle status, timestamp and request ID where available.
support@subdomain.to →Responsible disclosure or control question
Describe the affected surface and reproduction steps. Do not send active credentials by email.
security@subdomain.to →Data or privacy request
Use a dedicated subject so the request is identifiable without adding sensitive data to the first message.
legal@subdomain.to →A useful first message is reproducible.
Small pieces of technical context remove a full round trip without requiring you to share secrets.
What are you trying to ship?
New integration, customer onboarding, migration, domain incident or billing question.
Which object is involved?
Organization, HTTPS destination ID, domain ID or webhook delivery ID. Never the secret value.
What did the system return?
HTTP status, API error code, request ID and the separate DNS, certificate and routing statuses.
You may not need to wait
Use the source closest to the problem.
Setup and contract questions are often answered faster by the quickstart or API reference. Account-specific incidents belong with support, while security details have their own documented boundary.
Quickstart and API reference
Create an HTTPS destination and customer domain, then render the returned DNS instructions.
Read the quickstart ↗Security and support
Route an account incident to support or review the controls enforced before traffic reaches an origin.
Email support ↗Review security →