SSL Check WHOIS
Dashboard / Security Report

omo.cl

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

No HTTPS on omo.cl

Port 443 accepts connections on its IPv4 address, but no TLS handshake is completed: there is no working HTTPS.

20.238.208.21 IPv4 · Port 443 accepted the connection, but no TLS handshake was completed: the server answered with the TLS alert “unrecognized_name”.
Checked 2026-11-16 22:49 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)
omo.cl301 → http://www.omo.cl/ → 503 Service UnavailableTLS handshake failed
www.omo.cl503 Service Unavailable (unencrypted)503 Service Unavailable
  • http://omo.cl redirects to http://www.omo.cl/, which is not HTTPS either.
  • HTTPS works on www.omo.cl: visitors who use that name get an encrypted connection. View its report ›

DNS Records

As a public resolver answered for omo.cl. Looked up 2026-11-16 22:49 UTC · today

TypeRecords
A
AAAA None
NS
ns1-44.azure-dns.com ns2-44.azure-dns.net ns3-44.azure-dns.org ns4-44.azure-dns.info
MX
10 inbound-smtp.us-east-1.amazonaws.com
SPF
v=spf1 include:sendgrid.net include:mail.dms.unileverservices.com ~all v=spf1 include:amazonses.com ~all
More than one SPF policy: receivers treat this as an error and SPF fails (RFC 7208).

TLS History & Relations

Everything our scans have seen for omo.cl, first seen 2026-11-16.

Addresses

AddressCertificateSeen
20.238.208.21 no TLS 2026-11-16

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-16 22:49No HTTPS— 20.238.208.21

Other hosts seen on the same addresses