SSL Report:
repo.sparkylinux.org
(184.174.34.74)
Assessed on: Fri, 28 Mar 2025 06:26:28 UTC
| Clear cache
Summary
0
20
40
60
80
100
Certificate
Protocol Support
Key Exchange
Cipher Strength
Visit our documentation page
for more information, configuration guides, and books. Known issues are documented
here.
This site works only in browsers with SNI support.
This server supports TLS 1.3.
Certificate #1: EC 256 bits (SHA384withECDSA)

Server Key and Certificate #1
|
|
Subject |
repo.sparkylinux.org
Fingerprint SHA256: 840986dbbd399016d31243296597599b4649000c64c59ad2f0addea63c4c3e3a Pin SHA256: 48Yzlvag928jDsaFNaQP+ETB9O2mBIH0c83utPk0tgI= |
Common names | repo.sparkylinux.org |
Alternative names | repo.sparkylinux.org |
Serial Number | 069972f4ddad4b4f43eab7064d0f02f76af1 |
Valid from | Wed, 19 Mar 2025 22:43:49 UTC |
Valid until | Tue, 17 Jun 2025 22:43:48 UTC (expires in 2 months and 19 days) |
Key | EC 256 bits |
Weak key (Debian) | No |
Issuer | E6
AIA: http://e6.i.lencr.org/ |
Signature algorithm | SHA384withECDSA |
Extended Validation | No |
Certificate Transparency | Yes (certificate) |
OCSP Must Staple | No |
Revocation information |
CRL, OCSP CRL: http://e6.c.lencr.org/114.crl OCSP: http://e6.o.lencr.org |
Revocation status | Good (not revoked) |
DNS CAA | No (more info) |
Trusted | Yes
Mozilla Apple Android Java Windows |


![]() |
Certificate #2: EC 256 bits (SHA384withECDSA)
No SNI

Configuration

Protocols | |
TLS 1.3 | Yes |
TLS 1.2 | Yes* |
TLS 1.1 | No |
TLS 1.0 | No |
SSL 3 | No |
SSL 2 | No |
(*) Experimental: Server negotiated using No-SNI |

Cipher Suites | ||
![]() ![]() # TLS 1.3 (server has no preference)
|
||
TLS_AES_128_GCM_SHA256 (0x1301 )
ECDH x25519 (eq. 3072 bits RSA) FS
|
128 | |
TLS_AES_256_GCM_SHA384 (0x1302 )
ECDH x25519 (eq. 3072 bits RSA) FS
|
256 | |
TLS_CHACHA20_POLY1305_SHA256 (0x1303 )
ECDH x25519 (eq. 3072 bits RSA) FS
|
256 | |
![]() ![]() # TLS 1.2 (server has no preference)
|
||
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (0xc02b )
ECDH secp521r1 (eq. 15360 bits RSA) FS
|
128 | |
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (0xc02c )
ECDH secp521r1 (eq. 15360 bits RSA) FS
|
256 | |
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 (0xcca9 )
ECDH secp521r1 (eq. 15360 bits RSA) FS
|
256 |

Handshake Simulation | |||
Android 4.4.2 | EC 256 (SHA384) | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 ECDH secp521r1 FS |
Android 5.0.0 | EC 256 (SHA384) | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH secp521r1 FS |
Android 6.0 | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH secp256r1 FS |
Android 7.0 | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 ECDH x25519 FS |
Android 8.0 | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 ECDH x25519 FS |
Android 8.1 | - | TLS 1.3 | TLS_CHACHA20_POLY1305_SHA256 ECDH x25519 FS |
Android 9.0 | - | TLS 1.3 | TLS_CHACHA20_POLY1305_SHA256 ECDH x25519 FS |
BingPreview Jan 2015 | EC 256 (SHA384) | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 ECDH secp521r1 FS |
Chrome 49 / XP SP3 |
Server sent fatal alert: handshake_failure |
||
Chrome 69 / Win 7 R | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH x25519 FS |
Chrome 70 / Win 10 | - | TLS 1.3 | TLS_AES_128_GCM_SHA256 ECDH x25519 FS |
Chrome 80 / Win 10 R | - | TLS 1.3 | TLS_AES_128_GCM_SHA256 ECDH x25519 FS |
Firefox 31.3.0 ESR / Win 7 | EC 256 (SHA384) | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH secp256r1 FS |
Firefox 47 / Win 7 R | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH secp256r1 FS |
Firefox 49 / XP SP3 | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH secp256r1 FS |
Firefox 62 / Win 7 R | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH x25519 FS |
Firefox 73 / Win 10 R | - | TLS 1.3 | TLS_AES_128_GCM_SHA256 ECDH x25519 FS |
Googlebot Feb 2018 | EC 256 (SHA384) | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH x25519 FS |
IE 11 / Win 7 R | EC 256 (SHA384) | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS |
IE 11 / Win 8.1 R | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS |
IE 11 / Win Phone 8.1 R | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH secp256r1 FS |
IE 11 / Win Phone 8.1 Update R | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS |
IE 11 / Win 10 R | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS |
Edge 15 / Win 10 R | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 ECDH x25519 FS |
Edge 16 / Win 10 R | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 ECDH x25519 FS |
Edge 18 / Win 10 R | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 ECDH x25519 FS |
Edge 13 / Win Phone 10 R | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS |
Java 8u161 | EC 256 (SHA384) | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS |
Java 11.0.3 | - | TLS 1.3 | TLS_AES_128_GCM_SHA256 ECDH secp256r1 FS |
Java 12.0.1 | - | TLS 1.3 | TLS_AES_128_GCM_SHA256 ECDH secp256r1 FS |
OpenSSL 1.0.1l R | EC 256 (SHA384) | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 ECDH secp521r1 FS |
OpenSSL 1.0.2s R | EC 256 (SHA384) | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS |
OpenSSL 1.1.0k R | EC 256 (SHA384) | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 ECDH x25519 FS |
OpenSSL 1.1.1c R | - | TLS 1.3 | TLS_AES_256_GCM_SHA384 ECDH x25519 FS |
Safari 6 / iOS 6.0.1 |
Server sent fatal alert: handshake_failure |
||
Safari 7 / iOS 7.1 R |
Server sent fatal alert: handshake_failure |
||
Safari 7 / OS X 10.9 R |
Server sent fatal alert: handshake_failure |
||
Safari 8 / iOS 8.4 R |
Server sent fatal alert: handshake_failure |
||
Safari 8 / OS X 10.10 R |
Server sent fatal alert: handshake_failure |
||
Safari 9 / iOS 9 R | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS |
Safari 9 / OS X 10.11 R | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS |
Safari 10 / iOS 10 R | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS |
Safari 10 / OS X 10.12 R | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS |
Safari 12.1.2 / MacOS 10.14.6 Beta R | - | TLS 1.3 | TLS_CHACHA20_POLY1305_SHA256 ECDH x25519 FS |
Safari 12.1.1 / iOS 12.3.1 R | - | TLS 1.3 | TLS_CHACHA20_POLY1305_SHA256 ECDH x25519 FS |
Apple ATS 9 / iOS 9 R | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS |
Yahoo Slurp Jan 2015 | EC 256 (SHA384) | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 ECDH secp384r1 FS |
YandexBot Jan 2015 | EC 256 (SHA384) | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 ECDH secp521r1 FS |
![]() # Not simulated clients (Protocol mismatch)
|
|||
Android 2.3.7 No SNI 2 |
Protocol mismatch (not simulated) |
||
Android 4.0.4 |
Protocol mismatch (not simulated) |
||
Android 4.1.1 |
Protocol mismatch (not simulated) |
||
Android 4.2.2 |
Protocol mismatch (not simulated) |
||
Android 4.3 |
Protocol mismatch (not simulated) |
||
Baidu Jan 2015 |
Protocol mismatch (not simulated) |
||
IE 6 / XP No FS 1 No SNI 2 |
Protocol mismatch (not simulated) |
||
IE 7 / Vista |
Protocol mismatch (not simulated) |
||
IE 8 / XP No FS 1 No SNI 2 |
Protocol mismatch (not simulated) |
||
IE 8-10 / Win 7 R |
Protocol mismatch (not simulated) |
||
IE 10 / Win Phone 8.0 |
Protocol mismatch (not simulated) |
||
Java 6u45 No SNI 2 |
Protocol mismatch (not simulated) |
||
Java 7u25 |
Protocol mismatch (not simulated) |
||
OpenSSL 0.9.8y |
Protocol mismatch (not simulated) |
||
Safari 5.1.9 / OS X 10.6.8 |
Protocol mismatch (not simulated) |
||
Safari 6.0.4 / OS X 10.8.4 R |
Protocol mismatch (not simulated) |
||
(1) Clients that do not support Forward Secrecy (FS) are excluded when determining support for it. | |||
(2) No support for virtual SSL hosting (SNI). Connects to the default site if the server uses SNI. | |||
(3) Only first connection attempt simulated. Browsers sometimes retry with a lower protocol version. | |||
(R) Denotes a reference browser or client, with which we expect better effective security. | |||
(All) We use defaults, but some platforms do not use their best protocols and features (e.g., Java 6 & 7, older IE). | |||
(All) Certificate trust is not checked in handshake simulation, we only perform TLS handshake. |

Protocol Details | |
Secure Renegotiation | Supported |
Secure Client-Initiated Renegotiation | No |
Insecure Client-Initiated Renegotiation | No |
BEAST attack | Mitigated server-side (more info) |
POODLE (SSLv3) | No, SSL 3 not supported (more info) |
POODLE (TLS) | No (more info) |
Zombie POODLE | No (more info) |
GOLDENDOODLE | No (more info) |
OpenSSL 0-Length | No (more info) |
Sleeping POODLE | No (more info) |
Downgrade attack prevention | Yes, TLS_FALLBACK_SCSV supported (more info) |
SSL/TLS compression | No |
RC4 | No |
Heartbeat (extension) | No |
Heartbleed (vulnerability) | No (more info) |
Ticketbleed (vulnerability) | No (more info) |
OpenSSL CCS vuln. (CVE-2014-0224) | No (more info) |
OpenSSL Padding Oracle vuln. (CVE-2016-2107) |
No (more info) |
ROBOT (vulnerability) | No (more info) |
Forward Secrecy | Yes (with most browsers) ROBUST (more info) |
ALPN | Yes http/1.1 |
NPN | No |
Session resumption (caching) | Yes |
Session resumption (tickets) | No |
OCSP stapling | No |
Strict Transport Security (HSTS) | No |
HSTS Preloading | Not in: Chrome Edge Firefox IE |
Public Key Pinning (HPKP) | No (more info) |
Public Key Pinning Report-Only | No |
Public Key Pinning (Static) | No (more info) |
Long handshake intolerance | No |
TLS extension intolerance | No |
TLS version intolerance | No |
Incorrect SNI alerts | No |
Uses common DH primes | No, DHE suites not supported |
DH public server param (Ys) reuse | No, DHE suites not supported |
ECDH public server param reuse | No |
Supported Named Groups | secp256r1 |
SSL 2 handshake compatibility | No |
0-RTT enabled | No |

![]() |
1 https://repo.sparkylinux.org/
(HTTP/1.1 200 OK)
| ||
1 | ||
Date | Fri, 28 Mar 2025 06:25:09 GMT | |
Server | Apache/2.4.62 (Debian) | |
Last-Modified | Thu, 27 Mar 2025 23:41:57 GMT | |
ETag | "7de1-6315b7fdbb1da" | |
Accept-Ranges | bytes | |
Content-Length | 32225 | |
Vary | Accept-Encoding | |
Connection | close | |
Content-Type | text/html |

Miscellaneous | |
Test date | Fri, 28 Mar 2025 06:24:54 UTC |
Test duration | 93.527 seconds |
HTTP status code | 200 |
HTTP server signature | Apache/2.4.62 (Debian) |
Server hostname | vmi2141266.contaboserver.net |
SSL Report v2.3.1