React Native Requires Chilkat v11.0.0+

Examine SSL/TLS Server Certificate

See more Socket/SSL/TLS Examples

Demonstrates how an application can examine and check a server's SSL/TLS certificate. React Native

import { Cert, Socket } from '@chilkat/react-native'

async function chilkatExample() {
  // This example assumes the Chilkat API to have been previously unlocked.
  // See Global Unlock Sample for sample code.

  const socket = new Socket();

  // Connect to a server.
  const useTls = true;
  const maxWaitMs = 2000;
  try {
    await socket.connectAsync('www.intel.com', 443, useTls, maxWaitMs);
  } catch {
    console.log(socket.lastErrorText);
    return;
  }

  // If we get here, the TLS connection ws made..
  // In any SSL/TLS handshake, the server sends its certificate in a TLS handshake message.
  // Chilkat will keep it cached within the object that made the connection.
  // Get the server's cert and examine a few things.
  const cert = new Cert();
  socket.getServerCert(cert);

  console.log(`Distinguished Name: ${cert.subjectDN}`);
  console.log(`Common Name: ${cert.subjectCN}`);
  console.log(`Issuer Distinguished Name: ${cert.issuerDN}`);
  console.log(`Issuer Common Name: ${cert.issuerCN}`);

  console.log(`Expired: ${cert.expired}`);
  console.log(`Revoked: ${cert.revoked}`);
  console.log(`Signature Verified: ${cert.signatureVerified}`);
  console.log(`Trusted Root: ${cert.trustedRoot}`);

  // Sample output:

  // Distinguished Name: C=US, ST=California, O=Intel Corporation, CN=*.intel.com
  // Common Name: *.intel.com
  // Issuer Distinguished Name: C=GB, ST=Greater Manchester, L=Salford, O=Sectigo Limited, CN=Sectigo RSA Organization Validation Secure Server CA
  // Issuer Common Name: Sectigo RSA Organization Validation Secure Server CA
  // Expired: False
  // Revoked: False
  // Signature Verified: True
  // Trusted Root: True
}