Get Email DetectiveDetect any senderright in your inbox Gmail Outlook

Dust

dust.tt
🏆Rank #165,601 🏷 Media

Dust uses Customer.io for marketing email and SendGrid for transactional/notifications. They rank #165,601 in the Tranco list of most-popular domains. Email goes out from 2 different subdomains. Their email authentication setup is solid (score 85/100).

Marketing ESPCustomer.io
Transactional ESPSendGrid
Total observations2
Active days2
Avg per active day1.0
Last activity💤 Dormant · 5 weeks ago
Cadence~weekly

Other technologies

Non-ESP tools detected in this brand's emails. Independent of who sends — a brand can use any combination.

HTML builder Beefree SDK
Compare Dust with another brand:

Email setup 85/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.

Strong email setup
Authentication is in good shape — SPF, DKIM, and DMARC enforcement all configured.
85/100
SPF
pass
DKIM
pass
DMARC
pass (reject)
BIMI
none
Unsubscribe
one-click
SPF lookups 4/10
Authentication

DMARC reports sent to cloudflare.net. Policy p=reject means receivers actively block or quarantine spoofed mail.

SPF alignment: all 2 observed emails use a return-path aligned with dust.tt (cioeu103297.dust.tt, em3616.notifications.dust.tt). SPF authenticates the visible From — supports DMARC directly.

DKIM alignment: all 2 observed emails sign with a domain aligned with dust.tt (cioeu103297.dust.tt, notifications.dust.tt). DKIM authenticates the visible From — supports DMARC directly.

Other ESPs detected

Brands often use multiple ESPs (e.g. one for marketing, another for transactional/notifications).

None — only the primary ESP(s) shown above

Confirmed senders

ESPs 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.

SendGrid ✓ confirmed

Other SPF authorizations

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.

Google Workspace Mailgun

Probed: dust.tt, cioeu103297.dust.tt, em3616.notifications.dust.tt, notifications.dust.tt

Where emails landed (Gmail)

Folder distribution across all emails from this brand observed in Gmail inboxes. High inbox % = good deliverability; spam appearances are the headline signal.

FolderCountShare
inbox 2 100.0%

Placement by ESP

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 %
Customer.io 1
100.0% 0.0% 0.0%
SendGrid 1
100.0% 0.0% 0.0%

ESP activity over time

May 22 – May 29, 2026 · 2 days with sends

Daily observations per ESP. Brands often run multiple ESPs concurrently — marketing on one, transactional on another — so this chart shows usage rather than switches.

1 0 Customer.io: 1 (2026-05-22)1SendGrid: 1 (2026-05-29)105/2205/2305/2405/2505/2605/2705/2805/29
Customer.io SendGrid

Similar brands using Customer.io

Sending IPs

IP addresses dust.tt has been observed sending from, and where their mail landed in Gmail.

IPHostnameObsReputation
143.55.239.107 v5107.v5a39be5d.euw1.send.eu.mailgun.net 1 Check →
159.183.1.143 wfbthkvf.outbound-mail.sendgrid.net 1 Check →

Per-IP inbox / promotions / spam is being collected and will appear here as new emails are observed.

Sending domains

DomainESPs detectedDelivery (7d)
dust.ttCustomer.io 1
notifications.dust.ttSendGrid 1