Peopleforce uses HubSpot for marketing email and Amazon SES for transactional/notifications. They rank #158,540 in the Tranco list of most-popular domains. Their email authentication setup is solid (score 85/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 DMARC Digests. Policy
p=reject means receivers actively block or quarantine spoofed mail.
SPF alignment: 93% of observed emails use an aligned return-path (mail.peopleforce.io); the rest use third-party paths (bf04.eu1.hubspotemail.net) where DMARC has to rely on DKIM alignment.
DKIM alignment: all 27 observed emails sign with a domain aligned with peopleforce.io (peopleforce.io). DKIM authenticates the visible From — supports DMARC directly.
TLS: modern — 92% TLS 1.3 (across 12 sends).
Delivery: fast — 100% of emails in the last 7 days arrive in under 10 seconds (across 10 sends).
Gmail's own filter showed these warnings to real subscribers in their inbox — independent of SPF/DKIM/DMARC pass/fail status. A consistent pattern often signals reputation issues or brand-impersonation concerns.
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: peopleforce.io, mail.peopleforce.io, bf04.eu1.hubspotemail.net
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 | 44 | 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 | 40 | 100.0% | 0.0% | 0.0% | |
| HubSpot | 3 | 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 peopleforce.io has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Placement | Reputation |
|---|---|---|---|---|
| 69.169.224.58 | b224-58.smtp-out.eu-central-1.amazonses.com |
14 | 2 | Check → |
| 69.169.224.57 | b224-57.smtp-out.eu-central-1.amazonses.com |
6 | 2 | Check → |
| 69.169.224.52 | b224-52.smtp-out.eu-central-1.amazonses.com |
5 | 1 | Check → |
| 69.169.224.51 | b224-51.smtp-out.eu-central-1.amazonses.com |
4 | — | Check → |
| 69.169.224.50 | b224-50.smtp-out.eu-central-1.amazonses.com |
4 | 2 | Check → |
| 69.169.224.56 | b224-56.smtp-out.eu-central-1.amazonses.com |
4 | 1 | Check → |
| 69.169.224.53 | b224-53.smtp-out.eu-central-1.amazonses.com |
4 | — | Check → |
| 108.179.145.178 | 4f2n1w.bf04.eu1.hubspotemail.net |
3 | 1 | Check → |
| 69.169.224.59 | b224-59.smtp-out.eu-central-1.amazonses.com |
1 | — | Check → |
| Domain | ESPs detected | Delivery (7d) |
|---|---|---|
peopleforce.io | Amazon SES 42 HubSpot 3 |