In DotNetBrowser 1.7 the Certificate Validation API has been introduced. Using this API you can get information about each SSL certificate used for displaying HTTPS web pages and decide whether it should be accepted or rejected. By default, Chromium engine decides whether certificate should be accepted/rejected. You can register your own CertificateVerifier implementation to modify default behavior. For example:

using DotNetBrowser;
using DotNetBrowser.WPF;
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Windows;

namespace CertificateVerifierSample
    /// <summary>
    /// The sample demonstrates how to accept/reject SSL certificates using
    /// custom SSL certificate verifier.
    /// </summary>
    public class WindowMain : Window
        private WPFBrowserView browserView;

        class TestCertificateVerifier : CertificateVerifier
            public CertificateVerifyResult Verify(CertificateVerifyParams parameters)
                // Reject SSL certificate for all "" hosts.
                if (parameters.HostName.Contains(""))
                    return CertificateVerifyResult.INVALID;
                return CertificateVerifyResult.OK;

        public WindowMain()
            BrowserContext browserContext = BrowserContext.DefaultContext;
            Browser browser = BrowserFactory.Create(browserContext);

            //add custom request handler
            browser.Context.NetworkService.CertificateVerifier = new TestCertificateVerifier();

            browserView = new WPFBrowserView(browser);
            Content = browserView;

            Width = 1024;
            Height = 768;
            this.Loaded += WindowMain_Loaded;

        void WindowMain_Loaded(object sender, RoutedEventArgs e)

        public static void Main()
            Application app = new Application();

            WindowMain wnd = new WindowMain();

            var browser = wnd.browserView.Browser;