ProNet Cyber

Email spoofing report for Oakfield Solicitors

oakfieldlaw.co.uk · 1 November 2026 · High risk

Someone can send email that looks exactly like it came from oakfieldlaw.co.uk, and it will reach the inbox.

This report explains, in plain English, whether someone can send email that looks like it came from oakfieldlaw.co.uk, why that matters, and the exact steps to stop it. You can hand the "How to fix it" section straight to whoever looks after your email or website — they will know what to do with it.

1. What we found

DMARC: No DMARC record was found. Nothing tells receiving mail servers to reject email that forges your address, so forged mail is delivered normally.

SPF: An SPF record exists but ends in “~all” (a soft fail). On its own, SPF does not stop someone forging your exact address in the “From” line.

Your domain's current records, for reference:

DMARC (_dmarc.oakfieldlaw.co.uk): (no record at _dmarc.oakfieldlaw.co.uk)

SPF (oakfieldlaw.co.uk): v=spf1 include:_spf.google.com ~all

2. Why it matters

Without an enforcing DMARC policy, a criminal can send an email with your exact address in the "From" line and have it land in your clients' or your staff's inbox. This is how invoice and "we've changed our bank details" fraud usually begins: the message looks genuinely like it came from you, so people trust it and pay.

Fixing it costs nothing but the right DNS settings — the hard part is knowing exactly what to put, and rolling it out without blocking your own genuine email. That is what the next section gives you.

3. How to fix it

These changes are made in your domain's DNS settings (with your domain registrar or email provider). Add them as TXT records. Do them in order — the staged DMARC rollout is deliberate, so you never block your own real email.

  1. Make sure SPF is correct. You should have exactly one SPF record, listing the servers allowed to send for you, ending in -all: v=spf1 include:_spf.google.com -all
  2. Start DMARC in "monitor" mode. Add a TXT record at _dmarc.oakfieldlaw.co.uk. This watches and reports, without changing delivery, so you can see who sends on your behalf: v=DMARC1; p=none; rua=mailto:[email protected]; fo=1 Reports come to the address in the record. Leave this for 2–4 weeks.
  3. Tighten to "quarantine". Once the reports show only your genuine senders, change p=none to p=quarantine. Forged mail now goes to spam.
  4. Tighten to "reject". After another couple of weeks, change it to p=reject. Forged mail is now blocked outright. You are protected.
  5. DKIM. Make sure DKIM signing is switched on with your email provider (Microsoft 365, Google Workspace, etc.). DMARC relies on it.

We provide the exact settings; we do not log in to or change your systems. If anything is unclear, your email provider or IT person can apply these in minutes.

4. Keep it that way — monitoring

DNS settings get changed, email providers get switched, and a protective record can be weakened or removed by accident — quietly reopening the gap. Our monitoring checks oakfieldlaw.co.uk regularly and warns you the moment your protection drops, so you find out before a criminal does.