Every uses Kit for marketing email and Mailgun for transactional/notifications. They rank #114,473 in the Tranco list of most-popular domains. We've also observed sends via 2 other providers: Amazon SES, Resend. Their email authentication setup is good (score 80/100).
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 10 emails we've observed. DMARC policy is read live from DNS.
DMARC reports sent to every.to. Policy
p=quarantine means receivers actively block or quarantine spoofed mail.
SPF alignment: all 19 observed emails use a return-path aligned with every.to (send.every.to, ckespa.every.to, mg.every.to). SPF authenticates the visible From — supports DMARC directly.
DKIM alignment: all 17 observed emails sign with a domain aligned with every.to (every.to, mg.every.to). DKIM authenticates the visible From — supports DMARC directly.
TLS: modern — 100% TLS 1.3 (across 12 sends).
Delivery: fast — 100% of emails in the last 7 days arrive in under 10 seconds (across 9 sends).
Brands often use multiple ESPs (e.g. one for marketing, another for transactional/notifications).
Amazon SES 8 Resend 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: every.to, mg.every.to, ckespa.every.to, send.every.to
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 | 23 | 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 | 8 | 100.0% | 0.0% | 0.0% | |
| Kit | 5 | 100.0% | 0.0% | 0.0% | |
| Mailgun | 4 | 100.0% | 0.0% | 0.0% | |
| Resend | 2 | 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 every.to has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Placement | Reputation |
|---|---|---|---|---|
| 204.220.183.29 | k29.k3ae2098.use4.send.mailgun.net |
5 | — | Check → |
| 204.220.184.19 | k19.kb8c70eb.use4.send.mailgun.net |
3 | — | Check → |
| 149.72.39.237 | o38.ck.n.convertkit.com |
3 | — | Check → |
| 54.240.9.34 | a9-34.smtp-out.amazonses.com |
2 | 1 | Check → |
| 54.240.9.92 | a9-92.smtp-out.amazonses.com |
2 | 2 | Check → |
| 168.245.5.113 | o20.ck.n.convertkit.com |
2 | 2 | Check → |
| 54.240.9.36 | a9-36.smtp-out.amazonses.com |
2 | 2 | Check → |
| 54.240.9.46 | a9-46.smtp-out.amazonses.com |
1 | — | Check → |
| 54.240.9.30 | a9-30.smtp-out.amazonses.com |
1 | 1 | Check → |
| 54.240.9.54 | a9-54.smtp-out.amazonses.com |
1 | 1 | Check → |
| 54.240.9.32 | a9-32.smtp-out.amazonses.com |
1 | 1 | Check → |
| Domain | ESPs detected | Delivery (7d) |
|---|---|---|
every.to | Mailgun 8 Amazon SES 8 Kit 5 Resend 2 |
