Mail domain report: phoenixcontact.com

SPF

pass

SPF record published

Found

Record: v=spf1 ip4:62.157.123.119 ip4:155.56.208.100/30 ip4:157.133.97.216/30 ip4:169.145.66.70/31 ip4:169.145.66.72/31 ip4:109.75.185.63 ip4:109.75.185.66 include:spf.protection.outlook.com ip4:149.208.233.125 ip4:10.99.164.3 ip4:10.99.164.7 ip4:62.157.123.72 ip4:62.157.123.74 ip4:85.10.214.4 ip4:198.207.147.224/27 ip4:204.239.0.224/27 ip4:216.230.14.224/27 ip4:18.184.132.155 ip4:18.198.57.255 ip4:44.195.150.103 ip4:3.90.132.252 ip4:49.12.8.69 ip6:2a01:4f8:c17:390a::1 ip4:195.201.11.236 include:spf.u2d.de include:amazonses.com include:_spf.senders.scnem.com include:mail.zendesk.com include:aspmx.pardot.com ip4:194.156.135.1 ip4:46.183.40.225 ip4:164.128.172.0/28 include:_spf.salesforce.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

pass

p=reject (_dmarc.phoenixcontact.com)

Found

Record: v=DMARC1; p=reject; sp=reject; rua=mailto:pxc-dmarc-rua@phoenixcontact.com; aspf=r
Found at: _dmarc.phoenixcontact.com

Tag	Value	Meaning
v	DMARC1	Version
p	reject	Policy
sp	reject	Subdomain policy
rua	mailto:pxc-dmarc-rua@phoenixcontact.com	Aggregate report addresses
aspf	r	SPF alignment (r = relaxed, s = strict)

Checks

✓ Policy: reject #4

DMARC policy is set to 'reject', which provides the strongest protection against email spoofing.
✓ 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.
✓ Aggregate reports enabled #19

Aggregate reports are sent to: mailto:pxc-dmarc-rua@phoenixcontact.com
✓ Subdomain policy: reject #20

Subdomains are covered by policy 'reject'.
✓ 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 2048 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). 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
0	phoenixcontact-com.mail.protection.outlook.com	A 52.101.73.155 A 52.101.103.140 A 52.101.73.153 A 52.101.68.10 AAAA 2a01:111:f403:ca38::a AAAA 2a01:111:f403:ca09::26 AAAA 2a01:111:f403:ca04::9 AAAA 2a01:111:f403:ca04::4	mail-am7pr02cu00203.inbound.protection.outlook.com ✓ mail-miypr02cu00204.inbound.protection.outlook.com ✓ mail-as8pr05cu00401.inbound.protection.outlook.com ✓ mail-dbbpr03cu00102.inbound.protection.outlook.com ✓ mail-wa4pr05cu00102.inbound.protection.outlook.com ✓ mail-am8pr83cu00106.inbound.protection.outlook.com ✓ mail-db7pr03cu00601.inbound.protection.outlook.com ✓ mail-db4pr02cu00204.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

info

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

Found

MTA-STS record: v=STSv1; id=20241119120000Z
Policy URL: https://mta-sts.phoenixcontact.com/.well-known/mta-sts.txt
Mode: enforce
Allowed MX: *.mail.protection.outlook.com
Max age: 604800 seconds
TLS-RPT record: v=TLSRPTv1;rua=mailto:pxc-dmarc-ruf@phoenixcontact.com

DANE (TLSA records)

MX host	TLSA	DNSSEC
phoenixcontact-com.mail.protection.outlook.com	none	-

Checks

✓ Record published #32

MTA-STS record found with id 20241119120000Z.
✓ Policy enforced #33

The MTA-STS policy is enforced and cached for 168h0m0s.
✓ All MX hosts covered #34

Every MX host matches an mx: line of the MTA-STS policy.
✓ Reports enabled #35

TLS reports are sent to: mailto:pxc-dmarc-ruf@phoenixcontact.com
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