Download websites that use Yandex.Messenger
1 live site using Yandex.Messenger right now
Technology
Preview Yandex.Messenger site datasets
Yandex.Messenger detection is a value inside the Technologies column. Two datasets carry it, switch between them to compare what's included.
| Domain | TLD suffix | TLD | Domain type | HTTP status | IP address | Country by IP | Social networks | Technologies last data checked | Technologies | PR value | Harmonic value | Domain creation date | Domain expiration date |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| zarulem63.ru | ru | ru | ICANN | HTTP 200 | 185.11.247.78 | RU | — | 2026-09-24 | PHP 5.2.17, Nginx 1.4.2, Yandex.Messenger | 0.00000000451321 | 10,503,876 | 2009-06-18 | 2027-06-18 |
| … | … | … | … | … | … | … | … | … | … | … | … | … | … |
| Domain | TLD suffix | TLD | Domain type | HTTP status | IP address | Country by IP | Social networks | Technologies last data checked | Technologies | DNS last data checked | DNS Status | DNS records | PR value | Harmonic value | RDAP/WHOIS last data checked | RDAP/WHOIS method | Domain creation date | Domain expiration date | Domain last changed | Registrar | RDAP/WHOIS Record | Response Status RDAP/WHOIS |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| zarulem63.ru | ru | ru | ICANN | HTTP 200 | 185.11.247.78 | RU | — | 2026-09-24 | PHP 5.2.17, Nginx 1.4.2, Yandex.Messenger | 2026-10-01 | TRUE | {"A":["185.11.247.78"],"MX":[{"host":"mail.zarulem63.ru","priority":20},{"host":"mail.zarulem63.ru","priority":10}],"NS":["ns1.n-n.ru","ns2.n-n.ru"],"SOA":{"mname":"ns1.n-n.ru","retry":3600,"rname":"root.n-n.ru","expire":604800,"serial":2009070108,"minimum":86400,"refresh":10800},"TXT":["v=spf1 ip4:185.12.94.15 a mx ~all"]} | 0.00000000451321 | 10,503,876 | 2026-06-17 | WHOIS | 2009-06-18 | 2027-06-18 | 2026-06-17 | REGRU-RU | {"raw_response":"% TCI Whois Service. Terms of use:\n% https://tcinet.ru/documents/whois_ru_rf.pdf (in Russian)\n% https://tcinet.ru/documents/whois_su.pdf (in Russian)\n\ndomain: ZARULEM63.RU\nnserver: ns1.n-n.ru.\nnserver: ns2.n-n.ru.\nstate: REGISTERED, DELEGATED, VERIFIED\norg: ANO DPO \"PCOT\"\ntaxpayer-id: 6319138340\nregistrar: REGRU-RU\nadmin-contact: http://www.reg.ru/whois/admin_contact\ncreated: 2009-06-18T20:00:00Z\npaid-till: 2027-06-18T21:00:00Z\nfree-date: 2027-07-20\nsource: TCI\n\nLast updated on 2026-06-17T03:48:01Z"} | Domain is active |
| … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … |
The Yandex.Messenger dataset
Every site we've detected as running Yandex.Messenger, with version, hosting, country, TLD and traffic rank.
Yandex.Messenger lives inside 2 datasets
Yandex.Messenger detection is part of Technologies (€159/mo) and All data (€599/mo). Buy either to filter the full 1-site list, or grab a free preview first.
About Yandex.Messenger
The name carries more information than the record does, which makes it worth separating what we can see from what we are assuming. Yandex.Messenger is stored here with a site count and very little else: no vendor, no licence, no first release year, no category, no website. The name itself points at the messaging product in the Yandex family, and the match is a match on a page reference, so that attribution belongs to the signature rather than to any documentation we hold.
A messenger reference on a website is a customer contact decision before it is a technical one. Somebody decided that visitors should reach the business through a chat product they already carry on their phone, instead of through a form, an email address or a hosted support widget. Contact routing of that kind says something about where an audience already is, because a business rarely offers a channel its customers do not use.
Detection of chat and messaging integrations undercounts more than most categories, and the reason is mundane. Widgets are frequently loaded on a single page, usually contact or checkout, and a crawl that reads the front page of a domain never sees them. Consent gating removes another slice, and a deferred script that only initialises on interaction removes more. Any figure we publish for a messaging integration should be read as a floor.
As of October 2026 the recorded footprint for Yandex.Messenger stands at 1. A count at that level supports a narrow claim, which is that the pattern occurs on live sites, and not a broad one about how common the integration has become.
For anyone mapping which support channels a market has settled on, the value of the download is that every match arrives with its neighbours attached. Each domain comes with its country, its top level domain and the rest of its detected stack, so a contact channel can be compared against the audience it was chosen for rather than counted in isolation. A per-domain lookup cannot support that comparison, because comparison needs the whole set at once.
Frequently asked questions
How many websites use Yandex.Messenger?
webatla detects Yandex.Messenger on 1 website, refreshed daily, with its domain, DNS, WHOIS, IP, country and ranking.
Can I download the list of websites using Yandex.Messenger?
Yes, as structured JSONL. Grab a free sample first.
What's included for each site, and how fresh is it?
Domain, DNS, RDAP/WHOIS, the full technology stack, IP & country, PageRank and Harmonic, re-detected and re-exported daily.
How do I find the websites using Yandex.Messenger?
Buy the technology dataset, then download the complete list of domains we detect using Yandex.Messenger, re-exported every day.
What else is in the Yandex.Messenger technology data?
Each row places Yandex.Messenger next to the other technology on the same site, plus DNS, WHOIS, IP, country and ranking.
Can I download just the sites using Yandex.Messenger, or the whole database?
Both. Every site running Yandex.Messenger comes in the Technologies dataset, one downloadable file. Or buy All data for the entire database: technologies plus identity, ranking, DNS and RDAP/WHOIS for every domain, combined in one file. Daily fresh export.
How do I download the list of websites using Yandex.Messenger?
Three steps: (1) grab the free 10,000-row sample to inspect the schema, (2) buy the Technologies dataset, (3) download the full list of every domain we detect running Yandex.Messenger as a JSON Lines file. It is re-exported daily, so you can re-download the freshest list any time inside your access window. Each row carries the domain plus DNS, WHOIS, IP, hosting country and rank.
Get the full list of websites using Yandex.Messenger
Pick the dataset that covers what you need. Each one includes Yandex.Messenger and downloads as JSONL, rebuilt daily.
Full website tech stack per site: CMS, payments, analytics, frameworks.
Everything we have, in a single package. The full webatla universe.
Want to compare every dataset side by side? Visit the pricing page
Related technologies
