Get Email DetectiveDetect any senderright in your inbox Gmail Outlook

Pipedrive

pipedrive.com
🏆Rank #8,343 🏷 SaaS 🇪🇪Estonia ✓ Inbox 100%

Pipedrive uses Customer.io for marketing email and SendGrid for transactional/notifications. They rank #8,343 in the Tranco list of most-popular domains. Email goes out from 4 different subdomains. Their email authentication setup is solid (score 100/100).

Marketing ESPCustomer.io
Transactional ESPSendGrid
Total observations46
Active days30
Avg per active day1.5
Last activity📬 Active · yesterday
Cadence~every 3 days

Other technologies

Non-ESP tools detected in this brand's emails. Independent of who sends — a brand can use any combination.

HTML builder Beefree SDK
Compare Pipedrive with another brand:

Email setup 100/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.
100/100
SPF
pass
DKIM
pass
DMARC
pass (reject)
BIMI
verified VMC
Unsubscribe
one-click
SPF lookups 7/10

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

Authentication

DMARC reports sent to Red Sift OnDMARC. Policy p=reject means receivers actively block or quarantine spoofed mail.

SPF alignment: 98% of observed emails use an aligned return-path (em8719.activities.pipedrive.com, em2577.email.pipedrive.com, em3269.pipedrive.com); the rest use third-party paths (amazonses.com) where DMARC has to rely on DKIM alignment.

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

Brand visibility

VMC issued by: digicert.

Transport & deliverability

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

Delivery: fast — 100% of emails in the last 7 days arrive in under 10 seconds (across 10 sends).

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.

SendGrid ✓ confirmed Customer.io ✓ via SendGrid

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.

Amazon SES

Probed: pipedrive.com, amazonses.com, em8719.activities.pipedrive.com, em2577.email.pipedrive.com, em2894.pipedrive.com, em3269.pipedrive.com, em512.scheduler.pipedrive.com, em7341.pipedrive.com, activities.pipedrive.com, email.pipedrive.com, scheduler.pipedrive.com, email2.pipedrive.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 46 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 %
SendGrid 35
100.0% 0.0% 0.0%
Customer.io 5
100.0% 0.0% 0.0%

ESP activity over time

May 5 – Jun 29, 2026 · 29 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.

4 0 SendGrid: 1 (2026-05-05)1SendGrid: 1 (2026-05-06)1SendGrid: 1 (2026-05-07)1Customer.io: 1 (2026-05-08)1SendGrid: 1 (2026-05-11)1SendGrid: 1 (2026-05-12)1SendGrid: 1 (2026-05-14)1SendGrid: 1 (2026-05-15)1SendGrid: 1 (2026-05-21)1SendGrid: 1 (2026-05-22)Customer.io: 1 (2026-05-22)2SendGrid: 1 (2026-05-26)1SendGrid: 2 (2026-05-29)2SendGrid: 4 (2026-06-02)4SendGrid: 2 (2026-06-05)2SendGrid: 1 (2026-06-06)1SendGrid: 2 (2026-06-09)2SendGrid: 2 (2026-06-10)2SendGrid: 1 (2026-06-11)1Customer.io: 2 (2026-06-12)2SendGrid: 1 (2026-06-17)1SendGrid: 2 (2026-06-18)2SendGrid: 1 (2026-06-19)Customer.io: 1 (2026-06-19)2SendGrid: 2 (2026-06-20)2SendGrid: 1 (2026-06-22)1SendGrid: 1 (2026-06-23)1SendGrid: 1 (2026-06-24)1SendGrid: 2 (2026-06-25)2SendGrid: 2 (2026-06-26)Customer.io: 1 (2026-06-26)3SendGrid: 2 (2026-06-29)205/0505/1105/1705/2305/2906/0406/1006/1606/2206/28
SendGrid Customer.io

Similar brands using Customer.io

Sending IPs

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

IPHostnameObsPlacementReputation
159.183.3.24 wfbthpkv.outbound-mail.sendgrid.net 12 5 Check →
208.117.52.78 o1.email.pipedrive.com 11 1 Check →
159.183.27.38 wfbtkbns.outbound-mail.sendgrid.net 11 3 Check →
159.183.171.139 o3.ptr3047.email2.pipedrive.com 5 2 Check →
168.245.93.185 o2.email2.pipedrive.com 2 Check →
159.183.18.148 o5.ptr6129.email2.pipedrive.com 2 1 Check →
54.240.48.42 a48-42.smtp-out.amazonses.com 1 Check →
159.183.175.40 o4.ptr3822.email2.pipedrive.com 1 Check →

Sending domains

DomainESPs detectedDelivery (7d)
activities.pipedrive.comSendGrid 33
pipedrive.comSendGrid 6
email.pipedrive.comCustomer.io 6
scheduler.pipedrive.comSendGrid 1