Descargar sitios web que utilizan Letro
29 sitios activos que usan Letro ahora mismo
Social · Open Source
Acerca de Letro
webatla rastrea 29 sitios web activos que utilizan Letro, 0.0% de todos los sitios que indexamos. Descargue la lista completa de sitios web que usan Letro como una exportación JSONL diaria. Cada registro incluye el dominio, además de DNS, WHOIS, dirección IP, país de hosting y ranking global.
Letro es un protocolo de comunicación y una aplicación descentralizados y de código abierto, diseñados para ofrecer mensajería segura y privada mediante cifrado de extremo a extremo. Construido sobre el principio de la soberanía del usuario, pretende ofrecer una alternativa a las plataformas de mensajería centralizadas al permitir que los usuarios se comuniquen sin depender de una única infraestructura corporativa.
Letro se basa en el protocolo de red Awala, desarrollado para enrutar datos a través de múltiples operadores y resistir la censura y la vigilancia. El proyecto se dirige a usuarios y organizaciones preocupados por la privacidad en entornos donde las comunicaciones pueden ser monitorizadas o restringidas. Como iniciativa de código abierto, Letro lo mantiene una pequeña comunidad de desarrolladores y sigue en desarrollo activo.
Vista previa de la base de datos de sitios Letro
La detección de Letro es un valor de la columna Technologies . Dos datasets la incluyen, cambie entre ambos para comparar qué incluye cada uno.
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| mini-mal.tokyo | tokyo | tokyo | ICANN | HTTP 200 | 23.227.38.32 | CA | {"facebook":["https://facebook.com/minimalchocolate"],"instagram":["https://instagram.com/minimal_beantobarchocolate"],"x-twitter":["https://twitter.com/Minimal_tokyo"]} | 2026-08-12 | HSTS, Letro, A8.net, HTTP/3, jQuery 3.5.1, Favicon, Klaviyo, Shopify, Apple Pay, Amazon SES | 0.000000100561 | 14,188,359 | 2014-08-23 | 2028-08-23 |
| bglen.net | net | net | ICANN | HTTP 200 | 54.192.35.29 | US | {"threads":["https://threads.net/@bglen_official"],"youtube":["https://youtube.com/@bglen_official"],"instagram":["https://instagram.com/bglen_official"],"x-twitter":["https://twitter.com/bglen_official"]} | 2026-07-24 | PHP 7.1.33, Letro, Vimeo, HTTP/3, jQuery 1.11.3, EC-CUBE, Favicon, hreflang, jsDelivr, Bootstrap | 0.0000000681514 | 13,420,808 | 2004-08-27 | 2026-08-27 |
| atoa-kobe.jp | jp | jp | ICANN | HTTP 200 | 160.16.214.172 | JP | {"youtube":["https://youtube.com/channel/UC-slxcqbaMS4hnybQye7nag"],"facebook":["https://facebook.com/atoa.kobe"],"instagram":["https://instagram.com/atoa_kobe"],"x-twitter":["https://twitter.com/atoa_kobe"]} | 2026-07-23 | PHP 7.2.24, Letro, Slick, jQuery 3.6.0, Favicon, Google Ads, Open Graph, TikTok Pixel, scrollreveal, Facebook Pixel | 0.0000000679826 | 13,700,399 | 2020-09-10 | 2026-09-30 |
| nifrel.jp | jp | jp | ICANN | HTTP 200 | 13.112.194.21 | JP | {"youtube":["https://youtube.com/@nifrel_official"],"facebook":["https://facebook.com/nifrel.jp"],"instagram":["https://instagram.com/NIFREL_OFFICIAL"],"x-twitter":["https://twitter.com/NIFREL_official"]} | 2026-08-13 | Letro, Plesk, HTTP/2, Swiper, jQuery 3.2.1, Twitter, Varnish, YouTube, Google Ads, Open Graph | 0.0000000653597 | 13,836,274 | 2015-03-04 | 2027-03-31 |
| frantz.jp | jp | jp | ICANN | HTTP 200 | 219.99.174.101 | JP | {"facebook":["https://facebook.com/kobefrantz"],"instagram":["https://instagram.com/kobefrantz"],"x-twitter":["https://twitter.com/kobefrantz"]} | 2026-08-03 | HSTS, Letro, Nginx, jQuery 3.7.1, Zendesk, jsDelivr, Open Graph, Google Font API, Google Analytics, Cart Functionality | 0.0000000461346 | 13,690,923 | 2003-05-27 | 2027-05-31 |
| … | … | … | … | … | … | … | … | … | … | … | … | … | … |
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| mini-mal.tokyo | tokyo | tokyo | ICANN | HTTP 200 | 23.227.38.32 | CA | {"facebook":["https://facebook.com/minimalchocolate"],"instagram":["https://instagram.com/minimal_beantobarchocolate"],"x-twitter":["https://twitter.com/Minimal_tokyo"]} | 2026-08-12 | HSTS, Letro, A8.net, HTTP/3, jQuery 3.5.1, Favicon, Klaviyo, Shopify, Apple Pay, Amazon SES | 2026-08-13 | TRUE | {"A":["23.227.38.32"],"MX":[{"host":"mx-proxy501.heteml.jp","priority":10},{"host":"mx-proxy502.heteml.jp","priority":20}],"NS":["01.dnsv.jp","02.dnsv.jp","03.dnsv.jp","04.dnsv.jp"],"SOA":{"mname":"01.dnsv.jp","retry":900,"rname":"hostmaster.dnsv.jp","expire":604800,"serial":1755051181,"minimum":300,"refresh":3600},"TXT":["facebook-domain-verification=q2bbcfw5o1qtwu97qh2f84lod55bf0","google-site-verification=FfuH_dTNYtvnGMXt-B8OkifwrvzPPeF8ObGe4hLqei0","klaviyo-site-verification=LcDatu","v=spf1 include:amazonses.com ip4:157.7.189.17 ip4:157.7.189.18 include:_spf.heteml.jp include:mini-mal.tokyo ~all"]} | 0.000000100561 | 14,188,359 | 2026-03-21 | RDAP | 2014-08-23 | 2028-08-23 | 2026-03-21 | GMO Internet Group, Inc. | {"raw_response":{"lang":"en","links":[{"rel":"about","href":"https://rdap.gmo-onamae.com/rdap/v1/","type":"application/rdap+json","value":"https://rdap.gmo-onamae.com/rdap/v1/"},{"rel":"related","href":"https://rdap.gmo-onamae.com/rdap/v1/domain/mini-mal.tokyo","type":"application/rdap+json","value":"https://rdap.gmo-onamae.com/rdap/v1/domain/mini-mal.tokyo"},{"rel":"self","href":"https://rdap.gmoregistry.net/rdap/domain/mini-mal.tokyo","type":"application/rdap+json","value":"https://rdap.gmoregistry.net/rdap/domain/mini-mal.tokyo"}],"events":[{"eventDate":"2014-08-23T10:23:00.0Z","eventAction":"registration"},{"eventDate":"2028-08-23T23:59:59.0Z","eventAction":"expiration"},{"eventDate":"2025-12-22T07:07:04.0Z","eventAction":"last changed"},{"eventDate":"2026-03-21T03:35:00.0Z","eventAction":"last update of RDAP database"}],"handle":"DO167805-GMO","status":["active"],"ldhName":"mini-mal.tokyo","notices":[{"links":[{"rel":"alternate","href":"https://icann.org/epp","type":"text/html","value":"https://icann.org/epp"}],"title":"Status Codes","description":["For more information on domain status codes, please visit https://icann.org/epp"]},{"links":[{"rel":"alternate","href":"https://www.icann.org/wicf/","type":"text/html","value":"https://www.icann.org/wicf/"}],"title":"RDDS Inaccuracy Complaint Form","description":["URL of the ICANN RDDS Inaccuracy Complaint Form: https://www.icann.org/wicf"]},{"links":[{"rel":"alternate","href":"https://www.gmoregistry.com/en/privacy/","type":"text/html","value":"https://www.gmoregistry.com/en/privacy/"}],"title":"Privacy Policy","description":["GMO Registry prioritizes data privacy, adhering to strict policies and collaborating with partners to protect customer information."]},{"description":["This response conforms to the RDAP Operational Profile for gTLD Registries and Registrars version 1.0"]},{"links":[{"rel":"terms-of-service","href":"https://rdap.gmoregistry.net/tos","type":"text/html","value":"https://rdap.gmoregistry.net/rdap/domain/mini-mal.tokyo"}],"title":"Terms of Service","description":["Please query the RDAP service of the Registrar of Record identified in this output for information on how to contact the Registrar, Registrant, Admin, or Tech contact of the queried domain name.","","This RDAP service is provided by GMO Registry and only contains information pertaining to Internet domain names we have registered for our customers.","GMO Registry does not guarantee the accuracy of this data.","","By using this service you are agreeing;","","(1) only to use the data for lawful purposes.","(2) not to use any information presented here for any purpose other than determining ownership of domain names.","..."]}],"entities":[{"links":[{"rel":"self","href":"https://rdap.gmoregistry.net/rdap/entity/49","type":"application/rdap+json","value":"https://rdap.gmoregistry.net/rdap/entity/49"},{"rel":"about","href":"https://rdap.gmo-onamae.com/rdap/v1/","type":"application/rdap+json","value":"https://rdap.gmo-onamae.com/rdap/v1/"}],"roles":["registrar"],"handle":"49","status":["active"],"entities":[{"roles":["abuse"],"vcardArray":["vcard",[["version",{},"text","4.0"],["email",{},"text","abuse@internet.gmo"],["tel",{"type":"voice"},"uri","tel:+81.337709199"],["fn",{},"text","GMO Internet Group, Inc."]]],"objectClassName":"entity"}],"publicIds":[{"type":"IANA Registrar ID","identifier":"49"}],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text","GMO Internet Group, Inc."]]],"objectClassName":"entity"}],"secureDNS":{"delegationSigned":false},"nameservers":[{"links":[{"rel":"self","href":"https://rdap.gmoregistry.net/rdap/nameserver/01.dnsv.jp","type":"application/rdap+json","value":"https://rdap.gmoregistry.net/rdap/nameserver/01.dnsv.jp"}],"ldhName":"01.dnsv.jp","objectClassName":"nameserver"},{"links":[{"rel":"self","href":"https://rdap.gmoregistry.net/rdap/nameserver/02.dnsv.jp","type":"application/rdap+json","value":"https://rdap.gmoregistry.net/rdap/nameserver/02.dnsv.jp"}],"ldhName":"02.dnsv.jp","objectClassName":"nameserver"},{"links":[{"rel":"self","href":"https://rdap.gmoregistry.net/rdap/nameserver/03.dnsv.jp","type":"application/rdap+json","value":"https://rdap.gmoregistry.net/rdap/nameserver/03.dnsv.jp"}],"ldhName":"03.dnsv.jp","objectClassName":"nameserver"},{"links":[{"rel":"self","href":"https://rdap.gmoregistry.net/rdap/nameserver/04.dnsv.jp","type":"application/rdap+json","value":"https://rdap.gmoregistry.net/rdap/nameserver/04.dnsv.jp"}],"ldhName":"04.dnsv.jp","objectClassName":"nameserver"}],"objectClassName":"domain","rdapConformance":["rdap_level_0","icann_rdap_response_profile_1","icann_rdap_technical_implementation_guide_1"]}} | Domain is active |
| bglen.net | net | net | ICANN | HTTP 200 | 54.192.35.29 | US | {"threads":["https://threads.net/@bglen_official"],"youtube":["https://youtube.com/@bglen_official"],"instagram":["https://instagram.com/bglen_official"],"x-twitter":["https://twitter.com/bglen_official"]} | 2026-07-24 | PHP 7.1.33, Letro, Vimeo, HTTP/3, jQuery 1.11.3, EC-CUBE, Favicon, hreflang, jsDelivr, Bootstrap | 2026-08-09 | TRUE | {"A":["54.192.35.29","54.192.35.62","54.192.35.72","54.192.35.83"],"MX":[{"host":"mx1-us1.ppe-hosted.com","priority":10},{"host":"mx2-us1.ppe-hosted.com","priority":20}],"NS":["ns-1507.awsdns-60.org","ns-1594.awsdns-07.co.uk","ns-237.awsdns-29.com","ns-891.awsdns-47.net"],"SOA":{"mname":"ns-1507.awsdns-60.org","retry":900,"rname":"awsdns-hostmaster.amazon.com","expire":1209600,"serial":1,"minimum":86400,"refresh":7200},"TXT":["_a8avc8oedleyg1kuqqx7h44tvymvjig","facebook-domain-verification=ozieo2np7b2211wu97j9nilacoayjg","google-site-verification=Is15O3ce4J6MtGPe0c9opBt5UHg2b5utZFTVGh2Bk5I","google-site-verification=xXlWcr2lXj1ie1i0-b-n77cvsw4nHA8W5skRr77zlDc","google-site-verification=yaw3_ZUYT7U6-oNmnoPuLYaGrB2UfU0reILTVqu2jS8","v=spf1 ip4:18.176.83.69 ip4:54.249.57.64 ip4:54.176.251.181 ip4:180.147.237.5 include:aws-ec2.bglen.net include:webcas.net ip4:52.192.139.194 include:sm.bglen.net include:spf.repica.jp include:mdburnet.maildealer.jp include:spf-bma.mpme.jp ~all"]} | 0.0000000681514 | 13,420,808 | 2025-08-24 | RDAP | 2004-08-27 | 2026-08-27 | 2025-08-24 | GMO Internet Group, Inc. d/b/a Onamae.com | {"raw_response":{"links":[{"rel":"self","href":"https://rdap.verisign.com/net/v1/domain/BGLEN.NET","type":"application/rdap+json","value":"https://rdap.verisign.com/net/v1/domain/BGLEN.NET"},{"rel":"related","href":"https://rdap.gmo-onamae.com/rdap/v1/domain/BGLEN.NET","type":"application/rdap+json","value":"https://rdap.gmo-onamae.com/rdap/v1/domain/BGLEN.NET"}],"events":[{"eventDate":"2004-08-27T00:25:15Z","eventAction":"registration"},{"eventDate":"2026-08-27T00:25:15Z","eventAction":"expiration"},{"eventDate":"2025-08-20T17:10:46Z","eventAction":"last changed"},{"eventDate":"2025-08-24T19:19:18Z","eventAction":"last update of RDAP database"}],"handle":"128451565_DOMAIN_NET-VRSN","status":["client transfer prohibited"],"ldhName":"BGLEN.NET","notices":[{"links":[{"rel":"terms-of-service","href":"https://www.verisign.com/domain-names/registration-data-access-protocol/terms-service/index.xhtml","type":"text/html","value":"https://rdap.verisign.com/net/v1/domain/bglen.net"}],"title":"Terms of Service","description":["Service subject to Terms of Use."]},{"links":[{"href":"https://icann.org/epp","type":"text/html"}],"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":"text/html","value":"https://rdap.verisign.com/net/v1/domain/bglen.net"}],"title":"RDDS Inaccuracy Complaint Form","description":["URL of the ICANN RDDS Inaccuracy Complaint Form: https://icann.org/wicf"]}],"entities":[{"links":[{"rel":"about","href":"http://gmo.jp","type":"text/html","value":"https://rdap.gmo-onamae.com/rdap/v1/"}],"roles":["registrar"],"handle":"49","entities":[{"roles":["abuse"],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text",""],["tel",{"type":"voice"},"uri","tel:+81.337709199"],["email",{},"text","abuse@internet.gmo"]]],"objectClassName":"entity"}],"publicIds":[{"type":"IANA Registrar ID","identifier":"49"}],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text","GMO Internet Group, Inc. d/b/a Onamae.com"]]],"objectClassName":"entity"}],"secureDNS":{"delegationSigned":false},"nameservers":[{"ldhName":"NS-1507.AWSDNS-60.ORG","objectClassName":"nameserver"},{"ldhName":"NS-1594.AWSDNS-07.CO.UK","objectClassName":"nameserver"},{"ldhName":"NS-237.AWSDNS-29.COM","objectClassName":"nameserver"},{"ldhName":"NS-891.AWSDNS-47.NET","objectClassName":"nameserver"}],"objectClassName":"domain","rdapConformance":["rdap_level_0","icann_rdap_technical_implementation_guide_1","icann_rdap_response_profile_1"]}} | Domain is active |
| atoa-kobe.jp | jp | jp | ICANN | HTTP 200 | 160.16.214.172 | JP | {"youtube":["https://youtube.com/channel/UC-slxcqbaMS4hnybQye7nag"],"facebook":["https://facebook.com/atoa.kobe"],"instagram":["https://instagram.com/atoa_kobe"],"x-twitter":["https://twitter.com/atoa_kobe"]} | 2026-07-23 | PHP 7.2.24, Letro, Slick, jQuery 3.6.0, Favicon, Google Ads, Open Graph, TikTok Pixel, scrollreveal, Facebook Pixel | 2026-08-16 | TRUE | {"A":["160.16.214.172"],"MX":[{"host":"mail.atoa-kobe.jp","priority":10}],"NS":["01.dnsv.jp","02.dnsv.jp","03.dnsv.jp","04.dnsv.jp"],"SOA":{"mname":"01.dnsv.jp","retry":900,"rname":"hostmaster.dnsv.jp","expire":604800,"serial":1709701967,"minimum":300,"refresh":3600},"TXT":["v=spf1 ip4:160.16.214.172 ip4:163.43.252.151 -all"]} | 0.0000000679826 | 13,700,399 | 2025-10-12 | WHOIS | 2020-09-10 | 2026-09-30 | 2025-10-01 | (Not displayed by registrant's request) | {"raw_response":"[ JPRS database provides information on network administration. Its use is ]\r\n[ restricted to network administration purposes. For further information, ]\r\n[ use 'whois -h whois.jprs.jp help'. To suppress Japanese output, add'/e' ]\r\n[ at the end of command, e.g. 'whois -h whois.jprs.jp xxx/e'. ]\r\nDomain Information:\r\n[Domain Name] ATOA-KOBE.JP\r\n\r\n[Registrant] (Not displayed by registrant's request)\r\n For details -> https://jprs.jp/about/dom-rule/whois-concealment/ (only in Japanese)\r\n\r\n[Name Server] 03.dnsv.jp\r\n[Name Server] 02.dnsv.jp\r\n[Name Server] 01.dnsv.jp\r\n[Name Server] 04.dnsv.jp\r\n[Signing Key] \r\n\r\n[Created on] 2020/09/10\r\n[Expires on] 2026/09/30\r\n[Status] Active\r\n[Last Updated] 2025/10/01 01:05:04 (JST)\r\n\r\nContact Information:\r\n[Name] Whois Privacy Protection Service by onamae.com\r\n[Email] proxy@whoisprotectservice.com\r\n[Web Page] \r\n[Postal code] 150-8512\r\n[Postal Address] Shibuya-ku\r\n 26-1 Sakuragaoka-cho\r\n Cerulean Tower 11F\r\n[Phone] +81.354562560\r\n[Fax] \r\n\r\n"} | Domain is active |
| nifrel.jp | jp | jp | ICANN | HTTP 200 | 13.112.194.21 | JP | {"youtube":["https://youtube.com/@nifrel_official"],"facebook":["https://facebook.com/nifrel.jp"],"instagram":["https://instagram.com/NIFREL_OFFICIAL"],"x-twitter":["https://twitter.com/NIFREL_official"]} | 2026-08-13 | Letro, Plesk, HTTP/2, Swiper, jQuery 3.2.1, Twitter, Varnish, YouTube, Google Ads, Open Graph | 2026-08-08 | TRUE | {"A":["13.112.194.21"],"MX":[{"host":"kaiyukan.in.tmems-jp.trendmicro.com","priority":10}],"NS":["ns-1490.awsdns-58.org","ns-1591.awsdns-06.co.uk","ns-205.awsdns-25.com","ns-991.awsdns-59.net"],"SOA":{"mname":"ns-991.awsdns-59.net","retry":900,"rname":"awsdns-hostmaster.amazon.com","expire":1209600,"serial":1,"minimum":86400,"refresh":7200},"TXT":["v=spf1 ip4:164.46.119.216 ip4:219.99.164.76 include:_spf.google.com include:spf.messagelabs.com ~all"]} | 0.0000000653597 | 13,836,274 | 2026-04-22 | WHOIS | 2015-03-04 | 2027-03-31 | 2026-04-01 | — | {"raw_response":"[ JPRS database provides information on network administration. Its use is ]\r\n[ restricted to network administration purposes. For further information, ]\r\n[ use 'whois -h whois.jprs.jp help'. To suppress Japanese output, add'/e' ]\r\n[ at the end of command, e.g. 'whois -h whois.jprs.jp xxx/e'. ]\r\nDomain Information:\r\n[Domain Name] NIFREL.JP\r\n\r\n[Registrant] kaiyukan\r\n\r\n[Name Server] ns-991.awsdns-59.net\r\n[Name Server] ns-1490.awsdns-58.org\r\n[Name Server] ns-205.awsdns-25.com\r\n[Name Server] ns-1591.awsdns-06.co.uk\r\n[Signing Key] \r\n\r\n[Created on] 2015/03/04\r\n[Expires on] 2027/03/31\r\n[Status] Active\r\n[Last Updated] 2026/04/01 01:05:03 (JST)\r\n\r\nContact Information:\r\n[Name] kaiyukan\r\n[Email] tai@kaiyukan.com\r\n[Web Page] \r\n[Postal code] 565-0826\r\n[Postal Address] Senri Bampakukoen, Suita-shi\r\n[Phone] 06-6876-2204\r\n[Fax] 06-6876-2235"} | Domain is active |
| frantz.jp | jp | jp | ICANN | HTTP 200 | 219.99.174.101 | JP | {"facebook":["https://facebook.com/kobefrantz"],"instagram":["https://instagram.com/kobefrantz"],"x-twitter":["https://twitter.com/kobefrantz"]} | 2026-08-03 | HSTS, Letro, Nginx, jQuery 3.7.1, Zendesk, jsDelivr, Open Graph, Google Font API, Google Analytics, Cart Functionality | 2026-08-10 | TRUE | {"A":["219.99.174.101","219.99.174.102"],"MX":[{"host":"mail.frantz.jp","priority":10}],"NS":["ns0.future-s.com","ns1.future-s.com"],"SOA":{"mname":"ns0.future-s.com","retry":600,"rname":"dnsadmin.future-s.com","expire":3600000,"serial":2026011602,"minimum":36000,"refresh":360000},"TXT":["google-site-verification=WXUzbY2u0XPI4HrmyyPlIak6pm-JPxabKR762RaBYlY","v=spf1 +ip4:111.89.202.65/32 +ip4:111.89.202.2/32 include:spfgw.fsi.ne.jp include:spf.q-send.jp include:_spf.google.com include:mail.zendesk.com include:fmx.etius.jp include:send.k-crm.jp -all"]} | 0.0000000461346 | 13,690,923 | 2026-06-26 | WHOIS | 2003-05-27 | 2027-05-31 | 2026-06-01 | — | {"raw_response":"[ JPRS database provides information on network administration. Its use is ]\r\n[ restricted to network administration purposes. For further information, ]\r\n[ use 'whois -h whois.jprs.jp help'. To suppress Japanese output, add'/e' ]\r\n[ at the end of command, e.g. 'whois -h whois.jprs.jp xxx/e'. ]\r\nDomain Information:\r\n[Domain Name] FRANTZ.JP\r\n\r\n[Registrant] Frantz,inc\r\n\r\n[Name Server] ns0.future-s.com\r\n[Name Server] ns1.future-s.com\r\n[Signing Key] \r\n\r\n[Created on] 2003/05/27\r\n[Expires on] 2027/05/31\r\n[Status] Active\r\n[Lock Status] DomainTransferLocked\r\n[Lock Status] AgentChangeLocked\r\n[Last Updated] 2026/06/01 01:05:03 (JST)\r\n\r\nContact Information:\r\n[Name] Future Spirits Co.,Ltd.\r\n[Email] jpnic-apply@future-s.com\r\n[Web Page] \r\n[Postal code] 600-8815\r\n[Postal Address] Kyoto\r\n Shimogyo-ku, Kyoto-shi\r\n KRP #9, 91, Chudoji Awatacho\r\n[Phone] 075-326-3700\r\n[Fax] 075-326-7400"} | Domain is active |
| … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … |
El dataset Letro
Todos los sitios que hemos detectado utilizando Letro, con versión, hosting, país, TLD y ranking de tráfico.
Letro está presente en 2 datasets
La detección de Letro forma parte de Technologies (€159/mes) y All data (€599/mes). Compre cualquiera de los dos para filtrar la lista completa de 29 sitios, o consiga antes una vista previa gratuita.
¿Qué sitios web utilizan Letro?
webatla detecta todos los sitios que utilizan Letro y los exporta en una única lista descargable, para que pueda ver quién depende de esta tecnología y qué más se ejecuta junto a ella.
Abra el dataset de la tecnología Letro para desglosar la adopción por país y TLD, compararla con una tecnología competidora, y hacer seguimiento de los nuevos dominios a lo largo del tiempo.
Preguntas frecuentes
¿Cuántos sitios web usan Letro?
webatla detecta Letro en 29 sitios web, actualizados a diario, cada uno con su dominio, DNS, WHOIS, IP, país y clasificación.
¿Puedo descargar la lista de sitios web que usan Letro?
Sí, en formato JSONL estructurado. Consiga antes una muestra gratuita.
¿Qué incluye cada sitio, y con qué frecuencia se actualiza?
Dominio, DNS, RDAP/WHOIS, la stack tecnológica completa, IP & país, PageRank y Harmonic, redetectados y reexportados a diario.
¿Cómo encuentro los sitios web que utilizan Letro?
Compre el dataset Technologies y descargue la lista completa de dominios en los que detectamos Letro, reexportada cada día.
¿Qué más incluyen los datos de tecnología de Letro?
Cada fila coloca Letro junto a las demás tecnologías del mismo sitio, además de DNS, WHOIS, IP, país y clasificación.
¿Puedo descargar solo los sitios que utilizan Letro, o la base de datos completa?
Ambos. Cada sitio que usa Letro figura en el dataset Technologies, un archivo descargable. O compre All data para toda la base de datos: tecnologías, más identidad, ranking, DNS y RDAP/WHOIS para cada dominio, reunidos en un solo archivo. Exportación actualizada a diario.
¿Cómo descargo la lista de sitios web que utilizan Letro?
Tres pasos: (1) consiga la muestra gratuita de 10.000 filas para examinar el esquema, (2) compre el dataset Technologies, (3) descargue la lista completa de todos los dominios en los que detectamos Letro, en forma de archivo JSON Lines. Se reexporta a diario, así que puede volver a descargar la lista más reciente en cualquier momento dentro de su periodo de acceso. Cada fila contiene el dominio junto con el DNS, el WHOIS, la IP, el país de alojamiento y la clasificación.
Consiga la lista completa de sitios web que usan Letro
Elija el dataset que cubra lo que necesita. Cada uno incluye Letro y se descarga en JSONL, reconstruido a diario.
¿Quiere comparar todos los datasets uno junto al otro? Ver la página de precios