Important reminder, if you own a domain name and don't use it for sending email.

There is nothing to stop scammers from sending email claiming to be coming from your domain. And the older it gets, the more valuable it is for spoofing. It could eventually damage your domain's reputation and maybe get it blacklisted, unless you take the steps to notify email servers that any email received claiming to come from your domain should be trashed.

Just add these two TXT records to the DNS for your domain:
TXT v=spf1 -all
TXT v=DMARC1; p=reject;

The first says there is not a single SMTP server on earth authorized to send email on behalf of your domain. The second says that any email that says otherwise should be trashed.

If you do use your domain for sending email, be sure to add 3 records:
SPF record to indicate which SMTP server(s) are allowed to send your email.
DKIM records to add a digital signature to emails, allowing the receiving server to verify the sender and ensure message integrity.
DMARC record that tells the receiving email server how to handle email that fails either check.

You cannot stop scammers from sending email claiming to be from your domain, any more than you can prevent people from using your home address as a return address on a mailed letter. But, you can protect both your domain and intended scam victims by adding appropriate DNS records.

UPDATE: The spf and the dmarc records need to be appropriately named. The spf record should be named "@", and the dmarc record name should be "_dmarc".

Here's what I have for one domain.

One difference that I have is that I'm requesting that email providers email me a weekly aggregated report when they encounter a spoof. gmail and Microsoft send them, but most providers won't, but since most email goes to Gmail, it's enlightening when they come.

#cybersecurity #email #DomainSpoofing #EmailSecurity #phishing

@Jerry No-email [inbound] domains should also set a "null MX", per RFC7505:

https://www.rfc-editor.org/rfc/rfc7505.html

MX 0 "."

RFC 7505: A "Null MX" No Service Resource Record for Domains That Accept No Mail

@tychotithonus @Jerry
Important: the preference number should be 0.

RFC 7505 indicates "no-email" inbound; it's a way for your domain to tell the rest of the world that it does not accept any email from outside.

Don't use it on a domain that's supposed to be hosting the email address in a DMARC 'rua' value.

@dec23k

Oof, finger-memory typo - will fix, good catch

@Jerry

@tychotithonus @Jerry
It will probably work OK with 10 - that's supposed to be a relative number, for when there's more than one MX record and a "main MX / backup MX" disposition is desired.

As with line numbers in BASIC, the default is 10 to allow for numbers to be added above and below.

The important part is the null host (single dot).
But I wouldn't want to rely on every other mail server interpreting that correctly.

@dec23k @tychotithonus
My DNS provider doesn't allow just a dot. Many don't. But saying nobody is allowed to send emails for me (SPF record) should cover it.
@Jerry @tychotithonus
The last time I tried it on Cloudflare (more than a year ago) they didn't support it.
But I moved away from them so _/shrug\_
@dec23k @Jerry
For others, could be worth opening a ticket with providers for it, mentioning the RFC. And probably other platforms don't support it. Gotta blaze the trail. 😁