Piletitasku uses Smaily for marketing email and Mailjet for transactional/notifications. They're the #547,649 most-visited website overall, per Tranco (a web-popularity measure, not an email one). Their email authentication setup is good (score 83/100). Missing: DMARC enforcement.
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 5 emails we've observed. DMARC policy is read live from DNS.
DMARC reports sent to DMARC Digests. Policy
p=none is monitor-only — receivers won't act on spoofing yet.
SPF alignment: observed emails use a third-party return-path (smlydlv3.net, a1677885.bnc3.mailjet.com) — SPF passes there but doesn't align with piletitasku.ee, so DMARC has to rely on DKIM alignment.
DKIM alignment: all 17 observed emails sign with a domain aligned with piletitasku.ee (piletitasku.ee). DKIM authenticates the visible From — supports DMARC directly.
TLS: 0% TLS 1.3, 100% TLS 1.2 (across 8 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 14 min. 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: piletitasku.ee, smlydlv3.net, a1677885.bnc3.mailjet.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 | 18 | 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 % |
|---|---|---|---|---|---|
| Mailjet | 3 | 100.0% | 0.0% | 0.0% | |
| Smaily | 15 | 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 piletitasku.ee has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Placement | Reputation |
|---|---|---|---|---|
| 149.154.156.10 | b10.mta01.smlydlv3.net |
5 | 1 | Check → |
| 149.154.156.7 | b7.mta01.smlydlv3.net |
5 | 1 | Check → |
| 149.154.156.5 | b5.mta01.smlydlv3.net |
3 | — | Check → |
| 149.154.156.8 | b8.mta01.smlydlv3.net |
2 | 2 | Check → |
| 87.253.234.136 | o136.p9.mailjet.com |
2 | 2 | Check → |
| 87.253.235.16 | o16.p10.mailjet.com |
1 | — | Check → |