amoCRM (Kommo) SaaS sender

According to Live Direct Marketing's daily Tranco top-1M scan (July 13, 2026), amoCRM (Kommo) is the SaaS sender for 300 domains — 0.05% of 617,702 SPF-publishing domains. Detection method: include: mechanisms in the SPF record.

Key facts

amoCRM (Kommo) is a customer relationship management platform that enables businesses to manage customer interactions and send transactional and marketing email on behalf of their domains. Like other multi-tenant SaaS email platforms, it uses SPF, DKIM, and DMARC to authenticate outbound mail sent by its customers.

In email infrastructure surveys, amoCRM's presence is concentrated amongst smaller to mid-market websites rather than the largest enterprises, with particular prevalence in the Russian-language internet. This distribution pattern means organisations which send email or manage mail infrastructure frequently encounter amoCRM's SPF include mechanisms and should understand how its multi-tenant architecture affects sender reputation and deliverability.

Where amoCRM (Kommo) sits in the Tranco ranking

Tranco rank bandDomainsShare of its base
Top 1,00010.3%
Top 10,00041.3%
Top 100,0004214.0%
Top 1,000,00022876.0%
Unranked258.3%

Top-level domain split

TLDDomainsShare
.ru15250.7%
.com6421.3%
.io144.7%
.net93.0%
.com.br72.3%
.org51.7%
.pro41.3%
.cl41.3%
.su31.0%
.online31.0%

What amoCRM (Kommo) users also use

Cross-tabulated from the same daily snapshot — the other email services seen on the same 300 domains.

TypeServiceDomainsShare of amoCRM (Kommo) users
MailboxYandex 36012642.0%
MailboxGoogle Workspace7123.7%
MailboxSelf-Hosted4113.7%
MailboxMail.ru for Business258.3%
MailboxMicrosoft 365103.3%
MailboxUnknown / Other62.0%

Multi-tenant SPF configuration and reputation sharing

Because amoCRM sends mail on behalf of many customer domains from a shared pool of sending IP addresses, all customers inherit the platform's collective email reputation. If any customer engages in spam or poor sending practices, it can degrade reputation across the entire platform. Organisations using amoCRM must therefore configure SPF records to include amoCRM's designated sending servers, align DKIM signing keys where the platform permits, and monitor DMARC reports to detect unauthorised sending. The centralised sending model means that even diligent senders may experience deliverability friction if other platform customers attract spam complaints or blacklist entries.

See the full amoCRM (Kommo) data page (KPI cards, trend, sample domains) →

Are your emails landing in spam?
Run a free inbox-placement test across Gmail, Outlook, Yahoo and more — see exactly where your mail lands and why.
Test inbox placement →

Frequently asked questions

What is amoCRM and why does it appear in email authentication records?

amoCRM is a SaaS CRM platform that handles email sending for many customer domains simultaneously. Its SPF include records appear because amoCRM's infrastructure sends mail on behalf of those customers, and domain owners must authorise amoCRM's servers to send email in their name.

How many domains use amoCRM (Kommo)?

300 domains in the Tranco top-1M use amoCRM (Kommo) as their SaaS sender as of July 13, 2026 (0.05% of SPF-publishing domains), according to Live Direct Marketing's daily DNS scan.

Is amoCRM (Kommo) common enough to affect email deliverability testing?

amoCRM (Kommo) accounts for 0.05% of SPF-publishing domains in the top 1M. Whether you should seed a test mailbox there depends on how much of your audience it represents — the co-usage table above shows the services it appears alongside most.

Which countries or TLDs use amoCRM (Kommo) most?

amoCRM (Kommo)'s largest TLD is .ru (50.7% of its domains); it appears across 38 TLDs in total.

Other SaaS senders

Shopify (0.87%)Pardot (Salesforce) (0.79%)CodeTwo Email Signatures 365 (0.71%)KnowBe4 (0.56%)Statuspage (Atlassian) (0.34%)Trustpilot (0.30%)Atlassian (Jira/Confluence) (0.30%)Firebase (Google) (0.29%)BigCommerce (0.22%)Lark / Feishu (0.21%)