Domains
Verify custom domains and assign their receiving destinations.
List custom domains
Hosted test addresses are excluded. Returns DNS instructions, readiness and the custom-domain allowance.
Create a custom domain
The authenticated account can create a domain. Domain names normalize to DNS form. Domains reserved for Wildmail service use cannot be added. Configure returned TXT and MX records before verification.
Delete custom domain
Signed-in browser session or a scoped API key. Removes a custom domain and refreshes admission routing.
Set domain destination
Requires endpointId. Set null or an empty string to disconnect. Hosted addresses use /api/hosted-address. Newly accepted messages use the selected destination, while previously accepted messages keep the destination recorded at acceptance.
List exact-address routes for a custom domain
Lists this domain's exact local-part routes and the account-wide route allowance. UTF-8 local parts are trimmed, Unicode-normalized, and lowercased before matching. Unicode domains use lowercase IDNA ASCII for lookup. Matching is case-insensitive. Plus-tags are preserved literally and are not stripped. Exact matches take precedence over the domain catch-all. A matching exact route can accept mail without a catch-all endpoint. Unmatched addresses are rejected if no catch-all is configured. A suspended exact route or one whose endpoint is unavailable is rejected during SMTP admission instead of falling through to catch-all.
Create an exact-address route
Creates an exact local-part route to an endpoint in this account. UTF-8 local parts are trimmed, Unicode-normalized, and lowercased before matching. The maximum is 64 UTF-8 bytes. Free has an allowance of zero and returns 409 route_limit_reached. Recognized non-Free plans have unlimited exact routes. Route status is suspended while the effective plan disallows routes. Stored suspended routes remain counted. Hosted test addresses are managed separately.
Delete an exact-address route
Removes the exact route so future mail to that address uses the domain catch-all, if configured. Unmatched addresses are rejected when no catch-all is configured. Previously accepted messages retain their pinned route and endpoint revisions.
Update an exact-address route
Replaces the route's local part and endpoint for future accepted mail. UTF-8 local parts (at most 64 UTF-8 bytes) are trimmed, Unicode-normalized, and lowercased before matching. Plus-tags are preserved literally and are not stripped. Previously accepted messages retain their pinned route and endpoint revisions.
Check domain DNS
No body. Checks ownership TXT and MX separately with an eight-second DNS timeout. A 200 response may have observed.ownership or observed.mx false. domain.ready reports domain catch-all readiness. With no catch-all, a verified domain with valid MX can still accept matching active exact-address routes with active endpoints.