A95/100

linkedin.com

Name: linkedin.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 80 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

One DKIM key is 1024-bit.

Selector google._domainkey is 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:199.101.162.0/25 ip4:108.174.3.0/24 ip4:108.174.6.0/24 ip4:108.174.0.0/24 ip6:2620:109:c00d:104::/64 ip6:2620:109:c006:104::/64 ip6:2620:109:c003:104::/64 ip6:2620:119:50c0:207::/64 ip4:199.101.161.130 mx mx:docusign.net ~all

DMARC · _dmarc.linkedin.com

v=DMARC1; p=reject; rua=mailto:d@rua.agari.com,mailto:yfy3q-9359@rua.dmarc.emailanalyst.com; ruf=mailto:d@ruf.agari.com

DKIM · 1 of 79 selectors

google._domainkey · 1024-bit

MX · Custom / other

10 mail-1.linkedin.com
10 mail-c.linkedin.com
10 mail-d.linkedin.com
20 mail-a.linkedin.com
20 mail.linkedin.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 Azure DNS commands, guardrails, and how to verify. Paste it into Claude, Cursor, Copilot or ChatGPT.

# Fix email authentication for linkedin.com

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

## What is published right now (do not assume anything else)
- SPF (TXT linkedin.com): v=spf1 ip4:199.101.162.0/25 ip4:108.174.3.0/24 ip4:108.174.6.0/24 ip4:108.174.0.0/24 ip6:2620:109:c00d:104::/64 ip6:2620:109:c006:104::/64 ip6:2620:109:c003:104::/64 ip6:2620:119:50c0:207::/64 ip4:199.101.161.130 mx mx:docusign.net ~all   — valid, 2 of 10 lookups
- DMARC (TXT _dmarc.linkedin.com): v=DMARC1; p=reject; rua=mailto:d@rua.agari.com,mailto:yfy3q-9359@rua.dmarc.emailanalyst.com; ruf=mailto:d@ruf.agari.com
- DKIM: google._domainkey (1024-bit)
- MX: mail-1.linkedin.com, mail-c.linkedin.com, mail-d.linkedin.com, mail-a.linkedin.com, mail.linkedin.com  → a custom mail host
- Nameservers: dns1.p09.nsone.net, dns2.p09.nsone.net …  → records are managed in Azure DNS

## Tasks, in order of impact
…

# Fix email authentication for linkedin.com

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

## What is published right now (do not assume anything else)
- SPF (TXT linkedin.com): v=spf1 ip4:199.101.162.0/25 ip4:108.174.3.0/24 ip4:108.174.6.0/24 ip4:108.174.0.0/24 ip6:2620:109:c00d:104::/64 ip6:2620:109:c006:104::/64 ip6:2620:109:c003:104::/64 ip6:2620:119:50c0:207::/64 ip4:199.101.161.130 mx mx:docusign.net ~all   — valid, 2 of 10 lookups
- DMARC (TXT _dmarc.linkedin.com): v=DMARC1; p=reject; rua=mailto:d@rua.agari.com,mailto:yfy3q-9359@rua.dmarc.emailanalyst.com; ruf=mailto:d@ruf.agari.com
- DKIM: google._domainkey (1024-bit)
- MX: mail-1.linkedin.com, mail-c.linkedin.com, mail-d.linkedin.com, mail-a.linkedin.com, mail.linkedin.com  → a custom mail host
- Nameservers: dns1.p09.nsone.net, dns2.p09.nsone.net …  → records are managed in Azure DNS

## Tasks, in order of impact
### 1. One DKIM key is 1024-bit.
Why: Selector google._domainkey is 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 Azure DNS, stop and say exactly what access you need.

## Verify
  dig +short TXT linkedin.com
  dig +short TXT _dmarc.linkedin.com
Then open https://www.mailauthwatch.com/check/linkedin.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:199.101.162.0/25 ip4:108.174.3.0/24 ip4:108.174.6.0/24 ip4:108.174.0.0/24 ip6:2620:109:c00d:104::/64 ip6:2620:109:c006:104::/64 ip6:2620:109:c003:104::/64 ip6:2620:119:50c0:207::/64 ip4:199.101.161.130 mx mx:docusign.net ~all

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

OK No problems detected.

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=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCLhE5uHP4DCQPLBtQNWwX2rvKIxmdgrYvd…`

WarningDKIM selector "google" uses a 1024-bit key. Rotate to 2048 bits.
NoteSelector "dk" is published with an empty key (decommissioned). Harmless as long as nothing signs with it.

DMARC OK

v=DMARC1; p=reject; rua=mailto:d@rua.agari.com,mailto:yfy3q-9359@rua.dmarc.emailanalyst.com; ruf=mailto:d@ruf.agari.com

Policy: p=reject
Applies to: 100% of failing mail
Aggregate reports: mailto:d@rua.agari.com mailto:yfy3q-9359@rua.dmarc.emailanalyst.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: OK v=TLSRPTv1; rua=mailto:tlsreports@linkedin.com
BIMI: OK v=BIMI1; l=https://media.licdn.com/media/AAYQAQQhAAgAAQAAAAAAABrLiVuNIZ3fRKGlFSn4hGZubg.svg; a=https://media.licdn.com/media/AAYABAQhAAgAAQAAAAAAAYFI0DP_wvHFSv6mYduMZuEwSA.pem;

How the grade is calculated

Score 95/100. SPF present and valid. SPF ends with ~all. DKIM found (1 selector). 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

google.com1 lookupsnot foundp=rejectB live.com5 lookups2048-bitp=noneB amazon.com4 lookups1024-bitp=quarantineA github.com10 lookups2048-bitp=quarantineA gmail.com1 lookupsnot foundp=noneC microsoftonline.com6 lookupsnot foundp=rejectB salesforce.com4 lookups2048-bitp=rejectA mailauthwatch.com1 lookups1024-bitp=rejectA notion.so0 lookupsnot foundp=quarantineC gandi.net2 lookupsnot foundp=noneC mailship.com1 lookupsnot foundmissingD azure.com2 lookupsnot foundp=rejectB