Descarregar lista completa de domínios .inagi.tokyo.jp

Name: All .inagi.tokyo.jp domains
Creator: webatla
License: https://webatla.com/terms

Sobre .inagi.tokyo.jp Pré-visualização da base de dados Descarregar

Sobre .inagi.tokyo.jp

.inagi.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.inagi.tokyo.jp

TLD superior.jp

RegistoJapan Registry Services Co., Ltd. (JPRS)

Domínios6

Todos os números à data de 18/08/2026

Novos registos de domínio

— semana passada

— mês passado

Domínios ativos

6

domínios registados e ativos na zona .inagi.tokyo.jp

Sites ativos

2

sites ativos na zona .inagi.tokyo.jp

DNS

6

domínios com registos DNS

Países

1

países representados (por IP de alojamento)

RDAP & WHOIS

6

domínios com registos RDAP e WHOIS

Pré-visualização da base de dados de domínios .inagi.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-inagi-tokyo-jp-all-2026-08-18.jsonl.zst · 6 linhas · 23 colunas Exportação diária atualizada

Domain	TLD suffix	TLD	Domain type
city.inagi.tokyo.jp	inagi.tokyo.jp	jp	ICANN
hospital.inagi.tokyo.jp	inagi.tokyo.jp	jp	ICANN
iplaza.inagi.tokyo.jp	inagi.tokyo.jp	jp	ICANN
library.inagi.tokyo.jp	inagi.tokyo.jp	jp	ICANN
neo-system.inagi.tokyo.jp	inagi.tokyo.jp	jp	ICANN
…	…	…	…

Domain	TLD suffix	TLD	Domain type	Country by IP	PR value	Harmonic value	Domain creation date	Domain expiration date
city.inagi.tokyo.jp	inagi.tokyo.jp	jp	ICANN	—	0.000000149248	14,148,189	—	—
hospital.inagi.tokyo.jp	inagi.tokyo.jp	jp	ICANN	JP	0.0000000208014	12,495,911	—	—
iplaza.inagi.tokyo.jp	inagi.tokyo.jp	jp	ICANN	JP	0.0000000188277	13,751,103	—	—
library.inagi.tokyo.jp	inagi.tokyo.jp	jp	ICANN	—	0.0000000116518	13,999,146	—	—
neo-system.inagi.tokyo.jp	inagi.tokyo.jp	jp	ICANN	—	0.00000000421688	9,557,899	—	—
…	…	…	…	…	…	…	…	…

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.inagi.tokyo.jp	inagi.tokyo.jp	jp	ICANN	HTTP 200	—	—	{"youtube":["https://youtube.com/channel/UC8HpK1asxbTtFVt_Yyeu5mA"],"facebook":["https://facebook.com/profile.php?id=61586200166915"]}	2026-07-27	HSTS, HTTP/2, jQuery 3.5.1, Favicon, Open Graph, Google Font API, Google Analytics GA4, Amazon CloudFront, Amazon Web Services, Google Site Verification	0.000000149248	14,148,189	—	—
hospital.inagi.tokyo.jp	inagi.tokyo.jp	jp	ICANN	HTTP 0	194.91.0.197	JP	—	2026-08-05	—	0.0000000208014	12,495,911	—	—
iplaza.inagi.tokyo.jp	inagi.tokyo.jp	jp	ICANN	HTTP 0	60.43.147.252	JP	—	2026-08-06	—	0.0000000188277	13,751,103	—	—
library.inagi.tokyo.jp	inagi.tokyo.jp	jp	ICANN	HTTP 200	—	—	{"facebook":["https://facebook.com/inagilib.tokyo.jp"],"x-twitter":["https://twitter.com/Inagilib"]}	2026-08-08	HSTS, Slick, jQuery, DigiCert, Google Font API, Google Analytics GA4, Apache HTTP Server, Google Site Verification	0.0000000116518	13,999,146	—	—
neo-system.inagi.tokyo.jp	inagi.tokyo.jp	jp	ICANN	HTTP 200	—	—	{"facebook":["https://facebook.com/MSPOENTRY"]}	2026-08-13	PHP, HSTS, MySQL, jQuery, Favicon, Sectigo, WordPress, Open Graph, jQuery Migrate 1.4.1, Google Analytics	0.00000000421688	9,557,899	—	—
…	…	…	…	…	…	…	…	…	…	…	…	…	…

Domain	TLD suffix	TLD	Domain type	DNS last data checked	DNS Status	DNS records
city.inagi.tokyo.jp	inagi.tokyo.jp	jp	ICANN	2026-08-07	TRUE	{"MX":[{"host":"mailgw.city.inagi.lg.jp","priority":1}],"NS":["ns.center.web.ad.jp","ns.city.inagi.lg.jp","ns.city.inagi.tokyo.jp"],"SOA":{"mname":"ns.city.inagi.lg.jp","retry":900,"rname":"root.ns.city.inagi.lg.jp","expire":604800,"serial":2022122601,"minimum":86400,"refresh":10800}}
hospital.inagi.tokyo.jp	inagi.tokyo.jp	jp	ICANN	2026-08-10	TRUE	{"A":["194.91.0.197"],"MX":[{"host":"vlmx-air.secure.ne.jp","priority":10}],"NS":["ns4.cpi.ad.jp","ns5.cpi.ad.jp"],"SOA":{"mname":"ns4.cpi.ad.jp","retry":900,"rname":"hostmaster.cpi.ad.jp","expire":3600000,"serial":2024032501,"minimum":3600,"refresh":3600},"TXT":["v=spf1 include:spf2.secure.ne.jp -all"]}
iplaza.inagi.tokyo.jp	inagi.tokyo.jp	jp	ICANN	2026-08-09	TRUE	{"A":["60.43.147.252"],"MX":[{"host":"mwbgw1.ocn.ad.jp","priority":10},{"host":"mwbgw2.ocn.ad.jp","priority":10}],"NS":["mwns1.customer.ne.jp","mwns2.customer.ne.jp"],"SOA":{"mname":"mwns1.customer.ne.jp","retry":1800,"rname":"host-plan-ac.ntt.com","expire":3628800,"serial":1613914488,"minimum":3600,"refresh":3600},"TXT":["v=spf1 a include:_spf.bizmw.com ~all"]}
library.inagi.tokyo.jp	inagi.tokyo.jp	jp	ICANN	2026-08-16	TRUE	{"MX":[{"host":"mail.library.inagi.tokyo.jp","priority":10}],"NS":["ns-kg022.ocn.ad.jp","ns1.library.inagi.tokyo.jp"],"SOA":{"mname":"ns1.library.inagi.tokyo.jp","retry":1800,"rname":"postmaster.library.inagi.tokyo.jp","expire":1209600,"serial":2026062901,"minimum":3600,"refresh":7200},"TXT":["google-site-verification=7WVRTjjBOn4EdnIpTV0kEdC86pLrR85ExGTB12viMWQ","v=spf1 ip4:153.231.196.114 -all"]}
neo-system.inagi.tokyo.jp	inagi.tokyo.jp	jp	ICANN	2026-08-07	TRUE	{"MX":[{"host":"alpha.neo-system.jp","priority":10}],"NS":["alpha.neo-system.jp","neodb.neo-system.jp"],"SOA":{"mname":"alpha.neo-system.jp","retry":3600,"rname":"bind-admin.neo-system.jp","expire":604800,"serial":2024041001,"minimum":86400,"refresh":10800},"TXT":["v=spf1 +ip4:211.133.244.18 +ip4:121.119.167.65 +ip4:153.231.197.56/29 +ip4:202.33.12.144/29 ~all"]}
…	…	…	…	…	…	…

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.inagi.tokyo.jp	2026-08-17	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.INAGI.TOKYO.JP\r\ng. [Organization] INAGI CITY\r\nl. [Organization Type] Local Public body\r\nm. [Administrative Contact] KN42330JP\r\nn. [Technical Contact] ST41342JP\r\np. [Name Server] ns.center.web.ad.jp\r\np. [Name Server] ns.city.inagi.tokyo.jp\r\ns. [Signing Key] \r\n[State] Connected (2026/09/30)\r\n[Registered Date] 2000/09/26\r\n[Connected Date] 2000/11/22\r\n[Last Update] 2025/10/01 01:00:41 (JST)"}	Domain is active
hospital.inagi.tokyo.jp	2026-08-09	WHOIS	—	—	2026-08-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] HOSPITAL.INAGI.TOKYO.JP\r\ng. [Organization] Inagi municpal hospital\r\nl. [Organization Type] Hospital\r\nm. [Administrative Contact] MK2943JP\r\nn. [Technical Contact] MY61887JP\r\np. [Name Server] ns4.cpi.ad.jp\r\np. [Name Server] ns5.cpi.ad.jp\r\ns. [Signing Key] \r\n[State] Connected (2027/07/31)\r\n[Registered Date] 1999/07/21\r\n[Connected Date] 1999/07/22\r\n[Last Update] 2026/08/01 01:03:26 (JST)"}	Domain is active
iplaza.inagi.tokyo.jp	2026-08-09	WHOIS	—	—	2026-08-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] IPLAZA.INAGI.TOKYO.JP\r\ng. [Organization] INAGI CULTURE CENTER SERVICE CORPORATION\r\nl. [Organization Type] Unlimited Partnership\r\nm. [Administrative Contact] SH7448JP\r\nn. [Technical Contact] KN13668JP\r\np. [Name Server] mwns1.customer.ne.jp\r\np. [Name Server] mwns2.customer.ne.jp\r\ns. [Signing Key] \r\n[State] Connected (2027/07/31)\r\n[Registered Date] 2009/07/10\r\n[Connected Date] 2009/07/21\r\n[Last Update] 2026/08/01 01:05:25 (JST)"}	Domain is active
library.inagi.tokyo.jp	2026-08-18	WHOIS	—	—	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\na. [Domain Name] LIBRARY.INAGI.TOKYO.JP\r\ng. [Organization] INAGI PUBLIC LIBRARY\r\nl. [Organization Type] Local Public Body\r\nm. [Administrative Contact] MI28949JP\r\nn. [Technical Contact] DM8590JP\r\np. [Name Server] ns-kg022.ocn.ad.jp\r\np. [Name Server] ns1.library.inagi.tokyo.jp\r\ns. [Signing Key] \r\n[State] Connected (2027/03/31)\r\n[Registered Date] 2006/03/17\r\n[Connected Date] 2006/03/30\r\n[Last Update] 2026/04/01 01:04:34 (JST)"}	Domain is active
neo-system.inagi.tokyo.jp	2026-08-11	WHOIS	—	—	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\na. [Domain Name] NEO-SYSTEM.INAGI.TOKYO.JP\r\ng. [Organization] Neosystem (Kiyomoto, Naoshi)\r\nl. [Organization Type] Person\r\nm. [Administrative Contact] NK123JP\r\nn. [Technical Contact] KS1475JP\r\np. [Name Server] alpha.neo-system.inagi.tokyo.jp\r\np. [Name Server] alpha.neo-system.jp\r\np. [Name Server] neodb.neo-system.jp\r\ns. [Signing Key] \r\n[State] Connected (2027/05/31)\r\n[Registered Date] 1996/05/13\r\n[Connected Date] 1996/05/20\r\n[Last Update] 2026/06/01 01:00:39 (JST)"}	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.inagi.tokyo.jp	inagi.tokyo.jp	jp	ICANN	HTTP 200	—	—	{"youtube":["https://youtube.com/channel/UC8HpK1asxbTtFVt_Yyeu5mA"],"facebook":["https://facebook.com/profile.php?id=61586200166915"]}	2026-07-27	HSTS, HTTP/2, jQuery 3.5.1, Favicon, Open Graph, Google Font API, Google Analytics GA4, Amazon CloudFront, Amazon Web Services, Google Site Verification	2026-08-07	TRUE	{"MX":[{"host":"mailgw.city.inagi.lg.jp","priority":1}],"NS":["ns.center.web.ad.jp","ns.city.inagi.lg.jp","ns.city.inagi.tokyo.jp"],"SOA":{"mname":"ns.city.inagi.lg.jp","retry":900,"rname":"root.ns.city.inagi.lg.jp","expire":604800,"serial":2022122601,"minimum":86400,"refresh":10800}}	0.000000149248	14,148,189	2026-08-17	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.INAGI.TOKYO.JP\r\ng. [Organization] INAGI CITY\r\nl. [Organization Type] Local Public body\r\nm. [Administrative Contact] KN42330JP\r\nn. [Technical Contact] ST41342JP\r\np. [Name Server] ns.center.web.ad.jp\r\np. [Name Server] ns.city.inagi.tokyo.jp\r\ns. [Signing Key] \r\n[State] Connected (2026/09/30)\r\n[Registered Date] 2000/09/26\r\n[Connected Date] 2000/11/22\r\n[Last Update] 2025/10/01 01:00:41 (JST)"}	Domain is active
hospital.inagi.tokyo.jp	inagi.tokyo.jp	jp	ICANN	HTTP 0	194.91.0.197	JP	—	2026-08-05	—	2026-08-10	TRUE	{"A":["194.91.0.197"],"MX":[{"host":"vlmx-air.secure.ne.jp","priority":10}],"NS":["ns4.cpi.ad.jp","ns5.cpi.ad.jp"],"SOA":{"mname":"ns4.cpi.ad.jp","retry":900,"rname":"hostmaster.cpi.ad.jp","expire":3600000,"serial":2024032501,"minimum":3600,"refresh":3600},"TXT":["v=spf1 include:spf2.secure.ne.jp -all"]}	0.0000000208014	12,495,911	2026-08-09	WHOIS	—	—	2026-08-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] HOSPITAL.INAGI.TOKYO.JP\r\ng. [Organization] Inagi municpal hospital\r\nl. [Organization Type] Hospital\r\nm. [Administrative Contact] MK2943JP\r\nn. [Technical Contact] MY61887JP\r\np. [Name Server] ns4.cpi.ad.jp\r\np. [Name Server] ns5.cpi.ad.jp\r\ns. [Signing Key] \r\n[State] Connected (2027/07/31)\r\n[Registered Date] 1999/07/21\r\n[Connected Date] 1999/07/22\r\n[Last Update] 2026/08/01 01:03:26 (JST)"}	Domain is active
iplaza.inagi.tokyo.jp	inagi.tokyo.jp	jp	ICANN	HTTP 0	60.43.147.252	JP	—	2026-08-06	—	2026-08-09	TRUE	{"A":["60.43.147.252"],"MX":[{"host":"mwbgw1.ocn.ad.jp","priority":10},{"host":"mwbgw2.ocn.ad.jp","priority":10}],"NS":["mwns1.customer.ne.jp","mwns2.customer.ne.jp"],"SOA":{"mname":"mwns1.customer.ne.jp","retry":1800,"rname":"host-plan-ac.ntt.com","expire":3628800,"serial":1613914488,"minimum":3600,"refresh":3600},"TXT":["v=spf1 a include:_spf.bizmw.com ~all"]}	0.0000000188277	13,751,103	2026-08-09	WHOIS	—	—	2026-08-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] IPLAZA.INAGI.TOKYO.JP\r\ng. [Organization] INAGI CULTURE CENTER SERVICE CORPORATION\r\nl. [Organization Type] Unlimited Partnership\r\nm. [Administrative Contact] SH7448JP\r\nn. [Technical Contact] KN13668JP\r\np. [Name Server] mwns1.customer.ne.jp\r\np. [Name Server] mwns2.customer.ne.jp\r\ns. [Signing Key] \r\n[State] Connected (2027/07/31)\r\n[Registered Date] 2009/07/10\r\n[Connected Date] 2009/07/21\r\n[Last Update] 2026/08/01 01:05:25 (JST)"}	Domain is active
library.inagi.tokyo.jp	inagi.tokyo.jp	jp	ICANN	HTTP 200	—	—	{"facebook":["https://facebook.com/inagilib.tokyo.jp"],"x-twitter":["https://twitter.com/Inagilib"]}	2026-08-08	HSTS, Slick, jQuery, DigiCert, Google Font API, Google Analytics GA4, Apache HTTP Server, Google Site Verification	2026-08-16	TRUE	{"MX":[{"host":"mail.library.inagi.tokyo.jp","priority":10}],"NS":["ns-kg022.ocn.ad.jp","ns1.library.inagi.tokyo.jp"],"SOA":{"mname":"ns1.library.inagi.tokyo.jp","retry":1800,"rname":"postmaster.library.inagi.tokyo.jp","expire":1209600,"serial":2026062901,"minimum":3600,"refresh":7200},"TXT":["google-site-verification=7WVRTjjBOn4EdnIpTV0kEdC86pLrR85ExGTB12viMWQ","v=spf1 ip4:153.231.196.114 -all"]}	0.0000000116518	13,999,146	2026-08-18	WHOIS	—	—	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\na. [Domain Name] LIBRARY.INAGI.TOKYO.JP\r\ng. [Organization] INAGI PUBLIC LIBRARY\r\nl. [Organization Type] Local Public Body\r\nm. [Administrative Contact] MI28949JP\r\nn. [Technical Contact] DM8590JP\r\np. [Name Server] ns-kg022.ocn.ad.jp\r\np. [Name Server] ns1.library.inagi.tokyo.jp\r\ns. [Signing Key] \r\n[State] Connected (2027/03/31)\r\n[Registered Date] 2006/03/17\r\n[Connected Date] 2006/03/30\r\n[Last Update] 2026/04/01 01:04:34 (JST)"}	Domain is active
neo-system.inagi.tokyo.jp	inagi.tokyo.jp	jp	ICANN	HTTP 200	—	—	{"facebook":["https://facebook.com/MSPOENTRY"]}	2026-08-13	PHP, HSTS, MySQL, jQuery, Favicon, Sectigo, WordPress, Open Graph, jQuery Migrate 1.4.1, Google Analytics	2026-08-07	TRUE	{"MX":[{"host":"alpha.neo-system.jp","priority":10}],"NS":["alpha.neo-system.jp","neodb.neo-system.jp"],"SOA":{"mname":"alpha.neo-system.jp","retry":3600,"rname":"bind-admin.neo-system.jp","expire":604800,"serial":2024041001,"minimum":86400,"refresh":10800},"TXT":["v=spf1 +ip4:211.133.244.18 +ip4:121.119.167.65 +ip4:153.231.197.56/29 +ip4:202.33.12.144/29 ~all"]}	0.00000000421688	9,557,899	2026-08-11	WHOIS	—	—	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\na. [Domain Name] NEO-SYSTEM.INAGI.TOKYO.JP\r\ng. [Organization] Neosystem (Kiyomoto, Naoshi)\r\nl. [Organization Type] Person\r\nm. [Administrative Contact] NK123JP\r\nn. [Technical Contact] KS1475JP\r\np. [Name Server] alpha.neo-system.inagi.tokyo.jp\r\np. [Name Server] alpha.neo-system.jp\r\np. [Name Server] neodb.neo-system.jp\r\ns. [Signing Key] \r\n[State] Connected (2027/05/31)\r\n[Registered Date] 1996/05/13\r\n[Connected Date] 1996/05/20\r\n[Last Update] 2026/06/01 01:00:39 (JST)"}	Domain is active
…	…	…	…	…	…	…	…	…	…	…	…	…	…	…	…	…	…	…	…	…	…	…

A mostrar 5 de 6 linhas · All active domains · Cada domínio ativo com o seu TLD e tipo de domínio.

↓ Transferir pré-visualização (20 linhas, grátis) Comprar All active domains — €29 / mês

Como descarregar a lista de domínios .inagi.tokyo.jp

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

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

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

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