instacount.cloud
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.
The IPv4 report below is complete. IPv6 results will be added to this page automatically when the scan finishes.
No HTTPS over IPv4 on instacount.cloud
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.
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.
| Host | http:// (port 80) | https:// (port 443) |
|---|---|---|
| instacount.cloud | 200 OK (unencrypted) | TLS handshake failed |
| www.instacount.cloud | 200 OK (unencrypted) | TLS handshake failed |
- instacount.cloud is served over plain HTTP only: everything visitors send and receive is unencrypted and can be read or changed on the way.
- www.instacount.cloud has no working HTTPS either (TLS handshake failed).
DNS Records
As a public resolver answered for instacount.cloud. Looked up 2026-11-10 00:53 UTC · 10 days ago
| Type | Records |
|---|---|
| A | |
| AAAA | |
| NS | docks14.rzone.de shades01.rzone.de |
| MX | 5 smtpin.rzone.de |
| SPF | None |
TLS History & Relations
Everything our scans have seen for instacount.cloud, first seen 2026-11-10.
Addresses
| Address | Certificate | Seen |
|---|---|---|
| 217.160.0.12 | no TLS | 2026-11-10 |
TLS history (a row per change; repeated checks only extend it)
| Since → last checked (UTC) | Grade | TLS | Certificates | Addresses |
|---|---|---|---|---|
| 2026-11-10 00:53 | No HTTPS | — | 217.160.0.12 |