hostzen.us
Overall grade based on: IPv4: 1 of 1 complete · IPv6: 0 of 1 complete, 1 pending — IPv6 results are added below when their scan finishes; they do not count until then.
IPv6 scan in progress
2400:52e0:1e01::1056:1 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
The IPv4 report below is complete. IPv6 results will be added to this page automatically when the scan finishes.
Grade Breakdown
Protocol Support 50%
Key Exchange 90%
Cipher Strength 100%
Certificate 100%
Certificate does not match the domain name.
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.
| Host | http:// (port 80) | https:// (port 443) |
|---|---|---|
| hostzen.us | 301 → https://hostzen.net/ → 503 Service Unavailable | 301 → https://hostzen.net/ → 503 Service Unavailable · certificate does not cover this name |
| www.hostzen.us | Does not resolve | Does not resolve |
- http://hostzen.us redirects to HTTPS.
- https://hostzen.us forwards visitors to hostzen.net, a different site, which answers 503 Service Unavailable. View its report ›
- www.hostzen.us does not resolve: visitors who type it reach nothing.
DNS Records
As a public resolver answered for hostzen.us. Looked up 2026-11-07 17:41 UTC · today
| Type | Records |
|---|---|
| A | |
| AAAA | |
| NS | coco.bunny.net kiki.bunny.net |
| MX | None |
| SPF | None |
Certificate Identity
| Common Name | hostzen.us |
| Alt Names | *.b-cdn.net b-cdn.net |
| Issuer | CN=SSL.com TLS Issuing RSA CA R1, O=SSL Corporation, C=US |
| Validity | 2026-10-27 to 2027-05-13 (186 days remaining) |
| Key | RSA 2048 bits (sha256RSA) |
| Serial Number | 61A05491895F3B775A4079C9F532F12E |
| SHA256 Fingerprint | 633a9458626d8cf2dabcbd5080bf6dd543369941589d8faa5236c01e86752f85 |
| Pin SHA256 | U3UaUGvrn3P3KdmLkzn4EZRfhivXbq3G6Ha1uXFTqy0= |
Certificate Properties
| Type | DV |
| Cert Transparency | Yes (SCT) |
| OCSP Must Staple | No |
| Revocation | Good (not revoked) OCSP: http://ocsps.ssl.com CRL: http://crls.ssl.com/SSL.com-TLS-I-RSA-R1.crl |
| DNS CAA | No (missing) |
| Trusted By | Yes Mozilla · Apple · Android · Java · Windows |
| Name Match | No — certificate does not cover this host |
| Validity Period | 198 days (maximum 200 days for certificates issued then) |
| Policy Warnings | • Certificate does not cover hostzen.us (name mismatch): browsers will show an error. |
| Chain Issues | None |
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 | No |
| Supported Named Groups | X25519MLKEM768 x25519 secp256r1 secp384r1 (server preference order) |
| Post-Quantum Key Exchange | Yes X25519MLKEM768 |
| HTTP/3 (QUIC) | No |
| Encrypted Client Hello | No |
| Security Features | |
| Forward Secrecy | Yes (ECDHE / DHE) |
| Downgrade Prevention | Yes (TLS_FALLBACK_SCSV) |
| Secure Renegotiation | Supported (RFC 5746) |
| Extended Master Secret | Yes (RFC 7627) |
| OCSP Stapling | No |
| HSTS | Unknown (the HTTPS request to this IP failed) |
| 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 Compression | No (not supported by .NET TLS stack) |
| Heartbleed | Not tested |
Cipher Suite Analysis
| Cipher Suite | Hex | Key Exchange | FS | Bits | Strength |
|---|---|---|---|---|---|
| # TLS 1.3 (server-preferred order) | |||||
| TLS_AES_256_GCM_SHA384 | 0x1302 | ECDHE | FS | 256 | Secure |
| TLS_AES_128_GCM_SHA256 | 0x1301 | ECDHE | FS | 128 | Secure |
| TLS_CHACHA20_POLY1305_SHA256 | 0x1303 | ECDHE | FS | 256 | Secure |
| # TLS 1.2 (server-preferred order) | |||||
| TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | 0xC030 | ECDHE | FS | 256 | Secure |
| TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | 0xC02F | ECDHE | FS | 128 | Secure |
| TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 | 0xCCA8 | ECDHE | FS | 256 | Secure |
| TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 | 0xC028 | ECDHE | FS | 256 | Weak |
| TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA | 0xC014 | ECDHE | FS | 256 | Weak |
| TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 | 0xC027 | ECDHE | FS | 128 | Weak |
| TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA | 0xC013 | ECDHE | FS | 128 | Weak |
| TLS_RSA_WITH_AES_256_GCM_SHA384 | 0x009D | RSA | No FS | 256 | Weak |
| TLS_RSA_WITH_AES_256_CBC_SHA256 | 0x003D | RSA | No FS | 256 | Weak |
| TLS_RSA_WITH_AES_256_CBC_SHA | 0x0035 | RSA | No FS | 256 | Weak |
| TLS_RSA_WITH_AES_128_GCM_SHA256 | 0x009C | RSA | No FS | 128 | Weak |
| TLS_RSA_WITH_AES_128_CBC_SHA256 | 0x003C | RSA | No FS | 128 | Weak |
| TLS_RSA_WITH_AES_128_CBC_SHA | 0x002F | RSA | No FS | 128 | Weak |
Handshake Simulation
| Client | Protocol | Cipher Suite | Result |
|---|---|---|---|
| Chrome 120 / Win 11 | TLS 1.3 | TLS_AES_256_GCM_SHA384 | Success |
| Chrome 80 / Win 10 | TLS 1.3 | TLS_AES_256_GCM_SHA384 | Success |
| Firefox 115 / Win 10 | TLS 1.3 | TLS_AES_256_GCM_SHA384 | Success |
| iOS 17 / Safari | TLS 1.3 | TLS_CHACHA20_POLY1305_SHA256 | Success |
| macOS 14 / Safari | TLS 1.3 | TLS_AES_256_GCM_SHA384 | Success |
| Android 14 | TLS 1.3 | TLS_AES_128_GCM_SHA256 | Success |
| Chrome 69 / Win 7 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| Chrome 49 / XP SP3 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| IE 11 / Win 10 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| IE 11 / Win 7 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 9.0 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 7.0 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 5.0 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 4.4.2 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| Java 11 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| Java 8u121 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 4.0.4 | TLS 1.0 | TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA | Success |
| Android 4.1.1 | TLS 1.0 | TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA | Success |
| Baidu Jan 2015 | TLS 1.0 | TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA | Success |
| Java 6 | TLS 1.0 | TLS_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=*.b-cdn.net (Issuer: CN=SSL.com TLS Issuing RSA CA R1, O=SSL Corporation, C=US)
Intermediate CA
CN=SSL.com TLS Issuing RSA CA R1, O=SSL Corporation, C=US (Issuer: CN=SSL.com TLS RSA Root CA 2022, O=SSL Corporation, C=US)
Root Certificate
CN=SSL.com TLS RSA Root CA 2022, O=SSL Corporation, C=US (Issuer: CN=SSL.com TLS RSA Root CA 2022, O=SSL Corporation, C=US)
TLS History & Relations
Everything our scans have seen for hostzen.us, first seen 2026-11-07; current certificate since 2026-11-07.
Certificates served
| Certificate (SHA-256) | Issuer | Valid | Served |
|---|---|---|---|
| 633a9458626d8cf2… current | SSL.com TLS Issuing RSA CA R1 | 2026-10-27 → 2027-05-13 | 2026-11-07 |
Addresses
| Address | Certificate | Seen |
|---|---|---|
| 84.17.46.49 | 633a9458626d8cf2… | 2026-11-07 |
TLS history (a row per change; repeated checks only extend it)
| Since → last checked (UTC) | Grade | TLS | Certificates | Addresses |
|---|---|---|---|---|
| 2026-11-07 17:41 | T | TLS 1.3 | 633a9458626d8cf2… | 84.17.46.49 |
Other domains on the same certificate
- b-cdn.net 2 names *.b-cdn.net