0 last week
1 last month
55 active domains
40 domains with DNS records
Domains from 4 countries
54 domains with RDAP and WHOIS records
Includes 26 unique IPs hosting active domains
A metric that estimates network influence and trust, based on the link structure of domains using .yamaguchi.jp TLD
The average PageRank score reflecting the SEO authority of websites with the .yamaguchi.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 | tryangle.yamaguchi.jp | yamaguchi.jp | United States (US) | 172.67.220.233 | ["Google Tag Manager", "Google AdSens... | 0.00000002275 | 14,650,276.00 | 2026/02/13 | 1 | {"A": ["172.67.220.233", "104.21.94.7... | 2025/11/04 | WHOIS | 2018/10/11 | 2026/10/31 | 2025/11/01 | kaneda takanori | {"raw_response": ... | |
| jp | glowup.yamaguchi.jp | yamaguchi.jp | Japan (JP) | 162.43.94.31 | ["Google Tag Manager", "WordPress", "... | 0.00000000883 | 12,808,591.00 | 2026/02/22 | 1 | {"A": ["162.43.94.31"], "MX": [{"host... | 2025/07/04 | WHOIS | 2024/04/05 | 2026/04/30 | 2025/05/01 | (Not displayed by registrant's request) | {"raw_response": ... | |
| jp | lawaku.yamaguchi.jp | yamaguchi.jp | United States (US) | 185.230.63.171 | ["Wix"] | 0.00000000801 | 12,631,187.00 | 2026/02/04 | 1 | {"A": ["185.230.63.171", "185.230.63.... | 2025/07/09 | WHOIS | 2020/02/25 | 2026/02/28 | 2025/03/01 | (Not displayed by registrant's request) | {"raw_response": ... | |
| jp | wdc.yamaguchi.jp | yamaguchi.jp | Japan (JP) | 162.43.122.174 | ["Google Tag Manager", "WordPress", "... | 0.00000000719 | 12,639,441.00 | 2026/02/09 | 1 | {"A": ["162.43.122.174"], "MX": [{"ho... | 2025/08/31 | WHOIS | 2023/05/09 | 2026/05/31 | 2025/06/01 | (Not displayed by registrant's request) | {"raw_response": ... | |
| jp | magasin.yamaguchi.jp | yamaguchi.jp | Japan (JP) | 133.130.35.90 | ["Google Tag Manager", "NGINX", "PHP"... | 0.00000000696 | 12,953,226.00 | 2026/01/30 | 1 | {"A": ["133.130.35.90"], "MX": [{"hos... | 2025/07/11 | WHOIS | 2022/02/02 | 2026/02/28 | 2025/03/01 | kenji kasuga | {"raw_response": ... | |
| jp | wings.yamaguchi.jp | yamaguchi.jp | Japan (JP) | 162.43.122.174 | ["NGINX"] | 0.00000000601 | 12,594,682.00 | 2026/02/01 | 1 | {"A": ["162.43.122.174"], "MX": [{"ho... | 2025/08/24 | WHOIS | 2023/05/09 | 2026/05/31 | 2025/06/01 | (Not displayed by registrant's request) | {"raw_response": ... | |
| jp | blossom.yamaguchi.jp | yamaguchi.jp | Japan (JP) | 162.43.94.46 | 0.00000000594 | 12,877,012.00 | 2026/02/02 | 1 | {"A": ["162.43.94.46"], "MX": [{"host... | 2025/08/14 | WHOIS | 2024/04/14 | 2026/04/30 | 2025/05/01 | kei kitano | {"raw_response": ... | ||
| jp | collection.yamaguchi.jp | yamaguchi.jp | Japan (JP) | 35.73.31.55 | ["Apache HTTP Server"] | 0.00000000520 | 11,050,141.00 | 2026/02/16 | 1 | {"A": ["35.73.31.55", "54.199.20.166"... | 2026/01/07 | WHOIS | 2023/12/04 | 2026/12/31 | 2026/01/01 | (Not displayed by registrant's request) | {"raw_response": ... | |
| jp | landmark.yamaguchi.jp | yamaguchi.jp | Japan (JP) | 59.106.171.50 | ["Google Tag Manager", "NGINX"] | 0.00000000513 | 10,759,722.00 | 2026/02/06 | 1 | {"A": ["59.106.171.50"], "MX": [{"hos... | 2026/01/02 | WHOIS | 2024/01/25 | 2026/01/31 | 2025/02/01 | (Not displayed by registrant's request) | {"raw_response": ... | |
| jp | daisuke.yamaguchi.jp | yamaguchi.jp | Japan (JP) | 163.44.185.202 | ["Google Tag Manager", "Apache HTTP S... | 0.00000000460 | 10,169,399.00 | 2026/02/02 | 1 | {"A": ["163.44.185.202"], "MX": [{"ho... | 2026/01/02 | WHOIS | 2015/01/05 | 2026/01/31 | 2025/02/01 | yamaguchi daisuke | {"raw_response": ... | |
| jp | deli.yamaguchi.jp | yamaguchi.jp | Japan (JP) | 183.181.98.47 | ["Google Tag Manager", "WordPress", "... | 0.00000000460 | 11,069,275.00 | 2026/02/07 | 1 | {"A": ["183.181.98.47"], "MX": [{"hos... | 2026/01/02 | WHOIS | 2018/01/25 | 2026/01/31 | 2025/02/01 | Xserver Inc. | {"raw_response": ... | |
| jp | we-love.yamaguchi.jp | yamaguchi.jp | Japan (JP) | 202.233.67.96 | ["Google Tag Manager", "Google AdSens... | 0.00000000446 | 12,563,842.00 | 2026/02/26 | 1 | {"A": ["202.233.67.96"], "MX": [{"hos... | 2025/10/12 | WHOIS | 2016/09/26 | 2026/09/30 | 2025/10/01 | (Not displayed by registrant's request) | {"raw_response": ... | |
| jp | the.yamaguchi.jp | yamaguchi.jp | Japan (JP) | 160.16.60.165 | 0.00000000422 | 0.00 | 2026/01/18 | 1 | {"A": ["160.16.60.165"], "MX": [{"hos... | 2026/01/07 | WHOIS | 2012/12/05 | 2026/12/31 | 2026/01/01 | CobitWork | {"raw_response": ... | ||
| jp | gospelhouse.yamaguchi.jp | yamaguchi.jp | Japan (JP) | 118.27.125.244 | ["LiteSpeed Web Server", "WordPress",... | 0.00000000416 | 1.00 | 2026/01/31 | 1 | {"A": ["118.27.125.244"], "MX": [{"ho... | 2025/12/07 | WHOIS | 2022/11/05 | 2026/11/30 | 2025/12/01 | Satosi Murakami | {"raw_response": ... | |
| jp | takenocco.yamaguchi.jp | yamaguchi.jp | Japan (JP) | 202.226.39.118 | ["NGINX"] | 0.00000000406 | 9,766,775.00 | 2026/01/28 | 1 | {"A": ["202.226.39.118"], "MX": [{"ho... | 2025/12/07 | WHOIS | 2014/11/25 | 2026/11/30 | 2025/12/01 | Kuniyuki Takenaka | {"raw_response": ... | |
| jp | shuho.yamaguchi.jp | yamaguchi.jp | Japan (JP) | 183.90.250.10 | 0.00000000400 | 10,170,939.00 | 2026/02/01 | 1 | {"A": ["183.90.250.10"], "MX": [{"hos... | 2025/10/12 | WHOIS | 2016/09/01 | 2026/09/30 | 2025/10/01 | office JTP | {"raw_response": ... | ||
| jp | ism.yamaguchi.jp | yamaguchi.jp | Japan (JP) | 59.106.171.28 | 0.00000000393 | 0.00 | 2026/02/09 | 1 | {"A": ["59.106.171.28"], "MX": [{"hos... | 2025/09/09 | WHOIS | 2013/05/31 | 2026/05/31 | 2025/06/01 | plusism | {"raw_response": ... | ||
| jp | kyobun2021.yamaguchi.jp | yamaguchi.jp | Japan (JP) | 163.44.185.186 | 0.00000000393 | 0.00 | 2026/02/10 | 1 | {"A": ["163.44.185.186"], "MX": [{"ho... | 2025/08/27 | WHOIS | 2021/04/23 | 2026/04/30 | 2025/05/01 | Kumura Toshio | {"raw_response": ... | ||
| jp | manabiya.yamaguchi.jp | yamaguchi.jp | Japan (JP) | 133.130.64.112 | ["Apache HTTP Server"] | 0.00000000393 | 0.00 | 2026/02/06 | 1 | {"A": ["133.130.64.112"], "MX": [{"ho... | 2026/01/02 | WHOIS | 2018/01/04 | 2026/01/31 | 2025/02/01 | (Not displayed by registrant's request) | {"raw_response": ... | |
| jp | tire.yamaguchi.jp | yamaguchi.jp | Japan (JP) | 157.7.107.73 | 0.00000000312 | 10,802,659.00 | 2026/02/02 | 1 | {"A": ["157.7.107.73"], "MX": [{"host... | 2026/01/02 | WHOIS | 2022/01/17 | 2026/01/31 | 2025/02/01 | Takanori Nakashima | {"raw_response": ... | ||
| jp | rolex.yamaguchi.jp | yamaguchi.jp | Switzerland (CH) | 35.216.171.99 | 0.00000000290 | 0.00 | 2026/01/30 | 1 | {"A": ["35.216.171.99"], "NS": ["dns1... | 2025/12/07 | WHOIS | 2012/11/18 | 2026/11/30 | 2025/12/01 | ROLEX SA | {"raw_response": ... | ||
| jp | xn--gckg4ecj7a4pxbzj.yamaguchi.jp | yamaguchi.jp | Switzerland (CH) | 35.216.176.23 | 0.00000000290 | 0.00 | 2026/02/18 | 1 | {"A": ["35.216.176.23"], "NS": ["dns1... | 2025/12/07 | WHOIS | 2012/11/18 | 2026/11/30 | 2025/12/01 | Montres Tudor SA | {"raw_response": ... | ||
| jp | xn--7ckq7fza7f.yamaguchi.jp | yamaguchi.jp | Switzerland (CH) | 35.216.176.23 | 0.00000000288 | 11,183,318.00 | 2026/01/30 | 1 | {"A": ["35.216.176.23"], "NS": ["dns1... | 2025/12/07 | WHOIS | 2012/11/18 | 2026/11/30 | 2025/12/01 | Montres Tudor SA | {"raw_response": ... | ||
| jp | kts.yamaguchi.jp | yamaguchi.jp | United States (US) | 18.66.122.24 | 0.00000000000 | 0.00 | 2026/01/28 | 1 | {"A": ["18.66.122.24", "18.66.122.23"... | 2025/08/29 | WHOIS | 2025/08/06 | 2026/08/31 | 2025/08/06 | (Not displayed by registrant's request) | {"raw_response": ... | ||
| jp | tudor.yamaguchi.jp | yamaguchi.jp | Switzerland (CH) | 35.216.176.23 | 0.00000000000 | 0.00 | 2026/02/08 | 1 | {"A": ["35.216.176.23"], "NS": ["dns1... | 2025/12/07 | WHOIS | 2012/11/18 | 2026/11/30 | 2025/12/01 | Montres Tudor SA | {"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 |
|---|---|---|
| Google Tag Manager | 8 | 18.60 |
| NGINX | 8 | 18.60 |
| PHP | 7 | 16.28 |
| WordPress | 7 | 16.28 |
| Apache HTTP Server | 3 | 6.98 |
| 3 | 6.98 | |
| Google AdSense | 2 | 4.65 |
| Google reCAPTCHA | 2 | 4.65 |
| Cloudflare | 1 | 2.33 |
| LiteSpeed Web Server | 1 | 2.33 |
| Wix | 1 | 2.33 |
| Country | Count Domain | Percentage of Country |
|---|---|---|
| Japan (JP) | 19 | 34.55 |
| 15 | 27.27 | |
| Switzerland (CH) | 9 | 16.36 |
| Germany (DE) | 7 | 12.73 |
| United States (US) | 5 | 9.09 |
The .yamaguchi.jp TLD is a geographic second‑level label under Japan’s .jp namespace, denoting entities connected to Yamaguchi Prefecture. It is typically used by local administrations, educational bodies, businesses, and residents seeking a clear regional identifier. As domain analysts, we track both .yamaguchi.jp domains and .yamaguchi.jp websites to understand local internet presence and change over time. In our index, we currently observe 55 active .yamaguchi.jp domains and 40 live .yamaguchi.jp websites, offering a concise view of this niche namespace. Such figures help benchmark adoption against other Japanese geographic zones and inform portfolio decisions. Download .yamaguchi.jp domain datasets from webatla for deeper analysis.
Geographic second‑level spaces under .jp have been available for many years, with .yamaguchi.jp reflecting the long‑standing practice of mapping prefectures inside the national ccTLD. This structure emphasizes locality while leveraging .jp’s mature technical and policy framework. For .yamaguchi.jp domains, registrars commonly require a presence in Japan, and DNSSEC support at the .jp layer strengthens security for .yamaguchi.jp websites. Recent activity is subdued: 0 new registrations last week and 1 in February 2026, while 40 domains currently resolve via DNS, closely aligned with 40 live sites. These signals point to a stable, low‑churn namespace suitable for consistent regional branding. Download .yamaguchi.jp domain datasets from webatla to explore trends.
Organizations choose .yamaguchi.jp to communicate verified locality – useful for governments, schools, tourism portals, and SMEs anchoring services in Yamaguchi. The TLD can aid geotargeting, directory alignment, and user trust when evaluated alongside content and hosting signals across .yamaguchi.jp websites. We see adoption beyond Japan as well, with usage distributed across 4 countries, though volumes remain focused locally. Portfolio managers can assess competitive density using 55 registered .yamaguchi.jp domains and activity evidenced by 40 visible sites. For content teams, aligning titles and metadata with the locality helps .yamaguchi.jp websites surface in regionally scoped searches, while consistent naming conventions ease portfolio management at scale. Download .yamaguchi.jp domain datasets from webatla now.
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.
