Custom domains

Use a domain you control for your Solo identity and agent email addresses. Your website does not move, and your existing @solomail.io addresses remain available.

Before you start

You need access to the account where your domain's DNS records are managed. If the domain already receives email, also identify the current email provider. The DNS provider and email provider can be different.

For example, a domain can use Cloudflare for DNS while Google Workspace receives its email.

What completing setup does

SoloMail activates the domain as soon as its SPF and DKIM records are verified. At that point it automatically creates the identity's primary custom-domain address, such as kaelonegan@kaelon.io. You do not need to create that address again in Addresses & aliases.

Receiving mail at the address is a separate, optional choice. If the domain already receives mail somewhere else, keep that provider and add a forward only when you want those messages to appear in SoloMail.

Choose how incoming mail works (optional)

Keep your current provider

This is the recommended option when the domain already has working mailboxes. SoloMail adds sending-authentication records but does not replace your MX records. No receiving change is required to finish custom-domain setup. To also receive custom-domain mail in SoloMail, forward the identity's base address to its normal SoloMail address:

kaelonegan@kaelon.io → kaelonegan@solomail.io

When the provider supports subaddressing, the same rule covers the base address and all of its +role variations.

One rule covers every current and future agent:

kaelonegan@kaelon.io          → Inbox Manager
kaelonegan+sales@kaelon.io    → Sales
kaelonegan+support@kaelon.io  → Support
kaelonegan+future-role@kaelon.io → that future agent

If a role is missing or mistyped, SoloMail keeps the message and sends it to Inbox Manager.

Move all incoming mail to SoloMail

This option replaces the domain's MX records. It affects every mailbox and catch-all on the domain, so migrate or recreate existing addresses before making the change.

Connect the domain

  1. In Identity → Profile & Branding → Domain, enter the domain.
  2. Choose an identity email name. This is the part before @ and before every agent's +role suffix.
  3. Select Set up automatically or Set up manually to add the displayed SPF and DKIM records where DNS is managed.
  4. Select Check DNS. Once SPF and DKIM pass, the page shows Ready and creates the primary custom-domain address automatically.
  5. Optional: if you want incoming messages in SoloMail, open Receive mail in SoloMail and add the displayed forwarding rule at your current email provider.

Automatic DNS setup

Cloudflare is currently supported. Select Set up automatically, choose Cloudflare, and continue to Cloudflare. You will sign in there, choose the account that owns the domain, review the requested DNS permission, and approve the change.

SoloMail then:

  • finds the Cloudflare zone for your domain;
  • adds only the DNS records required to activate sending;
  • keeps CNAME records DNS-only;
  • refuses to replace conflicting SPF, CNAME, or MX records; and
  • revokes its one-time Cloudflare access after the attempt.

When you choose Keep your current provider, automatic setup does not change MX records. It does not change your website or unrelated DNS records in either mode.

Cloudflare account administrators can restrict third-party OAuth applications. If your account does not allow the connection, use the manual setup path or ask the Cloudflare account administrator to allow the authorization.

Manual DNS setup

Select Set up manually, then choose the DNS provider for provider-specific tips. If the provider is not listed, choose Another provider; the record type, name, value, priority, and TTL are still portable to any standards-based DNS service.

If an SPF record already exists, merge the SoloMail include into it; do not publish two SPF records at the same name. Cloudflare CNAME records used for email must be set to DNS only rather than proxied.

The email-tracking CNAME is optional. It enables open, click, and unsubscribe tracking, but it does not block domain activation, sending, incoming routing, or custom addresses.

Provider instructions

Cloudflare Email Routing

This is separate from Cloudflare DNS. Use these steps only when Cloudflare Email Routing currently receives mail for the domain and you want that incoming mail to appear in SoloMail. DNS records activate the custom domain for sending; this optional routing rule forwards mail to the identity's existing SoloMail inbox without replacing the domain's MX records.

  1. Open Email Routing → Settings and enable subaddressing.
  2. Add the identity's normal @solomail.io address as a destination address.
  3. Open the verification message in your Solo inbox and approve the destination.
  4. Create one routing rule from the custom-domain base address to that normal SoloMail address. Cloudflare applies that rule to its +role subaddresses.
  5. Keep the existing catch-all and unrelated routing rules unchanged.

Google Workspace

Use a recipient routing or split-delivery rule for the identity base address and its subaddresses. Send matching messages to the identity's normal @solomail.io address and leave the original recipient headers intact.

Microsoft 365

Use an Exchange mail-flow rule and connector for the identity base address and its subaddresses. Redirect matching messages to the identity's normal @solomail.io address without rewriting the original recipient.

Another provider

Look for Forwarding, Aliases, Email routing, Recipient rules, or Split delivery. Create one rule from the identity base address and its subaddresses to the identity's normal @solomail.io address.

If the provider only supports a fixed forward and removes the original recipient, dynamic +role routing cannot be verified. Use a provider connector, move MX to SoloMail, or create explicit static aliases instead.

Public aliases

Public aliases such as sales@kaelon.io and support@kaelon.io are separate from identity agent addresses such as kaelonegan+sales@kaelon.io. Create and manage public aliases in the Addresses & aliases section, then select the agent that should handle each address.

Frequently asked questions

Do I need a new provider rule when I add an agent?

No. A verified base-address route covers future +role agent addresses.

Does SoloMail configure my domain inside the SoloMail Cloudflare account?

No. DNS and mail-routing changes stay in your domain provider and email provider accounts. The forwarding destination is a SoloMail-owned receiving address, not a transfer of your domain.

Does this affect my website?

No. SoloMail only requests email-authentication and, when explicitly selected, mail-routing records.

Is forwarding required to activate the domain?

No. Existing-provider setup is complete when SPF and DKIM are verified. Forwarding is optional and only controls whether incoming custom-domain mail is also delivered to SoloMail.

How do I know my forwarding rule is correct?

Send a normal message from another inbox to the primary custom-domain address, such as kaelonegan@kaelon.io, and confirm it appears in SoloMail. There is no special SoloMail test address or separate activation check.