Broadcast sends through your own mailbox, not our servers — so we can't fix your domain's email authentication for you, but we can tell you exactly what's missing and how to add it.
SPF (Sender Policy Framework) is a DNS record listing which mail servers are allowed to send email for your domain. Without it, receiving mail servers have no way to confirm your messages are legitimate.
Add (or extend) a TXT record at your domain's root with include:_spf.google.com — for example: v=spf1 include:_spf.google.com ~all.
Add (or extend) a TXT record at your domain's root with include:spf.protection.outlook.com — for example: v=spf1 include:spf.protection.outlook.com ~all.
Ask your email provider for the SPF include value they require, then add it to your domain's TXT record the same way.
DKIM (DomainKeys Identified Mail) cryptographically signs your outgoing mail so receivers can verify it wasn't altered in transit.
In the Google Workspace admin console: Apps → Google Workspace → Gmail → Authenticate email → Generate new record. Add the resulting TXT record to your DNS, then return and click Start authentication.
In the Microsoft 365 Defender / Exchange admin center: Email & collaboration → Policies & rules → Threat policies → Email authentication settings → DKIM. Select your domain and toggle Enable.
Ask your mail server administrator to confirm DKIM signing is enabled and published for your domain — there's no universal admin panel for this.
DMARC tells receiving mail servers what to do if a message fails its SPF or DKIM check, and where to send reports about it. Unlike SPF and DKIM, the record itself is identical regardless of your mail provider.
Add a TXT record at _dmarc.yourdomain.com with a value like:
v=DMARC1; p=none; rua=mailto:you@yourdomain.com
p=none is a safe, monitoring-only starting policy — it doesn't block any mail. Replace the rua address with one you actually want reports sent to. Tightening to p=quarantine or p=reject later is a deliberate follow-up step, not something this checklist requires.
Same record as above — DMARC doesn't vary by mail provider. Add it at _dmarc.yourdomain.com through wherever you manage your domain's DNS.
Same record as above — add it at _dmarc.yourdomain.com through wherever you manage your domain's DNS.
Broadcast can't override LinkedIn's, Instagram's, or your email provider's own account-safety systems — but here's what to expect from ours, and why.
New and reconnected accounts start conservative and send more each day only after a string of clean days with no checkpoints, disconnects, or bounces. This warm-up ramp — and the daily send/invite caps that go with it — exist specifically to keep your account in good standing with whichever platform you're sending through. A slower start is the product working as intended, not a limitation to work around.
If an account shows "Checkpoint — reconnect" or "Disconnected," the platform itself asked for a pause — usually a security check, a verification prompt, or a temporary restriction. This is a safety mechanism, not a sign anything is broken. Reconnecting is safe once you've cleared any prompt on the platform's own site or app; any messages that were waiting on that account resume automatically once it reconnects.
A large pile of LinkedIn connection invitations that have sat pending for a long time without being accepted is itself a signal LinkedIn's own systems watch for. It's worth periodically checking your sent invitations on LinkedIn directly and withdrawing ones that are old and unlikely to be accepted.