Yandex.Direct logo

Scaricare i siti web che utilizzano Yandex.Direct

133 siti attivi che utilizzano Yandex.Direct in questo momento

Advertising · di Yandex · dal 2001 · Proprietary

133 siti Dataset aggiornato · 2026-08-30
Categorie Pubblicità
🔒 Ottenere l’elenco
Richiede l’acquisto di un dataset

Informazioni su Yandex.Direct

webatla monitora 133 siti web attivi che utilizzano Yandex.Direct, ovvero il 0,0% di tutti i siti che indicizziamo. Scarichi l’elenco completo dei siti web che utilizzano Yandex.Direct come esportazione JSONL giornaliera. Ogni record include il dominio, oltre a DNS, WHOIS, indirizzo IP, paese di hosting e ranking globale.

Yandex.Direct è la principale piattaforma pubblicitaria pay-per-click gestita da Yandex, che permette agli inserzionisti di mostrare annunci su Yandex Search, sulla Yandex Advertising Network e su siti partner. Supporta annunci testuali, banner display, smart banner e formati pubblicitari video con un targeting del pubblico sofisticato.

Yandex.Direct è la piattaforma pubblicitaria digitale dominante in Russia e detiene una quota di mercato significativa nei paesi della CSI, rendendola essenziale per le aziende che si rivolgono a un pubblico di lingua russa. La piattaforma offre pubblicità di ricerca basata su parole chiave paragonabile a Google Ads, oltre a retargeting, audience lookalike e strategie di offerta automatizzate. La presenza di tag Yandex.Direct su un sito web indica campagne pubblicitarie attive sull’ecosistema Yandex.

A colpo d’occhio

VendorYandex
LicenseProprietary
First release2001-01-01
Tutti i dati aggiornati in data 30 ago 2026
133 Siti rilevati
0,0% Di tutti i siti web

Anteprima del database dei siti Yandex.Direct

Il rilevamento di Yandex.Direct è un valore della colonna Technologies . Due dataset la contengono, passi dall’uno all’altro per confrontare cosa è incluso.

webatla-technologies-yandex-direct-2026-08-30.jsonl.zst · 133 righe · 14 colonne Esportazione giornaliera aggiornata
DomainTLD suffixTLDDomain typeHTTP statusIP addressCountry by IPSocial networksTechnologies last data checkedTechnologiesPR valueHarmonic valueDomain creation dateDomain expiration date
infox.rururuICANNHTTP 200141.105.67.141RU{"ok":["https://ok.ru/infoxnovos"],"vk":["https://vk.com/infoxnews"],"telegram":["https://t.me/newsinfox"],"x-twitter":["https://twitter.com/newsinfox"]}2026-08-06PWA, HSTS, Nginx, jQuery 1.11.1, Favicon, hreflang, GlobalSign, Open Graph, Yandex.Direct, Google Site Verification0.00000031261316,650,3992000-04-282027-04-30
krisha.kzkzkzICANNHTTP 200185.143.129.89KZ{"vk":["https://vk.com/krishakz"],"youtube":["https://youtube.com/channel/UCwRTPCE3dGzd6w3BKSQRPxQ"],"facebook":["https://facebook.com/krisha.kz"],"instagram":["https://instagram.com/krisha.kz"]}2026-08-08PWA, HSTS, Nginx, HTTP/3, Favicon, hreflang, Google Ads, TikTok Pixel, Yandex.Direct, Facebook Pixel0.00000021063514,195,8342004-07-23
ivd.rururuICANNHTTP 20095.213.134.157RU{"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-08-06Nginx, cdnjs, HTTP/2, Favicon, VK Pixel, jsDelivr, Pinterest, Cloudflare, Open Graph, Yandex.Direct0.00000020677514,214,5172000-08-092027-08-09
novate.rururuICANNHTTP 200194.67.203.171RU{"ok":["https://ok.ru/novate"],"vk":["https://vk.com/novate"]}2026-08-13RSS, Nginx 1.30.4, HTTP/2, jQuery 3.7.1, Favicon, FancyBox, Cloudflare, Open Graph, Liveinternet, Yandex.Direct0.00000016386914,197,7312007-10-162026-10-16
lokomotiv.infoinfoinfoICANNHTTP 200194.67.203.180RU{"vk":["https://vk.com/lokomotivinfo"],"facebook":["https://facebook.com/lokomotivinfo"],"instagram":["https://instagram.com/lokomotivinfo"],"x-twitter":["https://twitter.com/lokomotivinfo"]}2026-08-09RSS, HSTS, Nginx 1.30.4, HTTP/2, jQuery 1.6.2, Open Graph, Liveinternet, Yandex.Direct, Google Hosted Libraries0.000000016945513,886,1032006-04-182027-04-18
DomainTLD suffixTLDDomain typeHTTP statusIP addressCountry by IPSocial networksTechnologies last data checkedTechnologiesDNS last data checkedDNS StatusDNS recordsPR valueHarmonic valueRDAP/WHOIS last data checkedRDAP/WHOIS methodDomain creation dateDomain expiration dateDomain last changedRegistrarRDAP/WHOIS RecordResponse Status RDAP/WHOIS
infox.rururuICANNHTTP 200141.105.67.141RU{"ok":["https://ok.ru/infoxnovos"],"vk":["https://vk.com/infoxnews"],"telegram":["https://t.me/newsinfox"],"x-twitter":["https://twitter.com/newsinfox"]}2026-08-06PWA, HSTS, Nginx, jQuery 1.11.1, Favicon, hreflang, GlobalSign, Open Graph, Yandex.Direct, Google Site Verification2026-08-17TRUE{"A":["141.105.67.141"],"MX":[{"host":"emx.mail.ru","priority":10}],"NS":["belgorod.ens.mail.ru","novgorod.ens.mail.ru"],"SOA":{"mname":"belgorod.ens.mail.ru","retry":3600,"rname":"support.biz.mail.ru","expire":604800,"serial":2026081702,"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"]}0.00000031261316,650,3992026-04-21WHOIS2000-04-282027-04-302026-04-21RU-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
krisha.kzkzkzICANNHTTP 200185.143.129.89KZ{"vk":["https://vk.com/krishakz"],"youtube":["https://youtube.com/channel/UCwRTPCE3dGzd6w3BKSQRPxQ"],"facebook":["https://facebook.com/krisha.kz"],"instagram":["https://instagram.com/krisha.kz"]}2026-08-08PWA, HSTS, Nginx, HTTP/3, Favicon, hreflang, Google Ads, TikTok Pixel, Yandex.Direct, Facebook Pixel2026-08-28TRUE{"A":["185.143.129.89","185.143.129.90"],"MX":[{"host":"alt1.aspmx.l.google.com","priority":5},{"host":"alt2.aspmx.l.google.com","priority":5},{"host":"aspmx.l.google.com","priority":1},{"host":"aspmx2.googlemail.com","priority":10},{"host":"aspmx3.googlemail.com","priority":10}],"NS":["ns1.kolesa.kz","ns2.kolesa.kz","ns3.kolesa.kz"],"SOA":{"mname":"ns1.kolesa.kz","retry":60,"rname":"dns.kolesa.kz","expire":2419200,"serial":2023022921,"minimum":60,"refresh":1800},"TXT":["v=spf1 include:_spf.kolesa.kz -all"],"DNSKEY":[{"flags":257,"protocol":3,"algorithm":13,"public_key":"7i7b1haAMwnBqbF/3vAiTyDO2Bf/nO5Q4j1ahF85xPjFVZo2WPHkeCLH35m4q9eIghdib4ctFElggsBtt1UKUg=="}]}0.00000021063514,195,8342026-08-28WHOIS2004-07-232024-04-09ICPS{"raw_response":"Whois Server for the KZ top level domain name.\nThis server is maintained by KazNIC Organization, a ccTLD manager for Kazakhstan Republic.\n\nDomain Name............: krisha.kz\n\nOrganization Using Domain Name\nName...................: [HIDDEN PERSONAL DATA]\nOrganization Name......: [HIDDEN PERSONAL DATA]\nStreet Address.........: [HIDDEN PERSONAL DATA]\nCity...................: [HIDDEN PERSONAL DATA]\nState..................: [HIDDEN PERSONAL DATA]\nPostal Code............: [HIDDEN PERSONAL DATA]\nCountry................: [HIDDEN PERSONAL DATA]\n\nAdministrative Contact/Agent\nNIC Handle.............: PS-KZ-1712666348\nName...................: [HIDDEN PERSONAL DATA]\nPhone Number...........: [HIDDEN PERSONAL DATA]\nFax Number.............: [HIDDEN PERSONAL DATA]\nEmail Address..........: [HIDDEN PERSONAL DATA]\n\nNameserver in listed order\n\nPrimary server.........: ns1.kolesa.kz\nPrimary ip address.....: 185.146.2.2, 185.146.2.3\n\nSecondary server.......: ns2.kolesa.kz\nSecondary ip address...: 89.218.30.251, 89.218.30.252\n\nSecondary server.......: ns3.kolesa.kz\nSecondary ip address...: 185.146.2.2, 89.218.30.251\n\n\nDomain created: 2004-07-23 03:18:42 (GMT+0:00)\nLast modified : 2024-04-09 12:39:08 (GMT+0:00)\nDomain status : clientTransferProhibited - \n clientRenewProhibited - \n \nRegistar created: KAZNIC\nCurrent Registar: ICPS"}Domain is active
ivd.rururuICANNHTTP 20095.213.134.157RU{"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-08-06Nginx, cdnjs, HTTP/2, Favicon, VK Pixel, jsDelivr, Pinterest, Cloudflare, Open Graph, Yandex.Direct2026-08-21TRUE{"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"],"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"]}0.00000020677514,214,5172026-08-19WHOIS2000-08-092027-08-092025-08-20RU-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.rururuICANNHTTP 200194.67.203.171RU{"ok":["https://ok.ru/novate"],"vk":["https://vk.com/novate"]}2026-08-13RSS, Nginx 1.30.4, HTTP/2, jQuery 3.7.1, Favicon, FancyBox, Cloudflare, Open Graph, Liveinternet, Yandex.Direct2026-08-25TRUE{"A":["194.67.203.171"],"MX":[{"host":"emx.mail.ru","priority":10}],"NS":["desi.ns.cloudflare.com","ernest.ns.cloudflare.com"],"SOA":{"mname":"desi.ns.cloudflare.com","retry":2400,"rname":"dns.cloudflare.com","expire":604800,"serial":2412521680,"minimum":1800,"refresh":10000},"TXT":["v=spf1 redirect=_spf.mail.ru"]}0.00000016386914,197,7312025-09-17WHOIS2007-10-162026-10-162025-09-17R01-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: R01-RU\nadmin-contact: https://partner.r01.ru/contact_admin.khtml\ncreated: 2007-10-16T20:00:00Z\npaid-till: 2026-10-16T21:00:00Z\nfree-date: 2026-11-17\nsource: TCI\n\nLast updated on 2025-09-17T00:33:01Z\n\n"}Domain is active
lokomotiv.infoinfoinfoICANNHTTP 200194.67.203.180RU{"vk":["https://vk.com/lokomotivinfo"],"facebook":["https://facebook.com/lokomotivinfo"],"instagram":["https://instagram.com/lokomotivinfo"],"x-twitter":["https://twitter.com/lokomotivinfo"]}2026-08-09RSS, HSTS, Nginx 1.30.4, HTTP/2, jQuery 1.6.2, Open Graph, Liveinternet, Yandex.Direct, Google Hosted Libraries2026-08-17TRUE{"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"],"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"]}0.000000016945513,886,1032026-04-09RDAP2006-04-182027-04-182026-03-02Regional 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
Visualizzazione 5 di 133 righe · Technologies · Lo stack tecnologico completo di ogni sito: CMS, pagamenti, analytics, framework.

Il dataset Yandex.Direct

Tutti i siti in cui abbiamo rilevato l’uso di Yandex.Direct, con versione, hosting, paese, TLD e ranking di traffico.

Yandex.Direct è presente in 2 dataset

Il rilevamento di Yandex.Direct fa parte di Technologies (€159/mese) e All data (€599/mese). Acquisti uno dei due per filtrare l’elenco completo di 133 siti, oppure scarichi prima un’anteprima gratuita.

I suoi download di Yandex.Direct

I dataset che possiede, filtrati su Yandex.Direct. Ogni pulsante trasmette direttamente l’ultima esportazione giornaliera.

Formato: JSONL (zstd) Dataset aggiornato: 2026-08-30

API, colonne & ricette → /account/api

Quali siti web utilizzano Yandex.Direct?

webatla rileva tutti i siti che utilizzano Yandex.Direct e li esporta in un’unica lista scaricabile, così può vedere chi dipende da questa tecnologia e cos’altro viene eseguito insieme ad essa.

Apra il dataset della tecnologia Yandex.Direct per suddividere l’adozione per paese ed estensione di dominio, confrontarla con una tecnologia concorrente e monitorare i nuovi domini nel tempo.

Domande frequenti

Quanti siti web utilizzano Yandex.Direct?

webatla rileva Yandex.Direct su 133 siti web, aggiornati ogni giorno, ciascuno con il proprio dominio, DNS, WHOIS, IP, paese e ranking.

Posso scaricare l’elenco dei siti web che utilizzano Yandex.Direct?

Sì, in formato JSONL strutturato. Scarichi prima un campione gratuito.

Che cosa è incluso per ogni sito, e con quale frequenza viene aggiornato?

Dominio, DNS, RDAP/WHOIS, lo stack tecnologico completo, IP e paese, PageRank e Harmonic, ridilevati e riesportati ogni giorno.

Come trovo i siti web che utilizzano Yandex.Direct?

Acquisti il dataset Technologies, poi scarichi l’elenco completo dei domini in cui rileviamo Yandex.Direct, riesportato ogni giorno.

Che altro contengono i dati sulla tecnologia Yandex.Direct?

Ogni riga colloca Yandex.Direct accanto alle altre tecnologie dello stesso sito, oltre a DNS, WHOIS, IP, paese e ranking.

Posso scaricare solo i siti che utilizzano Yandex.Direct, o l’intero database?

Entrambi. Ogni sito che utilizza Yandex.Direct è incluso nel dataset Technologies, un unico file scaricabile. Oppure acquisti All data per l’intero database: tecnologie, più identità, ranking, DNS e RDAP/WHOIS per ogni dominio, riuniti in un unico file. Esportazione aggiornata ogni giorno.

Come scarico l’elenco dei siti web che utilizzano Yandex.Direct?

Tre passaggi: (1) scarichi il campione gratuito di 10.000 righe per esaminare lo schema, (2) acquisti il dataset Technologies, (3) scarichi l’elenco completo di tutti i domini in cui rileviamo Yandex.Direct, in un file JSON Lines. Viene riesportato ogni giorno, quindi può riscaricare l’elenco più aggiornato in qualsiasi momento durante il suo periodo di accesso. Ogni riga contiene il dominio, oltre a DNS, WHOIS, IP, paese di hosting e ranking.

Ottenga l’elenco completo dei siti web che usano Yandex.Direct

Scelga il dataset che copre ciò di cui ha bisogno. Ciascuno include Yandex.Direct ed è scaricabile in JSONL, ricostruito ogni giorno.

Vuole confrontare tutti i dataset fianco a fianco? Visitare la pagina dei prezzi