Authentication history · 60 days observed
represent.com
Observed from 4 Aug 2026 to 3 Oct 2026. Nothing published in DNS has moved in that window.
Where it stands today
Live lookup, 3 Oct 2026. The same check /check/represent.com runs.
- 1to fix
- 1fine
- 1context
Fix this
No record
Gmail requires from , and Outlook rejects unauthenticated mail outright with 550 5.7.515. Without SPF you are failing both.
From Gmail enforces authentication, PTR, TLS and a 0.30 percent spam rateSee what this looks like →
This one needs you
Publish one TXT record at the root of the domain. Start with ~all while you are still finding out what sends as you, and tighten to -all only once the reports are quiet.
Looks fine
present with p=quarantine
A policy that actually instructs receivers, which is more than most senders publish.
v=DMARC1; p=quarantine; adkim=r; aspf=r; rua=mailto:dmarc_rua@onsecureserver.net;
From DMARC p=none is monitoring, not enforcementSee what this looks like →
Context
No key found on the selectors we know
This is inconclusive, not a failure. selectors cannot be listed from , so we probed the common ones for Klaviyo, Google, Microsoft, Mailchimp, SendGrid and Postmark. A custom selector will not show up here.
From DKIM passing is not DKIM alignedSee what this looks like →
What has moved
One entry per day a published record actually changed. Days we looked and found nothing different are counted, not listed.
First observation — what was already published
No SPF record.
DMARC published.
v=DMARC1; p=quarantine; adkim=r; aspf=r; rua=mailto:dmarc_rua@onsecureserver.net;
No DKIM key on the selectors we probe.