SSL Check WHOIS
Dashboard / Security Report

parcmontbellevue.com

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
F 185.230.63.107 IPv4 WHOIS › F 185.230.63.171 IPv4 WHOIS › F 185.230.63.186 IPv4 WHOIS ›
F

Critical: Insecure

Overall Rating
Assessed 2026-11-19 08:47 UTC

Grade Breakdown

Protocol Support 95%
Key Exchange 90%
Cipher Strength 100%
Certificate 0%
Certificate has expired. This domain's SSL/TLS certificate is no longer valid and browsers will show security warnings to visitors.
Certificate is expired.

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 secp521r1 (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
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_RSA_WITH_AES_128_GCM_SHA2560xC02FECDHEFS128Secure
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3840xC030ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA2560xCCA8ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA0xC013ECDHEFS128Weak
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA0xC014ECDHEFS256Weak

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_RSA_WITH_AES_128_GCM_SHA256Success
Chrome 49 / XP SP3TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
IE 11 / Win 10TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
IE 11 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 9.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 7.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 5.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 4.4.2TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Java 11TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Java 8u121TLS 1.2TLS_ECDHE_RSA_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)
parcmontbellevue.com301 → https://parcmontbellevue.com/ → … → https://www.parcmontbellevue.com/ → 200 OK301 → https://www.parcmontbellevue.com/ → 200 OK · certificate expired
www.parcmontbellevue.com301 → https://www.parcmontbellevue.com/ → 200 OK200 OK
  • http://parcmontbellevue.com redirects to HTTPS.

DNS Records

As a public resolver answered for parcmontbellevue.com. Looked up 2026-11-19 08:47 UTC · today

TypeRecords
A
AAAA None
NS
ns12.wixdns.net ns13.wixdns.net
MX
10 parcmontbellevue-com.mail.protection.outlook.com
SPF
v=spf1 include:spf.protection.outlook.com include:spfa.cpmails.com -all

Certificate Identity

Common Nameparcmontbellevue.com
Alt Names parcmontbellevue.com www.parcmontbellevue.com
IssuerCN=WR1, O=Google Trust Services, C=US
Validity 2025-10-14 to 2026-01-12 (310 days ago — expired)
KeyRSA 2048 bits (sha256RSA)
Serial Number00B03855207CBA47510E16E28BC9D11BB9
SHA256 Fingerprint f89a336366a8fbbccafd813015eed2f2ecc737c64dd3c52db34a533b0bfcc892
Pin SHA256/80wYYiIFf0MW+sKayoWaV1afzOjLHFaS1s/FGUfw0M=

Certificate Properties

Type DV Domain Validated
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) OCSP: http://o.pki.goog/s/wr1/sDg CRL: http://c.pki.goog/wr1/vG1jRk4SsDs.crl
DNS CAA No (missing)
Trusted By Not verified
Name Match Yes
Validity Period 90 days (maximum 398 days for certificates issued then)
Chain IssuesNone

Trust Chain Architecture

End-Entity Certificate
CN=parcmontbellevue.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 parcmontbellevue.com, first seen 2026-11-19; current certificate since 2026-11-19.

Certificates served

Certificate (SHA-256)IssuerValidServed
f89a336366a8fbbc… current WR12025-10-14 → 2026-01-122026-11-19

Addresses

AddressCertificateSeen
185.230.63.107 f89a336366a8fbbc… 2026-11-19
185.230.63.171 f89a336366a8fbbc… 2026-11-19
185.230.63.186 f89a336366a8fbbc… 2026-11-19

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-19 08:47FTLS 1.3 f89a336366a8fbbc… 185.230.63.107, 185.230.63.171, 185.230.63.186

Other hosts seen on the same addresses