Buildbetter uses Amazon SES as their primary email service provider. Their email authentication setup is good (score 73/100). Missing: DMARC enforcement, one-click unsubscribe.
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 1 email 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.
SPF alignment: all 12 observed emails use a return-path aligned with buildbetter.ai (envelope.hey.buildbetter.ai). SPF authenticates the visible From — supports DMARC directly.
DKIM alignment: all 10 observed emails sign with a domain aligned with buildbetter.ai (hey.buildbetter.ai). DKIM authenticates the visible From — supports DMARC directly.
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: buildbetter.ai, envelope.hey.buildbetter.ai, hey.buildbetter.ai
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 | 14 | 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 | 12 | 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 buildbetter.ai has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Placement | Reputation |
|---|---|---|---|---|
| 216.221.169.107 | g169-107.smtp-out.amazonses.com |
4 | — | Check → |
| 24.110.89.109 | i89-109.smtp-out.amazonses.com |
4 | — | Check → |
| 76.223.139.17 | c139-17.smtp-out.amazonses.com |
3 | — | Check → |
| 23.251.229.168 | e229-168.smtp-out.amazonses.com |
2 | 1 | Check → |
| 54.240.39.204 | a39-204.smtp-out.amazonses.com |
1 | — | Check → |
| Domain | ESPs detected | Delivery (7d) |
|---|---|---|
hey.buildbetter.ai | Amazon SES 14 |
