safenests.com
/.well-known/
resources for
safenests.com
Site Scan
Site Details
| Site Domain | safenests.com |
| Base Domain | safenests.com |
| Added | 2024-06-09T23:19:32+00:00 |
| Last Scan | 2024-09-10T00:36:11+00:00 |
| Next Scan | 2024-09-24T00:36:11+00:00 |
Found Resources
| Resource | Found At | Scan Status |
|---|---|---|
| apple-app-site-association | 2024-09-10T00:36: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://safenests.com/ads.txt |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | https://www.safenests.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://safenests.com/app-ads.txt |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | https://www.safenests.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 (3)
| URL | https://safenests.com/.well-known/apple-app-site-association |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | https://www.safenests.com/.well-known/apple-app-site-association |
| Result | Failed fetching resource - Server returned a client error (403). |
| URL | https://www.safenests.com/apple-app-site-association |
| Result | Resource Found. |
Last Scan
| Scanned | 2024-09-10T00:36:11+00:00 |
| URL | https://www.safenests.com/apple-app-site-association |
| Domain IPs | 2600:9000:2003:4200:1c:1334:4200:93a1, 2600:9000:2003:7e00:1c:1334:4200:93a1, 2600:9000:2003:9200:1c:1334:4200:93a1, 2600:9000:2003:9400:1c:1334:4200:93a1, 2600:9000:2003:a00:1c:1334:4200:93a1, 2600:9000:2003:a600:1c:1334:4200:93a1, 2600:9000:2003:a800:1c:1334:4200:93a1, 2600:9000:2003:b400:1c:1334:4200:93a1, 52.84.229.115, 52.84.229.129, 52.84.229.60, 52.84.229.99 |
| Response IP | 52.84.229.60 |
| Found | Yes - View Resource |
| Hash | b95fb8506451ab53754a50be96c83d537af7df68a29d1fdefbe4cbed82dcd327 |
| SimHash | 79c83554ff17 |
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://safenests.com/.well-known/assetlinks.json |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | https://www.safenests.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://safenests.com/.well-known/gpc.json |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | https://www.safenests.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://safenests.com/.well-known/nodeinfo |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | https://www.safenests.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://safenests.com/.well-known/openid-configuration |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | https://www.safenests.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://safenests.com/robots.txt |
| Result | Failed fetching resource - Couldn't connect to server. |
| URL | https://www.safenests.com/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 (3)
| URL | https://safenests.com/.well-known/security.txt |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | https://www.safenests.com/.well-known/security.txt |
| Result | Failed fetching resource - Server returned a client error (403). |
| URL | https://www.safenests.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 (3)
| URL | https://safenests.com/.well-known/trust.txt |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | https://www.safenests.com/.well-known/trust.txt |
| Result | Failed fetching resource - Server returned a client error (403). |
| URL | https://www.safenests.com/trust.txt |
| Result | Failed fetching resource - Server returned a client error (403). |