Get Email DetectiveDetect any senderright in your inbox Gmail Outlook

Figma

figma.com
🏆Rank #834 🏷 SaaS 🇺🇸United States ✓ Inbox 97%

Figma uses Customer.io for marketing email and SendGrid for transactional/notifications. They rank #834 in the Tranco list of most-popular domains. Email goes out from 3 different subdomains. Their email authentication setup is solid (score 90/100). We've recorded 8 ESP changes since first observing this brand.

Marketing ESPCustomer.io
Transactional ESPSendGrid
Total observations463
Active days46
Avg per active day10.1
Last activity📬 Active · today
Cadence~weekly
Compare Figma with another brand:

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

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

Authentication

DMARC enforced with p=quarantine — receivers actively reject or quarantine spoofed mail. No aggregate reporting destination configured.

SPF alignment: all 91 observed emails use a return-path aligned with figma.com (cio100993.figma.com, email.figma.com, em5250.friends.figma.com). SPF authenticates the visible From — supports DMARC directly.

DKIM alignment: all 345 observed emails sign with a domain aligned with figma.com (figma.com, cio100993.figma.com, friends.figma.com). DKIM authenticates the visible From — supports DMARC directly.

Transport & deliverability

TLS: 70% TLS 1.3, 30% TLS 1.2 (across 135 sends).

🚨 Extreme delivery delays observed

4 of 61 emails in the last 7 days were delayed beyond 5 minutes (7%) — peaks crossed 4 hours, which usually means stalled queues or hard receiver throttling. Slow sends averaged 1 h 35 min, peaked at 4 h 34 min. 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.

SendGrid ✓ confirmed Customer.io ✓ via Mailgun

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.

Adobe Campaign Google Workspace Mailgun Marketo

Probed: figma.com, cio100993.figma.com, email.figma.com, em5250.friends.figma.com, em325.figma.com, friends.figma.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 350 97.0%
promotions 11 3.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 272
98.9% 1.1% 0.0%
Customer.io 47
83.0% 17.0% 0.0%

ESP activity over time

Sep 29, 2025 – Jun 29, 2026 · 13 weeks with sends

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

71 0 SendGrid: 12 (week of 2025-09-29)12SendGrid: 12 (week of 2026-04-06)12SendGrid: 12 (week of 2026-04-13)12SendGrid: 1 (week of 2026-04-27)1SendGrid: 40 (week of 2026-05-04)Customer.io: 2 (week of 2026-05-04)42SendGrid: 29 (week of 2026-05-11)Customer.io: 7 (week of 2026-05-11)36SendGrid: 50 (week of 2026-05-18)Customer.io: 8 (week of 2026-05-18)58SendGrid: 29 (week of 2026-05-25)Customer.io: 7 (week of 2026-05-25)36SendGrid: 71 (week of 2026-06-01)71SendGrid: 61 (week of 2026-06-08)Customer.io: 10 (week of 2026-06-08)71SendGrid: 43 (week of 2026-06-15)Customer.io: 1 (week of 2026-06-15)44SendGrid: 47 (week of 2026-06-22)Customer.io: 14 (week of 2026-06-22)61SendGrid: 7 (week of 2026-06-29)7Sep 29 '25Oct 27 '25Nov 24 '25Dec 22 '25Jan 19 '26Feb 16 '26Mar 16 '26Apr 13 '26May 11 '26Jun 8 '26Jun 29 '26
🚨
🐢
🚨
SendGrid Customer.io

Similar brands using Customer.io

Sending IPs

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

IPHostnameObsPlacementReputation
167.89.87.53 o1.email.figma.com 122 5 Check →
168.245.25.177 xvfrkwbk.outbound-mail.sendgrid.net 115 9 Check →
149.72.216.165 wrqvdvxr.outbound-mail.sendgrid.net 88 17 Check →
167.89.79.69 xtrwqfqr.outbound-mail.sendgrid.net 85 17 Check →
159.112.243.48 v548.v5be21903.use4.send.mailgun.net 49 14 Check →
50.31.42.31 o1.ptr7481.bevy.com 2 Check →
149.72.24.138 o83.ptr4909.rainfocus.com 1 1 Check →

Sending domains

DomainESPs detectedDelivery (7d)
email.figma.comSendGrid 361
figma.comSendGrid 51 Customer.io 49🚨 4/27 extreme delay (avg 1 h 4 min, peak 4 h 34 min)
friends.figma.comSendGrid 2