SSL Check WHOIS
Dashboard / Security Report

hellmanns.com.py

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

No HTTPS on hellmanns.com.py

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-10 15:27 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)
hellmanns.com.py301 → http://www.hellmanns.com.py/ → 403 ForbiddenTLS handshake failed
www.hellmanns.com.py403 Forbidden (unencrypted)403 Forbidden
  • http://hellmanns.com.py redirects to http://www.hellmanns.com.py/, which is not HTTPS either.
  • HTTPS works on www.hellmanns.com.py: visitors who use that name get an encrypted connection. View its report ›

DNS Records

As a public resolver answered for hellmanns.com.py. Looked up 2026-11-10 15:27 UTC · 6 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 None
SPF
v=spf1 mx a ptr include:servers.mcsv.net include:_spf.google.com include:amazonses.com include:amazonaws.com include:mail.dms.unileverservices.com -all

TLS History & Relations

Everything our scans have seen for hellmanns.com.py, first seen 2026-11-10.

Addresses

AddressCertificateSeen
20.238.208.21 no TLS 2026-11-10

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-10 15:27No HTTPS— 20.238.208.21

Other hosts seen on the same addresses