Robot | Path | Permission |
GoogleBot | / | ✔ |
BingBot | / | ✔ |
BaiduSpider | / | ✔ |
YandexBot | / | ✔ |
Title | 大和軒 - 天理 ならまち - |
Description | 天理・ならまち 大和軒のホームページです。 |
Keywords | 天理,ならまち,秋田屋,吉座傳右衛門,和食,中華,居酒屋 |
WebSite | www.yamatoken.co.jp |
Host IP | 219.94.203.118 |
Location | Osaka, Ōsaka, Japan |
Site | Rank |
US$9,191
Last updated: Dec 4, 2020
Yamatoken.co.jp has global traffic rank of 1,856,354. Yamatoken.co.jp has an estimated worth of US$ 9,191, based on its estimated Ads revenue. Yamatoken.co.jp receives approximately 1,678 unique visitors each day. Its web server is located in Osaka, Ōsaka, Japan, with IP address 219.94.203.118. According to SiteAdvisor, yamatoken.co.jp is safe to visit. |
Purchase/Sale Value | US$9,191 |
Daily Ads Revenue | US$5 |
Monthly Ads Revenue | US$151 |
Yearly Ads Revenue | US$1,838 |
Daily Unique Visitors | 1,678 |
Note: All traffic and earnings values are estimates. |
Global Rank | 1,856,354 |
Delta (90 Days) | 0 |
Most Popular In Country | N/A |
Country Rank | N/A |
Host | Type | TTL | Data |
yamatoken.co.jp | A | 21599 | IP: 219.94.203.118 |
yamatoken.co.jp | MX | 21599 | Priority: 0 Target: yamatoken.co.jp. |
yamatoken.co.jp | NS | 21599 | Target: ns2.xserver.jp. |
yamatoken.co.jp | NS | 21599 | Target: ns3.xserver.jp. |
yamatoken.co.jp | NS | 21599 | Target: ns1.xserver.jp. |
yamatoken.co.jp | SOA | 21599 | MNAME: ns1.xserver.jp. RNAME: root.xserver.jp. Serial: 0 Refresh: 10800 Retry: 3600 Expire: 604800 Minimum TTL: 3600 |
HTTP/1.1 200 OK Server: nginx Date: Fri, 04 Dec 2020 22:00:46 GMT Content-Type: text/html; charset=UTF-8 Transfer-Encoding: chunked Connection: keep-alive Vary: Accept-Encoding |
a. [Domain Name] YAMATOKEN.CO.JP g. [Organization] YAMATO-KEN CO.,LTD. l. [Organization Type] Company m. [Administrative Contact] YI2479JP n. [Technical Contact] SY7696JP p. [Name Server] ns1.xserver.jp p. [Name Server] ns2.xserver.jp p. [Name Server] ns3.xserver.jp p. [Name Server] ns4.xserver.jp p. [Name Server] ns5.xserver.jp s. [Signing Key] [State] Connected (2021/05/31) [Registered Date] 2000/05/24 [Connected Date] 2000/06/13 [Last Update] 2020/06/01 01:03:27 (JST) |