0 last week
0 last month
155 active domains
146 domains with DNS records
Domains from 5 countries
155 domains with RDAP and WHOIS records
Includes 120 unique IPs hosting active domains
A metric that estimates network influence and trust, based on the link structure of domains using .nagano.jp TLD
The average PageRank score reflecting the SEO authority of websites with the .nagano.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 | minami.nagano.jp | nagano.jp | Japan (JP) | 157.112.189.20 | ["WordPress", "NGINX", "Google reCAPT... | 0.00000002859 | 13,343,979.00 | 2026/06/01 | 1 | {"A": ["157.112.189.20"], "MX": [{"ho... | 2026/05/23 | WHOIS | 2014/04/10 | 2026/04/30 | 2025/05/01 | makoto | {"raw_response": ... | |
| jp | oshigoto.nagano.jp | nagano.jp | Japan (JP) | 153.127.40.50 | ["Google Tag Manager", "Apache HTTP S... | 0.00000002342 | 12,427,140.00 | 2026/06/05 | 1 | {"A": ["153.127.40.50"], "MX": [{"hos... | 2025/10/12 | WHOIS | 2014/09/12 | 2026/09/30 | 2025/10/01 | (Not displayed by registrant's request) | {"raw_response": ... | |
| jp | culture.nagano.jp | nagano.jp | Japan (JP) | 183.181.99.18 | ["Google Tag Manager", "WordPress", "... | 0.00000002327 | 13,961,996.00 | 2026/05/24 | 1 | {"A": ["183.181.99.18"], "MX": [{"hos... | 2025/12/07 | WHOIS | 2019/11/08 | 2026/11/30 | 2025/12/01 | Tanakara Inc. | {"raw_response": ... | |
| jp | biotope.nagano.jp | nagano.jp | Japan (JP) | 49.212.243.35 | ["WordPress", "NGINX"] | 0.00000002194 | 13,635,646.00 | 2026/06/01 | 1 | {"A": ["49.212.243.35"], "MX": [{"hos... | 2025/12/07 | WHOIS | 2020/11/20 | 2026/11/30 | 2025/12/01 | SHIN TANAKA | {"raw_response": ... | |
| jp | ace.nagano.jp | nagano.jp | Japan (JP) | 183.90.228.8 | ["Google Tag Manager", "WordPress", "... | 0.00000001664 | 12,210,373.00 | 2026/05/25 | 1 | {"A": ["183.90.228.8"], "MX": [{"host... | 2026/04/22 | WHOIS | 2015/03/16 | 2027/03/31 | 2026/04/01 | {"raw_response": ... | ||
| jp | go-iijima.nagano.jp | nagano.jp | Japan (JP) | 157.7.189.64 | ["Google Tag Manager", "Apache HTTP S... | 0.00000001490 | 13,956,977.00 | 2026/05/29 | 1 | {"A": ["157.7.189.64"], "NS": ["01.dn... | 2025/12/07 | WHOIS | 2018/11/12 | 2026/11/30 | 2025/12/01 | (Not displayed by registrant's request) | {"raw_response": ... | |
| jp | xn--vuqxni75aysf.nagano.jp | nagano.jp | Japan (JP) | 49.212.180.222 | ["Google Tag Manager", "WordPress", "... | 0.00000001406 | 12,236,764.00 | 2026/06/05 | 1 | {"A": ["49.212.180.222"], "MX": [{"ho... | 2025/08/28 | WHOIS | 2016/07/14 | 2026/07/31 | 2025/08/01 | (Not displayed by registrant's request) | {"raw_response": ... | |
| jp | hakkou-valley.nagano.jp | nagano.jp | United States (US) | 34.111.141.225 | ["Nuxt.js"] | 0.00000001266 | 12,314,788.00 | 2026/05/29 | 1 | {"A": ["34.111.141.225"], "MX": [{"ho... | 2025/10/31 | WHOIS | 2023/09/15 | 2026/09/30 | 2025/10/01 | (Not displayed by registrant's request) | {"raw_response": ... | |
| jp | kankou-minamiminowa.nagano.jp | nagano.jp | Japan (JP) | 219.94.163.42 | ["WordPress", "NGINX"] | 0.00000001150 | 12,298,401.00 | 2026/06/03 | 1 | {"A": ["219.94.163.42"], "MX": [{"hos... | 2026/01/07 | WHOIS | 2022/12/16 | 2026/12/31 | 2026/01/05 | Minamiminowamura Kankoukyoukai | {"raw_response": ... | |
| jp | shiosaki.nagano.jp | nagano.jp | Japan (JP) | 210.136.205.247 | ["WordPress", "PHP", "Microsoft IIS"] | 0.00000001059 | 10,714,589.00 | 2026/05/28 | 1 | {"A": ["210.136.205.247"], "NS": ["dn... | 2026/01/07 | WHOIS | 2012/12/20 | 2026/12/31 | 2026/01/01 | AMATSUKAMI Honpo | {"raw_response": ... | |
| jp | goshikinoyu.nagano.jp | nagano.jp | Japan (JP) | 163.43.102.76 | ["WordPress", "NGINX", "Google reCAPT... | 0.00000001058 | 12,248,572.00 | 2026/06/01 | 1 | {"A": ["163.43.102.76"], "MX": [{"hos... | 2025/10/12 | WHOIS | 2018/09/03 | 2026/09/30 | 2025/10/01 | (Not displayed by registrant's request) | {"raw_response": ... | |
| jp | next.nagano.jp | nagano.jp | Japan (JP) | 183.90.235.39 | ["Google Tag Manager", "WordPress", "... | 0.00000001035 | 11,972,460.00 | 2026/05/29 | 1 | {"A": ["183.90.235.39"], "MX": [{"hos... | 2026/03/12 | WHOIS | 2023/02/06 | 2027/02/28 | 2026/03/01 | (Not displayed by registrant's request) | {"raw_response": ... | |
| jp | zen.nagano.jp | nagano.jp | Japan (JP) | 183.90.246.42 | ["Google Tag Manager", "WordPress", "... | 0.00000001026 | 12,726,981.00 | 2026/06/05 | 1 | {"A": ["183.90.246.42"], "MX": [{"hos... | 2025/11/04 | WHOIS | 2020/10/14 | 2026/10/31 | 2025/11/01 | (Not displayed by registrant's request) | {"raw_response": ... | |
| jp | syarousi.nagano.jp | nagano.jp | Japan (JP) | 183.181.88.55 | ["Google Tag Manager", "Google AdSens... | 0.00000000942 | 12,652,380.00 | 2026/06/05 | 1 | {"A": ["183.181.88.55"], "MX": [{"hos... | 2026/04/22 | WHOIS | 2019/03/18 | 2027/03/31 | 2026/04/01 | {"raw_response": ... | ||
| jp | hyokyo.nagano.jp | nagano.jp | Japan (JP) | 122.28.47.60 | ["Apache HTTP Server"] | 0.00000000924 | 10,783,987.00 | 2026/05/31 | 1 | {"A": ["122.28.47.60"], "MX": [{"host... | 2026/03/12 | WHOIS | 2015/02/02 | 2027/02/28 | 2026/03/01 | nagano car no association | {"raw_response": ... | |
| jp | medinex.nagano.jp | nagano.jp | Japan (JP) | 183.90.232.24 | ["Google Tag Manager", "WordPress", "... | 0.00000000891 | 12,648,660.00 | 2026/06/01 | 1 | {"A": ["183.90.232.24"], "MX": [{"hos... | 2025/09/09 | WHOIS | 2018/08/02 | 2026/08/31 | 2025/09/01 | Medinex Inc. | {"raw_response": ... | |
| jp | career.nagano.jp | nagano.jp | Japan (JP) | 218.216.182.152 | ["Apache HTTP Server"] | 0.00000000880 | 12,314,407.00 | 2026/05/28 | 1 | {"A": ["218.216.182.152"], "MX": [{"h... | 2025/12/07 | WHOIS | 2012/11/18 | 2026/11/30 | 2025/12/01 | Willways Corporation | {"raw_response": ... | |
| jp | noa.nagano.jp | nagano.jp | Japan (JP) | 183.90.235.39 | ["Google Tag Manager", "WordPress", "... | 0.00000000849 | 11,992,297.00 | 2026/05/28 | 1 | {"A": ["183.90.235.39"], "MX": [{"hos... | 2026/05/30 | WHOIS | 2021/05/12 | 2026/05/31 | 2025/06/01 | {"raw_response": ... | ||
| jp | uzuraya.nagano.jp | nagano.jp | Japan (JP) | 183.90.240.42 | ["WordPress", "NGINX"] | 0.00000000825 | 12,581,386.00 | 2026/06/05 | 1 | {"A": ["183.90.240.42"], "MX": [{"hos... | 2025/12/07 | WHOIS | 2017/11/22 | 2026/11/30 | 2025/12/01 | Xserver Inc. | {"raw_response": ... | |
| jp | amec.nagano.jp | nagano.jp | Japan (JP) | 183.90.248.44 | ["WordPress", "NGINX", "Google reCAPT... | 0.00000000782 | 10,605,955.00 | 2026/06/03 | 1 | {"A": ["183.90.248.44"], "MX": [{"hos... | 2025/09/07 | WHOIS | 2019/07/01 | 2026/07/31 | 2025/08/01 | Wakabayashi Shouichi | {"raw_response": ... | |
| jp | bar.nagano.jp | nagano.jp | Japan (JP) | 85.131.209.32 | ["Google Tag Manager", "WordPress", "... | 0.00000000776 | 10,867,813.00 | 2026/05/30 | 1 | {"A": ["85.131.209.32"], "MX": [{"hos... | 2025/09/07 | WHOIS | 2020/07/31 | 2026/07/31 | 2025/08/01 | (Not displayed by registrant's request) | {"raw_response": ... | |
| jp | oasis.nagano.jp | nagano.jp | Japan (JP) | 157.7.107.22 | ["Google Tag Manager", "Apache HTTP S... | 0.00000000664 | 12,333,402.00 | 2026/06/05 | 1 | {"A": ["157.7.107.22"], "MX": [{"host... | 2025/10/09 | WHOIS | 2013/09/13 | 2026/09/30 | 2025/10/01 | takeshi ohkuma | {"raw_response": ... | |
| jp | kawanakajima.nagano.jp | nagano.jp | Japan (JP) | 192.47.67.202 | ["Google Tag Manager", "Apache HTTP S... | 0.00000000631 | 12,262,015.00 | 2026/06/05 | 1 | {"A": ["192.47.67.202"], "NS": ["ns01... | 2025/11/04 | WHOIS | 2023/10/24 | 2026/10/31 | 2025/11/01 | Nagano City | {"raw_response": ... | |
| jp | sansonryugaku.nagano.jp | nagano.jp | Japan (JP) | 194.91.3.103 | ["Google Tag Manager", "Apache HTTP S... | 0.00000000628 | 12,005,930.00 | 2026/06/04 | 1 | {"A": ["194.91.3.103"], "MX": [{"host... | 2025/12/07 | WHOIS | 2022/11/29 | 2026/11/30 | 2025/12/01 | Mercury Project Office, Inc. | {"raw_response": ... | |
| jp | aokiya.nagano.jp | nagano.jp | Japan (JP) | 210.131.236.210 | ["Apache HTTP Server"] | 0.00000000597 | 11,893,255.00 | 2026/05/31 | 1 | {"A": ["210.131.236.210"], "MX": [{"h... | 2026/04/22 | WHOIS | 2015/03/09 | 2027/03/31 | 2026/04/01 | {"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 |
|---|---|---|
| WordPress | 65 | 22.18 |
| NGINX | 59 | 20.14 |
| Google Tag Manager | 40 | 13.65 |
| Apache HTTP Server | 38 | 12.97 |
| PHP | 37 | 12.63 |
| Google reCAPTCHA | 17 | 5.80 |
| 12 | 4.10 | |
| Google Analytics | 9 | 3.07 |
| Google AdSense | 6 | 2.05 |
| LiteSpeed Web Server | 5 | 1.71 |
| Cloudflare | 1 | 0.34 |
| Laravel | 1 | 0.34 |
| Microsoft IIS | 1 | 0.34 |
| Nuxt.js | 1 | 0.34 |
| WooCommerce | 1 | 0.34 |
| Country | Count Domain | Percentage of Country |
|---|---|---|
| Japan (JP) | 123 | 79.35 |
| 16 | 10.32 | |
| Switzerland (CH) | 9 | 5.81 |
| Germany (DE) | 3 | 1.94 |
| United States (US) | 3 | 1.94 |
| Canada (CA) | 1 | 0.65 |
.nagano.jp is a geographic second‑level space within Japan’s .jp country‑code top‑level domain, used by entities connected to Nagano Prefecture. In our global index, .nagano.jp domains and .nagano.jp websites are monitored alongside other locality namespaces to compare regional web footprints. We currently observe active registrations, with live sites and configured with DNS, distributed across countries. This footprint indicates modest scale but relatively high activation compared to many regional zones. As a locality label, eligibility and usage often emphasize a real connection to Nagano, supporting geographic relevance in Japan. We analyse naming patterns, hosting dispersion, and lifecycle signals to quantify local digital presence and cross‑border use. Download .nagano.jp domain datasets from webatla.
Japan’s .jp namespace is administered by the Japan Registry Services, and .nagano.jp sits within its geographic naming structure aimed at reflecting regional identity online. While detailed launch timelines are not public here, the model favors locality signalling and straightforward delegation. In our dataset, .nagano.jp domains and .nagano.jp websites show steady activation: of have DNS, suggesting high readiness. Recent flows are muted, with new registrations last week and overall, indicating a mature, low-churn zone. Hosting and DNS patterns concentrate domestically with some overseas presence consistent with countries of use. Download the .nagano.jp domain datasets from webatla for longitudinal analysis.
Organizations selecting .nagano.jp typically want clear geographic signalling – municipal offices, schools, SMEs, tourism bodies, and community groups – while some individuals adopt it for local identity. For discoverability, .nagano.jp domains align with place-specific content and citation patterns; .nagano.jp websites frequently host civic information, hospitality listings, or event calendars. We observe live sites within registrations, a meaningful content ratio, and countries of use that reflect hosting dispersion and ownership footprints. These metrics help benchmark competitors, assess category saturation, and monitor stability when weekly intake is . Our datasets surface naming, DNS, and hosting trends to inform planning and risk review. Download webatla’s .nagano.jp domain datasets to benchmark adoption.
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.
