Peopleperhour uses Amazon SES as their primary email service provider. They rank #25,443 in the Tranco list of most-popular domains. Their email authentication setup is solid (score 85/100). Missing: 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 3 emails we've observed. DMARC policy is read live from DNS.
DMARC enforced with p=reject — receivers actively reject or quarantine spoofed mail. No aggregate reporting destination configured.
SPF alignment: observed emails use a third-party return-path (amazonses.com) — SPF passes there but doesn't align with peopleperhour.com, so DMARC has to rely on DKIM alignment.
DKIM alignment: all 9 observed emails sign with a domain aligned with peopleperhour.com (peopleperhour.com). DKIM authenticates the visible From — supports DMARC directly.
TLS: modern — 100% TLS 1.3 (across 6 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: peopleperhour.com, amazonses.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 | 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 | 9 | 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 peopleperhour.com has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Placement | Reputation |
|---|---|---|---|---|
| 54.240.8.208 | a8-208.smtp-out.amazonses.com |
2 | — | Check → |
| 54.240.48.178 | a48-178.smtp-out.amazonses.com |
2 | 2 | Check → |
| 54.240.11.75 | a11-75.smtp-out.amazonses.com |
1 | — | Check → |
| 54.240.11.16 | a11-16.smtp-out.amazonses.com |
1 | — | Check → |
| 54.240.8.21 | a8-21.smtp-out.amazonses.com |
1 | — | Check → |
| 54.240.11.6 | a11-6.smtp-out.amazonses.com |
1 | — | Check → |
| 54.240.11.70 | a11-70.smtp-out.amazonses.com |
1 | 1 | Check → |
| Domain | ESPs detected | Delivery (7d) |
|---|---|---|
peopleperhour.com | Amazon SES 9 |
