Get Email DetectiveDetect any senderright in your inbox Gmail Outlook

Michaelsenoff

michaelsenoff.com
🏆Rank N/A 🏷 Media 🇺🇸United States ✓ Inbox 100%

Michaelsenoff uses AWeber as their primary email service provider. Their email authentication setup is good (score 73/100). Missing: DMARC enforcement.

Marketing ESPAWeber
Total observations18
Active days7
Avg per active day2.6
Last activity📬 Active · 2 days ago
Cadencealmost daily
Interested in using AWeber?
Learn about the pros and cons at .
Read the review →
Compare Michaelsenoff 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 1/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 hardtofindseminars.com. Policy p=none is monitor-only — receivers won't act on spoofing yet.

SPF alignment: observed emails use a third-party return-path (smtp-soi-g26-176.aweber.com, smtp-soi-g14-139.aweber.com, smtp-soi-g14-140.aweber.com) — SPF passes there but doesn't align with michaelsenoff.com, so DMARC has to rely on DKIM alignment.

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

Transport & deliverability

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

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

AWeber ✓ via sending IP

Other SPF authorizations

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

Probed: michaelsenoff.com, smtp-soi-g26-176.aweber.com, smtp-soi-g22-164.aweber.com, smtp-soi-g28-183.aweber.com, smtp-soi-g28-181.aweber.com, smtp-soi-g14-139.aweber.com, smtp-soi-g14-141.aweber.com, smtp-soi-g14-140.aweber.com, smtp-soi-g24-169.aweber.com, smtp-soi-g30-188.aweber.com, smtp-soi-g09-126.aweber.com, smtp-soi-g09-125.aweber.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 15 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 %
AWeber 15
100.0% 0.0% 0.0%

ESP activity over time

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

4 0 AWeber: 3 (2026-06-22)3AWeber: 4 (2026-06-24)4AWeber: 2 (2026-06-25)2AWeber: 1 (2026-06-26)1AWeber: 2 (2026-06-27)2AWeber: 4 (2026-06-28)4AWeber: 2 (2026-06-29)206/2206/2306/2406/2506/2606/2706/2806/29
AWeber

Similar brands using AWeber

Sending IPs

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

IPHostnameObsPlacementReputation
204.194.223.176 smtp-soi-g26-176.aweber.com 2 2 Check →
204.194.223.139 smtp-soi-g14-139.aweber.com 2 2 Check →
204.194.223.140 smtp-soi-g14-140.aweber.com 2 2 Check →
204.194.223.126 smtp-soi-g09-126.aweber.com 2 1 Check →
204.194.223.125 smtp-soi-g09-125.aweber.com 2 1 Check →
204.194.223.164 smtp-soi-g22-164.aweber.com 1 1 Check →
204.194.223.183 smtp-soi-g28-183.aweber.com 1 1 Check →
204.194.223.181 smtp-soi-g28-181.aweber.com 1 1 Check →
204.194.223.141 smtp-soi-g14-141.aweber.com 1 Check →
204.194.223.169 smtp-soi-g24-169.aweber.com 1 1 Check →
204.194.223.188 smtp-soi-g30-188.aweber.com 1 1 Check →
204.194.223.161 smtp-soi-g21-161.aweber.com 1 1 Check →
204.194.223.124 smtp-soi-g09-124.aweber.com 1 1 Check →

Sending domains

DomainESPs detectedDelivery (7d)
michaelsenoff.comAWeber 18