Get Email DetectiveDetect any senderright in your inbox Gmail Outlook

Ticketmaster

ticketmaster.com.mx
🏆Rank #14,332 🏷 Entertainment 🇺🇸United States

Ticketmaster uses Salesforce MC as their primary email service provider. They rank #14,332 in the Tranco list of most-popular domains. Email goes out from 2 different subdomains. Their email authentication setup is good (score 73/100). Missing: DMARC enforcement.

Marketing ESPSalesforce MC
Total observations2
Active days2
Avg per active day1.0
Last activity📬 Active · 2 days ago
Cadence~monthly
Compare Ticketmaster with another brand:

Email setup 73/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.

Solid setup, room to improve
Most authentication signals are present. A couple of pieces would tighten things up.
73/100
SPF
pass
DKIM
pass
DMARC
pass (none)
BIMI
none
Unsubscribe
one-click
SPF lookups 7/10

SPF / DKIM / DMARC above reflect the last 1 email we've observed. DMARC policy is read live from DNS.

Authentication

DMARC reports sent to Return Path / Validity. Policy p=none is monitor-only — receivers won't act on spoofing yet.

SPF alignment: all 1 observed email use a return-path aligned with ticketmaster.com.mx (bounce.info.ticketmaster.com.mx). SPF authenticates the visible From — supports DMARC directly.

DKIM alignment: all 1 observed email sign with a domain aligned with ticketmaster.com.mx (info.ticketmaster.com.mx). DKIM authenticates the visible From — supports DMARC directly.

Other ESPs detected

Brands often use multiple ESPs (e.g. one for marketing, another for transactional/notifications).

None — only the primary ESP(s) shown above

Confirmed senders

ESPs 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.

Salesforce MC ✓ confirmed

Other SPF authorizations

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.

Mandrill Microsoft 365 SendGrid

Probed: ticketmaster.com.mx, bounce.info.ticketmaster.com.mx, emails.ticketmaster.com.mx, info.ticketmaster.com.mx

Where emails landed (Gmail)

Folder distribution across all emails from this brand observed in Gmail inboxes. High inbox % = good deliverability; spam appearances are the headline signal.

FolderCountShare
inbox 2 100.0%

Placement by ESP

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 MC 2
100.0% 0.0% 0.0%

ESP activity over time

Jun 29 – Jun 29, 2026 · 1 day with sends

Daily observations per ESP. Brands often run multiple ESPs concurrently — marketing on one, transactional on another — so this chart shows usage rather than switches.

1 0 Salesforce MC: 1 (2026-06-29)106/29
Salesforce MC

Similar brands using Salesforce MC

Sending IPs

IP addresses ticketmaster.com.mx has been observed sending from, and where their mail landed in Gmail.

IPHostnameObsPlacementReputation
13.111.59.52 mta.info.ticketmaster.nl 1 Check →
13.111.59.34 mta.mailings.tickethour.com 1 1 Check →

Sending domains

DomainESPs detectedDelivery (7d)
emails.ticketmaster.com.mxSalesforce MC 1
info.ticketmaster.com.mxSalesforce MC 1