SSL Check WHOIS
Dashboard / Security Report

engage.bellevue.edu

IPv6: no public AAAA record — the domain is reachable over IPv4 only.
All 2 endpoints share identical configuration Select an IP for owner, ASN & location
A+ 192.0.78.168 IPv4 WHOIS › A+ 192.0.78.252 IPv4 WHOIS ›
A+

Exceptional Security

Overall Rating
Assessed 2026-11-09 20:48 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 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
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
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA0xC009ECDHEFS128Weak
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA0xC00AECDHEFS256Weak

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)
engage.bellevue.edu301 → https://engage.bellevue.edu/ → … → https://engage.bellevue.edu/wp-login.php → 200 OK302 → https://engage.bellevue.edu/wp-login.php → 200 OK
  • http://engage.bellevue.edu redirects to HTTPS.

DNS Records

As a public resolver answered for engage.bellevue.edu and its domain bellevue.edu. Looked up 2026-11-09 20:48 UTC · 7 days ago

TypeRecords
engage.bellevue.edu
A
AAAA None
MX None
SPF
v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all
bellevue.edu
A
AAAA None
NS
ns-1001.awsdns-61.net ns-110.awsdns-13.com ns-1228.awsdns-25.org ns-1752.awsdns-27.co.uk
MX
10 mxa-00250701.gslb.pphosted.com 10 mxb-00250701.gslb.pphosted.com
SPF
v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all

Certificate Properties

Type DV
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) CRL: http://c.pki.goog/wr1/CSgwEPPALl0.crl No OCSP responder — revocation is published via CRL only (as CA/B Forum rules now allow).
DNS CAA Yes (configured) 0 issue "amazon.com" 0 issue "digicert.com" 0 issue "letsencrypt.org" 0 issue "pki.goog" 0 issue "ssl.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=tls.automattic.com (Issuer: CN=WR1, O=Google Trust Services, C=US)
Intermediate CA
CN=WR1, O=Google Trust Services, C=US (Issuer: CN=GTS Root R1, O=Google Trust Services LLC, C=US)
Root Certificate
CN=GTS Root R1, O=Google Trust Services LLC, C=US (Issuer: CN=GTS Root R1, O=Google Trust Services LLC, C=US)

TLS History & Relations

Everything our scans have seen for engage.bellevue.edu, first seen 2026-11-07; current certificate since 2026-11-09.

Certificates served

Certificate (SHA-256)IssuerValidServed
a5b7e4fb322c1d0a… current WR12026-10-28 → 2027-01-262026-11-09

Addresses

AddressCertificateSeen
192.0.78.168 a5b7e4fb322c1d0a… 2026-11-09
192.0.78.252 a5b7e4fb322c1d0a… 2026-11-09

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-09 20:48A+TLS 1.3 a5b7e4fb322c1d0a… 192.0.78.168, 192.0.78.252

Other domains on the same certificate

Other hosts seen on the same addresses