Get Email DetectiveDetect any senderright in your inbox Gmail Outlook

Myrescuefund

myrescuefund.com
🌐Web popularity N/A 🏷 Nonprofit 🇺🇸United States

Myrescuefund uses Amazon SES as their primary email service provider. Their email authentication setup is incomplete (score 50/100). Missing: DMARC, DMARC enforcement.

Transactional ESPAmazon SES
Total observations6
Active days1
Avg per active day6.0
Last activity📬 Active · yesterday
Cadenceone-off
Compare Myrescuefund with another brand:

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

Setup has gaps
Some authentication is missing or weak — receivers may give less benefit of the doubt.
50/100
SPF
pass
DKIM
pass
DMARC
multiple records
BIMI
none
Unsubscribe
one-click
SPF lookups 2/10

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

Authentication

Multiple DMARC records published — receivers apply no DMARC at all (RFC 7489). The domain is effectively unprotected until the duplicate record is removed.

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

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

Transport & deliverability

TLS: modern — 100% TLS 1.3 (across 6 sends).

Delivery: fast — 100% of emails in the last 7 days arrive in under 10 seconds (across 6 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 ✓ confirmed

Other SPF authorizations

No additional ESPs authorized in the brand's SPF beyond the confirmed senders above.

Probed: myrescuefund.com, us-west-1.amazonses.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
promotions 3 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
0.0% 100.0% 0.0%

ESP activity over time

Jul 1 – Jul 1, 2026 · 1 day 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 Amazon SES: 6 (2026-07-01)607/01
Amazon SES

Similar brands using Amazon SES

Sending IPs

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

IPHostnameObsPlacementReputation
23.251.242.51 e242-51.smtp-out.us-west-1.amazonses.com 3 3 Check →
23.251.242.78 e242-78.smtp-out.us-west-1.amazonses.com 3 Check →

Sending domains

DomainESPs detectedDelivery (7d)
myrescuefund.comAmazon SES 6