SSL Check WHOIS
Dashboard / Security Report

bahai.de

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

Exceptional Security

Overall Rating
104.198.14.52 · WHOIS ›
Assessed 2026-11-19 02:56 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)
bahai.de301 → https://bahai.de/ → … → https://www.bahai.de/ → 200 OK301 → https://www.bahai.de/ → 200 OK
www.bahai.de301 → https://www.bahai.de/ → 200 OK200 OK
  • http://bahai.de redirects to HTTPS.

DNS Records

As a public resolver answered for bahai.de. Looked up 2026-11-19 02:56 UTC · today

TypeRecords
A
AAAA None
NS
ns81.domaincontrol.com ns82.domaincontrol.com
MX
0 bahai-de.mail.protection.outlook.com
SPF
v=spf1 mx include:spf.mailjet.com include:spf.protection.outlook.com a include:ispgateway.de ip4:82.206.66.78 ip4:80.67.29.51 ip4:134.119.19.105 ip6:2a00:1169:103:7800:: include:_spf.zimpel.de ~all

Certificate Identity

Common Namebahai.de
Alt Names bahai.de www.bahai.de
IssuerCN=YE2, O=Let's Encrypt, C=US
Validity 2026-10-25 to 2027-01-23 (65 days remaining)
KeyECDSA 256 bits (sha384ECDSA)
Serial Number059B8EEA17E7DD361CE46F66A917F19D833D
SHA256 Fingerprint 4c4beb3ede753507c18b76cb257789e211455b5fdff641c81b95127f67fbc740
Pin SHA256qRvETFfZRZC5x8GmtGKfKNFRKu6mD+JdLNul6K62Ovg=

Certificate Properties

Type DV Domain Validated
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) CRL: http://ye2.c.lencr.org/62.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 x25519 secp256r1 (server preference order)
Post-Quantum Key Exchange No (no hybrid ML-KEM group such as 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 1 year
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_ECDSA_WITH_AES_128_GCM_SHA2560xC02BECDHEFS128Secure
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA3840xC02CECDHEFS256Secure
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA2560xCCA9ECDHEFS256Secure

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_ECDSA_WITH_AES_128_GCM_SHA256 Success
Chrome 49 / XP SP3TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Success
IE 11 / Win 10TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Success
IE 11 / Win 7TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Success
Android 9.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Success
Android 7.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Success
Android 5.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Success
Android 4.4.2TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Success
Java 11TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Success
Java 8u121TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_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=www.bahai.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 bahai.de, first seen 2026-11-19; current certificate since 2026-11-19.

Certificates served

Certificate (SHA-256)IssuerValidServed
4c4beb3ede753507… current YE22026-10-25 → 2027-01-232026-11-19

Addresses

AddressCertificateSeen
104.198.14.52 4c4beb3ede753507… 2026-11-19

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-19 02:56A+TLS 1.3 4c4beb3ede753507… 104.198.14.52

Other hosts seen on the same addresses