SSL Check WHOIS
Dashboard / Security Report

shai.se

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

Robust Security

Overall Rating
51.120.88.55 · WHOIS ›
Assessed 2026-11-17 05:33 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)
shai.se301 → https://shai.se/ → 200 OK200 OK
www.shai.se301 → https://shai.se/ → 200 OK301 → https://shai.se/ → 200 OK
  • http://shai.se redirects to HTTPS.

DNS Records

As a public resolver answered for shai.se. Looked up 2026-11-17 05:33 UTC · today

TypeRecords
A
AAAA None
NS
ns01.no.brand.one.com ns02.no.brand.one.com
MX
10 shai-se.mail.protection.outlook.com
SPF
v=spf1 include:_spf.createsend.com include:spf.protection.outlook.com include:helpscoutemail.com -all

Certificate Identity

Common Nameshai.se
Alt Names dizolve.no dizolve.se duktigvovve.se flinkbisk.no pace6.se shai.no shai.se www.dizolve.no www.dizolve.se www.duktigvovve.se www.flinkbisk.no www.pace6.se www.shai.no www.shai.se
IssuerCN=YR2, O=Let's Encrypt, C=US
Validity 2026-11-02 to 2027-01-31 (75 days remaining)
KeyRSA 3072 bits (sha256RSA)
Serial Number051C1962F10EBE7D58166895514E81B2FDAB
SHA256 Fingerprint 175f367b6b0c83be09f2c463d7daf4e0b809b58199853e4dee94742ac9e0ec58
Pin SHA2561XUlawxCpxWaGwFTMihCIxdPfdXqT/TVbVr0zU+lDgs=

Certificate Properties

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

Protocol Details

Connection
ALPN h2 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 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.2 (server-preferred order)
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3840xC030ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA2560xC02FECDHEFS128Secure
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA3840xC028ECDHEFS256Weak
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA2560xC027ECDHEFS128Weak
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA0xC014ECDHEFS256Weak
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA0xC013ECDHEFS128Weak

Handshake Simulation

ClientProtocolCipher SuiteResult
Chrome 120 / Win 11TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Chrome 80 / Win 10TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Firefox 115 / Win 10TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
iOS 17 / SafariTLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
macOS 14 / SafariTLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Android 14TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 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=dizolve.no (Issuer: CN=YR2, O=Let's Encrypt, C=US)
Intermediate CA
CN=YR2, 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 shai.se, first seen 2026-11-17; current certificate since 2026-11-17.

Certificates served

Certificate (SHA-256)IssuerValidServed
175f367b6b0c83be… current YR22026-11-02 → 2027-01-312026-11-17

Addresses

AddressCertificateSeen
51.120.88.55 175f367b6b0c83be… 2026-11-17

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-17 05:33ATLS 1.2 175f367b6b0c83be… 51.120.88.55

Other domains on the same certificate

Other hosts seen on the same addresses