storeys.com
/.well-known/
resources for
storeys.com
Site Scan
Site Details
Site Domain | storeys.com |
Base Domain | storeys.com |
Added | 2021-03-12T03:16:06+00:00 |
Last Scan | 2024-08-22T21:10:02+00:00 |
Next Scan | 2024-11-20T21:10:02+00:00 |
Found Resources
Resource | Found At | Scan Status |
---|---|---|
robots.txt | 2023-07-07T21:02:53+00:00 | Failed |
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://storeys.com/ads.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.storeys.com/ads.txt |
Result | Failed fetching resource - Server returned a client error (403). |
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://storeys.com/app-ads.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.storeys.com/app-ads.txt |
Result | Failed fetching resource - Server returned a client error (403). |
Apple Associated Domain
Resource Details
Resource | apple-app-site-association |
Status | Failed |
Failure Stage | Fetching resource. |
Failure Reason | Server returned a client error. |
Archive | Check Archive |
Scan Requests (4)
URL | https://storeys.com/.well-known/apple-app-site-association |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://storeys.com/apple-app-site-association |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.storeys.com/.well-known/apple-app-site-association |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.storeys.com/apple-app-site-association |
Result | Failed fetching resource - Server returned a client error (403). |
Digital Asset Links
Resource Details
Resource | assetlinks.json |
Status | Failed |
Failure Stage | Fetching resource. |
Failure Reason | Server returned a client error. |
Archive | Check Archive |
Scan Requests (2)
URL | https://storeys.com/.well-known/assetlinks.json |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.storeys.com/.well-known/assetlinks.json |
Result | Failed fetching resource - Server returned a client error (403). |
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://storeys.com/.well-known/gpc.json |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.storeys.com/.well-known/gpc.json |
Result | Failed fetching resource - Server returned a client error (403). |
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://storeys.com/.well-known/nodeinfo |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.storeys.com/.well-known/nodeinfo |
Result | Failed fetching resource - Server returned a client error (403). |
OpenID Provider Configuration
Resource Details
Resource | openid-configuration |
Status | Failed |
Failure Stage | Fetching resource. |
Failure Reason | Server returned a client error. |
Archive | Check Archive |
Scan Requests (2)
URL | https://storeys.com/.well-known/openid-configuration |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.storeys.com/.well-known/openid-configuration |
Result | Failed fetching resource - Server returned a client error (403). |
Robots Exclusion Standard
Resource Details
Resource | robots.txt |
Status | Failed |
Failure Stage | Fetching resource. |
Failure Reason | Server returned a client error. |
Archive | Check Archive |
Scan Requests (2)
URL | https://storeys.com/robots.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.storeys.com/robots.txt |
Result | Failed fetching resource - Server returned a client error (403). |
Last Successful Scan
Scanned | 2023-07-07T21:02:53+00:00 |
URL | https://storeys.com/robots.txt |
Domain IPs | 104.21.46.24, 172.67.222.160, 2606:4700:3031::ac43:dea0, 2606:4700:3036::6815:2e18 |
Response IP | 104.21.46.24 |
Found | Yes - View Resource |
Hash | a626d67b77ffe68138ca8560bd8e144c7b21eb7c1ae4d40d7d80010706ee8889 |
SimHash | c100ca208bb2 |
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 (4)
URL | https://storeys.com/.well-known/security.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://storeys.com/security.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.storeys.com/.well-known/security.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.storeys.com/security.txt |
Result | Failed fetching resource - Server returned a client error (403). |
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 (4)
URL | https://storeys.com/.well-known/trust.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://storeys.com/trust.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.storeys.com/.well-known/trust.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.storeys.com/trust.txt |
Result | Failed fetching resource - Server returned a client error (403). |