Email security report card · 2026-11-07
slack.com
slack.com scores 62/100 (grade C). Legitimate mail can’t fully prove where it comes from, so some of it is likely to land in spam. Forged mail “from” slack.com is refused by the big inboxes. The most valuable next step: correct your SPF record.
C62/100
| Area | Check | Status | Points |
|---|---|---|---|
| Authentication | SPF and DKIMPartly. One of the two proofs is missing or weak. SPF: The SPF record doesn’t include Google Workspace, which handles your email. DKIM: Your mail carries a signature inboxes can verify (1024-bit). 1024-bit keys still work, but 2048 bits is the current recommendation — rotate when you next touch DKIM. | Partly | 12/25 |
| Anti-spoofing | DMARC enforcementMail that fails your checks is refused. | Pass | 30/30 |
| Delivery | Google, Yahoo and Microsoft sender rulesAlmost. Correct your SPF record and you meet them. | Partly | 8/15 |
| Encryption | MTA-STSWithout it, an attacker on the network path can downgrade delivery to unencrypted. | Missing | 0/8 |
| Encryption | TLS-RPTAdd a TXT record at _smtp._tls.slack.com: v=TLSRPTv1; rua=mailto:tls-reports@slack.com | Missing | 0/4 |
| DNS hardening | DNSSECYour DNS is signed and validates. | Pass | 8/8 |
| DNS hardening | CAAOnly amazon.com, digicert.com, letsencrypt.org may issue certificates. | Pass | 4/4 |
| Brand | BIMI logoYour DMARC already qualifies. Publish an SVG logo at default._bimi.slack.com; Gmail and Apple also need a mark certificate. | Missing | 0/6 |
What if you fixed…
Today C 62/100
Fix next
- Correct your SPF record
- Turn on MTA-STS
- Turn on BIMI logo
- Turn on TLS-RPT
Exact records and where to click: full check for slack.com.
Lookalike exposure
Not scanned this time (scan limit reached). Run the lookalike radar.