SurfaceMap › x › xerox.com

xerox.com

Checked 2026-10-22 11:34 UTC · first added 2026-10-21

✗Problems found Score 63 of 100

Domain & DNS

fail

26 passed 4 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers !SOA iDNSSEC iRecords

Problems

✗

No DNS over TCP

Nameservers · DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: curly.xerox.com (13.13.138.12): dial tcp 13.13.138.12:53: connect: connection refused; shemp.xerox.com (13.8.138.8): dial tcp 13.8.138.8:53: connect: connection refused.

#19
!

NS sets differ

Delegation · The nameservers at the parent and in the zone should be the same. Only in the zone: athena.xerox.com, betelgeuse.xerox.com, curly.xerox.com, shemp.xerox.com. adrastea.xerox.com, ash.xerox.com, athena.xerox.com, betelgeuse.xerox.com, carme.xerox.com, curly.xerox.com, gum.xerox.com, shemp.xerox.com report NS adrastea.xerox.com ash.xerox.com athena.xerox.com betelgeuse.xerox.com carme.xerox.com curly.xerox.com gum.xerox.com shemp.xerox.com.

#7
!

No IPv6

Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.

#13
!

Software version disclosed

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: adrastea.xerox.com: "9.11.36-RedHat-9.11.36-16.el8_10.14"; ash.xerox.com: "9.11.36-RedHat-9.11.36-16.el8_10.14"; athena.xerox.com: "9.11.36-RedHat-9.11.36-16.el8_10.14"; betelgeuse.xerox.com: "9.11.36-RedHat-9.11.36-16.el8_10.14"; carme.xerox.com: "9.11.36-RedHat-9.11.36-16.el8_10.14"; curly.xerox.com: "9.11.36-RedHat-9.11.36-16.el8_10.14"; gum.xerox.com: "9.11.36-RedHat-9.11.36-16.el8_10.14"; shemp.xerox.com: "9.11.36-RedHat-9.11.36-16.el8_10.14". Hide or replace the version string.

#17
!

Unusual SOA timers

SOA · expire 100h is shorter than 7d; secondaries stop answering too soon when the primary is down. Current values: refresh 1h, retry 15m, expire 100h, negative TTL 4h.

#23

Recent checks

✗

Full report

Domain & DNS report for xerox.com ›

Mail

warn

25 passed 5 warn 0 failed

Areas

✓SPF !DMARC !DKIM ✓DNSSEC !MX !TLS iBIMI

Problems

!

Policy: quarantine

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

#4
!

Hosts without IPv6

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

#11
!

Subdomains unprotected (sp=none)

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

#20
!

1024-bit DKIM key

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

#23
!

Not configured

TLS · 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

Recent checks

Full report

Mail report for xerox.com ›