SSL Check WHOIS
Dashboard / Security Report

bergen.com

Overall grade based on: IPv4: 3 of 3 complete · IPv6: 3 of 3 complete
All 6 endpoints share identical configuration Select an IP for owner, ASN & location
A+ 18.185.24.46 IPv4 WHOIS › A+ 3.126.5.188 IPv4 WHOIS › A+ 3.71.139.153 IPv4 WHOIS › A+ 2a05:d014:803:f30a:4c8d:5530:dac2:179 IPv6 WHOIS › A+ 2a05:d014:803:f30c:505c:9738:13c:b7a5 IPv6 WHOIS › A+ 2a05:d014:803:f30e:ffe5:90d1:736a:fcad IPv6 WHOIS ›

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 No
SNI Required Yes
Supported Named Groups X25519MLKEM768 SecP256r1MLKEM768 SecP384r1MLKEM1024 x25519 secp256r1 secp384r1 secp521r1 (server preference order)
Post-Quantum Key Exchange Yes X25519MLKEM768, SecP256r1MLKEM768, SecP384r1MLKEM1024
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 Unknown (the HTTPS request to this IP failed)
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
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)
bergen.com301 → https://www.northjersey.com/ → 402 Payment Required301 → https://www.northjersey.com/ → 402 Payment Required
www.bergen.com301 → https://www.northjersey.com/ → 402 Payment Required301 → https://www.northjersey.com/ → 402 Payment Required
  • http://bergen.com redirects to HTTPS.
  • https://bergen.com forwards visitors to www.northjersey.com, a different site, which answers 402 Payment Required. View its report ›

Certificate Identity

Common Namebergen.com
Alt Names bergen.com
IssuerCN=YE1, O=Let's Encrypt, C=US
Validity 2026-10-25 to 2027-01-23 (66 days remaining)
KeyECDSA 256 bits (sha384ECDSA)
Serial Number05CD8256023AA615E7DC0CAAE794682D7A36
SHA256 Fingerprint e3a130d7cf1d9c0590f081606e5ea85fe749ddbb8fe10f6ec51ebdd3a6024c6a
Pin SHA256g7diQu0zVrTiGJG1UwGQO2PkdT6WWDW47Pp5Gb/TGXw=

Certificate Properties

Type DV
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) CRL: http://ye1.c.lencr.org/55.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=bergen.com (Issuer: CN=YE1, O=Let's Encrypt, C=US)
Intermediate CA
CN=YE1, 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 bergen.com, first seen 2026-11-02; current certificate since 2026-11-02.

Certificates served

Certificate (SHA-256)IssuerValidServed
e3a130d7cf1d9c05… current YE12026-10-25 → 2027-01-232026-11-02

Addresses

AddressCertificateSeen
3.71.139.153 e3a130d7cf1d9c05… 2026-11-02
3.126.5.188 e3a130d7cf1d9c05… 2026-11-02
18.185.24.46 e3a130d7cf1d9c05… 2026-11-02
2a05:d014:803:f30a:4c8d:5530:dac2:179 e3a130d7cf1d9c05… 2026-11-02
2a05:d014:803:f30c:505c:9738:13c:b7a5 e3a130d7cf1d9c05… 2026-11-02
2a05:d014:803:f30e:ffe5:90d1:736a:fcad e3a130d7cf1d9c05… 2026-11-02

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-02 00:37A+TLS 1.3 e3a130d7cf1d9c05… 3.71.139.153, 3.126.5.188, 18.185.24.46

Other hosts seen on the same addresses