Piletilevi uses Smaily for marketing email and Postmark for transactional/notifications. They rank #276,756 in the Tranco list of most-popular domains. Their email authentication setup is solid (score 85/100). We've recorded 1 ESP change since first observing this brand.
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.
SPF / DKIM / DMARC above reflect the last 6 emails we've observed. DMARC policy is read live from DNS.
DMARC reports sent to piletilevi.ee. Policy
p=reject means receivers actively block or quarantine spoofed mail.
SPF alignment: 16% of observed emails use an aligned return-path (pm-bounces.piletilevi.ee); the rest use third-party paths (smlydlv3.net, smlydlv1.net) where DMARC has to rely on DKIM alignment.
DKIM alignment: all 37 observed emails sign with a domain aligned with piletilevi.ee (piletilevi.ee). DKIM authenticates the visible From — supports DMARC directly.
TLS: 14% TLS 1.3, 86% TLS 1.2 (across 14 sends).
1 of 4 emails in the last 7 days were delayed beyond 5 minutes (25%) — delays stayed within 5–15 minutes. Slow sends averaged 9 min 50 sec. Healthy senders deliver in under 30 seconds. Consistent delays usually mean greylisting, reputation-based throttling, or receiver-side filter scrutiny — worth investigating sender reputation and authentication setup.
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: piletilevi.ee, smlydlv3.net, pm-bounces.piletilevi.ee, smlydlv1.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 | 42 | 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 % |
|---|---|---|---|---|---|
| Postmark | 7 | 100.0% | 0.0% | 0.0% | |
| Smaily | 35 | 100.0% | 0.0% | 0.0% |
Weekly 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 piletilevi.ee has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Placement | Reputation |
|---|---|---|---|---|
| 149.154.156.9 | b9.mta01.smlydlv3.net |
9 | 1 | Check → |
| 149.154.156.5 | b5.mta01.smlydlv3.net |
9 | — | Check → |
| 149.154.156.7 | b7.mta01.smlydlv3.net |
6 | 1 | Check → |
| 149.154.156.10 | b10.mta01.smlydlv3.net |
6 | 2 | Check → |
| 149.154.156.8 | b8.mta01.smlydlv3.net |
5 | — | Check → |
| 50.31.156.114 | sc-ord-mta114.mtasv.net |
2 | — | Check → |
| 50.31.156.126 | sc-ord-mta126.mtasv.net |
2 | — | Check → |
| 50.31.156.124 | sc-ord-mta124.mtasv.net |
2 | 2 | Check → |
| 149.154.156.6 | b6.mta01.smlydlv1.net |
1 | — | Check → |
| 50.31.156.113 | sc-ord-mta113.mtasv.net |
1 | — | Check → |