Domains
Send from an identity your customers recognize and your business controls. Add a domain such as mail.example.com, publish the supplied DNS records and complete verification before using it for a campaign, template or workflow email.
Until a domain is verified, nothing sends from it. Broadcasts and template sends refuse with "domain not verified", and so do test sends from the editor: a test goes out through your own verified domain and picked sender, exactly like a real send. Verify a domain before you plan to preview anything in a real inbox.
Domains live in Settings, then Domains under Workspace settings. The page is called Sending Domains.
Add your sending domain
Add the domain
Click Add domain and type the name. maxclicks checks it as you type and tells you if it has already been added. The name cannot be changed afterwards, so if you want to send from a subdomain (and you usually do, see subdomains vs root domains) decide that now.
Copy the DNS records into your registrar
Verification opens straight after you add the domain, showing every record you need. Each Name and Value has a copy button next to it. Paste them into your DNS provider exactly as shown.
Start the check
Click Start verification check. maxclicks then keeps checking on its own through the day and flips the domain to verified as soon as your records resolve. DNS caches and provider checks can delay verification. A Pending result immediately after a change is not proof the record is wrong; compare the exact record names and values, then check again after the provider has published them.
The records you add
maxclicks generates all of them at once. You get one or more DKIM records, plus SPF, bounce handling and DMARC.
| Type | What it is for |
|---|---|
CNAME (one or more, on a _domainkey name) | DKIM. Signs your mail so mailbox providers can prove it really came from you. |
TXT on the return-path subdomain | SPF. Authorizes maxclicks to send on your behalf. |
MX on the return-path subdomain, priority 10 | Bounce handling. Routes the delivery failures for your mail back to maxclicks. |
TXT on _dmarc | DMARC. Tells mailbox providers what to do with mail that fails the checks above. |
The return-path is a label under your sending domain, commonly send.. Use the exact name generated for your domain rather than reconstructing it. It is the bounce-handling address, distinct from the visible From address.
Each record carries a status you can watch: Not Started, Pending, Verified, Failed or Temporary Failure. The whole domain shows Verified For Sending or Not Verified For Sending at the top.
Leave every record in place for as long as you send. maxclicks re-checks through the day, and if the records disappear it un-verifies the domain and all sending from it stops.
Diagnose a blocked send
Read the overall Verified For Sending status, then the individual authentication records. Copying a record into a DNS dashboard is only the first step; maxclicks must observe the required state before the domain can send.
Verification and permission to send are separate checks. A verified domain can still belong to a workspace whose sending is disabled because of delivery or reputation issues. Inspect the current message and the workspace Inbox instead of repeatedly recreating the domain. A successful in-app preview needs no inbox delivery; Send test does, and uses the same verified domain requirement as other sends.
The default domain
The first domain you add becomes the space default, used wherever you do not pick one yourself. It becomes the default when you add it, not when it verifies: verification is what lets it send.
Set as default on any row moves it, but only a verified domain can hold the spot. The menu item stays clickable on an unverified domain, and running it there is refused: you get a "Failed to set domain as default" message and nothing changes. Verify the domain first.
Moving the default also moves the default sender. It becomes the first sender profile saved on the new default domain, or nothing at all when that domain has no profiles yet.
If you delete the default, maxclicks picks another verified domain to replace it, or leaves the space without a default when none is verified.
Deleting a domain takes more with it than the domain itself. Every sender profile saved on it is deleted too, and any broadcast, template or workflow email whose from-address pointed at that domain or one of its profiles is left without one, so it refuses to send until someone picks a new from-address. The confirmation dialog does not spell this out.
Sender profiles
A sender profile is a saved from-address, so nobody has to retype support@ every time they build an email. They live in Settings, then Sender Profiles.
Each profile has a Name (the display name recipients see, like Janet Vargas), an optional description, and an Email: the part before the @ plus one of your domains. maxclicks previews the finished address as you type. Typing a name suggests a local part for you.
You can save a sender before its domain verifies, but two senders in a space cannot end up at the same address.
One profile is the space default. Set as default is only available on a profile whose domain is itself the default domain, so if the option is greyed out, set that domain as default first.
Checking verification from your own code
If a deploy script or health check needs to confirm a domain is ready before it points sending at it, the API can read domains and senders. See the domains and senders API reference.
The public API reads domain and sender configuration. Domain setup and verification are managed through the app and authorized product actions. Creating a domain requires editing access (Member or Admin), not a Non-paid Admin role. A domain name already assigned to another workspace cannot be claimed again.