SSL Check WHOIS
Dashboard / Security Report

rdap.joker.com

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
2a01:4fc0:0:1000::2100:1111 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.

A+

Exceptional Security

Overall Rating
194.245.148.104 · WHOIS ›
Assessed 2026-10-18 13:09 UTC

Grade Breakdown

Protocol Support 95%
Key Exchange 90%
Cipher Strength 100%
Certificate 100%

Certificate Identity

Common Namerdap.joker.com
Alt Names rdap.joker.com
IssuerCN=YE1, O=Let's Encrypt, C=US
Validity 2026-09-14 to 2026-12-13 (24 days remaining)
KeyECDSA 256 bits (sha384ECDSA)
Serial Number0579F302F12D5F40823E3C797C6EE59DC515
SHA256 Fingerprint 4ba2c95920962cc1f71e58d120d18ed1a83df157614bc9d23598fd559732b95c
Pin SHA256k525dknm3B2Gk3HZSHF67kk8XuQhqTTNYQAurhDAoi8=

Certificate Properties

Type DV
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) CRL: http://ye1.c.lencr.org/22.crl No OCSP responder — revocation is published via CRL only (as CA/B Forum rules now allow).
DNS CAA Yes (configured) 0 issue "geotrust.com" 0 issue "letsencrypt.org" 0 issue "comodoca.com"
Trusted By Yes Mozilla · Apple · Android · Java · Windows
Name Match Yes
Validity Period 90 days (maximum 200 days for certificates issued then)
Chain IssuesNone

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 No
SNI Required No
Supported Named Groups secp256r1 (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 (legacy TLS disabled)
Secure Renegotiation Supported (RFC 5746)
Extended Master Secret Yes (RFC 7627)
OCSP Stapling No (certificate has no OCSP responder)
HSTS Yes 180 days
HSTS Preloading Not preloadedSubmit →
Security Checks
BEAST attack Mitigated
POODLE (SSLv3) No (SSL 3 not supported)
POODLE (TLS) No
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_ECDSA_WITH_AES_128_GCM_SHA2560xC02BECDHEFS128Secure
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA3840xC02CECDHEFS256Secure
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA2560xCCA9ECDHEFS256Secure
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA3840xC024ECDHEFS256Weak
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA2560xC023ECDHEFS128Weak
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA0xC00AECDHEFS256Weak
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA0xC009ECDHEFS128Weak

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_ECDSA_WITH_AES_128_GCM_SHA256 Success
Chrome 49 / XP SP3TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Success
IE 11 / Win 10TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Success
IE 11 / Win 7TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Success
Android 9.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Success
Android 7.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Success
Android 5.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Success
Android 4.4.2TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Success
Java 11TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Success
Java 8u121TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Success
Android 4.0.4-- No
Android 4.1.1-- No
Baidu Jan 2015-- No
Java 6-- No

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

Trust Chain Architecture

End-Entity Certificate
CN=rdap.joker.com (Issuer: CN=YE1, O=Let's Encrypt, C=US)
Intermediate CA
CN=YE1, O=Let's Encrypt, C=US (Issuer: CN=Root YE, O=ISRG, C=US)
Intermediate CA
CN=Root YE, O=ISRG, C=US (Issuer: CN=ISRG Root X2, O=Internet Security Research Group, C=US)
Root Certificate
CN=ISRG Root X2, O=Internet Security Research Group, C=US (Issuer: CN=ISRG Root X2, O=Internet Security Research Group, C=US)

TLS History & Relations

Everything our scans have seen for rdap.joker.com, first seen 2026-10-18; current certificate since 2026-10-18.

Certificates served

Certificate (SHA-256)IssuerValidServed
4ba2c95920962cc1… current YE12026-09-14 → 2026-12-132026-10-18

Addresses

AddressCertificateSeen
194.245.148.104 4ba2c95920962cc1… 2026-10-18

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-10-18 13:09A+TLS 1.3 4ba2c95920962cc1… 194.245.148.104