Skip to content
https://latimes.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 Madrid, Spain
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.latimes.com/
200https://latimes.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://latimes.com/ → https://www.latimes.com:443/

Consistent

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

Certificate validity

72
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, 100 ms lookup
PASS
2 A records, 100 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 13.248.222.133, 76.223.88.230
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-452.awsdns-56.com, ns-1295.awsdns-33.org, ns-1610.awsdns-09.co.uk, ns-926.awsdns-51.net
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: 100 ms
Got: 100 ms
A13.248.222.133, 76.223.88.230
AAAA—
CNAME—
NSns-452.awsdns-56.com, ns-1295.awsdns-33.org, ns-1610.awsdns-09.co.uk, ns-926.awsdns-51.net
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 alt4.aspmx.l.google.com
10 alt3.aspmx.l.google.com
TXT
MS=ms84911362
google-site-verification=0QPIq2D0D26lPn2VMKR_gwmqwwDK7wgJHFwtq4Tfeco
h0cbo410n1chebj71kbs8q5i8d
tsh0eincv0t3bkcva1c667uro2
cfkmds6ga7654tqcg9mlurf3k6
docusign=453b6b21-b568-4004-a8f2-1f380829ad43
did=did:plc:d2jith367s6ybc3ldsusgdae
eg1tppoar646d8rqa33u0sml3n
7oq87bhdv6itabagtvsdpmul82
yahoo-verification-key=Ciu/bCX+AjkCYWVEJujDW87A2yvpX7P/3oshj+CNWL8=
perplexity-ai-domain-verification-yjtp28=sgBMn1poEbOGFaINpjgWeJHTt
brave-ledger-verification=cf086c207603abfa9afd6b8df9d777e0d9b789e44a6776901cfbc6...
google-site-verification=WTDW0cjEz4J9pWQ9NuMKwwGnrcjOL-VX6IBj2uiOeuM
anthropic-domain-verification-3t139r=kQ0TFtp3S4RF2437XVJZRA30j
7smmkkb798j8eqi401d3q63bm8
apple-domain-verification=SRTHJpUVgV2MwCx1
google-site-verification=fYTWZ7SJbOe5bGtSQicUJCm7J29yhRLflY8BzxnAv1c
klaviyo-site-verification=WzaHYE
slack-domain-verification=YIhuR9QT67Qcp8phI1Pb1vfhADwTYhXwmzBVDBoD
8tmpnpldi5uf9kq1c8gqt2365s
docusign=2d955b28-e01f-4abe-abb8-048933e31be9
6ufavjtn14r307ahi6bebk12ch
facebook-domain-verification=drgkoxezy6edhuvga4m8enwp9p5lpo
fastly-domain-delegation-7nrjqkfn4ijvfvumyfpr-00443853-2025-07-01
SPF v=spf1 include:spf.protection.outlook.com include:spfgoempyrean.latimes.com incl...
atlassian-domain-verification=avbLPU/ADIkquoCsJ4H4uUbecC5pukRw8QK8hUI1RT6Bz1T37I...
canva-site-verification=C9E6EFcG4a0EnUgrhkrK-w
google-site-verification=1j4vVJRfXKvGgNOxUn5x3gVHixSXp4d2zsPizV5hCBA
globalsign-domain-verification=KaParXxs1OHDy7o8CMbPpHBN-2m_mzwdPqKMMQ66a6
1t01p8l91of55fv98hq62avf7r
OrGvTtRy5V5MRiw9GUf61MfeMi4fOpeA5P+VvKpZg+nECQ60jZjw5kotD1BMCNARJ+Uc4qDYR5vTKjQ0...
google-site-verification=9--yY3liEoth6rMdNuUnIHjul8sH4Oh-U48nx8LhEus
CAALookup not available with standard resolver
Resolved in 100 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), 680 ms total
PASS
1 redirect(s), 680 ms total
Info::
Single redirect
Got: https://latimes.com → https://www.latimes.com:443/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 680 ms total
Got: 680 ms

https://latimes.com

595 ms · HTTP/1.1

301

https://www.latimes.com:443/

85 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://latimes.com301595 msHTTP/1.1awselb/2.0
2https://www.latimes.com:443/20085 msHTTP/1.1N/A

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 615 URLs
PASS
robots.txt present, sitemap with 615 URLs
Info::
robots.txt is present
Got: 1768 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 615 entries
Info::
Sitemap index with 615 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1768 B Sitemaps referenced 2 User-agents Googlebot-News, Twitterbot, Mediapartners-Google, AmazonAdBot, Bytespider, discobot, GPTBot, ClaudeBot, Diffbot, ImagesiftBot, omgili, omgilibot, * Blocking No — crawling allowed
User-agent: *
Disallow: /search
Disallow: /recipes/search
Disallow: /changebrowser
Disallow: /thirdpartyservice
Disallow: /*/thirdpartyservice
Disallow: /config/
Disallow: /*/config
Disallow: /dzcfg
Disallow: /*/dzcfg
Disallow: /*/test-template
Disallow: /test/
Disallow: /includes/
Disallow: /_comments/
Disallow: /deeplinkid/
Disallow: /searchsuggest
Disallow: /*/searchsuggest
Disallow: /svgimageproc
Disallow: /hive/
Disallow: /get-galleryfragment*
Disallow: /gs-*

User-agent: Googlebot-News
Disallow: /*-ugc-*.html
Disallow: /about/
Disallow: /cbp-*.html
Disallow: /*/cbp-*.html
Disallow: /bp/*
Disallow: /*-adstory.html
Disallow: /*sns-ap
Disallow: /*photogallery
Disallow: /brandpublishing/
Disallow: /*/brandpublishing/
Disallow: /shopping/
Disallow: /*/shopping/
Disallow: /paid-posts/
Disallow: /*/paid-posts/
Disallow: /search
Disallow: /*/search
Disallow: /changebrowser
Disallow: /thirdpartyservice
Disallow: /*/thirdpartyservice
Disallow: /config/
Disallow: /*/config
Disallow: /dzcfg
Disallow: /*/dzcfg
Disallow: /*/test-template
Disallow: /test/
Disallow: /_comments/
Disallow: /deeplinkid/
Disallow: /searchsuggest
Disallow: /*/searchsuggest
Disallow: /svgimageproc
Disallow: /hive/
Disallow: /get-galleryfragment*
Disallow: /sponsored/
Disallow: /*/sponsored/

User-agent: Twitterbot
Allow: /

User-agent: Mediapartners-Google
Allow: /

User-agent: AmazonAdBot
Allow: /

User-agent: Bytespider
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: Diffbot
Disallow: /

User-agent: discobot
Disallow: /

User-agent: GPTBot
Disallow: /

User-agent: ImagesiftBot
Disallow: /

User-agent: omgili
Disallow: /

User-agent: omgilibot
Disallow: /

Sitemap: https://www.latimes.com/sitemaps/sitemap.xml
Sitemap: https://www.latimes.com/news-sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 615 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
latimes.com — via MarkMonitor Inc., 35 years, 10 months old, hosted on AWS
PASS
latimes.com — via MarkMonitor Inc., 35 years, 10 months old, hosted on AWS
Info::
Domain registered until Dec 11, 2027 (1 years, 8 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: MarkMonitor 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: AS16509
Domain expiry

515 days

December 11, 2027

SSL certificate

72 days

Issued by Amazon

Domain age

35 years, 10 months

Registered December 12, 1990

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

13.248.222.133

Registrar

MarkMonitor Inc.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar MarkMonitor Inc.
Created December 12, 1990 (35 years, 10 months ago)
Expires December 11, 2027 (1 years, 8 months)
Last Updated November 9, 2025
Name Servers ns-1295.awsdns-33.org, ns-1610.awsdns-09.co.uk, ns-452.awsdns-56.com, ns-926.awsdns-51.net
DNSSEC Not enabled
Hosting
IP Address 13.248.222.133
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.3s)

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 639 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
29 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
457 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
639 ms
Total Time Total request time from DNS lookup through full response.
639 ms

Connection waterfall

DNS Lookup 29 ms TCP Connect 1 ms TLS Handshake 457 ms Server Processing 152 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