Wellkasa.app valuation and analysis

Wellkasa.app has global traffic rank of 2,381,817. Wellkasa.app has an estimated worth of US$ 14,299, based on its estimated Ads revenue. Wellkasa.app receives approximately 1,305 unique visitors each day. Its web server is located in Columbus, Ohio, United States, with IP address 3.138.74.8. According to SiteAdvisor, wellkasa.app is unknown to visit.

HTTP/1.1 301 Moved Permanently
Server: awselb/2.0
Date: Tue, 18 Jan 2022 10:02:25 GMT
Content-Type: text/html
Content-Length: 134
Connection: keep-alive
Location: https://wellkasa.app:443/

HTTP/2 301 
date: Tue, 18 Jan 2022 10:02:26 GMT
content-type: text/html; charset=UTF-8
content-length: 346
location: https://wellkasa.app/home
server: Apache/2.4.41 (Ubuntu)
access-control-allow-origin: *
access-control-allow-methods: POST, GET, OPTIONS, PUT, DELETE
access-control-allow-headers: Content-Type, X-Auth-Token, Origin, Authorization
set-cookie: XSRF-TOKEN=eyJpdiI6InlVQTAvMTRUWE9UMmRCTEMxRlRHbGc9PSIsInZhbHVlIjoiNWlMYUI4elcrenVZRTdLK1p3Q3FRcGRpRDVlVVQrVS9aNWY3a05kQk95aUJzQXZFaVIrMEYrdzdsejRoaEphSkxHOFc3ZjZCMVM1U0JISnIxS3VHRmtoVy9KSGxoWlUxcEtnK2NDT0l0a3JrMWNLM29wRWZRZEV6U3dPM21ja2oiLCJtYWMiOiI3YzljYTU0NGZlM2I5MzA1Yzc4MzljMDRmYTYxNTE5ZWY3NTQ0N2NkMDllYmM3ODMxZjljMWY1YjIzOGFmMGE5IiwidGFnIjoiIn0%3D; expires=Tue, 18-Jan-2022 12:02:26 GMT; Max-Age=7200; path=/; samesite=lax
set-cookie: wellkasa_session=eyJpdiI6IlZrYkFuVlRmVHY5WXVUZVpPZFEvVVE9PSIsInZhbHVlIjoiUXJzS1JPWnBHbEhEb3RmVGZYK2llZnlmMVhzakZiVW5qa1psaXlaRXNmVGtUSndKR3pIZTdVRnA5bnNIRGRwd1p4Sk8zRk9zd2MxNWIyUWlIVmRydWdjRUd1TWlZZmtseDZYL09rRnFBMVBtRldycFJ2bHB4cjlDZG5oTFpiSWYiLCJtYWMiOiIyOGQ3YjQ1YzI4ZjkxNzY3OGIyNDEyNzMyMmRjOGU5MmU1MTE1MWIzNmQ4Y2M1NzkzYzRjYTcxM2EwYzhiZWJlIiwidGFnIjoiIn0%3D; expires=Tue, 18-Jan-2022 12:02:26 GMT; Max-Age=7200; path=/; httponly; samesite=lax

HTTP/2 301 
date: Tue, 18 Jan 2022 10:02:26 GMT
content-type: text/html; charset=iso-8859-1
content-length: 318
location: http://wellkasa.app/public/home/
server: Apache/2.4.41 (Ubuntu)

HTTP/1.1 301 Moved Permanently
Server: awselb/2.0
Date: Tue, 18 Jan 2022 10:02:26 GMT
Content-Type: text/html
Content-Length: 134
Connection: keep-alive
Location: https://wellkasa.app:443/public/home/

HTTP/2 301 
date: Tue, 18 Jan 2022 10:02:26 GMT
content-type: text/html; charset=UTF-8
content-length: 0
location: https://wellkasa.app/home/
server: Apache/2.4.41 (Ubuntu)
vary: X-Forwarded-Proto
expires: Wed, 11 Jan 1984 05:00:00 GMT
cache-control: no-cache, must-revalidate, max-age=0
x-redirect-by: WordPress

HTTP/2 200 
date: Tue, 18 Jan 2022 10:02:26 GMT
content-type: text/html; charset=UTF-8
server: Apache/2.4.41 (Ubuntu)
vary: X-Forwarded-Proto,Accept-Encoding
last-modified: Tue, 18 Jan 2022 10:02:26 GMT
expires: Tue, 18 Jan 2022 11:02:26 GMT
pragma: public
cache-control: max-age=3600, public
etag: "cb108c4c22cb0fe47f5eceba6edf896c"

Domain Name: wellkasa.app
Registry Domain ID: 459F3175B-APP
Registrar WHOIS Server: whois.nic.google
Registrar URL: https://www.godaddy.com/
Updated Date: 2021-08-16T16:13:01Z
Creation Date: 2021-01-24T18:51:46Z
Registry Expiry Date: 2023-01-24T18:51:46Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: abuse@godaddy.com
Registrar Abuse Contact Phone: +1.4806242505
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: Wellkasa Inc.
Registrant Street: REDACTED FOR PRIVACY
Registrant Street:
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: Arizona
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 Street:
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 Street:
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 Street:
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: ns-1522.awsdns-62.org
Name Server: ns-1749.awsdns-26.co.uk
Name Server: ns-503.awsdns-62.com
Name Server: ns-787.awsdns-34.net
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.