beavercreeknewscurrent.com
/.well-known/
resources for
beavercreeknewscurrent.com
Site Scan
Site Details
Site Domain | beavercreeknewscurrent.com |
Base Domain | beavercreeknewscurrent.com |
Added | 2022-11-20T17:40:14+00:00 |
Last Scan | 2024-09-04T13:19:21+00:00 |
Next Scan | 2024-12-03T13:19:21+00:00 |
Found Resources
Resource | Found At | Scan Status |
---|---|---|
ads.txt | 2023-11-10T01:07:51+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://beavercreeknewscurrent.com/ads.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.beavercreeknewscurrent.com/ads.txt |
Result | Failed fetching resource - Server returned a client error (403). |
Last Successful Scan
Scanned | 2023-11-10T01:07:51+00:00 |
URL | https://beavercreeknewscurrent.com/ads.txt |
Redirect | https://www.beavercreeknewscurrent.com/ads.txt |
Redirect Domain | www.beavercreeknewscurrent.com |
Redirect Base | beavercreeknewscurrent.com |
Domain IPs | 104.21.32.138, 172.67.152.94, 2606:4700:3033::ac43:985e, 2606:4700:3036::6815:208a |
Redirect IPs | 104.21.32.138, 172.67.152.94, 2606:4700:3033::ac43:985e, 2606:4700:3036::6815:208a |
Response IP | 172.67.152.94 |
Found | Yes - View Resource |
Hash | a18d4e12376d4b76aa1f9dd96ee83ead1558467d65e8c86d5b3a062e31fecf08 |
SimHash | 421c9ccf71fe |
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://beavercreeknewscurrent.com/app-ads.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.beavercreeknewscurrent.com/app-ads.txt |
Result | Failed fetching resource - Server returned a client error (403). |
Last Successful Scan
Scanned | 2023-11-10T01:07:51+00:00 |
URL | https://beavercreeknewscurrent.com/app-ads.txt |
Redirect | https://www.beavercreeknewscurrent.com/app-ads.txt |
Redirect Domain | www.beavercreeknewscurrent.com |
Redirect Base | beavercreeknewscurrent.com |
Domain IPs | 104.21.32.138, 172.67.152.94, 2606:4700:3033::ac43:985e, 2606:4700:3036::6815:208a |
Redirect IPs | 104.21.32.138, 172.67.152.94, 2606:4700:3033::ac43:985e, 2606:4700:3036::6815:208a |
Response IP | 172.67.152.94 |
Found | No |
Not Found Reason | Resource doesn't exist. |
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://beavercreeknewscurrent.com/.well-known/apple-app-site-association |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://beavercreeknewscurrent.com/apple-app-site-association |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.beavercreeknewscurrent.com/.well-known/apple-app-site-association |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.beavercreeknewscurrent.com/apple-app-site-association |
Result | Failed fetching resource - Server returned a client error (403). |
Last Successful Scan
Scanned | 2023-11-10T01:07:51+00:00 |
URL | https://beavercreeknewscurrent.com/.well-known/apple-app-site-association |
Redirect | https://www.beavercreeknewscurrent.com/.well-known/apple-app-site-association |
Redirect Domain | www.beavercreeknewscurrent.com |
Redirect Base | beavercreeknewscurrent.com |
Domain IPs | 104.21.32.138, 172.67.152.94, 2606:4700:3033::ac43:985e, 2606:4700:3036::6815:208a |
Redirect IPs | 104.21.32.138, 172.67.152.94, 2606:4700:3033::ac43:985e, 2606:4700:3036::6815:208a |
Response IP | 172.67.152.94 |
Found | No |
Not Found Reason | Resource doesn't exist. |
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://beavercreeknewscurrent.com/.well-known/assetlinks.json |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.beavercreeknewscurrent.com/.well-known/assetlinks.json |
Result | Failed fetching resource - Server returned a client error (403). |
Last Successful Scan
Scanned | 2023-11-10T01:07:51+00:00 |
URL | https://beavercreeknewscurrent.com/.well-known/assetlinks.json |
Redirect | https://www.beavercreeknewscurrent.com/.well-known/assetlinks.json |
Redirect Domain | www.beavercreeknewscurrent.com |
Redirect Base | beavercreeknewscurrent.com |
Domain IPs | 104.21.32.138, 172.67.152.94, 2606:4700:3033::ac43:985e, 2606:4700:3036::6815:208a |
Redirect IPs | 104.21.32.138, 172.67.152.94, 2606:4700:3033::ac43:985e, 2606:4700:3036::6815:208a |
Response IP | 172.67.152.94 |
Found | No |
Not Found Reason | Resource doesn't exist. |
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://beavercreeknewscurrent.com/.well-known/gpc.json |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.beavercreeknewscurrent.com/.well-known/gpc.json |
Result | Failed fetching resource - Server returned a client error (403). |
Last Successful Scan
Scanned | 2023-11-10T01:07:51+00:00 |
URL | https://beavercreeknewscurrent.com/.well-known/gpc.json |
Redirect | https://www.beavercreeknewscurrent.com/.well-known/gpc.json |
Redirect Domain | www.beavercreeknewscurrent.com |
Redirect Base | beavercreeknewscurrent.com |
Domain IPs | 104.21.32.138, 172.67.152.94, 2606:4700:3033::ac43:985e, 2606:4700:3036::6815:208a |
Redirect IPs | 104.21.32.138, 172.67.152.94, 2606:4700:3033::ac43:985e, 2606:4700:3036::6815:208a |
Response IP | 104.21.32.138 |
Found | No |
Not Found Reason | Resource doesn't exist. |
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://beavercreeknewscurrent.com/.well-known/nodeinfo |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.beavercreeknewscurrent.com/.well-known/nodeinfo |
Result | Failed fetching resource - Server returned a client error (403). |
Last Successful Scan
Scanned | 2023-11-10T01:07:51+00:00 |
URL | https://beavercreeknewscurrent.com/.well-known/nodeinfo |
Redirect | https://www.beavercreeknewscurrent.com/.well-known/nodeinfo |
Redirect Domain | www.beavercreeknewscurrent.com |
Redirect Base | beavercreeknewscurrent.com |
Domain IPs | 104.21.32.138, 172.67.152.94, 2606:4700:3033::ac43:985e, 2606:4700:3036::6815:208a |
Redirect IPs | 104.21.32.138, 172.67.152.94, 2606:4700:3033::ac43:985e, 2606:4700:3036::6815:208a |
Response IP | 172.67.152.94 |
Found | No |
Not Found Reason | Resource doesn't exist. |
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://beavercreeknewscurrent.com/.well-known/openid-configuration |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.beavercreeknewscurrent.com/.well-known/openid-configuration |
Result | Failed fetching resource - Server returned a client error (403). |
Last Successful Scan
Scanned | 2023-11-10T01:07:51+00:00 |
URL | https://beavercreeknewscurrent.com/.well-known/openid-configuration |
Redirect | https://www.beavercreeknewscurrent.com/.well-known/openid-configuration |
Redirect Domain | www.beavercreeknewscurrent.com |
Redirect Base | beavercreeknewscurrent.com |
Domain IPs | 104.21.32.138, 172.67.152.94, 2606:4700:3033::ac43:985e, 2606:4700:3036::6815:208a |
Redirect IPs | 104.21.32.138, 172.67.152.94, 2606:4700:3033::ac43:985e, 2606:4700:3036::6815:208a |
Response IP | 172.67.152.94 |
Found | No |
Not Found Reason | Resource doesn't exist. |
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://beavercreeknewscurrent.com/robots.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.beavercreeknewscurrent.com/robots.txt |
Result | Failed fetching resource - Server returned a client error (403). |
Last Successful Scan
Scanned | 2023-11-10T01:07:51+00:00 |
URL | https://beavercreeknewscurrent.com/robots.txt |
Redirect | https://www.beavercreeknewscurrent.com/robots.txt |
Redirect Domain | www.beavercreeknewscurrent.com |
Redirect Base | beavercreeknewscurrent.com |
Domain IPs | 104.21.32.138, 172.67.152.94, 2606:4700:3033::ac43:985e, 2606:4700:3036::6815:208a |
Redirect IPs | 104.21.32.138, 172.67.152.94, 2606:4700:3033::ac43:985e, 2606:4700:3036::6815:208a |
Response IP | 172.67.152.94 |
Found | No |
Not Found Reason | Resource didn't match the expected format. |
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://beavercreeknewscurrent.com/.well-known/security.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://beavercreeknewscurrent.com/security.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.beavercreeknewscurrent.com/.well-known/security.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.beavercreeknewscurrent.com/security.txt |
Result | Failed fetching resource - Server returned a client error (403). |
Last Successful Scan
Scanned | 2023-11-10T01:07:51+00:00 |
URL | https://beavercreeknewscurrent.com/.well-known/security.txt |
Redirect | https://www.beavercreeknewscurrent.com/.well-known/security.txt |
Redirect Domain | www.beavercreeknewscurrent.com |
Redirect Base | beavercreeknewscurrent.com |
Domain IPs | 104.21.32.138, 172.67.152.94, 2606:4700:3033::ac43:985e, 2606:4700:3036::6815:208a |
Redirect IPs | 104.21.32.138, 172.67.152.94, 2606:4700:3033::ac43:985e, 2606:4700:3036::6815:208a |
Response IP | 104.21.32.138 |
Found | No |
Not Found Reason | Resource doesn't exist. |
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://beavercreeknewscurrent.com/.well-known/trust.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://beavercreeknewscurrent.com/trust.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.beavercreeknewscurrent.com/.well-known/trust.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.beavercreeknewscurrent.com/trust.txt |
Result | Failed fetching resource - Server returned a client error (403). |
Last Successful Scan
Scanned | 2023-11-10T01:07:51+00:00 |
URL | https://beavercreeknewscurrent.com/.well-known/trust.txt |
Redirect | https://www.beavercreeknewscurrent.com/.well-known/trust.txt |
Redirect Domain | www.beavercreeknewscurrent.com |
Redirect Base | beavercreeknewscurrent.com |
Domain IPs | 104.21.32.138, 172.67.152.94, 2606:4700:3033::ac43:985e, 2606:4700:3036::6815:208a |
Redirect IPs | 104.21.32.138, 172.67.152.94, 2606:4700:3033::ac43:985e, 2606:4700:3036::6815:208a |
Response IP | 172.67.152.94 |
Found | No |
Not Found Reason | Resource doesn't exist. |