spotify.com
Receivers are told to reject mail that fails authentication for this domain.
Receivers are told to reject mail that fails authentication for this domain. Keep watching aggregate reports so a new sending service does not silently start failing.
Score held up: DMARC is enforcing at p=reject, so nobody else can send as this domain. That is the hard part, and it is done. What is left below is about your own mail arriving, not about anyone spoofing you.
162 DNS queries · 766 ms
- 1Could not verify DKIM signing for Salesforce Marketing CloudConfirm DKIM is switched on in Salesforce Marketing Cloud, then add your selector here so every future scan can verify it directly.
- 2Selector 'google' uses a 1024-bit RSA keyRotate to 2048-bit at your next key rotation.
- 3Selector 'k1' uses a 1024-bit RSA keyRotate to 2048-bit at your next key rotation.
- 4Selector 'mandrill' uses a 1024-bit RSA keyRotate to 2048-bit at your next key rotation.
Identity ·Sending services detected
Read from your SPF includes and MX hosts, then checked for a published DKIM key.
Identity ·DMARC
- Policy
- reject
- Coverage
- 100%
- Alignment
- dkim=r spf=r
Identity ·DKIM
113 selectors probed
googleGoogle WorkspaceRSA 1024k1Mailchimp / MailgunRSA 1024mandrillMailchimp TransactionalRSA 1024mte1Mailchimp TransactionalRSA 2048mte2Mailchimp TransactionalRSA 2048s1SendGridRSA 2048s2SendGridRSA 1024smtpapiSendGridRSA 1024zendesk1ZendeskRSA 2048zendesk2ZendeskRSA 2048intercomIntercomRSA 1024Identity ·SPF
Worst-case evaluation across every include.
- include:_spf.google.com
- include:servers.mcsv.net
- include:_spf.salesforce.com
- include:_spf.netigate.se
- include:21894833.spf06.hubspotemail.net
Findings (14)
MediumCould not verify DKIM signing for Salesforce Marketing Cloud›
Salesforce Marketing Cloud was detected via SPF include:_spf.salesforce.com, so it is authorised to send mail as spotify.com. We checked the selectors it uses by default (sfmc1, sfmc2, exacttarget) and found no key. Salesforce Marketing Cloud lets you choose your own selector name, so this may simply mean yours is custom. If signing genuinely is not enabled, mail through this service will fail DMARC once forwarded.
Confirm DKIM is switched on in Salesforce Marketing Cloud, then add your selector here so every future scan can verify it directly.
RFC 6376
MediumSelector 'google' uses a 1024-bit RSA key›
1024-bit is the RFC 8301 floor, not a good target. 2048-bit is the current recommendation and is universally supported.
Rotate to 2048-bit at your next key rotation.
RFC 8301
MediumSelector 'k1' uses a 1024-bit RSA key›
1024-bit is the RFC 8301 floor, not a good target. 2048-bit is the current recommendation and is universally supported.
Rotate to 2048-bit at your next key rotation.
RFC 8301
MediumSelector 'mandrill' uses a 1024-bit RSA key›
1024-bit is the RFC 8301 floor, not a good target. 2048-bit is the current recommendation and is universally supported.
Rotate to 2048-bit at your next key rotation.
RFC 8301
MediumSelector 's2' uses a 1024-bit RSA key›
1024-bit is the RFC 8301 floor, not a good target. 2048-bit is the current recommendation and is universally supported.
Rotate to 2048-bit at your next key rotation.
RFC 8301
MediumSelector 'smtpapi' uses a 1024-bit RSA key›
1024-bit is the RFC 8301 floor, not a good target. 2048-bit is the current recommendation and is universally supported.
Rotate to 2048-bit at your next key rotation.
RFC 8301
MediumSelector 'intercom' uses a 1024-bit RSA key›
1024-bit is the RFC 8301 floor, not a good target. 2048-bit is the current recommendation and is universally supported.
Rotate to 2048-bit at your next key rotation.
RFC 8301
LowSPF ends in '~all' (softfail)›
Softfail is the correct setting while you are still discovering senders, but it asks receivers to accept unauthorised mail and merely note it.
Once your aggregate reports show no unexplained legitimate sources, tighten to '-all'.
LowNo MTA-STS policy›
Without MTA-STS, mail to your domain can be downgraded to plaintext by an active network attacker, because SMTP's STARTTLS is opportunistic by default.
Publish a TXT record at _mta-sts.spotify.com and a policy file at https://mta-sts.spotify.com/.well-known/mta-sts.txt.
RFC 8461
LowNo TLS-RPT record›
Sending servers have no address to report TLS failures on mail to your domain, so transport problems stay invisible to you until someone complains.
Publish 'v=TLSRPTv1; rua=mailto:<address>' at _smtp._tls.spotify.com.
RFC 8460
LowBIMI has no Verified Mark Certificate›
Gmail requires a VMC (the a= tag) before it will display a BIMI logo. Without one, only a handful of receivers will show it.
Obtain a VMC from an authorised issuer and add it as the a= tag.
LowNo CAA record›
Any certificate authority in the world may issue a certificate for this domain. A mis-issued certificate can be used to intercept mail on the wire and to impersonate your domain over HTTPS.
Publish a CAA record naming your certificate authority, for example: 0 issue "letsencrypt.org"
RFC 8659
InfoHubSpot uses selectors we cannot discover›
Detected via SPF include:21894833.spf06.hubspotemail.net. HubSpot selectors include a per-portal id (hs1-12345678._domainkey), so they cannot be guessed. Copy yours from the HubSpot DNS setup screen. We cannot confirm or rule out DKIM signing for this service from DNS alone.
Add your HubSpot selector so we can verify it on every scan.
InfoZone is not signed with DNSSEC›
This is the common case and not a misconfiguration -- most working mail domains are unsigned. It is worth knowing because your authentication records are only as trustworthy as the DNS answers carrying them, and because DNSSEC is the prerequisite for DANE.
If your DNS provider supports one-click DNSSEC, enabling it is low risk. If it does not, this is not worth changing providers over.
RFC 4033
Show 12 passing checks
PassAggregate reporting is configured›
Aggregate reports are requested at: [email protected].
PassExternal report destination ag.eu.dmarcian.com is correctly authorised›
Authorised by spotify.com._report._dmarc.ag.eu.dmarcian.com
PassDMARC policy is p=reject›
Mail failing authentication is rejected outright. This is the correct end state.
PassSPF lookup count is healthy (6/10)›
Worst-case evaluation stays within the limit with headroom to spare.
PassGoogle Workspace's DKIM key is published at google._domainkey›
Detected via SPF include:_spf.google.com, MX alt1.aspmx.l.google.com, MX alt2.aspmx.l.google.com, MX aspmx.l.google.com, MX aspmx2.googlemail.com, MX aspmx3.googlemail.com, MX aspmx4.googlemail.com, MX aspmx5.googlemail.com. A valid public key for this service is published at google._domainkey.spotify.com.
PassMailchimp's DKIM key is published at k1._domainkey›
Detected via SPF include:servers.mcsv.net. A valid public key for this service is published at k1._domainkey.spotify.com.
Pass11 DKIM key(s) published›
Found at: google, intercom, k1, mandrill, mte1, mte2, s1, s2, smtpapi, zendesk1, zendesk2.
PassSelector 'mte1' uses a 2048-bit RSA key›
Key length meets current guidance.
PassSelector 'mte2' uses a 2048-bit RSA key›
Key length meets current guidance.
PassSelector 's1' uses a 2048-bit RSA key›
Key length meets current guidance.
PassSelector 'zendesk1' uses a 2048-bit RSA key›
Key length meets current guidance.
PassSelector 'zendesk2' uses a 2048-bit RSA key›
Key length meets current guidance.
Transport and zone
Where your mail lands, and whether the DNS carrying your records can be trusted.
This is the configuration. It is not the whole picture.
A DNS scan cannot tell you whether spotify.com’s mail actually aligns, because alignment is decided per message at the receiver. Collect DMARC aggregate reports to see every source sending as this domain.