A quick checkup on your email setup. No strings attached.
By Yanna-Torry Aspraki, Deliverability Specialist & Founder, Review My EmailsQuick summary of every check. Click a row to jump straight to the detail below.
From public DNS alone we can see three services touching driftwoodprovisions.com mail: Google Workspace for corporate inbox, Klaviyo for marketing campaigns, and SendGrid for transactional sends (order confirmations, shipping notifications, account alerts). There may be others we cannot see from DNS, because DKIM selectors are arbitrary names and only the sender knows them. If you have something like Attentive, Postscript, or another platform in the mix that we missed, let us know.
The most actionable gap is the DMARC record. It exists, which puts you ahead of most, but it is set to p=none with no reporting address. That means you have a policy published but no enforcement and no visibility. You cannot see who is sending as driftwoodprovisions.com right now, whether that is your own services or someone spoofing you. Adding a reporting address is the single highest-value DNS change you can make today.
The UCEPROTECT listing is a secondary signal. It does not hit your inbox placement directly, but it is telling you something about your list. Domains land on UCEPROTECT when their outbound mail touches spamtrap addresses, and that usually traces back to list quality. If your subscriber list has segments that have been quiet for a while, those are the segments most likely to contain addresses that have rolled over into traps.
We ran a sample of 103,247 subscriber addresses through our validation engine. The results show 47% safe to send, 28% worth monitoring, and 25% that should be suppressed before your next campaign. The list cleaning analysis includes per-provider warmup recommendations, label-by-label breakdown, and a few addresses we flagged for a human look.
Your DMARC is set to p=none with no rua reporting address. That means the policy provides zero enforcement AND zero visibility. You have a DMARC record on paper, but no way of seeing who is currently sending as your domain, whether legitimate or spoofed.
DMARC has three policy levels: "none" (monitor only), "quarantine" (send suspicious emails to spam), and "reject" (block them entirely). You are at the first level, which is fine as a starting point. But without a reporting address (rua=mailto:...), you are not even getting the monitoring data. Every day, Gmail, Outlook, Yahoo, and others are generating DMARC reports for your domain and trying to send them to you, but there is nowhere for them to go.
The first step is adding a reporting address so you can see who is sending as your domain. Free DMARC receivers exist if you do not want to self-host a parser. Once you have 2 to 4 weeks of reports and have confirmed all legitimate senders are passing, move to p=quarantine. After another observation period, move to p=reject.
Use the DMARC generator below to build the record with a reporting address included.
Your SPF record uses ~all (soft fail) instead of -all (hard fail). This means unauthorized senders are flagged as suspicious but not necessarily blocked. With three legitimate services already listed in your SPF, tightening to -all is safe.
driftwoodprovisions.com appears on UCEPROTECT Level 1. UCEPROTECT is not a list that Gmail or Outlook consult directly, so the immediate inbox placement impact is low. But the reason domains end up on it is worth knowing.
With a 103K subscriber list that has segments dating back several years, re-engagement needs to be deliberate. Sending to the full list at once after a period of low activity will trigger volume spike alerts at every major mailbox provider.
Quick wins pulled from the opportunities above. You or your IT person can knock these out in an afternoon.
Add a DMARC reporting address (rua=) so you can see who sends as your domain. Then move from p=none to p=quarantine.
See the detail→Switch SPF from ~all to -all after confirming all senders pass via DMARC reports.
See the detail→Validate your subscriber list to find and remove addresses that may be feeding spamtrap hits.
See the detail→Segment by engagement recency. Send to warmest 90-day group first. Ramp volume gradually with a consistent mix of good and uncertain addresses in every batch.
See the detail→Where next
I offer a free 30-minute call where I go through each finding, answer your questions, and help you figure out next steps. Nothing urgent, no pressure, just a conversation about your email setup.
If this checkup saved you some time or helped you catch something, feel free to leave a tip. It helps us keep doing free stuff like this.
Leave a TipTell us what is wrong. We read every one.
Every check, every source, named and dated.
We will take this down within 24 hours. No questions asked.
I enjoy digging into this stuff. If any of this was useful, I'm glad I took the time to put it together. Email deliverability is one of those things that quietly drifts in the background. Hope this catches things before they become a problem.
If you have any questions at all, even just "what does this mean," feel free to reach out. Happy to help.
