Robot | Path | Permission |
GoogleBot | / | ✔ |
BingBot | / | ✔ |
BaiduSpider | / | ✔ |
YandexBot | / | ✔ |
Title | |
Description | N/A |
Keywords | N/A |
WebSite | zenk.co.jp |
Host IP | 157.7.231.224 |
Location | Japan |
Site | Rank |
US$735,570
Last updated:
zenk.co.jp has Semrush global rank of 14,389,268. zenk.co.jp has an estimated worth of US$ 735,570, based on its estimated Ads revenue. zenk.co.jp receives approximately 84,874 unique visitors each day. Its web server is located in Japan, with IP address 157.7.231.224. According to SiteAdvisor, zenk.co.jp is safe to visit. |
Purchase/Sale Value | US$735,570 |
Daily Ads Revenue | US$679 |
Monthly Ads Revenue | US$20,370 |
Yearly Ads Revenue | US$244,436 |
Daily Unique Visitors | 5,659 |
Note: All traffic and earnings values are estimates. |
Host | Type | TTL | Data |
zenk.co.jp. | A | 597 | IP: 157.7.231.224 |
zenk.co.jp. | NS | 600 | NS Record: dns01.gmoserver.jp. |
zenk.co.jp. | NS | 600 | NS Record: dns02.gmoserver.jp. |
zenk.co.jp. | MX | 600 | MX Record: 30 aspmx3.googlemail.com. |
zenk.co.jp. | MX | 600 | MX Record: 10 aspmx.l.google.com. |
zenk.co.jp. | MX | 600 | MX Record: 30 aspmx5.googlemail.com. |
zenk.co.jp. | MX | 600 | MX Record: 20 alt2.aspmx.l.google.com. |
zenk.co.jp. | MX | 600 | MX Record: 30 aspmx4.googlemail.com. |
zenk.co.jp. | MX | 600 | MX Record: 20 alt1.aspmx.l.google.com. |
zenk.co.jp. | MX | 600 | MX Record: 30 aspmx2.googlemail.com. |
zenk.co.jp. | TXT | 600 | TXT Record: v=spf1 include:aspmx.googlemail.com ~all |
HTTP/1.1 301 Moved Permanently Date: Sat, 30 Oct 2021 10:48:30 GMT Server: Apache X-Powered-By: PHP/5.5.38 X-Pingback: https://zenk.co.jp/test_wordpress/wp/xmlrpc.php Set-Cookie: redirect_count=1; path=/ Location: https://zenk.co.jp/ Content-Type: text/html; charset=UTF-8 HTTP/1.1 200 OK Date: Sat, 30 Oct 2021 10:48:31 GMT Server: Apache X-Powered-By: PHP/5.5.38 X-Pingback: https://zenk.co.jp/test_wordpress/wp/xmlrpc.php Content-Type: text/html; charset=UTF-8 |
Cannot process your search request. Service currently unavailable due to incoming of a large amount of requests. Try again later. |