/.well-known/

Log In Sign Up

washingtontimes.com

/.well-known/ resources for washingtontimes.com

Site Scan

Site Details

Site Domain	washingtontimes.com
Base Domain	washingtontimes.com
Added	2021-02-26T13:57:05+00:00
Last Scan	2024-10-27T03:46:39+00:00
Next Scan	2024-11-03T03:46:39+00:00

Found Resources

Resource	Found At	Scan Status
ads.txt	2024-10-27T03:46:39+00:00	Ok
robots.txt	2024-10-27T03:46:39+00:00	Ok

Authorized Digital Sellers

Resource Details

Resource	ads.txt
Status	Ok
Archive	Check Archive

Scan Requests (1)

URL	https://washingtontimes.com/ads.txt
Result	Resource Found.

Last Scan

Scanned	2024-10-27T03:46:39+00:00
URL	https://washingtontimes.com/ads.txt
Redirect	https://www.washingtontimes.com:443/ads.txt
Redirect Domain	www.washingtontimes.com
Redirect Base	washingtontimes.com
Domain IPs	34.194.234.100, 34.234.125.69
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	fee0c2ee6b1d4c3eda4475bf549a5c36c7b0b95f0a4ddaeaee08335e0b40f118
SimHash	16cc1b7252e3

Back to top

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://washingtontimes.com/app-ads.txt
Result	Failed fetching resource - Server returned a client error (403).

URL	https://www.washingtontimes.com/app-ads.txt
Result	Failed fetching resource - Server returned a client error (403).

Last Successful Scan

Scanned	2023-12-29T09:19:13+00:00
URL	https://washingtontimes.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.

Back to top

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://washingtontimes.com/.well-known/apple-app-site-association
Result	Failed fetching resource - Server returned a client error (403).

URL	https://washingtontimes.com/apple-app-site-association
Result	Failed fetching resource - Server returned a client error (403).

URL	https://www.washingtontimes.com/.well-known/apple-app-site-association
Result	Failed fetching resource - Server returned a client error (403).

URL	https://www.washingtontimes.com/apple-app-site-association
Result	Failed fetching resource - Server returned a client error (403).

Last Successful Scan

Scanned	2023-12-29T09:19:13+00:00
URL	https://washingtontimes.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.58.64
Found	No
Not Found Reason	Resource doesn't exist.

Back to top

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://washingtontimes.com/.well-known/assetlinks.json
Result	Failed fetching resource - Server returned a client error (403).

URL	https://www.washingtontimes.com/.well-known/assetlinks.json
Result	Failed fetching resource - Server returned a client error (403).

Last Successful Scan

Scanned	2023-12-29T09:19:13+00:00
URL	https://washingtontimes.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.

Back to top

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://washingtontimes.com/.well-known/gpc.json
Result	Failed fetching resource - Server returned a client error (403).

URL	https://www.washingtontimes.com/.well-known/gpc.json
Result	Failed fetching resource - Server returned a client error (403).

Last Successful Scan

Scanned	2023-12-29T09:19:13+00:00
URL	https://washingtontimes.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	172.67.8.119
Found	No
Not Found Reason	Resource doesn't exist.

Back to top

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://washingtontimes.com/.well-known/nodeinfo
Result	Failed fetching resource - Server returned a client error (403).

URL	https://www.washingtontimes.com/.well-known/nodeinfo
Result	Failed fetching resource - Server returned a client error (403).

Last Successful Scan

Scanned	2023-12-29T09:19:13+00:00
URL	https://washingtontimes.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.

Back to top

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://washingtontimes.com/.well-known/openid-configuration
Result	Failed fetching resource - Server returned a client error (403).

URL	https://www.washingtontimes.com/.well-known/openid-configuration
Result	Failed fetching resource - Server returned a client error (403).

Last Successful Scan

Scanned	2023-12-29T09:19:13+00:00
URL	https://washingtontimes.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.

Back to top

Robots Exclusion Standard

Resource Details

Resource	robots.txt
Status	Ok
Archive	Check Archive

Scan Requests (1)

URL	https://washingtontimes.com/robots.txt
Result	Resource Found.

Last Scan

Scanned	2024-10-27T03:46:39+00:00
URL	https://washingtontimes.com/robots.txt
Redirect	https://www.washingtontimes.com:443/robots.txt
Redirect Domain	www.washingtontimes.com
Redirect Base	washingtontimes.com
Domain IPs	34.194.234.100, 34.234.125.69
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	c8004b5d24949b9048629ed418e1550e115abbe1b478f9505eab816b521182fa
SimHash	2346d46281d0

Back to top

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://washingtontimes.com/.well-known/security.txt
Result	Failed fetching resource - Server returned a client error (403).

URL	https://washingtontimes.com/security.txt
Result	Failed fetching resource - Server returned a client error (403).

URL	https://www.washingtontimes.com/.well-known/security.txt
Result	Failed fetching resource - Server returned a client error (403).

URL	https://www.washingtontimes.com/security.txt
Result	Failed fetching resource - Server returned a client error (403).

Last Successful Scan

Scanned	2023-12-29T09:19:13+00:00
URL	https://washingtontimes.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.

Back to top

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://washingtontimes.com/.well-known/trust.txt
Result	Failed fetching resource - Server returned a client error (403).

URL	https://washingtontimes.com/trust.txt
Result	Failed fetching resource - Server returned a client error (403).

URL	https://www.washingtontimes.com/.well-known/trust.txt
Result	Failed fetching resource - Server returned a client error (403).

URL	https://www.washingtontimes.com/trust.txt
Result	Failed fetching resource - Server returned a client error (403).

Last Successful Scan

Scanned	2023-12-29T09:19:13+00:00
URL	https://washingtontimes.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.

Back to top