How to set up DMARC/DKIM/SPF for SDR Force

Updated on 9 Nov 2026: We clarified how to verify SDR Force's actual sending service and protect existing mail when enforcing DMARC.
SPF, DKIM, and DMARC need to work together for SDR Force outreach, but the DNS owner first needs to identify which system transmits each message. SPF authorizes infrastructure for the MAIL FROM domain, DKIM signs the message with a domain, and DMARC compares either authenticated domain with the visible From domain. Configure the records supplied by the actual sending service, then test a live SDR Force message for DMARC alignment.
Use records from the actual sender
SDR Force's public site describes outsourced sales development, and it does not provide a universal SPF include or DKIM selector set. Ask the team managing your outreach for DNS instructions from the actual sending service. The record patterns and interface images below are illustrative, not verified SDR Force production settings. Do not copy DNS values from the images.
Identify the actual sending system
This check prevents adding DNS records for SDR Force when a connected mailbox service or another relay performs the delivery. Send one message through the same outreach workflow and mailbox that will be used in production, then inspect its full headers before changing DNS.
- Find the MAIL FROM domain: Read the Return-Path header and the smtp.mailfrom value in the recipient's Authentication-Results. This is the domain SPF authenticates for DMARC.
- Find the DKIM domain: Find a dkim=pass result in the recipient's Authentication-Results, then match its header.d domain to d= in the corresponding DKIM-Signature and note the s= selector. The passing d= domain needs DMARC alignment with the visible From domain.
- Trace the sending IP: Use Authentication-Results added by the recipient's mail system and its inbound Received header to identify the external sending IP. Earlier headers can contain untrusted claims.
- Choose the record owner: Ask the team managing SDR Force outreach which mailbox service or relay sends and signs each message. Use that service's exact DNS instructions for the confirmed message path.
Do not infer the sender from branding
The visible SDR Force workflow does not prove that SDR Force owns the sending IP, return path, or DKIM key. Message headers and generated DNS instructions determine the authentication setup.
Inventory all senders before changing DMARC policy
A DMARC policy affects all mail using the covered From domain, including messages outside SDR Force outreach. Build a sender inventory before changing SPF or enforcing DMARC so an outreach setup does not interrupt another business workflow.
- List every authorized sender, including staff mailboxes, billing systems, customer support, and website forms.
- For each sender, record its owner, visible From domain, MAIL FROM domain, and DKIM d= domain with active selectors.
- Compare the inventory with representative message headers and aggregate reports. Investigate unfamiliar sources before authorizing them.
- Include infrequent workflows such as monthly invoices, and save the existing DNS values before making changes.
Monitoring must cover the workflows you actually use. A quiet week of outreach does not establish that a monthly billing system is ready for p=reject. Keep an existing working enforcement policy while testing a new SDR Force sending route.
Add and verify your domain
Get domain verification and authentication instructions from the service that sends the SDR Force outreach messages. Publish its records at your authoritative DNS host, which is not necessarily your domain registrar. Manage signing and mailbox settings in the sending service.
- Confirm access: Obtain access to the domain's authoritative DNS zone and the service that sends the outreach messages.
- Confirm the sender: Match the connected mailbox and sending route to the live headers collected earlier.
- Add the requested domain: Use the domain the sending service asks you to verify, which can be the organizational domain or a dedicated subdomain.
- Copy records: Copy each hostname, record type, and value exactly, including every DKIM selector and any custom return-path record.
- Verify after DNS resolves: Wait for cached DNS answers to expire according to their TTL, confirm public resolution, run the sending service's verification, and then test a new outbound message.

Illustrative sending-domain verification screen for SDR Force outreach.
The visible From domain and the authenticated domains must have the intended relationship. A message from jane@example.com has example.com as its visible From domain. A message from jane@sales.example.com has sales.example.com as its visible From domain. The default adkim=r and aspf=r settings use relaxed alignment, which permits domains sharing the same organizational domain. Strict alignment (adkim=s or aspf=s) requires an exact domain match for that method. A return path at bounce.example.com therefore has SPF alignment with example.com in relaxed mode, but not strict mode.
|
|
|
|---|---|---|
TXT | MAIL FROM domain | SPF authorization |
CNAME or TXT | selector._domainkey.signing-domain | DKIM verification |
TXT | _dmarc.visible-From-domain | DMARC policy and reporting |
CNAME, or MX and TXT | Custom MAIL FROM subdomain | Return-path routing and SPF alignment, as instructed by the sender |
DNS map for the domains involved in authentication.
Set up SPF
SPF contributes to DMARC only when the authenticated MAIL FROM domain has alignment with the visible From domain. The connected sending service can use its own return path, a custom return-path subdomain, or the mailbox domain. The live Return-Path header shows which case applies.
- Find the SPF domain: Use the smtp.mailfrom result or Return-Path header from a real SDR Force message, not the visible From address alone.
- Check the exact host: Look for an existing SPF TXT record at the MAIL FROM hostname before publishing a value. SPF records are not inherited from the parent domain.
- Keep one record: When the sending service requires an include at a host that already has SPF, add it to the existing record instead of creating a second SPF record.
- Check the lookup count: Keep SPF evaluation within the limit of 10 terms that require DNS queries, including nested includes and redirects. This limit counts evaluated mechanisms and modifiers, not every DNS packet, as specified in RFC 7208.
- Verify authentication and alignment: Send a new test and confirm both spf=pass and an aligned smtp.mailfrom domain in Authentication-Results.
SPF pattern when the sender provides an includeDNS
v=spf1 include:spf.sender.example include:_spf.example.net -all
The domains above are reserved examples. Replace the include values with those supplied by the actual sending services, preserving existing authorized senders. If the service provides a custom return-path CNAME instead, publish the CNAME as instructed and do not invent a separate SPF include.
SPF checker
Find SPF syntax issues, lookup limits, and weak records.
?/16tests passed
After the SPF checker finds one valid record at the intended hostname, test a real message. An SPF pass on a service-owned return path does not make DMARC pass unless that domain has alignment with the visible From domain.

Illustrative SPF and custom return-path DNS settings for SDR Force outreach.
Do not publish two SPF records
Two SPF TXT records at the same hostname cause SPF permerror. Merge required mechanisms into one record, then remove the duplicate without changing unrelated senders.
Set up DKIM
DKIM is usually the more durable DMARC path because a valid signature can survive forwarding when the signed content is unchanged. Configure DKIM in the service that signs the outbound message and make its d= domain share the required DMARC relationship with the visible From domain.
- Open DKIM settings: Use the sending service identified in the message headers and copy every selector it assigns to your domain.
- Create the records: Add each DKIM CNAME or TXT record exactly as displayed by the signing service. After DNS verification, enable or activate DKIM signing if the service requires a separate action; publishing a key alone does not sign messages.
- Avoid doubled domains: If the DNS interface automatically appends the zone name, enter only the host prefix.
- Support rotation: Publish every active selector. Use 2048-bit RSA keys and rotate them when the signing service exposes those controls. Keep previous selectors available while messages signed with those keys are still in transit.
- Verify the signature: Send a new message and confirm dkim=pass, the expected s= selector, and DMARC alignment for the d= domain.
DKIM CNAME patternDNS
selector1._domainkey.example.com. CNAME selector1._domainkey.sender.example. selector2._domainkey.example.com. CNAME selector2._domainkey.sender.example.
The selector and target names above are reserved examples. Production records must come from the signing service. After publishing them, confirm that a live SDR Force message has a DKIM-Signature with the same selector and the intended d= domain.

Illustrative DKIM selector CNAME records for SDR Force outreach.
DKIM checks that should pass
- Pass: The DKIM signature validates against the public key in DNS.
- Aligned: The d= domain has the required DMARC relationship with the visible From domain.
- Maintainable: All active selectors resolve so the signing service can rotate keys safely.
DKIM problems to resolve
- Missing: The selector host does not resolve, often because the DNS name was entered twice.
- Unaligned: The d= domain passes DKIM but does not have DMARC alignment with the visible From domain.
- Broken: A later system changes signed content after the sending service applies DKIM.
Set up DMARC
Publish DMARC at _dmarc beneath the visible From domain. For a domain without an existing policy, p=none provides monitoring while aggregate reports show sources observed by participating receivers. If a working p=quarantine or p=reject policy already covers the domain, keep it and authenticate the new sending path before production traffic begins.
Starter DMARC recordDNS
v=DMARC1; p=none; rua=mailto:dmarc@example.com
For example.com, publish one DMARC TXT record at _dmarc.example.com and replace dmarc@example.com with a real report destination. For an outreach subdomain, check the applicable parent policy before adding a record: an inherited organizational-domain policy uses sp for existing subdomains, or p when sp is absent. If rua points outside your organizational domain, confirm that the reporting service publishes the external-report authorization required by RFC 9990.
Use the DMARC record generator to build a TXT value with an aggregate-report address or subdomain policy. RFC 9989 defines DMARC, RFC 9990 defines aggregate reporting, and RFC 9991 defines failure reporting. The pct tag is historic. The t=y testing flag is not percentage sampling, and receivers using older rules ignore it. Keep p=none for initial monitoring rather than relying on t=y to prevent enforcement.
DMARC checker
Look up a domain's DMARC record and catch policy issues.
?/7tests passed
After the record resolves, send SDR Force mail to a mailbox that exposes full authentication headers. The target is dmarc=pass through aligned SPF or aligned DKIM. Check both paths when available because either one can later fail independently.

Illustrative SPF, DKIM, and DMARC verification statuses for SDR Force outreach.
DMARC pass condition
A message passes DMARC when SPF passes for an aligned MAIL FROM domain or DKIM passes for an aligned d= domain. Both are preferable for operational resilience, but the protocol requires only one aligned pass.
Verify and troubleshoot
Do not stop after DNS records resolve or an interface shows green checks. Verify a real outbound message because correct DNS can still accompany the wrong signing domain, an unaligned return path, or a different route for one connected mailbox.
- Send a production-shaped test: Use the same outreach workflow, mailbox, From domain, and sending route intended for production.
- Read the results: Check the recipient's Authentication-Results for SPF, DKIM, and DMARC verdicts, plus smtp.mailfrom and header.d values.
- Check DMARC alignment: Confirm that at least one passing authenticated domain has the required relationship with the visible From domain.
- Fix the named cause: Correct doubled hostnames, duplicate SPF records, missing selectors, or a mailbox that uses an unexpected sending route.
- Retest with a new message: Authentication headers belong to one message, so send a fresh test after each change.
Send a new SDR Force outreach message to Suped's email tester and inspect the live header diagnosis. This checks the selected sending route as well as DNS. A DMARC pass authenticates the From domain; it does not guarantee inbox placement.
Email tester
Send a real email to this address. Suped shows a results button when the test is ready.
?/43tests passed
Treat SPF and DKIM as separate evidence. Forwarding commonly breaks SPF because the forwarding server becomes the connecting IP, while DKIM can survive unless signed content changes. An aligned DKIM pass can still produce a DMARC pass when SPF fails.
Enforcement readiness checks
Use evidence from live mail and aggregate reports. DMARC defines no universal pass-rate threshold for enforcement.
Ready
All known mail passes
All legitimate SDR Force paths are identified and consistently pass DMARC.
Investigate
Unexplained results remain
Any source, mailbox, selector, or sending IP is unexplained.
Do not enforce
Known mail can fail
A legitimate SDR Force path still fails both aligned SPF and aligned DKIM.
Common authentication failure patterns
- SPF permerror: The evaluated MAIL FROM hostname has duplicate SPF records or exceeds the DNS lookup limit.
- DKIM none: The message was not signed. Enable DKIM in the sending service, then send a fresh test.
- DKIM key lookup error: A signed message has no usable selector key, or DNS lookup fails. Check the receiver's diagnostic reason and distinguish a missing key from a temporary DNS error; RFC 8601 defines the reported result values.
- DMARC fail: Neither SPF nor DKIM produces a passing result with DMARC alignment to the From domain. Check authentication failures as well as domain mismatches.
- Route mismatch: One outreach mailbox or workflow sends through a different service than the tested path.
Get alerted when authentication breaks
Authentication can break after a DNS cleanup, mailbox reconnection, SPF edit, or DKIM rotation. Aggregate reports usually cover a day and arrive after processing, so alerts depend on report arrival. Not every receiver reports, and aggregate data does not identify individual mailboxes. Use send logs and fresh headers alongside the domain-level data described in RFC 9990.
- Group the source: Use sending IPs, reverse DNS, envelope domains, and DKIM selectors to group the mail path used by SDR Force.
- Alert on new behavior: Trigger notifications when DMARC pass rates fall, an unfamiliar IP appears, or an expected selector disappears.
- Trace alignment failures: Compare the visible From domain with smtp.mailfrom and header.d instead of treating an SPF or DKIM pass alone as success.
- Check reputation: Monitor blocklist (blacklist) listings for sending domains and IPs associated with the confirmed SDR Force mail path.
Suped's product turns RFC 9990 aggregate reports into source-level views and alerts. For an SDR Force workflow, Suped can group the confirmed sending IPs and authenticated domains, flag a new source, and show whether SPF or DKIM lost DMARC alignment.
Use DMARC monitoring to investigate the confirmed SDR Force sending route alongside other authorized mail on the same domain. Shared IPs and authenticated domains can combine several workflows, so use send logs and test headers to attribute the reported traffic.
Manual monitoring
- Delayed: DNS and headers are inspected after someone notices a delivery problem.
- Hard to correlate: Source IPs, selectors, and alignment results must be connected by hand.
- Mailbox-specific gaps: A test for one mailbox can miss a different route used by another mailbox.
Suped monitoring
- Source grouped: Aggregate-report data is organized around the authenticated sender.
- Failure explained: The view distinguishes authentication failure from DMARC alignment failure.
- Change detected: Alerts identify new sending IPs or unexpected authentication changes.
Secure your domain with p=reject
Move to p=reject only after every legitimate sending path is identified and consistently passes DMARC in live tests and available aggregate reports, including mail outside SDR Force outreach. A p=reject policy expresses the domain owner's requested handling, although receiving systems retain local discretion.
- Start in monitoring mode: If the domain has no working enforcement policy, use p=none while representative traffic validates the sender inventory. Test every connected mailbox directly because aggregate reports do not identify individual mailboxes.
- Authorize each source: Confirm that every legitimate sender produces aligned SPF or aligned DKIM.
- Fix SDR Force paths: Resolve return-path, lookup, selector, signing-domain, and routing problems shown by live headers.
- Use quarantine when useful: Move to p=quarantine only after monitoring is clean if a quarantine stage fits the domain's risk plan.
- Request rejection: Publish p=reject after legitimate failures are resolved and every remaining unknown source has been classified.
Policy rollout path
Hypothetical values illustrate the rollout sequence, not SDR Force measurements or protocol thresholds. Investigate legitimate failures even at a 99.5% pass rate.
DMARC pass rate
Suped's hosted DMARC can manage the policy change without repeated DNS edits and connect a failure to its source data. That workflow is useful when the same domain carries SDR Force outreach and other legitimate mail.
Do not enforce over unknown failures
If a legitimate SDR Force message still fails both aligned SPF and aligned DKIM, a stronger policy risks adverse handling by receivers. Fix that sending path before requesting quarantine or rejection.
FAQ
Use the records required by the service that actually sends and signs the message. These commonly include an SPF record for the MAIL FROM domain, DKIM selector records, and a DMARC TXT record beneath the visible From domain. Add a verification or return-path record only when the sending service supplies it.
Not automatically. SPF authenticates the MAIL FROM domain used by the system that transmits the message. Inspect a live SDR Force email, then publish only the SPF mechanism or custom return-path record supplied for that sending path.
Use p=none for a domain without an existing policy while reviewing aggregate reports, then move to quarantine or reject after every legitimate sender passes DMARC. If the domain already has a working enforcement policy, authenticate and test the new SDR Force path before sending production mail.
DKIM can pass cryptographic verification while its d= domain lacks DMARC alignment with the visible From domain. Configure the signing service to use an aligned domain, then test a new message.
Match a known SDR Force test message to its sending IP, reverse DNS, MAIL FROM domain, DKIM d= domain, and selector. Use that combination to classify aggregate-report rows. Reverse DNS alone is a clue, not proof.

