Get Email DetectiveDetect any senderright in your inbox Gmail Outlook

Plaud

plaud.ai
🏆Rank #40,529 🏷 SaaS 🇺🇸United States

Plaud uses Klaviyo for marketing email and Amazon SES for transactional/notifications. They rank #40,529 in the Tranco list of most-popular domains. Their email authentication setup is good (score 73/100). Missing: DMARC enforcement.

Marketing ESPKlaviyo
Transactional ESPAmazon SES
Total observations7
Active days2
Avg per active day3.5
Last activity💤 Dormant · 6 weeks ago
Cadencealmost daily
Interested in using Klaviyo?
Learn about the pros and cons at .
Read the review →
Compare Plaud 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 10/10
Authentication

DMARC reports sent to izyrec.com. Policy p=none is monitor-only — receivers won't act on spoofing yet.

SPF alignment: all 7 observed emails use a return-path aligned with plaud.ai (ases.plaud.ai, email.plaud.ai). SPF authenticates the visible From — supports DMARC directly.

DKIM alignment: all 7 observed emails sign with a domain aligned with plaud.ai (plaud.ai). 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.

Amazon SES ✓ 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.

Google Workspace Mailchimp Mailgun SendGrid

Probed: plaud.ai, email.plaud.ai, ases.plaud.ai

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 4 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 %
Amazon SES 3
100.0% 0.0% 0.0%
Klaviyo 1
100.0% 0.0% 0.0%

ESP activity over time

May 21 – May 22, 2026 · 2 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.

6 0 Klaviyo: 1 (2026-05-21)1Amazon SES: 6 (2026-05-22)605/2105/22
Amazon SES Klaviyo

Similar brands using Klaviyo

Sending IPs

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

IPHostnameObsReputation
54.240.27.23 a27-23.smtp-out.us-west-2.amazonses.com 2 Check →
168.245.31.178 o1328.shared.klaviyomail.com 1 Check →
54.240.27.192 a27-192.smtp-out.us-west-2.amazonses.com 1 Check →

Per-IP inbox / promotions / spam is being collected and will appear here as new emails are observed.

Sending domains

DomainESPs detectedDelivery (7d)
plaud.aiAmazon SES 6 Klaviyo 1