SSL Check WHOIS
Dashboard / Security Report

wuppertaler-rundschau.de

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.

wuppertaler-rundschau.de: SSL/TLS grade B (HTTPS Monitor)wuppertaler-rundschau.deB
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.67.236 IPv4 WHOIS › B 172.67.182.245 IPv4 WHOIS › B 2606:4700:3033::ac43:b6f5 IPv6 WHOIS › B 2606:4700:3035::6815:43ec 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 Yes 2 years
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_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)
wuppertaler-rundschau.de302 → https://wuppertaler-rundschau.de/ → … → https://www.wuppertaler-rundschau.de/ → 200 OK301 → https://www.wuppertaler-rundschau.de/ → 200 OK
www.wuppertaler-rundschau.de302 → https://www.wuppertaler-rundschau.de/ → 200 OK200 OK
  • http://wuppertaler-rundschau.de redirects to HTTPS.

DNS Records

As a public resolver answered for wuppertaler-rundschau.de. Looked up 2026-11-17 08:07 UTC · 3 days ago

TypeRecords
A
AAAA
NS
javier.ns.cloudflare.com joyce.ns.cloudflare.com
MX
0 wuppertalerrundschau-de02i.mail.protection.outlook.com
SPF
v=spf1 mx ip4:144.76.226.135 a:webserver.simadesign.de include:_spf.salesforce.com include:spf.rbpd.de -all

Certificate Identity

Common Namewuppertaler-rundschau.de
Alt Names *.wuppertaler-rundschau.de wuppertaler-rundschau.de
IssuerCN=YE2, O=Let's Encrypt, C=US
Validity 2026-10-19 to 2027-01-17 (57 days remaining)
KeyECDSA 256 bits (sha384ECDSA)
Serial Number05E5BFBF9549C5B55E8831C02E0311F4C87C
SHA256 Fingerprint e2aee90250365bac31d149f2d1dfd55a0bf7218ed8363a0e2d375dbb30ab8509
Pin SHA256Yq2eUVitCmMBqhlLQgagwq+y4IK/EIX9TwMhsqBGTxk=

Certificate Properties

Type DV Domain Validated
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) CRL: http://ye2.c.lencr.org/125.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=wuppertaler-rundschau.de (Issuer: CN=YE2, O=Let's Encrypt, C=US)
Intermediate CA
CN=YE2, 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 wuppertaler-rundschau.de, first seen 2026-11-17; current certificate since 2026-11-17.

Certificates served

Certificate (SHA-256)IssuerValidServed
e2aee90250365bac… current YE22026-10-19 → 2027-01-172026-11-17

Addresses

AddressCertificateSeen
104.21.67.236 e2aee90250365bac… 2026-11-17
172.67.182.245 e2aee90250365bac… 2026-11-17
2606:4700:3033::ac43:b6f5 e2aee90250365bac… 2026-11-17
2606:4700:3035::6815:43ec e2aee90250365bac… 2026-11-17

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-17 08:07BTLS 1.3 e2aee90250365bac… 104.21.67.236, 172.67.182.245

Other hosts seen on the same addresses