Mail domain report: sennheiser.com

SPF

pass

SPF record published

Found

Record: v=spf1 ip4:52.35.123.36 ip4:208.75.123.0/24 ip4:160.34.204.28 ip4:210.247.232.211 ip4:185.217.45.75 ip4:185.217.45.140 ip4:185.217.45.76 ip4:85.125.245.124 ip4:85.125.245.125 ip4:84.17.184.240/28 ip4:195.25.217.68 ip4:80.190.118.0/24 ip4:80.190.129.128/25 ip4:87.106.27.67 ip4:208.79.250.0/24 ip4:208.82.174.0/24 ip4:139.138.59.249 ip4:139.138.34.246 ip4:51.116.145.35 ip4:62.55.182.68 ip4:185.217.45.16 ip4:185.217.45.17 ip4:147.160.167.0/26 ip4:23.21.109.197 ip4:23.21.109.212 ip4:35.246.188.19 ip4:34.107.41.233 include:_spf.salesforce.com include:spf.servicemail24.de include:_spf.senders.scnem.com include:servers.mcsv.net include:spf.sendinblue.com include:customers.prezly.io include:shops.shopify.com include:spf.protection.outlook.com -all
DNS lookups: 9 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 9 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.sennheiser.com)

Found

Record: v=DMARC1; p=quarantine; ruf=mailto:dmarc@sennheiser.com; fo=1;
Found at: _dmarc.sennheiser.com

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
ruf	mailto:dmarc@sennheiser.com	Failure report addresses
fo	1	Failure reporting options

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: quarantine #20

Subdomains are covered by policy 'quarantine'.
✓ Report addresses in own domain #29

All report addresses are in your own organizational domain.

DKIM

warn

Selectors: selector1, selector2, s1, s2

Found

Selectors: selector1, selector2, s1, s2
_domainkey: NOERROR

Selector	Key	Flags
selector1	RSA 1024 bits
selector2	RSA 2048 bits
s1	RSA 2048 bits
s2	RSA 1024 bits

Checks

✓ Keys found: selector1, selector2, s1, s2 #7

DKIM keys found for this domain with selectors: selector1, selector2, s1, s2
!

1024-bit DKIM key

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

#23
✓ No problematic flags #24

No keys in test mode, revoked, or limited to SHA-1.

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
10	sennheiser-com.mail.protection.outlook.com	A 52.101.168.0 A 52.101.170.2 A 52.101.170.1 A 52.101.170.0 AAAA 2a01:111:f403:ca09::28 AAAA 2a01:111:f403:ca38::a AAAA 2a01:111:f403:c967::a AAAA 2a01:111:f403:ca21::c	mail-beup281cu00100.inbound.protection.outlook.com ✓ mail-fr6p281cu00202.inbound.protection.outlook.com ✓ mail-fr4p281cu03101.inbound.protection.outlook.com ✓ mail-fr5p281cu00500.inbound.protection.outlook.com ✓ mail-am6pr02cu00300.inbound.protection.outlook.com ✓ mail-wa4pr05cu00102.inbound.protection.outlook.com ✓ mail-cpjpr05cu00102.inbound.protection.outlook.com ✓ mail-matpr04cu00204.inbound.protection.outlook.com ✓

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 8 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
sennheiser-com.mail.protection.outlook.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

info

No BIMI record

Checks

i

Not configured

BIMI shows your logo next to your mail in supporting mail clients. It requires DMARC enforcement.

#38