For Meghan Farrar
You have been apologising for this on your own contact page for years. Nobody seems to have measured it for you, so I did, on September 25, 2026, straight at your authoritative nameserver rather than through a checker that caches. Here is everything I found, including the part that weakens my own case.
“If you haven't had a response in 24 hours - please check your SPAM folder. If no email there (send help - somethings wrong lol) please text us 703-283-9827 or email us directly.”
Your contact page, live today
What your domain publishes
Read from ns13.wixdns.net, your own nameserver. You can run every one of these yourself in a terminal, or paste the domain into any public DNS checker and get the same answers.
| Record | What is published | Verdict | What it means |
|---|---|---|---|
| SPF | v=spf1 include:_spf.google.com ~all |
Fine | Present and correct. It authorises Google to send as your domain, and nothing else. |
| DKIM | Nothing, on 17 common selectors including Google\’s own |
Missing | Google Workspace ships DKIM switched off. You have to generate the key and publish it yourself, and almost nobody is told that. |
| DMARC | No record at all |
Missing | Nothing is watching. Without it you have no way of seeing what is failing, or who is sending as you. |
| MX | Google, answering on port 25 right now |
Fine | Your mail infrastructure is live and healthy. This is not the problem. |
| MTA-STS, TLS-RPT, BIMI | Not published |
Note | Optional extras. Worth having one day, not causing anything today. |
| DNS host | Wix (ns13.wixdns.net) |
Note | Good news: you already have the login, and these are a form in your dashboard. No transfer, no registrar, no developer. |
The part I have to walk back
Here is where I have to walk something back. Since February 2024 Google requires every sender to have SPF or DKIM, and requires both plus DMARC only of bulk senders at five thousand messages a day. You have SPF. You are not a bulk sender. So you meet Google\’s stated minimum, and the missing records are very unlikely to be the whole story on their own. They weaken you, and they should be fixed, but I am not going to tell you they are the cause when I cannot show that.
Source: Google Workspace Admin Help, Email sender guidelines.
Three things it could be
I cannot tell which of these is true from outside your account, so I am not going to pretend I can.
01
Most likely, given it is the address you publish everywhere.
Then none of the records above touch your replies at all. Google signs consumer Gmail under gmail.com and it authenticates fine. The cause would be something else: links, attachments, an image-heavy signature, or simply that the couple has never written to you before.
What it would mean. Rules out the DNS gap as the cause. Points at message content.
02
Plausible: your domain has Google mail records, so a mailbox probably exists.
Then the missing DKIM matters a great deal. Your replies would be carrying one authentication signal where they could carry two, and a receiving mail server has less reason to trust them.
What it would mean. Makes DKIM the first fix, and it is a ten minute job.
03
Common, easy to set up years ago and forget, and the worst of the three.
Your message would say it is from your domain while being sent in a way your domain does not vouch for. That is the exact shape spam filters are built to catch, and it would explain a persistent problem that never quite gets bad enough to bounce.
What it would mean. Makes DKIM urgent, and explains why it has gone on this long.
One question settles it: when you reply to a couple, does the message come from the gmail address or from one at farreverafterevents.com? That is the whole diagnosis.
What to actually do
Google Workspace, Apps, Google Workspace, Gmail, Authenticate email. It generates a key, you paste one record into Wix. Ten minutes, and it is worth doing whichever of the three turns out to be true.
A record of v=DMARC1; p=none; rua=mailto:you@\… changes nothing about how your mail is treated. What it does is start the reports.
Within a few days they name every system sending as your domain and whether each one passes. That is how you find out whether it is Wix, a send-as alias, or nothing to do with your domain at all. The diagnosis and the first step of the fix are the same action.
Once the reports are clean you can move DMARC to quarantine. Doing that first, before you know what is sending as you, is how people accidentally send their own mail to spam.
What I did not do: submit a fake inquiry through your form to catch your reply and read its headers. It would have answered this in one afternoon and it would also have wasted your time, and you answer those personally.
Next
Every step above is yours to do, in a dashboard you already have a login for. If you would rather I did it with you, say the word.