Verify a domain

Before Bytloop Mail will send from an address on your domain, the domain has to be verified. Verification proves you control the domain and gives mailbox providers (Gmail, Outlook, Yahoo, Apple Mail) the signals they need to trust your mail. It is a one-time set-up per domain.

Head to Domains in the dashboard, click Add domain, and enter a subdomain you want to send from — for example send.acme.com. Bytloop returns three record sets you need to publish at your DNS host.

DKIM#

DomainKeys Identified Mail. Bytloop generates a keypair for the domain, holds the private half, and asks you to publish the public half as a TXT record. Signatures on outbound mail are then verifiable by any receiver.

Publish two records that look like this — the exact selectors and values come from the dashboard:

Two selectors are published so we can rotate keys without breaking your verified status — if one is compromised, the other stays live.

SPF#

Sender Policy Framework. A TXT record on the sending domain that lists the servers allowed to send mail on its behalf. If your domain already has an SPF record for another provider, do not create a second one — merge Bytloop's include into the existing record.

v=spf1 include:spf.bytloop.mail -all

v=spf1 include:spf.bytloop.mail -all

If you already send through, say, Google Workspace:

v=spf1 include:_spf.google.com include:spf.bytloop.mail -all

v=spf1 include:_spf.google.com include:spf.bytloop.mail -all

The -all at the end says "anything not listed above should be rejected." Some hosts use ~all (soft fail) instead; either is fine, but -all is stricter and preferred once you are confident your record is complete.

DMARC#

Domain-based Message Authentication, Reporting & Conformance. Sits on top of DKIM and SPF, telling receivers what to do with mail that fails both. Publish this on the root domain (the one users see in the From header), not the sending subdomain.

Start in monitor mode so nothing gets rejected while you validate:

v=DMARC1; p=none; rua=mailto:dmarc-reports@acme.com; adkim=r; aspf=r

v=DMARC1; p=none; rua=mailto:dmarc-reports@acme.com; adkim=r; aspf=r

Once you have watched aggregate reports for a couple of weeks and every legitimate stream aligns, move to p=quarantine and eventually p=reject. See the DMARC status card in Domains for a live read of your alignment rate.

Verifying the records#

Once the records are live, click Verify on the domain in the dashboard. Bytloop resolves each record and either flips the domain to verified or shows exactly which record is still missing or misformed.

DNS caches can hold old NXDOMAIN answers for a while; if verification fails right after you published records, wait five minutes and try again.

Next#

• Send a first message with the domain from Send a transactional email.
• If you want to receive replies too, publish the MX record described in Receive email.