[ Sending-service guides ]

Authenticate email sent through Yotpo: configuration and verification

Configure the documented Yotpo sending route, preserve other mail services, and verify the delivered identities before accepting the change.

By the EmailAuth research team · 5 min read

[ Key points ]

  • Configure the documented Yotpo sending route, preserve other mail services, and verify the delivered identities before accepting the change.
  • An occupied SendGrid selector needs a Support-approved alternative.
On this page
  1. Scope and prerequisites
  2. Configure the documented route
  3. Product-specific risks
  4. Prove the route at the receiving end
  5. Diagnose failures without widening access
  6. Handover and recovery
  7. Confirm the provider boundary
  8. Work through a fictional diagnostic case
  9. Separate a passing message from enforcement readiness

Scope and prerequisites

This procedure is for the Reviews and Loyalty custom-domain route described in Yotpo's CNAME authentication guide. It is not a claim that every Yotpo product, including SMS & Email, uses the same setup. The documented route uses SendGrid behind Yotpo and requires support-supplied, domain-specific records. Have the Reviews or Loyalty owner confirm the exact domain shown in the product's email settings before requesting records.

Configure the documented route

  • Step 1. Record the product, account, intended visible From domain and existing DNS ownership. Identify any other application already using SendGrid for that domain.
  • Step 2. Request the domain's CNAME set from Yotpo Reviews Support or Yotpo Loyalty Support. Give the exact email-settings domain and disclose an existing SendGrid integration so support can provide a non-conflicting record structure.
  • Step 3. Copy every supplied host and target to the authoritative DNS zone. Yotpo's illustration includes an envelope-related CNAME and two DKIM CNAMEs, but its host and value strings are unique per domain. The illustration is not a configuration for your account.
  • Step 4. Preserve record types. Do not replace a requested CNAME with a TXT record or overwrite a selector delegated to another sender. At a CNAME owner, conflicting ordinary records must be resolved before publishing the new delegation.
  • Step 5. Ask Yotpo support to validate the published records and complete activation. DNS publication alone is not the final documented step.
  • Step 6. Trigger a representative Reviews or Loyalty message after support confirms completion. Capture the resulting identities before rolling the configuration out to another product or storefront.

Product-specific risks

If the domain still fails validation, compare the DNS owner and CNAME target with the latest support-issued set, not an old screenshot. If an existing SendGrid selector is occupied, return to support for the correct alternate structure instead of deleting a working integration. A working tracking link or branded display name cannot establish DKIM alignment. Keep the support case identifier with the change record so later key or domain questions can be tied to the original delegation.

Prove the route at the receiving end

Use an approved external mailbox and save the complete raw message with its timestamp and message identifier. No live tenant test is claimed in this guide. The following is an acceptance worksheet to complete during implementation, not a record of observed results.

  • Evidence field: Visible From; What to record: Actual address and domain; Acceptance question: Is this the intended sender identity?
  • Evidence field: Envelope; What to record: Return-Path and receiver-reported SPF domain; Acceptance question: Which domain did SPF actually authenticate?
  • Evidence field: SPF; What to record: Trusted receiver result and evaluated identity; Acceptance question: Did it pass, and does that identity align?
  • Evidence field: DKIM; What to record: Every d= domain, s= selector and receiver result; Acceptance question: Does at least one passing signature align?
  • Evidence field: DMARC; What to record: Receiver result and applicable policy; Acceptance question: Does an aligned passing path exist?
  • Evidence field: Route; What to record: Product, account and message type; Acceptance question: Did the test use the production path?

DMARC needs at least one aligned, passing SPF or DKIM path. A passing signature from an unrelated service domain is not enough. Strict alignment requires exact domain equality; relaxed alignment uses the applicable organizational-domain relationship. Check the domain's actual alignment settings before declaring success. A subdomain is not an automatic strict match. SPF uses the SMTP identity, not the display name or Reply-To. Consult the alignment glossary when recording the decision.

Use Authentication-Results from the receiving system you trust, not a header supplied by an arbitrary sender. Capture all signatures rather than stopping at the first failure. For forwarded mail, compare a direct test with a forwarded copy: forwarding may change SPF evaluation or alter signed content. Do not diagnose those effects by adding the forwarder's address to your provider authorization.

Diagnose failures without widening access

Compare authoritative DNS with the exact configured record names first, then check recursive visibility and service validation. A wrong name, truncated key or conflicting CNAME is not fixed by waiting for caches. Keep only one SPF policy at an owner and check the ten DNS-lookup-term limit across evaluated includes and redirects before merging another sender. DKIM selectors belong to individual signing configurations; do not overwrite another application's record to force a validation result.

If authentication passes but delivery is poor, inspect the recipient response, reputation, content and sending permissions separately. DMARC pass does not promise acceptance or inbox placement. If neither path aligns, stop expansion and correct the actual sender configuration. Do not weaken the whole domain's DMARC policy to hide a single product failure.

Handover and recovery

Save the approved DNS diff, public lookup results, service status and redacted received-message worksheet with a named owner. Keep credentials and private keys out of tickets. On failure, pause the affected sending job or use a previously tested route under the service owner's control. Restore only the changed records that belong to this integration; keep public keys needed by in-flight messages. Retest after rollback, key rotation, domain migration or a change in outbound relay. Close the change only when the product owner and mail administrator can explain the observed identity chain.

Confirm the provider boundary

The source’s CNAME illustration is domain-specific, and its product metadata includes unfinished placeholders for other Yotpo products. Treat only the explicit Reviews/Loyalty instructions as supported here. Domain authentication delegates a sending role; it does not establish that an individual author is trusted or that every message is safe.

Work through a fictional diagnostic case

Fictional written case only: YO-01 assumes Reviews needs reviews@shop.example but s1._domainkey.shop.example already delegates to another approved SendGrid application. No Yotpo message has been captured, so envelope and DKIM results are unknown. The Reviews owner must disclose the collision to Support, obtain the domain-specific alternative set and preserve the other application before testing. A Loyalty or unrelated SendGrid sample cannot close this route. No tenant, DNS, server command or message was exercised for this case.

Separate a passing message from enforcement readiness

RFC 9989 Section 7.4 requires valid DKIM for a domain publishing p=reject and cautions about indirect-mail interoperability. A single aligned SPF result does not by itself justify a reject-policy rollout. Review all legitimate routes and policy ownership separately from this provider setup.

[ Takeaway ]

An occupied SendGrid selector needs a Support-approved alternative.

[ By role ]

What this means for you

Choose your role for practical next steps.

IT / Mail Admin

Verify identities, not green badges

For Yotpo, keep product activation, DNS visibility and receiver results as separate evidence.

Next steps

  1. Capture current authoritative records before editing.
  2. Test each distinct sender and delivery route.
  3. Retain the public evidence and a narrow rollback plan.

CISO / SecOps

Limit delegated sending authority

The Yotpo integration should have a documented domain scope and accountable owner.

Next steps

  1. Review selector and envelope ownership before delegation.
  2. Exclude credentials and private keys from handover material.
  3. Require revalidation after channel or domain changes.

Founder / Non-technical

Protect the message that matters

Assign business ownership to the Yotpo route rather than treating DNS validation as project completion.

Next steps

  1. Name the critical message type and its sender.
  2. Approve a small representative test before broader sending.
  3. Keep an operational fallback and owner for failures.

[ FAQs ]

Frequently asked questions

Can I copy the three CNAMEs in the Yotpo example?

No. Yotpo says the hosts and targets are generated per domain. Obtain your exact set from Reviews or Loyalty Support.

What if another app already uses SendGrid?

Tell Yotpo support before publishing. Its documentation explicitly calls for a different record structure in that situation.

Is the process complete when DNS resolves?

No. Yotpo asks you to return to support for validation after adding the records. Then test the actual product message.

Does this procedure cover Yotpo SMS & Email?

This guide is scoped to the Reviews and Loyalty route in the cited source. Confirm the separate product configuration before reusing any records.

What proves Yotpo mail passes DMARC?

A representative received message must have at least one passing SPF or DKIM identifier aligned with its visible From domain under the applicable alignment mode. Service verification alone is insufficient.

Can Yotpo authentication guarantee the inbox?

No. The recipient retains its own acceptance and filtering policy. Keep authentication results separate from placement and reputation evidence.

What should I save for a Yotpo handover?

Save the product route, approved DNS diff, verification status and redacted receiver evidence. Include the timestamp and sender identity, but exclude credentials and private keys.

When should the Yotpo route be retested?

Retest after a domain or selector change, relay migration, sending-channel change or rollback. Cover each distinct sender domain and representative message type.

[ Sources ]

Sources

  1. Authenticate Yotpo emails on your domain - Adding CNAME records

    Sections How to configure DNS records with Yotpo

  2. dmarc

    Sections §4.4 · §5.3.5 · §7.4

  3. spf

    Sections §4.5 · §4.6.4

  4. dkim

    Sections §3.5 · §3.6.1 · §6.1

[ Glossary ]

Glossary

Alignment
The required relationship between the visible From domain and an authenticated SPF or DKIM domain.
Selector
The DKIM signature identifier that selects a DNS public key beneath the signing domain.
Return-Path
The delivered representation of the SMTP reverse-path, useful alongside receiver results when identifying the SPF domain.

Enterprise provenance

Why top financial institutions and governments retired their email security dashboards.

Traditional email authentication platforms sell you a dashboard and ask your engineers to do the labour. In high-stakes environments, manual oversight means delayed enforcement, configuration drift and unmonitored shadow domains.

EmailAuth is the agentic email provenance platform. Our agents enforce p=reject, keep third-party senders aligned and move your domains to full RFC 9989 compliance, the new DMARC standard,, with human-in-the-loop auditability.

Governments Large enterprises Tier-1 financial institutions

SaaS · Dedicated tenancy · Air-gapped on-prem · BYOK encryption

Knowledge Base