Mail domain report: supersaas.de

SPF

pass

SPF record published

Found

Record: v=spf1 ip4:185.183.32.172 ip6:2a00:7c80:0:261::2 ip4:213.227.134.181 ip6:2001:1af8:4a00:4:3::2 ip4:62.112.10.127 ip6:2a00:7c80:0:e9::2 include:_spf.google.com include:mailgun.org -all
DNS lookups: 6 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

No ptr mechanism found in SPF record.
✓ 6 of 10 DNS lookups #2

SPF record needs 6 DNS lookups (limit is 10).
✓ Ends with -all #3

SPF record properly uses -all to restrict unauthorized senders.
✓ Record published #6

SPF record exists for this domain.
✓ Single record #16

Exactly one SPF record is published.
✓ Valid syntax #25

All SPF mechanisms and modifiers are valid.
✓ No void lookups #26

All include/redirect targets exist.
✓ No overly broad IP ranges #27

All ip4/ip6 ranges are narrow enough.

DMARC

warn

p=quarantine (_dmarc.supersaas.de)

Found

Record: v=DMARC1; p=quarantine; sp=reject; aspf=s; adkim=s;
Found at: _dmarc.supersaas.de

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
sp	reject	Subdomain policy
adkim	s	DKIM alignment (r = relaxed, s = strict)
aspf	s	SPF alignment (r = relaxed, s = strict)

Checks

!

Policy: quarantine

DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.

#4
✓ Record published #5

DMARC record exists for this domain.
✓ Valid syntax #17

DMARC record syntax is valid.
✓ Applies to 100% of mail #18

DMARC policy applies to all failing mail.
!

No aggregate reports (rua)

DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...

#19
✓ Subdomain policy: reject #20

Subdomains are covered by policy 'reject'.

DKIM

warn

Selectors: mail, google, mx

Found

Selectors: mail, google, mx
_domainkey: NXDOMAIN

Selector	Key	Flags
mail	RSA 1024 bits	test mode (t=y)
google	RSA 1024 bits
mx	RSA 1024 bits

Checks

✓ Keys found: mail, google, mx #7

DKIM keys found for this domain with selectors: mail, google, mx
!

1024-bit DKIM key

1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits), google (1024 bits), mx (1024 bits). Rotate to a 2048-bit key.

#23
!

Key in test mode

These keys have t=y, so receivers treat DKIM failures as a test: mail. Remove t=y once DKIM works.

#24

DNSSEC

warn

Not signed

Found

DNSKEY records: No (0)
DS at parent: No

Checks

!

Not enabled

DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.

#8

MX

warn

1 mail server

Found

Priority	Host	Records	Reverse DNS
1	smtp.google.com	A 142.251.127.26 A 142.251.127.27 AAAA 2a00:1450:4001:c21::1b AAAA 2a00:1450:4001:c21::1a	lcfrai-in-f26.1e100.net ✓ lcfrai-in-f27.1e100.net ✓ lcfrai-in-f27.1e100.net ✓ lcfrai-in-f26.1e100.net ✓

Checks

✓ 1 MX record #9

Found 1 MX records for this domain.
✓ All hosts resolve #10

All MX records resolve to valid IP addresses.
✓ All hosts have IPv6 #11

All MX records resolve to IPv6 addresses.
!

Single MX host, no backup

Only one MX record found. For better email reliability, consider adding at least one backup MX server.

#12
✓ At most 5 MX records #13

Found 1 MX records, which is within the recommended range (1-5).
✓ No localhost targets #14

No MX records pointing to localhost found.
✓ No private IP addresses #15

No MX records resolving to private IP addresses found.
✓ No CNAME targets #22

No MX records point to a CNAME.
✓ Reverse DNS confirmed #30

All 4 MX addresss have a PTR record that resolves back to them.

TLS

warn

no MTA-STS · no TLS-RPT · DANE on 0 of 1 MX hosts

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
smtp.google.com	none	-

Checks

!

Not configured

MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.

#32
i

Not configured

TLS-RPT lets senders report TLS delivery problems to you. It is most useful together with MTA-STS or DANE.

#35
i

Not used

No MX host publishes TLSA records. DANE lets senders verify your mail server's certificate through DNSSEC; it requires DNSSEC on the MX host's zone.

#36

BIMI

warn

https://cdn.supersaas.net/img/bimi/supersaas_bimi.svg

Found

Record: v=BIMI1; l=https://cdn.supersaas.net/img/bimi/supersaas_bimi.svg
Found at: default._bimi.supersaas.de
Logo: https://cdn.supersaas.net/img/bimi/supersaas_bimi.svg

Checks

!

No certificate (a=)

The logo is published without a Verified Mark Certificate. Gmail and Apple Mail only show BIMI logos with a VMC or CMC; Yahoo shows it without one.

#38
✓ DMARC meets BIMI requirements #39

DMARC is enforced on all mail, as BIMI requires.