Alertrequest uses SparkPost

Alertrequest uses SparkPost as their primary email service provider. Their email authentication setup is good (score 80/100).

Transactional ESP

SparkPost

Total observations35

Active days18

Avg per active day1.9

Last activity📬 Active · 9 days ago

Cadence~every 2 days

Other technologies

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

HTML builder

Stripo

Compare Alertrequest with another brand:

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

80/100

SPF

pass

DKIM

pass

DMARC

pass (quarantine)

BIMI

none

Unsubscribe

one-click

SPF lookups 4/10

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

Authentication

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

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

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

Transport & deliverability

TLS: 0% TLS 1.3, 100% TLS 1.2 (across 19 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.

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

Amazon SES

Probed: alertrequest.com, spmailtechno.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.

Folder	Count	Share
inbox	30	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 %
SparkPost	30		100.0%	0.0%	0.0%

ESP activity over time

May 26 – Jun 22, 2026 · 20 days with sends

Last 30d Last 90d

By ESP By inbox/spam

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