Site AI Auditod Internet Solutions

Site AI Audit for Businesses That Send Invoices by E-mail

21 listopada 2026Czas czytania: 8 minDostarczalność e-maili
Site AI Audit for Businesses That Send Invoices by E-mail

Short answer: A business that sends invoices, quotes or payment links by e-mail is a target: anyone can write a message that appears to come from your address, unless your domain says otherwise. Site AI Audit checks the records that say otherwise, which are MX, SPF, DKIM and DMARC, and lists what is missing or weak in its E-mail area. The order of work is simple: fix SPF, switch on DKIM, publish DMARC in monitoring mode, read the reports and tighten the policy step by step.

Why invoices are a special case

Most e-mail abuse is noise. Invoice fraud is targeted. A criminal sends a customer a message that looks exactly like your invoice, with your name, your logo and a changed bank account. Or the criminal writes to your accountant in the name of a supplier. Because the amounts are real, the damage can be large, and because the message looks right, nobody is suspicious. The article on invoice fraud by e-mail describes how these attacks work.

E-mail was built without a check of the sender’s name. The From address of a message can be written freely. SPF, DKIM and DMARC were added later to close this gap, and they only work if the owner of the domain publishes them. When a domain has none, receivers have no way to tell a real message from a fake one. When a domain has them, a receiver can reject or quarantine fakes, and the customer never sees them.

What the audit checks for your domain

The E-mail area of the report looks at the DNS records of your main domain. The findings, with their severity, are:

Together, they tell you how easy it is to impersonate you. The article on Site AI Audit e-mail checks explains each check, and the e-mail area is 15 percent of the overall score.

The order of work

1. SPF: list who may send

SPF is the list of servers that may send mail for your domain. Publish one record that includes your mail provider and every other service that sends in your name, such as an invoicing system or a newsletter tool, and end it with ~all or -all. Keep to one record, and stay within ten lookups. See the articles on the SPF findings and on the lookup limit.

2. DKIM: sign the messages

DKIM adds a digital signature to every message, which a receiver checks against a public key in your DNS. It proves that the message was not changed on the way, for example that nobody replaced the bank account in your invoice. Turn on DKIM signing in your mail provider and in your invoicing tool, and publish the keys they give you. The audit looks for keys at common selector names. Your provider may use another name, so the notice can be a false alarm, as the article on the DKIM finding explains.

3. DMARC: tell receivers what to do

DMARC ties SPF and DKIM to the address people see in the From line and tells receivers what to do when a message fails. Start with p=none and a report address, read the reports for two to four weeks, fix any legitimate sender that fails, and then move to quarantine and finally reject. The articles on the missing DMARC record and on monitoring mode and reports describe the steps.

Make sure every system that sends invoices is covered

Invoices rarely leave from the same place as ordinary mail. List every system that sends e-mail with your domain in the From address:

Each of these either goes into SPF, signs with DKIM or both. A system that is forgotten will start to fail once your DMARC policy gets stricter, which is why the monitoring phase is important. Some invoicing tools offer to send on your behalf from their own domain, with your name in the display. That is safe for DMARC, but a message with your own domain in the From address needs the steps above.

What to tell customers

Authentication protects against fake mail that uses your domain. It does not protect against a criminal who registers a similar domain, for example one with an extra letter. For that, give customers a few habits: your invoices always come from the same address, your bank details never change by e-mail alone, and a change is always confirmed by phone with a person they know. Put this in a short line at the bottom of your invoices. It costs nothing and stops a real share of attempts.

Common traps for small businesses

None of this needs a specialist for a small business. It needs an hour with the DNS panel, a list of your senders and the audit report next to you, and it is worth doing once and then re-checking after every change of mail provider.

Daily checks on the Business plan

Records can disappear when someone changes the DNS provider or edits a zone. On the Business plan, Site AI Audit runs a daily check of the SSL certificate and of the SPF and DMARC records, and sends an alert if a record that was there has vanished. The article on the Business plan explains what is checked and when you are alerted. For a company whose invoices go by e-mail, this is a cheap way to avoid a gap that nobody notices for weeks.

Review your setup whenever something changes: a new mail provider, a new invoicing tool, a new web shop or a new domain. Each change is a moment when a record can be lost or a sender can be forgotten, and a quick audit afterwards takes a minute and confirms that your protection is still in place.

A worked example

A small building contractor sends quotes and invoices from an accounting program and answers customers from a mailbox. His audit shows a critical finding, no DMARC record, a critical finding, two SPF records, and a notice, no DKIM key found. His IT helper merges the two SPF records into one that includes the mailbox provider and the accounting program, turns on DKIM in both and publishes a DMARC record with p=none and a report address. After three weeks, the reports show a contact form tool that also sends as the domain and fails. It is added to SPF, and the policy is moved to quarantine. A new audit shows no critical e-mail findings, and the contractor adds a line about bank details to his invoice template.

To see how your own domain stands, run a Site AI Audit with a free account. The plans unlock the full report and the instructions for each finding.

Related reading

The bottom line

If invoices go by e-mail, authenticate your domain. Fix SPF, switch on DKIM, start DMARC in monitoring mode, read the reports and tighten the policy, and tell customers never to trust bank detail changes by e-mail alone. Run the audit to see where you stand.

FAQ

Can SPF, DKIM and DMARC stop all fake invoices?

They stop fake mail that uses your exact domain. They cannot stop a look-alike domain, so customer habits matter too.

Which finding should I fix first?

The critical ones: a missing or multiple SPF record, a missing DMARC record, and an SPF record over the lookup limit.

Will DMARC reject block my own invoices?

Only if a system sending them is not covered by SPF or DKIM. That is why you read the reports before tightening the policy.

Does the audit read my e-mail?

No. It reads the public DNS records of your domain, not any messages.

How can I be told if a record disappears?

The Business plan checks the SPF and DMARC records daily and alerts you when one that was present is gone.

#Email Authentication#Email Security#Website audit
Sprawdź własną witrynę.Czy Twoja strona jest chroniona przed włamaniem?
Sprawdź stronę
Internet Solutions

Więcej od naszego zespołu

Stworzone przez Internet Solutions. Wypróbuj nasze pozostałe produkty — każdy oszczędza czas na swój sposób.

internet-solutions.net ↗