voorschriftopzak.be
/.well-known/
resources for
voorschriftopzak.be
Site Scan
Site Details
| Site Domain | voorschriftopzak.be |
| Base Domain | voorschriftopzak.be |
| Added | 2023-01-20T12:43:21+00:00 |
| Last Scan | 2024-11-04T22:37:19+00:00 |
| Next Scan | 2024-11-18T22:37:19+00:00 |
Found Resources
| Resource | Found At | Scan Status |
|---|---|---|
| apple-app-site-association | 2024-11-04T22:37:19+00:00 | Ok |
| assetlinks.json | 2024-11-04T22:37:19+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://voorschriftopzak.be/ads.txt |
| Result | Failed fetching resource - Server returned a client error (403). |
| URL | https://www.voorschriftopzak.be/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://voorschriftopzak.be/app-ads.txt |
| Result | Failed fetching resource - Server returned a client error (403). |
| URL | https://www.voorschriftopzak.be/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://voorschriftopzak.be/.well-known/apple-app-site-association |
| Result | Resource Found. |
Last Scan
| Scanned | 2024-11-04T22:37:19+00:00 |
| URL | https://voorschriftopzak.be/.well-known/apple-app-site-association |
| Domain IPs | 65.9.112.110, 65.9.112.128, 65.9.112.3, 65.9.112.84 |
| Response IP | 3.164.206.56 |
| Found | Yes - View Resource |
| Hash | 775eac8fbe601be7d6c9906ee433d015b7b5474c47030be978dafdca60d96818 |
| SimHash | 5178bd74ff17 |
Digital Asset Links
Resource Details
| Resource | assetlinks.json |
| Status | Ok |
| Archive | Check Archive |
Scan Requests (1)
| URL | https://voorschriftopzak.be/.well-known/assetlinks.json |
| Result | Resource Found. |
Last Scan
| Scanned | 2024-11-04T22:37:19+00:00 |
| URL | https://voorschriftopzak.be/.well-known/assetlinks.json |
| Domain IPs | 65.9.112.110, 65.9.112.128, 65.9.112.3, 65.9.112.84 |
| Response IP | 3.164.206.56 |
| Found | Yes - View Resource |
| Hash | f4fc815e69c9ed29d2cb647203543331fabe329d661b2036acbd0e1d770aa41c |
| SimHash | fc7f5b4df63b |
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://voorschriftopzak.be/.well-known/gpc.json |
| Result | Failed fetching resource - Server returned a client error (403). |
| URL | https://www.voorschriftopzak.be/.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://voorschriftopzak.be/.well-known/nodeinfo |
| Result | Failed fetching resource - Server returned a client error (403). |
| URL | https://www.voorschriftopzak.be/.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://voorschriftopzak.be/.well-known/openid-configuration |
| Result | Failed fetching resource - Server returned a client error (403). |
| URL | https://www.voorschriftopzak.be/.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://voorschriftopzak.be/robots.txt |
| Result | Failed fetching resource - Server returned a client error (403). |
| URL | https://www.voorschriftopzak.be/robots.txt |
| Result | Failed fetching resource - Server returned a client error (403). |
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://voorschriftopzak.be/.well-known/security.txt |
| Result | Failed fetching resource - Server returned a client error (403). |
| URL | https://voorschriftopzak.be/security.txt |
| Result | Failed fetching resource - Server returned a client error (403). |
| URL | https://www.voorschriftopzak.be/.well-known/security.txt |
| Result | Failed fetching resource - Server returned a client error (403). |
| URL | https://www.voorschriftopzak.be/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://voorschriftopzak.be/.well-known/trust.txt |
| Result | Failed fetching resource - Server returned a client error (403). |
| URL | https://voorschriftopzak.be/trust.txt |
| Result | Failed fetching resource - Server returned a client error (403). |
| URL | https://www.voorschriftopzak.be/.well-known/trust.txt |
| Result | Failed fetching resource - Server returned a client error (403). |
| URL | https://www.voorschriftopzak.be/trust.txt |
| Result | Failed fetching resource - Server returned a client error (403). |