SSL Check WHOIS
Dashboard / Security Report

payment.goog

Overall grade based on: IPv4: 0 of 4 complete, 4 unreachable · IPv6: 0 of 4 complete, 4 pending — IPv6 results are added below when their scan finishes; they do not count until then.
IPv6 scan in progress
2001:4860:4802:32::15 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2001:4860:4802:34::15 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2001:4860:4802:36::15 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2001:4860:4802:38::15 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 payment.goog

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

216.239.32.21 IPv4 · Port 443 accepted the connection, but no TLS handshake was completed: the server closed the connection.
216.239.34.21 IPv4 · Port 443 accepted the connection, but no TLS handshake was completed: the server closed the connection.
216.239.36.21 IPv4 · Port 443 accepted the connection, but no TLS handshake was completed: the server closed the connection.
216.239.38.21 IPv4 · Port 443 accepted the connection, but no TLS handshake was completed: the server closed the connection.
Checked 2026-10-23 22:23 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)
payment.goog404 Not Found (unencrypted)TLS handshake failed
www.payment.goog404 Not Found (unencrypted)TLS handshake failed
  • payment.goog is served over plain HTTP only: everything visitors send and receive is unencrypted and can be read or changed on the way.
  • www.payment.goog has no working HTTPS either (TLS handshake failed).

TLS History & Relations

Everything our scans have seen for payment.goog, first seen 2026-10-09.

Addresses

AddressCertificateSeen
216.239.32.21 no TLS 2026-10-23
216.239.34.21 no TLS 2026-10-23
216.239.36.21 no TLS 2026-10-23
216.239.38.21 no TLS 2026-10-23

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-10-23 22:23No HTTPS— 216.239.32.21, 216.239.34.21, 216.239.36.21, 216.239.38.21

Other hosts seen on the same addresses