SSL Check WHOIS
Dashboard / Security Report

apotheke.biontech.de

Overall grade based on: IPv4: 3 of 3 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:9100:20::17c0:76d2 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2a02:26f0:9100:20::17c0:76d5 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 3 endpoints share identical configuration Select an IP for owner, ASN & location
A+ 95.101.137.197 IPv4 WHOIS › A+ 95.101.137.200 IPv4 WHOIS › A+ 95.101.137.216 IPv4 WHOIS ›
A+

Exceptional Security

Overall Rating
Assessed 2026-11-09 17:41 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 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 (legacy TLS disabled)
Secure Renegotiation Supported (RFC 5746)
Extended Master Secret Yes (RFC 7627)
OCSP Stapling No (certificate has no OCSP responder)
HSTS Yes 182 days
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)
apotheke.biontech.de301 → https://apotheke.biontech.de/ → … → https://pro.biontech.com/ → Too many redirects301 → https://praxis.biontech.de/ → … → https://pro.biontech.com/de/en/public.html → 200 OK
  • http://apotheke.biontech.de ends in too many redirects: visitors never reach a page.
  • https://apotheke.biontech.de forwards visitors to praxis.biontech.de, a different site. View its report ›

DNS Records

As a public resolver answered for apotheke.biontech.de and its domain biontech.de. Looked up 2026-11-09 17:41 UTC · 7 days ago

TypeRecords
apotheke.biontech.de
A
AAAA
MX None
SPF None
biontech.de
A
AAAA
NS
a1-250.akam.net a12-64.akam.net a24-65.akam.net a26-67.akam.net a3-67.akam.net a7-67.akam.net
MX
10 mxa-006a3d01.gslb.pphosted.com 10 mxb-006a3d01.gslb.pphosted.com
SPF
v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com include:mail.zendesk.com ~all

Certificate Properties

Type DV
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) CRL: http://yr2.c.lencr.org/57.crl No OCSP responder — revocation is published via CRL only (as CA/B Forum rules now allow).
DNS CAA Yes (configured) 0 issue "globalsign.com" 0 iodef "mailto:[email protected]" 0 issue "letsencrypt.org" 0 issue "swisssign.com" 0 issue "sectigo.com" 0 issue "awstrust.com"
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=www.biontech.de (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 apotheke.biontech.de, first seen 2026-05-21; current certificate since 2026-11-09.

Certificates served

Certificate (SHA-256)IssuerValidServed
2eea0d23a7e5bdf4… current YR22026-11-03 → 2027-02-012026-11-09

Addresses

AddressCertificateSeen
95.101.137.197 2eea0d23a7e5bdf4… 2026-11-09
95.101.137.200 2eea0d23a7e5bdf4… 2026-11-09
95.101.137.216 2eea0d23a7e5bdf4… 2026-11-09

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-09 17:41A+TLS 1.3 2eea0d23a7e5bdf4… 95.101.137.197, 95.101.137.200, 95.101.137.216

Other domains on the same certificate

Other hosts seen on the same addresses