Get Email DetectiveDetect any senderright in your inbox Gmail Outlook

Getrecall

getrecall.ai
🏆Rank #443,914

Getrecall uses Mailtrap as their primary email service provider. They rank #443,914 in the Tranco list of most-popular domains. Their email authentication setup is good (score 73/100). Missing: DMARC enforcement.

Transactional ESPMailtrap
Total observations1
Active days1
Avg per active day1.0
Last activity💤 Dormant · 5 weeks ago
Cadenceone-off

Other technologies

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

HTML builder Unlayer
Compare Getrecall 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 6/10
Authentication

DMARC reports sent to brevo.com. Policy p=none is monitor-only — receivers won't act on spoofing yet.

SPF alignment: all 1 observed email use a return-path aligned with getrecall.ai (mt98.getrecall.ai). SPF authenticates the visible From — supports DMARC directly.

DKIM alignment: all 1 observed email sign with a domain aligned with getrecall.ai (getrecall.ai). 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.

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

Brevo Google Workspace SendGrid

Probed: getrecall.ai, mt98.getrecall.ai

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 1 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 %
Mailtrap 1
100.0% 0.0% 0.0%

ESP activity over time

May 25 – May 25, 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.

1 0 Mailtrap: 1 (2026-05-25)105/25
Mailtrap

Similar brands using Mailtrap

Sending IPs

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

IPHostnameObsReputation
45.158.83.3 smtp-83-3.mailtrap.live 1 Check →

Per-IP inbox / promotions / spam is being collected and will appear here as new emails are observed.

Sending domains

DomainESPs detectedDelivery (7d)
getrecall.aiMailtrap 1