Bitwarden uses SendGrid as their primary email service provider. They rank #3,767 in the Tranco list of most-popular domains. We've also observed sends via Amazon SES. Their email authentication setup is solid (score 95/100). Missing: one-click unsubscribe.
Authentication signals observed in this brand's emails. SPF, DKIM and DMARC are the standard sender-authentication stack — see the DMARC policy below for whether spoofing is actually blocked or just monitored. One-click unsubscribe meets Google & Yahoo's bulk-sender requirements.
SPF / DKIM / DMARC above reflect the last 2 emails we've observed. DMARC policy is read live from DNS.
DMARC reports sent to dmarcian. Policy
p=reject means receivers actively block or quarantine spoofed mail.
SPF alignment: all 11 observed emails use a return-path aligned with bitwarden.com (em3430.bitwarden.com, bounce.bitwarden.com, mailses.bitwarden.com). SPF authenticates the visible From — supports DMARC directly.
DKIM alignment: all 5 observed emails sign with a domain aligned with bitwarden.com (bitwarden.com). DKIM authenticates the visible From — supports DMARC directly.
Brands often use multiple ESPs (e.g. one for marketing, another for transactional/notifications).
Amazon SES 2ESPs we've seen sending email for this brand. Green = confirmed by SPF, sender IP rDNS, or known infra pairing (label shows the source). Grey = observed but not yet confirmed by SPF or PTR.
ESPs this brand has authorized in their SPF record. We confirm them with a green ✓ only after seeing recurring use (3+ emails across 2+ days). Until then they stay here — either we haven't observed any email yet, or we've seen a handful but not enough to call them a regular sender for the brand.
Probed: bitwarden.com, em3430.bitwarden.com, bounce.bitwarden.com, mailses.bitwarden.com, ptr9945.bitwarden.com, ptr9647.bitwarden.com, ptr996.bitwarden.com, ptr6477.bitwarden.com
Folder distribution across all emails from this brand observed in Gmail inboxes. High inbox % = good deliverability; spam appearances are the headline signal.
| Folder | Count | Share |
|---|---|---|
| inbox | 11 | 100.0% |
Which ESP's emails are landing where. Sorted by spam % so problem senders surface first. Brands using one ESP for marketing and another for transactional often see very different placement profiles per ESP. Per-ESP folder data only started being captured recently — counts here may be smaller than the total above until backfill catches up.
| ESP | Emails | Placement | Inbox % | Tabs % | Spam % |
|---|---|---|---|---|---|
| Amazon SES | 2 | 100.0% | 0.0% | 0.0% | |
| SendGrid | 9 | 100.0% | 0.0% | 0.0% |
Daily observations per ESP. Brands often run multiple ESPs concurrently — marketing on one, transactional on another — so this chart shows usage rather than switches.
IP addresses bitwarden.com has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Placement | Reputation |
|---|---|---|---|---|
| 159.183.10.22 | o3.ptr9945.bitwarden.com |
4 | 1 | Check → |
| 159.183.31.141 | o5.ptr9647.bitwarden.com |
2 | — | Check → |
| 159.183.131.47 | o1.ptr996.bitwarden.com |
2 | 1 | Check → |
| 159.183.16.34 | o4.ptr6477.bitwarden.com |
1 | — | Check → |
| 54.240.42.185 | a42-185.smtp-out.amazonses.com |
1 | — | Check → |
| 54.240.49.237 | a49-237.smtp-out.amazonses.com |
1 | — | Check → |
| Domain | ESPs detected | Delivery (7d) |
|---|---|---|
bitwarden.com | SendGrid 9 Amazon SES 2 |
