SSL Check WHOIS
Dashboard / Security Report

m1.vingle.net

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

No HTTPS on m1.vingle.net

Port 443 accepts connections on all 4 IPv4 addresses, but no TLS handshake is completed: there is no working HTTPS.

99.86.109.100 IPv4 · Port 443 accepted the connection, but no TLS handshake was completed: the server answered with the TLS alert “handshake_failure”.
99.86.109.120 IPv4 · Port 443 accepted the connection, but no TLS handshake was completed: the server answered with the TLS alert “handshake_failure”.
99.86.109.33 IPv4 · Port 443 accepted the connection, but no TLS handshake was completed: the server answered with the TLS alert “handshake_failure”.
99.86.109.65 IPv4 · Port 443 accepted the connection, but no TLS handshake was completed: the server answered with the TLS alert “handshake_failure”.
Checked 2026-10-27 10:25 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)
m1.vingle.net403 Forbidden (unencrypted)TLS handshake failed
  • m1.vingle.net is served over plain HTTP only: everything visitors send and receive is unencrypted and can be read or changed on the way.

TLS History & Relations

Everything our scans have seen for m1.vingle.net, first seen 2026-06-22.

Addresses

AddressCertificateSeen
99.86.109.33 no TLS 2026-10-27
99.86.109.65 no TLS 2026-10-27
99.86.109.100 no TLS 2026-10-27
99.86.109.120 no TLS 2026-10-27

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-10-27 10:25No HTTPS— 99.86.109.33, 99.86.109.65, 99.86.109.100, 99.86.109.120

Other hosts seen on the same addresses