1 last week
2 last month
913 active domains
858 domains with DNS records
Domains from 8 countries
913 domains with RDAP and WHOIS records
Includes 645 unique IPs hosting active domains
A metric that estimates network influence and trust, based on the link structure of domains using .tokyo.jp TLD
The average PageRank score reflecting the SEO authority of websites with the .tokyo.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 | oceans.tokyo.jp | tokyo.jp | United States (US) | 18.239.105.28 | ["Google Tag Manager", "Amazon CloudF... | 0.00000019968 | 14,576,973.00 | 2026/05/02 | 1 | {"A": ["18.239.105.28", "18.239.105.3... | 2025/08/30 | WHOIS | 2015/06/01 | 2026/06/30 | 2025/07/01 | LIGHTHOUSE MEDIA INC. | {"raw_response": ... | |
| jp | untitled.tokyo.jp | tokyo.jp | Japan (JP) | 118.27.125.184 | ["NGINX"] | 0.00000010558 | 12,642,416.00 | 2026/05/08 | 1 | {"A": ["118.27.125.184", "174.129.25.... | 2025/10/12 | WHOIS | 2013/09/02 | 2026/09/30 | 2025/10/01 | MITSUHIRO ITO | {"raw_response": ... | |
| jp | mikiki.tokyo.jp | tokyo.jp | Japan (JP) | 202.238.151.85 | ["Google Tag Manager"] | 0.00000010455 | 14,556,702.00 | 2026/05/02 | 1 | {"A": ["202.238.151.85"], "NS": ["ns0... | 2026/03/11 | WHOIS | 2014/02/17 | 2027/02/28 | 2026/03/01 | TOWER RECORDS Inc. | {"raw_response": ... | |
| jp | kaitoriplus.tokyo.jp | tokyo.jp | Japan (JP) | 162.43.122.200 | ["Google Tag Manager", "WordPress", "... | 0.00000009833 | 12,904,172.00 | 2026/04/29 | 1 | {"A": ["162.43.122.200"], "MX": [{"ho... | 2025/09/06 | WHOIS | 2024/05/17 | 2026/05/31 | 2025/06/01 | (Not displayed by registrant's request) | {"raw_response": ... | |
| jp | kosodate-machida.tokyo.jp | tokyo.jp | Japan (JP) | 210.189.174.93 | ["NGINX"] | 0.00000007585 | 14,318,840.00 | 2026/04/30 | 1 | {"A": ["210.189.174.93"], "NS": ["ns0... | 2026/03/12 | WHOIS | 2017/02/27 | 2027/02/28 | 2026/03/01 | Machida City | {"raw_response": ... | |
| jp | acceleration.tokyo.jp | tokyo.jp | Japan (JP) | 49.212.243.71 | ["Google Tag Manager", "NGINX", "Goog... | 0.00000007484 | 13,952,493.00 | 2026/05/06 | 1 | {"A": ["49.212.243.71"], "MX": [{"hos... | 2025/10/09 | WHOIS | 2015/09/17 | 2026/09/30 | 2025/10/01 | Jumpei Notomi | {"raw_response": ... | |
| jp | grid.tokyo.jp | tokyo.jp | United States (US) | 188.114.96.3 | ["Google Tag Manager", "Apache HTTP S... | 0.00000003812 | 14,415,890.00 | 2026/05/06 | 1 | {"A": ["188.114.96.3", "188.114.97.3"... | 2026/01/13 | WHOIS | 2026/01/01 | 2027/01/31 | 2026/01/01 | Taka Enterprise Ltd. WHOIS Privacy Se... | {"raw_response": ... | |
| jp | opensource-robotics.tokyo.jp | tokyo.jp | United States (US) | 35.87.168.231 | ["Apache HTTP Server", "WordPress", "... | 0.00000003646 | 17,008,612.00 | 2026/05/02 | 1 | {"A": ["35.87.168.231"], "MX": [{"hos... | 2025/10/12 | WHOIS | 2013/09/03 | 2026/09/30 | 2025/10/01 | Tokyo Opensource Robotics Kyokai Asso... | {"raw_response": ... | |
| jp | nihonbashi5-chuo.tokyo.jp | tokyo.jp | Japan (JP) | 163.43.102.102 | ["Google Tag Manager", "WordPress", "... | 0.00000003293 | 16,943,434.00 | 2026/05/01 | 1 | {"A": ["163.43.102.102"], "MX": [{"ho... | 2025/11/04 | WHOIS | 2017/10/30 | 2026/10/31 | 2025/11/01 | INDIE-DESIGN-OFFICE | {"raw_response": ... | |
| jp | bassontop.tokyo.jp | tokyo.jp | Japan (JP) | 49.212.66.202 | ["NGINX", "PHP"] | 0.00000003182 | 13,618,737.00 | 2026/05/01 | 1 | {"A": ["49.212.66.202"], "MX": [{"hos... | 2026/05/07 | WHOIS | 2014/04/14 | 2026/04/30 | 2025/05/01 | BASS ON TOP INC. | {"raw_response": ... | |
| jp | jtol.tokyo.jp | tokyo.jp | United States (US) | 34.111.141.225 | ["Nuxt.js"] | 0.00000003133 | 16,944,758.00 | 2026/04/29 | 1 | {"A": ["34.111.141.225"], "MX": [{"ho... | 2025/08/29 | WHOIS | 2024/07/26 | 2026/07/31 | 2025/08/01 | (Not displayed by registrant's request) | {"raw_response": ... | |
| jp | acf.tokyo.jp | tokyo.jp | Japan (JP) | 183.90.232.14 | ["Google Tag Manager", "NGINX", "PHP"... | 0.00000003028 | 16,943,282.00 | 2026/05/01 | 1 | {"A": ["183.90.232.14"], "MX": [{"hos... | 2025/09/10 | WHOIS | 2018/07/02 | 2026/07/31 | 2025/08/01 | (Not displayed by registrant's request) | {"raw_response": ... | |
| jp | coworking.tokyo.jp | tokyo.jp | United States (US) | 75.2.60.5 | ["Nuxt.js"] | 0.00000002971 | 13,746,477.00 | 2026/05/06 | 1 | {"A": ["75.2.60.5", "99.83.231.61"], ... | 2025/12/07 | WHOIS | 2012/11/19 | 2026/11/30 | 2025/12/01 | Direct Search Japan Inc. | {"raw_response": ... | |
| jp | tapo.tokyo.jp | tokyo.jp | Japan (JP) | 157.112.187.81 | ["NGINX"] | 0.00000002896 | 16,943,282.00 | 2026/04/30 | 1 | {"A": ["157.112.187.81"], "MX": [{"ho... | 2025/07/07 | WHOIS | 2020/06/12 | 2026/06/30 | 2025/07/01 | Netowl,Inc. | {"raw_response": ... | |
| jp | fact.tokyo.jp | tokyo.jp | Japan (JP) | 118.27.122.211 | ["Google Tag Manager", "WordPress", "... | 0.00000002427 | 12,288,867.00 | 2026/05/01 | 1 | {"A": ["118.27.122.211"], "MX": [{"ho... | 2026/03/12 | WHOIS | 2019/02/15 | 2027/02/28 | 2026/03/01 | (Not displayed by registrant's request) | {"raw_response": ... | |
| jp | lab.tokyo.jp | tokyo.jp | Japan (JP) | 153.123.7.50 | ["Google Tag Manager", "Plesk", "Word... | 0.00000001941 | 13,578,426.00 | 2026/04/30 | 1 | {"A": ["153.123.7.50"], "MX": [{"host... | 2025/12/07 | WHOIS | 2012/11/18 | 2026/11/30 | 2025/12/01 | Taiyokikaku Co.,Ltd. | {"raw_response": ... | |
| jp | hanami-web.tokyo.jp | tokyo.jp | Japan (JP) | 162.43.120.196 | ["Google Tag Manager", "phpBB", "Goog... | 0.00000001889 | 13,123,961.00 | 2026/05/04 | 1 | {"A": ["162.43.120.196"], "MX": [{"ho... | 2025/11/04 | WHOIS | 2017/10/18 | 2026/10/31 | 2025/11/01 | (Not displayed by registrant's request) | {"raw_response": ... | |
| jp | kyoei.tokyo.jp | tokyo.jp | Japan (JP) | 219.94.199.23 | ["NGINX"] | 0.00000001775 | 13,054,459.00 | 2026/05/01 | 1 | {"A": ["219.94.199.23"], "MX": [{"hos... | 2026/04/22 | WHOIS | 2019/03/25 | 2027/03/31 | 2026/04/01 | {"raw_response": ... | ||
| jp | f-line.tokyo.jp | tokyo.jp | Japan (JP) | 85.131.215.19 | ["Google Tag Manager", "Apache HTTP S... | 0.00000001598 | 12,822,844.00 | 2026/05/02 | 1 | {"A": ["85.131.215.19"], "MX": [{"hos... | 2025/09/09 | WHOIS | 2018/08/02 | 2026/08/31 | 2025/09/01 | (Not displayed by registrant's request) | {"raw_response": ... | |
| jp | trias.tokyo.jp | tokyo.jp | Japan (JP) | 183.90.245.16 | ["Google Tag Manager", "NGINX"] | 0.00000001495 | 12,915,873.00 | 2026/05/08 | 1 | {"A": ["183.90.245.16"], "MX": [{"hos... | 2025/08/25 | WHOIS | 2018/07/02 | 2026/07/31 | 2025/08/01 | Xserver Inc. | {"raw_response": ... | |
| jp | nehan.tokyo.jp | tokyo.jp | Japan (JP) | 157.7.189.68 | ["Google Tag Manager", "Apache HTTP S... | 0.00000001395 | 13,952,472.00 | 2026/05/07 | 1 | {"A": ["157.7.189.68"], "MX": [{"host... | 2026/04/13 | WHOIS | 2015/03/27 | 2027/03/31 | 2026/04/01 | {"raw_response": ... | ||
| jp | keamane.tokyo.jp | tokyo.jp | Japan (JP) | 182.48.49.223 | ["Google Tag Manager", "WordPress", "... | 0.00000001356 | 12,809,383.00 | 2026/05/06 | 1 | {"A": ["182.48.49.223"], "MX": [{"hos... | 2025/12/07 | WHOIS | 2018/11/15 | 2026/11/30 | 2025/12/01 | The Tokyo Metropolitan Foundation for... | {"raw_response": ... | |
| jp | bousai-machida.tokyo.jp | tokyo.jp | United States (US) | 13.32.121.15 | ["Amazon CloudFront"] | 0.00000001245 | 12,936,967.00 | 2026/05/08 | 1 | {"A": ["13.32.121.15", "13.32.121.27"... | 2026/05/07 | WHOIS | 2023/04/28 | 2026/04/30 | 2025/05/01 | {"raw_response": ... | ||
| jp | mori2ichiba.tokyo.jp | tokyo.jp | Japan (JP) | 157.7.44.179 | ["Apache HTTP Server", "WordPress", "... | 0.00000001228 | 13,939,542.00 | 2026/05/05 | 1 | {"A": ["157.7.44.179"], "MX": [{"host... | 2025/07/05 | WHOIS | 2013/05/16 | 2026/05/31 | 2025/06/01 | (Not displayed by registrant's request) | {"raw_response": ... | |
| jp | kitaku-vplaza.tokyo.jp | tokyo.jp | Japan (JP) | 119.245.211.144 | ["Apache HTTP Server"] | 0.00000001170 | 12,309,057.00 | 2026/05/03 | 1 | {"A": ["119.245.211.144"], "MX": [{"h... | 2026/04/20 | WHOIS | 2016/01/22 | 2027/01/31 | 2026/02/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 |
|---|---|---|
| NGINX | 218 | 19.98 |
| PHP | 196 | 17.97 |
| WordPress | 179 | 16.41 |
| Google Tag Manager | 149 | 13.66 |
| Apache HTTP Server | 141 | 12.92 |
| Google Analytics | 51 | 4.67 |
| 27 | 2.47 | |
| Google reCAPTCHA | 23 | 2.11 |
| Google AdSense | 22 | 2.02 |
| LiteSpeed Web Server | 15 | 1.37 |
| Wix | 14 | 1.28 |
| Cloudflare | 11 | 1.01 |
| Plesk | 11 | 1.01 |
| Shopify | 6 | 0.55 |
| Amazon CloudFront | 5 | 0.46 |
| OpenResty | 4 | 0.37 |
| Laravel | 3 | 0.27 |
| Nuxt.js | 3 | 0.27 |
| ASP.NET | 2 | 0.18 |
| Gravatar | 2 | 0.18 |
| Microsoft IIS | 2 | 0.18 |
| WooCommerce | 2 | 0.18 |
| Pepyaka | 1 | 0.09 |
| AdBlock | 1 | 0.09 |
| CakePHP | 1 | 0.09 |
| Joomla | 1 | 0.09 |
| phpBB | 1 | 0.09 |
| Country | Count Domain | Percentage of Country |
|---|---|---|
| Japan (JP) | 677 | 74.15 |
| 116 | 12.71 | |
| United States (US) | 81 | 8.87 |
| Germany (DE) | 14 | 1.53 |
| Canada (CA) | 13 | 1.42 |
| Switzerland (CH) | 9 | 0.99 |
| Kazakhstan (KZ) | 1 | 0.11 |
| Singapore (SG) | 1 | 0.11 |
| United Kingdom (GB) | 1 | 0.11 |
.tokyo.jp is a regional namespace within Japan’s .jp country-code hierarchy, used to signal a Tokyo-focused web presence. In practice, .tokyo.jp domains support organizations, projects, and individuals that identify with Tokyo’s administrative and cultural sphere, making .tokyo.jp websites a clear geographic cue for users and search engines. We currently index active .tokyo.jp domains; of these, are live and publish DNS records, indicating a high activation rate for this space. Utilization is not limited to Japan alone, with activity observed across countries, reflecting diaspora and multinational use cases. For benchmarking, we monitor weekly and monthly discoveries to track growth and churn over time. Download the complete .tokyo.jp dataset from webatla now.
Established as part of Japan’s structured .jp taxonomy, .tokyo.jp groups registrants aligned with the Tokyo metropolis inside a recognizable geographic label. While policies are defined by the .jp registry and local naming conventions, the zone’s practical appeal lies in clear regional signaling, stable governance, and predictable resolution patterns across .tokyo.jp domains and .tokyo.jp websites. We observe multi-country footprint in countries and modest net new activity, with recorded, suggesting steady but selective adoption. Aggregate visibility remains strong: live properties and resolving hosts point to consistent operational usage. Our historical lens emphasizes continuity rather than hype, useful for long-term digital planning. Download webatla’s .tokyo.jp domain datasets for longitudinal analysis.
Organizations prioritizing localized reach, compliance alignment, and audience trust often select .tokyo.jp domains to anchor services, directories, and civic initiatives to Tokyo. For search and user perception, .tokyo.jp websites convey precise geography, complementing Japanese-language content and local addresses. From public institutions to SMEs and cultural venues, usage patterns favor clarity over volume: active registrations with live sites underline purposeful deployment, while new registrations last week indicates a mature, low-churn zone. Cross-border adopters in countries leverage the label to target Tokyo constituencies without ambiguity. We quantify these behaviors to support procurement, risk assessment, and competitive mapping. Download curated .tokyo.jp datasets from webatla to deepen your 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.
