Mail domain report: xerox.com

SPF

pass

SPF record published

Found

Record: v=spf1 include:_iphmx.xerox.com include:_iphmx2.xerox.com include:spf.protection.outlook.com include:spf.constantcontact.com include:_spf.salesforce.com include:nw026.com include:mail.zendesk.com include:autotask.net ip4:141.193.184.64/26 ip4:141.193.185.128/25 ip4:18.208.124.128/25 ip4:141.193.184.128/25 ip4:141.193.185.64/26 ip4:158.247.16.0/20 ip4:3.93.157.0/24 ip4:216.139.64.0/19 ip4:108.179.144.0/20 ip4:54.174.60.0/23 ip4:143.244.80.0/20 ip4:54.174.59.0/24 ip4:54.174.63.0/24 ip4:3.210.190.0/24 ip4:141.193.184.32/27 ip4:54.174.52.0/24 ip4:139.180.17.0/24 ip4:141.193.185.32/27 ip4:54.174.57.0/24 ~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.xerox.com)

Found

Record: v=DMARC1; p=quarantine; sp=none; fo=1; rua=mailto:dmarc_rua@emaildefense.proofpoint.com; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com;
Found at: _dmarc.xerox.com
External report address: mailto:dmarc_rua@emaildefense.proofpoint.com (authorized)
External report address: mailto:dmarc_ruf@emaildefense.proofpoint.com (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
sp	none	Subdomain policy
rua	mailto:dmarc_rua@emaildefense.proofpoint.com	Aggregate report addresses
ruf	mailto:dmarc_ruf@emaildefense.proofpoint.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.
✓ Aggregate reports enabled #19

Aggregate reports are sent to: mailto:dmarc_rua@emaildefense.proofpoint.com
!

Subdomains unprotected (sp=none)

DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.

#20
✓ External report addresses authorized #29

Report addresses in other domains have published their authorization.

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

pass

Signed, DS published at parent

Found

DNSKEY records: Yes (2)
DS at parent: Yes
Algorithms: RSASHA256 (8)
Key tags: 51724, 36420
Signatures valid until: 1 November 2026, 07:33 UTC

Checks

✓ Signed, DS published at parent #8

DNSSEC is enabled for this domain (DNSKEY and DS present), providing additional security for DNS lookups.
✓ Signatures valid until 2026-11-01 #21

DNSKEY signatures are valid until 2026-11-01T07:33:47Z.

MX

warn

2 mail servers

Found

Priority	Host	Records	Reverse DNS
50	mx1.xerox.iphmx.com	A 68.232.143.65 A 68.232.129.32 A 68.232.130.182 A 68.232.130.234 A 68.232.130.184 A 68.232.141.28 A 68.232.143.61 A 68.232.130.216 A 68.232.143.66 A 68.232.135.190 A 68.232.141.29 A 68.232.135.102 A 68.232.143.64 A 68.232.143.63 A 68.232.130.31 A 68.232.143.62	esa15.xerox.iphmx.com ✓ esa10.xerox.iphmx.com ✓ esa7.xerox.iphmx.com ✓ esa2.xerox.iphmx.com ✓ esa8.xerox.iphmx.com ✓ esa6.xerox.iphmx.com ✓ esa11.xerox.iphmx.com ✓ esa1.xerox.iphmx.com ✓ esa16.xerox.iphmx.com ✓ esa4.xerox.iphmx.com ✓ esa9.xerox.iphmx.com ✓ esa5.xerox.iphmx.com ✓ esa14.xerox.iphmx.com ✓ esa13.xerox.iphmx.com ✓ esa3.xerox.iphmx.com ✓ esa12.xerox.iphmx.com ✓
50	mx2.xerox.iphmx.com	A 68.232.135.102 A 68.232.135.190 A 68.232.130.182 A 68.232.143.66 A 68.232.143.62 A 68.232.143.63 A 68.232.141.28 A 68.232.143.64 A 68.232.130.234 A 68.232.130.31 A 68.232.143.61 A 68.232.130.184 A 68.232.130.216 A 68.232.143.65 A 68.232.141.29 A 68.232.129.32	esa5.xerox.iphmx.com ✓ esa4.xerox.iphmx.com ✓ esa7.xerox.iphmx.com ✓ esa16.xerox.iphmx.com ✓ esa12.xerox.iphmx.com ✓ esa13.xerox.iphmx.com ✓ esa6.xerox.iphmx.com ✓ esa14.xerox.iphmx.com ✓ esa2.xerox.iphmx.com ✓ esa3.xerox.iphmx.com ✓ esa11.xerox.iphmx.com ✓ esa8.xerox.iphmx.com ✓ esa1.xerox.iphmx.com ✓ esa15.xerox.iphmx.com ✓ esa9.xerox.iphmx.com ✓ esa10.xerox.iphmx.com ✓

Checks

✓ 2 MX records #9

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

All MX records resolve to valid IP addresses.
!

Hosts without IPv6

The following MX hosts could not be resolved to IPv6 addresses: mx1.xerox.iphmx.com, mx2.xerox.iphmx.com

#11
✓ Redundant MX hosts #12

Found 2 MX records, which provides redundancy for email delivery.
✓ At most 5 MX records #13

Found 2 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 32 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
mx1.xerox.iphmx.com	none	-
mx2.xerox.iphmx.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