0 last week
0 last month
83 active domains
79 domains with DNS records
Domains from 4 countries
83 domains with RDAP and WHOIS records
Includes 59 unique IPs hosting active domains
A metric that estimates network influence and trust, based on the link structure of domains using .toyama.jp TLD
The average PageRank score reflecting the SEO authority of websites with the .toyama.jp TLD
| TLD | Domain | TLD suffix | Country | IP address | Technologies | PR value | Harmonic value | Detected hosts count | DNS last data checked | DNS Status | DNS records | RDAP/WHOIS last data checked | RDAP/WHOIS method | Domain creation date | Domain expiration date | Domain last changed | Registrar | RDAP/WHOIS Record |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| jp | levo.toyama.jp | toyama.jp | Japan (JP) | 157.112.152.14 | ["Google Tag Manager", "NGINX"] | 0.00000001675 | 12,916,908.00 | 2026/05/20 | 1 | {"A": ["157.112.152.14"], "MX": [{"ho... | 2026/05/23 | WHOIS | 2014/04/17 | 2027/04/30 | 2026/05/01 | {"raw_response": ... | ||
| jp | sancoh.toyama.jp | toyama.jp | Japan (JP) | 162.43.94.167 | ["Google Tag Manager", "WordPress", "... | 0.00000000937 | 12,640,159.00 | 2026/05/20 | 1 | {"A": ["162.43.94.167"], "MX": [{"hos... | 2025/09/16 | WHOIS | 2018/07/06 | 2026/07/31 | 2025/08/01 | Yoshitaka Inanami | {"raw_response": ... | |
| jp | kibounosato.toyama.jp | toyama.jp | Japan (JP) | 162.43.116.61 | ["Google Tag Manager", "NGINX"] | 0.00000000894 | 12,572,742.00 | 2026/05/29 | 1 | {"A": ["162.43.116.61"], "MX": [{"hos... | 2026/05/22 | WHOIS | 2014/05/16 | 2026/05/31 | 2025/06/01 | Nakayamakai Medical Corporation | {"raw_response": ... | |
| jp | papamaru.toyama.jp | toyama.jp | Japan (JP) | 162.43.24.61 | ["Google Tag Manager", "Apache HTTP S... | 0.00000000754 | 12,514,384.00 | 2026/05/19 | 1 | {"A": ["162.43.24.61"], "MX": [{"host... | 2025/09/08 | WHOIS | 2016/08/09 | 2026/08/31 | 2025/09/01 | tanii futoshi | {"raw_response": ... | |
| jp | ikiiki.toyama.jp | toyama.jp | Japan (JP) | 162.43.116.61 | ["Google Tag Manager", "WordPress", "... | 0.00000000715 | 9,823,999.00 | 2026/05/19 | 1 | {"A": ["162.43.116.61"], "MX": [{"hos... | 2025/07/13 | WHOIS | 2022/06/24 | 2026/06/30 | 2025/07/01 | Nakayamakai Medical Corporation | {"raw_response": ... | |
| jp | machinodenkiya.toyama.jp | toyama.jp | Japan (JP) | 157.7.189.135 | ["Apache HTTP Server"] | 0.00000000713 | 9,804,482.00 | 2026/05/19 | 1 | {"A": ["157.7.189.135"], "MX": [{"hos... | 2026/03/12 | WHOIS | 2018/02/05 | 2027/02/28 | 2026/03/01 | (Not displayed by registrant's request) | {"raw_response": ... | |
| jp | akanekai.toyama.jp | toyama.jp | United States (US) | 34.111.141.225 | ["Google Tag Manager", "Nuxt.js"] | 0.00000000610 | 9,922,009.00 | 2026/05/22 | 1 | {"A": ["34.111.141.225"], "MX": [{"ho... | 2025/12/07 | WHOIS | 2013/11/21 | 2026/11/30 | 2025/12/01 | Xserver Inc. | {"raw_response": ... | |
| jp | kodomo-wakamono.toyama.jp | toyama.jp | Japan (JP) | 162.43.9.216 | ["Google Tag Manager", "Apache HTTP S... | 0.00000000534 | 12,256,251.00 | 2026/05/19 | 1 | {"A": ["162.43.9.216"], "MX": [{"host... | 2025/07/11 | WHOIS | 2020/06/10 | 2026/06/30 | 2025/07/01 | futoshi tanii | {"raw_response": ... | |
| jp | pc119.toyama.jp | toyama.jp | United States (US) | 104.244.98.109 | ["Google Tag Manager", "NGINX", "Face... | 0.00000000528 | 12,688,502.00 | 2026/05/18 | 1 | {"A": ["104.244.98.109"], "MX": [{"ho... | 2025/11/04 | WHOIS | 2013/10/18 | 2026/10/31 | 2025/11/01 | Hideki Shimizu | {"raw_response": ... | |
| jp | kizuna.toyama.jp | toyama.jp | Japan (JP) | 162.43.116.61 | ["NGINX"] | 0.00000000495 | 9,709,218.00 | 2026/05/21 | 1 | {"A": ["162.43.116.61"], "MX": [{"hos... | 2026/04/30 | WHOIS | 2023/03/27 | 2027/03/31 | 2026/04/01 | {"raw_response": ... | ||
| jp | neurosurgery.toyama.jp | toyama.jp | Japan (JP) | 183.181.79.96 | ["WordPress", "NGINX"] | 0.00000000488 | 12,268,382.00 | 2026/05/25 | 1 | {"A": ["183.181.79.96"], "MX": [{"hos... | 2026/05/22 | WHOIS | 2019/05/20 | 2026/05/31 | 2025/06/01 | Department of Neurosurgery, Faculty o... | {"raw_response": ... | |
| jp | swim.toyama.jp | toyama.jp | Japan (JP) | 120.136.10.49 | ["WordPress", "NGINX"] | 0.00000000481 | 12,138,143.00 | 2026/05/24 | 1 | {"A": ["120.136.10.49"], "MX": [{"hos... | 2025/12/07 | WHOIS | 2012/11/18 | 2026/11/30 | 2025/12/01 | toyama swimming federation | {"raw_response": ... | |
| jp | atom.toyama.jp | toyama.jp | Japan (JP) | 202.253.106.137 | ["Apache HTTP Server"] | 0.00000000460 | 12,255,368.00 | 2026/05/24 | 1 | {"A": ["202.253.106.137"], "MX": [{"h... | 2026/03/12 | WHOIS | {"raw_response": ... | |||||
| jp | onkyo.toyama.jp | toyama.jp | Japan (JP) | 183.90.238.16 | ["Google Tag Manager", "WordPress", "... | 0.00000000454 | 14,291,652.00 | 2026/05/19 | 1 | {"A": ["183.90.238.16"], "MX": [{"hos... | 2026/05/22 | WHOIS | 2017/05/22 | 2026/05/31 | 2025/06/01 | {"raw_response": ... | ||
| jp | hosho.toyama.jp | toyama.jp | Japan (JP) | 60.43.238.62 | ["Apache HTTP Server", "WordPress", "... | 0.00000000448 | 12,509,264.00 | 2026/05/27 | 1 | {"A": ["60.43.238.62"], "MX": [{"host... | 2025/11/04 | WHOIS | 2013/10/16 | 2026/10/31 | 2025/11/01 | Masuyama,Masaki | {"raw_response": ... | |
| jp | iwase.toyama.jp | toyama.jp | Japan (JP) | 183.90.238.16 | ["Google Tag Manager", "WordPress", "... | 0.00000000442 | 12,499,104.00 | 2026/05/20 | 1 | {"A": ["183.90.238.16"], "MX": [{"hos... | 2025/12/31 | WHOIS | 2017/09/22 | 2026/09/30 | 2025/10/01 | Shoji Baba | {"raw_response": ... | |
| jp | shoryu.toyama.jp | toyama.jp | Japan (JP) | 157.112.152.38 | ["NGINX"] | 0.00000000440 | 12,542,450.00 | 2026/05/20 | 1 | {"A": ["157.112.152.38"], "MX": [{"ho... | 2025/11/04 | WHOIS | 2016/10/29 | 2026/10/31 | 2025/11/01 | kyohei shibano | {"raw_response": ... | |
| jp | karuta.toyama.jp | toyama.jp | Japan (JP) | 49.212.180.145 | ["adyen", "NGINX"] | 0.00000000439 | 12,138,708.00 | 2026/05/28 | 1 | {"A": ["49.212.180.145"], "MX": [{"ho... | 2025/12/07 | WHOIS | 2012/11/18 | 2026/11/30 | 2025/12/01 | Toyama Karuta Assoc. | {"raw_response": ... | |
| jp | gachok.toyama.jp | toyama.jp | Japan (JP) | 157.7.107.39 | ["Google Tag Manager", "Apache HTTP S... | 0.00000000435 | 9,639,217.00 | 2026/05/21 | 1 | {"A": ["157.7.107.39"], "MX": [{"host... | 2025/11/08 | WHOIS | 2017/10/17 | 2026/10/31 | 2025/11/01 | GACHOK | {"raw_response": ... | |
| jp | medicalcare.toyama.jp | toyama.jp | Japan (JP) | 118.27.122.181 | ["Envoy Proxy", "Pepyaka", "NGINX", "... | 0.00000000428 | 10,863,720.00 | 2026/05/25 | 1 | {"A": ["118.27.122.181", "185.230.63.... | 2025/09/08 | WHOIS | 2021/07/02 | 2026/07/31 | 2025/08/01 | (Not displayed by registrant's request) | {"raw_response": ... | |
| jp | moriy.toyama.jp | toyama.jp | Japan (JP) | 163.44.185.164 | ["Apache HTTP Server", "Google Analyt... | 0.00000000426 | 10,896,267.00 | 2026/05/24 | 1 | {"A": ["163.44.185.164"], "MX": [{"ho... | 2025/07/12 | WHOIS | 2014/06/24 | 2026/06/30 | 2025/07/01 | Mizuho Morita | {"raw_response": ... | |
| jp | mongolia.toyama.jp | toyama.jp | Japan (JP) | 162.43.121.64 | ["NGINX"] | 0.00000000422 | 8,889,947.00 | 2026/05/18 | 1 | {"A": ["162.43.121.64"], "MX": [{"hos... | 2026/05/23 | WHOIS | 2023/04/18 | 2026/04/30 | 2025/05/01 | {"raw_response": ... | ||
| jp | wedding.toyama.jp | toyama.jp | Japan (JP) | 210.131.236.150 | ["Apache HTTP Server"] | 0.00000000418 | 0.00 | 2026/05/29 | 1 | {"A": ["210.131.236.150"], "MX": [{"h... | 2026/03/12 | WHOIS | 2014/02/22 | 2027/02/28 | 2026/03/01 | Forever.co | {"raw_response": ... | |
| jp | ohyama.toyama.jp | toyama.jp | Japan (JP) | 162.43.24.61 | ["Google Tag Manager", "Apache HTTP S... | 0.00000000415 | 12,623,697.00 | 2026/05/19 | 1 | {"A": ["162.43.24.61"], "MX": [{"host... | 2025/11/04 | WHOIS | 2019/10/18 | 2026/10/31 | 2025/11/01 | futoshi tanii | {"raw_response": ... | |
| jp | sushiacademy.toyama.jp | toyama.jp | Japan (JP) | 183.90.240.85 | ["WordPress", "NGINX", "Google Analyt... | 0.00000000415 | 10,866,473.00 | 2026/05/29 | 1 | {"A": ["183.90.240.85"], "MX": [{"hos... | 2025/09/29 | WHOIS | 2015/08/04 | 2026/08/31 | 2025/09/01 | Shinminato Sushi Academy | {"raw_response": ... |
The largest database of live domains and detailed information about them, designed to boost your digital strategies.
| Technology | Count Domain | Percentage of Technology |
|---|---|---|
| NGINX | 32 | 25.00 |
| Google Tag Manager | 23 | 17.97 |
| Apache HTTP Server | 20 | 15.63 |
| PHP | 16 | 12.50 |
| WordPress | 15 | 11.72 |
| Plesk | 6 | 4.69 |
| 4 | 3.13 | |
| Google Analytics | 3 | 2.34 |
| Google reCAPTCHA | 2 | 1.56 |
| adyen | 1 | 0.78 |
| Pepyaka | 1 | 0.78 |
| Amazon CloudFront | 1 | 0.78 |
| CakePHP | 1 | 0.78 |
| Envoy Proxy | 1 | 0.78 |
| Nuxt.js | 1 | 0.78 |
| Wix | 1 | 0.78 |
| Country | Count Domain | Percentage of Country |
|---|---|---|
| Japan (JP) | 60 | 72.29 |
| Switzerland (CH) | 9 | 10.84 |
| 8 | 9.64 | |
| Germany (DE) | 3 | 3.61 |
| United States (US) | 3 | 3.61 |
.toyama.jp is a geographic second‑level label within Japan’s .jp hierarchy, intended for entities connected to Toyama Prefecture. In our taxonomy, .toyama.jp domains and .toyama.jp websites form a compact regional corpus useful for studying local identity and audience targeting within Japan. We currently index active registrations, with resolving as live sites and usage observed in countries, indicating modest but distributed adoption. These signals help us profile content types, hosting choices, and language patterns specific to Toyama‑affiliated registrants. Researchers and digital strategists can compare this namespace against other Japanese localities to assess brand fit, visibility, and risk. Download .toyama.jp domain datasets from webatla to explore deeper.
.toyama.jp emerged as part of Japan’s locality‑based .jp structure, where prefecture names operate at the second level to signal geographic provenance. Typical characteristics include descriptive naming aligned to municipalities or organizations and alignment with Japan‑focused audiences. For .toyama.jp domains and .toyama.jp websites, DNS readiness and freshness matter: have active DNS records, while recent registration signals show last week and last month, suggesting a stable, low‑volatility zone. We analyze uptime, resolver diversity, and hosting geography to understand resilience and reach for Toyama‑aligned digital assets. These features make the space suitable for case studies on regional branding and long‑lived institutional content. Get webatla’s .toyama.jp domain datasets to benchmark this namespace.
Organizations choose .toyama.jp to express an affiliation with Toyama – municipal units, cultural institutions, SMEs, and tourism bodies are typical adopters. In competitive positioning, .toyama.jp domains and .toyama.jp websites communicate locality, help disambiguate Japanese audiences, and enable consistent regional branding across services. From our index, live sites arise from active registrations, with activity present in countries; DNS configuration stands at , indicating most names are technically enabled. These parameters let us score discoverability, content freshness, and network exposure for organizations deciding between geographic or generic namespaces. Stakeholders can compare peer clusters, spot infrastructure biases, and size opportunities before committing resources. Download webatla’s .toyama.jp domain datasets for unbiased competitive analysis.
The largest database of live domains and detailed information about them, designed to boost your digital strategies.
Yes, you can view examples to see the file format and the amount of information provided. You can download them on the Pricing page, under each package.
All files are provided in CSV format. If you need a different format (XML, JSON, SQL), please contact our support team.
You need to make a purchase on our website. Once the payment is complete, you will receive a download link for the files in your selected package.
We only offer package solutions. You can check out our packages and pricing on the Pricing page.
