win-tech.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 | 183.90.183.26 |
| Location | Japan |
Related Websites
| Site | Rank |
More to Explore
win-tech.jp Valuation
|
US$1,737
Last updated:
win-tech.jp has Semrush global rank of 0. win-tech.jp has an estimated worth of US$ 1,737, based on its estimated Ads revenue. win-tech.jp receives approximately 200 unique visitors each day. Its web server is located in Japan, with IP address 183.90.183.26. According to SiteAdvisor, win-tech.jp is safe to visit. |
Traffic & Worth Estimates
| Purchase/Sale Value | US$1,737 |
| Daily Ads Revenue | US$1 |
| Monthly Ads Revenue | US$48 |
| Yearly Ads Revenue | US$577 |
| Daily Unique Visitors | 13 |
| Note: All traffic and earnings values are estimates. | |
DNS Records
| Host | Type | TTL | Data |
| win-tech.jp. | A | 3600 | IP: 183.90.183.26 |
| win-tech.jp. | NS | 3600 | NS Record: ns2.value-domain.com. |
| win-tech.jp. | NS | 3600 | NS Record: ns1.value-domain.com. |
| win-tech.jp. | MX | 3600 | MX Record: 10 win-tech.jp. |
| win-tech.jp. | TXT | 3600 | TXT Record: v=spf1 ip4:183.90.183.26 ~all |
HTTP Headers
HTTP/1.1 302 Found Date: Thu, 06 Jan 2022 08:45:59 GMT Content-Type: text/html; charset=iso-8859-1 Content-Length: 208 Connection: keep-alive Location: https://www.win-tech.jp/ X-Cache-Status: HIT HTTP/2 200 date: Thu, 06 Jan 2022 08:46:00 GMT content-type: text/html; charset=UTF-8 content-length: 299380 vary: Accept-Encoding strict-transport-security: max-age=31536000 vary: User-Agent,Accept-Encoding last-modified: Thu, 06 Jan 2022 03:28:48 GMT accept-ranges: bytes cache-control: max-age=0, no-cache, no-store, must-revalidate pragma: no-cache expires: Mon, 29 Oct 1923 20:30:00 GMT x-cache-status: MISS |
win-tech.jp Whois Information
Cannot process your search request. Service currently unavailable due to incoming of a large amount of requests. Try again later. |