Cognativemtb 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 3 emails we've observed. DMARC policy is read live from DNS.
DMARC reports sent to Red Sift OnDMARC. Policy
p=none is monitor-only — receivers won't act on spoofing yet.
DKIM alignment: all 16 observed emails sign with a domain aligned with cognativemtb.com (cognativemtb.com). DKIM authenticates the visible From — supports DMARC directly.
Delivery (last 7 days): 33% under 10 seconds, 0% over 1 minute (across 3 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: cognativemtb.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 | 21 | 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 | 21 | 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 cognativemtb.com has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Placement | Reputation |
|---|---|---|---|---|
| 204.220.169.90 | g90.gb126d70.use4.send.mailgun.net |
3 | 2 | Check → |
| 204.220.169.14 | g14.gb126d70.use4.send.mailgun.net |
3 | — | Check → |
| 204.220.169.10 | g10.gb126d70.use4.send.mailgun.net |
2 | — | Check → |
| 204.220.169.91 | g91.gb126d70.use4.send.mailgun.net |
2 | — | Check → |
| 204.220.169.75 | g75.gb126d70.use4.send.mailgun.net |
2 | — | Check → |
| 204.220.169.97 | g97.gb126d70.use4.send.mailgun.net |
2 | — | Check → |
| 204.220.169.96 | g96.gb126d70.use4.send.mailgun.net |
1 | — | Check → |
| 204.220.169.93 | g93.gb126d70.use4.send.mailgun.net |
1 | — | Check → |
| 204.220.169.118 | g118.gb126d70.use4.send.mailgun.net |
1 | — | Check → |
| 204.220.169.66 | g66.gb126d70.use4.send.mailgun.net |
1 | — | Check → |
| 204.220.169.12 | g12.gb126d70.use4.send.mailgun.net |
1 | — | Check → |
| 204.220.169.71 | g71.gb126d70.use4.send.mailgun.net |
1 | — | Check → |
| 204.220.169.132 | g132.gb126d70.use4.send.mailgun.net |
1 | — | Check → |
| 204.220.169.8 | g8.gb126d70.use4.send.mailgun.net |
1 | — | Check → |
| 204.220.169.2 | g2.gb126d70.use4.send.mailgun.net |
1 | — | Check → |
| 204.220.169.86 | 86.static.twc.health |
1 | — | Check → |
| 204.220.169.126 | g126.gb126d70.use4.send.mailgun.net |
1 | — | Check → |
| 204.220.169.3 | g3.gb126d70.use4.send.mailgun.net |
1 | 1 | Check → |
| Domain | ESPs detected | Delivery (7d) |
|---|---|---|
cognativemtb.com | Omnisend 26 |