xoom.com

Checked 22 October 2026, 11:36 UTC · via 8.8.8.8
!Passed with warnings
26 passed 4 warnings 0 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:8.26.33.0/24 ip4:205.189.102.0/23 ip4:198.199.247.0/24 ip4:192.254.121.104/29 ip4:65.52.232.173/32 ip4:157.55.209.64/32 ip4:62.13.150.47/32 ip4:198.21.2.183 ip4:74.112.67.243 include:pp._spf.paypal.com include:spf.protection.outlook.com -all
DNS lookups
2 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 2 of 10 DNS lookups #2
    SPF record needs 2 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=reject (_dmarc.xoom.com)

Found

Record
v=DMARC1; p=reject; fo=1; rf=afrf; rua=mailto:d8f02ed7@mxtoolbox.dmarc-report.com,mailto:xoom@rua.agari.com; ruf=mailto:d8f02ed7@forensics.dmarc-report.com,mailto:dk@bounce.paypal.com,mailto:xoom@ruf.agari.com
Found at
_dmarc.xoom.com
External report address
mailto:d8f02ed7@mxtoolbox.dmarc-report.com (authorized)
External report address
mailto:xoom@rua.agari.com (authorized)
External report address
mailto:d8f02ed7@forensics.dmarc-report.com (authorized)
External report address
mailto:dk@bounce.paypal.com (not authorized)
External report address
mailto:xoom@ruf.agari.com (authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
ruamailto:d8f02ed7@mxtoolbox.dmarc-report.com,mailto:xoom@rua.agari.comAggregate report addresses
rufmailto:d8f02ed7@forensics.dmarc-report.com,mailto:dk@bounce.paypal.com,mailto:xoom@ruf.agari.comFailure report addresses
fo1Failure reporting options
rfafrfFailure report format

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:d8f02ed7@mxtoolbox.dmarc-report.com, mailto:xoom@rua.agari.com
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.
  • !
    Report address not authorized
    These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:dk@bounce.paypal.com (needs xoom.com._report._dmarc.bounce.paypal.com). Ask the report provider to publish the record, or check the address.
    #29

DKIM

warn

Selectors: default, selector1

Found

Selectors
default, selector1
_domainkey
NOERROR
SelectorKeyFlags
defaultRSA 1024 bits
selector1RSA 1024 bits

Checks

  • ✓ Keys found: default, selector1 #7
    DKIM keys found for this domain with selectors: default, selector1
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: default (1024 bits), 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 (4)
DS at parent
Yes
Algorithms
ECDSAP256SHA256 (13)
Key tags
25500, 40424, 34351, 10876
Signatures valid until
18 November 2026, 01:55 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-18 #21
    DNSKEY signatures are valid until 2026-11-18T01:55:21Z.

MX

warn

2 mail servers

Found

PriorityHostRecordsReverse DNS
10mx1.paypalcorp.comA 173.224.165.17mx1.paypalcorp.com ✓
10mx2.paypalcorp.comA 173.224.166.50mx2.paypalcorp.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.paypalcorp.com, mx2.paypalcorp.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 2 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 hostTLSADNSSEC
mx1.paypalcorp.comnone-
mx2.paypalcorp.comnone-

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