SSL Check WHOIS
Dashboard / Security Report

blipps.io

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

No HTTPS on blipps.io

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

75.2.70.75 IPv4 · Port 443 accepted the connection, but no TLS handshake was completed: the server answered with the TLS alert “internal_error”.
99.83.190.102 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 01:02 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)
blipps.io301 → https://blipps.io/ → TLS handshake failedTLS handshake failed
www.blipps.io301 → https://www.blipps.io/ → TLS handshake failedTLS handshake failed
  • http://blipps.io redirects to HTTPS.
  • www.blipps.io has no working HTTPS either (TLS handshake failed).

DNS Records

As a public resolver answered for blipps.io. Looked up 2026-11-18 01:02 UTC · today

TypeRecords
A
AAAA None
NS
bingo.ns.cloudflare.com rocco.ns.cloudflare.com
MX
10 mx.zoho.com 20 mx2.zoho.com 30 mx3.zoho.com
SPF
v=spf1 include:zoho.com ~all

TLS History & Relations

Everything our scans have seen for blipps.io, first seen 2026-11-18.

Addresses

AddressCertificateSeen
75.2.70.75 no TLS 2026-11-18
99.83.190.102 no TLS 2026-11-18

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-18 01:02No HTTPS— 75.2.70.75, 99.83.190.102

Other hosts seen on the same addresses