SSL Check WHOIS
Dashboard / Security Report

finasteride.digital

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.

finasteride.digital: SSL/TLS grade B (HTTPS Monitor)finasteride.digitalB
Overall grade based on: IPv4: 4 of 5 complete, 1 unreachable · IPv6: 3 of 4 complete, 1 unreachable
1 different configuration detected across 9 endpoints Select an IP for owner, ASN & location
— 2 unreachable
B 139.162.174.209 IPv4 WHOIS › B 139.162.181.76 IPv4 WHOIS › B 172.104.203.186 IPv4 WHOIS › B 172.104.251.198 IPv4 WHOIS › B 2a01:7e01::2000:dff:fec1:5cdb IPv6 WHOIS › B 2a01:7e01::f03c:95ff:fe91:5d91 IPv6 WHOIS › B 2a01:7e01::f03c:95ff:feeb:9d4b IPv6 WHOIS ›
⚡
172.104.149.86 WHOIS › IPv4 — Port 443 accepted the connection, but no TLS handshake was completed: the server answered with the TLS alert “internal_error”.
⚡
2a01:7e01::f03c:95ff:fe00:2692 WHOIS › IPv6 — Port 443 accepted the connection, but no TLS handshake was completed: the server answered with the TLS alert “internal_error”.

Grade Breakdown

Protocol Support 95%
Key Exchange 90%
Cipher Strength 100%
Certificate 100%
Grade capped at B: server accepts 3DES cipher suites (Sweet32).

Security Vulnerabilities Detected

  • •Weak 3DES cipher supported (Sweet32).

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 x25519 secp256r1 secp384r1 secp521r1 x448 ffdhe2048 ffdhe3072 (server preference order)
Post-Quantum Key Exchange Yes X25519MLKEM768
HTTP/3 (QUIC) Yes (advertised)
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 Disabled (max-age=0)
HSTS Preloading N/A (HSTS not enabled)
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
TLS_AES_128_GCM_SHA2560x1301ECDHEFS128Secure
TLS_AES_256_GCM_SHA3840x1302ECDHEFS256Secure
TLS_CHACHA20_POLY1305_SHA2560x1303ECDHEFS256Secure
# TLS 1.2
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3840xC030ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA2560xC02FECDHEFS128Secure
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA2560xCCA8ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA3840xC028ECDHEFS256Weak
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA2560xC027ECDHEFS128Weak
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA0xC014ECDHEFS256Weak
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA0xC013ECDHEFS128Weak
TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA0xC012ECDHEFS112Weak
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
TLS_RSA_WITH_3DES_EDE_CBC_SHA0x000ARSANo FS112Weak

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_RSA_WITH_AES_256_GCM_SHA384Success
Chrome 49 / XP SP3TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
IE 11 / Win 10TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
IE 11 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Android 9.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Android 7.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Android 5.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Android 4.4.2TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Java 11TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Java 8u121TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
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.

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)
finasteride.digital200 OK (unencrypted)200 OK
www.finasteride.digital200 OK (unencrypted)TLS handshake failed
  • http://finasteride.digital answers without redirecting to HTTPS: visitors who type the address without https:// get an unencrypted page.
  • www.finasteride.digital has no working HTTPS (TLS handshake failed): visitors who type that name do not reach the HTTPS site.

Certificate Identity

Common Namefinasteride.digital
Alt Names *.finasteride.digital finasteride.digital
IssuerCN=YR1, O=Let's Encrypt, C=US
Validity 2026-10-06 to 2027-01-04 (44 days remaining)
KeyRSA 2048 bits (sha256RSA)
Serial Number06F38357E76E5B959BFD2591457BD04B5E52
SHA256 Fingerprint e0c8234fc54e31b7439a8a072bf7f694769abadab736126f7966aad5ee77dfd0
Pin SHA2563Cp4vN+zx7sidBtWZ3YgRY2sJ6WoGApSM9H8jGXoGl4=

Certificate Properties

Type DV Domain Validated
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) CRL: http://yr1.c.lencr.org/83.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 Issues
• Incomplete chain: the server does not send all intermediate certificates

Trust Chain Architecture

End-Entity Certificate
CN=finasteride.digital (Issuer: CN=YR1, O=Let's Encrypt, C=US)
Intermediate CA
CN=YR1, O=Let's Encrypt, C=US (Issuer: CN=Root YR, O=ISRG, C=US)
Intermediate CA
CN=Root YR, O=ISRG, C=US (Issuer: CN=ISRG Root X1, O=Internet Security Research Group, C=US)
Root Certificate
CN=ISRG Root X1, O=Internet Security Research Group, C=US (Issuer: CN=ISRG Root X1, O=Internet Security Research Group, C=US)

TLS History & Relations

Everything our scans have seen for finasteride.digital, first seen 2026-11-02; current certificate since 2026-11-02.

Certificates served

Certificate (SHA-256)IssuerValidServed
e0c8234fc54e31b7… current YR12026-10-06 → 2027-01-042026-11-02

Addresses

AddressCertificateSeen
139.162.174.209 e0c8234fc54e31b7… 2026-11-02
139.162.181.76 e0c8234fc54e31b7… 2026-11-02
172.104.149.86 no TLS 2026-11-02
172.104.203.186 e0c8234fc54e31b7… 2026-11-02
172.104.251.198 e0c8234fc54e31b7… 2026-11-02
2a01:7e01::2000:dff:fec1:5cdb e0c8234fc54e31b7… 2026-11-02
2a01:7e01::f03c:95ff:fe00:2692 no TLS 2026-11-02
2a01:7e01::f03c:95ff:fe91:5d91 e0c8234fc54e31b7… 2026-11-02
2a01:7e01::f03c:95ff:feeb:9d4b e0c8234fc54e31b7… 2026-11-02

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-02 01:16BTLS 1.3 e0c8234fc54e31b7… 139.162.174.209, 139.162.181.76, 172.104.149.86, 172.104.203.186, 172.104.251.198

Other hosts seen on the same addresses