Adjacent domains
Dedicated, brand-relevant domains isolate outreach reputation from the primary brand domain while remaining recognizable to recipients.
Live intake · self-serve provisioning
Bring the domain. Keep the risk visible.
Coldrig's BYO (bring-your-own) domain intake is live in the API and MCP surface — you can register a domain, run the pre-flight scan, and track consent today. Real DNS delegation and platform-provisioned mailboxes on your own domain are self-serve and automatic once you've gone live; mailbox send-authorization still completes on our side. Registering a domain does not itself provision anything real until your account has gone live.
Domain choices
Not all “bring your own” paths are equal.
Domain reputation has consequences outside a campaign. Coldrig's intended production flow makes that tradeoff explicit before any DNS or sender action.
Delegated subdomain
A customer-controlled sending subdomain can simplify ownership and DNS boundaries — but when a sending domain burns, and 8–18% a month do, you retire it and replace it, and you can’t throw away a subdomain of the domain your business runs on. Subdomains exist for splitting legitimate streams (transactional vs marketing vs corporate) where you want the parent reputation to carry over — the exact property that inverts for cold outreach.
Primary domain
Using the main website and employee-email domain concentrates reputation risk. It should require explicit, informed owner consent—not agent inference.
Before activation
The owner should be able to answer these.
- Who owns and can edit DNS?The account must not depend on credentials the owner cannot recover.
- What business traffic shares this reputation?Website, transactional, support, and employee mail change the risk calculation.
- What happens when the service ends?DNS ownership stays with the customer; mailbox and vendor portability must be confirmed before activation.
- Has the primary-domain risk been accepted explicitly?Silence, a prompt, or an agent default is not informed consent.
Honest implementation status
Live intake, self-serve provisioning.
Domain registration, DNS/setup checks at intake, and consent tracking are live, reachable tools in the API and MCP surface today (get_byo_domains, configure_byo_domain) — this is not a design document. Once you've gone live (self-serve: call POST /checkout for a hosted Stripe payment link and pay), actual DNS delegation and platform-provisioned mailboxes on your own domain are automatic — the only remaining step is mailbox send-authorization completing on our side. Live reputation/blocklist monitoring against your domain is on the roadmap, not running yet — don't rely on it today. A burned BYO domain hard-pauses and is never auto-replaced, unlike a burned lookalike domain, because it's your business's domain, not a disposable one. There is no published pricing yet for BYO-connected mailboxes specifically. Use the sandbox to validate workflow behavior, or go live to start a real intake.