SSL Check WHOIS
Dashboard / Security Report

app.for3sight.io

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

No HTTPS on app.for3sight.io

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

13.248.213.45 IPv4 · Port 443 accepted the connection, but no TLS handshake was completed: the server answered with the TLS alert “unrecognized_name”.
76.223.67.189 IPv4 · Port 443 accepted the connection, but no TLS handshake was completed: the server answered with the TLS alert “unrecognized_name”.
Checked 2026-11-04 23:03 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)
app.for3sight.io200 OK (unencrypted)TLS handshake failed
  • app.for3sight.io 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 app.for3sight.io, first seen 2026-11-01.

Addresses

AddressCertificateSeen
13.248.213.45 no TLS 2026-11-04
76.223.67.189 no TLS 2026-11-04

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-04 23:03No HTTPS— 13.248.213.45, 76.223.67.189

Other hosts seen on the same addresses