SSL Check WHOIS
Dashboard / Security Report

4patientcare.info

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.

4patientcare.info: SSL/TLS scan incomplete (HTTPS Monitor)4patientcare.info?
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 4patientcare.info

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-11-19 02:26 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)
4patientcare.info404 Not Found (unencrypted)TLS handshake failed
www.4patientcare.info404 Not Found (unencrypted)TLS handshake failed
  • 4patientcare.info is served over plain HTTP only: everything visitors send and receive is unencrypted and can be read or changed on the way.
  • www.4patientcare.info has no working HTTPS either (TLS handshake failed).

DNS Records

As a public resolver answered for 4patientcare.info. Looked up 2026-11-19 02:26 UTC · 3 days ago

TypeRecords
A
AAAA
NS
ns13.domaincontrol.com ns14.domaincontrol.com
MX
0 4patientcare-info.mail.protection.outlook.com 10 mxa.mailgun.org 10 mxb.mailgun.org
SPF
v=spf1 include:secureserver.net include:spf.protection.outlook.com include:mailgun.org ~all

Certificates & Relations

The current state of 4patientcare.info as of our latest scan.

Addresses

AddressAS
216.239.32.21 —
216.239.34.21 —
216.239.36.21 —
216.239.38.21 —

Other hosts on the same addresses