SSL Check WHOIS
Dashboard / Security Report

www.openbadges.org

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.

www.openbadges.org: SSL/TLS grade A+ (HTTPS Monitor)www.openbadges.orgA+
IPv6: no public AAAA record — the domain is reachable over IPv4 only.
All 3 endpoints share identical configuration Select an IP for owner, ASN & location
A+ 34.226.46.235 IPv4 WHOIS › A+ 34.238.11.122 IPv4 WHOIS › A+ 54.89.106.200 IPv4 WHOIS ›
A+

Exceptional Security

Overall Rating
Assessed 2026-11-08 12:19 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_128_GCM_SHA256

Protocol Details

Connection
ALPN h2 http/1.1
SNI Required Yes
Supported Named Groups X25519MLKEM768 x25519 secp256r1 secp384r1 (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 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_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_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.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.openbadges.org301 → https://www.openbadges.org/ → … → https://openbadges.org/ → 200 OK301 → https://openbadges.org/ → 200 OK
openbadges.org301 → https://openbadges.org/ → 200 OK200 OK
  • http://www.openbadges.org redirects to HTTPS.

DNS Records

As a public resolver answered for www.openbadges.org and its domain openbadges.org. Looked up 2026-11-08 12:19 UTC · 12 days ago

TypeRecords
www.openbadges.org
A
AAAA None
MX None
SPF None
openbadges.org
A
AAAA None
NS
ns-1193.awsdns-21.org ns-1980.awsdns-55.co.uk ns-337.awsdns-42.com ns-592.awsdns-10.net
MX
10 mx1.scl3.mozilla.com 20 mx2.scl3.mozilla.com
SPF
v=spf1 include:support.zendesk.com include:smtp.zendesk.com mx:mozilla.com ~all

Certificate Identity

Common Namewww.openbadges.org
Alt Names openbadges.org www.openbadges.org
IssuerCN=YE2, O=Let's Encrypt, C=US
Validity 2026-09-19 to 2026-12-18 (27 days remaining)
KeyECDSA 256 bits (sha384ECDSA)
Serial Number064515B5E89C54EEBDB5672A6F774145C053
SHA256 Fingerprint e2812aace26d6dd0fc14e99646162c8cf13fe5b13a7050a57aad4d74cd2276f5
Pin SHA256uj2++YXHKXeVNc5w9kBvs56I+S5xKfrfRQShP9YcVUA=

Certificate Properties

Type DV Domain Validated
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) CRL: http://ye2.c.lencr.org/84.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=openbadges.org (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 www.openbadges.org, first seen 2026-08-03; current certificate since 2026-11-08.

Certificates served

Certificate (SHA-256)IssuerValidServed
e2812aace26d6dd0… current YE22026-09-19 → 2026-12-182026-11-08

Addresses

AddressCertificateSeen
34.226.46.235 e2812aace26d6dd0… 2026-11-08
34.238.11.122 e2812aace26d6dd0… 2026-11-08
54.89.106.200 e2812aace26d6dd0… 2026-11-08

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-08 12:19A+TLS 1.3 e2812aace26d6dd0… 34.226.46.235, 34.238.11.122, 54.89.106.200

Other hosts seen on the same addresses