Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations169 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- 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
BCDN & DeliveryAkamaiREVIEW
A+DNS Records1 A records, 29 ms lookupPASS
| A | 23.37.175.74 |
| AAAA | 2a02:26f0:1380:2ad::3621, 2a02:26f0:1380:287::3621 |
| CNAME | — |
| NS | a26-66.akam.net, a1-127.akam.net, a28-67.akam.net, a2-65.akam.net, a9-64.akam.net |
| MX | 5 bounce.indiatimes.com |
| TXT | ckm2dcmtgb0sfndy095nyw42gcfcgrmq SPF v=spf1 include:_rng3.indiatimes.com include:_rng2.indiatimes.com include:tilc.in... SPF v=spf1 include:tilc.in -all kc1sjp3t0szkcng64gxlfy7rh5yr1rjj kgtpgmprbsnc9zrjqzkphdlkpdjslx97 google-site-verification=y9c59jMZUV2_mIpNBzMIp_Y_OphR1s7XBXF _1hxzw3ua6b8lslhbxqe7v2ommpzqeh7 _9zy0ue8xyf79j4p4zbyykbw897xaj7w google-site-verification=gS_4EO6y4tS3tWXaVsVsXuJZLQ_LMIhrbT9jFVb7Ge8 |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.
Learn more ▾ ▴
Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.
Source: SRE practice / DNS architecture
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
ARedirect Chain1 redirect(s), 101 ms totalPASS
https://indiatimes.com
7 ms · HTTP/1.1
https://www.indiatimes.com/
94 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://indiatimes.com | 301 | 7 ms | HTTP/1.1 | AkamaiGHost |
| 2 | https://www.indiatimes.com/ | 200 | 94 ms | HTTP/1.1 | Bhoot |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (1 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 9 URLsPASS
#robots.txt PS
User-agent: AmazonAdBot
Allow: /
Allow: /*
User-agent: meta-externalagent
Disallow: /
User-agent: *
Allow: /
Disallow: *.php*
Disallow: */7176/*
Disallow: */whatshot/*
Disallow: */wattpad/*
Disallow: */uc_feed/*
Disallow: */brief/*
Disallow: */search/*
Disallow: */user/*
Disallow: */idtoin/*
Disallow: */video_player/*
Disallow: */blog/*
Disallow: */content/*
Disallow: */seoarchive/*
Disallow: */trends/audios/*
Disallow: */trends/videos/*
Disallow: *{*
Disallow: *?ref=*
Disallow: *?v=*
Disallow: *?no_fullscreen_*
Disallow: *?symbol=*
Disallow: */?date=*
Disallow: *?fb_comment_id=*
Disallow: *?_twitter*
Disallow: */2011/*
Disallow: */2012/*
Disallow: */2013/*
Disallow: */2014/*
Disallow: */2015/*
Disallow: */2016/*
Disallow: */2017/*
Disallow: */2018/*
Disallow: */2019/*
Disallow: */2020/*
Disallow: */2021/*
Disallow: */2022/*
Disallow: */2023/*
Disallow: */2024/*
Disallow: *.ttf*
Disallow: *.woff*
Disallow: *.png*
Disallow: *.jpg*
#Sitemaps
Sitemap:https://www.indiatimes.com/sitemap.xml
Sitemap:https://www.indiatimes.com/sitemap-news.xml
Sitemap:https://www.indiatimes.com/sitemap-posts-index-2024.xml
Sitemap:https://www.indiatimes.com/hindi/sitemap-ampstories-2024.xml
Sitemap:https://www.indiatimes.com/staticsitemap/id-454/sitemap-index.xml
Sitemap:https://www.indiatimes.com/staticsitemap/id-454/sitemap-48hours.xml
- https://www.indiatimes.com/sitemap-autho...
- https://www.indiatimes.com/sitemap-ampst...
- https://www.indiatimes.com/sitemap-pages...
- https://www.indiatimes.com/sitemap-news....
- https://www.indiatimes.com/hindi/sitemap...
- https://www.indiatimes.com/sitemap-posts...
- https://www.indiatimes.com/sitemap-posts...
- https://www.indiatimes.com/staticsitemap...
- https://www.indiatimes.com/staticsitemap...
A+Domain Intelligenceindiatimes.com — via Tucows Domains Inc., 29 years, 9 months oldPASS
130 days
November 21, 2026
169 days
Issued by DigiCert Inc
29 years, 9 months
Registered November 22, 1996
Not enabled
Protects against DNS spoofing
Unknown
2a02:26f0:1380:287::3621
Tucows Domains Inc.
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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.
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