zork-follow.com
/.well-known/
resources for
zork-follow.com
Site Scan
Site Details
Site Domain | zork-follow.com |
Base Domain | zork-follow.com |
Added | 2023-09-03T23:31:09+00:00 |
Last Scan | 2024-10-24T13:37:07+00:00 |
Next Scan | 2024-11-07T13:37:07+00:00 |
Found Resources
Resource | Found At | Scan Status |
---|---|---|
apple-app-site-association | 2024-10-24T13:37:07+00:00 | Ok |
robots.txt | 2023-10-26T02:00:28+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://zork-follow.com/ads.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.zork-follow.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://zork-follow.com/app-ads.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.zork-follow.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 | Ok |
Archive | Check Archive |
Scan Requests (1)
URL | https://zork-follow.com/.well-known/apple-app-site-association |
Result | Resource Found. |
Last Scan
Scanned | 2024-10-24T13:37:07+00:00 |
URL | https://zork-follow.com/.well-known/apple-app-site-association |
Domain IPs | 104.21.26.14, 172.67.135.34, 2606:4700:3031::6815:1a0e, 2606:4700:3033::ac43:8722 |
Response IP | 104.21.26.14 |
Found | Yes - View Resource |
Hash | 44faddb5a8a7f42c2ed38212947cc150a67d66b39a6517ee788ca5439dbd9e2f |
SimHash | 0adead547135 |
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://zork-follow.com/.well-known/assetlinks.json |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.zork-follow.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://zork-follow.com/.well-known/gpc.json |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.zork-follow.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://zork-follow.com/.well-known/nodeinfo |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.zork-follow.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://zork-follow.com/.well-known/openid-configuration |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.zork-follow.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://zork-follow.com/robots.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.zork-follow.com/robots.txt |
Result | Failed fetching resource - Server returned a client error (403). |
Last Successful Scan
Scanned | 2023-10-26T02:00:28+00:00 |
URL | https://zork-follow.com/robots.txt |
Domain IPs | 104.21.26.14, 172.67.135.34, 2606:4700:3031::6815:1a0e, 2606:4700:3033::ac43:8722 |
Response IP | 104.21.26.14 |
Found | Yes - View Resource |
Hash | d5fe6998f8c5763824e41bfe37f6b64f6dd214c3deaae4c075fde53d645044f6 |
SimHash | 634767710ba7 |
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://zork-follow.com/.well-known/security.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://zork-follow.com/security.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.zork-follow.com/.well-known/security.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.zork-follow.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://zork-follow.com/.well-known/trust.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://zork-follow.com/trust.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.zork-follow.com/.well-known/trust.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.zork-follow.com/trust.txt |
Result | Failed fetching resource - Server returned a client error (403). |