SSL Check WHOIS
Dashboard / Security Report

act-node.com

Add this badge to your site

Shows this report's grade and links back to it. It is read from the stored report, never a new scan; a report older than 30 days also shows the month it was checked.

act-node.com: SSL/TLS scan incomplete (HTTPS Monitor)act-node.com?
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
2600:9000:2664:2a00:a:39ab:4f40:93a1 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2600:9000:2664:3c00:a:39ab:4f40:93a1 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2600:9000:2664:5c00:a:39ab:4f40:93a1 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2600:9000:2664:8a00:a:39ab:4f40:93a1 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 act-node.com

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.

18.245.199.3 IPv4 · Port 443 accepted the connection, but no TLS handshake was completed: the server answered with the TLS alert “handshake_failure”.
18.245.199.36 IPv4 · Port 443 accepted the connection, but no TLS handshake was completed: the server answered with the TLS alert “handshake_failure”.
18.245.199.61 IPv4 · Port 443 accepted the connection, but no TLS handshake was completed: the server answered with the TLS alert “handshake_failure”.
18.245.199.91 IPv4 · Port 443 accepted the connection, but no TLS handshake was completed: the server answered with the TLS alert “handshake_failure”.
Checked 2026-11-22 00:13 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)
act-node.com403 Forbidden (unencrypted)TLS handshake failed
www.act-node.com301 → https://www.act-node.com/ → 200 OK200 OK
  • act-node.com 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.act-node.com: visitors who use that name get an encrypted connection. View its report ›

DNS Records

As a public resolver answered for act-node.com. Looked up 2026-11-22 00:13 UTC · today

TypeRecords
A
AAAA
NS
ns-1307.awsdns-35.org ns-1919.awsdns-47.co.uk ns-257.awsdns-32.com ns-908.awsdns-49.net
MX
1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com 10 inbound-smtp.us-east-1.amazonaws.com
SPF None

TLS History & Relations

Everything our scans have seen for act-node.com, first seen 2026-11-22.

Addresses

AddressCertificateSeen
18.245.199.3 no TLS 2026-11-22
18.245.199.36 no TLS 2026-11-22
18.245.199.61 no TLS 2026-11-22
18.245.199.91 no TLS 2026-11-22

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-22 00:13No HTTPS— 18.245.199.3, 18.245.199.36, 18.245.199.61, 18.245.199.91

Other hosts seen on the same addresses