uproxy.site
/.well-known/
resources for
uproxy.site
Site Scan
Site Details
Site Domain | uproxy.site |
Base Domain | uproxy.site |
Added | 2022-12-18T23:05:03+00:00 |
Last Scan | 2025-01-25T17:36:45+00:00 |
Next Scan | 2025-04-25T17:36:45+00:00 |
Found Resources
Resource | Found At | Scan Status |
---|---|---|
robots.txt | 2022-12-27T01:46:11+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://uproxy.site/ads.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.uproxy.site/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://uproxy.site/app-ads.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.uproxy.site/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://uproxy.site/.well-known/apple-app-site-association |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://uproxy.site/apple-app-site-association |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.uproxy.site/.well-known/apple-app-site-association |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.uproxy.site/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://uproxy.site/.well-known/assetlinks.json |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.uproxy.site/.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://uproxy.site/.well-known/gpc.json |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.uproxy.site/.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://uproxy.site/.well-known/nodeinfo |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.uproxy.site/.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://uproxy.site/.well-known/openid-configuration |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.uproxy.site/.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://uproxy.site/robots.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.uproxy.site/robots.txt |
Result | Failed fetching resource - Server returned a client error (403). |
Last Successful Scan
Scanned | 2022-12-27T01:46:11+00:00 |
URL | https://uproxy.site/robots.txt |
Domain IPs | 104.21.67.140, 172.67.177.57, 2606:4700:3031::ac43:b139, 2606:4700:3034::6815:438c |
Response IP | 172.67.177.57 |
Found | Yes - View Resource |
Hash | a03dd0cfd4e9363170c9652f48c4dcdaa7ad3cab3f66c87c9b78b19992dc7720 |
SimHash | 6f08c2f2c331 |
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://uproxy.site/.well-known/security.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://uproxy.site/security.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.uproxy.site/.well-known/security.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.uproxy.site/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://uproxy.site/.well-known/trust.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://uproxy.site/trust.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.uproxy.site/.well-known/trust.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.uproxy.site/trust.txt |
Result | Failed fetching resource - Server returned a client error (403). |