Scanning your domain…
Checking SPF, DMARC, DKIM, MX, DNS, blacklists and domain & SSL expiry. A domain we haven't scanned before takes a few seconds — hang tight.
Checking SPF, DMARC, DKIM, MX, DNS, blacklists and domain & SSL expiry. A domain we haven't scanned before takes a few seconds — hang tight.
Scanned Nov 7, 2026 15:24 UTC · 7 checks · public report
Solid base — three policy steps remain.
stegs.uk publishes DMARC with p=none — spoofed mail is monitored but not blocked.
Your SPF check is using a soft-fail ending, which means servers are told to treat unknown senders as suspicious but not to fully reject them. This usually still works with DMARC, but it is a little less strict than a hard-fail setup. If you want to tighten protection, the fix is to switch to a hard-fail ending only after you have confirmed every legitimate email sender is included.
v=spf1 include:zoho.eu Your domain has DMARC set up, but it is only in monitoring mode, so it does not tell receiving mail servers to block or quarantine fake messages. That matters because it leaves your domain more exposed to spoofing and phishing attacks that pretend to come from you. The fix is to change DMARC from monitoring-only to an enforcement mode so unauthorised mail is filtered or rejected.
What DNS shows against each provider's published rules. Not a compliance verdict.
All 4 met
We email you a link to the full report, with every finding and fix. Opening it signs you in to a free account and starts a 14‑day Monitor trial. No card, and you can unsubscribe in one click.
Check SPF, DMARC, DKIM, MX, DNS health, blacklists and domain & SSL expiry in one free scan, with the exact record to paste for each problem it finds.
Domain owner? Re-scan any time, or email hello@dnsdoctor.dev to have this page removed.
v=DMARC1; p=none; rua=mailto:mail@stegs.me.uk; ruf=mailto:mail@stegs.me.uk; sp=none; adkim=r; aspf=rYour DKIM setup is using a weaker 1024-bit signing key, which is easier to attack than a stronger modern key. This matters because it can reduce trust in your outgoing email and make it more likely to be tampered with or rejected by stricter mail providers. The fix is to update your email service’s DKIM settings to use a stronger key, usually 2048-bit, and then publish the new DNS change they provide.
All 4 met
All 3 met
All 3 met
Send one real email and see how Gmail, Yahoo, Outlook and Apple are likely to treat it.DNS can't show these 4. One real message can.
Send a test emailSpam complaint rate stays under 0.3%Only each provider's own sender tools show this. All senders at Gmail, Yahoo.
How we read these: sender rules in our methodology. Each provider's rules: Gmail · Yahoo · Outlook · Apple