SSL Check WHOIS
Dashboard / Security Report

closedforgood.org

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

No HTTPS on closedforgood.org

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

2.17.198.49 IPv4 · Port 443 accepted the connection, but no TLS handshake was completed: the server answered with the TLS alert “internal_error”.
2.17.198.59 IPv4 · Port 443 accepted the connection, but no TLS handshake was completed: the server answered with the TLS alert “internal_error”.
Checked 2026-11-18 04:19 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)
closedforgood.org400 Bad Request (unencrypted)TLS handshake failed
www.closedforgood.org301 → https://www.closedforgood.org/ → … → https://www.bnz.co.nz/about-us/great-things → 404 Not Found302 → https://www.bnz.co.nz/about-us/great-things → 404 Not Found
  • closedforgood.org is served over plain HTTP only: everything visitors send and receive is unencrypted and can be read or changed on the way.
  • HTTPS works on www.closedforgood.org: visitors who use that name get an encrypted connection. View its report ›

DNS Records

As a public resolver answered for closedforgood.org. Looked up 2026-11-18 04:19 UTC · today

TypeRecords
A
AAAA None
NS
a1-97.akam.net a16-65.akam.net a24-64.akam.net a3-67.akam.net a8-66.akam.net a9-65.akam.net
MX None
SPF
v=spf1 mx -all

TLS History & Relations

Everything our scans have seen for closedforgood.org, first seen 2026-11-18.

Addresses

AddressCertificateSeen
2.17.198.49 no TLS 2026-11-18
2.17.198.59 no TLS 2026-11-18

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-18 04:19No HTTPS— 2.17.198.49, 2.17.198.59

Other hosts seen on the same addresses