Robot | Path | Permission |
GoogleBot | / | ✔ |
BingBot | / | ✔ |
BaiduSpider | / | ✔ |
YandexBot | / | ✔ |
Title | MyCrush |
Description | N/A |
Keywords | N/A |
WebSite | www.mycrush.app |
Host IP | 104.26.9.18 |
Location | United States |
Site | Rank |
nctmedia.online |
nf1i7fk75d.com |
nftbaoyi.com |
noraeinc.com |
ockerfisher.top |
offline-games.site |
openhentai.net |
oyse.shop |
paimaiguakao.com |
paltryvariety.com |
foxkmail.com |
freedumqua.com |
US$4,435
Last updated: Sep 25, 2024
Mycrush.app has global traffic rank of 18,880,226. Mycrush.app has an estimated worth of US$ 4,435, based on its estimated Ads revenue. Mycrush.app receives approximately 162 unique visitors each day. Its web server is located in United States, with IP address 104.26.9.18. According to SiteAdvisor, mycrush.app is unknown to visit. |
Purchase/Sale Value | US$4,435 |
Daily Ads Revenue | US$2 |
Monthly Ads Revenue | US$72 |
Yearly Ads Revenue | US$887 |
Daily Unique Visitors | 162 |
Note: All traffic and earnings values are estimates. |
Global Rank | 18,880,226 |
Delta (90 Days) | 0 |
Most Popular In Country | N/A |
Country Rank | N/A |
Host | Type | TTL | Data |
mycrush.app | A | 300 | IP: 104.26.9.18 |
mycrush.app | A | 300 | IP: 172.67.70.179 |
mycrush.app | A | 300 | IP: 104.26.8.18 |
mycrush.app | AAAA | 300 | IPv6: 2606:4700:20:0:0:0:681a:912 |
mycrush.app | AAAA | 300 | IPv6: 2606:4700:20:0:0:0:ac43:46b3 |
mycrush.app | AAAA | 300 | IPv6: 2606:4700:20:0:0:0:681a:812 |
mycrush.app | MX | 3600 | Priority: 1 Target: aspmx.l.google.com. |
mycrush.app | MX | 3600 | Priority: 10 Target: alt3.aspmx.l.google.com. |
mycrush.app | MX | 3600 | Priority: 5 Target: alt2.aspmx.l.google.com. |
mycrush.app | MX | 3600 | Priority: 10 Target: alt4.aspmx.l.google.com. |
mycrush.app | MX | 3600 | Priority: 5 Target: alt1.aspmx.l.google.com. |
mycrush.app | NS | 21600 | Target: adam.ns.cloudflare.com. |
mycrush.app | NS | 21600 | Target: emely.ns.cloudflare.com. |
mycrush.app | TXT | 3600 | TXT: v=spf1 include:_spf.google.com -all |
mycrush.app | TXT | 3600 | TXT: google-site-verification=cDc3iKXIg2-ZCB2JXrBz1CSeXScZrhE1NZx4W7br45E |
mycrush.app | SOA | 1800 | MNAME: adam.ns.cloudflare.com. RNAME: dns.cloudflare.com. Serial: 2351331270 Refresh: 10000 Retry: 2400 Expire: 604800 Minimum TTL: 1800 |
HTTP/1.1 301 Moved Permanently Date: Wed, 25 Sep 2024 07:20:30 GMT Content-Type: text/html Content-Length: 167 Connection: keep-alive Cache-Control: max-age=3600 Expires: Wed, 25 Sep 2024 08:20:30 GMT Location: https://mycrush.app/ Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v4?s=3kKPaZSIHmPjvwp9nhO9s325n1w0fMzlERf1jjPDalHJLo%2B1GTd4kxcxnEZAqUqxtxxdQokfwIdAZbZxnLBmh%2FKVLyuuBj8eQBY6P6GN7cOmKTheRtF3jwtIoe1vjz6y5fYOx8oOOluk"}],"group":"cf-nel","max_age":604800} NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800} Server: cloudflare CF-RAY: 8c894087cb83cd3c-LHR HTTP/2 200 date: Wed, 25 Sep 2024 07:20:31 GMT content-type: text/html last-modified: Fri, 20 Sep 2024 11:55:43 GMT cf-cache-status: DYNAMIC report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v4?s=h5CFtoeiIT5OaMk6utKUMViwC%2BRML7wJMDlER2zXApxDIjWm9af5u9cvt9QZnUXaCAtO0C1Rbtcba1CVE75Iusoiu5ljN%2FtSicuFqdKH4aphqcGposw0hlSwqp5QbvvBKvHKYRrPDZOj"}],"group":"cf-nel","max_age":604800} nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800} server: cloudflare cf-ray: 8c89408839996413-LHR |
Domain Name: mycrush.app Registry Domain ID: DFD7BFA34-APP Registrar WHOIS Server: whois.cloudflare.com Registrar URL: None Updated Date: 2024-09-15T04:08:43Z Creation Date: 2023-10-10T11:39:46Z Registry Expiry Date: 2025-10-10T11:39:46Z Registrar: CloudFlare, Inc. Registrar IANA ID: 1910 Registrar Abuse Contact Email: registrar-abuse@cloudflare.com Registrar Abuse Contact Phone: +1.4153197517 Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Registry Registrant ID: REDACTED FOR PRIVACY Registrant Name: REDACTED FOR PRIVACY Registrant Organization: RED PANDA APP LLC Registrant Street: REDACTED FOR PRIVACY Registrant City: REDACTED FOR PRIVACY Registrant State/Province: IN Registrant Postal Code: REDACTED FOR PRIVACY Registrant Country: US Registrant Phone: REDACTED FOR PRIVACY Registrant Email: 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. Registry Admin ID: REDACTED FOR PRIVACY Admin Name: REDACTED FOR PRIVACY Admin Organization: REDACTED FOR PRIVACY Admin Street: REDACTED FOR PRIVACY Admin City: REDACTED FOR PRIVACY Admin State/Province: REDACTED FOR PRIVACY Admin Postal Code: REDACTED FOR PRIVACY Admin Country: REDACTED FOR PRIVACY Admin Phone: REDACTED FOR PRIVACY Admin Email: 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. Registry Tech ID: REDACTED FOR PRIVACY Tech Name: REDACTED FOR PRIVACY Tech Organization: REDACTED FOR PRIVACY Tech Street: REDACTED FOR PRIVACY Tech City: REDACTED FOR PRIVACY Tech State/Province: REDACTED FOR PRIVACY Tech Postal Code: REDACTED FOR PRIVACY Tech Country: REDACTED FOR PRIVACY Tech Phone: REDACTED FOR PRIVACY Tech Email: 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. Registry Billing ID: REDACTED FOR PRIVACY Billing Name: REDACTED FOR PRIVACY Billing Organization: REDACTED FOR PRIVACY Billing Street: REDACTED FOR PRIVACY Billing City: REDACTED FOR PRIVACY Billing State/Province: REDACTED FOR PRIVACY Billing Postal Code: REDACTED FOR PRIVACY Billing Country: REDACTED FOR PRIVACY Billing Phone: REDACTED FOR PRIVACY Billing Email: 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. Name Server: adam.ns.cloudflare.com Name Server: emely.ns.cloudflare.com DNSSEC: unsigned URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/ 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. You may also request underlying Registrant data via ICANN's RDRS service (https://rdrs.icann.org/). |