SSL Check WHOIS
Dashboard / Security Report

knf.com

Overall grade based on: IPv4: 4 of 4 complete · IPv6: 4 of 4 complete
All 8 endpoints share identical configuration Select an IP for owner, ASN & location
A+ 3.162.38.24 IPv4 WHOIS › A+ 3.162.38.33 IPv4 WHOIS › A+ 3.162.38.7 IPv4 WHOIS › A+ 3.162.38.99 IPv4 WHOIS › A+ 2600:9000:262a:1a00:5:e821:ddc0:93a1 IPv6 WHOIS › A+ 2600:9000:262a:2000:5:e821:ddc0:93a1 IPv6 WHOIS › A+ 2600:9000:262a:800:5:e821:ddc0:93a1 IPv6 WHOIS › A+ 2600:9000:262a:9c00:5:e821:ddc0:93a1 IPv6 WHOIS ›

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 SecP256r1MLKEM768 x25519 secp256r1 secp384r1 (server preference order)
Post-Quantum Key Exchange Yes X25519MLKEM768, SecP256r1MLKEM768
HTTP/3 (QUIC) Yes (advertised)
Encrypted Client Hello No
Security Features
Forward SecrecyYes (ECDHE / DHE)
Scan Coverage Incomplete no answer in time for: key exchange groups — shown as unknown, not as unsupported
Downgrade Prevention Yes (legacy TLS disabled)
Secure Renegotiation Supported (RFC 5746)
Extended Master Secret Yes (RFC 7627)
OCSP Stapling Yes
HSTS No
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_128_GCM_SHA2560xC02FECDHEFS128Secure
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3840xC030ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA2560xCCA8ECDHEFS256Secure

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.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)
knf.com301 → https://knf.com/ → … → https://knf.com/fr/fr → 200 OK301 → https://knf.com/en/ → … → https://knf.com/fr/fr → 200 OK
www.knf.com301 → https://www.knf.com/ → … → https://knf.com/fr/fr → 200 OK301 → https://knf.com/ → … → https://knf.com/fr/fr → 200 OK
  • http://knf.com redirects to HTTPS.

Certificate Identity

Common Nameknf.com
Alt Names knf.com www.knf.com
IssuerCN=Amazon RSA 2048 M04, O=Amazon, C=US
Validity 2026-08-06 to 2027-02-19 (94 days remaining)
KeyRSA 2048 bits (sha256RSA)
Serial Number015FBA155E80B25C8B64BE38DEDAA056
SHA256 Fingerprint 679f5ce34f92ce1b1e374ef837066ac712b238e95c72af77ea5db3ce5d54d9d8
Pin SHA256gSE9kANZwLVczVDwqclwmF8+mrLX0wJqXku58qrix4o=

Certificate Properties

Type DV
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) OCSP: http://ocsp.r2m04.amazontrust.com CRL: http://crl.r2m04.amazontrust.com/r2m04.crl
DNS CAA No (missing)
Trusted By Yes Mozilla · Apple · Android · Java · Windows
Name Match Yes
Validity Period 198 days (maximum 200 days for certificates issued then)
Chain IssuesNone

Trust Chain Architecture

End-Entity Certificate
CN=knf.com (Issuer: CN=Amazon RSA 2048 M04, O=Amazon, C=US)
Intermediate CA
CN=Amazon RSA 2048 M04, O=Amazon, C=US (Issuer: CN=Amazon Root CA 1, O=Amazon, C=US)
Root Certificate
CN=Amazon Root CA 1, O=Amazon, C=US (Issuer: CN=Amazon Root CA 1, O=Amazon, C=US)

TLS History & Relations

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

Certificates served

Certificate (SHA-256)IssuerValidServed
679f5ce34f92ce1b… current Amazon RSA 2048 M042026-08-06 → 2027-02-192026-11-02

Addresses

AddressCertificateSeen
3.162.38.7 679f5ce34f92ce1b… 2026-11-02
3.162.38.24 679f5ce34f92ce1b… 2026-11-02
3.162.38.33 679f5ce34f92ce1b… 2026-11-02
3.162.38.99 679f5ce34f92ce1b… 2026-11-02
2600:9000:262a:800:5:e821:ddc0:93a1 679f5ce34f92ce1b… 2026-11-02
2600:9000:262a:1a00:5:e821:ddc0:93a1 679f5ce34f92ce1b… 2026-11-02
2600:9000:262a:2000:5:e821:ddc0:93a1 679f5ce34f92ce1b… 2026-11-02
2600:9000:262a:9c00:5:e821:ddc0:93a1 679f5ce34f92ce1b… 2026-11-02

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-02 00:04A+TLS 1.3 679f5ce34f92ce1b… 3.162.38.7, 3.162.38.24, 3.162.38.33, 3.162.38.99

Other hosts seen on the same addresses