SSL Check WHOIS
Dashboard / Security Report

flybase.net

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

No HTTPS on flybase.net

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

52.222.169.117 IPv4 · Port 443 accepted the connection, but no TLS handshake was completed: the server answered with the TLS alert “handshake_failure”.
52.222.169.19 IPv4 · Port 443 accepted the connection, but no TLS handshake was completed: the server answered with the TLS alert “handshake_failure”.
52.222.169.36 IPv4 · Port 443 accepted the connection, but no TLS handshake was completed: the server answered with the TLS alert “handshake_failure”.
52.222.169.52 IPv4 · Port 443 accepted the connection, but no TLS handshake was completed: the server answered with the TLS alert “handshake_failure”.
Checked 2026-11-04 23:10 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)
flybase.net403 Forbidden (unencrypted)TLS handshake failed
www.flybase.net403 Forbidden (unencrypted)TLS handshake failed
  • flybase.net is served over plain HTTP only: everything visitors send and receive is unencrypted and can be read or changed on the way.
  • www.flybase.net has no working HTTPS either (TLS handshake failed).

TLS History & Relations

Everything our scans have seen for flybase.net, first seen 2026-10-29.

Addresses

AddressCertificateSeen
52.222.169.19 no TLS 2026-11-04
52.222.169.36 no TLS 2026-11-04
52.222.169.52 no TLS 2026-11-04
52.222.169.117 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:10No HTTPS— 52.222.169.19, 52.222.169.36, 52.222.169.52, 52.222.169.117

Other hosts seen on the same addresses