Get Email DetectiveDetect any senderright in your inbox Gmail Outlook

Zacks

zacks.com
🏆Rank #18,942 🏷 Finance 🇺🇸United States 📥 Inbox 50%

Zacks uses Salesforce MC for marketing email and SendGrid for transactional/notifications. They rank #18,942 in the Tranco list of most-popular domains. Email goes out from 2 different subdomains. Their email authentication setup is solid (score 95/100).

Marketing ESPSalesforce MC
Transactional ESPSendGrid
Total observations19
Active days7
Avg per active day2.7
Last activity📬 Active · 5 days ago
Cadence~weekly
Compare Zacks with another brand:

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

Strong email setup
Authentication is in good shape — SPF, DKIM, and DMARC enforcement all configured.
95/100
SPF
pass
DKIM
pass
DMARC
pass (quarantine)
BIMI
verified VMC
Unsubscribe
one-click
SPF lookups 8/10

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

Authentication

DMARC reports sent to inboxmonster.com. Policy p=quarantine means receivers actively block or quarantine spoofed mail.

SPF alignment: all 19 observed emails use a return-path aligned with zacks.com (bounce.email.zacks.com, em4183.zacks.com). SPF authenticates the visible From — supports DMARC directly.

DKIM alignment: all 18 observed emails sign with a domain aligned with zacks.com (email.zacks.com, zacks.com). DKIM authenticates the visible From — supports DMARC directly.

Brand visibility

VMC issued by: digicert.

Transport & deliverability

TLS: modern — 100% TLS 1.3 (across 10 sends).

🐢 Slow delivery observed

1 of 2 emails in the last 7 days were delayed beyond 5 minutes (50%) — delays stayed within 5–15 minutes. Slow sends averaged 7 min 46 sec. 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.

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 SendGrid ✓ 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.

Acoustic Google Workspace HubSpot

Probed: zacks.com, bounce.email.zacks.com, em4183.zacks.com, email.zacks.com, grid1.zacks.com

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 8 50.0%
promotions 8 50.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 12
66.7% 33.3% 0.0%
SendGrid 4
0.0% 100.0% 0.0%

ESP activity over time

May 18 – Jun 25, 2026 · 7 days 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.

9 0 Salesforce MC: 1 (2026-05-18)1Salesforce MC: 2 (2026-06-06)2Salesforce MC: 3 (2026-06-09)3Salesforce MC: 6 (2026-06-12)SendGrid: 3 (2026-06-12)9Salesforce MC: 1 (2026-06-22)SendGrid: 1 (2026-06-22)2Salesforce MC: 1 (2026-06-24)1Salesforce MC: 1 (2026-06-25)105/1805/2205/2605/3006/0306/0706/1106/1506/1906/2306/25
🐢
Salesforce MC SendGrid

Similar brands using Salesforce MC

Sending IPs

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

IPHostnameObsPlacementReputation
13.111.28.182 mta2.email.zacks.com 6 2 Check →
13.111.28.183 mta3.email.zacks.com 6 Check →
192.254.123.151 o3.grid1.zacks.com 4 1 Check →
13.111.34.113 eh113.mta.exacttarget.com 2 Check →
13.111.28.181 mta.email.zacks.com 1 1 Check →

Sending domains

DomainESPs detectedDelivery (7d)
email.zacks.comSalesforce MC 15🐢 1/2 slow (avg 5 min 36 sec, peak 7 min 46 sec)
zacks.comSendGrid 4