.mitaka.tokyo.jp

Descarregar domínios .mitaka.tokyo.jp

5 domínios ativos

Sufixo público · Sob .jp · Operado por Japan Registry Services Co., Ltd. (JPRS)

Sufixo TLD Dataset atualizado · 2026-08-18
🔒 Obter a lista
A partir de €29 / mês

Sobre .mitaka.tokyo.jp

.mitaka.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

Sufixo.mitaka.tokyo.jp
TLD superior.jp
RegistoJapan Registry Services Co., Ltd. (JPRS)
Domínios5
Todos os números à data de 18/08/2026
Novos registos de domínio
semana passada
mês passado
Domínios ativos
5
domínios registados e ativos na zona .mitaka.tokyo.jp
Sites ativos
2
sites ativos na zona .mitaka.tokyo.jp
DNS
5
domínios com registos DNS
Países
1
países representados (por IP de alojamento)
RDAP & WHOIS
5
domínios com registos RDAP e WHOIS

Pré-visualização da base de dados de domínios .mitaka.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.

webatla-mitaka-tokyo-jp-all-2026-08-18.jsonl.zst · 5 linhas · 23 colunas Exportação diária atualizada
DomainTLD suffixTLDDomain type
city.mitaka.tokyo.jpmitaka.tokyo.jpjpICANN
library.mitaka.tokyo.jpmitaka.tokyo.jpjpICANN
suiren.mitaka.tokyo.jpmitaka.tokyo.jpjpICANN
hyc.mitaka.tokyo.jpmitaka.tokyo.jpjpICANN
mitaka.tokyo.jpmitaka.tokyo.jpjpICANN
DomainTLD suffixTLDDomain typeCountry by IPPR valueHarmonic valueDomain creation dateDomain expiration date
city.mitaka.tokyo.jpmitaka.tokyo.jpjpICANN0.00000007543314,204,692
library.mitaka.tokyo.jpmitaka.tokyo.jpjpICANN0.000000014700913,643,816
suiren.mitaka.tokyo.jpmitaka.tokyo.jpjpICANNJP0.000000004386639,549,756
hyc.mitaka.tokyo.jpmitaka.tokyo.jpjpICANNJP0.0000000041156510,471,868
mitaka.tokyo.jpmitaka.tokyo.jpjpICANN00
DomainTLD suffixTLDDomain typeHTTP statusIP addressCountry by IPSocial networksTechnologies last data checkedTechnologiesPR valueHarmonic valueDomain creation dateDomain expiration date
city.mitaka.tokyo.jpmitaka.tokyo.jpjpICANNHTTP 02026-07-27Apple iCloud Mail, Amazon Web Services0.00000007543314,204,692
library.mitaka.tokyo.jpmitaka.tokyo.jpjpICANNHTTP 3022026-08-08Java, Apache HTTP Server0.000000014700913,643,816
suiren.mitaka.tokyo.jpmitaka.tokyo.jpjpICANNHTTP 200160.251.151.144JP2026-07-08HSTS, HTTP/2, Apache HTTP Server0.000000004386639,549,756
hyc.mitaka.tokyo.jpmitaka.tokyo.jpjpICANNHTTP 403153.122.205.45JP2026-08-050.0000000041156510,471,868
mitaka.tokyo.jpmitaka.tokyo.jpjpICANNHTTP 02026-08-1200
DomainTLD suffixTLDDomain typeDNS last data checkedDNS StatusDNS records
city.mitaka.tokyo.jpmitaka.tokyo.jpjpICANN2026-08-07TRUE{"NS":["ns-1511.awsdns-60.org","ns-1548.awsdns-01.co.uk","ns-209.awsdns-26.com","ns-891.awsdns-47.net"],"SOA":{"mname":"ns-1511.awsdns-60.org","retry":1800,"rname":"awsdns-hostmaster.amazon.com","expire":3600000,"serial":2022101401,"minimum":900,"refresh":3600},"TXT":["apple-domain-verification=JDfBy2sFY1kJP2r1"]}
library.mitaka.tokyo.jpmitaka.tokyo.jpjpICANN2026-08-08TRUE{"MX":[{"host":"mtk-lib.in.tmems-jp.trendmicro.com","priority":10}],"NS":["ns-tk011.ocn.ad.jp","ns.library.mitaka.tokyo.jp"],"SOA":{"mname":"ns.library.mitaka.tokyo.jp","retry":3600,"rname":"admin.library.mitaka.tokyo.jp","expire":604800,"serial":2025091601,"minimum":300,"refresh":10800},"TXT":["trend-micro-v1-domain-verification.2fd985fa556d5576d07e05c682f8707c=3c39c175-07e3-4f44-84b1-f744a2d04aca","v=spf1 ip4:122.1.10.250 include:spf.tmems-jp.trendmicro.com ~all"]}
suiren.mitaka.tokyo.jpmitaka.tokyo.jpjpICANN2026-08-17TRUE{"A":["160.251.151.144"],"MX":[{"host":"mx1.suiren.mitaka.tokyo.jp","priority":10}],"NS":["ns1.value-domain.com","ns2.value-domain.com"],"SOA":{"mname":"ns1.value-domain.com","retry":900,"rname":"hostmaster.suiren.mitaka.tokyo.jp","expire":604800,"serial":2020082619,"minimum":120,"refresh":3600}}
hyc.mitaka.tokyo.jpmitaka.tokyo.jpjpICANN2026-08-13TRUE{"A":["153.122.205.45"],"MX":[{"host":"mx.hyc.mitaka.tokyo.jp","priority":100}],"NS":["ns1.shsvr.net","ns2.shsvr.net"],"SOA":{"mname":"ns1.shsvr.net","retry":1800,"rname":"root.shsvr.net","expire":259200,"serial":2698662687,"minimum":1800,"refresh":10800},"TXT":["v=spf1 include:_spf.shared-server.net ~all"]}
mitaka.tokyo.jpmitaka.tokyo.jpjpICANN2026-08-16TRUE{"TXT":["mitaka.tokyo.jp."]}
DomainRDAP/WHOIS last data checkedRDAP/WHOIS methodDomain creation dateDomain expiration dateDomain last changedRegistrarRDAP/WHOIS RecordResponse Status RDAP/WHOIS
city.mitaka.tokyo.jp2026-08-18WHOIS2026-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\na. [Domain Name] CITY.MITAKA.TOKYO.JP\r\ng. [Organization] MITAKA CITY\r\nl. [Organization Type] Local government\r\nm. [Administrative Contact] KS67729JP\r\nn. [Technical Contact] NM26928JP\r\np. [Name Server] ns-209.awsdns-26.com\r\np. [Name Server] ns-1548.awsdns-01.co.uk\r\np. [Name Server] ns-891.awsdns-47.net\r\np. [Name Server] ns-1511.awsdns-60.org\r\ns. [Signing Key] \r\n[State] Connected (2027/03/31)\r\n[Registered Date] 1997/03/19\r\n[Connected Date] 1997/04/23\r\n[Last Update] 2026/04/01 01:02:43 (JST)"}Domain is active
library.mitaka.tokyo.jp2026-08-17WHOIS2025-11-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] LIBRARY.MITAKA.TOKYO.JP\r\ng. [Organization] MITAKA CITY LIBRARY\r\nl. [Organization Type] Local Public Body\r\nm. [Administrative Contact] HT42260JP\r\nn. [Technical Contact] KO9785JP\r\np. [Name Server] ns.library.mitaka.tokyo.jp\r\np. [Name Server] ns-tk011.ocn.ad.jp\r\ns. [Signing Key] \r\n[State] Connected (2026/10/31)\r\n[Registered Date] 2007/10/24\r\n[Connected Date] 2007/11/05\r\n[Last Update] 2025/11/01 01:03:57 (JST)"}Domain is active
suiren.mitaka.tokyo.jp2026-08-09WHOIS2026-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\na. [Domain Name] SUIREN.MITAKA.TOKYO.JP\r\ng. [Organization] Mitaka Swimming Association\r\nl. [Organization Type] Group\r\nm. [Administrative Contact] YD114JP\r\nn. [Technical Contact] YD114JP\r\np. [Name Server] ns1.value-domain.com\r\np. [Name Server] ns2.value-domain.com\r\np. [Name Server] ns3.value-domain.com\r\ns. [Signing Key] \r\n[State] Connected (2027/05/31)\r\n[Registered Date] 2000/05/12\r\n[Connected Date] 2000/05/15\r\n[Last Update] 2026/06/01 01:01:04 (JST)"}Domain is active
hyc.mitaka.tokyo.jp2026-08-08WHOIS2025-09-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] HYC.MITAKA.TOKYO.JP\r\ng. [Organization] HYC CO.,LTD\r\nl. [Organization Type] Corporation\r\nm. [Administrative Contact] HY10519JP\r\nn. [Technical Contact] HY10519JP\r\np. [Name Server] ns1.shsvr.net\r\np. [Name Server] ns2.shsvr.net\r\ns. [Signing Key] \r\n[State] Connected (2026/08/31)\r\n[Registered Date] 2011/08/04\r\n[Connected Date] 2011/08/04\r\n[Last Update] 2025/09/01 01:04:33 (JST)"}Domain is active
mitaka.tokyo.jp2026-08-09WHOIS2012-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] MITAKA.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:42:16 (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
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
city.mitaka.tokyo.jpmitaka.tokyo.jpjpICANNHTTP 02026-07-27Apple iCloud Mail, Amazon Web Services2026-08-07TRUE{"NS":["ns-1511.awsdns-60.org","ns-1548.awsdns-01.co.uk","ns-209.awsdns-26.com","ns-891.awsdns-47.net"],"SOA":{"mname":"ns-1511.awsdns-60.org","retry":1800,"rname":"awsdns-hostmaster.amazon.com","expire":3600000,"serial":2022101401,"minimum":900,"refresh":3600},"TXT":["apple-domain-verification=JDfBy2sFY1kJP2r1"]}0.00000007543314,204,6922026-08-18WHOIS2026-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\na. [Domain Name] CITY.MITAKA.TOKYO.JP\r\ng. [Organization] MITAKA CITY\r\nl. [Organization Type] Local government\r\nm. [Administrative Contact] KS67729JP\r\nn. [Technical Contact] NM26928JP\r\np. [Name Server] ns-209.awsdns-26.com\r\np. [Name Server] ns-1548.awsdns-01.co.uk\r\np. [Name Server] ns-891.awsdns-47.net\r\np. [Name Server] ns-1511.awsdns-60.org\r\ns. [Signing Key] \r\n[State] Connected (2027/03/31)\r\n[Registered Date] 1997/03/19\r\n[Connected Date] 1997/04/23\r\n[Last Update] 2026/04/01 01:02:43 (JST)"}Domain is active
library.mitaka.tokyo.jpmitaka.tokyo.jpjpICANNHTTP 3022026-08-08Java, Apache HTTP Server2026-08-08TRUE{"MX":[{"host":"mtk-lib.in.tmems-jp.trendmicro.com","priority":10}],"NS":["ns-tk011.ocn.ad.jp","ns.library.mitaka.tokyo.jp"],"SOA":{"mname":"ns.library.mitaka.tokyo.jp","retry":3600,"rname":"admin.library.mitaka.tokyo.jp","expire":604800,"serial":2025091601,"minimum":300,"refresh":10800},"TXT":["trend-micro-v1-domain-verification.2fd985fa556d5576d07e05c682f8707c=3c39c175-07e3-4f44-84b1-f744a2d04aca","v=spf1 ip4:122.1.10.250 include:spf.tmems-jp.trendmicro.com ~all"]}0.000000014700913,643,8162026-08-17WHOIS2025-11-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] LIBRARY.MITAKA.TOKYO.JP\r\ng. [Organization] MITAKA CITY LIBRARY\r\nl. [Organization Type] Local Public Body\r\nm. [Administrative Contact] HT42260JP\r\nn. [Technical Contact] KO9785JP\r\np. [Name Server] ns.library.mitaka.tokyo.jp\r\np. [Name Server] ns-tk011.ocn.ad.jp\r\ns. [Signing Key] \r\n[State] Connected (2026/10/31)\r\n[Registered Date] 2007/10/24\r\n[Connected Date] 2007/11/05\r\n[Last Update] 2025/11/01 01:03:57 (JST)"}Domain is active
suiren.mitaka.tokyo.jpmitaka.tokyo.jpjpICANNHTTP 200160.251.151.144JP2026-07-08HSTS, HTTP/2, Apache HTTP Server2026-08-17TRUE{"A":["160.251.151.144"],"MX":[{"host":"mx1.suiren.mitaka.tokyo.jp","priority":10}],"NS":["ns1.value-domain.com","ns2.value-domain.com"],"SOA":{"mname":"ns1.value-domain.com","retry":900,"rname":"hostmaster.suiren.mitaka.tokyo.jp","expire":604800,"serial":2020082619,"minimum":120,"refresh":3600}}0.000000004386639,549,7562026-08-09WHOIS2026-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\na. [Domain Name] SUIREN.MITAKA.TOKYO.JP\r\ng. [Organization] Mitaka Swimming Association\r\nl. [Organization Type] Group\r\nm. [Administrative Contact] YD114JP\r\nn. [Technical Contact] YD114JP\r\np. [Name Server] ns1.value-domain.com\r\np. [Name Server] ns2.value-domain.com\r\np. [Name Server] ns3.value-domain.com\r\ns. [Signing Key] \r\n[State] Connected (2027/05/31)\r\n[Registered Date] 2000/05/12\r\n[Connected Date] 2000/05/15\r\n[Last Update] 2026/06/01 01:01:04 (JST)"}Domain is active
hyc.mitaka.tokyo.jpmitaka.tokyo.jpjpICANNHTTP 403153.122.205.45JP2026-08-052026-08-13TRUE{"A":["153.122.205.45"],"MX":[{"host":"mx.hyc.mitaka.tokyo.jp","priority":100}],"NS":["ns1.shsvr.net","ns2.shsvr.net"],"SOA":{"mname":"ns1.shsvr.net","retry":1800,"rname":"root.shsvr.net","expire":259200,"serial":2698662687,"minimum":1800,"refresh":10800},"TXT":["v=spf1 include:_spf.shared-server.net ~all"]}0.0000000041156510,471,8682026-08-08WHOIS2025-09-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] HYC.MITAKA.TOKYO.JP\r\ng. [Organization] HYC CO.,LTD\r\nl. [Organization Type] Corporation\r\nm. [Administrative Contact] HY10519JP\r\nn. [Technical Contact] HY10519JP\r\np. [Name Server] ns1.shsvr.net\r\np. [Name Server] ns2.shsvr.net\r\ns. [Signing Key] \r\n[State] Connected (2026/08/31)\r\n[Registered Date] 2011/08/04\r\n[Connected Date] 2011/08/04\r\n[Last Update] 2025/09/01 01:04:33 (JST)"}Domain is active
mitaka.tokyo.jpmitaka.tokyo.jpjpICANNHTTP 02026-08-122026-08-16TRUE{"TXT":["mitaka.tokyo.jp."]}002026-08-09WHOIS2012-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] MITAKA.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:42:16 (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
A mostrar 5 de 5 linhas · All active domains · Cada domínio ativo com o seu TLD e tipo de domínio.

O dataset .mitaka.tokyo.jp

Tudo o que temos sobre 5 domínios .mitaka.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 .mitaka.tokyo.jp

O fragmento completo de .mitaka.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 .mitaka.tokyo.jp

A lista completa de domínios .mitaka.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 .mitaka.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 .mitaka.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 .mitaka.tokyo.jp existem?

webatla regista 5 domínios .mitaka.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 .mitaka.tokyo.jp?

Sim, a lista completa de .mitaka.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 .mitaka.tokyo.jp?

Escolha um dataset, e a lista completa de .mitaka.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 .mitaka.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 .mitaka.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 .mitaka.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.