SSL Check WHOIS
Dashboard / Security Report

launch1.spaceship.net

Overall grade based on: IPv4: 0 of 1 complete, 1 unreachable · IPv6: 0 of 1 complete, 1 pending — IPv6 results are added below when their scan finishes; they do not count until then.
IPv6 scan in progress
2400:cb00:2049:1::a29f:1a26 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).

The IPv4 report below is complete. IPv6 results will be added to this page automatically when the scan finishes.

No HTTPS over IPv4 on launch1.spaceship.net

Port 443 accepts connections on its IPv4 address, but no TLS handshake is completed: there is no working HTTPS. IPv6 is still being checked; this page updates when it finishes.

162.159.26.38 IPv4 · Port 443 accepted the connection, but no TLS handshake was completed: the server answered with the TLS alert “handshake_failure”.
Checked 2026-11-17 01:54 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)
launch1.spaceship.net409 Conflict (unencrypted)TLS handshake failed
  • launch1.spaceship.net is served over plain HTTP only: everything visitors send and receive is unencrypted and can be read or changed on the way.

DNS Records

As a public resolver answered for launch1.spaceship.net and its domain spaceship.net. Looked up 2026-11-17 01:54 UTC · today

TypeRecords
launch1.spaceship.net
A
AAAA
MX None
SPF None
spaceship.net
A
AAAA None
NS
launch1.spaceship.com launch2.spaceship.com
MX
5 mx1.jellyfish.systems 10 mx2.jellyfish.systems
SPF
v=spf1 mx include:sendgrid.net -all

TLS History & Relations

Everything our scans have seen for launch1.spaceship.net, first seen 2026-11-17.

Addresses

AddressCertificateSeen
162.159.26.38 no TLS 2026-11-17

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-17 01:54No HTTPS— 162.159.26.38