A100/100

spotify.com

Name: spotify.com email authentication report
Creator: MailAuthWatch
License: https://creativecommons.org/publicdomain/zero/1.0/

Solid. A couple of things could still be tighter. 1 item below, ordered by how much inbox it is costing you. Measured 0s ago from public DNS in 232 ms.

SPF PASSDKIM 1024-BITDMARC REJECTMX OK

Monitor this domain Re-run check

Fix these, in this order, or hand the list to your agent

ranked by impact

7 DKIM keys are 1024-bit.

Selectors google._domainkey, k1._domainkey, s2._domainkey, mandrill._domainkey, cm._domainkey, krs._domainkey, smtpapi._domainkey are under 2048 bits, which some receivers already downgrade.

Do this: rotate to a 2048-bit key at the sending service.

Records found

SPF · TXT

v=spf1 ip4:80.76.146.172 ip4:80.76.146.173 include:_spf.google.com include:servers.mcsv.net include:_spf.salesforce.com include:_spf.netigate.se include:21894833.spf06.hubspotemail.net ~all

DMARC · _dmarc.spotify.com

v=DMARC1; p=reject; sp=reject; pct=100; fo=1; rf=afrf; rua=mailto:6jxge2ly@ag.eu.dmarcian.com;

DKIM · 12 of 79 selectors

google._domainkey · 1024-bit
k1._domainkey · 1024-bit
s1._domainkey · 2048-bit
s2._domainkey · 1024-bit
mandrill._domainkey · 1024-bit
cm._domainkey · 1024-bit
zendesk1._domainkey · 2048-bit
zendesk2._domainkey · 2048-bit
krs._domainkey · 1024-bit
mte1._domainkey · 2048-bit
mte2._domainkey · 2048-bit
smtpapi._domainkey · 1024-bit

MX · Google Workspace

1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 aspmx4.googlemail.com
10 aspmx5.googlemail.com
10 aspmx3.googlemail.com
10 aspmx2.googlemail.com

Fix this with your AI agent

AGENT-READY

A prompt built only from what was measured: the records as published, 1 task in order, exact record values and Google Cloud DNS commands, guardrails, and how to verify. Paste it into Claude, Cursor, Copilot or ChatGPT.

# Fix email authentication for spotify.com

You are working on the DNS and mail configuration for spotify.com.
Measured by MailAuthWatch on 17 Oct 2026 from public DNS. Grade A (100/100).
Report: https://www.mailauthwatch.com/check/spotify.com

## What is published right now (do not assume anything else)
- SPF (TXT spotify.com): v=spf1 ip4:80.76.146.172 ip4:80.76.146.173 include:_spf.google.com include:servers.mcsv.net include:_spf.salesforce.com include:_spf.netigate.se include:21894833.spf06.hubspotemail.net ~all   — valid, 6 of 10 lookups
- DMARC (TXT _dmarc.spotify.com): v=DMARC1; p=reject; sp=reject; pct=100; fo=1; rf=afrf; rua=mailto:6jxge2ly@ag.eu.dmarcian.com;
- DKIM: google._domainkey (1024-bit), k1._domainkey (1024-bit), s1._domainkey (2048-bit), s2._domainkey (1024-bit), mandrill._domainkey (1024-bit), cm._domainkey (1024-bit), zendesk1._domainkey (2048-bit), zendesk2._domainkey (2048-bit), krs._domainkey (1024-bit), mte1._domainkey (2048-bit), mte2._domainkey (2048-bit), smtpapi._domainkey (1024-bit)
- MX: aspmx.l.google.com, alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, aspmx4.googlemail.com, aspmx5.googlemail.com, aspmx3.googlemail.com, aspmx2.googlemail.com  → Google Workspace
- Nameservers: ns-cloud-a3.googledomains.com, ns-cloud-a1.googledomains.com …  → records are managed in Google Cloud DNS

## Tasks, in order of impact
…

# Fix email authentication for spotify.com

You are working on the DNS and mail configuration for spotify.com.
Measured by MailAuthWatch on 17 Oct 2026 from public DNS. Grade A (100/100).
Report: https://www.mailauthwatch.com/check/spotify.com

## What is published right now (do not assume anything else)
- SPF (TXT spotify.com): v=spf1 ip4:80.76.146.172 ip4:80.76.146.173 include:_spf.google.com include:servers.mcsv.net include:_spf.salesforce.com include:_spf.netigate.se include:21894833.spf06.hubspotemail.net ~all   — valid, 6 of 10 lookups
- DMARC (TXT _dmarc.spotify.com): v=DMARC1; p=reject; sp=reject; pct=100; fo=1; rf=afrf; rua=mailto:6jxge2ly@ag.eu.dmarcian.com;
- DKIM: google._domainkey (1024-bit), k1._domainkey (1024-bit), s1._domainkey (2048-bit), s2._domainkey (1024-bit), mandrill._domainkey (1024-bit), cm._domainkey (1024-bit), zendesk1._domainkey (2048-bit), zendesk2._domainkey (2048-bit), krs._domainkey (1024-bit), mte1._domainkey (2048-bit), mte2._domainkey (2048-bit), smtpapi._domainkey (1024-bit)
- MX: aspmx.l.google.com, alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, aspmx4.googlemail.com, aspmx5.googlemail.com, aspmx3.googlemail.com, aspmx2.googlemail.com  → Google Workspace
- Nameservers: ns-cloud-a3.googledomains.com, ns-cloud-a1.googledomains.com …  → records are managed in Google Cloud DNS

## Tasks, in order of impact
### 1. 7 DKIM keys are 1024-bit.
Why: Selectors google._domainkey, k1._domainkey, s2._domainkey, mandrill._domainkey, cm._domainkey, krs._domainkey, smtpapi._domainkey are under 2048 bits, which some receivers already downgrade. 
Rotate to a 2048-bit key at the sending service.

## Rules
- Publish exactly one SPF record; never add a second v=spf1 TXT.
- Do not remove any include: or ip4: you cannot account for; mail may depend on it.
- Do not set DMARC to p=reject in one step; stage through p=none → quarantine → reject.
- Show the planned DNS changes as a diff (record, old value, new value) before applying them.
- If you cannot access Google Cloud DNS or Google Workspace, stop and say exactly what access you need.

## Verify
  dig +short TXT spotify.com
  dig +short TXT _dmarc.spotify.com
Then open https://www.mailauthwatch.com/check/spotify.com?fresh=1 and confirm:
  the grade is unchanged and no new issues appear. Target grade: A.

## Report back
List each record you changed (name, type, old value, new value), what you verified, and anything you could not do.

Open in Claude Open in ChatGPT fix.md

Your agent, your DNS, your review. MailAuthWatch never changes records; it writes the plan and re-checks the result.

Grade history

Free checks keep nothing. Monitoring records every daily measurement and alerts you on change.

History goes back as far as your subscription.

SPF OK

v=spf1 ip4:80.76.146.172 ip4:80.76.146.173 include:_spf.google.com include:servers.mcsv.net include:_spf.salesforce.com include:_spf.netigate.se include:21894833.spf06.hubspotemail.net ~all

DNS lookups: 6 of 10 allowed
Final mechanism: ~all

OK No problems detected.

Include tree

6 / 10

spotify.com+1 direct

├─ include:_spf.google.com+1

├─ include:servers.mcsv.net+1

├─ include:_spf.salesforce.com+1

├─ include:_spf.netigate.se+1

└─ include:21894833.spf06.hubspotemail.net+1

DKIM OK

DKIM selectors cannot be listed from DNS, so 79 selectors used by common providers were probed.

Selector	Key	Record
`google`	RSA 1024-bit Weak	`v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCSiZTnXPysNqgPjX0hSeHC8wVY62ooFHCc…`
`k1`	RSA 1024-bit Weak	`k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDbNrX2cY/GUKIFx2G/1I00ftdAj713WP9AQ1xir85i8…`
`s1`	RSA 2048-bit OK	`k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwCEk4DORulk0uxTYFhRfxKQbzjyivhHv…`
`s2`	RSA 1024-bit Weak	`k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDT6ESgYVxBegX2kZGj7MiDOHS5Yr3hhemMD8xc…`
`mandrill`	RSA 1024-bit Weak	`v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCrLHiExVd55zd/IQ/J/mRwSRMAocV/hMB3…`
`cm`	RSA 1024-bit Weak	`k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDebmXkcrZd6KtTDU4CzbEOMIldk4nE7jvu2nKz4RpHM…`
`zendesk1`	RSA 2048-bit OK	`v=DKIM1;t=s;n=core;k=rsa;p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA9IqdLrO3Zr2/56MHt8o…`
`zendesk2`	RSA 2048-bit OK	`v=DKIM1; t=s; n=core; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAmiSFNkgXrO3I8aO…`
`krs`	RSA 1024-bit Weak	`k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDC0RrHTLssq6cMxkA2GRpaHYj8ubSbzEW+/QC/gCfto…`
`mte1`	RSA 2048-bit OK	`v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA2GGE1A9cwHjf5KYMV0GdrKcEhCVg…`
`mte2`	RSA 2048-bit OK	`v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAt7NkXm8fhrVVfUvX7UQBHmn8nlT1…`
`smtpapi`	RSA 1024-bit Weak	`k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDPtW5iwpXVPiH5FzJ7Nrl8USzuY9zqqzjE0D1r…`

WarningDKIM selectors "google", "k1", "s2", "mandrill", "cm", "krs", "smtpapi" use 1024-bit keys. Rotate to 2048 bits.

DMARC OK

v=DMARC1; p=reject; sp=reject; pct=100; fo=1; rf=afrf; rua=mailto:6jxge2ly@ag.eu.dmarcian.com;

Policy: p=reject · subdomains sp=reject
Applies to: 100% of failing mail
Aggregate reports: mailto:6jxge2ly@ag.eu.dmarcian.com

OK No problems detected.

Mail exchange and extras

OK No problems detected.

MTA-STS: Not published optional: enforces TLS for inbound mail
TLS-RPT: Not published
BIMI: OK v=BIMI1; l=https://message-editor.scdn.co/spotify-icon.svg

How the grade is calculated

Score 100/100. SPF present and valid. SPF ends with ~all. DKIM found (12 selectors). DKIM key is 2048-bit or stronger. DMARC present and valid. DMARC policy is reject. DMARC aggregate reporting enabled. SPF contributes up to 35 points, DKIM up to 25, DMARC up to 40 (policy strength and reporting). Any critical issue caps the grade at C. Lookups that failed are shown as "not measured" and never counted as missing.

Check another domain:

Other recently graded domains

Public checks from the last few days. Every report is re-measured from DNS when opened.

live

DomainSPFDKIMDMARCGrade

linkedin.com2 lookups1024-bitp=rejectA google.com1 lookupsnot foundp=rejectB amazon.com4 lookups1024-bitp=quarantineA gmail.com1 lookupsnot foundp=noneC salesforce.com4 lookups2048-bitp=rejectA gandi.net2 lookupsnot foundp=noneC zoom.us6 lookups2048-bitp=rejectA skype.com2 lookupsnot foundp=rejectB shopify.com4 lookups2048-bitp=rejectA bing.com1 lookupsnot foundp=rejectB ebay.com10 lookups2048-bitp=rejectA facebook.com1 lookupsnot foundp=rejectB