Needs work, with 4 things to fix

myfritz.net scored 64/100 (grade C). The main issues are no DKIM key found for the common selectors and DMARC alignment: DKIM alignment is unlikely under adkim=s, plus 2 more.

Checked 2026-10-04 02:02 UTC · fresh check

1 passed4 need attention0 failing3 for information

Fix this firstThe change with the biggest effect

Set up a DMARC report address

Without a rua address nobody receives aggregate reports, so you cannot see who sends as myfritz.net or tell when it is safe to tighten the policy. Adding reporting does not change how receivers treat your mail.

Applies to: _dmarc.myfritz.net

Get an address that collects DMARC aggregate reports: add myfritz.net to MailVakt to receive one, or sign up with any DMARC report service. 2. Edit the TXT record at _dmarc.myfritz.net and add rua=mailto:<that address>, keeping every other tag (p=reject, sp=reject) as it is. 3. A report service on another domain must authorize myfritz.net; most publish that record for you.

All checks

MXCan servers find your inbox?No issues foundPass

Nothing to report.

SPFWho may send as you?SPF ends in softfail (~all)Info

Info: SPF ends in softfail (~all)
"~all" is common and works well with DMARC. "-all" is stricter; switch when you are sure every sender is listed.

DKIMAre your emails signed?No DKIM key found for the common selectorsNeeds attention

Warning: No DKIM key found for the common selectors
None of the 47 selectors probed under myfritz.net publish a DKIM key. DNS cannot list selectors, so a key under a custom selector may exist: find the s= value in the DKIM-Signature header of a message you sent and check that selector. If DKIM is not set up, enable it at each service that sends mail for myfritz.net.

DMARCWhat happens to fakes?No DMARC aggregate report addressNeeds attention

Warning: No DMARC aggregate report address
Without a rua address you receive no aggregate reports, so you cannot see who sends as your domain or safely tighten the policy.
How to fix this
Info: DMARC uses strict alignment
With adkim=s or aspf=s the DKIM d= domain or the bounce domain must equal the From domain exactly; a subdomain is not enough. Third-party senders that sign or bounce from a subdomain (or their own domain) will then fail DMARC unless they are configured to use your exact domain.

AlignmentDoes it match your From?DKIM alignment is unlikely under adkim=sNeeds attention

Warning: DKIM alignment is unlikely under adkim=s
This is a heuristic. No DKIM key was found at myfritz.net under the selectors we probed, and adkim=s requires the signing d= domain to equal myfritz.net exactly. If your mail is signed with a provider's domain or a subdomain, DKIM will not align. A key may exist under a selector we did not try; send a test message to confirm.

BIMICan inboxes show your logo?BIMI logo is not a valid small SVGNeeds attention

Warning: BIMI logo is not a valid small SVG
The file at https://myfritz.net/static/images/icons/bimi.svg must be an SVG (content-type image/svg+xml) of at most 32 KB; got image/svg+xml and more than 32768 bytes.

MTA-STSIs mail to you encrypted?No MTA-STS recordInfo

Info: No MTA-STS record
No MTA-STS record at _mta-sts.myfritz.net. MTA-STS (RFC 8461) makes sending servers require TLS and a valid certificate when delivering to you, which blocks downgrade attacks.
How to fix this

TLS-RPTWill you hear about failures?No TLS-RPT recordInfo

Info: No TLS-RPT record
No TLS reporting record at _smtp._tls.myfritz.net. TLS-RPT (RFC 8460) tells senders where to send daily reports about failed encrypted deliveries to you.
How to fix this

Other fixes

Publish the MTA-STS recordTXT

Tells sending servers that myfritz.net publishes an MTA-STS policy at https://mta-sts.myfritz.net/.well-known/mta-sts.txt. Change the id whenever the policy file changes.

TypeTXT

Name / Host

_mta-sts.myfritz.net

Some DNS providers want just “_mta-sts” here.

Value

v=STSv1; id=202610040202

Host the MTA-STS policy filepolicy-file

Serve this file over HTTPS with a valid certificate for mta-sts.myfritz.net. It lists your MX hosts and starts in testing mode; switch to mode: enforce once TLS-RPT reports show no failures.

Location

https://mta-sts.myfritz.net/.well-known/mta-sts.txt

Contents

version: STSv1
mode: testing
mx: mail1.myfritz.net
mx: mail2.myfritz.net
max_age: 604800

Set up a TLS report addressinstruction

Sending servers will report TLS failures when delivering to myfritz.net, which you need before enforcing MTA-STS. The address must accept TLS reports; a DMARC report address does not necessarily do so.

Applies to: _smtp._tls.myfritz.net

Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@myfritz.net, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.myfritz.net with the value v=TLSRPTv1; rua=mailto:<that address>.