SSL Check WHOIS
Dashboard / Security Report

we-store.com

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

Robust Security

Overall Rating
3.214.141.188 · WHOIS ›
Assessed 2026-11-19 08:14 UTC

Grade Breakdown

Protocol Support 90%
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)
we-store.com301 → https://we-store.com/ → … → https://www.we-store.com/ → 200 OK301 → https://www.we-store.com/ → 200 OK
www.we-store.com308 → https://www.we-store.com/ → 200 OK200 OK
  • http://we-store.com redirects to HTTPS.

DNS Records

As a public resolver answered for we-store.com. Looked up 2026-11-19 08:14 UTC · today

TypeRecords
A
AAAA None
NS
ns-cloud-d1.googledomains.com ns-cloud-d2.googledomains.com ns-cloud-d3.googledomains.com ns-cloud-d4.googledomains.com
MX
1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com
SPF
v=spf1 include:_spf.google.com ~all

Certificate Identity

Common Namewe-store.com
Alt Names m.we-store.com we-store.com
IssuerCN=YR1, O=Let's Encrypt, C=US
Validity 2026-11-11 to 2027-02-09 (82 days remaining)
KeyRSA 2048 bits (sha256RSA)
Serial Number0582450335862B8F6018730222E32842B4D6
SHA256 Fingerprint 14f9c362b4fe009c2b86d0ac9cd82cf0d0b32d706ad3a9677cef49a523b4ced5
Pin SHA256bVIjndCtOAoPSfRzaqW2dOZm+Ey5NOjEj+GOqaIC8FE=

Certificate Properties

Type DV Domain Validated
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) CRL: http://yr1.c.lencr.org/87.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_ECDHE_RSA_WITH_AES_128_GCM_SHA256

Protocol Details

Connection
ALPN http/1.1
SNI Required Yes
Supported Named Groups secp256r1 (inferred)
Post-Quantum Key Exchange No (no hybrid ML-KEM group such as 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 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.2 (server-preferred order)
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA2560xC02FECDHEFS128Secure
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3840xC030ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA2560xCCA8ECDHEFS256Secure

Handshake Simulation

ClientProtocolCipher SuiteResult
Chrome 120 / Win 11TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
Chrome 80 / Win 10TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
Firefox 115 / Win 10TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
iOS 17 / SafariTLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
macOS 14 / SafariTLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
Android 14TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
Chrome 69 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
Chrome 49 / XP SP3TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
IE 11 / Win 10TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
IE 11 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
Android 9.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
Android 7.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
Android 5.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
Android 4.4.2TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
Java 11TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
Java 8u121TLS 1.2TLS_ECDHE_RSA_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=we-store.com (Issuer: CN=YR1, O=Let's Encrypt, C=US)
Intermediate CA
CN=YR1, O=Let's Encrypt, C=US (Issuer: CN=Root YR, O=ISRG, C=US)
Intermediate CA
CN=Root YR, O=ISRG, C=US (Issuer: CN=ISRG Root X1, O=Internet Security Research Group, C=US)
Root Certificate
CN=ISRG Root X1, O=Internet Security Research Group, C=US (Issuer: CN=ISRG Root X1, O=Internet Security Research Group, C=US)

TLS History & Relations

Everything our scans have seen for we-store.com, first seen 2026-11-19; current certificate since 2026-11-19.

Certificates served

Certificate (SHA-256)IssuerValidServed
14f9c362b4fe009c… current YR12026-11-11 → 2027-02-092026-11-19

Addresses

AddressCertificateSeen
3.214.141.188 14f9c362b4fe009c… 2026-11-19

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-19 08:14ATLS 1.2 14f9c362b4fe009c… 3.214.141.188