Get Email DetectiveDetect any senderright in your inbox Gmail Outlook

Splunkcloud

splunkcloud.com
🏆Rank #2,513 🏷 SaaS 🇺🇸United States

Splunkcloud uses Amazon SES as their primary email service provider. They rank #2,513 in the Tranco list of most-popular domains. Their email authentication setup is good (score 65/100). Missing: DMARC enforcement.

Transactional ESPAmazon SES
Total observations21
Active days3
Avg per active day7.0
Last activity📬 Active · 8 days ago
Cadence~weekly
Compare Splunkcloud with another brand:

Email setup 65/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.
65/100
SPF
pass
DKIM
pass
DMARC
pass (none)
BIMI
none
Unsubscribe
standard
SPF lookups 3/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 Postmark DMARC. Policy p=none is monitor-only — receivers won't act on spoofing yet.

SPF alignment: observed emails use a third-party return-path (ft.com) — SPF passes there but doesn't align with splunkcloud.com, so DMARC has to rely on DKIM alignment.

DKIM alignment: all 21 observed emails sign with a domain aligned with splunkcloud.com (splunkcloud.com). DKIM authenticates the visible From — supports DMARC directly.

Transport & deliverability

TLS: modern — 100% TLS 1.3 (across 18 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.

Amazon SES observed

"Observed" pills mean we detected emails from these ESPs, but they don't appear in any SPF record we probed. They may still be properly authorized — sending infrastructure can live on subdomains we haven't seen yet, or use IP-listing instead of include: directives.

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 HubSpot Mandrill Marketo Salesforce MC SendGrid

Probed: splunkcloud.com, ft.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 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 8
100.0% 0.0% 0.0%

ESP activity over time

Jun 9 – Jun 22, 2026 · 3 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.

16 0 Amazon SES: 3 (2026-06-09)3Amazon SES: 2 (2026-06-16)2Amazon SES: 16 (2026-06-22)1606/0906/1106/1306/1506/1706/1906/21
Amazon SES

Similar brands using Amazon SES

Sending domains

DomainESPs detectedDelivery (7d)
splunkcloud.comAmazon SES 21