bsky.app

bsky.app · Last checked 2026-10-04 02:09 UTC

bsky.app

Good, with 2 things to fix

bsky.app scored 80/100 (grade B). The main issues are no DKIM key found for the common selectors and SPF ends in neutral (?all). Detected senders: Google Workspace and Zendesk.

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

1 passed2 need attention0 failing5 for informationDetected senders: Google Workspace, Zendesk

All checks

MXCan servers find your inbox?Only one MX hostInfo
  • Info: Only one MX host

    All mail for bsky.app goes to aspmx.l.google.com. Most hosted providers make that one name highly available; if you run your own server, consider a backup MX.

SPFWho may send as you?SPF ends in neutral (?all)Needs attention
  • Warning: SPF ends in neutral (?all)

    "?all" tells receivers to treat mail from unlisted servers as neither pass nor fail, so SPF gives no protection. End the record with "-all" or "~all".

DKIMAre your emails signed?No DKIM key found for the common selectorsNeeds attention
  • Warning: No DKIM key found for the common selectors

    None of the 47 selectors probed under bsky.app publish a DKIM key. DNS cannot list selectors, so a key under a custom selector may exist: find the s= value in the DKIM-Signature header of a message you sent and check that selector. If DKIM is not set up, enable it at each service that sends mail for bsky.app.

DMARCWhat happens to fakes?No issues foundPass

Nothing to report.

AlignmentDoes it match your From?SPF alignment depends on a custom Return-PathInfo
  • Info: SPF alignment depends on a custom Return-Path

    This is a heuristic. Your SPF record only authorizes third-party senders (mail.zendesk.com). By default they bounce from their own Return-Path domain, and SPF then passes for that domain, not bsky.app. Even relaxed alignment needs the Return-Path's organizational domain to be bsky.app, so set up a custom Return-Path (bounce) domain under bsky.app with each provider, and sign with DKIM as bsky.app.

BIMICan inboxes show your logo?No BIMI recordInfo
  • Info: No BIMI record

    No BIMI record at default._bimi.bsky.app. BIMI is optional: it shows your logo next to your mail in supporting inboxes once DMARC is enforced.

    How to fix this
MTA-STSIs mail to you encrypted?No MTA-STS recordInfo
  • Info: No MTA-STS record

    No MTA-STS record at _mta-sts.bsky.app. 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?No TLS-RPT recordInfo
  • Info: No TLS-RPT record

    No TLS reporting record at _smtp._tls.bsky.app. TLS-RPT (RFC 8460) tells senders where to send daily reports about failed encrypted deliveries to you.

    How to fix this

How to fix it

Enable DKIM for Google Workspaceinstruction

Google Workspace generates the DKIM key for each account, so the exact record must come from Google Workspace. Without DKIM, mail it sends for bsky.app cannot pass DMARC through DKIM.

Applies to: google._domainkey.bsky.app

  1. In Google Workspace, enable DKIM signing for bsky.app: Generate the key in Admin console > Apps > Gmail > Authenticate email, then publish the TXT record shown there. Publish exactly the record Google Workspace shows (TXT or CNAME) at the host name it gives, then turn signing on. Instructions: https://support.google.com/a/answer/174124

Enable DKIM for Zendesk (zendesk1)CNAME

Points the zendesk1 selector at the key Zendesk manages, so mail it sends for bsky.app is DKIM-signed and can align with DMARC. Enable DKIM in Zendesk after publishing.

TypeCNAME
Name / Host
zendesk1._domainkey.bsky.app

Some DNS providers want just “zendesk1._domainkey” here.

Value
zendesk1._domainkey.zendesk.com

Enable DKIM for Zendesk (zendesk2)CNAME

Points the zendesk2 selector at the key Zendesk manages, so mail it sends for bsky.app is DKIM-signed and can align with DMARC. Enable DKIM in Zendesk after publishing.

TypeCNAME
Name / Host
zendesk2._domainkey.bsky.app

Some DNS providers want just “zendesk2._domainkey” here.

Value
zendesk2._domainkey.zendesk.com

Publish the MTA-STS recordTXT

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

TypeTXT
Name / Host
_mta-sts.bsky.app

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

Value
v=STSv1; id=202610040209

Host the MTA-STS policy filepolicy-file

Serve this file over HTTPS with a valid certificate for mta-sts.bsky.app. 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.bsky.app/.well-known/mta-sts.txt
Contents
version: STSv1
mode: testing
mx: aspmx.l.google.com
max_age: 604800

Set up a TLS report addressinstruction

Sending servers will report TLS failures when delivering to bsky.app, which you need before enforcing MTA-STS. The address must accept TLS reports; a DMARC report address does not necessarily do so.

Applies to: _smtp._tls.bsky.app

  1. Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@bsky.app, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.bsky.app with the value v=TLSRPTv1; rua=mailto:<that address>.

Prepare BIMIinstruction

BIMI shows your logo next to messages in supporting inboxes, but only for mail that passes DMARC under an enforced policy.

Applies to: default._bimi.bsky.app

  1. Enforce DMARC first: p=quarantine or p=reject at 100% (no pct below 100). 2. Convert your logo to an SVG Tiny PS file and host it over HTTPS, for example https://bsky.app/bimi/logo.svg. 3. For Gmail and Apple Mail, obtain a VMC or CMC certificate for the logo. 4. Publish a TXT record at default._bimi.bsky.app with v=BIMI1, l= set to the logo URL and a= set to the certificate URL.