kjbc.co.jp valuation and analysis
Robots.txt Information
| Robot | Path | Permission |
| GoogleBot | / | ✔ |
| BingBot | / | ✔ |
| BaiduSpider | / | ✔ |
| YandexBot | / | ✔ |
Meta Tags
| Title | |
| Description | N/A |
| Keywords | N/A |
Server Information
| WebSite | |
| Host IP | 153.122.57.76 |
| Location | Japan |
Related Websites
| Site | Rank |
More to Explore
kjbc.co.jp Valuation
|
US$273,135
Last updated:
kjbc.co.jp has Semrush global rank of 38,751,200. kjbc.co.jp has an estimated worth of US$ 273,135, based on its estimated Ads revenue. kjbc.co.jp receives approximately 31,516 unique visitors each day. Its web server is located in Japan, with IP address 153.122.57.76. According to SiteAdvisor, kjbc.co.jp is safe to visit. |
Traffic & Worth Estimates
| Purchase/Sale Value | US$273,135 |
| Daily Ads Revenue | US$253 |
| Monthly Ads Revenue | US$7,564 |
| Yearly Ads Revenue | US$90,765 |
| Daily Unique Visitors | 2,102 |
| Note: All traffic and earnings values are estimates. | |
DNS Records
| Host | Type | TTL | Data |
| kjbc.co.jp. | A | 21600 | IP: 153.122.57.76 |
| kjbc.co.jp. | NS | 21600 | NS Record: ns-1236.awsdns-26.org. |
| kjbc.co.jp. | NS | 21600 | NS Record: ns-1767.awsdns-28.co.uk. |
| kjbc.co.jp. | NS | 21600 | NS Record: ns-93.awsdns-11.com. |
| kjbc.co.jp. | NS | 21600 | NS Record: ns-993.awsdns-60.net. |
| kjbc.co.jp. | MX | 21600 | MX Record: 10 kjbc.sakura.ne.jp. |
| kjbc.co.jp. | TXT | 21600 | TXT Record: v=spf1 +ip4:153.122.57.76 ~all |
| kjbc.co.jp. | TXT | 21600 | TXT Record: v=spf1 a:www3021.sakura.ne.jp mx ~all |
HTTP Headers
HTTP/1.1 302 Found Date: Mon, 24 Jan 2022 09:15:09 GMT Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/7.4.12 Location: https://www.kjbc.co.jp/ Content-Type: text/html; charset=iso-8859-1 HTTP/1.1 403 Forbidden Date: Mon, 24 Jan 2022 09:15:11 GMT Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/7.4.12 Content-Type: text/html; charset=iso-8859-1 |
kjbc.co.jp Whois Information
Cannot process your search request. Service currently unavailable due to incoming of a large amount of requests. Try again later. |