Download websites that use Yandex.Direct
123 live sites using Yandex.Direct right now
Yandex.Direct site datasets
Two datasets include every website running Yandex.Direct. You will find it in the Technologies column.
1Choose a dataset Each one has its own columns and price
2Look at real rows from TechnologiesLook at real rows from All data Full website tech stack per site: CMS, payments, analytics, frameworks.Everything we have, in a single package. The full webatla universe.
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| infox.ru | ru | ru | ICANN | HTTP 200 | 158.255.1.56 | RU | {"ok":["https://ok.ru/infoxnovos"],"vk":["https://vk.com/infoxnews"],"telegram":["https://t.me/newsinfox"],"x-twitter":["https://twitter.com/newsinfox"]} | 2026-11-07 | PWA, Nginx 1.24.0, HTTP/2, Ubuntu, jQuery 1.11.1, Favicon, hreflang, GlobalSign, Open Graph, Yandex.Direct | 0.000000327677 | 17,228,326 | 2000-04-28 | 2027-04-30 |
| ivd.ru | ru | ru | ICANN | HTTP 200 | 95.213.134.157 | RU | {"ok":["https://ok.ru/group/55304897560804"],"vk":["https://vk.com/ivd_ru"],"youtube":["https://youtube.com/channel/UC36BCX-z36Vbt32jzoLJMmg"],"telegram":["https://t.me/ivd_ru"]} | 2026-11-20 | Nginx, cdnjs, HTTP/2, Favicon, VK Pixel, jsDelivr, Pinterest, Cloudflare, Open Graph, Yandex.Direct | 0.000000165761 | 14,764,378 | 2000-08-09 | 2027-08-09 |
| novate.ru | ru | ru | ICANN | HTTP 200 | 194.67.203.171 | RU | {"ok":["https://ok.ru/novate"],"vk":["https://vk.com/novate"]} | 2026-11-12 | RSS, Nginx 1.30.4, HTTP/2, jQuery 3.7.1, Favicon, FancyBox, Cloudflare, Open Graph, Liveinternet, Yandex.Direct | 0.00000015373 | 14,722,334 | 2007-10-16 | 2027-10-16 |
| lokomotiv.info | info | info | ICANN | HTTP 200 | 194.67.203.180 | RU | {"vk":["https://vk.com/lokomotivinfo"],"facebook":["https://facebook.com/lokomotivinfo"],"instagram":["https://instagram.com/lokomotivinfo"],"x-twitter":["https://twitter.com/lokomotivinfo"]} | 2026-11-08 | RSS, HSTS, Nginx 1.30.4, HTTP/2, jQuery 1.6.2, Open Graph, Liveinternet, Yandex.Direct, Google Hosted Libraries | 0.0000000117209 | 14,563,878 | 2006-04-18 | 2027-04-18 |
| seostop.ru | ru | ru | ICANN | HTTP 200 | 168.113.185.196 | RU | {"vk":["https://vk.com/media_solutions"]} | 2026-10-26 | PHP 7.4.33, Nginx, Drupal 7, HTTP/2, jQuery, Favicon, Liveinternet, Yandex.Direct | 0.00000000744879 | 14,062,581 | 2010-09-01 | 2027-09-01 |
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| infox.ru | ru | ru | ICANN | HTTP 200 | 158.255.1.56 | RU | {"ok":["https://ok.ru/infoxnovos"],"vk":["https://vk.com/infoxnews"],"telegram":["https://t.me/newsinfox"],"x-twitter":["https://twitter.com/newsinfox"]} | 2026-11-07 | PWA, Nginx 1.24.0, HTTP/2, Ubuntu, jQuery 1.11.1, Favicon, hreflang, GlobalSign, Open Graph, Yandex.Direct | 2026-11-13 | TRUE | {"A":["158.255.1.56"],"MX":[{"host":"emx.mail.ru","priority":10}],"NS":["belgorod.ens.mail.ru","novgorod.ens.mail.ru"],"ASN":{"org":"Hostkey B.v.","number":50867},"SOA":{"mname":"belgorod.ens.mail.ru","retry":3600,"rname":"support.biz.mail.ru","expire":604800,"serial":2026111204,"minimum":3600,"refresh":10800},"TXT":["_globalsign-domain-verification=9DXAYvXksgNMlc_EPJhm1lg-XmeWAPdyCmuynaOB5h","google-site-verification=vFNLLej75tGa47hvhb9rML08pj72kTmJJ2LVrGUjqp8","v=spf1 ip4:31.28.23.252 ip:141.105.68.141 a mx include:_spf.mail.ru ~all"],"WWW":{"A":["158.255.1.56"]},"DKIM":"absent","DMARC":["v=DMARC1;p=reject;pct=100;rua=mailto:postmaster@infox.ru"],"SMIME":"absent","DNSSEC":"insecure","OPENPGP":"absent","RESOLVER":"1.1.1.1"} | 0.000000327677 | 17,228,326 | 2026-04-21 | WHOIS | 2000-04-28 | 2027-04-30 | 2026-04-21 | RU-CENTER-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: INFOX.RU\nnserver: belgorod.ens.mail.ru.\nnserver: novgorod.ens.mail.ru.\nstate: REGISTERED, DELEGATED, VERIFIED\norg: LLC \"SMARTMEDIA\"\ntaxpayer-id: 7724303517\nregistrar: RU-CENTER-RU\nadmin-contact: https://www.nic.ru/whois\ncreated: 2000-04-28T11:10:54Z\npaid-till: 2027-04-30T21:00:00Z\nfree-date: 2027-06-01\nsource: TCI\n\nLast updated on 2026-04-21T14:28:02Z"} | Domain is active |
| ivd.ru | ru | ru | ICANN | HTTP 200 | 95.213.134.157 | RU | {"ok":["https://ok.ru/group/55304897560804"],"vk":["https://vk.com/ivd_ru"],"youtube":["https://youtube.com/channel/UC36BCX-z36Vbt32jzoLJMmg"],"telegram":["https://t.me/ivd_ru"]} | 2026-11-20 | Nginx, cdnjs, HTTP/2, Favicon, VK Pixel, jsDelivr, Pinterest, Cloudflare, Open Graph, Yandex.Direct | 2026-11-16 | TRUE | {"A":["95.213.134.157"],"MX":[{"host":"smtp.burda.ru","priority":20}],"NS":["ns2.lvls.ru","ns4-l2.nic.ru","ns4.lvls.ru","ns8-l2.nic.ru"],"ASN":{"org":"JSC Selectel","number":49505},"SOA":{"mname":"ns2.lvls.ru","retry":600,"rname":"lvls.ru","expire":1209600,"serial":2124110112,"minimum":3600,"refresh":7200},"TXT":["google-site-verification=4SiFZhSaYLuD_XQV2JdIDg_Mp3za5P9aDBdJB9m_-qk","v=spf1 ip4:95.213.134.144/28 ip4:92.53.84.67/27 ip4:95.213.179.163/27 ip4:95.213.134.144/28 ip4:95.213.179.163/32 ip4:92.53.84.67/32 mx a a:f1.burda.adm1.ru a:f2.burda.adm1.ru ~all"],"WWW":{"A":["95.213.134.157"],"CNAME":["ivd.ru"]},"DKIM":"present","DMARC":["v=DMARC1; p=reject; rua=mailto:It_common@burda.ru"],"SMIME":"absent","DNSSEC":"insecure","OPENPGP":"absent","RESOLVER":"8.8.8.8"} | 0.000000165761 | 14,764,378 | 2026-08-19 | WHOIS | 2000-08-09 | 2027-08-09 | 2025-08-20 | RU-CENTER-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: IVD.RU\nnserver: ns2.lvls.ru.\nnserver: ns4-l2.nic.ru.\nnserver: ns4.lvls.ru.\nnserver: ns8-l2.nic.ru.\nstate: REGISTERED, DELEGATED, VERIFIED\norg: \ntaxpayer-id: \nregistrar: RU-CENTER-RU\nadmin-contact: https://www.nic.ru/whois\ncreated: 2000-08-09T20:00:00Z\npaid-till: 2027-08-09T21:00:00Z\nfree-date: 2027-09-10\nsource: TCI\n\nLast updated on 2026-08-18T23:33:01Z"} | Domain is active |
| novate.ru | ru | ru | ICANN | HTTP 200 | 194.67.203.171 | RU | {"ok":["https://ok.ru/novate"],"vk":["https://vk.com/novate"]} | 2026-11-12 | RSS, Nginx 1.30.4, HTTP/2, jQuery 3.7.1, Favicon, FancyBox, Cloudflare, Open Graph, Liveinternet, Yandex.Direct | 2026-11-18 | TRUE | {"A":["194.67.203.171"],"MX":[{"host":"emx.mail.ru","priority":10}],"NS":["desi.ns.cloudflare.com","ernest.ns.cloudflare.com"],"ASN":{"org":"Ihor Hosting Ltd","number":209641},"SOA":{"mname":"desi.ns.cloudflare.com","retry":2400,"rname":"dns.cloudflare.com","expire":604800,"serial":2417621640,"minimum":1800,"refresh":10000},"TXT":["v=spf1 redirect=_spf.mail.ru"],"WWW":{"A":["194.67.203.171"],"CNAME":["novate.ru"]},"DKIM":"absent","DMARC":["v=DMARC1;p=none;ruf=mailto:dmarc@novate.ru;fo=1"],"SMIME":"absent","DNSSEC":"insecure","OPENPGP":"absent","RESOLVER":"8.8.8.8"} | 0.00000015373 | 14,722,334 | 2026-10-15 | WHOIS | 2007-10-16 | 2027-10-16 | 2025-09-17 | RU-CENTER-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: NOVATE.RU\nnserver: desi.ns.cloudflare.com.\nnserver: ernest.ns.cloudflare.com.\nstate: REGISTERED, DELEGATED, VERIFIED\nperson: Private Person\nregistrar: RU-CENTER-RU\nadmin-contact: https://www.nic.ru/whois\ncreated: 2007-10-16T20:00:00Z\npaid-till: 2027-10-16T21:00:00Z\nfree-date: 2027-11-17\nsource: TCI\n\nLast updated on 2026-10-14T22:13:01Z"} | Domain is active |
| lokomotiv.info | info | info | ICANN | HTTP 200 | 194.67.203.180 | RU | {"vk":["https://vk.com/lokomotivinfo"],"facebook":["https://facebook.com/lokomotivinfo"],"instagram":["https://instagram.com/lokomotivinfo"],"x-twitter":["https://twitter.com/lokomotivinfo"]} | 2026-11-08 | RSS, HSTS, Nginx 1.30.4, HTTP/2, jQuery 1.6.2, Open Graph, Liveinternet, Yandex.Direct, Google Hosted Libraries | 2026-11-13 | TRUE | {"A":["194.67.203.180"],"MX":[{"host":"emx.mail.ru","priority":10}],"NS":["ns3-l2.nic.ru","ns4-cloud.nic.ru","ns4-l2.nic.ru","ns8-cloud.nic.ru","ns8-l2.nic.ru"],"ASN":{"org":"Ihor Hosting Ltd","number":209641},"SOA":{"mname":"ns3-l2.nic.ru","retry":3600,"rname":"dns.nic.ru","expire":2592000,"serial":2014060910,"minimum":600,"refresh":1440},"TXT":["v=spf1 redirect=_spf.mail.ru"],"WWW":{"A":["194.67.203.180"],"CNAME":["lokomotiv.info"]},"DKIM":"present","SMIME":"absent","DNSSEC":"insecure","OPENPGP":"absent","RESOLVER":"8.8.8.8"} | 0.0000000117209 | 14,563,878 | 2026-04-09 | RDAP | 2006-04-18 | 2027-04-18 | 2026-03-02 | Regional Network Information Center, JSC dba RU-CENTER | {"raw_response":{"links":[{"rel":"related","href":"https://rdap.nic.ru/domain/lokomotiv.info","type":"application/rdap+json","value":"https://rdap.identitydigital.services/rdap/domain/lokomotiv.info"},{"rel":"self","href":"https://rdap.identitydigital.services/rdap/domain/lokomotiv.info","type":"application/rdap+json","value":"https://rdap.identitydigital.services/rdap/domain/lokomotiv.info"}],"events":[{"eventDate":"2009-02-24T02:02:22.389Z","eventAction":"transfer"},{"eventDate":"2027-04-18T21:44:43.389Z","eventAction":"expiration"},{"eventDate":"2006-04-18T21:44:43.389Z","eventAction":"registration"},{"eventDate":"2026-03-02T11:47:22.924Z","eventAction":"last changed"},{"eventDate":"2026-04-09T17:40:26.729Z","eventAction":"last update of RDAP database"}],"status":["client transfer prohibited"],"ldhName":"lokomotiv.info","notices":[{"links":[{"rel":"terms-of-service","href":"https://www.identity.digital/policies/rdds-access-policy","type":"text/html","value":"https://rdap.identitydigital.services/rdap/domain/lokomotiv.info"}],"title":"Terms of Service","description":["Access to RDAP information is provided to assist persons in determining the contents of a domain name registration record in the registry database. The data in this record is provided by Identity Digital or, if the record pertains to a TLD not operated by Identity Digital, then the corresponding primary Registry Operator for informational purposes only, and neither Identity Digital nor the Registry Operator guarantee its accuracy. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Identity Digital, a Registrar, or Registry Operator except as reasonably necessary to register domain names or modify existing registrations. When using the RDAP service, please consider the following: the RDAP service is not a replacement for standard EPP commands to the SRS service. RDAP is not considered authoritative for registered domain objects. The RDAP service may be scheduled for downtime during production or OT&E maintenance periods. Queries to the RDAP services are throttled. If too many queries are received from a single IP address within a specified time, the service will begin to reject further queries for a period of time to prevent disruption of RDAP service access. Abuse of the RDAP system through data mining is mitigated by detecting and limiting bulk query access from single sources. Where applicable, the presence of a [Non-Public Data] tag indicates that such data is not made publicly available due to applicable data privacy laws or requirements. Should you wish to contact the registrant, please refer to the RDAP records available through the registrar URL listed above. Access to non-public data may be provided, upon request, where it can be reasonably confirmed that the requester holds a specific legitimate interest and a proper legal basis for accessing the withheld data. Access to the data provided by Identity Digital can be requested by submitting a request via the form found at https://www.identity.digital/about/policies/whois-layered-access/ Identity Digital Inc. and, if applicable, the primary Registry Operators reserve the right to modify these terms at any time. By submitting this query, you agree to abide by this policy."]},{"links":[{"rel":"glossary","href":"https://icann.org/epp","type":"application/rdap+json","value":"https://rdap.identitydigital.services/rdap/domain/lokomotiv.info"}],"title":"Status Codes","description":["For more information on domain status codes, please visit https://icann.org/epp"]},{"links":[{"rel":"help","href":"https://icann.org/wicf","type":"application/rdap+json","value":"https://rdap.identitydigital.services/rdap/domain/lokomotiv.info"}],"title":"RDDS Inaccuracy Complaint Form","description":["URL of the ICANN RDDS Inaccuracy Complaint Form: https://icann.org/wicf"]}],"entities":[{"links":[{"rel":"self","href":"https://rdap.identitydigital.services/rdap/entity/463","type":"application/rdap+json","value":"https://rdap.identitydigital.services/rdap/entity/463"},{"rel":"about","href":"https://rdap.nic.ru/","type":"application/rdap+json","value":"https://rdap.nic.ru/"}],"roles":["registrar"],"handle":"463","entities":[{"roles":["abuse"],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text",""],["tel",{"type":"voice"},"uri","tel:+7.4950091333"],["email",{},"text","tld-abuse@nic.ru"]]],"objectClassName":"entity"}],"publicIds":[{"type":"IANA Registrar ID","identifier":"463"}],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text","Regional Network Information Center, JSC dba RU-CENTER"]]],"objectClassName":"entity"}],"redacted":[{"name":{"type":"Registry Domain ID"},"method":"removal","prePath":"$.handle","pathLang":"jsonpath"}],"secureDNS":{"maxSigLife":1,"delegationSigned":false},"nameservers":[{"handle":"e88781257aeb4e2485af8430a52fa154-DONUTS","status":["associated"],"ldhName":"ns8-l2.nic.ru","unicodeName":"ns8-l2.nic.ru","objectClassName":"nameserver"},{"handle":"30a2b291d43d47d68b6de2ba1bd14b1c-DONUTS","status":["associated"],"ldhName":"ns8-cloud.nic.ru","unicodeName":"ns8-cloud.nic.ru","objectClassName":"nameserver"},{"handle":"ce16f69bb5b645d692d675c9f3c6695c-DONUTS","status":["associated"],"ldhName":"ns4-l2.nic.ru","unicodeName":"ns4-l2.nic.ru","objectClassName":"nameserver"},{"handle":"b26c1a8404fa41f78eb50a54df3483f4-DONUTS","status":["associated"],"ldhName":"ns4-cloud.nic.ru","unicodeName":"ns4-cloud.nic.ru","objectClassName":"nameserver"},{"handle":"d254ab9fe7b147d5a9b1462c6a30b859-DONUTS","status":["associated"],"ldhName":"ns3-l2.nic.ru","unicodeName":"ns3-l2.nic.ru","objectClassName":"nameserver"}],"unicodeName":"lokomotiv.info","objectClassName":"domain","rdapConformance":["rdap_level_0","icann_rdap_response_profile_1","icann_rdap_technical_implementation_guide_1","redacted"]}} | Domain is active |
| seostop.ru | ru | ru | ICANN | HTTP 200 | 168.113.185.196 | RU | {"vk":["https://vk.com/media_solutions"]} | 2026-10-26 | PHP 7.4.33, Nginx, Drupal 7, HTTP/2, jQuery, Favicon, Liveinternet, Yandex.Direct | 2026-11-13 | TRUE | {"A":["168.113.185.196"],"MX":[{"host":"mx.raspisanija.ru","priority":10}],"NS":["ns1.reg.ru","ns2.reg.ru"],"ASN":{"org":"JSC IOT","number":29182},"SOA":{"mname":"ns1.reg.ru","retry":3600,"rname":"hostmaster.ns1.reg.ru","expire":604800,"serial":1794469241,"minimum":10800,"refresh":14400},"TXT":["v=spf1 ip4:168.113.185.196 ~all"],"WWW":{"A":["168.113.185.196"]},"DKIM":"absent","SMIME":"absent","DNSSEC":"insecure","OPENPGP":"absent","RESOLVER":"8.8.8.8"} | 0.00000000744879 | 14,062,581 | 2026-08-31 | WHOIS | 2010-09-01 | 2027-09-01 | 2025-08-24 | 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: SEOSTOP.RU\nnserver: ns1.beget.ru.\nnserver: ns2.beget.ru.\nstate: REGISTERED, DELEGATED, VERIFIED\nperson: Private Person\nregistrar: REGRU-RU\nadmin-contact: http://www.reg.ru/whois/admin_contact\ncreated: 2010-09-01T20:44:56Z\npaid-till: 2027-09-01T21:44:56Z\nfree-date: 2027-10-03\nsource: TCI\n\nLast updated on 2026-08-30T22:33:01Z"} | Domain is active |
3Download the free preview or buy the whole fileDownload the free preview or buy the whole file
118 more rows in the full file118 more rows in the full file
Your free preview is downloading
webatla-technologies-technology-yandex-direct-preview.jsonl · 20 rowswebatla-all-data-technology-yandex-direct-preview.jsonl · 20 rows
One domain per line, as a JSON record. Any text editor opens it. Download it manually
We sent a confirmation link to . Your account already works.
What's next for you?
What are you looking for?
Pick any that fit. Your answer goes straight to the people who build the files.
Thanks, that helps
The team reads every answer. We'll write to .
The lightest file on this page, Technologies, is €159 / month. Go to checkout
API access comes with every dataset. Read the API docs
Get the Yandex.Direct list
Technologies
The Yandex.Direct file with 123 websites, plus the whole dataset. 315,015,451 websites and ready files by technology, country and TLD.
All data
Everything in Technologies, plus DNS records and registrar. 426,720,010 domains in one file.
Compare every dataset on the pricing page.
About Yandex.Direct
Advertising · Yandex · Proprietary · first release 2001
An advertising tag says less about how a site was built than about how its owner earns from the page. Yandex has operated Yandex.Direct since 2001 as a Proprietary platform for search and network advertising, and the address we hold for the entry is the network's own portal for site owners who want to carry its ads, which is the side of that machinery a crawler can see.
As of November 2026 we detect Yandex.Direct on 123 sites. The pages behind the figure carry advertising code rather than a measurement counter, and the two are easy to confuse when you first look at advertising data. The company's separate analytics counter, Yandex.Metrika, is what a site owner places to measure their own traffic, and we track it under its own entry.
Carrying ad code is a durable business fact and a poor instantaneous one. Tags outlive campaigns and slots outlive the pages that once filled them, and a snippet left in a template after a site stopped selling space looks exactly like a snippet on a live account. We make no attempt to tell an earning placement from a dormant one, because nothing in the markup separates them, and any list built from tag presence should be read as evidence of a decision taken at some point rather than of revenue right now.
The kind of site that carries it is worth picturing before you download anything. Pages running network advertising tend to be content, media and community properties with enough traffic to be worth monetising, so the population leans toward publishers and away from brochure pages put up for a single business. Sites in the list also tend to carry a stack of neighbouring tags, analytics counters, session recorders, chat widgets and consent managers, which makes the domains useful as a joining key into the rest of our data rather than only as a standalone segment.
For a sales team, that qualification does much of the work in advance. A domain with the tag has an advertising setup that somebody signed up for and somebody still maintains, which puts it well ahead of a cold domain in any outreach list aimed at publishers. For a market researcher the interesting axis is linguistic and commercial rather than technical, because the platform serves Russian-speaking markets and its footprint follows business ties to those markets more closely than it follows hosting geography.
We hold no country or top-level-domain breakdown for Yandex.Direct in this profile, so the geographic reading has to be built from the domain list itself. Building it that way is more work and more honest than printing a share we cannot stand behind. A lookup on one domain tells you whether that site runs the tag. The downloadable list tells you which sites do, which is the version of the question that supports competitive research, agency prospecting or a study of how ad-tech adoption tracks language rather than borders.
Frequently asked questions
How to download the list of websites using Yandex.Direct
The complete list of websites using Yandex.Direct is available as one structured file. Every row is a site we detected running Yandex.Direct, exported with its full record, so you can filter it offline instead of crawling the web yourself.
- Choose a dataset in the preview above or the price cards below
- Check out by card or in crypto, priced in EUR
- Download the list one JSONL file (zstd) in your account, which you can re-download any time during your access month
What each file holds, for every site:
- Technologies: the domain, the full stack we detect with versions, IP, hosting country, HTTP status, social profiles, PageRank / Harmonic rank and domain dates.
- All data: every column in one file: the domain, technologies, IP, hosting country, rank and dates, plus DNS records and RDAP / WHOIS.
- A fresh export every day.
How many websites use Yandex.Direct?
webatla detects Yandex.Direct on 123 websites, refreshed daily. Each row has the domain with its IP, hosting country, ranking and the rest of its stack, and All data adds DNS and WHOIS.
Can I download the list of websites using Yandex.Direct?
Yes, the list downloads as structured JSONL (zstd), one domain per line.
What's included for each site, and how fresh is it?
The Technologies file has the domain, the full stack with versions, IP, hosting country, HTTP status, PageRank and Harmonic. All data adds DNS and RDAP/WHOIS. Everything is re-detected and re-exported daily.
How do I find the websites using Yandex.Direct?
Buy the technology dataset, then download the complete list of domains we detect using Yandex.Direct, re-exported every day.
What else is in the Yandex.Direct technology data?
Each row places Yandex.Direct next to the other technology on the same site, plus its IP, hosting country and ranking. All data adds DNS and WHOIS.
Can I download just the sites using Yandex.Direct, or the whole database?
Both. Every site running Yandex.Direct 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.