Descarregar domínios .meguro.tokyo.jp
5 domínios ativos
Sufixo público · Sob .jp · Operado por Japan Registry Services Co., Ltd. (JPRS)
Sobre .meguro.tokyo.jp
.meguro.tokyo.jp é um sufixo público multinível situado um nível abaixo de .jp. Sufixos como este existem porque os registos reservam um segundo nível para categorias específicas de titulares de domínios. Os titulares tratam-nos como se fossem TLD de nível superior, e os datasets da webatla também.
Numa vista de olhos
Pré-visualização da base de dados de domínios .meguro.tokyo.jp
5 linhas de amostra da base de dados em direto. Mude de dataset para ver o que cada um contém e depois consulte o ficheiro ou compre o dataset completo.
| Domain | TLD suffix | TLD | Domain type |
|---|---|---|---|
| city.meguro.tokyo.jp | meguro.tokyo.jp | jp | ICANN |
| tkh.meguro.tokyo.jp | meguro.tokyo.jp | jp | ICANN |
| ytnt.meguro.tokyo.jp | meguro.tokyo.jp | jp | ICANN |
| etandard.meguro.tokyo.jp | meguro.tokyo.jp | jp | ICANN |
| meguro.tokyo.jp | meguro.tokyo.jp | jp | ICANN |
| … | … | … | … |
| Domain | TLD suffix | TLD | Domain type | Country by IP | PR value | Harmonic value | Domain creation date | Domain expiration date |
|---|---|---|---|---|---|---|---|---|
| city.meguro.tokyo.jp | meguro.tokyo.jp | jp | ICANN | — | 0.000000520041 | 16,929,366 | — | — |
| tkh.meguro.tokyo.jp | meguro.tokyo.jp | jp | ICANN | JP | 0.0000000151804 | 12,308,368 | — | — |
| ytnt.meguro.tokyo.jp | meguro.tokyo.jp | jp | ICANN | JP | 0.00000000467586 | 12,159,489 | — | — |
| etandard.meguro.tokyo.jp | meguro.tokyo.jp | jp | ICANN | JP | 0.00000000420431 | 8,503,291 | — | — |
| meguro.tokyo.jp | meguro.tokyo.jp | jp | ICANN | — | 0 | 0 | — | — |
| … | … | … | … | … | … | … | … | … |
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| city.meguro.tokyo.jp | meguro.tokyo.jp | jp | ICANN | HTTP 200 | — | — | — | 2026-07-27 | Nginx, jQuery, Favicon, OpenResty, Amazon SES, Open Graph, Amazon CloudFront, Amazon Web Services | 0.000000520041 | 16,929,366 | — | — |
| tkh.meguro.tokyo.jp | meguro.tokyo.jp | jp | ICANN | HTTP 0 | 122.28.46.206 | JP | — | 2026-07-08 | — | 0.0000000151804 | 12,308,368 | — | — |
| ytnt.meguro.tokyo.jp | meguro.tokyo.jp | jp | ICANN | HTTP 200 | 180.222.87.94 | JP | — | 2026-07-18 | IIS 10.0, Unpkg, cdnjs, Swiper, jQuery 1.12.4, DigiCert, Bootstrap, Cloudflare, jQuery CDN, Google Maps | 0.00000000467586 | 12,159,489 | — | — |
| etandard.meguro.tokyo.jp | meguro.tokyo.jp | jp | ICANN | HTTP 0 | 219.166.161.226 | JP | — | 2026-08-03 | — | 0.00000000420431 | 8,503,291 | — | — |
| meguro.tokyo.jp | meguro.tokyo.jp | jp | ICANN | HTTP 0 | — | — | — | 2026-08-11 | — | 0 | 0 | — | — |
| … | … | … | … | … | … | … | … | … | … | … | … | … | … |
| Domain | TLD suffix | TLD | Domain type | DNS last data checked | DNS Status | DNS records |
|---|---|---|---|---|---|---|
| city.meguro.tokyo.jp | meguro.tokyo.jp | jp | ICANN | 2026-08-14 | TRUE | {"MX":[{"host":"mailgates01.city.meguro.tokyo.jp","priority":10}],"NS":["ns1.gslb8.sakura.ne.jp","ns2.gslb8.sakura.ne.jp"],"SOA":{"mname":"ns1.gslb8.sakura.ne.jp","retry":900,"rname":"noc.sakura.ad.jp","expire":2419200,"serial":1,"minimum":300,"refresh":3600},"TXT":["MS=ms53573273","v=spf1 ip4:111.98.253.110 include:smp.ne.jp include:_spf.mailio.jp include:amazonses.com ~all"]} |
| tkh.meguro.tokyo.jp | meguro.tokyo.jp | jp | ICANN | 2026-08-16 | TRUE | {"A":["122.28.46.206"],"MX":[{"host":"mwbgw1.ocn.ad.jp","priority":10},{"host":"mwbgw2.ocn.ad.jp","priority":10}],"NS":["ns1.surfline.ad.jp","ns3.surfline.ad.jp","ns4.surfline.ad.jp"],"SOA":{"mname":"ns1.surfline.ad.jp","retry":1800,"rname":"root.surfline.ad.jp","expire":604800,"serial":2024042501,"minimum":3600,"refresh":3600},"TXT":["v=spf1 a include:_spf.bizmw.com ip4:211.123.201.14 ip4:211.123.201.15 ip4:211.123.201.16 ip4:211.123.201.21 ip4:211.123.201.22 ~all"]} |
| ytnt.meguro.tokyo.jp | meguro.tokyo.jp | jp | ICANN | 2026-08-10 | TRUE | {"A":["180.222.87.94"],"MX":[{"host":"vlmx20.secure.ne.jp","priority":10},{"host":"vlmx21.secure.ne.jp","priority":10},{"host":"vlmx22.secure.ne.jp","priority":20}],"NS":["nsk0.secure.ne.jp","nsk1.secure.ne.jp"],"SOA":{"mname":"nsk0.secure.ne.jp","retry":900,"rname":"hostmaster.cpi.ad.jp","expire":3600000,"serial":2412180002,"minimum":86400,"refresh":3600},"TXT":["v=spf1 include:spf.secure.ne.jp -all"]} |
| etandard.meguro.tokyo.jp | meguro.tokyo.jp | jp | ICANN | 2026-08-09 | TRUE | {"A":["219.166.161.226"],"MX":[{"host":"bs.etandard.meguro.tokyo.jp","priority":20},{"host":"ns.etandard.meguro.tokyo.jp","priority":10}],"NS":["bs.etandard.meguro.tokyo.jp","ns-tk012.ocn.ad.jp","ns.etandard.meguro.tokyo.jp","ns6-tk01.ocn.ad.jp"],"PTR":["224.161.166.219.in-addr.arpa"],"SOA":{"mname":"ns.etandard.meguro.tokyo.jp","retry":900,"rname":"miki.etandard.meguro.tokyo.jp","expire":3600000,"serial":2025102503,"minimum":86400,"refresh":3600},"TXT":["v=spf1 ip4:219.166.161.226 include:_spf.google.com ~all"]} |
| meguro.tokyo.jp | meguro.tokyo.jp | jp | ICANN | 2026-08-03 | TRUE | {"TXT":["meguro.tokyo.jp."]} |
| … | … | … | … | … | … | … |
| Domain | 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 |
|---|---|---|---|---|---|---|---|---|
| city.meguro.tokyo.jp | 2026-08-09 | WHOIS | — | — | 2025-10-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\na. [Domain Name] CITY.MEGURO.TOKYO.JP\r\ng. [Organization] Meguro City\r\nl. [Organization Type] Local Government\r\nm. [Administrative Contact] MI31036JP\r\nn. [Technical Contact] MI31036JP\r\np. [Name Server] ns1.gslb8.sakura.ne.jp\r\np. [Name Server] ns2.gslb8.sakura.ne.jp\r\ns. [Signing Key] \r\n[State] Connected (2026/09/30)\r\n[Registered Date] 1997/09/16\r\n[Connected Date] 1997/09/25\r\n[Last Update] 2025/10/01 01:01:06 (JST)"} | Domain is active |
| tkh.meguro.tokyo.jp | 2026-08-17 | WHOIS | — | — | 2026-07-03 | — | {"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\na. [Domain Name] TKH.MEGURO.TOKYO.JP\r\ng. [Organization] TOKYO-KYOSAI-HOSPITAL\r\nl. [Organization Type] Hospital\r\nm. [Administrative Contact] HI50424JP\r\nn. [Technical Contact] TK1081JP\r\np. [Name Server] ns1.surfline.ad.jp\r\np. [Name Server] ns3.surfline.ad.jp\r\np. [Name Server] ns4.surfline.ad.jp\r\ns. [Signing Key] \r\n[State] Connected (2026/11/30)\r\n[Registered Date] 1999/11/16\r\n[Connected Date] 1999/12/02\r\n[Last Update] 2026/07/03 10:06:31 (JST)"} | Domain is active |
| ytnt.meguro.tokyo.jp | 2026-08-08 | WHOIS | — | — | 2026-03-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\na. [Domain Name] YTNT.MEGURO.TOKYO.JP\r\ng. [Organization] (Tohyama, Yoshio)\r\nl. [Organization Type] Person\r\nm. [Administrative Contact] YT828JP\r\nn. [Technical Contact] TK113580JP\r\np. [Name Server] nsk0.secure.ne.jp\r\np. [Name Server] nsk1.secure.ne.jp\r\ns. [Signing Key] \r\n[State] Connected (2027/02/28)\r\n[Registered Date] 1998/02/13\r\n[Connected Date] 1998/02/24\r\n[Last Update] 2026/03/01 01:02:48 (JST)"} | Domain is active |
| etandard.meguro.tokyo.jp | 2026-08-09 | WHOIS | — | — | 2026-01-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\na. [Domain Name] ETANDARD.MEGURO.TOKYO.JP\r\ng. [Organization] (Miki, Susumu)\r\nl. [Organization Type] Person\r\nm. [Administrative Contact] SM077JP\r\nn. [Technical Contact] SM077JP\r\np. [Name Server] ns.etandard.meguro.tokyo.jp\r\np. [Name Server] bs.etandard.meguro.tokyo.jp\r\np. [Name Server] ns-tk012.ocn.ad.jp\r\ns. [Signing Key] \r\n[State] Connected (2026/12/31)\r\n[Registered Date] 1997/12/22\r\n[Connected Date] 1998/01/23\r\n[Last Update] 2026/01/01 01:02:19 (JST)"} | Domain is active |
| meguro.tokyo.jp | 2026-08-09 | WHOIS | — | — | 2012-06-06 | — | {"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] MEGURO.TOKYO.JP\r\n\r\n[Registrant] \r\n\r\n[Name Server] \r\n[Signing Key] \r\n\r\n[Created on] \r\n[Expires on] \r\n[Status] Reserved\r\n[Last Updated] 2012/06/06 10:31:50 (JST)\r\n\r\nContact Information:\r\n[Name] \r\n[Email] \r\n[Web Page] \r\n[Postal code] \r\n[Postal Address] \r\n[Phone] \r\n[Fax]"} | Domain is active |
| … | … | … | … | … | … | … | … | … |
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| city.meguro.tokyo.jp | meguro.tokyo.jp | jp | ICANN | HTTP 200 | — | — | — | 2026-07-27 | Nginx, jQuery, Favicon, OpenResty, Amazon SES, Open Graph, Amazon CloudFront, Amazon Web Services | 2026-08-14 | TRUE | {"MX":[{"host":"mailgates01.city.meguro.tokyo.jp","priority":10}],"NS":["ns1.gslb8.sakura.ne.jp","ns2.gslb8.sakura.ne.jp"],"SOA":{"mname":"ns1.gslb8.sakura.ne.jp","retry":900,"rname":"noc.sakura.ad.jp","expire":2419200,"serial":1,"minimum":300,"refresh":3600},"TXT":["MS=ms53573273","v=spf1 ip4:111.98.253.110 include:smp.ne.jp include:_spf.mailio.jp include:amazonses.com ~all"]} | 0.000000520041 | 16,929,366 | 2026-08-09 | WHOIS | — | — | 2025-10-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\na. [Domain Name] CITY.MEGURO.TOKYO.JP\r\ng. [Organization] Meguro City\r\nl. [Organization Type] Local Government\r\nm. [Administrative Contact] MI31036JP\r\nn. [Technical Contact] MI31036JP\r\np. [Name Server] ns1.gslb8.sakura.ne.jp\r\np. [Name Server] ns2.gslb8.sakura.ne.jp\r\ns. [Signing Key] \r\n[State] Connected (2026/09/30)\r\n[Registered Date] 1997/09/16\r\n[Connected Date] 1997/09/25\r\n[Last Update] 2025/10/01 01:01:06 (JST)"} | Domain is active |
| tkh.meguro.tokyo.jp | meguro.tokyo.jp | jp | ICANN | HTTP 0 | 122.28.46.206 | JP | — | 2026-07-08 | — | 2026-08-16 | TRUE | {"A":["122.28.46.206"],"MX":[{"host":"mwbgw1.ocn.ad.jp","priority":10},{"host":"mwbgw2.ocn.ad.jp","priority":10}],"NS":["ns1.surfline.ad.jp","ns3.surfline.ad.jp","ns4.surfline.ad.jp"],"SOA":{"mname":"ns1.surfline.ad.jp","retry":1800,"rname":"root.surfline.ad.jp","expire":604800,"serial":2024042501,"minimum":3600,"refresh":3600},"TXT":["v=spf1 a include:_spf.bizmw.com ip4:211.123.201.14 ip4:211.123.201.15 ip4:211.123.201.16 ip4:211.123.201.21 ip4:211.123.201.22 ~all"]} | 0.0000000151804 | 12,308,368 | 2026-08-17 | WHOIS | — | — | 2026-07-03 | — | {"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\na. [Domain Name] TKH.MEGURO.TOKYO.JP\r\ng. [Organization] TOKYO-KYOSAI-HOSPITAL\r\nl. [Organization Type] Hospital\r\nm. [Administrative Contact] HI50424JP\r\nn. [Technical Contact] TK1081JP\r\np. [Name Server] ns1.surfline.ad.jp\r\np. [Name Server] ns3.surfline.ad.jp\r\np. [Name Server] ns4.surfline.ad.jp\r\ns. [Signing Key] \r\n[State] Connected (2026/11/30)\r\n[Registered Date] 1999/11/16\r\n[Connected Date] 1999/12/02\r\n[Last Update] 2026/07/03 10:06:31 (JST)"} | Domain is active |
| ytnt.meguro.tokyo.jp | meguro.tokyo.jp | jp | ICANN | HTTP 200 | 180.222.87.94 | JP | — | 2026-07-18 | IIS 10.0, Unpkg, cdnjs, Swiper, jQuery 1.12.4, DigiCert, Bootstrap, Cloudflare, jQuery CDN, Google Maps | 2026-08-10 | TRUE | {"A":["180.222.87.94"],"MX":[{"host":"vlmx20.secure.ne.jp","priority":10},{"host":"vlmx21.secure.ne.jp","priority":10},{"host":"vlmx22.secure.ne.jp","priority":20}],"NS":["nsk0.secure.ne.jp","nsk1.secure.ne.jp"],"SOA":{"mname":"nsk0.secure.ne.jp","retry":900,"rname":"hostmaster.cpi.ad.jp","expire":3600000,"serial":2412180002,"minimum":86400,"refresh":3600},"TXT":["v=spf1 include:spf.secure.ne.jp -all"]} | 0.00000000467586 | 12,159,489 | 2026-08-08 | WHOIS | — | — | 2026-03-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\na. [Domain Name] YTNT.MEGURO.TOKYO.JP\r\ng. [Organization] (Tohyama, Yoshio)\r\nl. [Organization Type] Person\r\nm. [Administrative Contact] YT828JP\r\nn. [Technical Contact] TK113580JP\r\np. [Name Server] nsk0.secure.ne.jp\r\np. [Name Server] nsk1.secure.ne.jp\r\ns. [Signing Key] \r\n[State] Connected (2027/02/28)\r\n[Registered Date] 1998/02/13\r\n[Connected Date] 1998/02/24\r\n[Last Update] 2026/03/01 01:02:48 (JST)"} | Domain is active |
| etandard.meguro.tokyo.jp | meguro.tokyo.jp | jp | ICANN | HTTP 0 | 219.166.161.226 | JP | — | 2026-08-03 | — | 2026-08-09 | TRUE | {"A":["219.166.161.226"],"MX":[{"host":"bs.etandard.meguro.tokyo.jp","priority":20},{"host":"ns.etandard.meguro.tokyo.jp","priority":10}],"NS":["bs.etandard.meguro.tokyo.jp","ns-tk012.ocn.ad.jp","ns.etandard.meguro.tokyo.jp","ns6-tk01.ocn.ad.jp"],"PTR":["224.161.166.219.in-addr.arpa"],"SOA":{"mname":"ns.etandard.meguro.tokyo.jp","retry":900,"rname":"miki.etandard.meguro.tokyo.jp","expire":3600000,"serial":2025102503,"minimum":86400,"refresh":3600},"TXT":["v=spf1 ip4:219.166.161.226 include:_spf.google.com ~all"]} | 0.00000000420431 | 8,503,291 | 2026-08-09 | WHOIS | — | — | 2026-01-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\na. [Domain Name] ETANDARD.MEGURO.TOKYO.JP\r\ng. [Organization] (Miki, Susumu)\r\nl. [Organization Type] Person\r\nm. [Administrative Contact] SM077JP\r\nn. [Technical Contact] SM077JP\r\np. [Name Server] ns.etandard.meguro.tokyo.jp\r\np. [Name Server] bs.etandard.meguro.tokyo.jp\r\np. [Name Server] ns-tk012.ocn.ad.jp\r\ns. [Signing Key] \r\n[State] Connected (2026/12/31)\r\n[Registered Date] 1997/12/22\r\n[Connected Date] 1998/01/23\r\n[Last Update] 2026/01/01 01:02:19 (JST)"} | Domain is active |
| meguro.tokyo.jp | meguro.tokyo.jp | jp | ICANN | HTTP 0 | — | — | — | 2026-08-11 | — | 2026-08-03 | TRUE | {"TXT":["meguro.tokyo.jp."]} | 0 | 0 | 2026-08-09 | WHOIS | — | — | 2012-06-06 | — | {"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] MEGURO.TOKYO.JP\r\n\r\n[Registrant] \r\n\r\n[Name Server] \r\n[Signing Key] \r\n\r\n[Created on] \r\n[Expires on] \r\n[Status] Reserved\r\n[Last Updated] 2012/06/06 10:31:50 (JST)\r\n\r\nContact Information:\r\n[Name] \r\n[Email] \r\n[Web Page] \r\n[Postal code] \r\n[Postal Address] \r\n[Phone] \r\n[Fax]"} | Domain is active |
| … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … |
O dataset .meguro.tokyo.jp
Tudo o que temos sobre 5 domínios .meguro.tokyo.jp num único ficheiro descarregável, com uma exportação atualizada todos os dias. Mesmas colunas e a mesma cadência que qualquer TLD de nível superior.
Compre um dataset para descarregar .meguro.tokyo.jp
O fragmento completo de .meguro.tokyo.jp (JSONL, exportações diárias atualizadas) está dentro de cada dataset. Obtenha um a partir de €29 até €599 por mês e descarregue imediatamente.
Como descarregar a lista de domínios .meguro.tokyo.jp
A lista completa de domínios .meguro.tokyo.jp está disponível como um único ficheiro estruturado. Cada entrada da lista é um domínio registado individual, exportado com o seu registo completo, para que possa processar tudo offline em vez de o rastrear pessoalmente.
Escolha o dataset que se adequa ao seu caso de uso e, em seguida, transfira a lista .meguro.tokyo.jp em JSONL (comprimido com zstd), exatamente a mesma lista que alimenta a nossa API. Uma amostra gratuita da lista está disponível antes de pagar, e pode voltar a transferir o export mais recente a qualquer momento durante o seu mês de acesso.
Cada lista de .meguro.tokyo.jp inclui, para cada domínio:
- Registos DNS, RDAP e WHOIS, registrar e datas em toda a lista.
- Tecnologias detetadas para cada site da lista.
- IP de alojamento, país e ranking PageRank / Harmonic.
- Uma exportação atualizada diariamente, para que a lista que recebe nunca esteja desatualizada.
Perguntas frequentes
Quantos domínios .meguro.tokyo.jp existem?
webatla regista 5 domínios .meguro.tokyo.jp ativos, reexportados todos os dias, cada um com o seu DNS, RDAP/WHOIS, tecnologias detetadas, IP, país de alojamento e classificação.
Posso descarregar a lista completa de domínios .meguro.tokyo.jp?
Sim, a lista completa de .meguro.tokyo.jp descarrega-se em JSONL estruturado (zstd). Antes disso está disponível uma amostra gratuita.
O que está incluído em cada domínio e quão atualizado está?
Cada domínio inclui o esquema completo (DNS, RDAP/WHOIS, tecnologias, IP & país, PageRank e Harmonic), reexportado diariamente.
Como descarrego a lista de domínios .meguro.tokyo.jp?
Escolha um dataset, e a lista completa de .meguro.tokyo.jp passa a ser sua num único ficheiro JSONL na sua conta. Pode voltar a descarregar a lista a qualquer momento durante o seu mês de acesso, e uma amostra gratuita está disponível para descarregar primeiro.
Em que formato está a lista de .meguro.tokyo.jp?
A lista é sua para descarregar como JSONL comprimido com zstd, um domínio por linha, pronta a carregar diretamente em qualquer base de dados ou script. Essa mesma lista também está disponível através da nossa API.
Posso descarregar apenas os domínios .meguro.tokyo.jp, ou a base de dados completa?
Ambas as opções. Cada dataset é um único ficheiro descarregável, compre apenas o que precisa para .meguro.tokyo.jp. Ou compre All data para toda a base de dados: todos os datasets combinados (identidade, ranking, tecnologias, DNS e RDAP/WHOIS) num único ficheiro. Exportação diária atualizada.
Consiga a lista completa de domínios .meguro.tokyo.jp
Escolha o dataset que cobre o que precisa. Cada um inclui .meguro.tokyo.jp e é transferido em JSONL, reconstruído diariamente.
Quer comparar todos os datasets lado a lado? Ver a página de preços