Skip to content
DMARC Pulse
Guides

Proofpoint

Proofpoint DMARC setup: SPF, DKIM and your email gateway

Proofpoint DMARC setup: when to add Proofpoint to SPF, which system should sign DKIM, and how to publish a DMARC record when mail uses the gateway.

How Proofpoint changes your DMARC setup

Proofpoint DMARC setup depends on one question: does your outgoing mail leave through Proofpoint? Proofpoint sells an email gateway, a service that inspects messages as they enter or leave your organization. When outgoing mail leaves through the gateway, receivers see Proofpoint's servers as the sender. Your SPF record then has to list those servers, and your DKIM signature has to survive the trip. When only incoming mail passes through it, the way your domain authenticates outgoing mail stays the same.

Existing DMARC policy: authenticating Proofpoint does not require resetting it. Keep one _dmarc record, preserve p, subdomain and alignment settings, and merge any needed rua address with existing destinations. The p=none example below is only for a new deployment without a valid record.

The Proofpoint name covers several products, and each one touches DMARC differently:

  • Proofpoint Essentials has its own MX hosts and an outbound smart host for each data center. A smart host is the server your mail system hands outgoing mail to.
  • Proofpoint Email Protection runs on the Protection Server. Proofpoint's administrator course covers its inbound and outbound routes, SPF and DMARC rules, and DKIM signing.
  • Core Email Protection deploys by API or inline, in the path of the mail. Proofpoint offers API protection for Microsoft 365. Use the check below to see whether your mail takes a Proofpoint route.
  • Email Fraud Defense hosts SPF, DKIM and DMARC records and helps your gateway enforce DMARC on incoming mail.
  • Secure Email Relay is a cloud relay for mail that applications generate. Proofpoint says it applies DKIM signatures automatically.

Unless you use Proofpoint's Hosted DMARC, your DMARC record lives in your own DNS.

Check whether mail leaves through Proofpoint

Incoming and outgoing routes are separate settings, so an MX record that points to Proofpoint tells you nothing about outgoing mail.

  1. Look up your MX records. Hosts such as mx1-us2.ppe-hosted.com mean Proofpoint Essentials receives your incoming mail.
  2. Send a normal message from a real mailbox to an address outside your organization.
  3. Paste its headers into the email header analyzer and read the Received lines. Send the test to a mailbox that is not behind Proofpoint. A host under ppe-hosted.com on the sending side of the path, before the recipient's own servers, indicates that the message left through Proofpoint Essentials. The Essentials guides name outbound-us1.ppe-hosted.com, outbound-us2.ppe-hosted.com and outbound-eu1.ppe-hosted.com as smart hosts. For other Proofpoint products, compare the hosts with the outbound route your administrator set up.
  4. Repeat for every other system that sends from your domain, such as a CRM or billing tool. Each one can take a different route.

SPF: list Proofpoint only if it sends your mail

Add Proofpoint to SPF only when the check above shows that outgoing mail leaves through it. An SPF record lists the servers allowed to send for your domain. Proofpoint's getting-started guides for Essentials give one entry per data center.

For the US1 and US2 data centers:

TXT
v=spf1 a:dispatch-us.ppe-hosted.com ~all

For the EU1 data center:

TXT
v=spf1 a:dispatch-eu.ppe-hosted.com ~all

These guides date from 2016 and 2017. Both hostnames resolved when we checked, but confirm the value for your account with Proofpoint or your partner before you publish it. The public pages we could open give no SPF entry for Proofpoint Email Protection or Proofpoint on Demand. Ask Proofpoint for the outbound hosts of your deployment.

If your domain also sends through another server, combine everything in one record. With one extra server, it looks like this:

TXT
v=spf1 a:dispatch-us.ppe-hosted.com ip4:192.0.2.10 ~all
  1. Find your current SPF record and edit that one. Caution: a domain must have a single SPF record. Two records produce a permerror, and SPF stops working for all your mail. See how to merge multiple SPF records.
  2. Add the Proofpoint mechanism and keep every sender you still use.
  3. Count the DNS lookups. The terms include, a, mx, ptr, exists and redirect count toward a limit of 10. Going over it also produces a permerror. The Proofpoint entry uses one. See the SPF lookup limit.
  4. Keep ~all while you test. It marks unlisted senders as a softfail, a weaker result than a fail. Caution: switch to -all only after your reports show every real sender listed, because receivers may reject mail that fails SPF under -all.

SPF helps DMARC only when the domain in the envelope sender, the MAIL FROM address, matches your From domain. Under the default relaxed mode, a subdomain such as bounce.example.com also counts. This match is called DMARC alignment.

The Essentials entry is shared: the guides give one value per data center, with nothing specific to your account. SPF alone therefore cannot separate your account from another one. A DKIM signature made with your own key can.

DKIM: sign after the last change to the message

A DKIM signature is a cryptographic stamp that a receiver checks against a public key in your DNS. Proofpoint's DKIM brief states the rule: signed elements "must remain unchanged in transit, or the DKIM signature will fail authentication." A signature added by your mail platform can fail if a later system changes the body or a signed header. A footer added after signing is one example. The safest order is to sign in the last system that changes the message.

Proofpoint's administrator course for the Protection Server lists DKIM signing and the creation of authentication keys. Proofpoint's Essentials help articles require a sign-in. Check there, or ask your partner, whether your plan signs outgoing mail.

Whichever system signs, follow the same order:

  1. Create the key in the system that signs, choosing 2048-bit RSA if offered, and copy its selector. A selector identifies the DNS key. RFC 8301 requires at least 1024 bits and recommends 2048. The cited Proofpoint documents give no fixed selector. See how DKIM selectors work.
  2. Publish the public key as a TXT at selector._domainkey.example.com and confirm it resolves before enabling signing. Keep an old selector in DNS until the new one is signing successfully; removing it early breaks verification of older messages.
  3. Enable signing and send a test. Read DKIM-Signature: d= should align with From and s= should be the configured selector.

DMARC: publish your record and read the reports

Publish one TXT record at _dmarc.example.com in your own DNS and start in monitoring mode:

New policy only: use this starter value only when no valid DMARC record exists. For an existing record, keep its policy and merge the report address instead of pasting over the value.

TXT
v=DMARC1; p=none; rua=mailto:dmarc@example.com

p=none asks receivers to leave their handling unchanged. rua says where aggregate reports go. RFC 9989, the current DMARC standard, says domain owners usually start this way. A message passes DMARC when SPF or DKIM passes for a domain aligned with the From address.

  1. Check for an existing _dmarc record and edit it if there is one. Caution: if receivers find more than one record at that name, RFC 9989 says they discard all of them.
  2. If the rua address sits under a different organizational domain, that domain must publish an authorization record under _report._dmarc. Without it, receivers cannot confirm that address is authorized, and your reports may not arrive.
  3. Read the reports for several weeks. Proofpoint's DMARC page suggests at least 30 days on p=none, then another 30 on p=quarantine before you consider p=reject. Reports normally arrive as GZIP-compressed XML attachments. If the rua mailbox sits behind Proofpoint, confirm the gateway delivers them. See DMARC reports not arriving.
  4. Confirm that Proofpoint and every other sender pass with an aligned domain.
  5. Preserve existing policy during authentication. For a new policy, start at p=none and collect representative reports, which may take months. After fixing all legitimate streams, consider p=quarantine and observe reports again. Evaluate p=reject separately: it is optional, needs aligned DKIM rather than SPF alone, and RFC 9989 §7.4 advises against it when users post to mailing lists. Forwarding and list transformations need testing; receiving servers decide the final disposition.

Incoming mail: DMARC checks and Microsoft 365

Proofpoint can also apply DMARC to mail you receive. Its brief says: "Email Fraud Defense works with the Proofpoint email gateway to enforce DMARC on inbound traffic." The Protection Server course also covers DMARC policies and rules. These checks apply to mail other domains send you, and they leave your own record unchanged.

If your MX points to Proofpoint and your mailboxes are in Microsoft 365, messages reach Microsoft from Proofpoint's addresses. Microsoft says the message "adopts the source IP of the last hop" and offers Enhanced Filtering for Connectors to preserve the original source. Microsoft intends this feature for domains whose MX record does not point to Microsoft 365.

  1. In the Microsoft Defender portal, go to Email & Collaboration > Policies & Rules > Threat policies page > Rules section > Enhanced filtering.
  2. Select the inbound connector that receives mail from Proofpoint.
  3. Under IP addresses to skip, choose Automatically detect and skip the last IP address if Proofpoint is the only hop to skip. Otherwise choose Skip these IP addresses that are associated with the connector and list them.
  4. Under Apply to these users, choose Apply to a small set of users. Caution: this changes how Microsoft filters incoming mail. Test it on a few recipients before you use Apply to entire organization.
  5. Select Save.
  6. Review any mail flow rules that set the spam confidence level to -1 for mail through that connector. Microsoft says to disable them after you turn on this feature, with exceptions for evaluation mode and a phased rollout of its Defense in Depth setup.

Hosted records in Email Fraud Defense

Email Fraud Defense includes Hosted SPF, Hosted DKIM and Hosted DMARC. Proofpoint describes Hosted SPF as a DNS service for Email Fraud Defense customers. It uses SPF macros to remove the limit of 10 lookups. Hosted DKIM is free for those customers, supports TXT and CNAME records, and handles keys up to 2,048 bits. Both services have a web interface where you manage senders or selectors.

Proofpoint's Hosted SPF brief carries one warning. If that service is disrupted, domains on p=reject that do not sign and align with DKIM may have legitimate mail blocked. Proofpoint discourages that setup, so get DKIM aligned before you rely on Hosted SPF at p=reject.

Common problems

  • SPF fails on mail that left through Proofpoint. The Proofpoint entry is missing, or the MAIL FROM domain differs from your From domain. Read both in the headers of a test message.
  • DKIM passes in your mail system and fails at the destination. Something changed the message after signing. Sign in the last system that changes it, or remove the change.
  • Microsoft 365 shows authentication failures after you moved your MX to Proofpoint. Set up Enhanced Filtering for Connectors on the connector that receives mail from Proofpoint.
  • Reports list Proofpoint addresses you do not recognize. Resolve dispatch-us.ppe-hosted.com or dispatch-eu.ppe-hosted.com and compare the addresses. A match points to Proofpoint Essentials. These hostnames are not specific to your account, so check the DKIM result in the same report row to see whether the mail was yours.
  • Your mail to a Proofpoint customer is blocked. Proofpoint's postmaster page says it requires senders to implement SPF, DKIM and DMARC. It also recommends aligning the From domain with the domains authenticated by SPF and DKIM, which it notes is required for DMARC compliance. If you meet those guidelines and the problem continues, the page points to a delist request through its IPCheck tool. The same page lists 554 Blocked for an IP or domain blocked over spam or malicious activity and 421 Deferred for throttling. It also says content filtering can happen with no error returned.

Frequently asked questions

Does Proofpoint publish my DMARC record?
Only if you use Hosted DMARC, part of Proofpoint Email Fraud Defense. Otherwise you publish a TXT record at _dmarc under your domain, in your own DNS.
Do I need to add Proofpoint to my SPF record?
Only if your outgoing mail leaves through Proofpoint. An MX record that points to Proofpoint covers incoming mail and does not by itself require an SPF change.
What is the Proofpoint DKIM selector?
The Proofpoint documents we could open name no fixed selector. Read the s= tag in the DKIM-Signature header of a message your system signed.
Can Proofpoint enforce DMARC on mail I receive?
Proofpoint says Email Fraud Defense works with its email gateway to enforce DMARC on inbound traffic. That filters mail sent to you and leaves your own DMARC record unchanged.
Why does DKIM fail after mail passes through a gateway?
A signature fails when a signed part of the message changes after signing. A footer added after signing is one example. Have the last system that changes the message do the signing.
Will p=reject block mail sent through Proofpoint?
Preserve existing policy during authentication. For a new policy, start at p=none and collect representative reports, which may take months. After fixing all legitimate streams, consider p=quarantine and observe reports again. Evaluate p=reject separately: it is optional, needs aligned DKIM rather than SPF alone, and RFC 9989 §7.4 advises against it when users post to mailing lists. Forwarding and list transformations need testing; receiving servers decide the final disposition.

Sources consulted

Proofpoint: What is DMARC?
checked 2026-11-09
Proofpoint Postmaster
checked 2026-11-09

Keep it healthy

Know the moment something breaks

Point your DMARC reports to DMARC Pulse and see who sends email as your domain, what fails and why — with a calm alert when anything changes.

Free plan: 1 domain, no credit card.