Verify your sending domain
Add the DNS records shown for your domain and confirm that your sender is ready.
Verify the domain used by your sender before sending to customers. This lets Bitelio authenticate messages from an address such as hello@yourstore.com; it does not move your website or mailbox.
1. Add the domain
Open the domain task from Second purchase → Settings, or the project's domain settings. Add the domain used after the @ in your sender address. You need access to that domain's DNS provider, or someone who can publish records for you.
The panel shows the exact DNS records for this domain and their current status. Use those names and values, not records copied from another project or a tutorial. Adding a domain to Bitelio alone does not publish records in your DNS.
2. Choose how to publish the records
Cloudflare connection
When the Cloudflare connection is available, authorize the account that manages your domain. Choose the zone and request a preview of the proposed changes. Check what would be added or replaced, then explicitly confirm publication.
If the preview reports an ambiguous record or conflict, resolve it before trying again. Bitelio does not choose which unrelated mail records to delete. You can run the preview again after a partial failure to see what remains.
The SPF record Bitelio needs belongs to the MAIL FROM subdomain shown in the panel. This connection does not rewrite your root domain's SPF for other senders.
Manual DNS setup
Open your DNS provider and add each record with its displayed type, name and value. Providers differ in whether they append your domain to the name: check the final full hostname so it is not repeated twice. Publish email-related CNAMEs as DNS records, without a website proxy.
Save the changes at the provider, then return to Bitelio and check verification. DNS updates can take time to become visible. A pending state means the records have not yet been confirmed; it does not mean you should add duplicates.
3. Understand the records shown
Different domains can use different authentication setups. Existing domains are not automatically migrated when a new setup becomes available.
| Record or setting | Purpose |
|---|---|
| DKIM CNAMEs | Authenticate the signature on your messages. A managed setup uses two CNAMEs; a legacy setup may show three. Publish the set shown for your domain. |
| MAIL FROM | The separate return address used by sending infrastructure. Depending on setup, the panel offers a delegated subdomain or MX/TXT records on that subdomain. |
| Optional NS delegation | Gives Bitelio control of only the specified MAIL FROM subdomain. It is not a change to your domain's main nameservers. Use the values shown in your panel. |
| Receiving email | A separate, optional MX setup for mail arriving at your domain. It is not required just to send. |
With managed authentication enabled, Bitelio maintains the DKIM material behind the two CNAMEs. The additional MAIL FROM delegation remains a separate choice. If managed authentication is unavailable, follow the legacy records displayed instead.
Do not add another SPF TXT record at a hostname that already has one. Review the exact hostname and conflict; do not alter the root SPF simply because a sending-domain tutorial mentions SPF.
Keep your existing mailbox working
Receiving email in Bitelio is a separate choice. If Google Workspace, Microsoft 365 or another provider already receives your mail, do not add Bitelio's inbound MX casually: it can compete with those mail servers. Leave the inbound option off unless you intend to configure receiving email.
DMARC is also a separate policy for your domain. Review it with whoever manages all your senders; copying a strict policy without checking those senders can affect legitimate mail. Domain verification alone is not a guarantee of inbox placement.
4. Confirm and return to your program
Once Bitelio shows the required records as verified, select a sender address on that domain and review its visible name. Return to Second purchase using the setup return link and check the remaining requirements.
If verification remains pending, compare the final DNS hostnames and values with the panel, confirm the authoritative provider, and check any publication error. Contact support@bitelio.com with the domain and the failing record type; do not send passwords or DNS credentials.