wellnessfoods.jp
/.well-known/
resources for
wellnessfoods.jp
Site Scan
Site Details
Site Domain | wellnessfoods.jp |
Base Domain | wellnessfoods.jp |
Added | 2023-01-20T12:46:24+00:00 |
Last Scan | 2024-11-07T04:41:43+00:00 |
Next Scan | 2024-11-21T04:41:43+00:00 |
Found Resources
Resource | Found At | Scan Status |
---|---|---|
apple-app-site-association | 2024-11-07T04:41:43+00:00 | Ok |
openid-configuration | 2024-11-07T04:41:43+00:00 | Ok |
robots.txt | 2024-11-07T04:41:43+00:00 | Ok |
Authorized Digital Sellers
Resource Details
Resource | ads.txt |
Status | Failed |
Failure Stage | Fetching resource. |
Failure Reason | Server returned a client error. |
Archive | Check Archive |
Scan Requests (2)
URL | https://wellnessfoods.jp/ads.txt |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | https://www.wellnessfoods.jp/ads.txt |
Result | Failed fetching resource - Server returned a client error (401). |
Authorized Digital Sellers for Apps
Resource Details
Resource | app-ads.txt |
Status | Failed |
Failure Stage | Fetching resource. |
Failure Reason | Server returned a client error. |
Archive | Check Archive |
Scan Requests (2)
URL | https://wellnessfoods.jp/app-ads.txt |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | https://www.wellnessfoods.jp/app-ads.txt |
Result | Failed fetching resource - Server returned a client error (401). |
Apple Associated Domain
Resource Details
Resource | apple-app-site-association |
Status | Ok |
Archive | Check Archive |
Scan Requests (2)
URL | https://wellnessfoods.jp/.well-known/apple-app-site-association |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | https://www.wellnessfoods.jp/.well-known/apple-app-site-association |
Result | Resource Found. |
Last Scan
Scanned | 2024-11-07T04:41:43+00:00 |
URL | https://www.wellnessfoods.jp/.well-known/apple-app-site-association |
Domain IPs | 2600:1413:1::173b:a872, 96.17.180.42, 96.17.180.46 |
Response IP | 23.55.39.7 |
Found | Yes - View Resource |
Hash | e9a431ec91ae50773c39d2ccc50fd4db53097f5fd45ecef7e5df645f0febd447 |
SimHash | 213d97477f03 |
Digital Asset Links
Resource Details
Resource | assetlinks.json |
Status | Ok |
Archive | Check Archive |
Scan Requests (2)
URL | https://wellnessfoods.jp/.well-known/assetlinks.json |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | https://www.wellnessfoods.jp/.well-known/assetlinks.json |
Result | Not Found - Resource wasn't valid JSON. |
Last Scan
Scanned | 2024-11-07T04:41:43+00:00 |
URL | https://www.wellnessfoods.jp/.well-known/assetlinks.json |
Domain IPs | 2600:1413:1::173b:a872, 96.17.180.42, 96.17.180.46 |
Response IP | 23.55.39.7 |
Found | No |
Not Found Reason | Resource wasn't valid JSON. |
Global Privacy Control
Resource Details
Resource | gpc.json |
Status | Failed |
Failure Stage | Fetching resource. |
Failure Reason | Server returned a client error. |
Archive | Check Archive |
Scan Requests (2)
URL | https://wellnessfoods.jp/.well-known/gpc.json |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | https://www.wellnessfoods.jp/.well-known/gpc.json |
Result | Failed fetching resource - Server returned a client error (401). |
NodeInfo
Resource Details
Resource | nodeinfo |
Status | Failed |
Failure Stage | Fetching resource. |
Failure Reason | Server returned a client error. |
Archive | Check Archive |
Scan Requests (2)
URL | https://wellnessfoods.jp/.well-known/nodeinfo |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | https://www.wellnessfoods.jp/.well-known/nodeinfo |
Result | Failed fetching resource - Server returned a client error (401). |
OpenID Provider Configuration
Resource Details
Resource | openid-configuration |
Status | Ok |
Archive | Check Archive |
Scan Requests (2)
URL | https://wellnessfoods.jp/.well-known/openid-configuration |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | https://www.wellnessfoods.jp/.well-known/openid-configuration |
Result | Resource Found. |
Last Scan
Scanned | 2024-11-07T04:41:43+00:00 |
URL | https://www.wellnessfoods.jp/.well-known/openid-configuration |
Domain IPs | 2600:1413:1::173b:a872, 96.17.180.42, 96.17.180.46 |
Response IP | 96.17.180.46 |
Found | Yes - View Resource |
Hash | e8b2a5cae059fba102b3fe4520ccc9e005d85403e7f135528dd9b5b9efa729f2 |
SimHash | 3dc5d72d3141 |
Robots Exclusion Standard
Resource Details
Resource | robots.txt |
Status | Ok |
Archive | Check Archive |
Scan Requests (2)
URL | https://wellnessfoods.jp/robots.txt |
Result | Failed fetching resource - Couldn't connect to server. |
URL | https://www.wellnessfoods.jp/robots.txt |
Result | Resource Found. |
Last Scan
Scanned | 2024-11-07T04:41:43+00:00 |
URL | https://www.wellnessfoods.jp/robots.txt |
Domain IPs | 2600:1413:1::173b:a872, 96.17.180.42, 96.17.180.46 |
Response IP | 23.55.39.7 |
Found | Yes - View Resource |
Hash | f251620f56642df6e3bad8faf803b7da76c1fc77a1ea504b144514812ad9f265 |
SimHash | 2320dbcdcf93 |
security.txt
Resource Details
Resource | security.txt |
Status | Failed |
Failure Stage | Fetching resource. |
Failure Reason | Server returned a client error. |
Archive | Check Archive |
Scan Requests (3)
URL | https://wellnessfoods.jp/.well-known/security.txt |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | https://www.wellnessfoods.jp/.well-known/security.txt |
Result | Failed fetching resource - Server returned a client error (401). |
URL | https://www.wellnessfoods.jp/security.txt |
Result | Failed fetching resource - Server returned a client error (401). |
trust.txt
Resource Details
Resource | trust.txt |
Status | Failed |
Failure Stage | Fetching resource. |
Failure Reason | Server returned a client error. |
Archive | Check Archive |
Scan Requests (3)
URL | https://wellnessfoods.jp/.well-known/trust.txt |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | https://www.wellnessfoods.jp/.well-known/trust.txt |
Result | Failed fetching resource - Server returned a client error (401). |
URL | https://www.wellnessfoods.jp/trust.txt |
Result | Failed fetching resource - Server returned a client error (401). |