Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wildcard DMARC report destination #142

Open
kazet opened this issue Jul 31, 2024 · 2 comments
Open

Wildcard DMARC report destination #142

kazet opened this issue Jul 31, 2024 · 2 comments

Comments

@kazet
Copy link
Contributor

kazet commented Jul 31, 2024

Hello,

The RFC says that:

A Report Receiver that is willing to receive reports for any domain can use a wildcard DNS record. For example, a TXT resource record at "*._report._dmarc.example.com" containing at least "v=DMARC1" confirms that example.com is willing to receive DMARC reports for any domain.

There are two possible interpretations of this paragraph. One is that to allow receiving reports from all domains the recipient domain should add a wildcard DNS record (not with a literal asterisk in the domain name) so that a query for any domain under _report._dmarc will return the same.

The second interpretation is that a DNS record with a literal asterisk should be added. Checkdmarc (and opendmarc) is checking for a domain with a literal asterisk. Are you sure this is a correct behavior?

@seanthegeek
Copy link
Contributor

The Wikipedia article on wildcard DNS records states that a wildcard DNS record has a * at the leftmost part of the hostname, which is the same as what we are checking with .*_report._dmarc.example.com, so I don't see the distinction you are making,

@kazet
Copy link
Contributor Author

kazet commented Aug 6, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants