labangmore.com
/.well-known/
resources for
labangmore.com
Site Scan
Site Details
Site Domain | labangmore.com |
Base Domain | labangmore.com |
Added | 2025-03-21T04:09:57+00:00 |
Last Scan | 2025-05-18T02:09:19+00:00 |
Next Scan | 2025-06-17T02:09:19+00:00 |
Found Resources
Resource | Found At | Scan Status |
---|---|---|
robots.txt | 2025-05-18T02:09: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://labangmore.com/ads.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.labangmore.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://labangmore.com/app-ads.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.labangmore.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://labangmore.com/.well-known/apple-app-site-association |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://labangmore.com/apple-app-site-association |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.labangmore.com/.well-known/apple-app-site-association |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.labangmore.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://labangmore.com/.well-known/assetlinks.json |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.labangmore.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://labangmore.com/.well-known/gpc.json |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.labangmore.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://labangmore.com/.well-known/nodeinfo |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.labangmore.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://labangmore.com/.well-known/openid-configuration |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.labangmore.com/.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://labangmore.com/robots.txt |
Result | Resource Found. |
Last Scan
Scanned | 2025-05-18T02:09:19+00:00 |
URL | https://labangmore.com/robots.txt |
Redirect | https://www.labangmore.com/robots.txt |
Redirect Domain | www.labangmore.com |
Redirect Base | labangmore.com |
Domain IPs | 3.171.198.110, 3.171.198.28, 3.171.198.61, 3.171.198.64 |
Redirect IPs | 108.156.144.36, 108.156.144.52, 108.156.144.61, 108.156.144.68 |
Response IP | 108.156.144.52 |
Found | Yes - View Resource |
Hash | b67f6ed4e1b46651a1475a6b3dbeec80384164712cbb1ad24f8119ed46219f7f |
SimHash | 4010d037c733 |
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://labangmore.com/.well-known/security.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://labangmore.com/security.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.labangmore.com/.well-known/security.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.labangmore.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://labangmore.com/.well-known/trust.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://labangmore.com/trust.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.labangmore.com/.well-known/trust.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.labangmore.com/trust.txt |
Result | Failed fetching resource - Server returned a client error (403). |