indiatimes.in
Overall grade based on: IPv4: 0 of 1 complete, 1 unreachable · IPv6: none
No HTTPS on indiatimes.in
Port 443 accepts connections on its IPv4 address, but no TLS handshake is completed: there is no working HTTPS.
223.165.27.134 IPv4 · Port 443 accepted the connection, but no TLS handshake was completed: the server closed the connection.
Checked 2026-11-08 21:51 UTC
Site Access: HTTP and HTTPS
What a visitor typing each address gets, and where its redirects end (up to 5 are followed), as seen from our scanner.
| Host | http:// (port 80) | https:// (port 443) |
|---|---|---|
| indiatimes.in | 200 OK (unencrypted) | TLS handshake failed |
| www.indiatimes.in | 200 OK (unencrypted) | TLS handshake failed |
- indiatimes.in is served over plain HTTP only: everything visitors send and receive is unencrypted and can be read or changed on the way.
- www.indiatimes.in has no working HTTPS either (TLS handshake failed).
DNS Records
As a public resolver answered for indiatimes.in. Looked up 2026-11-08 21:51 UTC · 9 days ago
| Type | Records |
|---|---|
| A | |
| AAAA | None |
| NS | ns-1193.awsdns-21.org ns-1917.awsdns-47.co.uk ns-34.awsdns-04.com ns-735.awsdns-27.net |
| MX | 1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com |
| SPF | v=spf1 include:_spf.google.com -all |
TLS History & Relations
Everything our scans have seen for indiatimes.in, first seen 2026-11-08.
Addresses
| Address | Certificate | Seen |
|---|---|---|
| 223.165.27.134 | no TLS | 2026-11-08 |
TLS history (a row per change; repeated checks only extend it)
| Since → last checked (UTC) | Grade | TLS | Certificates | Addresses |
|---|---|---|---|---|
| 2026-11-08 21:51 | No HTTPS | — | 223.165.27.134 |