Authentication history · 61 days observed
justeat.co.uk
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/justeat.co.uk runs.
- 2to fix
- 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.
Fix this
No record
This is the requirement no can meet for you, because it lives on your own . Microsoft rejects mail without it, and Gmail requires it above 5,000 a day.
From DMARC p=none is monitoring, not enforcementSee what this looks like →
This one needs you
Publish v=DMARC1; p=none; =mailto: with an address somebody actually . At p=none it changes nothing about delivery, and it starts the reports you need before you could safely enforce anything.
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.
No DMARC record.
No DKIM key on the selectors we probe.