elder-homecare.co.jp valuation and analysis
Robots.txt Information
| Robot | Path | Permission |
| GoogleBot | / | ✔ |
| BingBot | / | ✔ |
| BaiduSpider | / | ✔ |
| YandexBot | / | ✔ |
Meta Tags
| Title | q̗LVlz[EZ^Vlz[bG_[z[PA |
| Description | qs(_ސ)?SɗLVlz[EZ^Vlz[?Ă܂BkCyɂ₢킹B |
| Keywords | Vlz[,LVlz[,Z^Vlz[,,q,_ސ |
Server Information
| WebSite | |
| Host IP | 150.95.254.16 |
| Location | Japan |
Related Websites
| Site | Rank |
More to Explore
elder-homecare.co.jp Valuation
|
US$955
Last updated: 2022-07-05 11:33:47
elder-homecare.co.jp has Semrush global rank of 0. elder-homecare.co.jp has an estimated worth of US$ 955, based on its estimated Ads revenue. elder-homecare.co.jp receives approximately 110 unique visitors each day. Its web server is located in Japan, with IP address 150.95.254.16. According to SiteAdvisor, elder-homecare.co.jp is safe to visit. |
Traffic & Worth Estimates
| Purchase/Sale Value | US$955 |
| Daily Ads Revenue | US$0 |
| Monthly Ads Revenue | US$26 |
| Yearly Ads Revenue | US$317 |
| Daily Unique Visitors | 7 |
| Note: All traffic and earnings values are estimates. | |
DNS Records
| Host | Type | TTL | Data |
| elder-homecare.co.jp. | A | 599 | IP: 150.95.254.16 |
| elder-homecare.co.jp. | NS | 600 | NS Record: dns02.gmoserver.jp. |
| elder-homecare.co.jp. | NS | 600 | NS Record: dns01.gmoserver.jp. |
| elder-homecare.co.jp. | MX | 600 | MX Record: 10 mx17.gmoserver.jp. |
| elder-homecare.co.jp. | TXT | 600 | TXT Record: v=spf1 include:spf17.gmoserver.jp ~all |
HtmlToTextCheckTime:2022-07-05 11:33:47
| q̗LVlz[EZ^Vlz[bG_[z[PA LVlz[ b fCT[rX b 邾[̉L b ЊTv b X^bt,X^bt,ŌX^bt,}X^btWĂ܂B ڂ́ALւ₢킹B 0467-38-1251 @nƒc@qx@X`18܂ LVlz[i{݂̂ēj fCT[rX 邾[̉L ЊTv z[ b X^btW b lیj b ₢킹 Copyright (c) 2009 Elder Homecare. All Rights |
HTTP Headers
HTTP/1.1 200 OK Date: Fri, 29 Oct 2021 02:31:35 GMT Server: Apache Last-Modified: Mon, 20 Aug 2018 05:19:09 GMT Accept-Ranges: bytes Content-Length: 2875 Content-Type: text/html |
elder-homecare.co.jp Whois Information
Cannot process your search request. Service currently unavailable due to incoming of a large amount of requests. Try again later. |