SSL Check WHOIS
Dashboard / Security Report

www.kiesuwkrant.be

Overall grade based on: IPv4: 2 of 2 complete · IPv6: 0 of 2 complete, 2 pending — IPv6 results are added below when their scan finishes; they do not count until then.
IPv6 scan in progress
2a02:26f0:3900::211:c4a0 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2a02:26f0:3900::211:c4a2 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 2 endpoints share identical configuration Select an IP for owner, ASN & location
A+ 2.17.197.122 IPv4 WHOIS › A+ 2.17.197.179 IPv4 WHOIS ›
A+

Exceptional Security

Overall Rating
Assessed 2026-11-14 01:30 UTC

Grade Breakdown

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

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 http/1.1
SNI Required Yes
Supported Named Groups X25519MLKEM768 x25519 secp256r1 (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 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
TLS_AES_256_GCM_SHA3840x1302ECDHEFS256Secure
TLS_CHACHA20_POLY1305_SHA2560x1303ECDHEFS256Secure
TLS_AES_128_GCM_SHA2560x1301ECDHEFS128Secure
TLS_AES_128_CCM_SHA2560x1304ECDHEFS128Secure
# 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_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

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)
www.kiesuwkrant.be302 → https://advertising.persgroep.net/marketing/overkoepelend/2021/kranten/ → … → https://myprivacy.dpgmedia.be/consent → 200 OK302 → https://advertising.persgroep.net/marketing/overkoepelend/2021/kranten/ → … → https://myprivacy.dpgmedia.be/consent → 200 OK
kiesuwkrant.beNo answer (timed out)403 Forbidden · certificate does not cover this name
  • http://www.kiesuwkrant.be redirects to HTTPS.
  • https://www.kiesuwkrant.be forwards visitors to advertising.persgroep.net, a different site. View its report ›
  • kiesuwkrant.be serves a certificate that does not cover its name: browsers show a security warning there.

DNS Records

As a public resolver answered for www.kiesuwkrant.be and its domain kiesuwkrant.be. Looked up 2026-11-14 01:30 UTC · 3 days ago

TypeRecords
www.kiesuwkrant.be
A
AAAA
MX None
SPF None
kiesuwkrant.be
A
AAAA None
NS
eur2.akam.net eur5.akam.net eur6.akam.net ns1-125.akam.net ns1-25.akam.net usc2.akam.net use2.akam.net use5.akam.net
MX None
SPF
v=spf1 -all

Certificate Identity

Common Namewww.kiesuwkrant.be
Alt Names brandedcontentbe.nina.be brandedcontentbe.spaargids.be campus.persgroep.com guide-epargne.be persgroep.be persverkoper.persgroep.be playground.joe.be playground.qmusic.be playground.qmusic.nl spaargids.be www.guide-epargne.be www.kiesuwkrant.be www.leadsdirect.be www.medialaan-persgroep-adverteren.be www.primo.be www.spaargids.be
IssuerCN=YR2, O=Let's Encrypt, C=US
Validity 2026-09-24 to 2026-12-23 (35 days remaining)
KeyRSA 2048 bits (sha256RSA)
Serial Number05E9DF5DCFC6995961F9E11A96182F81DEAD
SHA256 Fingerprint b3d1167ec29e886c63bead5359566304d2cd9913b26c1cf62c56ee11bedbac38
Pin SHA256bF/8etBC1KPv45d489L2/h+yBSNbe8sJV8WyE6R/ZUw=

Certificate Properties

Type DV
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) CRL: http://yr2.c.lencr.org/46.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=persgroep.be (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.kiesuwkrant.be, first seen 2026-11-11; current certificate since 2026-11-14.

Certificates served

Certificate (SHA-256)IssuerValidServed
b3d1167ec29e886c… current YR22026-09-24 → 2026-12-232026-11-14

Addresses

AddressCertificateSeen
2.17.197.122 b3d1167ec29e886c… 2026-11-14
2.17.197.179 b3d1167ec29e886c… 2026-11-14

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-14 01:30A+TLS 1.3 b3d1167ec29e886c… 2.17.197.122, 2.17.197.179

Other domains on the same certificate

Other hosts seen on the same addresses