Skip to content
https://thetimes.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
79
GRADE
C
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
4 PASS 4 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

C
Crawlability
Action
robots.txt present, sitemap with 352 URLs
REVIEW
robots.txt present, sitemap with 352 URLs
Info::
robots.txt is present
Got: 2679 bytes
Critical::
robots.txt blocks all crawlers
Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 352 entries
Info::
robots.txt references sitemap

Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.

Why this matters

Disallow: / in robots.txt blocks every search crawler — the site becomes invisible in organic search.

Learn more

Common deployment mistake: a staging robots.txt with `User-agent: * / Disallow: /` ships to prod. The site falls out of search results within days. Verify your robots.txt is the production-intended version. If this is intentional (private site), no action needed.

Source: Google Search Central

robots.txt 200 OK
Size 2679 B Sitemaps referenced 6 User-agents GoogleOther, AdsBot-Google, facebookexternalhit, OnCrawl, GumGum-Bot, *, Googlebot-News, DuckDuckBot, adidxbot, Botify, Slackbot-LinkExpanding, Slack-ImgProxy, outbrain, APIs-Google, Applebot, proximic, ias_crawler, weborama-fetcher, AHC/2.1, CriteoBot/0.1, ChatGPT-User, Google-InspectionTool, Twitterbot, Bingbot, Snap URL Preview Service, TTD-Content, Leikibot, SirdataBot, EchoboxBot/1.0, Slurp, SemrushBot, peer39_crawler/1.0, Googlebot-Video, MicrosoftPreview, AmazonAdBot, parse.ly scraper, SmartologyBot, Googlebot, Mediapartners-Google, Yahoo Ad Monitoring, Pubmatic, AdDefend Site Context Crawler/1.0, Googlebot-Image, Screaming Frog SEO Spider, Chrome-Lighthouse, Slackbot, Dianomi, GPTBot, OAI-SearchBot Blocking Yes — all crawlers blocked
# This is the robots.txt file for thetimes.com
# The Times does not permit the unlicensed use of our content for large language models.
# Times Media Limited’s Terms of Use may be found at # https://www.thetimes.com/static/terms-and-conditions
# Contact enquiries@newslicensing.com for assistances


User-agent: *
Disallow: /

Sitemap: https://www.thetimes.com/sitemaps/news
Sitemap: https://www.thetimes.com/sitemaps/articles/2025
Sitemap: https://www.thetimes.com/sitemaps/articles
Sitemap: https://www.thetimes.com/sitemaps/sitemap.xml
Sitemap: https://www.thetimes.com/subscribe/sitemap_index.xml
Sitemap: https://www.thetimes.com/static/sitemap_index.xml


User-agent: Googlebot
User-agent: Googlebot-Image
User-agent: Googlebot-Video
User-agent: Googlebot-News
User-agent: Google-InspectionTool
User-agent: GoogleOther
User-agent: APIs-Google
User-agent: Mediapartners-Google
User-agent: DuckDuckBot
User-agent: Slurp
User-agent: Twitterbot
User-agent: Bingbot
User-agent: adidxbot
User-agent: MicrosoftPreview
User-agent: Applebot
User-agent: AdsBot-Google
User-agent: AmazonAdBot
User-agent: facebookexternalhit
User-agent: Yahoo Ad Monitoring
User-agent: parse.ly scraper
User-agent: Screaming Frog SEO Spider
User-agent: SemrushBot
User-agent: Botify
User-agent: OnCrawl
User-agent: Chrome-Lighthouse
User-agent: Slackbot-LinkExpanding
User-agent: Slack-ImgProxy
User-agent: Slackbot
User-agent: Snap URL Preview Service
User-agent: proximic
User-agent: GumGum-Bot
User-agent: TTD-Content
User-agent: Pubmatic 
User-agent: ias_crawler
User-agent: outbrain
User-agent: Leikibot
User-agent: weborama-fetcher
User-agent: AHC/2.1
User-agent: SirdataBot
User-agent: peer39_crawler/1.0
User-agent: EchoboxBot/1.0
User-agent: CriteoBot/0.1
User-agent: AdDefend Site Context Crawler/1.0
User-agent: SmartologyBot
User-agent: Dianomi
User-agent: ChatGPT-User
User-agent: GPTBot
User-agent: OAI-SearchBot



Allow: /
Allow: /ads.txt
Allow: /world/*?*region=*
Allow: /sport/*?*region=*

Disallow: /api/
Disallow: /archive/page/
Disallow: /archive/article/
Disallow: /article/category/
Disallow: /interactives/
Disallow: /my-articles
Disallow: /my-articles/
Disallow: /player/brightcove/
Disallow: /topic/bbc
Disallow: /tto/archive/article/
Disallow: /tto/archive/find/
Disallow: /tto/archive/frame/article/
Disallow: /tto/archive/page/
Disallow: /*?*shareToken=*
Disallow: /*?*region=*
Disallow: /*?s=*
Disallow: /*&s=*
Disallow: /?_ga
Disallow: /?ExternalDataReference
Disallow: /search?*
Disallow: /search/browse-by-day*
Disallow: /article/this-article-has-been-deleted*
Disallow: /article/this-article-has-been-removed*
Disallow: /article/this-article-is-no-longer-available*
C
URL Variants
Action
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
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.thetimes.com/
200https://thetimes.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

307http://thetimes.com/ https://thetimes.com/

Use 301 (permanent) instead of 302 (temporary)

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

Certificate validity

68
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
3 A records, 46 ms lookup
PASS
3 A records, 46 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 52.208.17.106, 34.240.28.43, 54.76.240.177
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1158.awsdns-16.org, ns-195.awsdns-24.com, ns-1610.awsdns-09.co.uk, ns-812.awsdns-37.net
Info::
2 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: 46 ms
Got: 46 ms
A52.208.17.106, 34.240.28.43, 54.76.240.177
AAAA
CNAME
NSns-1158.awsdns-16.org, ns-195.awsdns-24.com, ns-1610.awsdns-09.co.uk, ns-812.awsdns-37.net
MX
1 mxa-00596a01.gslb.pphosted.com
10 mxb-00596a01.gslb.pphosted.com
TXT
google-site-verification=74cuTCQF4OE0tm4h3xITeG2YOTRClvDZsIbyk8-cDJ0
google-site-verification=IQWGKPWkMir2bOT7RHGAP_cnTlBTaKK79GfUyVlvMVM
google-gws-recovery-domain-verification=47936229
ZOOM_verify_i7QA2Y0GzsIJIlZmqimrrK
adobe-idp-site-verification=564934793fede20477f3d065060f7c1557b4fd1d8343e33fea1c...
SPF v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com include:spf.flowmailer.net ~...
google-site-verification=a3KFcGlir95_hLciDr9SEJQ6sDJ1kDa36ZCqXhtAGbo
google-site-verification=zjgSEMb6CzkplYfsVfEnM5Q9zmd0pc0wO0hPv5qXXsQ
CAALookup not available with standard resolver
Resolved in 46 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), 594 ms total
PASS
1 redirect(s), 594 ms total
Info::
Single redirect
Got: https://thetimes.com → https://www.thetimes.com (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 594 ms total
Got: 594 ms

https://thetimes.com

159 ms · HTTP/1.1

301

https://www.thetimes.com

435 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://thetimes.com301159 msHTTP/1.1openresty/1.11.2.3
2https://www.thetimes.com200435 msHTTP/1.1CloudFront

See the visual redirect chain in the HTTP Probe tab →

A+
Domain Intelligence
thetimes.com — via MarkMonitor Inc., 31 years, 8 months old, hosted on AWS
PASS
thetimes.com — via MarkMonitor Inc., 31 years, 8 months old, hosted on AWS
Info::
Domain registered until Jan 10, 2027 (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

208 days

January 10, 2027

SSL certificate

68 days

Issued by Let's Encrypt

Domain age

31 years, 8 months

Registered January 11, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

54.76.240.177

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 January 11, 1995 (31 years, 8 months ago)
Expires January 10, 2027 (8 months)
Last Updated December 9, 2024
Name Servers ns-1158.awsdns-16.org, ns-1610.awsdns-09.co.uk, ns-195.awsdns-24.com, ns-812.awsdns-37.net
DNSSEC Not enabled
Hosting
IP Address 54.76.240.177
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 182 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
33 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
34 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
76 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
182 ms
Total Time Total request time from DNS lookup through full response.
182 ms

Connection waterfall

DNS Lookup 33 ms TCP Connect 34 ms TLS Handshake 76 ms Server Processing 38 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