washtimes.com
/.well-known/
resources for
washtimes.com
Site Scan
Site Details
Site Domain | washtimes.com |
Base Domain | washtimes.com |
Added | 2021-02-26T14:11:21+00:00 |
Last Scan | 2024-06-03T07:31:23+00:00 |
Next Scan | 2024-06-10T07:31:23+00:00 |
Found Resources
Resource | Found At | Scan Status |
---|---|---|
ads.txt | 2024-06-03T07:31:23+00:00 | Ok |
robots.txt | 2024-06-03T07:31:23+00:00 | Ok |
Authorized Digital Sellers
Resource Details
Resource | ads.txt |
Status | Ok |
Archive | Check Archive |
Scan Requests (1)
URL | https://washtimes.com/ads.txt |
Result | Resource Found. |
Last Scan
Scanned | 2024-06-03T07:31:23+00:00 |
URL | https://washtimes.com/ads.txt |
Redirect | https://www.washingtontimes.com:443/ads.txt |
Redirect Domain | www.washingtontimes.com |
Redirect Base | washingtontimes.com |
Domain IPs | 3.224.66.244, 3.232.33.200 |
Redirect IPs | 104.22.58.64, 104.22.59.64, 172.67.8.119 |
Response IP | 104.22.58.64 |
Found | Yes - View Resource |
Hash | 9a137a9da6c73391eed4559ec1044ccf294adbf7a91e0c9ec5c90c7456cc5ca7 |
SimHash | 16cc1f7252c3 |
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://washtimes.com/app-ads.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.washtimes.com/app-ads.txt |
Result | Failed fetching resource - Server returned a client error (403). |
Last Successful Scan
Scanned | 2023-12-29T21:12:57+00:00 |
URL | https://washtimes.com/app-ads.txt |
Redirect | https://www.washingtontimes.com:443/app-ads.txt/ |
Redirect Domain | www.washingtontimes.com |
Redirect Base | washingtontimes.com |
Domain IPs | 100.26.30.168, 34.192.124.80 |
Redirect IPs | 104.22.58.64, 104.22.59.64, 172.67.8.119 |
Response IP | 104.22.58.64 |
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://washtimes.com/.well-known/apple-app-site-association |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://washtimes.com/apple-app-site-association |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.washtimes.com/.well-known/apple-app-site-association |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.washtimes.com/apple-app-site-association |
Result | Failed fetching resource - Server returned a client error (403). |
Last Successful Scan
Scanned | 2023-12-29T21:12:57+00:00 |
URL | https://washtimes.com/.well-known/apple-app-site-association |
Redirect | https://www.washingtontimes.com:443/.well-known/apple-app-site-association/ |
Redirect Domain | www.washingtontimes.com |
Redirect Base | washingtontimes.com |
Domain IPs | 100.26.30.168, 34.192.124.80 |
Redirect IPs | 104.22.58.64, 104.22.59.64, 172.67.8.119 |
Response IP | 104.22.59.64 |
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://washtimes.com/.well-known/assetlinks.json |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.washtimes.com/.well-known/assetlinks.json |
Result | Failed fetching resource - Server returned a client error (403). |
Last Successful Scan
Scanned | 2023-12-29T21:12:57+00:00 |
URL | https://washtimes.com/.well-known/assetlinks.json |
Redirect | https://www.washingtontimes.com:443/.well-known/assetlinks.json/ |
Redirect Domain | www.washingtontimes.com |
Redirect Base | washingtontimes.com |
Domain IPs | 100.26.30.168, 34.192.124.80 |
Redirect IPs | 104.22.58.64, 104.22.59.64, 172.67.8.119 |
Response IP | 104.22.59.64 |
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://washtimes.com/.well-known/gpc.json |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.washtimes.com/.well-known/gpc.json |
Result | Failed fetching resource - Server returned a client error (403). |
Last Successful Scan
Scanned | 2023-12-29T21:12:57+00:00 |
URL | https://washtimes.com/.well-known/gpc.json |
Redirect | https://www.washingtontimes.com:443/.well-known/gpc.json/ |
Redirect Domain | www.washingtontimes.com |
Redirect Base | washingtontimes.com |
Domain IPs | 100.26.30.168, 34.192.124.80 |
Redirect IPs | 104.22.58.64, 104.22.59.64, 172.67.8.119 |
Response IP | 104.22.59.64 |
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://washtimes.com/.well-known/nodeinfo |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.washtimes.com/.well-known/nodeinfo |
Result | Failed fetching resource - Server returned a client error (403). |
Last Successful Scan
Scanned | 2023-12-29T21:12:57+00:00 |
URL | https://washtimes.com/.well-known/nodeinfo |
Redirect | https://www.washingtontimes.com:443/.well-known/nodeinfo/ |
Redirect Domain | www.washingtontimes.com |
Redirect Base | washingtontimes.com |
Domain IPs | 100.26.30.168, 34.192.124.80 |
Redirect IPs | 104.22.58.64, 104.22.59.64, 172.67.8.119 |
Response IP | 104.22.58.64 |
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://washtimes.com/.well-known/openid-configuration |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.washtimes.com/.well-known/openid-configuration |
Result | Failed fetching resource - Server returned a client error (403). |
Last Successful Scan
Scanned | 2023-12-29T21:12:57+00:00 |
URL | https://washtimes.com/.well-known/openid-configuration |
Redirect | https://www.washingtontimes.com:443/.well-known/openid-configuration/ |
Redirect Domain | www.washingtontimes.com |
Redirect Base | washingtontimes.com |
Domain IPs | 100.26.30.168, 34.192.124.80 |
Redirect IPs | 104.22.58.64, 104.22.59.64, 172.67.8.119 |
Response IP | 104.22.59.64 |
Found | No |
Not Found Reason | Resource doesn't exist. |
Robots Exclusion Standard
Resource Details
Resource | robots.txt |
Status | Ok |
Archive | Check Archive |
Scan Requests (1)
URL | https://washtimes.com/robots.txt |
Result | Resource Found. |
Last Scan
Scanned | 2024-06-03T07:31:23+00:00 |
URL | https://washtimes.com/robots.txt |
Redirect | https://www.washingtontimes.com:443/robots.txt |
Redirect Domain | www.washingtontimes.com |
Redirect Base | washingtontimes.com |
Domain IPs | 3.224.66.244, 3.232.33.200 |
Redirect IPs | 104.22.58.64, 104.22.59.64, 172.67.8.119 |
Response IP | 104.22.58.64 |
Found | Yes - View Resource |
Hash | 7b20d92db1570899e381c56342375cf83644271d21611c0c16d4942ec090634b |
SimHash | 6340d67085d1 |
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://washtimes.com/.well-known/security.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://washtimes.com/security.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.washtimes.com/.well-known/security.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.washtimes.com/security.txt |
Result | Failed fetching resource - Server returned a client error (403). |
Last Successful Scan
Scanned | 2023-12-29T21:12:57+00:00 |
URL | https://washtimes.com/.well-known/security.txt |
Redirect | https://www.washingtontimes.com:443/.well-known/security.txt/ |
Redirect Domain | www.washingtontimes.com |
Redirect Base | washingtontimes.com |
Domain IPs | 100.26.30.168, 34.192.124.80 |
Redirect IPs | 104.22.58.64, 104.22.59.64, 172.67.8.119 |
Response IP | 104.22.59.64 |
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://washtimes.com/.well-known/trust.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://washtimes.com/trust.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.washtimes.com/.well-known/trust.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.washtimes.com/trust.txt |
Result | Failed fetching resource - Server returned a client error (403). |
Last Successful Scan
Scanned | 2023-12-29T21:12:57+00:00 |
URL | https://washtimes.com/.well-known/trust.txt |
Redirect | https://www.washingtontimes.com:443/.well-known/trust.txt/ |
Redirect Domain | www.washingtontimes.com |
Redirect Base | washingtontimes.com |
Domain IPs | 100.26.30.168, 34.192.124.80 |
Redirect IPs | 104.22.58.64, 104.22.59.64, 172.67.8.119 |
Response IP | 104.22.59.64 |
Found | No |
Not Found Reason | Resource doesn't exist. |