SSL Report: admindocs.ap8.netsuite.com (140.238.243.12)
Assessed on:  Mon, 16 Jun 2025 00:23:11 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: B
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 chain is incomplete. Grade capped to B.
This site works only in browsers with SNI support.
This server supports TLS 1.3.  MORE INFO »
HTTP Strict Transport Security (HSTS) with long duration deployed on this server.  MORE INFO »
DNS Certification Authority Authorization (CAA) Policy found for this domain.  MORE INFO »
Certificate #1: EC 256 bits (SHA512withRSA)
Server Key and Certificate #1
Subject Admindocs-AP8-Prod
Fingerprint SHA256: 70469a011065388cafbc834d38c9cf3665f36478f25b842eeb123c48c2575cc1
Pin SHA256: 6lpKeFWQ/RITzLDM22eRw+hwzlZXeDs4V4F5A6p3IDw=
Common names Admindocs-AP8-Prod
Alternative names BanyanService admindocs.ap8.netsuite.com
Serial Number 71ed1e8144fe5bd05de395157e7260901e62181e
Valid from Sun, 15 Jun 2025 08:54:00 UTC
Valid until Mon, 15 Jun 2026 08:54:00 UTC (expires in 11 months and 30 days)
Key EC 256 bits
Weak key (Debian) No
Issuer nsgbu-prod Banyan Private Root CA
Signature algorithm SHA512withRSA
Extended Validation No
Certificate Transparency No
OCSP Must Staple No
Revocation information None
DNS CAA Yes
policy host: netsuite.com
issue: digicert.com flags:0
issue: letsencrypt.org flags:0
Trusted No   NOT TRUSTED (Why?)
Mozilla  Apple  Android  Java  Windows 


Additional Certificates (if supplied)
Certificates provided 1 (1146 bytes)
Chain issues Incomplete


Certification Paths
No trust paths available
Issuer unknown, or intermediate certificate(s) missing.
No trust paths available
Issuer unknown, or intermediate certificate(s) missing.
No trust paths available
Issuer unknown, or intermediate certificate(s) missing.
No trust paths available
Issuer unknown, or intermediate certificate(s) missing.
No trust paths available
Issuer unknown, or intermediate certificate(s) missing.

Click here to expand

Certificate #2: EC 256 bits (SHA512withRSA)
Server Key and Certificate #1
Subject Admindocs-AP8-Prod
Fingerprint SHA256: 8d2632df670ed5c41bff17a01c35d0046ebbbea0e4a2cff3896eb644bcacb353
Pin SHA256: UrDNb8s6uT3sWN8nyWPhlYW4NyxztJAhINEC+xNI8fA=
Common names Admindocs-AP8-Prod
Alternative names BanyanService admindocs.ap8.netsuite.com
Serial Number 773366bf794576ff7f883d9659ee51f3f2ac329d
Valid from Sun, 15 Jun 2025 09:16:00 UTC
Valid until Mon, 15 Jun 2026 09:16:00 UTC (expires in 11 months and 30 days)
Key EC 256 bits
Weak key (Debian) No
Issuer nsgbu-prod Banyan Private Root CA
Signature algorithm SHA512withRSA
Extended Validation No
Certificate Transparency No
OCSP Must Staple No
Revocation information None
DNS CAA Yes
policy host: netsuite.com
issue: digicert.com flags:0
issue: letsencrypt.org flags:0
Trusted No   NOT TRUSTED (Why?)
Mozilla  Apple  Android  Java  Windows 


Additional Certificates (if supplied)
Certificates provided 1 (1146 bytes)
Chain issues Incomplete


Certification Paths
No trust paths available
Issuer unknown, or intermediate certificate(s) missing.
No trust paths available
Issuer unknown, or intermediate certificate(s) missing.
No trust paths available
Issuer unknown, or intermediate certificate(s) missing.
No trust paths available
Issuer unknown, or intermediate certificate(s) missing.
No trust paths available
Issuer unknown, or intermediate certificate(s) missing.

Click here to expand

Certificate #3: EC 256 bits (SHA512withRSA)
Server Key and Certificate #1
Subject Admindocs-AP8-Prod
Fingerprint SHA256: a08f9b7e7770bc5f89545f908064859b0ef5006f1f9bb9e068d0983090197103
Pin SHA256: s/IVQhfv1ZsPBBITnhuc9CNbBLbK/cqrADfDBffeVbQ=
Common names Admindocs-AP8-Prod
Alternative names BanyanService admindocs.ap8.netsuite.com
Serial Number 2ed794c0bf17096de28a015c908993051fac3579
Valid from Sun, 15 Jun 2025 08:58:00 UTC
Valid until Mon, 15 Jun 2026 08:58:00 UTC (expires in 11 months and 30 days)
Key EC 256 bits
Weak key (Debian) No
Issuer nsgbu-prod Banyan Private Root CA
Signature algorithm SHA512withRSA
Extended Validation No
Certificate Transparency No
OCSP Must Staple No
Revocation information None
DNS CAA Yes
policy host: netsuite.com
issue: digicert.com flags:0
issue: letsencrypt.org flags:0
Trusted No   NOT TRUSTED (Why?)
Mozilla  Apple  Android  Java  Windows 


Additional Certificates (if supplied)
Certificates provided 1 (1146 bytes)
Chain issues Incomplete


Certification Paths
No trust paths available
Issuer unknown, or intermediate certificate(s) missing.
No trust paths available
Issuer unknown, or intermediate certificate(s) missing.
No trust paths available
Issuer unknown, or intermediate certificate(s) missing.
No trust paths available
Issuer unknown, or intermediate certificate(s) missing.
No trust paths available
Issuer unknown, or intermediate certificate(s) missing.

Click here to expand

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


Cipher Suites
# TLS 1.3 (suites in server-preferred order)
TLS_AES_128_GCM_SHA256 (0x1301)   ECDH x25519 (eq. 3072 bits RSA)   FS 128
TLS_AES_256_GCM_SHA384 (0x1302)   ECDH x25519 (eq. 3072 bits RSA)   FS 256
TLS_CHACHA20_POLY1305_SHA256 (0x1303)   ECDH x25519 (eq. 3072 bits RSA)   FS 256P
# TLS 1.2 (suites in server-preferred order)
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (0xc02b)   ECDH secp521r1 (eq. 15360 bits RSA)   FS 128
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (0xc02c)   ECDH secp521r1 (eq. 15360 bits RSA)   FS 256
(P) This server prefers ChaCha20 suites with clients that don't have AES-NI (e.g., Android devices)


Handshake Simulation
Android 4.4.2 EC 256 (SHA512)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH secp521r1  FS
Android 5.0.0 EC 256 (SHA512)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH secp521r1  FS
Android 6.0 EC 256 (SHA512)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
Android 7.0 EC 256 (SHA512)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH x25519  FS
Android 8.0 EC 256 (SHA512)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH x25519  FS
Android 8.1 -   TLS 1.3 TLS_CHACHA20_POLY1305_SHA256   ECDH x25519  FS
Android 9.0 -   TLS 1.3 TLS_CHACHA20_POLY1305_SHA256   ECDH x25519  FS
BingPreview Jan 2015 EC 256 (SHA512)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH secp521r1  FS
Chrome 49 / XP SP3 Server sent fatal alert: handshake_failure
Chrome 69 / Win 7  R EC 256 (SHA512)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH x25519  FS
Chrome 70 / Win 10 -   TLS 1.3 TLS_AES_128_GCM_SHA256   ECDH x25519  FS
Chrome 80 / Win 10  R -   TLS 1.3 TLS_AES_128_GCM_SHA256   ECDH x25519  FS
Firefox 31.3.0 ESR / Win 7 EC 256 (SHA512)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
Firefox 47 / Win 7  R EC 256 (SHA512)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
Firefox 49 / XP SP3 EC 256 (SHA512)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
Firefox 62 / Win 7  R EC 256 (SHA512)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH x25519  FS
Firefox 73 / Win 10  R -   TLS 1.3 TLS_AES_128_GCM_SHA256   ECDH x25519  FS
Googlebot Feb 2018 EC 256 (SHA512)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH x25519  FS
IE 11 / Win 7  R EC 256 (SHA512)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
IE 11 / Win 8.1  R EC 256 (SHA512)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
IE 11 / Win Phone 8.1  R EC 256 (SHA512)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
IE 11 / Win Phone 8.1 Update  R EC 256 (SHA512)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
IE 11 / Win 10  R EC 256 (SHA512)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
Edge 15 / Win 10  R EC 256 (SHA512)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH x25519  FS
Edge 16 / Win 10  R EC 256 (SHA512)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH x25519  FS
Edge 18 / Win 10  R EC 256 (SHA512)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH x25519  FS
Edge 13 / Win Phone 10  R EC 256 (SHA512)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
Java 8u161 EC 256 (SHA512)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_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.0.1l  R EC 256 (SHA512)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH secp521r1  FS
OpenSSL 1.0.2s  R EC 256 (SHA512)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
OpenSSL 1.1.0k  R EC 256 (SHA512)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH x25519  FS
OpenSSL 1.1.1c  R -   TLS 1.3 TLS_AES_128_GCM_SHA256   ECDH x25519  FS
Safari 6 / iOS 6.0.1 Server sent fatal alert: handshake_failure
Safari 7 / iOS 7.1  R Server sent fatal alert: handshake_failure
Safari 7 / OS X 10.9  R Server sent fatal alert: handshake_failure
Safari 8 / iOS 8.4  R Server sent fatal alert: handshake_failure
Safari 8 / OS X 10.10  R Server sent fatal alert: handshake_failure
Safari 9 / iOS 9  R EC 256 (SHA512)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
Safari 9 / OS X 10.11  R EC 256 (SHA512)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
Safari 10 / iOS 10  R EC 256 (SHA512)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
Safari 10 / OS X 10.12  R EC 256 (SHA512)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
Safari 12.1.2 / MacOS 10.14.6 Beta  R -   TLS 1.3 TLS_CHACHA20_POLY1305_SHA256   ECDH x25519  FS
Safari 12.1.1 / iOS 12.3.1  R -   TLS 1.3 TLS_CHACHA20_POLY1305_SHA256   ECDH x25519  FS
Apple ATS 9 / iOS 9  R EC 256 (SHA512)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
Yahoo Slurp Jan 2015 EC 256 (SHA512)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH secp384r1  FS
YandexBot Jan 2015 EC 256 (SHA512)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH secp521r1  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)
Baidu Jan 2015 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 10 / Win Phone 8.0 Protocol mismatch (not simulated)
Java 6u45   No SNI 2 Protocol mismatch (not simulated)
Java 7u25 Protocol mismatch (not simulated)
OpenSSL 0.9.8y Protocol mismatch (not simulated)
Safari 5.1.9 / OS X 10.6.8 Protocol mismatch (not simulated)
Safari 6.0.4 / OS X 10.8.4  R 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
Secure Renegotiation Supported
Secure Client-Initiated Renegotiation No
Insecure Client-Initiated Renegotiation No
BEAST attack Mitigated server-side (more info)  
POODLE (SSLv3) No, SSL 3 not supported (more info)
POODLE (TLS) No (more info)
Zombie POODLE No (more info)  
GOLDENDOODLE No (more info)  
OpenSSL 0-Length No (more info)  
Sleeping POODLE No (more info)  
Downgrade attack prevention Yes, TLS_FALLBACK_SCSV supported (more info)
SSL/TLS compression No
RC4 No
Heartbeat (extension) No
Heartbleed (vulnerability) No (more info)
Ticketbleed (vulnerability) No (more info)
OpenSSL CCS vuln. (CVE-2014-0224) No (more info)
OpenSSL Padding Oracle vuln.
(CVE-2016-2107)
No (more info)
ROBOT (vulnerability) No (more info)
Forward Secrecy Yes (with most browsers)   ROBUST (more info)
ALPN No
NPN No
Session resumption (caching) No (IDs empty)
Session resumption (tickets) No
OCSP stapling No
Strict Transport Security (HSTS) Yes
max-age=31536000
HSTS Preloading Not in: Chrome  Edge  Firefox  IE 
Public Key Pinning (HPKP) No (more info)
Public Key Pinning Report-Only No
Public Key Pinning (Static) No (more info)
Long handshake intolerance No
TLS extension intolerance No
TLS version intolerance No
Incorrect SNI alerts No
Uses common DH primes No, DHE suites not supported
DH public server param (Ys) reuse No, DHE suites not supported
ECDH public server param reuse No
Supported Named Groups secp256r1, secp384r1, secp521r1, x25519 (Server has no preference)
SSL 2 handshake compatibility No
0-RTT enabled No


HTTP Requests
1 https://admindocs.ap8.netsuite.com/  (HTTP/1.1 302 Found)
1
Cache-Control no-cache, no-store, max-age=0, must-revalidate
Content-Type text/html; charset=utf-8
Location https://nsgbu-prod.trust-oracle.banyanops.com/v2/auth?client_id=kOXV60O6eXhPyGUzb3oX8Q&nonce=NnccjZ4xikVIUHxjiUVJ5&redirect_uri=https%3A%2F%2Fadmindocs.ap8.netsuite.com%2Fbnn_trust_cb&response_type=code&scope=openid+profile+email&state=L19Q7-Ax1bQkEgrdU8r4Rw
Set-Cookie bnn_nonce_NnccjZ4xikVIUHxjiUVJ5L19Q7-Ax1bQkEgrdU8r4Rw=B0EdwP0HsBb7TCVgwkpUrcO5b4btgwlkVDcea6Gnd_rLwVPFZ4I7Z930h75jMAkSE1RCiNf2WSUnvgGfVnPLoQ; Path=/; Expires=Mon, 16 Jun 2025 00:37:04 GMT; HttpOnly; Secure
Set-Cookie bnn_return_NnccjZ4xikVIUHxjiUVJ5L19Q7-Ax1bQkEgrdU8r4Rw=; Path=/; Max-Age=0; HttpOnly; Secure
Strict-Transport-Security max-age=31536000
Date Mon, 16 Jun 2025 00:22:04 GMT
Content-Length 301
Connection close


Miscellaneous
Test date Mon, 16 Jun 2025 00:21:28 UTC
Test duration 102.802 seconds
HTTP status code 302
HTTP forwarding https://nsgbu-prod.trust-oracle.banyanops.com
HTTP server signature -
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