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@hear-me.social
@yunohost@toot.aquilenet.fr I think it is ok:
https://doc.yunohost.org/fr/dns_config

But in case of ⬆️

permalink
report
reply
2 points

Yeah I regularly get DMARC reports for domains I’m not using. For ease I just added them as an alias to an Google workspace account I already have and use the DKIM, DMARC etc that Google provides. In case I ever need to send an email with that domain

permalink
report
reply
1 point

@Jerry@hear-me.social thank you sir

permalink
report
reply

@Jerry@hear-me.social Can you undo this later without consequence?

permalink
report
reply
1 point

@daniel@masto.doserver.top
Should be able to.

permalink
report
parent
reply

@Jerry@hear-me.social (Just thinking from a cache perspective)

permalink
report
parent
reply
1 point

@daniel@masto.doserver.top
I’ve never had issues making changes, so I think it wouldn’t be an issue. The caches should recognize they need updating.

permalink
report
parent
reply
2 points

@Jerry@hear-me.social If I change my mind and I want to send e-mails from the domain: Can I expect that this will work, if I change the DNS records file again and wait for TTL seconds? Or will this take considerably longer?

permalink
report
reply
1 point

@nimi@norrebro.space
Hi,

Depending on the ISP, after making the changes, it usually takes up to 15 minutes for the changes to get distributed to all the DNS servers worldwide. It’s pretty quick.

permalink
report
parent
reply

Cybersecurity

!cybersecurity@fedia.io

Create post

An umbrella community for all things cybersecurity / infosec. News, research, questions, are all welcome!

Rules

Community Rules

  • Be kind
  • Limit promotional activities
  • Non-cybersecurity posts should be redirected to other communities within infosec.pub.

Community stats

  • 706

    Monthly active users

  • 39

    Posts

  • 116

    Comments