Allianzlife uses Marketo for marketing email and Salesforce CRM for transactional/notifications. They rank #59,879 in the Tranco list of most-popular domains. We've also observed sends via Responsys. Email goes out from 4 different subdomains. 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 10 emails we've observed. DMARC policy is read live from DNS.
DMARC reports sent to allianz.com. Policy
p=reject means receivers actively block or quarantine spoofed mail.
SPF alignment: 72% of observed emails use an aligned return-path (envelope1.allianzlife.com, envelope.allianzlife.com); the rest use third-party paths (ljn8z3xtmgl99yqy.51in19veu7f7wkxv.3irk6za.6-ivsleas.usa706.bnc.salesforce.com, 3eregafs8fahwefz.qv1cvcs4j7qgogfj.2q7e6.6-ivsleas.usa706.bnc.salesforce.com) where DMARC has to rely on DKIM alignment.
DKIM alignment: all 30 observed emails sign with a domain aligned with allianzlife.com (connect3.allianzlife.com, connect.allianzlife.com, connect4.allianzlife.com). DKIM authenticates the visible From — supports DMARC directly.
TLS: 63% TLS 1.3, 38% TLS 1.2 (across 16 sends).
Delivery: fast — 100% of emails in the last 7 days arrive in under 10 seconds (across 4 sends).
Brands often use multiple ESPs (e.g. one for marketing, another for transactional/notifications).
Responsys 12ESPs 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: allianzlife.com, envelope1.allianzlife.com, envelope.allianzlife.com, ljn8z3xtmgl99yqy.51in19veu7f7wkxv.3irk6za.6-ivsleas.usa706.bnc.salesforce.com, 3eregafs8fahwefz.qv1cvcs4j7qgogfj.2q7e6.6-ivsleas.usa706.bnc.salesforce.com, connect3.allianzlife.com, connect.allianzlife.com, connect4.allianzlife.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 | 30 | 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 % |
|---|---|---|---|---|---|
| Salesforce CRM | 5 | 100.0% | 0.0% | 0.0% | |
| Responsys | 12 | 100.0% | 0.0% | 0.0% | |
| Marketo | 13 | 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 allianzlife.com has been observed sending from, and where their mail landed in Gmail.
| Domain | ESPs detected | Delivery (7d) |
|---|---|---|
connect3.allianzlife.com | Marketo 13 | |
connect.allianzlife.com | Responsys 7 | |
connect4.allianzlife.com | Responsys 5 | |
allianzlife.com | Salesforce CRM 5 |