Robot | Path | Permission |
GoogleBot | / | ✔ |
BingBot | / | ✔ |
BaiduSpider | / | ✔ |
YandexBot | / | ✔ |
Title | 果醬珍珍•JamJam - 健忘女孩Jam的學習筆記和生活雜記 |
Description | 健忘女孩Jam的學習筆記和生活雜記 |
Keywords | N/A |
WebSite | www.jamleecute.web.app |
Host IP | 151.101.1.195 |
Location | United States |
Site | Rank |
US$4,823
Last updated: Jul 27, 2021
Jamleecute.web.app has global traffic rank of 3,519,469. Jamleecute.web.app has an estimated worth of US$ 4,823, based on its estimated Ads revenue. Jamleecute.web.app receives approximately 881 unique visitors each day. Its web server is located in United States, with IP address 151.101.1.195. According to SiteAdvisor, jamleecute.web.app is safe to visit. |
Purchase/Sale Value | US$4,823 |
Daily Ads Revenue | US$2 |
Monthly Ads Revenue | US$79 |
Yearly Ads Revenue | US$964 |
Daily Unique Visitors | 881 |
Note: All traffic and earnings values are estimates. |
Global Rank | 3,519,469 |
Delta (90 Days) | 0 |
Most Popular In Country | N/A |
Country Rank | N/A |
Host | Type | TTL | Data |
jamleecute.web.app | A | 21599 | IP: 151.101.1.195 |
jamleecute.web.app | A | 21599 | IP: 151.101.65.195 |
HTTP/1.1 301 Moved Permanently Server: Varnish Retry-After: 0 Location: https://jamleecute.web.app/ Content-Length: 0 Accept-Ranges: bytes Date: Tue, 27 Jul 2021 21:09:25 GMT Connection: close X-Served-By: cache-lga21950-LGA X-Cache: HIT X-Cache-Hits: 0 X-Timer: S1627420165.178316,VS0,VE0 HTTP/2 200 cache-control: max-age=3600 content-type: text/html; charset=utf-8 etag: "31beac6e49d19ca8772b730223fb986862ef717d029dd152f826d5473187d118" last-modified: Thu, 22 Jul 2021 12:50:03 GMT strict-transport-security: max-age=31556926; includeSubDomains; preload accept-ranges: bytes date: Tue, 27 Jul 2021 21:09:25 GMT x-served-by: cache-lga21955-LGA x-cache: MISS x-cache-hits: 0 x-timer: S1627420165.223591,VS0,VE163 vary: x-fh-requested-host, accept-encoding content-length: 42430 |
Nameserver not found. Please query the WHOIS server of the owning registrar identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. |