Mail domain report: soundcloud.com

SPF

pass

SPF record published

Found

Record: v=spf1 include:_spf.google.com ip4:178.249.138.0/23 ip4:145.253.129.216/29 ip4:80.82.202.192/28 ip4:52.17.172.90/32 include:spf.mandrillapp.com include:7303199.spf04.hubspotemail.net include:spf.extole.io -all
DNS lookups: 4 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

No ptr mechanism found in SPF record.
✓ 4 of 10 DNS lookups #2

SPF record needs 4 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.soundcloud.com)

Found

Record: v=DMARC1; p=reject; rua=mailto:yL97s5R6Jy@dmarc.inboxmonster.com,mailto:dmarc-rua@soundcloud.com; ruf=mailto:dmarc-ruf@soundcloud.com; pct=100; sp=reject;
Found at: _dmarc.soundcloud.com
External report address: mailto:yL97s5R6Jy@dmarc.inboxmonster.com (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	reject	Policy
sp	reject	Subdomain policy
pct	100	Percentage of mail the policy applies to
rua	mailto:yL97s5R6Jy@dmarc.inboxmonster.com,mailto:dmarc-rua@soundcloud.com	Aggregate report addresses
ruf	mailto:dmarc-ruf@soundcloud.com	Failure report addresses

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:yL97s5R6Jy@dmarc.inboxmonster.com, mailto:dmarc-rua@soundcloud.com
✓ Subdomain policy: reject #20

Subdomains are covered by policy 'reject'.
✓ External report addresses authorized #29

Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: google, s1, s2

Found

Selectors: google, s1, s2
_domainkey: NXDOMAIN

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

Checks

✓ Keys found: google, s1, s2 #7

DKIM keys found for this domain with selectors: google, s1, s2
!

1024-bit DKIM key

1024-bit RSA keys are the minimum and are considered weak today: 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

pass

5 mail servers

Found

Priority	Host	Records	Reverse DNS
10	aspmx.l.google.com	A 142.251.127.26 AAAA 2a00:1450:4001:c21::1b	lcfrai-in-f26.1e100.net ✓ lcfrai-in-f27.1e100.net ✓
20	alt1.aspmx.l.google.com	A 142.250.147.26 AAAA 2a00:1450:4025:c01::1b	rd-in-f26.1e100.net ✓ rd-in-f27.1e100.net ✓
20	alt2.aspmx.l.google.com	A 172.253.152.26 AAAA 2a00:1450:4010:c22::1a	yulpptr-in-f26.1e100.net ✓ yulpptr-in-f26.1e100.net ✓
50	aspmx2.googlemail.com	A 142.250.147.26 AAAA 2a00:1450:4025:c01::1b	rd-in-f26.1e100.net ✓ rd-in-f27.1e100.net ✓
50	aspmx3.googlemail.com	A 172.253.152.26 AAAA 2a00:1450:4010:c22::1b	yulpptr-in-f26.1e100.net ✓ yulpptr-in-f27.1e100.net ✓

Checks

✓ 5 MX records #9

Found 5 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.
✓ Redundant MX hosts #12

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

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

TLS

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
aspmx.l.google.com	none	-
alt1.aspmx.l.google.com	none	-
alt2.aspmx.l.google.com	none	-
aspmx2.googlemail.com	none	-
aspmx3.googlemail.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

pass

https://brand.sndcdn.com/vmc/soundcloudLogo_bimi_title_fixed.svg

Found

Record: v=BIMI1; l=https://brand.sndcdn.com/vmc/soundcloudLogo_bimi_title_fixed.svg; a=https://brand.sndcdn.com/vmc/soundcloud-com.pem; avp=personal;
Found at: default._bimi.soundcloud.com
Logo: https://brand.sndcdn.com/vmc/soundcloudLogo_bimi_title_fixed.svg
Certificate: https://brand.sndcdn.com/vmc/soundcloud-com.pem

Checks

✓ Logo and certificate published #38

BIMI logo: https://brand.sndcdn.com/vmc/soundcloudLogo_bimi_title_fixed.svg; certificate: https://brand.sndcdn.com/vmc/soundcloud-com.pem
✓ DMARC meets BIMI requirements #39

DMARC is enforced on all mail, as BIMI requires.