Robot | Path | Permission |
GoogleBot | / | ✔ |
BingBot | / | ✔ |
BaiduSpider | / | ✔ |
YandexBot | / | ✔ |
Title | 株式会社メディウェルズ きらめきグループ 訪問看護 訪問リハビリ デイサービス |
Description | N/A |
Keywords | N/A |
WebSite | |
Host IP | 49.212.235.157 |
Location | Osaka, Ōsaka, Japan |
Site | Rank |
US$37,183
Last updated: Nov 22, 2020
Kiramekiriha.co.jp has global traffic rank of 1,379,973. Kiramekiriha.co.jp has an estimated worth of US$ 37,183, based on its estimated Ads revenue. Kiramekiriha.co.jp receives approximately 2,263 unique visitors each day. Its web server is located in Osaka, Ōsaka, Japan, with IP address 49.212.235.157. According to SiteAdvisor, kiramekiriha.co.jp is unknown to visit. |
Purchase/Sale Value | US$37,183 |
Daily Ads Revenue | US$20 |
Monthly Ads Revenue | US$611 |
Yearly Ads Revenue | US$7,436 |
Daily Unique Visitors | 2,263 |
Note: All traffic and earnings values are estimates. |
Global Rank | 1,379,973 |
Delta (90 Days) | 0 |
Most Popular In Country | N/A |
Country Rank | N/A |
Host | Type | TTL | Data |
kiramekiriha.co.jp | A | 3599 | IP: 49.212.235.157 |
kiramekiriha.co.jp | MX | 3599 | Priority: 10 Target: kiramekiriha.co.jp. |
kiramekiriha.co.jp | NS | 3599 | Target: ns2.dns.ne.jp. |
kiramekiriha.co.jp | NS | 3599 | Target: ns1.dns.ne.jp. |
kiramekiriha.co.jp | TXT | 3599 | TXT: v=spf1 a:www3417.sakura.ne.jp mx ~all |
kiramekiriha.co.jp | SOA | 3599 | MNAME: master.dns.ne.jp. RNAME: tech.sakura.ad.jp. Serial: 2018021124 Refresh: 3600 Retry: 900 Expire: 3600000 Minimum TTL: 3600 |
HTTP/1.1 200 OK Server: nginx Date: Sun, 22 Nov 2020 11:49:28 GMT Content-Type: text/html; charset=UTF-8 Transfer-Encoding: chunked Connection: keep-alive Link: <http://kiramekiriha.co.jp/group/wp-json/>; rel="https://api.w.org/" Vary: Accept-Encoding |
a. [Domain Name] KIRAMEKIRIHA.CO.JP g. [Organization] mediwels l. [Organization Type] Corporation m. [Administrative Contact] TK72932JP n. [Technical Contact] KW419JP p. [Name Server] ns1.dns.ne.jp p. [Name Server] ns2.dns.ne.jp s. [Signing Key] [State] Connected (2020/12/31) [Registered Date] 2017/12/22 [Connected Date] 2017/12/22 [Last Update] 2020/01/01 01:15:29 (JST) |