0 last week
0 last month
364 active domains
326 domains with DNS records
Domains from 7 countries
364 domains with RDAP and WHOIS records
Includes 219 unique IPs hosting active domains
A metric that estimates network influence and trust, based on the link structure of domains using .kyoto.jp TLD
The average PageRank score reflecting the SEO authority of websites with the .kyoto.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 | konpeki.kyoto.jp | kyoto.jp | Japan (JP) | 27.133.157.232 | ["Google Tag Manager", "Apache HTTP S... | 0.00000003941 | 12,631,514.00 | 2026/04/13 | 1 | {"A": ["27.133.157.232"], "MX": [{"ho... | 2026/03/11 | WHOIS | 2019/02/20 | 2027/02/28 | 2026/03/01 | Konpeki Co.,Ltd. | {"raw_response": ... | |
| jp | iere.kyoto.jp | kyoto.jp | Japan (JP) | 35.75.122.51 | ["NGINX"] | 0.00000003365 | 17,345,958.00 | 2026/04/13 | 1 | {"A": ["35.75.122.51"], "MX": [{"host... | 2025/07/15 | WHOIS | 2021/04/12 | 2026/04/30 | 2025/05/01 | (Not displayed by registrant's request) | {"raw_response": ... | |
| jp | otabe.kyoto.jp | kyoto.jp | Japan (JP) | 133.18.79.60 | ["Google Tag Manager", "NGINX", "Goog... | 0.00000002649 | 13,274,120.00 | 2026/04/07 | 1 | {"A": ["133.18.79.60"], "MX": [{"host... | 2026/03/11 | WHOIS | 2015/02/03 | 2027/02/28 | 2026/03/01 | (Not displayed by registrant's request) | {"raw_response": ... | |
| jp | webjobpark.kyoto.jp | kyoto.jp | Japan (JP) | 150.60.249.134 | ["Apache HTTP Server"] | 0.00000002241 | 12,932,155.00 | 2026/04/08 | 1 | {"A": ["150.60.249.134"], "MX": [{"ho... | 2025/09/07 | WHOIS | 2018/08/07 | 2026/08/31 | 2025/09/01 | (Not displayed by registrant's request) | {"raw_response": ... | |
| jp | michinoeki.kyoto.jp | kyoto.jp | Japan (JP) | 157.7.107.82 | ["Apache HTTP Server", "WordPress", "... | 0.00000001869 | 13,710,903.00 | 2026/04/08 | 1 | {"A": ["157.7.107.82"], "MX": [{"host... | 2025/10/12 | WHOIS | 2016/09/30 | 2026/09/30 | 2025/10/01 | Kenji Morimoto | {"raw_response": ... | |
| jp | gokounomiya.kyoto.jp | kyoto.jp | Japan (JP) | 133.130.64.96 | ["Apache HTTP Server"] | 0.00000001521 | 13,230,740.00 | 2026/04/08 | 1 | {"A": ["133.130.64.96"], "MX": [{"hos... | 2025/09/07 | WHOIS | 2017/08/01 | 2026/08/31 | 2025/09/01 | (Not displayed by registrant's request) | {"raw_response": ... | |
| jp | kamoshika.kyoto.jp | kyoto.jp | Japan (JP) | 118.27.125.191 | ["Google Tag Manager", "LiteSpeed Web... | 0.00000001494 | 13,115,609.00 | 2026/04/07 | 1 | {"A": ["118.27.125.191"], "MX": [{"ho... | 2025/08/14 | WHOIS | 2014/04/09 | 2026/04/30 | 2025/05/01 | Megumi Seki | {"raw_response": ... | |
| jp | trip.kyoto.jp | kyoto.jp | Japan (JP) | 210.152.106.152 | ["Apache HTTP Server"] | 0.00000001425 | 14,946,455.00 | 2026/04/07 | 1 | {"A": ["210.152.106.152"], "NS": ["01... | 2025/12/07 | WHOIS | 2012/11/18 | 2026/11/30 | 2025/12/01 | Hearst Fujingaho Co., Ltd. | {"raw_response": ... | |
| jp | sanjokai.kyoto.jp | kyoto.jp | Japan (JP) | 164.46.58.197 | ["Apache HTTP Server", "WordPress", "... | 0.00000001369 | 14,269,268.00 | 2026/04/11 | 1 | {"A": ["164.46.58.197"], "NS": ["ns-1... | 2025/08/26 | WHOIS | 2014/07/16 | 2026/07/31 | 2025/08/01 | (Not displayed by registrant's request) | {"raw_response": ... | |
| jp | miyaco.kyoto.jp | kyoto.jp | Japan (JP) | 163.44.185.210 | ["Google Tag Manager", "LiteSpeed Web... | 0.00000001339 | 14,641,458.00 | 2026/04/08 | 1 | {"A": ["163.44.185.210"], "MX": [{"ho... | 2025/11/04 | WHOIS | 2020/10/01 | 2026/10/31 | 2025/11/01 | takuya chuma | {"raw_response": ... | |
| jp | kvsc.kyoto.jp | kyoto.jp | Japan (JP) | 49.212.180.94 | ["WordPress", "NGINX", "Google Analyt... | 0.00000001169 | 13,063,435.00 | 2026/04/09 | 1 | {"A": ["49.212.180.94"], "MX": [{"hos... | 2026/03/12 | WHOIS | 2015/02/17 | 2027/02/28 | 2026/03/01 | Kyoto Victim Support Center | {"raw_response": ... | |
| jp | clearvision.kyoto.jp | kyoto.jp | Japan (JP) | 219.94.128.148 | ["WordPress", "NGINX", "PHP"] | 0.00000001087 | 13,226,917.00 | 2026/04/06 | 1 | {"A": ["219.94.128.148"], "MX": [{"ho... | 2025/12/07 | WHOIS | 2015/11/30 | 2026/11/30 | 2025/12/01 | kabusikigaisya kuriawa-ku | {"raw_response": ... | |
| jp | miyakosougou.kyoto.jp | kyoto.jp | Japan (JP) | 157.7.107.63 | ["Google Tag Manager", "Apache HTTP S... | 0.00000001032 | 13,226,606.00 | 2026/04/09 | 1 | {"A": ["157.7.107.63"], "MX": [{"host... | 2025/12/07 | WHOIS | 2017/11/20 | 2026/11/30 | 2025/12/01 | SHIGEKI TAKAYA | {"raw_response": ... | |
| jp | tokonagesan.kyoto.jp | kyoto.jp | Japan (JP) | 85.131.199.9 | ["Apache HTTP Server"] | 0.00000000944 | 13,113,938.00 | 2026/04/12 | 1 | {"A": ["85.131.199.9"], "TXT": ["v=sp... | 2025/11/01 | WHOIS | 2018/08/01 | 2026/08/31 | 2025/09/01 | TOKONAGESAN | {"raw_response": ... | |
| jp | komaruya.kyoto.jp | kyoto.jp | United States (US) | 198.185.159.144 | ["Google Tag Manager"] | 0.00000000911 | 13,610,972.00 | 2026/04/10 | 1 | {"A": ["198.185.159.144", "198.185.15... | 2026/01/07 | WHOIS | 2014/12/21 | 2026/12/31 | 2026/01/01 | Regioncreate co.,Ltd | {"raw_response": ... | |
| jp | salon-k.kyoto.jp | kyoto.jp | Japan (JP) | 157.7.107.79 | ["Apache HTTP Server", "WordPress", "... | 0.00000000815 | 13,226,032.00 | 2026/04/09 | 1 | {"A": ["157.7.107.79"], "MX": [{"host... | 2026/03/12 | WHOIS | 2016/03/13 | 2026/03/31 | 2025/04/01 | ibillet | {"raw_response": ... | |
| jp | sinfonia.kyoto.jp | kyoto.jp | Japan (JP) | 103.3.2.147 | ["WordPress", "NGINX", "PHP"] | 0.00000000781 | 12,997,067.00 | 2026/04/06 | 1 | {"A": ["103.3.2.147"], "MX": [{"host"... | 2025/12/07 | WHOIS | 2022/11/13 | 2026/11/30 | 2025/12/01 | (Not displayed by registrant's request) | {"raw_response": ... | |
| jp | honkuzu.kyoto.jp | kyoto.jp | Japan (JP) | 160.251.148.242 | ["Google Tag Manager", "NGINX"] | 0.00000000775 | 12,890,128.00 | 2026/04/06 | 1 | {"A": ["160.251.148.242"], "MX": [{"h... | 2025/12/07 | WHOIS | 2015/11/25 | 2026/11/30 | 2025/12/01 | aifinc Ltd. | {"raw_response": ... | |
| jp | yanagimachi.kyoto.jp | kyoto.jp | Japan (JP) | 120.136.14.58 | ["NGINX", "Google Analytics"] | 0.00000000736 | 13,500,428.00 | 2026/04/07 | 1 | {"A": ["120.136.14.58"], "MX": [{"hos... | 2026/01/07 | WHOIS | 2014/12/01 | 2026/12/31 | 2026/01/01 | Yuma Adachi | {"raw_response": ... | |
| jp | sky.kyoto.jp | kyoto.jp | Japan (JP) | 183.90.231.8 | ["Google Tag Manager", "NGINX"] | 0.00000000731 | 12,807,432.00 | 2026/04/08 | 1 | {"A": ["183.90.231.8"], "MX": [{"host... | 2025/07/13 | WHOIS | 2016/04/19 | 2026/04/30 | 2025/05/01 | Odanitsune Co., Ltd. | {"raw_response": ... | |
| jp | gochio.kyoto.jp | kyoto.jp | Japan (JP) | 112.78.125.106 | ["Google Tag Manager", "NGINX", "Goog... | 0.00000000720 | 12,751,080.00 | 2026/04/09 | 1 | {"A": ["112.78.125.106"], "MX": [{"ho... | 2026/01/02 | WHOIS | 2018/01/23 | 2026/01/31 | 2025/02/01 | (Not displayed by registrant's request) | {"raw_response": ... | |
| jp | matchamore.kyoto.jp | kyoto.jp | Japan (JP) | 183.181.97.110 | ["WordPress", "NGINX", "PHP"] | 0.00000000719 | 13,031,308.00 | 2026/04/06 | 1 | {"A": ["183.181.97.110"], "MX": [{"ho... | 2026/01/07 | WHOIS | 2020/12/24 | 2026/12/31 | 2026/01/03 | Ryo Tsukamoto | {"raw_response": ... | |
| jp | rocher.kyoto.jp | kyoto.jp | Japan (JP) | 183.77.66.33 | ["Google Tag Manager", "NGINX"] | 0.00000000691 | 12,970,297.00 | 2026/04/12 | 1 | {"A": ["183.77.66.33"], "SOA": {"mnam... | 2026/03/12 | WHOIS | 2014/02/25 | 2027/02/28 | 2026/03/01 | Epea Co., Ltd. | {"raw_response": ... | |
| jp | calligraphy.kyoto.jp | kyoto.jp | Japan (JP) | 133.18.34.25 | ["WordPress", "NGINX", "Google reCAPT... | 0.00000000683 | 13,512,231.00 | 2026/04/07 | 1 | {"A": ["133.18.34.25"], "MX": [{"host... | 2025/09/08 | WHOIS | 2015/08/25 | 2026/08/31 | 2025/09/01 | chifumi niimi | {"raw_response": ... | |
| jp | komatsu.kyoto.jp | kyoto.jp | United States (US) | 188.114.96.3 | ["Cloudflare"] | 0.00000000683 | 10,926,720.00 | 2026/04/09 | 1 | {"A": ["188.114.96.3", "188.114.97.3"... | 2026/01/02 | WHOIS | 2014/01/09 | 2026/01/31 | 2025/02/01 | Yoshito Komatsu | {"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 | 112 | 18.73 |
| PHP | 105 | 17.56 |
| WordPress | 95 | 15.89 |
| Apache HTTP Server | 80 | 13.38 |
| Google Tag Manager | 79 | 13.21 |
| Google Analytics | 39 | 6.52 |
| 32 | 5.35 | |
| Google reCAPTCHA | 17 | 2.84 |
| Plesk | 9 | 1.51 |
| LiteSpeed Web Server | 7 | 1.17 |
| Wix | 4 | 0.67 |
| Cloudflare | 3 | 0.50 |
| Google AdSense | 3 | 0.50 |
| WooCommerce | 3 | 0.50 |
| Gravatar | 2 | 0.33 |
| Jimdo | 2 | 0.33 |
| ASP.NET | 1 | 0.17 |
| Envoy Proxy | 1 | 0.17 |
| Laravel | 1 | 0.17 |
| Microsoft IIS | 1 | 0.17 |
| OpenResty | 1 | 0.17 |
| Shopify | 1 | 0.17 |
| Country | Count Domain | Percentage of Country |
|---|---|---|
| Japan (JP) | 223 | 61.26 |
| 110 | 30.22 | |
| United States (US) | 16 | 4.40 |
| Switzerland (CH) | 7 | 1.92 |
| Germany (DE) | 5 | 1.37 |
| Canada (CA) | 1 | 0.27 |
| Malaysia (MY) | 1 | 0.27 |
| Netherlands (NL) | 1 | 0.27 |
The .kyoto.jp top-level domain – technically a regional second-level namespace under .jp – identifies digital properties linked to Kyoto, Japan. It groups municipal, cultural, academic, and tourism entities that want a locally anchored identity while remaining within Japan’s national ccTLD framework. In our index, we currently observe active .kyoto.jp domains and live .kyoto.jp websites, reflecting a compact yet stable footprint distributed across countries through multi-location hosting and registrant presence. This scale enables focused analysis of local actors, content patterns, and infrastructure choices. We track lifecycle metrics, ownership signals, and technology stacks to benchmark performance against neighboring Japanese localities. Download the .kyoto.jp domain datasets from webatla.
Japan’s domain landscape includes locality-specific second‑level spaces created to reflect administrative regions; .kyoto.jp belongs to this structured .jp hierarchy and inherits standard .jp operational practices. In practice, registrars prioritize demonstrable ties to Kyoto, so adoption concentrates among regional stakeholders. On infrastructure, provisioning is robust: .kyoto.jp domains currently publish DNS records, a clear indicator of configuration readiness across the zone. Recent registrations have been subdued – – which aligns with a stable base of .kyoto.jp websites rather than rapid expansion. We monitor nameserver concentration, hosting geography, and change velocity to surface systemic shifts and emerging risks across this namespace. Download historical .kyoto.jp domain datasets from webatla.
Organizations choose .kyoto.jp to signal geographic relevance, cultural affinity, and audience targeting within Japan. Typical adopters include local businesses, cultural institutions, universities, tourism operators, event organizers, and global brands localizing offerings, all seeking credible .kyoto.jp websites aligned with Kyoto-specific search demand. For risk‑aware planning, we analyze churn, ownership consolidation, and technology stacks across .kyoto.jp domains, correlating market signals with seasonal activity. Last week’s activity – new registrations – suggests a steady, low‑volatility namespace where renewals dominate. These metrics complement counts of active entities and help prioritize outreach or investment timing. Our datasets reveal hosting dispersion, CDN uptake, and security adoption patterns useful for benchmarking. Download curated .kyoto.jp domain datasets from webatla.
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.
