SSL Check WHOIS
Dashboard / Security Report

rogersbh.org

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

Exceptional Security

Overall Rating
150.171.109.106 · WHOIS ›
Assessed 2026-11-06 00:30 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)
rogersbh.org307 → https://rogersbh.org/ → 200 OK200 OK
www.rogersbh.org307 → https://www.rogersbh.org/ → … → https://rogersbh.org/ → 200 OK308 → https://rogersbh.org/ → 200 OK
  • http://rogersbh.org redirects to HTTPS.

DNS Records

As a public resolver answered for rogersbh.org. Looked up 2026-11-06 00:30 UTC · 11 days ago

TypeRecords
A
AAAA None
NS
ns1-01.azure-dns.com ns2-01.azure-dns.net ns3-01.azure-dns.org ns4-01.azure-dns.info
MX
0 rogersbh-org.mail.protection.outlook.com
SPF
v=spf1 include:spf.protection.outlook.com ip4:205.182.132.75 ip4:167.89.101.239 ip4:158.228.129.79 ip4:198.2.128.0/18 ip4:205.201.128.0/20 ip4:149.72.147.186 ip4:23.21.0.26 ip4:52.203.38.31 ip4:52.158.168.30 include:servers.mcsv.net include:outboundmail.blackbaud.net include:_spf.salesforce.com include:spf-00b03901.pphosted.com ~all

Certificate Identity

Common Namerogersbh.org
Alt Names rogersbh.org
IssuerCN=GeoTrust TLS RSA CA G1, OU=www.digicert.com, O=DigiCert Inc, C=US
Validity 2026-06-10 to 2026-12-10 (23 days remaining)
KeyRSA 2048 bits (sha256RSA)
Serial Number07484F40533ABD5AE85121F5FA1AB397
SHA256 Fingerprint 3743dfc177ea6999f7fd769a59f0a91d9b8aaefbb6d9f56e9462510ae61e1621
Pin SHA256mlPk0PYmr/cXcXYyRAkOKJ9o9D0KmYWzOkYM8ebRdok=

Certificate Properties

Type DV
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) OCSP: http://status.geotrust.com CRL: http://cdp.geotrust.com/GeoTrustTLSRSACAG1.crl
DNS CAA Yes (configured) 0 issue "sectigo.com" 0 issue "letsencrypt.org" 0 issue "digicert.com" 0 issue "amazon.com" 0 issue "godaddy.com"
Trusted By Yes Mozilla · Apple · Android · Java · Windows
Name Match Yes
Validity Period 184 days (maximum 200 days for certificates issued then)
Chain Issues
• Contains anchor (root CA included in chain)

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 SecP256r1MLKEM768 X25519MLKEM768 secp256r1 secp384r1 secp521r1 (server preference order)
Post-Quantum Key Exchange Yes SecP256r1MLKEM768, 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
HSTS Yes 1 year · includeSubDomains · preload
HSTS Preloading Preloaded
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_256_GCM_SHA3840x1302ECDHEFS256Secure
TLS_AES_128_GCM_SHA2560x1301ECDHEFS128Secure
# TLS 1.2 (server-preferred order)
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3840xC030ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA2560xC02FECDHEFS128Secure

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_AES_256_GCM_SHA384 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_RSA_WITH_AES_256_GCM_SHA384 Success
Chrome 49 / XP SP3TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
IE 11 / Win 10TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
IE 11 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Android 9.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Android 7.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Android 5.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Android 4.4.2TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Java 11TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Java 8u121TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 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=rogersbh.org (Issuer: CN=GeoTrust TLS RSA CA G1, OU=www.digicert.com, O=DigiCert Inc, C=US)
Intermediate CA
CN=GeoTrust TLS RSA CA G1, OU=www.digicert.com, O=DigiCert Inc, C=US (Issuer: CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US)
Root Certificate
CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US (Issuer: CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US)

TLS History & Relations

Everything our scans have seen for rogersbh.org, first seen 2026-11-06; current certificate since 2026-11-06.

Certificates served

Certificate (SHA-256)IssuerValidServed
3743dfc177ea6999… current GeoTrust TLS RSA CA G12026-06-10 → 2026-12-102026-11-06

Addresses

AddressCertificateSeen
150.171.109.106 3743dfc177ea6999… 2026-11-06

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-06 00:30A+TLS 1.3 3743dfc177ea6999… 150.171.109.106

Other hosts seen on the same addresses