SSL Check WHOIS
Dashboard / Security Report

clusterfuzz.com

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.

clusterfuzz.com: SSL/TLS grade B (HTTPS Monitor)clusterfuzz.comB
Overall grade based on: IPv4: 4 of 4 complete · IPv6: 0 of 4 complete, 4 pending — IPv6 results are added below when their scan finishes; they do not count until then.
IPv6 scan in progress
2001:4860:4802:32::15 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2001:4860:4802:34::15 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2001:4860:4802:36::15 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2001:4860:4802:38::15 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.

All 4 endpoints share identical configuration Select an IP for owner, ASN & location
B 216.239.32.21 IPv4 WHOIS › B 216.239.34.21 IPv4 WHOIS › B 216.239.36.21 IPv4 WHOIS › B 216.239.38.21 IPv4 WHOIS ›
B

Adequate Protection

Overall Rating
Assessed 2026-11-22 14:10 UTC

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.
  • •Weak 3DES cipher supported (Sweet32).
  • •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 x25519 secp256r1 (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 (TLS_FALLBACK_SCSV)
Secure Renegotiation Supported (RFC 5746)
Extended Master Secret Yes (RFC 7627)
OCSP Stapling No (certificate has no OCSP responder)
HSTS Yes 30 days · includeSubDomains
max-age below six months: too short for the A+ grade
HSTS Preloading Not preloadedSubmit →
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_RSA_WITH_AES_128_GCM_SHA2560xC02FECDHEFS128Secure
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA2560xCCA8ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3840xC030ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA0xC013ECDHEFS128Weak
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA0xC014ECDHEFS256Weak
TLS_RSA_WITH_AES_128_GCM_SHA2560x009CRSANo FS128Weak
TLS_RSA_WITH_AES_256_GCM_SHA3840x009DRSANo FS256Weak
TLS_RSA_WITH_AES_128_CBC_SHA0x002FRSANo FS128Weak
TLS_RSA_WITH_AES_256_CBC_SHA0x0035RSANo FS256Weak
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_128_GCM_SHA256Success
Chrome 49 / XP SP3TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
IE 11 / Win 10TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
IE 11 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 9.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 7.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 5.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 4.4.2TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Java 11TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Java 8u121TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 4.0.4TLS 1.0TLS_ECDHE_RSA_WITH_AES_128_CBC_SHASuccess
Android 4.1.1TLS 1.0TLS_ECDHE_RSA_WITH_AES_128_CBC_SHASuccess
Baidu Jan 2015TLS 1.0TLS_ECDHE_RSA_WITH_AES_128_CBC_SHASuccess
Java 6TLS 1.0TLS_ECDHE_RSA_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)
clusterfuzz.com302 → https://clusterfuzz.com/ → … → https://clusterfuzz.com/login → 200 OK302 → https://clusterfuzz.com/login → 200 OK
www.clusterfuzz.com302 → https://www.clusterfuzz.com/ → TLS handshake failedTLS handshake failed
  • http://clusterfuzz.com redirects to HTTPS.
  • www.clusterfuzz.com has no working HTTPS (TLS handshake failed): visitors who type that name do not reach the HTTPS site.

DNS Records

As a public resolver answered for clusterfuzz.com. Looked up 2026-11-22 14:10 UTC · today

TypeRecords
A
AAAA
NS
ns-cloud-b1.googledomains.com ns-cloud-b2.googledomains.com ns-cloud-b3.googledomains.com ns-cloud-b4.googledomains.com
MX None
SPF
v=spf1 include:_spf.google.com ?all

Certificate Identity

Common Nameclusterfuzz.com
Alt Names clusterfuzz.com
IssuerCN=WR3, O=Google Trust Services, C=US
Validity 2026-10-08 to 2027-01-06 (45 days remaining)
KeyRSA 2048 bits (sha256RSA)
Serial Number00AE94A45A7A73DC060ACBEC9D93804CA4
SHA256 Fingerprint fe984a5ce4d0987fc7eb54730e3e1737c7add1fdedef7e362de61cedd9ca8d4a
Pin SHA256p/67XjVKWOhjFtq656RxIwk5P88MBjuRMFZdrbEOBpk=

Certificate Properties

Type DV Domain Validated
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) CRL: http://c.pki.goog/wr3/RqT89ooGdns.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=clusterfuzz.com (Issuer: CN=WR3, O=Google Trust Services, C=US)
Intermediate CA
CN=WR3, O=Google Trust Services, C=US (Issuer: CN=GTS Root R1, O=Google Trust Services LLC, C=US)
Root Certificate
CN=GTS Root R1, O=Google Trust Services LLC, C=US (Issuer: CN=GTS Root R1, O=Google Trust Services LLC, C=US)

TLS History & Relations

Everything our scans have seen for clusterfuzz.com, first seen 2026-11-22; current certificate since 2026-11-22.

Certificates served

Certificate (SHA-256)IssuerValidServed
fe984a5ce4d0987f… current WR32026-10-08 → 2027-01-062026-11-22

Addresses

AddressCertificateSeen
216.239.32.21 fe984a5ce4d0987f… 2026-11-22
216.239.34.21 fe984a5ce4d0987f… 2026-11-22
216.239.36.21 fe984a5ce4d0987f… 2026-11-22
216.239.38.21 fe984a5ce4d0987f… 2026-11-22

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-22 14:10BTLS 1.3 fe984a5ce4d0987f… 216.239.32.21, 216.239.34.21, 216.239.36.21, 216.239.38.21

Other hosts seen on the same addresses