SSL Check WHOIS
igmchicago.org has no HTTPS: HTTPS could not be reached on its IPv4 address. The site is served on www.igmchicago.org; this is its report. (igmchicago.org checked 2026-09-16 14:14 UTC)
Dashboard / Security Report

www.igmchicago.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.igmchicago.org: SSL/TLS grade A+ (HTTPS Monitor)www.igmchicago.orgA+
IPv6: no public AAAA record — the domain is reachable over IPv4 only.
A+

Exceptional Security

Overall Rating
66.235.200.147 · WHOIS ›
Assessed 2026-11-18 22:24 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)
www.igmchicago.org403 Forbidden (unencrypted)403 Forbidden
igmchicago.org403 Forbidden (unencrypted)TLS handshake failed
  • http://www.igmchicago.org answers without redirecting to HTTPS: visitors who type the address without https:// get an unencrypted page.
  • igmchicago.org has no working HTTPS (TLS handshake failed): visitors who type that name do not reach the HTTPS site.

DNS Records

As a public resolver answered for www.igmchicago.org and its domain igmchicago.org. Looked up 2026-11-18 22:24 UTC · 1 day ago

TypeRecords
www.igmchicago.org
A
AAAA None
MX
0 mail.igmchicago.org
SPF
v=spf1 +a +mx +ip4:50.87.231.172 +ip4:50.87.231.173 +include:websitewelcome.com ~all
igmchicago.org
A
AAAA None
NS
ns1.bluehost.com ns2.bluehost.com
MX
0 mail.igmchicago.org
SPF
v=spf1 +a +mx +ip4:50.87.231.172 +ip4:50.87.231.173 +include:websitewelcome.com ~all

Certificate Identity

Common Namewww.igmchicago.org
Alt Names www.igmchicago.org
IssuerCN=WE1, O=Google Trust Services, C=US
Validity 2026-10-22 to 2027-01-20 (61 days remaining)
KeyECDSA 256 bits (sha256ECDSA)
Serial Number3EE51844FCCE180C0E27AB447E4A211D
SHA256 Fingerprint fe67f21bc37416ad270b8b764a8be3b81dd0e19f40b20b31d5cda704f477db78
Pin SHA256d+cqzzwf+Gbmv7cSckERoeHbn0evbgK0wct/MczLbM0=

Certificate Properties

Type DV Domain Validated
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) CRL: http://c.pki.goog/we1/IgdQtKwMhFI.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_256_GCM_SHA384

Protocol Details

Connection
ALPN h2 http/1.1
SNI Required Yes
Supported Named Groups X25519MLKEM768 X25519Kyber768Draft00 x25519 secp256r1 secp384r1 secp521r1 (server preference order)
Post-Quantum Key Exchange Yes X25519MLKEM768, X25519Kyber768Draft00
HTTP/3 (QUIC) Yes (advertised)
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 (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.igmchicago.org (Issuer: CN=WE1, O=Google Trust Services, C=US)
Intermediate CA
CN=WE1, O=Google Trust Services, C=US (Issuer: CN=GTS Root R4, O=Google Trust Services LLC, C=US)
Root Certificate
CN=GTS Root R4, O=Google Trust Services LLC, C=US (Issuer: CN=GTS Root R4, O=Google Trust Services LLC, C=US)

TLS History & Relations

Everything our scans have seen for www.igmchicago.org, first seen 2026-11-18; current certificate since 2026-11-18.

Certificates served

Certificate (SHA-256)IssuerValidServed
fe67f21bc37416ad… current WE12026-10-22 → 2027-01-202026-11-18

Addresses

AddressCertificateSeen
66.235.200.147 fe67f21bc37416ad… 2026-11-18

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-18 22:24A+TLS 1.3 fe67f21bc37416ad… 66.235.200.147

Other hosts seen on the same addresses