bolly-flix.my
/.well-known/
resources for
bolly-flix.my
Site Scan
Site Details
Site Domain | bolly-flix.my |
Base Domain | bolly-flix.my |
Added | 2025-02-17T22:26:36+00:00 |
Last Scan | 2025-03-11T22:39:11+00:00 |
Next Scan | 2025-04-10T22:39:11+00:00 |
Found Resources
Resource | Found At | Scan Status |
---|---|---|
robots.txt | 2025-03-11T22:39:11+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://bolly-flix.my/ads.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.bolly-flix.my/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://bolly-flix.my/app-ads.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.bolly-flix.my/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://bolly-flix.my/.well-known/apple-app-site-association |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://bolly-flix.my/apple-app-site-association |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.bolly-flix.my/.well-known/apple-app-site-association |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.bolly-flix.my/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://bolly-flix.my/.well-known/assetlinks.json |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.bolly-flix.my/.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://bolly-flix.my/.well-known/gpc.json |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.bolly-flix.my/.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://bolly-flix.my/.well-known/nodeinfo |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.bolly-flix.my/.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://bolly-flix.my/.well-known/openid-configuration |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.bolly-flix.my/.well-known/openid-configuration |
Result | Failed fetching resource - Server returned a client error (403). |
Robots Exclusion Standard
Resource Details
Resource | robots.txt |
Status | Ok |
Archive | Check Archive |
Scan Requests (1)
URL | https://bolly-flix.my/robots.txt |
Result | Resource Found. |
Last Scan
Scanned | 2025-03-11T22:39:11+00:00 |
URL | https://bolly-flix.my/robots.txt |
Redirect | https://bolly-flix.club/robots.txt |
Redirect Domain | bolly-flix.club |
Redirect Base | bolly-flix.club |
Domain IPs | 104.21.22.123, 172.67.204.207, 2606:4700:3031::6815:167b, 2606:4700:3034::ac43:cccf |
Redirect IPs | 104.21.3.187, 172.67.131.25, 2606:4700:3031::ac43:8319, 2606:4700:3037::6815:3bb |
Response IP | 172.67.131.25 |
Found | Yes - View Resource |
Hash | 02f5a005d068c47bc8a6b777c5f2f0acbfa63569aae8d7a7ab20641b68febee4 |
SimHash | 69009c000f93 |
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://bolly-flix.my/.well-known/security.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://bolly-flix.my/security.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.bolly-flix.my/.well-known/security.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.bolly-flix.my/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://bolly-flix.my/.well-known/trust.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://bolly-flix.my/trust.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.bolly-flix.my/.well-known/trust.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.bolly-flix.my/trust.txt |
Result | Failed fetching resource - Server returned a client error (403). |