Good, with 2 things to fix

linkedin.com scored 84/100 (grade B). The main issues are DKIM key shorter than 2048 bits and SPF has too many lookups that return nothing. Detected senders: Google Workspace.

Checked 2026-10-04 02:01 UTC · fresh check

4 passed2 need attention0 failing2 for informationDetected senders: Google Workspace

All checks

MXCan servers find your inbox?No issues foundPass

Nothing to report.

SPFWho may send as you?SPF has too many lookups that return nothingNeeds attention

Warning: SPF has too many lookups that return nothing
Checking mail from linkedin.com, IPv6 clients would hit 5 void lookups (DNS queries that return no data). RFC 7208 lets receivers fail SPF after 2. Remove includes and mechanisms that point at names that no longer exist, or MX hosts without an address for that family.
Info: SPF ends in softfail (~all)
"~all" is common and works well with DMARC. "-all" is stricter; switch when you are sure every sender is listed.

DKIMAre your emails signed?DKIM key shorter than 2048 bitsNeeds attention

Warning: DKIM key shorter than 2048 bits
google (1024-bit) uses an RSA key below 2048 bits. Short keys can be factored and some receivers treat them as weak. Rotate to a 2048-bit key at your sending provider.
Pass: DKIM key published
linkedin.com publishes a DKIM key under google.

DMARCWhat happens to fakes?No issues foundPass

Nothing to report.

AlignmentDoes it match your From?SPF alignment is unknownInfo

Info: SPF alignment is unknown
The SPF record of linkedin.com can pass for some senders (those matched before the failing part), but another evaluation path ends in a permanent error (spf.void-lookups). Senders that reach that path fail SPF, so whether your mail aligns through SPF is unknown. Fix the error so every path evaluates.

BIMICan inboxes show your logo?No issues foundPass

Nothing to report.

MTA-STSIs mail to you encrypted?No MTA-STS recordInfo

Info: No MTA-STS record
No MTA-STS record at _mta-sts.linkedin.com. MTA-STS (RFC 8461) makes sending servers require TLS and a valid certificate when delivering to you, which blocks downgrade attacks.
How to fix this

TLS-RPTWill you hear about failures?TLS-RPT is configuredPass

Pass: TLS-RPT is configured
TLS reports will be sent to mailto:tlsreports@linkedin.com.

How to fix it

Publish the MTA-STS recordTXT

Tells sending servers that linkedin.com publishes an MTA-STS policy at https://mta-sts.linkedin.com/.well-known/mta-sts.txt. Change the id whenever the policy file changes.

TypeTXT

Name / Host

_mta-sts.linkedin.com

Some DNS providers want just “_mta-sts” here.

Value

v=STSv1; id=202610040201

Host the MTA-STS policy filepolicy-file

Serve this file over HTTPS with a valid certificate for mta-sts.linkedin.com. It lists your MX hosts and starts in testing mode; switch to mode: enforce once TLS-RPT reports show no failures.

Location

https://mta-sts.linkedin.com/.well-known/mta-sts.txt

Contents

version: STSv1
mode: testing
mx: mail-a.linkedin.com
mx: mail-c.linkedin.com
mx: mail-d.linkedin.com
mx: mail.linkedin.com
max_age: 604800