Signitic uses Customer.io for marketing email and Amazon SES for transactional/notifications. They rank #176,128 in the Tranco list of most-popular domains. Email goes out from 2 different subdomains. Their email authentication setup is solid (score 95/100).
Amazon SESNon-ESP tools detected in this brand's emails. Independent of who sends — a brand can use any combination.
| HTML builder |
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 4 emails we've observed. DMARC policy is read live from DNS.
DMARC reports sent to signitic.com. Policy
p=quarantine means receivers actively block or quarantine spoofed mail.
SPF alignment: 90% of observed emails use an aligned return-path (cioeu116424.mail.signitic.com, ses.mail.signitic.com, cioeu84931.billing.signitic.com); the rest use third-party paths (red-robot.net) where DMARC has to rely on DKIM alignment.
DKIM alignment: all 20 observed emails sign with a domain aligned with signitic.com (cioeu116424.mail.signitic.com, mail.signitic.com, cioeu84931.billing.signitic.com). DKIM authenticates the visible From — supports DMARC directly.
TLS: 43% TLS 1.3, 57% TLS 1.2 (across 21 sends).
Delivery: fast — 100% of emails in the last 7 days arrive in under 10 seconds (across 3 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: signitic.com, ses.mail.signitic.com, cioeu116424.mail.signitic.com, cioeu84931.billing.signitic.com, red-robot.net, mail.signitic.com, billing.signitic.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 | 50.0% |
| promotions | 9 | 50.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 % |
|---|---|---|---|---|---|
| Customer.io | 13 | 30.8% | 69.2% | 0.0% | |
| Amazon SES | 5 | 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 signitic.com has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Placement | Reputation |
|---|---|---|---|---|
| 198.244.60.100 | a100.a5d06dfa.euw1.send.eu.mailgun.net |
6 | 1 | Check → |
| 23.251.246.59 | e246-59.smtp-out.eu-west-3.amazonses.com |
3 | — | Check → |
| 23.251.246.65 | e246-65.smtp-out.eu-west-3.amazonses.com |
3 | — | Check → |
| 185.250.238.78 | v578.v5bda8fb2.euw1.send.eu.mailgun.net |
3 | — | Check → |
| 198.244.60.102 | a102.a5d06dfa.euw1.send.eu.mailgun.net |
3 | — | Check → |
| Domain | ESPs detected | Delivery (7d) |
|---|---|---|
mail.signitic.com | Customer.io 10 Amazon SES 8 | |
billing.signitic.com | Customer.io 3 |