Sdsarms uses Omnisend as their primary email service provider. Their email authentication setup is good (score 73/100). Missing: DMARC enforcement.
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 5 emails we've observed. DMARC policy is read live from DNS.
DMARC published as p=none with no rua= reporting — monitor-only, and the sender isn't collecting reports either.
DKIM alignment: all 12 observed emails sign with a domain aligned with sdsarms.com (sdsarms.com). DKIM authenticates the visible From — supports DMARC directly.
TLS: 0% TLS 1.3, 100% TLS 1.2 (across 5 sends).
Delivery: fast — 100% of emails in the last 7 days arrive in under 10 seconds (across 2 sends).
Brands often use multiple ESPs (e.g. one for marketing, another for transactional/notifications).
None — only the primary ESP(s) shown aboveESPs 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: sdsarms.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 | 20 | 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 % |
|---|---|---|---|---|---|
| Omnisend | 20 | 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 sdsarms.com has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Placement | Reputation |
|---|---|---|---|---|
| 204.220.169.65 | g65.gb126d70.use4.send.mailgun.net |
3 | 3 | Check → |
| 204.220.169.134 | g134.gb126d70.use4.send.mailgun.net |
2 | — | Check → |
| 204.220.169.89 | g89.gb126d70.use4.send.mailgun.net |
2 | — | Check → |
| 204.220.169.93 | g93.gb126d70.use4.send.mailgun.net |
2 | — | Check → |
| 204.220.169.132 | g132.gb126d70.use4.send.mailgun.net |
2 | 2 | Check → |
| 204.220.169.68 | g68.gb126d70.use4.send.mailgun.net |
1 | — | Check → |
| 204.220.169.31 | g31.gb126d70.use4.send.mailgun.net |
1 | — | Check → |
| 204.220.169.75 | g75.gb126d70.use4.send.mailgun.net |
1 | — | Check → |
| 204.220.169.118 | g118.gb126d70.use4.send.mailgun.net |
1 | — | Check → |
| 204.220.169.92 | g92.gb126d70.use4.send.mailgun.net |
1 | — | Check → |
| 204.220.169.74 | g74.gb126d70.use4.send.mailgun.net |
1 | — | Check → |
| 204.220.169.141 | g141.gb126d70.use4.send.mailgun.net |
1 | — | Check → |
| 204.220.169.86 | 86.static.twc.health |
1 | — | Check → |
| 204.220.169.6 | g6.gb126d70.use4.send.mailgun.net |
1 | — | Check → |
| 204.220.169.13 | g13.gb126d70.use4.send.mailgun.net |
1 | — | Check → |
| Domain | ESPs detected | Delivery (7d) |
|---|---|---|
sdsarms.com | Omnisend 21 |