Where this lives. Sign in and open /domains in the app.
What it does
The Domains page is the command center for every sending domain in your workspace. It lists domains with their DNS status, connected mailboxes, warmup state, reputation, and any tags, and lets you filter by workspace, freshness, DNS state, and more using quick view chips like DNS action, DNS in progress, DNS verified, Ready for warmup, and Blocked.
Each domain also has its own DNS zone console at /domains/<id>/dns, where individual records live: what the platform intends to publish, what the registrar holds, and what public DNS currently answers. Records mail authentication depends on (SPF, DKIM, DMARC, MX) are marked so an edit that could break delivery asks you to confirm first.
Buying a brand new domain is not done from this page. The Buy / check domains button in the header takes you to Domain & Inbox Forge, which handles purchasing and setting up inboxes. This page is for domains you already have, whether bought elsewhere or through Forge earlier.
Before you start
- To import domains from a registrar account, that registrar must already be connected to your workspace. If the connected account holds no domains, the app tells you to buy one from Domain & Inbox Forge or connect the registrar that actually holds your portfolio.
- To add a domain held at a registrar the platform has no API connection to (GoDaddy, Namecheap, Cloudflare, or anywhere else), you only need to already own it. Adding it here changes nothing at that registrar.
- To write DNS records from the zone console, your workspace needs a registrar connected with DNS write access under Settings → Integrations. Without one, records can be listed but not changed here.
Set it up, step by step
- On the Domains page, click Import owned domains to pull domains from a registrar account already connected to your workspace. A drawer titled "Import domains you already own" opens and reads your registrar account live.
- Filter the list with the Filter… box if needed, then use Select all or check individual domains, and click Import N domains. Importing is free and does not change anything at the registrar; it just brings the domain under management here.
- To add a domain from a registrar the platform cannot connect to directly, click Add domain from another registrar. In the "Add a domain you own elsewhere" drawer, paste one domain per line (or comma-separated; URLs and email addresses are accepted and the domain is pulled out of them) and click Add N domains.
- Open a domain and go to its DNS console at
/domains/<id>/dns. Click Add record, choose the record Type, fill in Name (use@for the root), Value, TTL, an optional Priority, and a Purpose, then click Add. - To change a record, click Edit on its row, adjust the fields, and click Save. To remove one, click Delete.
- If the record you are adding, editing, or deleting is marked auth (an authentication record), the app stops and asks you to confirm, for example "Change TXT @?" or "Add MX @?", explaining that this is one of the records receivers check before accepting mail from the domain. Click Change it / Add it (or Delete in the delete dialog) to proceed, or close the dialog to back out.
- Click Check live DNS at any time to re-query public DNS for every record on the domain and compare it against what is intended.
What you should see
After importing or adding, the domain appears in the main Domains list with its DNS, users, and readiness columns starting at their initial state. On the zone console, each record row shows a Live DNS status pill: live (public DNS matches what is intended), differs (public DNS returned a different value, shown underneath the row), missing (public DNS returned nothing), or not checked. After clicking Add record, Save, or Delete, a toast confirms the write and reminds you that DNS takes a few minutes to propagate. Check live DNS shows a toast such as "Checked 6 record(s): 4 live, 2 not matching."
Records that exist at the registrar but were not created through this console show up in a separate table lower on the page, labeled "At the registrar but not tracked here", so you can see what someone added outside the app.
Common problems
- "This workspace is on a sandbox registrar": records can be planned but nothing publishes to real DNS. Connect a live registrar under Settings → Integrations.
- "No registrar with DNS write access is connected": records are read-only here. Either connect a registrar, or edit at the registrar directly and click Check live DNS to pick it up.
- "The registrar did not answer": the registrar API failed to respond, but the live DNS data shown is still accurate since it comes from a direct DNS query, not the registrar.
- Deleting an auth record: the confirmation dialog warns that it "stops delivery from this domain until it is put back." Only proceed if you mean to.
- "Removed here, but the registrar said: ...": the record was deleted from the app's records but the registrar rejected the actual deletion. Check the registrar directly.
- Importing from an empty registrar account: buy a domain through Domain & Inbox Forge, or connect a different registrar account.
Related
Common questions
How many domains do I need for cold email?
Divide your daily target by sixteen to twenty, which is what one domain carries at two mailboxes sending eight to ten each. A thousand a day needs about fifty domains. Buy a few more than the arithmetic says, because you will retire some.
Can I send cold email from my main company domain?
No. Reputation damage does not stay in one place. The same domain carries your invoices, password resets and support replies, and none of those can afford a spam folder.
Why does my SPF record fail when it looks correct?
Two causes cover almost all of it. Two SPF records on the same host is an automatic permanent error, and each record looks valid on its own. An include chain past ten DNS lookups is the same error by a slower route. Check with a public resolver, not the registrar dashboard.
How long does DNS propagation take?
Minutes to hours. Treat a record as unverified until a resolver outside your own account returns it, which is exactly what the verification step here does.
Read next
Last updated September 19, 2026. Written by the team that operates the platform.