Free tool
Can someone send fake emails from your company address
Without two DNS records anyone can send an email from office@yourcompany.com, and the receiving server has no grounds to reject it.
Enter the domain or a full address. We only ask public DNS. We do not visit your website or your mailbox.
What to do about it
- SPF and DMARC records are set in the domain’s DNS. Usually the company that hosts your domain or email does it, or your IT person.
- First list everything that sends email in your name. Mailbox, invoicing software, online shop, newsletter. Without this, SPF can block your own emails.
- Start DMARC in monitoring mode, and after a few weeks of reports move to spam or reject.
We do not check DKIM. Its name is known only to whoever set up the email, and guessing it on someone else’s domain is something we do not do.
How it works
- We take only the domain from the address, so office@yourcompany.com becomes yourcompany.com.
- We ask public DNS for the domain’s SPF record and the DMARC record at _dmarc.yourcompany.com. Two queries, nothing more.
- It is the same logic our free website scan uses. The result for the same domain is cached for a few hours.
Questions
- Does this show whether someone is already faking our emails
- No. We only check whether the domain has the records that make faking harder. Whether someone already sends fake emails is what DMARC reports show, once you switch them on.
- Our email is on Google or Microsoft. Is this not set automatically
- Not always. The mailbox works without these records. SPF and DMARC have to be added in the domain’s DNS, and your email provider’s help pages say what to enter.
- Can the change break our email
- It can, if SPF is missing a server that sends your invoices or newsletter. That is why you list everything that sends email first, and DMARC starts in monitoring mode.