Robot | Path | Permission |
GoogleBot | / | ✔ |
BingBot | / | ✔ |
BaiduSpider | / | ✔ |
YandexBot | / | ✔ |
Title | N/A |
Description | N/A |
Keywords | N/A |
WebSite | www.ran.co.jp |
Host IP | 60.43.228.20 |
Location | Japan |
Site | Rank |
US$8,897
Last updated: May 23, 2020
Ran.co.jp has global traffic rank of 1,917,252. Ran.co.jp has an estimated worth of US$ 8,897, based on its estimated Ads revenue. Ran.co.jp receives approximately 1,625 unique visitors each day. Its web server is located in Japan, with IP address 60.43.228.20. According to SiteAdvisor, ran.co.jp is safe to visit. |
Purchase/Sale Value | US$8,897 |
Daily Ads Revenue | US$4 |
Monthly Ads Revenue | US$146 |
Yearly Ads Revenue | US$1,779 |
Daily Unique Visitors | 1,625 |
Note: All traffic and earnings values are estimates. |
Global Rank | 1,917,252 |
Delta (90 Days) | 0 |
Most Popular In Country | N/A |
Country Rank | N/A |
Host | Type | TTL | Data |
ran.co.jp | A | 3599 | IP: 60.43.228.20 |
ran.co.jp | MX | 3599 | Priority: 10 Target: ran.co.jp. |
ran.co.jp | NS | 59 | Target: ns-220.dns.jp-w1.cloudn-service.com. |
ran.co.jp | NS | 59 | Target: ns-221.dns.us-e1.cloudn-service.com. |
ran.co.jp | NS | 59 | Target: ns-219.dns.jp-e1.cloudn-service.com. |
ran.co.jp | TXT | 3599 | TXT: v=spf1 a include:_spf.bizmw.com ~all |
ran.co.jp | SOA | 59 | MNAME: ns-219.dns.jp-e1.cloudn-service.com. RNAME: root.cloudn2.net. Serial: 1 Refresh: 7200 Retry: 900 Expire: 1209600 Minimum TTL: 86400 |
HTTP/1.1 200 OK Date: Sat, 23 May 2020 07:17:12 GMT Server: Apache Last-Modified: Sun, 08 Nov 2015 05:50:00 GMT ETag: "aff-524010c17b200" Accept-Ranges: bytes Content-Length: 2815 Content-Type: text/html |
a. [Domain Name] RAN.CO.JP g. [Organization] infomation Center Ran ,inc. l. [Organization Type] Corporation m. [Administrative Contact] NO252JP n. [Technical Contact] NO252JP p. [Name Server] ns-219.dns.jp-e1.cloudn-service.com p. [Name Server] ns-220.dns.jp-w1.cloudn-service.com p. [Name Server] ns-221.dns.us-e1.cloudn-service.com s. [Signing Key] [State] Connected (2020/07/31) [Registered Date] 1998/07/07 [Connected Date] 1998/07/09 [Last Update] 2019/08/01 01:07:13 (JST) |