Robot | Path | Permission |
GoogleBot | / | ✔ |
BingBot | / | ✔ |
BaiduSpider | / | ✔ |
YandexBot | / | ✔ |
Title | |
Description | N/A |
Keywords | N/A |
WebSite | yeay.jp |
Host IP | 52.197.44.244 |
Location | United States |
Site | Rank |
US$1,219,684
Last updated:
yeay.jp has Semrush global rank of 8,677,912. yeay.jp has an estimated worth of US$ 1,219,684, based on its estimated Ads revenue. yeay.jp receives approximately 140,733 unique visitors each day. Its web server is located in United States, with IP address 52.197.44.244. According to SiteAdvisor, yeay.jp is safe to visit. |
Purchase/Sale Value | US$1,219,684 |
Daily Ads Revenue | US$1,126 |
Monthly Ads Revenue | US$33,776 |
Yearly Ads Revenue | US$405,311 |
Daily Unique Visitors | 9,383 |
Note: All traffic and earnings values are estimates. |
Host | Type | TTL | Data |
yeay.jp. | A | 300 | IP: 52.197.44.244 |
yeay.jp. | NS | 86400 | NS Record: ns-1431.awsdns-50.org. |
yeay.jp. | NS | 86400 | NS Record: ns-1620.awsdns-10.co.uk. |
yeay.jp. | NS | 86400 | NS Record: ns-63.awsdns-07.com. |
yeay.jp. | NS | 86400 | NS Record: ns-713.awsdns-25.net. |
yeay.jp. | MX | 300 | MX Record: 5 alt2.aspmx.l.google.com. |
yeay.jp. | MX | 300 | MX Record: 1 aspmx.l.google.com. |
yeay.jp. | MX | 300 | MX Record: 10 alt3.aspmx.l.google.com. |
yeay.jp. | MX | 300 | MX Record: 10 alt4.aspmx.l.google.com. |
yeay.jp. | MX | 300 | MX Record: 5 alt1.aspmx.l.google.com. |
yeay.jp. | TXT | 300 | TXT Record: pardot_333271_*=8f66ebbdaf811960d6c5c733449656bd988318876d5bd8aa926e893dc6101b18 |
yeay.jp. | TXT | 300 | TXT Record: google-site-verification=JDBuh--lKK1lkrgNc35ut3CifjUdRQBN5N3nu2YD75I |
yeay.jp. | TXT | 300 | TXT Record: google-site-verification=Pbv_iFQfPFOYqig4BQvGHcmwL_WoytGTrrQ0KRrAUl8 |
HTTP/1.1 200 OK Server: nginx/1.16.1 Date: Thu, 21 Oct 2021 19:17:29 GMT Content-Type: text/html Content-Length: 54 Last-Modified: Wed, 10 Feb 2021 03:18:06 GMT Connection: keep-alive ETag: "6023506e-36" Accept-Ranges: bytes |
Cannot process your search request. Service currently unavailable due to incoming of a large amount of requests. Try again later. |