lifesavvy.com
/.well-known/
resources for
lifesavvy.com
Site Scan
Site Details
Site Domain | lifesavvy.com |
Base Domain | lifesavvy.com |
Added | 2021-02-28T10:27:06+00:00 |
Last Scan | 2024-08-28T21:03:34+00:00 |
Next Scan | 2024-11-26T21:03:34+00:00 |
Found Resources
Resource | Found At | Scan Status |
---|---|---|
ads.txt | 2024-02-01T20:24:51+00:00 | Failed |
robots.txt | 2024-02-01T20:24:51+00:00 | Failed |
Authorized Digital Sellers
Resource Details
Resource | ads.txt |
Status | Failed |
Failure Stage | Checking robots.txt. |
Failure Reason | Couldn't connect to server. |
Archive | Check Archive |
Scan Requests (4)
URL | https://lifesavvy.com/ads.txt |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | https://www.lifesavvy.com/ads.txt |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | http://lifesavvy.com/ads.txt |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | http://www.lifesavvy.com/ads.txt |
Result | Failed checking robots.txt - Couldn't connect to server. |
Last Successful Scan
Scanned | 2024-02-01T20:24:51+00:00 |
URL | https://lifesavvy.com/ads.txt |
Redirect | https://www.lifesavvy.com/ads.txt |
Redirect Domain | www.lifesavvy.com |
Redirect Base | lifesavvy.com |
Domain IPs | 151.101.130.217, 151.101.194.217, 151.101.2.217, 151.101.66.217 |
Redirect IPs | 151.101.130.49, 151.101.194.49, 151.101.2.49, 151.101.66.49 |
Response IP | 199.232.46.49 |
Found | Yes - View Resource |
Hash | f6e0e94aa6f6e5c30f6b6c5ab0d8afd8430b5c24781f8b6b03ae5ceaedbf5249 |
SimHash | 86c6841e6362 |
Authorized Digital Sellers for Apps
Resource Details
Resource | app-ads.txt |
Status | Failed |
Failure Stage | Checking robots.txt. |
Failure Reason | Couldn't connect to server. |
Archive | Check Archive |
Scan Requests (4)
URL | https://lifesavvy.com/app-ads.txt |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | https://www.lifesavvy.com/app-ads.txt |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | http://lifesavvy.com/app-ads.txt |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | http://www.lifesavvy.com/app-ads.txt |
Result | Failed checking robots.txt - Couldn't connect to server. |
Last Successful Scan
Scanned | 2024-02-01T20:24:51+00:00 |
URL | https://lifesavvy.com/app-ads.txt |
Redirect | https://www.lifesavvy.com/app-ads.txt |
Redirect Domain | www.lifesavvy.com |
Redirect Base | lifesavvy.com |
Domain IPs | 151.101.130.217, 151.101.194.217, 151.101.2.217, 151.101.66.217 |
Redirect IPs | 151.101.130.49, 151.101.194.49, 151.101.2.49, 151.101.66.49 |
Response IP | 199.232.46.49 |
Found | No |
Not Found Reason | Resource doesn't exist. |
Apple Associated Domain
Resource Details
Resource | apple-app-site-association |
Status | Failed |
Failure Stage | Checking robots.txt. |
Failure Reason | Couldn't connect to server. |
Archive | Check Archive |
Scan Requests (2)
URL | https://lifesavvy.com/.well-known/apple-app-site-association |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | https://www.lifesavvy.com/.well-known/apple-app-site-association |
Result | Failed checking robots.txt - Couldn't connect to server. |
Last Successful Scan
Scanned | 2022-09-22T22:36:29+00:00 |
URL | https://lifesavvy.com/.well-known/apple-app-site-association |
Redirect | https://www.lifesavvy.com/.well-known/apple-app-site-association/ |
Redirect Domain | www.lifesavvy.com |
Redirect Base | lifesavvy.com |
Response IP | 199.232.46.49 |
Found | No |
Not Found Reason | Request was redirected to another domain. |
Digital Asset Links
Resource Details
Resource | assetlinks.json |
Status | Failed |
Failure Stage | Checking robots.txt. |
Failure Reason | Couldn't connect to server. |
Archive | Check Archive |
Scan Requests (4)
URL | https://lifesavvy.com/.well-known/assetlinks.json |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | https://www.lifesavvy.com/.well-known/assetlinks.json |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | http://lifesavvy.com/.well-known/assetlinks.json |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | http://www.lifesavvy.com/.well-known/assetlinks.json |
Result | Failed checking robots.txt - Couldn't connect to server. |
Last Successful Scan
Scanned | 2022-09-22T22:36:29+00:00 |
URL | https://lifesavvy.com/.well-known/assetlinks.json |
Redirect | https://www.lifesavvy.com/.well-known/assetlinks.json |
Redirect Domain | www.lifesavvy.com |
Redirect Base | lifesavvy.com |
Response IP | 199.232.46.49 |
Found | No |
Not Found Reason | Request was redirected to another domain. |
Global Privacy Control
Resource Details
Resource | gpc.json |
Status | Failed |
Failure Stage | Checking robots.txt. |
Failure Reason | Couldn't connect to server. |
Archive | Check Archive |
Scan Requests (4)
URL | https://lifesavvy.com/.well-known/gpc.json |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | https://www.lifesavvy.com/.well-known/gpc.json |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | http://lifesavvy.com/.well-known/gpc.json |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | http://www.lifesavvy.com/.well-known/gpc.json |
Result | Failed checking robots.txt - Couldn't connect to server. |
Last Successful Scan
Scanned | 2022-09-22T22:36:29+00:00 |
URL | https://lifesavvy.com/.well-known/gpc.json |
Redirect | https://www.lifesavvy.com/.well-known/gpc.json |
Redirect Domain | www.lifesavvy.com |
Redirect Base | lifesavvy.com |
Response IP | 199.232.46.49 |
Found | No |
Not Found Reason | Server returned a client error. |
NodeInfo
Resource Details
Resource | nodeinfo |
Status | Failed |
Failure Stage | Checking robots.txt. |
Failure Reason | Couldn't connect to server. |
Archive | Check Archive |
Scan Requests (4)
URL | https://lifesavvy.com/.well-known/nodeinfo |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | https://www.lifesavvy.com/.well-known/nodeinfo |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | http://lifesavvy.com/.well-known/nodeinfo |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | http://www.lifesavvy.com/.well-known/nodeinfo |
Result | Failed checking robots.txt - Couldn't connect to server. |
OpenID Provider Configuration
Resource Details
Resource | openid-configuration |
Status | Failed |
Failure Stage | Checking robots.txt. |
Failure Reason | Couldn't connect to server. |
Archive | Check Archive |
Scan Requests (2)
URL | https://lifesavvy.com/.well-known/openid-configuration |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | https://www.lifesavvy.com/.well-known/openid-configuration |
Result | Failed checking robots.txt - Couldn't connect to server. |
Last Successful Scan
Scanned | 2022-09-22T22:36:29+00:00 |
URL | https://lifesavvy.com/.well-known/openid-configuration |
Redirect | https://www.lifesavvy.com/.well-known/openid-configuration/ |
Redirect Domain | www.lifesavvy.com |
Redirect Base | lifesavvy.com |
Response IP | 199.232.46.49 |
Found | No |
Not Found Reason | Server returned a client error. |
Robots Exclusion Standard
Resource Details
Resource | robots.txt |
Status | Failed |
Failure Stage | Fetching resource. |
Failure Reason | Couldn't connect to server. |
Archive | Check Archive |
Scan Requests (4)
URL | https://lifesavvy.com/robots.txt |
Result | Failed fetching resource - Couldn't connect to server. |
URL | https://www.lifesavvy.com/robots.txt |
Result | Failed fetching resource - Couldn't connect to server. |
URL | http://lifesavvy.com/robots.txt |
Result | Failed fetching resource - Couldn't connect to server. |
URL | http://www.lifesavvy.com/robots.txt |
Result | Failed fetching resource - Couldn't connect to server. |
Last Successful Scan
Scanned | 2024-02-01T20:24:51+00:00 |
URL | https://lifesavvy.com/robots.txt |
Redirect | https://www.lifesavvy.com/robots.txt |
Redirect Domain | www.lifesavvy.com |
Redirect Base | lifesavvy.com |
Domain IPs | 151.101.130.217, 151.101.194.217, 151.101.2.217, 151.101.66.217 |
Redirect IPs | 151.101.130.49, 151.101.194.49, 151.101.2.49, 151.101.66.49 |
Response IP | 199.232.46.49 |
Found | Yes - View Resource |
Hash | 37b33b7a7f1a86f926df5eaa383ba72e460bb7f1e28260fe3def121fb6cb9ad0 |
SimHash | e8295c50aa82 |
security.txt
Resource Details
Resource | security.txt |
Status | Failed |
Failure Stage | Checking robots.txt. |
Failure Reason | Couldn't connect to server. |
Archive | Check Archive |
Scan Requests (2)
URL | https://lifesavvy.com/.well-known/security.txt |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | https://www.lifesavvy.com/.well-known/security.txt |
Result | Failed checking robots.txt - Couldn't connect to server. |
Last Successful Scan
Scanned | 2022-09-22T22:36:29+00:00 |
URL | https://lifesavvy.com/.well-known/security.txt |
Redirect | https://www.lifesavvy.com/.well-known/security.txt |
Redirect Domain | www.lifesavvy.com |
Redirect Base | lifesavvy.com |
Response IP | 199.232.46.49 |
Found | No |
Not Found Reason | Server returned a client error. |
trust.txt
Resource Details
Resource | trust.txt |
Status | Failed |
Failure Stage | Checking robots.txt. |
Failure Reason | Couldn't connect to server. |
Archive | Check Archive |
Scan Requests (4)
URL | https://lifesavvy.com/.well-known/trust.txt |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | https://www.lifesavvy.com/.well-known/trust.txt |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | http://lifesavvy.com/.well-known/trust.txt |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | http://www.lifesavvy.com/.well-known/trust.txt |
Result | Failed checking robots.txt - Couldn't connect to server. |
Last Successful Scan
Scanned | 2022-09-22T22:36:29+00:00 |
URL | https://lifesavvy.com/.well-known/trust.txt |
Redirect | https://www.lifesavvy.com/.well-known/trust.txt |
Redirect Domain | www.lifesavvy.com |
Redirect Base | lifesavvy.com |
Response IP | 199.232.46.49 |
Found | No |
Not Found Reason | Server returned a client error. |