Get Email DetectiveDetect any senderright in your inbox Gmail Outlook

Katiemckiever

katiemckiever.com
🏆Rank N/A 🏷 Media 🇺🇸United States

Katiemckiever uses Flodesk for marketing email and Amazon SES for transactional/notifications. Their email authentication setup is good (score 73/100). Missing: DMARC enforcement.

Marketing ESPFlodesk
Transactional ESPAmazon SES
Total observations2
Active days2
Avg per active day1.0
Last activity📬 Active · yesterday
Cadence~every 2 weeks
Compare Katiemckiever 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 3/10

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

Authentication

DMARC published as p=none with no rua= reporting — monitor-only, and the sender isn't collecting reports either.

SPF alignment: all 2 observed emails use a return-path aligned with katiemckiever.com (fdesp.katiemckiever.com). SPF authenticates the visible From — supports DMARC directly.

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

Probed: katiemckiever.com, fdesp.katiemckiever.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 2 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 1
100.0% 0.0% 0.0%
Flodesk 1
100.0% 0.0% 0.0%

ESP activity over time

Jun 1 – Jun 29, 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.

1 0 Flodesk: 1 (2026-06-01)1Amazon SES: 1 (2026-06-29)106/0106/0406/0706/1006/1306/1606/1906/2206/2506/28
Flodesk Amazon SES

Similar brands using Flodesk

Sending IPs

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

IPHostnameObsPlacementReputation
54.240.64.19 a64-19.smtp-out.amazonses.com 1 Check →
54.240.64.25 a64-25.smtp-out.amazonses.com 1 1 Check →

Sending domains

DomainESPs detectedDelivery (7d)
katiemckiever.comFlodesk 1 Amazon SES 1