Domains

Domain requests start with customer-facing availability checks and end with domain purchase authority.

Each purchase request must include one absolute https:// web redirect target. Message Science applies it to every purchased domain after the purchase completes.

Domain lifecycle

1. Add desired .com domains to a request.
2. Run availability checks for user feedback.
3. Re-check availability near purchase.
4. Purchase successful domains.
5. Configure verification DNS.
6. Verify and connect the domain.
7. Configure sending DNS, MX, and forwarding records.

Partial failures

If a domain cannot be purchased or verified, it remains visible as a partial failure. Successful domains continue through provisioning.

Replacement domains use the normal provisioning request path. Create a new request for the same customer, group, and batch, add the replacement .com domain, and point the skipped mailbox targets at that replacement domain. Purchase requests and execution remain disabled by default.

Admins can use the separate real-domain purchase bypass for Stripe sandbox verification only when the admin-only gate, purchase execution gate, sending setup, baseline DNS config, and redirect configuration are all explicitly enabled. Customers cannot bypass Stripe payment confirmation.