SSL Check WHOIS
Dashboard / Security Report

www.tennis.net

Overall grade based on: IPv4: 0 of 2 complete, 2 unreachable · IPv6: none

No HTTPS on www.tennis.net

Port 443 does not answer on all 2 IPv4 addresses (connections time out).

165.160.13.20 IPv4 · No answer on port 443 (the connection timed out).
165.160.15.20 IPv4 · No answer on port 443 (the connection timed out).
Checked 2026-11-07 21:29 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.

Hosthttp:// (port 80)https:// (port 443)
www.tennis.net301 → https://www.pwptennis.com/ → No answer (timed out)No answer (timed out)
tennis.net301 → http://www.tennis.net/ → … → https://www.pwptennis.com/ → No answer (timed out)301 → https://www.tennis.net/ → No answer (timed out)
  • http://www.tennis.net redirects to HTTPS.
  • HTTPS works on tennis.net: visitors who use that name get an encrypted connection. View its report ›

DNS Records

As a public resolver answered for www.tennis.net and its domain tennis.net. Looked up 2026-11-07 21:29 UTC · 9 days ago

TypeRecords
www.tennis.net
A
AAAA None
MX None
SPF None
tennis.net
A
AAAA None
NS
ns1.netnames.net ns2.netnames.net ns5.netnames.net ns6.netnames.net
MX
10 cluster4.eu.messagelabs.com 20 cluster4a.eu.messagelabs.com
SPF
v=spf1 include:spf.messagelabs.com ?all

TLS History & Relations

Everything our scans have seen for www.tennis.net, first seen 2026-11-06.

Addresses

AddressCertificateSeen
165.160.13.20 no TLS 2026-11-07
165.160.15.20 no TLS 2026-11-07

TLS history (a row per change; repeated checks only extend it)

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-07 21:29No HTTPS— 165.160.13.20, 165.160.15.20

Other hosts seen on the same addresses