SSL Report: as4.eu.9800089400002.gasops.equinor.com (4.208.83.34)
Assessed on:  Mon, 09 Jun 2025 13:56:28 UTC | Clear cache

Due to a recently discovered bug in Apple's code, your browser is exposed to MITM attacks. Click here for more information.

Summary
Overall Rating
T
If trust issues are ignored: A
0
20
40
60
80
100
Certificate
 
Protocol Support
 
Key Exchange
 
Cipher Strength
 

Visit our documentation page for more information, configuration guides, and books. Known issues are documented here.
This server's certificate is not trusted, see below for details.
This server's certificate is not trusted by major browsers. MORE INFO »
HTTP request to this server failed, see below for details.
This server supports TLS 1.3.  MORE INFO »
DNS Certification Authority Authorization (CAA) Policy found for this domain.  MORE INFO »
Certificate #1: EC 256 bits (SHA256withECDSA)
Server Key and Certificate #1
Subject 9800089400002.EMT.MAK-ASA
Fingerprint SHA256: 82b888fde1f9778dd1a8f6e317eb1a36f3545f9e47889d87ef5fdd802faf769e
Pin SHA256: ZXRh9Cc9IzSMcPrqfwTNGrfTYZU1Vgj8PU3LBLTIFhc=
Common names 9800089400002.EMT.MAK-ASA
Alternative names as4.eu.9800089400002.gasops.equinor.com
Serial Number 35a90ab4d8a0297d4efa3e203a95e048
Valid from Fri, 14 Mar 2025 09:04:20 UTC
Valid until Sun, 14 Mar 2027 23:59:59 UTC (expires in 1 year and 9 months)
Key EC 256 bits
Weak key (Debian) No
Issuer Schleupen-Smart-Metering-Sub.CA
Signature algorithm SHA256withECDSA
Extended Validation No
Certificate Transparency No
OCSP Must Staple No
Revocation information None
DNS CAA Yes
policy host: equinor.com
issue: digicert.com flags:0
Trusted No   NOT TRUSTED (Why?)
Mozilla  Apple  Android  Java  Windows 


Additional Certificates (if supplied)
Certificates provided 3 (3231 bytes)
Chain issues Contains anchor
#2
Subject Schleupen-Smart-Metering-Sub.CA
Fingerprint SHA256: 9889eec6871e7d4bb0984782660771061d917eed35057abbbfe6ea0c09f34a98
Pin SHA256: Lpo2qxKZ7WA5tqXMUTsIM7V3wVXZVQzmm4Rf+NB9pI8=
Valid until Mon, 24 Sep 2029 23:59:59 UTC (expires in 4 years and 3 months)
Key EC 256 bits
Issuer SM-Root.CA
Signature algorithm SHA384withECDSA
#3
Subject SM-Root.CA   Not in trust store
Fingerprint SHA256: b3579a8b774edc42cdc8d645c34c7ae0e5e1457fcf21c52a3fd4b23fa2fd0b95
Pin SHA256: 8u4048ZCkCr9Fk+O3xGLW7kSIBoX3WbW3I91jH+NlFQ=
Valid until Sat, 12 Oct 2030 23:59:59 UTC (expires in 5 years and 4 months)
Key EC 384 bits
Issuer SM-Root.CA   Self-signed
Signature algorithm SHA384withECDSA


Certification Paths
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server 9800089400002.EMT.MAK-ASA
Fingerprint SHA256: 82b888fde1f9778dd1a8f6e317eb1a36f3545f9e47889d87ef5fdd802faf769e
Pin SHA256: ZXRh9Cc9IzSMcPrqfwTNGrfTYZU1Vgj8PU3LBLTIFhc=

EC 256 bits / SHA256withECDSA
2 Sent by server Schleupen-Smart-Metering-Sub.CA
Fingerprint SHA256: 9889eec6871e7d4bb0984782660771061d917eed35057abbbfe6ea0c09f34a98
Pin SHA256: Lpo2qxKZ7WA5tqXMUTsIM7V3wVXZVQzmm4Rf+NB9pI8=

EC 256 bits / SHA384withECDSA
3 Sent by server
  Not in trust store
SM-Root.CA   Self-signed
Fingerprint SHA256: b3579a8b774edc42cdc8d645c34c7ae0e5e1457fcf21c52a3fd4b23fa2fd0b95
Pin SHA256: 8u4048ZCkCr9Fk+O3xGLW7kSIBoX3WbW3I91jH+NlFQ=

EC 384 bits / SHA384withECDSA
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server 9800089400002.EMT.MAK-ASA
Fingerprint SHA256: 82b888fde1f9778dd1a8f6e317eb1a36f3545f9e47889d87ef5fdd802faf769e
Pin SHA256: ZXRh9Cc9IzSMcPrqfwTNGrfTYZU1Vgj8PU3LBLTIFhc=

EC 256 bits / SHA256withECDSA
2 Sent by server Schleupen-Smart-Metering-Sub.CA
Fingerprint SHA256: 9889eec6871e7d4bb0984782660771061d917eed35057abbbfe6ea0c09f34a98
Pin SHA256: Lpo2qxKZ7WA5tqXMUTsIM7V3wVXZVQzmm4Rf+NB9pI8=

EC 256 bits / SHA384withECDSA
3 Sent by server
  Not in trust store
SM-Root.CA   Self-signed
Fingerprint SHA256: b3579a8b774edc42cdc8d645c34c7ae0e5e1457fcf21c52a3fd4b23fa2fd0b95
Pin SHA256: 8u4048ZCkCr9Fk+O3xGLW7kSIBoX3WbW3I91jH+NlFQ=

EC 384 bits / SHA384withECDSA
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server 9800089400002.EMT.MAK-ASA
Fingerprint SHA256: 82b888fde1f9778dd1a8f6e317eb1a36f3545f9e47889d87ef5fdd802faf769e
Pin SHA256: ZXRh9Cc9IzSMcPrqfwTNGrfTYZU1Vgj8PU3LBLTIFhc=

EC 256 bits / SHA256withECDSA
2 Sent by server Schleupen-Smart-Metering-Sub.CA
Fingerprint SHA256: 9889eec6871e7d4bb0984782660771061d917eed35057abbbfe6ea0c09f34a98
Pin SHA256: Lpo2qxKZ7WA5tqXMUTsIM7V3wVXZVQzmm4Rf+NB9pI8=

EC 256 bits / SHA384withECDSA
3 Sent by server
  Not in trust store
SM-Root.CA   Self-signed
Fingerprint SHA256: b3579a8b774edc42cdc8d645c34c7ae0e5e1457fcf21c52a3fd4b23fa2fd0b95
Pin SHA256: 8u4048ZCkCr9Fk+O3xGLW7kSIBoX3WbW3I91jH+NlFQ=

EC 384 bits / SHA384withECDSA
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server 9800089400002.EMT.MAK-ASA
Fingerprint SHA256: 82b888fde1f9778dd1a8f6e317eb1a36f3545f9e47889d87ef5fdd802faf769e
Pin SHA256: ZXRh9Cc9IzSMcPrqfwTNGrfTYZU1Vgj8PU3LBLTIFhc=

EC 256 bits / SHA256withECDSA
2 Sent by server Schleupen-Smart-Metering-Sub.CA
Fingerprint SHA256: 9889eec6871e7d4bb0984782660771061d917eed35057abbbfe6ea0c09f34a98
Pin SHA256: Lpo2qxKZ7WA5tqXMUTsIM7V3wVXZVQzmm4Rf+NB9pI8=

EC 256 bits / SHA384withECDSA
3 Sent by server
  Not in trust store
SM-Root.CA   Self-signed
Fingerprint SHA256: b3579a8b774edc42cdc8d645c34c7ae0e5e1457fcf21c52a3fd4b23fa2fd0b95
Pin SHA256: 8u4048ZCkCr9Fk+O3xGLW7kSIBoX3WbW3I91jH+NlFQ=

EC 384 bits / SHA384withECDSA
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server 9800089400002.EMT.MAK-ASA
Fingerprint SHA256: 82b888fde1f9778dd1a8f6e317eb1a36f3545f9e47889d87ef5fdd802faf769e
Pin SHA256: ZXRh9Cc9IzSMcPrqfwTNGrfTYZU1Vgj8PU3LBLTIFhc=

EC 256 bits / SHA256withECDSA
2 Sent by server Schleupen-Smart-Metering-Sub.CA
Fingerprint SHA256: 9889eec6871e7d4bb0984782660771061d917eed35057abbbfe6ea0c09f34a98
Pin SHA256: Lpo2qxKZ7WA5tqXMUTsIM7V3wVXZVQzmm4Rf+NB9pI8=

EC 256 bits / SHA384withECDSA
3 Sent by server
  Not in trust store
SM-Root.CA   Self-signed
Fingerprint SHA256: b3579a8b774edc42cdc8d645c34c7ae0e5e1457fcf21c52a3fd4b23fa2fd0b95
Pin SHA256: 8u4048ZCkCr9Fk+O3xGLW7kSIBoX3WbW3I91jH+NlFQ=

EC 384 bits / SHA384withECDSA

Click here to expand

Configuration
Protocols
TLS 1.3 Yes
TLS 1.2 No
TLS 1.1 No
TLS 1.0 No
SSL 3 No
SSL 2 No


Cipher Suites
# TLS 1.3 (server has no preference)
TLS_AES_128_GCM_SHA256 (0x1301)   ECDH secp256r1 (eq. 3072 bits RSA)   FS 128
TLS_AES_256_GCM_SHA384 (0x1302)   ECDH secp256r1 (eq. 3072 bits RSA)   FS 256
TLS_CHACHA20_POLY1305_SHA256 (0x1303)   ECDH secp256r1 (eq. 3072 bits RSA)   FS 256


Handshake Simulation
Android 8.1 -   TLS 1.3 TLS_CHACHA20_POLY1305_SHA256   ECDH secp256r1  FS
Android 9.0 -   TLS 1.3 TLS_CHACHA20_POLY1305_SHA256   ECDH secp256r1  FS
Chrome 69 / Win 7  R Server sent fatal alert: handshake_failure
Chrome 70 / Win 10 -   TLS 1.3 TLS_AES_128_GCM_SHA256   ECDH secp256r1  FS
Chrome 80 / Win 10  R -   TLS 1.3 TLS_AES_128_GCM_SHA256   ECDH secp256r1  FS
Firefox 62 / Win 7  R Server sent fatal alert: handshake_failure
Firefox 73 / Win 10  R -   TLS 1.3 TLS_AES_128_GCM_SHA256   ECDH secp256r1  FS
Java 11.0.3 -   TLS 1.3 TLS_AES_128_GCM_SHA256   ECDH secp256r1  FS
Java 12.0.1 -   TLS 1.3 TLS_AES_128_GCM_SHA256   ECDH secp256r1  FS
OpenSSL 1.1.0k  R Server sent fatal alert: handshake_failure
OpenSSL 1.1.1c  R -   TLS 1.3 TLS_AES_256_GCM_SHA384   ECDH secp256r1  FS
Safari 12.1.2 / MacOS 10.14.6 Beta  R -   TLS 1.3 TLS_CHACHA20_POLY1305_SHA256   ECDH secp256r1  FS
Safari 12.1.1 / iOS 12.3.1  R -   TLS 1.3 TLS_CHACHA20_POLY1305_SHA256   ECDH secp256r1  FS
# Not simulated clients (Protocol mismatch)
Android 2.3.7   No SNI 2 Protocol mismatch (not simulated)
Android 4.0.4 Protocol mismatch (not simulated)
Android 4.1.1 Protocol mismatch (not simulated)
Android 4.2.2 Protocol mismatch (not simulated)
Android 4.3 Protocol mismatch (not simulated)
Android 4.4.2 Protocol mismatch (not simulated)
Android 5.0.0 Protocol mismatch (not simulated)
Android 6.0 Protocol mismatch (not simulated)
Android 7.0 Protocol mismatch (not simulated)
Android 8.0 Protocol mismatch (not simulated)
Baidu Jan 2015 Protocol mismatch (not simulated)
BingPreview Jan 2015 Protocol mismatch (not simulated)
Chrome 49 / XP SP3 Protocol mismatch (not simulated)
Firefox 31.3.0 ESR / Win 7 Protocol mismatch (not simulated)
Firefox 47 / Win 7  R Protocol mismatch (not simulated)
Firefox 49 / XP SP3 Protocol mismatch (not simulated)
Googlebot Feb 2018 Protocol mismatch (not simulated)
IE 6 / XP   No FS 1   No SNI 2 Protocol mismatch (not simulated)
IE 7 / Vista Protocol mismatch (not simulated)
IE 8 / XP   No FS 1   No SNI 2 Protocol mismatch (not simulated)
IE 8-10 / Win 7  R Protocol mismatch (not simulated)
IE 11 / Win 7  R Protocol mismatch (not simulated)
IE 11 / Win 8.1  R Protocol mismatch (not simulated)
IE 10 / Win Phone 8.0 Protocol mismatch (not simulated)
IE 11 / Win Phone 8.1  R Protocol mismatch (not simulated)
IE 11 / Win Phone 8.1 Update  R Protocol mismatch (not simulated)
IE 11 / Win 10  R Protocol mismatch (not simulated)
Edge 15 / Win 10  R Protocol mismatch (not simulated)
Edge 16 / Win 10  R Protocol mismatch (not simulated)
Edge 18 / Win 10  R Protocol mismatch (not simulated)
Edge 13 / Win Phone 10  R Protocol mismatch (not simulated)
Java 6u45   No SNI 2 Protocol mismatch (not simulated)
Java 7u25 Protocol mismatch (not simulated)
Java 8u161 Protocol mismatch (not simulated)
OpenSSL 0.9.8y Protocol mismatch (not simulated)
OpenSSL 1.0.1l  R Protocol mismatch (not simulated)
OpenSSL 1.0.2s  R Protocol mismatch (not simulated)
Safari 5.1.9 / OS X 10.6.8 Protocol mismatch (not simulated)
Safari 6 / iOS 6.0.1 Protocol mismatch (not simulated)
Safari 6.0.4 / OS X 10.8.4  R Protocol mismatch (not simulated)
Safari 7 / iOS 7.1  R Protocol mismatch (not simulated)
Safari 7 / OS X 10.9  R Protocol mismatch (not simulated)
Safari 8 / iOS 8.4  R Protocol mismatch (not simulated)
Safari 8 / OS X 10.10  R Protocol mismatch (not simulated)
Safari 9 / iOS 9  R Protocol mismatch (not simulated)
Safari 9 / OS X 10.11  R Protocol mismatch (not simulated)
Safari 10 / iOS 10  R Protocol mismatch (not simulated)
Safari 10 / OS X 10.12  R Protocol mismatch (not simulated)
Apple ATS 9 / iOS 9  R Protocol mismatch (not simulated)
Yahoo Slurp Jan 2015 Protocol mismatch (not simulated)
YandexBot Jan 2015 Protocol mismatch (not simulated)

Click here to expand

(1) Clients that do not support Forward Secrecy (FS) are excluded when determining support for it.
(2) No support for virtual SSL hosting (SNI). Connects to the default site if the server uses SNI.
(3) Only first connection attempt simulated. Browsers sometimes retry with a lower protocol version.
(R) Denotes a reference browser or client, with which we expect better effective security.
(All) We use defaults, but some platforms do not use their best protocols and features (e.g., Java 6 & 7, older IE).
(All) Certificate trust is not checked in handshake simulation, we only perform TLS handshake.


Protocol Details
ROBOT (vulnerability) No (more info)
Forward Secrecy Yes (with most browsers)   ROBUST (more info)
ALPN No
Session resumption (tickets) No
OCSP stapling No
Strict Transport Security (HSTS) Unknown (failed HTTP request?)
HSTS Preloading Not in: Chrome  Edge  Firefox  IE 
Public Key Pinning (HPKP) Unknown (failed HTTP request?)
Public Key Pinning Report-Only Unknown (failed HTTP request?)
Public Key Pinning (Static) No (more info)
Supported Named Groups secp256r1, secp384r1, secp521r1, ffdhe2048, ffdhe3072 (server preferred order)
SSL 2 handshake compatibility No
0-RTT enabled No


HTTP Requests
1 https://as4.eu.9800089400002.gasops.equinor.com/  (Request failed)


Miscellaneous
Test date Mon, 09 Jun 2025 13:56:08 UTC
Test duration 20.883 seconds
HTTP status code Request failed
HTTP server signature Unknown
Server hostname -


Why is my certificate not trusted?

There are many reasons why a certificate may not be trusted. The exact problem is indicated on the report card in bright red. The problems fall into three categories:

  1. Invalid certificate
  2. Invalid configuration
  3. Unknown Certificate Authority

1. Invalid certificate

A certificate is invalid if:

2. Invalid configuration

In some cases, the certificate chain does not contain all the necessary certificates to connect the web server certificate to one of the root certificates in our trust store. Less commonly, one of the certificates in the chain (other than the web server certificate) will have expired, and that invalidates the entire chain.

3. Unknown Certificate Authority

In order for trust to be established, we must have the root certificate of the signing Certificate Authority in our trust store. SSL Labs does not maintain its own trust store; instead we use the store maintained by Mozilla.

If we mark a web site as not trusted, that means that the average web user's browser will not trust it either. For certain special groups of users, such web sites can still be secure. For example, if you can securely verify that a self-signed web site is operated by a person you trust, then you can trust that self-signed web site too. Or, if you work for an organisation that manages its own trust, and you have their own root certificate already embedded in your browser. Such special cases do not work for the general public, however, and this is what we indicate on our report card.

4. Interoperability issues

In some rare cases trust cannot be established because of interoperability issues between our code and the code or configuration running on the server. We manually review such cases, but if you encounter such an issue please feel free to contact us. Such problems are very difficult to troubleshoot and you may be able to provide us with information that might help us determine the root cause.

SSL Report v2.4.0