Patch uses Sailthru as their primary email service provider. They rank #4,440 in the Tranco list of most-popular domains. Their email authentication setup is solid (score 85/100).
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 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: all 28 observed emails use a return-path aligned with patch.com (bounce.patch.com). SPF authenticates the visible From — supports DMARC directly.
DKIM alignment: all 28 observed emails sign with a domain aligned with patch.com (patch.com). DKIM authenticates the visible From — supports DMARC directly.
TLS: modern — 100% TLS 1.3 (across 22 sends).
Delivery (last 7 days): 31% under 10 seconds, 15% over 1 minute (across 13 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: patch.com, bounce.patch.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 | 25 | 92.6% |
| promotions | 2 | 7.4% |
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 % |
|---|---|---|---|---|---|
| Sailthru | 26 | 92.3% | 7.7% | 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 patch.com has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Placement | Reputation |
|---|---|---|---|---|
| 192.64.237.8 | patch-d.sailthru.com |
6 | 3 | Check → |
| 192.64.236.136 | mta236-136.sailthru.com |
6 | 2 | Check → |
| 192.64.238.40 | mta238-40.sailthru.com |
6 | 6 | Check → |
| 192.64.238.63 | mta238-63.sailthru.com |
3 | — | Check → |
| 192.64.236.29 | mta236-29.sailthru.com |
2 | 1 | Check → |
| 192.64.237.9 | patch-c.sailthru.com |
2 | — | Check → |
| 192.64.237.10 | patch-b.sailthru.com |
1 | — | Check → |
| 192.64.236.135 | mta236-135.sailthru.com |
1 | — | Check → |
| 192.64.236.28 | mta236-28.sailthru.com |
1 | — | Check → |
| 192.64.237.220 | patch-a.sailthru.com |
1 | 1 | Check → |
| Domain | ESPs detected | Delivery (7d) |
|---|---|---|
patch.com | Sailthru 29 |