SSL Check WHOIS
inklume.xyz has no HTTPS: HTTPS could not be reached on its IPv4 address. The site is served on www.inklume.xyz; this is its report. (inklume.xyz checked 2026-09-16 20:08 UTC)
Dashboard / Security Report

www.inklume.xyz

Add this badge to your site

Shows this report's grade and links back to it. It is read from the stored report, never a new scan; a report older than 30 days also shows the month it was checked.

www.inklume.xyz: SSL/TLS grade B (HTTPS Monitor)www.inklume.xyzB
Overall grade based on: IPv4: 2 of 2 complete · IPv6: 2 of 2 complete
All 4 endpoints share identical configuration Select an IP for owner, ASN & location
B 104.21.36.152 IPv4 WHOIS › B 172.67.196.116 IPv4 WHOIS › B 2606:4700:3034::6815:2498 IPv6 WHOIS › B 2606:4700:3037::ac43:c474 IPv6 WHOIS ›

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).

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 X25519MLKEM768 X25519Kyber768Draft00 x25519 secp256r1 secp384r1 secp521r1 (server preference order)
Post-Quantum Key Exchange Yes X25519MLKEM768, X25519Kyber768Draft00
HTTP/3 (QUIC) Yes (advertised)
Encrypted Client Hello Yes(ECH config in HTTPS DNS record)
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 (certificate has no OCSP responder)
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
TLS_AES_128_GCM_SHA2560x1301ECDHEFS128Secure
TLS_AES_256_GCM_SHA3840x1302ECDHEFS256Secure
TLS_CHACHA20_POLY1305_SHA2560x1303ECDHEFS256Secure
# TLS 1.2
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA2560xC02BECDHEFS128Secure
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA2560xCCA9ECDHEFS256Secure
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA0xC009ECDHEFS128Weak
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA3840xC02CECDHEFS256Secure
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA0xC00AECDHEFS256Weak
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA2560xC023ECDHEFS128Weak
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA3840xC024ECDHEFS256Weak

Handshake Simulation

ClientProtocolCipher SuiteResult
Chrome 120 / Win 11TLS 1.3TLS_AES_256_GCM_SHA384Success
Chrome 80 / Win 10TLS 1.3TLS_AES_256_GCM_SHA384Success
Firefox 115 / Win 10TLS 1.3TLS_AES_256_GCM_SHA384Success
iOS 17 / SafariTLS 1.3TLS_CHACHA20_POLY1305_SHA256Success
macOS 14 / SafariTLS 1.3TLS_AES_256_GCM_SHA384Success
Android 14TLS 1.3TLS_AES_128_GCM_SHA256Success
Chrome 69 / Win 7TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Chrome 49 / XP SP3TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
IE 11 / Win 10TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
IE 11 / Win 7TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Android 9.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Android 7.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Android 5.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Android 4.4.2TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Java 11TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Java 8u121TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Android 4.0.4TLS 1.0TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHASuccess
Android 4.1.1TLS 1.0TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHASuccess
Baidu Jan 2015TLS 1.0TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHASuccess
Java 6TLS 1.0TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHASuccess

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

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)
www.inklume.xyz301 → https://www.inklume.xyz/ → … → https://inklume.xyz/ → 200 OK301 → https://inklume.xyz/ → 200 OK
inklume.xyz301 → https://inklume.xyz/ → 200 OK200 OK
  • http://www.inklume.xyz redirects to HTTPS.

DNS Records

As a public resolver answered for www.inklume.xyz and its domain inklume.xyz. Looked up 2026-11-18 18:11 UTC · 1 day ago

TypeRecords
www.inklume.xyz
A
AAAA
MX None
SPF None
inklume.xyz
A
AAAA
NS
amir.ns.cloudflare.com robin.ns.cloudflare.com
MX None
SPF None

Certificate Identity

Common Namewww.inklume.xyz
Alt Names *.inklume.xyz inklume.xyz
IssuerCN=YE1, O=Let's Encrypt, C=US
Validity 2026-10-14 to 2027-01-12 (53 days remaining)
KeyECDSA 256 bits (sha384ECDSA)
Serial Number064F7EBA837CF1BCA522CF62E7D1B60A2FFD
SHA256 Fingerprint 6447c79986756d61a914b89acc3fd0dc207aa14e43a6df6c279dba154376324d
Pin SHA256YNGdHC+EB8vps/yF/JtaCBalpQzK8cfXOw9G2J9r3Xw=

Certificate Properties

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

Trust Chain Architecture

End-Entity Certificate
CN=inklume.xyz (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 www.inklume.xyz, first seen 2026-11-18; current certificate since 2026-11-18.

Certificates served

Certificate (SHA-256)IssuerValidServed
6447c79986756d61… current YE12026-10-14 → 2027-01-122026-11-18

Addresses

AddressCertificateSeen
104.21.36.152 6447c79986756d61… 2026-11-18
172.67.196.116 6447c79986756d61… 2026-11-18
2606:4700:3034::6815:2498 6447c79986756d61… 2026-11-18
2606:4700:3037::ac43:c474 6447c79986756d61… 2026-11-18

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-18 18:11BTLS 1.3 6447c79986756d61… 104.21.36.152, 172.67.196.116

Other hosts seen on the same addresses