SSL Check WHOIS
Dashboard / Security Report

zalamo.com

IPv6: no public AAAA record — the domain is reachable over IPv4 only.
B

Adequate Protection

Overall Rating
185.170.104.35 · WHOIS ›
Assessed 2026-11-19 10:17 UTC

Grade Breakdown

Protocol Support 50%
Key Exchange 90%
Cipher Strength 100%
Certificate 100%
Grade capped at B: server supports obsolete TLS 1.0/1.1.

Security Vulnerabilities Detected

  • •Obsolete TLS versions (1.0/1.1) supported.
  • •CBC cipher suites with TLS 1.0/1.1 (BEAST, Lucky13).

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)
zalamo.com301 → https://zalamo.com/ → … → https://zalamo.com/newborn/ → 200 OK302 → https://zalamo.com/home → … → https://zalamo.com/newborn/ → 200 OK
www.zalamo.com301 → https://www.zalamo.com/ → … → http://zalamo.com/newborn/ → Too many redirects301 → https://zalamo.com/ → … → https://zalamo.com/newborn/ → 200 OK
  • http://zalamo.com redirects to HTTPS.

DNS Records

As a public resolver answered for zalamo.com. Looked up 2026-11-19 10:17 UTC · today

TypeRecords
A
AAAA None
NS
george.ns.cloudflare.com maya.ns.cloudflare.com
MX
1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com
SPF
v=spf1 include:_spf.google.com -all

Certificate Identity

Common Namezalamo.com
Alt Names *.zalamo.com zalamo.com
IssuerCN=Sectigo Public Server Authentication CA DV R36, O=Sectigo Limited, C=GB
Validity 2025-12-15 to 2027-01-14 (56 days remaining)
KeyRSA 2048 bits (sha256RSA)
Serial Number75CD43154056679AC45FBA87A93548AE
SHA256 Fingerprint 63474f1a452008345acfb7fbe2b3d5e7643e16fc8adeac216205567fb2dfed74
Pin SHA256y1aUQBqgVmP41eelrNje7AbNcMEETVvHNb42c7vvq+8=

Certificate Properties

Type DV Domain Validated
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Unknown (OCSP-only certificate; not queried) OCSP: http://ocsp.sectigo.com
DNS CAA No (missing)
Trusted By Yes Mozilla · Apple · Android · Java · Windows
Name Match Yes
Validity Period 396 days (maximum 398 days for certificates issued then)
Chain Issues
• Contains anchor (root CA included in chain)

Protocol Configuration

Supported Protocols

TLS 1.3
TLS 1.2
TLS 1.1
TLS 1.0
SSL 3
SSL 2

Negotiated Cipher

TLS_AES_256_GCM_SHA384

Protocol Details

Connection
ALPN h2 http/1.1
SNI Required Yes
Supported Named Groups x25519 secp256r1 x448 secp521r1 secp384r1 (server preference order)
Post-Quantum Key Exchange No (no hybrid ML-KEM group such as X25519MLKEM768)
HTTP/3 (QUIC) No
Encrypted Client Hello No
Security Features
Forward SecrecyYes (ECDHE / DHE)
Downgrade Prevention Yes (TLS_FALLBACK_SCSV)
Secure Renegotiation Supported (RFC 5746)
Extended Master Secret Yes (RFC 7627)
OCSP Stapling No
HSTS No
HSTS Preloading N/A (HSTS not enabled)
Security Checks
BEAST attack Not mitigated server-side (TLS 1.0 + CBC)
POODLE (SSLv3) No (SSL 3 not supported)
POODLE (TLS) Possible (CBC + legacy TLS present)
RC4 No
SSL/TLS CompressionNo (not supported by .NET TLS stack)
HeartbleedNot tested

Cipher Suite Analysis

Cipher SuiteHexKey ExchangeFSBitsStrength
# TLS 1.3 (server-preferred order)
TLS_AES_256_GCM_SHA3840x1302ECDHEFS256Secure
TLS_CHACHA20_POLY1305_SHA2560x1303ECDHEFS256Secure
TLS_AES_128_GCM_SHA2560x1301ECDHEFS128Secure
# TLS 1.2 (server-preferred order)
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3840xC030ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA2560xC02FECDHEFS128Secure
TLS_DHE_RSA_WITH_AES_256_GCM_SHA3840x009FDHEFS256Secure
TLS_DHE_RSA_WITH_AES_128_GCM_SHA2560x009EDHEFS128Secure
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA3840xC028ECDHEFS256Weak
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA0xC014ECDHEFS256Weak
TLS_DHE_RSA_WITH_AES_256_CBC_SHA2560x006BDHEFS256Weak
TLS_DHE_RSA_WITH_AES_256_CBC_SHA0x0039DHEFS256Weak
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA2560xC027ECDHEFS128Weak
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA0xC013ECDHEFS128Weak
TLS_DHE_RSA_WITH_AES_128_CBC_SHA2560x0067DHEFS128Weak
TLS_DHE_RSA_WITH_AES_128_CBC_SHA0x0033DHEFS128Weak
TLS_RSA_WITH_AES_256_GCM_SHA3840x009DRSANo FS256Weak
TLS_RSA_WITH_AES_128_GCM_SHA2560x009CRSANo FS128Weak
TLS_RSA_WITH_AES_256_CBC_SHA2560x003DRSANo FS256Weak
TLS_RSA_WITH_AES_128_CBC_SHA2560x003CRSANo FS128Weak
TLS_RSA_WITH_AES_256_CBC_SHA0x0035RSANo FS256Weak
TLS_RSA_WITH_AES_128_CBC_SHA0x002FRSANo FS128Weak

Handshake Simulation

ClientProtocolCipher SuiteResult
Chrome 120 / Win 11TLS 1.3TLS_AES_256_GCM_SHA384 Success
Chrome 80 / Win 10TLS 1.3TLS_AES_256_GCM_SHA384 Success
Firefox 115 / Win 10TLS 1.3TLS_AES_256_GCM_SHA384 Success
iOS 17 / SafariTLS 1.3TLS_CHACHA20_POLY1305_SHA256 Success
macOS 14 / SafariTLS 1.3TLS_AES_256_GCM_SHA384 Success
Android 14TLS 1.3TLS_AES_128_GCM_SHA256 Success
Chrome 69 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Chrome 49 / XP SP3TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
IE 11 / Win 10TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
IE 11 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Android 9.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Android 7.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Android 5.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Android 4.4.2TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Java 11TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Java 8u121TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Android 4.0.4TLS 1.0TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA Success
Android 4.1.1TLS 1.0TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA Success
Baidu Jan 2015TLS 1.0TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA Success
Java 6TLS 1.0TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA Success

* Simulated based on server's supported protocols and cipher configuration.

Trust Chain Architecture

End-Entity Certificate
CN=*.zalamo.com (Issuer: CN=Sectigo Public Server Authentication CA DV R36, O=Sectigo Limited, C=GB)
Intermediate CA
CN=Sectigo Public Server Authentication CA DV R36, O=Sectigo Limited, C=GB (Issuer: CN=Sectigo Public Server Authentication Root R46, O=Sectigo Limited, C=GB)
Root Certificate
CN=Sectigo Public Server Authentication Root R46, O=Sectigo Limited, C=GB (Issuer: CN=Sectigo Public Server Authentication Root R46, O=Sectigo Limited, C=GB)

TLS History & Relations

Everything our scans have seen for zalamo.com, first seen 2026-11-19; current certificate since 2026-11-19.

Certificates served

Certificate (SHA-256)IssuerValidServed
63474f1a45200834… current Sectigo Public Server Authentication CA DV R362025-12-15 → 2027-01-142026-11-19

Addresses

AddressCertificateSeen
185.170.104.35 63474f1a45200834… 2026-11-19

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-19 10:17BTLS 1.3 63474f1a45200834… 185.170.104.35