elgarde / research

The “new IBAN” email: how deposit fraud works, and three DNS records that stop it

An email from your landlord's real address asks you to send the deposit to a new account. Why that is easy to fake, and how a company can prevent it.

The message looks routine. It comes from the agency’s usual address, mentions the right flat and the right amount, and says one thing has changed: “our bank details have been updated, please use the IBAN below for the deposit.” The tenant pays. The money lands in an account opened for this one purpose and is gone within hours.

Investigators call this business email compromise, or payment diversion fraud. It works especially well in real estate, where people send large one-off transfers to someone they have never met, under time pressure, by email.

Why the sender address proves nothing

Email was designed in the early 1980s, when nobody had to prove who they were. The “From:” line you see is text written by the sending program. Unless the owner of a domain publishes instructions saying otherwise, any server on the internet can send a message that says From: rent@your-agency.pt, and the receiving mailbox will usually deliver it like any other.

Nobody had to break into the agency’s systems for this. The agency simply never told the world which mail really comes from it.

The three records

Three public DNS records fix this. They cost nothing, and once they are set up correctly, legitimate mail keeps arriving as before.

  1. SPF lists the servers allowed to send mail for the domain, for example Google Workspace or Microsoft 365 plus the newsletter tool. It ends with -all or ~all, which tells receivers that any other server is not authorised.
  2. DKIM adds a cryptographic signature to every outgoing message. The receiver checks it against a public key in DNS, and a forger cannot produce a valid one.
  3. DMARC tells receivers what to do when a message claims to come from your domain but fails SPF and DKIM: p=none (deliver it and send a report), p=quarantine (put it in spam) or p=reject (refuse it). This is the record that actually protects you.

The common mistake is to stop halfway. With p=none, DMARC only monitors, and forged mail still reaches the inbox. The same happens when the policy covers only part of the traffic, for example pct=25. Many domains that “have DMARC” can still be impersonated.

Check a domain

Type any company domain below. The check reads the same public records a receiving mail server reads and shows whether the domain asks receivers to reject mail that falsely uses its name.

Runs entirely in your browser via public DNS-over-HTTPS (Cloudflare, Google). Nothing is sent to us. Passive lookup only: no mail is sent and nothing is probed. The result describes the domain's public DNS configuration at the moment of the check; it is not a security audit of the company.

What to do

If your company receives payments by bank transfer:

  • Publish SPF and DKIM for every service that sends mail in your name. Then move DMARC from p=none to p=quarantine and finally to p=reject, reading the DMARC reports in between so you don’t block your own invoices.
  • Tell clients in writing, at the start, that your bank details will never change by email.
  • Register the obvious lookalike domains (your-agency.com, youragency.pt) before someone else does.

If you are the one paying:

  • Treat any change of bank details as suspicious until you confirm it by phone, on a number you already had and not the one in the email.
  • Since October 2025, banks in the euro area must run a Verification of Payee check before a transfer and show whether the name you typed matches the account holder. If the result is “no match” or “close match”, stop.
  • If you have already paid, call your bank immediately and ask them to recall the transfer. The first hours matter.

A spoofed sender is the cheapest version of this attack. A hijacked mailbox, a lookalike domain or a compromised invoicing system takes more than three DNS records to stop, and that is what we test.

Contact

hello@elgarde.eu

Tell us what worries you. We reply within one business day, in English or Portuguese.