Loops.so shows your domain as unverified, or your product emails fail DKIM — and you added the records on Cloudflare.
Two Loops-specific gotchas trip most people. First, Loops issues three DKIM records that are added as CNAMEs (not TXT) — you add all three, one by one. Second, on Cloudflare each of those CNAMEs must be set to “DNS only” (grey cloud, proxy OFF); if the orange proxy is on, Cloudflare rewrites the record and DKIM validation fails. Note too that Loops lets you publish a DMARC policy but has no built-in DMARC reporting — you still need your own rua= destination to actually see who's sending as you. Source: Loops Docs — Setting up your domain · verified 2026-07-18.
rua= address — Loops won't collect reports for you.No. Adding SPF includes and DKIM records (whether TXT or CNAME) only adds authentication — it never blocks mail. The only step that can affect delivery is tightening your DMARC policy to quarantine or reject, and that comes later, once reports confirm every legitimate sender passes.
Yes. Most platforms handle DKIM (and sometimes SPF) so their mail can pass, but the DMARC record is published on your own domain and controlled by you — it's what tells receivers to act on failures. Providers rarely publish it for you, and you want your own rua= address to see the reports.
Send yourself a test message and check the headers for dkim=pass and dmarc=pass — or run the free check below on your domain to see SPF, DKIM and DMARC state, and which sending services currently align, in one place.