Email domain check.Can anyone pretend to be you?
Criminals send fake invoices and password resets that look like they came from your domain. Three DNS records stop them. We check all of them, plus your mail servers and DNSSEC.
example-bakery.co.uk
Good start. A couple of things to tighten.
SPFPass
SPF in place (soft fail). Good. Pair it with a DMARC policy so failures get rejected.
v=spf1 include:_spf.google.com ~allDMARCImprove
DMARC is monitoring only. p=none collects reports but lets fake email through.
v=DMARC1; p=none; rua=mailto:[email protected]How to fix: When reports show only your real senders, change p=none to p=quarantine, then p=reject.
DKIMPass
DKIM key found (selector "google"). Your email is signed, so changes in transit can be detected.
google._domainkey.example-bakery.co.ukMXPass
1 mail server found. Your domain receives email.
1 smtp.google.com.DNSSECImprove
DNSSEC is off. Less common for small businesses, but it stops DNS tampering.
How to fix: Turn on DNSSEC with your domain registrar or DNS host (often one click).