Reputation Builder
DNS setup (Inbox Boost)
Before warmup can send on your behalf, your domain must publish the authentication records SenderSignal assigns, then verify them in the app.
Why DNS setup comes first
Inbox Boost sends real warmup mail from infrastructure dedicated to your domain. Receiving providers must see valid SPF, DKIM, and aligned return-path. Without them, mail bounces or lands in spam. DNS setup walks you through publishing exactly the records needed for your domain, then confirms they are live at public resolvers before warmup unlocks.
Where to start
- Open Reputation Builder → DNS Setup in the sidebar.
- Add a domain that is already monitored under Monitor (or register a new monitored domain first).
- Open the domain detail page: you will see a step-by-step wizard: Domain added → Publish DNS → Verify records → Inbox Boost ready.
Records you will publish
SenderSignal generates domain-specific values. Copy each record into your DNS registrar or DNS provider (Cloudflare, Route 53, GoDaddy, etc.). Typical records include:
SPF (TXT at root / apex)
- Authorizes which servers may send mail for your domain
- If you already have SPF, SenderSignal shows a merged value: your existing includes plus the dedicated sending include assigned to your domain
- Only one SPF TXT record should exist at the apex; replace or merge rather than adding a duplicate
DKIM (TXT on selector subdomain)
- Public key for signing outbound mail (e.g.
selector._domainkey.yourdomain.com) - Host name and full TXT value are shown on the setup page: copy both exactly
Return-path (CNAME)
- Custom bounce/return-path domain (e.g.
rp.yourdomain.com) pointing to your assigned return-path hostname - Improves alignment between envelope sender and your brand domain
Domain ownership (TXT, when required)
- Some domains require a one-time ownership TXT record before SPF/DKIM values are issued
- After ownership verifies, remaining records appear automatically
DMARC (TXT at _dmarc, recommended)
- Policy telling receivers what to do with mail that fails SPF/DKIM alignment
- If you already publish DMARC, the page shows your live policy and may suggest tightening
p=nonetoquarantineorreject - If DMARC is missing, a recommended starter record is provided
Custom MAIL FROM / MX (when shown)
Depending on your configuration, additional MX or MAIL FROM guidance may appear. Follow the on-page instructions: they are tailored to your domain.
Publishing at your registrar
- Copy Host / Name and Value from each record card
- Paste into your DNS provider: use TXT for SPF/DKIM/DMARC, CNAME for return-path
- Save changes and wait for propagation (often minutes; can take up to 24–48 hours globally)
- Return to SenderSignal and click Verify DNS records
Verification statuses
| Status | Meaning |
|---|---|
| Verified | Record found at DNS and matches expected value |
| Pending | Not found yet or still propagating: verify again later |
| Advisory | Record exists but could be improved (e.g. weak DMARC policy) |
| Failed | Missing or wrong value: compare registrar entry with expected value |
After verification
When SPF and DKIM verify, SenderSignal provisions your dedicated sending configuration in the background. The wizard advances to Inbox Boost ready. You can then configure warmup template and From address under Inbox Boost before starting volume ramp.
Common issues
- Duplicate SPF: merge into one TXT record; delete extras
- Wrong DKIM host: some registrars append the apex automatically; enter only the selector portion if instructed
- CNAME conflict: return-path host cannot coexist with other record types on the same name
- SPF lookup limit: too many
include:mechanisms; SenderSignal warns when merge would exceed DNS lookup limits
Relationship to Monitor deliverability
Monitor → Deliverability checks SPF/DKIM/DMARC independently. DNS Setup records are optimized for sending through Inbox Boost. Keep both aligned: after publishing here, rescan deliverability on the same domain to confirm external probes agree.