Netlify uses HubSpot for marketing email and Amazon SES for transactional/notifications. They rank #4,556 in the Tranco list of most-popular domains. 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 2 emails we've observed. DMARC policy is read live from DNS.
DMARC reports sent to dmarcian. Policy
p=reject means receivers actively block or quarantine spoofed mail.
SPF alignment: 60% of observed emails use an aligned return-path (smtp-out-ses.netlify.com, 7477936t.netlify.com); the rest use third-party paths (bf53x.hubspotemail.net) where DMARC has to rely on DKIM alignment.
DKIM alignment: all 10 observed emails sign with a domain aligned with netlify.com (netlify.com, 7477936t.netlify.com). DKIM authenticates the visible From — supports DMARC directly.
Delivery: fast — 100% of emails in the last 7 days arrive in under 10 seconds (across 2 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: netlify.com, smtp-out-ses.netlify.com, bf53x.hubspotemail.net, 7477936t.netlify.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 | 9 | 81.8% |
| promotions | 2 | 18.2% |
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 | 4 | 100.0% | 0.0% | 0.0% | |
| HubSpot | 6 | 66.7% | 33.3% | 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 netlify.com has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Placement | Reputation |
|---|---|---|---|---|
| 54.240.9.11 | a9-11.smtp-out.amazonses.com |
2 | — | Check → |
| 158.247.23.169 | bid47o7.bf53x.hubspotemail.net |
2 | — | Check → |
| 158.247.17.208 | bid46jm.7477936t.netlify.com |
2 | — | Check → |
| 54.240.48.194 | a48-194.smtp-out.amazonses.com |
2 | — | Check → |
| 158.247.23.131 | bid47n5.bf53x.hubspotemail.net |
1 | — | Check → |
| 158.247.23.168 | bid47o6.bf53x.hubspotemail.net |
1 | 1 | Check → |
| 158.247.23.195 | bid47px.bf53x.hubspotemail.net |
1 | 1 | Check → |
| Domain | ESPs detected | Delivery (7d) |
|---|---|---|
netlify.com | HubSpot 7 Amazon SES 4 |