Jp-store.shop valuation and analysis
Robots.txt Information
| Robot | Path | Permission |
| GoogleBot | / | ✔ |
| BingBot | / | ✔ |
| BaiduSpider | / | ✔ |
| YandexBot | / | ✔ |
Meta Tags
| Title | IIS Windows Server |
| Description | N/A |
| Keywords | N/A |
Server Information
| WebSite | |
| Host IP | 156.225.2.159 |
| Location | Hong Kong |
Related Websites
| Site | Rank |
More to Explore
Jp-store.shop Valuation
|
US$5,359
Last updated: Jun 20, 2022
Jp-store.shop has global traffic rank of 15,651,159. Jp-store.shop has an estimated worth of US$ 5,359, based on its estimated Ads revenue. Jp-store.shop receives approximately 195 unique visitors each day. Its web server is located in Hong Kong, with IP address 156.225.2.159. According to SiteAdvisor, jp-store.shop is unknown to visit. |
Traffic & Worth Estimates
| Purchase/Sale Value | US$5,359 |
| Daily Ads Revenue | US$2 |
| Monthly Ads Revenue | US$88 |
| Yearly Ads Revenue | US$1,071 |
| Daily Unique Visitors | 195 |
| Note: All traffic and earnings values are estimates. | |
Traffic Ranks
| Global Rank | 15,651,159 |
| Delta (90 Days) | 0 |
| Most Popular In Country | N/A |
| Country Rank | N/A |
DNS Records
| Host | Type | TTL | Data |
| jp-store.shop | A | 600 | IP: 156.225.2.159 |
| jp-store.shop | MX | 600 | Priority: 5 Target: mxbiz1.qq.com. |
| jp-store.shop | MX | 600 | Priority: 10 Target: mxbiz2.qq.com. |
| jp-store.shop | NS | 21600 | Target: drought.dnspod.net. |
| jp-store.shop | NS | 21600 | Target: tracy.dnspod.net. |
| jp-store.shop | TXT | 600 | TXT: v=spf1 include:spf.mail.qq.com ~all |
| jp-store.shop | SOA | 180 | MNAME: tracy.dnspod.net. RNAME: freednsadmin.dnspod.com. Serial: 1654838297 Refresh: 3600 Retry: 180 Expire: 1209600 Minimum TTL: 180 |
HTTP Headers
HTTP/1.1 200 OK Content-Type: text/html Last-Modified: Mon, 09 Aug 2021 20:39:19 GMT Accept-Ranges: bytes ETag: "ac95b4a05e8dd71:0" Server: Microsoft-IIS/8.5 X-Powered-By: ASP.NET Date: Mon, 20 Jun 2022 09:33:12 GMT Content-Length: 701 |
Jp-store.shop Whois Information
Server is busy now, please try again later. |