Every domain you add is a new identity — a new colour in the margin and a new From you can be reached at. Start at /app/domains/new, type the domain, and you land on its setup page. That one screen offers the fastest path your DNS host allows — a one-click connect where the host supports it, a direct link into its DNS editor where it doesn't — and, underneath, every record as a copy-paste card with a live status.
§ The records
Publish the records the wizard prints at your registrar (Cloudflare, Route 53, Namecheap, whoever holds the zone). Names are written as suffixes; most registrars accept the leading @ or will append your apex automatically. New domains usually show seven records: four public mail records, one Amazon SES identity TXT, and two MAIL FROM records under mail. for Return-Path alignment.
The DMARC rua address points at dmarc-rua@<your-domain> — a receive-only mailbox Folio creates and manages for you on this domain. Aggregate reports land in your /app/deliverability view, not your inbox, and you don't create the alias yourself. No separate _report._dmarc authorization record is needed.
- ·MX tells the world that letters for your domain should arrive at our inbound server.
- ·SPF (that first TXT) declares which senders are allowed to write on your behalf.
- ·DKIM (the
_domainkeyTXT) publishes the public half of a signing key generated for this domain alone; outgoing letters are signed with the private half. - ·DMARC (the
_dmarcTXT) tells receivers what to do if a letter arrives unsigned — and sends aggregate reports to Folio for review. - ·SES identity (the
_amazonsesTXT) proves to Amazon SES that you control the domain. - ·MAIL FROM (the
mail.MX and SPF pair) aligns the outbound Return-Path with your domain instead of a shared carrier domain.
§ Verification
The setup page checks the records on its own while it is open and shows two milestones: Receiving turns green the moment the MX resolves (mail to the domain lands in Folio from then on), and Sending turns green when all seven records do. You do not need to wait on the page — background verification revisits pending domains and emails you when the domain is live. Most zones resolve in under ten minutes; Cloudflare, in our experience, is closer to two.
A domain can sit at pending for up to forty-eight hours without issue. Only at that point do we stop polling and ask you to check the records manually.
§ Sending enabled
Once the DNS, SES identity, and MAIL FROM gates are green, a final green badge appears on the domain: sending enabled. From that moment forward, any reply to a letter that arrived at *@studio.example will be sent from that domain, DKIM-signed in its own key.
If you only want to receive on a domain and never send, inbound routing can work before the outbound carrier gates finish. The UI keeps that distinction visible instead of pretending the domain is fully send-ready early.