SSL Check WHOIS
Dashboard / Security Report

axe.cl

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

No HTTPS on axe.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-07 01:51 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)
axe.cl301 → http://www.axe.cl/ → … → https://www.axe.com/cl// → 403 ForbiddenTLS handshake failed
www.axe.cl301 → https://www.axe.com/cl// → 403 Forbidden301 → https://www.axe.com/cl// → 403 Forbidden
  • http://axe.cl redirects to HTTPS.
  • HTTPS works on www.axe.cl: visitors who use that name get an encrypted connection. View its report ›

DNS Records

As a public resolver answered for axe.cl. Looked up 2026-11-07 01:51 UTC · 10 days ago

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:_spf.embluemail.com include:amazonses.com -all

TLS History & Relations

Everything our scans have seen for axe.cl, first seen 2026-11-07.

Addresses

AddressCertificateSeen
20.238.208.21 no TLS 2026-11-07

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-07 01:51No HTTPS— 20.238.208.21

Other hosts seen on the same addresses