Skip to content
https://washingtontimes.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Amsterdam, Netherlands
301 Moved Permanently
Checks
9
5 PASS 3 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.washingtontimes.com/
200https://washingtontimes.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://washingtontimes.com/ → https://washingtontimes.com:443/

Consistent

B
TLS Certificate Expiry & Recommendations
81 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

81
days left
0d 30d 60d 90d+

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
2 A records, 9 ms lookup
PASS
2 A records, 9 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 100.24.200.226, 52.202.194.212
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: dora.ns.cloudflare.com, jake.ns.cloudflare.com
Info::
5 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 9 ms
Got: 9 ms
A100.24.200.226, 52.202.194.212
AAAA—
CNAME—
NSdora.ns.cloudflare.com, jake.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 alt4.aspmx.l.google.com
10 alt3.aspmx.l.google.com
TXT
IPROTA_D63985-XXX
_globalsign-domain-verification=1qNwvTrnfWSyToTMRe-GuEe2yrr1o9v_M7TXOF7hGm
_globalsign-domain-verification=n0b8SvOmFjFo5XsQryM_ctBNsI3-rVwKtYMU7d5YlX
apple-domain-verification=2rIeDhQ5nM0P7R0P
facebook-domain-verification=enux1luw6ilrt2pr8bqisi0zmt30lu
google-site-verification=HL6iKtLBsqb-Bhbm8D_a0_wFYzaSmYTaPrbr3_L4c5U
google-site-verification=_7LdiHTEfzxvKAeBAB9K8aLM75CdEfP1FEFYtAq3gkA
google-site-verification=kgoDrq76vNYZKOf6bWnY4lZysdF28twyMlq85sX1R00
gucnm6klc8qdp0pkiipthpb359
SPF v=spf1 mx a ip4:144.86.165.15 ip4:34.198.201.16 ip4:51.161.116.198 include:_spf....
CAALookup not available with standard resolver
Resolved in 9 ms

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A
Redirect Chain
1 redirect(s), 420 ms total
PASS
1 redirect(s), 420 ms total
Info::
Single redirect
Got: https://washingtontimes.com → https://www.washingtontimes.com:443/ (301)
Info::
WWW normalization redirect

https://washingtontimes.com

380 ms · HTTP/1.1

301

https://www.washingtontimes.com:443/

40 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://washingtontimes.com301380 msHTTP/1.1awselb/2.0
2https://www.washingtontimes.com:443/20040 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 8 URLs
PASS
robots.txt present, sitemap with 8 URLs
Info::
robots.txt is present
Got: 3694 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 8 entries
Info::
Sitemap index with 8 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 3694 B Sitemaps referenced 5 User-agents Slurp, CCBot, GoogleProducer, YandexBot, omgilibot, Amazonbot, applebot, Spinn3r, Mail.RU_Bot, bingbot, msnbot, googlebot, Baiduspider, AhrefsBot, omgili, * Blocking No — crawling allowed
User-agent: YandexBot
Disallow: /apps/
Disallow: /search/
Disallow: /wire-*
Disallow: /budget/
Disallow: /guns/
Disallow: /taxes/
Disallow: /users/
Disallow: /accounts/
Disallow: /upi-breaking/
Disallow: /weather/
Disallow: /account/
Disallow: /voting/
Disallow: /mailfriend
Disallow: /admin
Disallow: /comments
Disallow: /offensivecontent/
Disallow: /accounts
Disallow: /ajax

User-agent: Spinn3r
Disallow: /apps/
Disallow: /search/
Disallow: /wire-*
Disallow: /budget/
Disallow: /guns/
Disallow: /taxes/
Disallow: /users/
Disallow: /accounts/
Disallow: /upi-breaking/
Disallow: /weather/
Disallow: /account/
Disallow: /voting/
Disallow: /mailfriend
Disallow: /admin
Disallow: /comments
Disallow: /offensivecontent/
Disallow: /accounts
Disallow: /ajax
Crawl-delay: 30

User-agent: Mail.RU_Bot
Disallow: /apps/
Disallow: /search/
Disallow: /wire-*
Disallow: /budget/
Disallow: /guns/
Disallow: /taxes/
Disallow: /users/
Disallow: /accounts/
Disallow: /upi-breaking/
Disallow: /weather/
Disallow: /account/
Disallow: /voting/
Disallow: /mailfriend
Disallow: /admin
Disallow: /comments
Disallow: /offensivecontent/
Disallow: /accounts
Disallow: /ajax
Crawl-delay: 60

User-agent: Baiduspider
Allow: /news/
Disallow: /apps/
Crawl-delay: 30

User-agent: Slurp
Allow: /
Crawl-delay: 10

User-agent: AhrefsBot
Disallow: /

User-agent: bingbot
Allow: /
Disallow: /admin
Disallow: /newsletters/modal/
Disallow: /atom/
Disallow: /topics/
Disallow: /media/
Crawl-delay: 1

User-agent: msnbot
Allow: /news/
Disallow: /apps/
Disallow: /search/
Disallow: /wire-*
Disallow: /budget/
Disallow: /guns/
Disallow: /taxes/
Disallow: /users/
Disallow: /accounts/
Disallow: /upi-breaking/
Disallow: /weather/
Disallow: /account/
Disallow: /voting/
Disallow: /mailfriend
Disallow: /admin
Disallow: /comments
Disallow: /offensivecontent/
Disallow: /accounts
Disallow: /ajax
Crawl-delay: 1

User-agent: CCBot
Disallow: /

User-agent: omgilibot
Disallow: /

User-agent: omgili
Disallow: /

User-agent: GoogleProducer
Allow: /atom/

User-agent: Amazonbot
Disallow: /

User-agent: applebot
Allow: /
Disallow: /atom/
Disallow: /topics/
Disallow: /media/
Disallow: /news/2020/
Disallow: /news/2021/
Disallow: /news/2019/
Disallow: /news/2018/
Disallow: /news/2017/
Disallow: /news/2016/
Disallow: /news/2015/
Disallow: /news/2014/
Disallow: /news/2013/
Disallow: /news/2012/
Disallow: /news/2011/
Disallow: /news/2010/
Disallow: /news/2009/
Disallow: /news/2008/
Disallow: /news/2007/
Disallow: /news/2006/
Disallow: /news/2005/
Disallow: /news/2004/
Disallow: /news/2003/
Disallow: /news/2002/
Disallow: /news/2001/
Disallow: /news/2000/
Disallow: /news/1999/
Disallow: /news/1998/
Disallow: /news/1997/
Disallow: /news/1996/
Disallow: /news/1995/
Disallow: /news/1994/
Crawl-delay: 20

User-agent: *
Allow: /*utm_medium=*
Disallow: /apps/
Disallow: /search/
Disallow: /wire-*
Disallow: /budget/
Disallow: /guns/
Disallow: /taxes/
Disallow: /users/
Disallow: /accounts/
Disallow: /upi-breaking/
Disallow: /weather/
Disallow: /account/
Disallow: /voting/
Disallow: /mailfriend
Disallow: /admin
Disallow: /comments
Disallow: /offensivecontent/
Disallow: /accounts
Disallow: /ajax
Disallow: /higher-ground/2*
Disallow: /*twitter.com*

User-agent: googlebot
Allow: /
Disallow: /news/2025/feb/26/new-fbi-whistleblower-disclosures-identify-agent-assigned-infiltrate/
Disallow: /*twitter.com*

Host: www.washingtontimes.com
Sitemap: https://www.washingtontimes.com/sitemap_index.xml
Sitemap: https://www.washingtontimes.com/sitemap-stories.xml
Sitemap: https://www.washingtontimes.com/sitemap-entries.xml
Sitemap: https://www.washingtontimes.com/news_sitemap.xml
Sitemap: https://www.washingtontimes.com/sitemap-video-index.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 8 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
washingtontimes.com — via DNC Holdings, Inc., 28 years old, hosted on AWS
PASS
washingtontimes.com — via DNC Holdings, Inc., 28 years old, hosted on AWS
Info::
Domain registered until Sep 13, 2026 (4 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: DNC Holdings, Inc.
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: AWS
Got: AS14618
Domain expiry

89 days

September 13, 2026

SSL certificate

81 days

Issued by Amazon

Domain age

28 years

Registered September 14, 1998

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

52.202.194.212

Registrar

DNC Holdings, Inc.

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar DNC Holdings, Inc.
Created September 14, 1998 (28 years ago)
Expires September 13, 2026 (4 months)
Last Updated July 30, 2025
Name Servers dora.ns.cloudflare.com, jake.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 52.202.194.212
ASN AS14618 (AMAZON-AES - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.2s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more ▾

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A+
HTTP Probe Timing
Total 376 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
4 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
92 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
187 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
377 ms
Total Time Total request time from DNS lookup through full response.
377 ms

Connection waterfall

DNS Lookup 4 ms TCP Connect 92 ms TLS Handshake 187 ms Server Processing 94 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback