Binance uses Amazon SES as their primary email service provider. They rank #997 in the Tranco list of most-popular domains. We've also observed sends via Mailgun. Email goes out from 4 different subdomains. Their email authentication setup is solid (score 95/100).
Amazon SESAuthentication 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 Netcraft. Policy
p=quarantine means receivers actively block or quarantine spoofed mail.
SPF alignment: 98% of observed emails use an aligned return-path (mf.smailer1.binance.com, mf.smailer2.binance.com, aws.ses.binance.com); the rest use third-party paths (red-robot.net) where DMARC has to rely on DKIM alignment.
DKIM alignment: all 34 observed emails sign with a domain aligned with binance.com (smailer1.binance.com, smailer2.binance.com, ses.binance.com). DKIM authenticates the visible From — supports DMARC directly.
VMC issued by: entrust.
TLS: modern — 92% TLS 1.3 (across 13 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).
Mailgun 1ESPs 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: binance.com, mf.smailer1.binance.com, mftk.ses.binance.com, mf.smailer2.binance.com, mfca.ses.binance.com, aws.ses.binance.com, red-robot.net, ses.binance.com, smailer1.binance.com, smailer2.binance.com, mgdirectmail.binance.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 | 25 | 67.6% |
| promotions | 12 | 32.4% |
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 % |
|---|---|---|---|---|---|
| Mailgun | 1 | 0.0% | 100.0% | 0.0% | |
| Amazon SES | 36 | 69.4% | 30.6% | 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 binance.com has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Placement | Reputation |
|---|---|---|---|---|
| 206.55.152.66 | h152-66.smtp-out.ap-northeast-1.amazonses.com |
9 | 4 | Check → |
| 206.55.152.63 | h152-63.smtp-out.ap-northeast-1.amazonses.com |
3 | — | Check → |
| 206.55.152.32 | h152-32.smtp-out.ap-northeast-1.amazonses.com |
3 | — | Check → |
| 76.223.149.167 | c149-167.smtp-out.eu-west-1.amazonses.com |
3 | — | Check → |
| 76.223.150.192 | c150-192.smtp-out.eu-west-1.amazonses.com |
3 | — | Check → |
| 206.55.152.34 | h152-34.smtp-out.ap-northeast-1.amazonses.com |
3 | — | Check → |
| 76.223.150.219 | c150-219.smtp-out.eu-west-1.amazonses.com |
2 | — | Check → |
| 24.110.82.42 | i82-42.smtp-out.us-west-1.amazonses.com |
2 | — | Check → |
| 76.223.150.184 | c150-184.smtp-out.eu-west-1.amazonses.com |
2 | — | Check → |
| 76.223.150.197 | c150-197.smtp-out.eu-west-1.amazonses.com |
2 | — | Check → |
| 69.169.229.60 | b229-60.smtp-out.eu-west-1.amazonses.com |
2 | 1 | Check → |
| 206.55.154.27 | h154-27.smtp-out.ap-northeast-1.amazonses.com |
1 | — | Check → |
| 76.223.150.195 | c150-195.smtp-out.eu-west-1.amazonses.com |
1 | — | Check → |
| 206.55.154.21 | h154-21.smtp-out.ap-northeast-1.amazonses.com |
1 | — | Check → |
| 24.110.82.36 | i82-36.smtp-out.us-west-1.amazonses.com |
1 | — | Check → |
| 24.110.82.54 | i82-54.smtp-out.us-west-1.amazonses.com |
1 | — | Check → |
| 206.55.152.58 | h152-58.smtp-out.ap-northeast-1.amazonses.com |
1 | — | Check → |
| 206.55.152.41 | h152-41.smtp-out.ap-northeast-1.amazonses.com |
1 | 1 | Check → |
| 69.72.37.2 | v52.v5729ba63.use4.send.mailgun.net |
1 | 1 | Check → |
| Domain | ESPs detected | Delivery (7d) |
|---|---|---|
smailer1.binance.com | Amazon SES 15 | |
smailer2.binance.com | Amazon SES 15 | |
ses.binance.com | Amazon SES 12 | |
mgdirectmail.binance.com | Mailgun 1 |
