Mail domain report: underarmour.com

SPF

pass

SPF record published

Found

Record: v=spf1 ip4:104.130.47.0/24 ip4:67.133.225.146 mx include:spf.protection.outlook.com include:mail.zendesk.com include:spf.mailjet.com include:amazonses.com include:_spf.salesforce.com include:cust-spf.exacttarget.com include:_spf-dc8.sapsf.com ip4:20.119.174.191 ip4:20.230.106.230 ip4:20.114.186.35 ip4:20.119.207.133 ip4:74.117.200.0/21 ip4:160.34.0.0/16 ip4:208.72.88.0/21 ip4:129.152.0.0/17 ip4:199.167.173.0/24 ip4:205.223.80.0/20 ip4:129.91.5.0/24 ip4:141.145.85.0/24 ip4:216.136.229.0/24 ip4:216.136.162.64/26 ip4:216.136.168.32/28 ip4:216.136.168.64/27 ip4:64.56.194.128/25 ip6:2606:b400::/32 ip6:2a02:6900:8814::/48 ip6:2a02:6900:8810::/48 ip4:103.28.42.0/24 ip4:146.88.28.0/24 ip4:163.47.180.0/22 ip4:203.55.21.0/24 ip4:204.75.142.0/24 ip4:167.89.64.70 ip4:167.89.64.72 ip4:167.89.71.63 ip4:31.186.247.98 ip4:104.130.96.5 ip4:54.221.235.134 ip4:204.29.196.148/30 ip4:204.29.196.121 ip4:204.29.196.122/31 ip4:204.29.196.124 ~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.underarmour.com)

Found

Record: v=DMARC1; p=quarantine; rua=mailto:webmaster@underarmour.com,mailto:NxckeQXK6F@dmarc.inboxmonster.com,mailto:dmarc_agg@dmarc.everest.email; adkim=r; aspf=r; pct=10; ri=86400; sp=none;
Found at: _dmarc.underarmour.com
External report address: mailto:NxckeQXK6F@dmarc.inboxmonster.com (authorized)
External report address: mailto:dmarc_agg@dmarc.everest.email (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
sp	none	Subdomain policy
pct	10	Percentage of mail the policy applies to
rua	mailto:webmaster@underarmour.com,mailto:NxckeQXK6F@dmarc.inboxmonster.com,mailto:dmarc_agg@dmarc.everest.email	Aggregate report addresses
adkim	r	DKIM alignment (r = relaxed, s = strict)
aspf	r	SPF alignment (r = relaxed, s = strict)
ri	86400	Report interval (seconds)

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 10% of mail

DMARC policy only applies to 10% of failing mail (pct=10). Raise pct to 100 once you are confident in your setup.

#18
✓ Aggregate reports enabled #19

Aggregate reports are sent to: mailto:webmaster@underarmour.com, mailto:NxckeQXK6F@dmarc.inboxmonster.com, mailto:dmarc_agg@dmarc.everest.email
!

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, s1, s2

Found

Selectors: selector1, s1, s2
_domainkey: NOERROR

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

Checks

✓ Keys found: selector1, s1, s2 #7

DKIM keys found for this domain with selectors: selector1, 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
0	underarmour-com.mail.protection.outlook.com	A 52.101.194.164 A 52.101.202.159 A 52.101.41.3 A 52.101.41.4 AAAA 2a01:111:f403:f903::3 AAAA 2a01:111:f403:f907:: AAAA 2a01:111:f403:c946::1a AAAA 2a01:111:f403:c946::10	mail-ch5pr04cu00204.inbound.protection.outlook.com ✓ mail-ph5pr04cu00107.inbound.protection.outlook.com ✓ mail-sj2pr05cu00103.inbound.protection.outlook.com ✓ mail-sj2pr05cu00204.inbound.protection.outlook.com ✓ mail-mn0pr04cu00203.inbound.protection.outlook.com ✓ mail-dm2pr02cu00100.inbound.protection.outlook.com ✓ mail-ch0pr02cu00102.inbound.protection.outlook.com ✓ mail-ch4pr04cu00300.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
underarmour-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