SSL Check WHOIS
Dashboard / Security Report

www.acluva.org

IPv6: no public AAAA record — the domain is reachable over IPv4 only.
A+

Exceptional Security

Overall Rating
23.185.0.2 · WHOIS ›
Assessed 2026-11-08 03:21 UTC

Grade Breakdown

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

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.acluva.org301 → https://www.acluva.org/ → 200 OK200 OK
acluva.org301 → https://www.acluva.org/ → 200 OK301 → https://www.acluva.org/ → 200 OK
  • http://www.acluva.org redirects to HTTPS.

DNS Records

As a public resolver answered for www.acluva.org and its domain acluva.org. Looked up 2026-11-08 03:21 UTC · 3 days ago

TypeRecords
www.acluva.org
A
AAAA None
MX None
SPF None
acluva.org
A
AAAA None
NS
ns-1205.awsdns-22.org ns-1557.awsdns-02.co.uk ns-224.awsdns-28.com ns-683.awsdns-21.net
MX
10 acluva-org.mail.protection.outlook.com
SPF
v=spf1 a mx include:_spfprod.ngpvan.com include:aspmx.sailthru.com ip4:173.203.13.221 ip4:166.78.227.196 include:spf.protection.outlook.com include:spf-00331602.pphosted.com ~all include:sparkpostmail.com ~all

Certificate Identity

Common Namewww.acluva.org
Alt Names acluva.org www.acluva.org
IssuerCN=YR2, O=Let's Encrypt, C=US
Validity 2026-11-02 to 2027-01-31 (81 days remaining)
KeyRSA 2048 bits (sha256RSA)
Serial Number0655E7BDB35A5759F13F3E48D74387AC76DB
SHA256 Fingerprint 13c3227e98e4928ea20d66581abf84f79c1da5bb8800e64760ee354996f7c70e
Pin SHA256xJeS/6NFl7GBLoWTFMpC3grDLAA3ec7xFZZ9xsTa2Zc=

Certificate Properties

Type DV
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) CRL: http://yr2.c.lencr.org/92.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

Protocol Configuration

Supported Protocols

TLS 1.3
TLS 1.2
TLS 1.1
TLS 1.0
SSL 3
SSL 2

Negotiated Cipher

TLS_AES_128_GCM_SHA256

Protocol Details

Connection
ALPN h2 http/1.1
SNI Required Yes
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 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 0 days
max-age below six months: too short for the A+ grade
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_128_GCM_SHA2560x1301ECDHEFS128Secure
TLS_AES_256_GCM_SHA3840x1302ECDHEFS256Secure
TLS_CHACHA20_POLY1305_SHA2560x1303ECDHEFS256Secure
# TLS 1.2 (server-preferred order)
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA2560xCCA8ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA2560xC02FECDHEFS128Secure
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3840xC030ECDHEFS256Secure

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_RSA_WITH_CHACHA20_POLY1305_SHA256 Success
Chrome 49 / XP SP3TLS 1.2TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Success
IE 11 / Win 10TLS 1.2TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Success
IE 11 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Success
Android 9.0TLS 1.2TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Success
Android 7.0TLS 1.2TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Success
Android 5.0TLS 1.2TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Success
Android 4.4.2TLS 1.2TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Success
Java 11TLS 1.2TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Success
Java 8u121TLS 1.2TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_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=acluva.org (Issuer: CN=YR2, O=Let's Encrypt, C=US)
Intermediate CA
CN=YR2, 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 www.acluva.org, first seen 2026-11-03; current certificate since 2026-11-08.

Certificates served

Certificate (SHA-256)IssuerValidServed
13c3227e98e4928e… current YR22026-11-02 → 2027-01-312026-11-08

Addresses

AddressCertificateSeen
23.185.0.2 13c3227e98e4928e… 2026-11-08

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-08 03:21A+TLS 1.3 13c3227e98e4928e… 23.185.0.2

Other hosts seen on the same addresses