When browsing the web in Silo for Research, you may occasionally encounter a full-page Chromium warning such as: "This site doesn't support a secure connection" or “Your connection is not private”



Below shows an error code like NET::ERR_CERT_INVALID, NET::ERR_CERT_AUTHORITY_INVALID, or NET::ERR_CERT_DATE_INVALID



The warnings do not apply exclusively to Silo. In many Chromium-based browsers, this warning includes an Advanced option with a “Proceed anyway” link. In some cases, that option is not shown at all. This article explains how and why typing thisisunsafe can allow you to continue with the addition of risk details of using Silo for Research when compared to a local browser.



Step-by-step: Using thisisunsafe in Silo for Research

Remain on the warning page, ensure you are on the full-page “Your connection is not private” screen.
  1. Click once anywhere on the page
    This ensures the Silo browser window has focus.
  2. Type: thisisunsafe
    • Do not type it into the address bar
    • Do not include spaces
    • No characters will appear on screen
  3. Wait briefly and if permitted, the page will load immediately after typing the final character.
This action applies only to that browsing session and site.



What is thisisunsafe

Chromium includes a built-in, undocumented “security interstitial bypass keyword” that triggers the same action as clicking Proceed anyway, even when the UI option is hidden. The keyword most commonly used today is: thisisunsafe

This behavior is widely referenced in Chromium troubleshooting discussions and aligns with Chromium’s internal handling of SSL interstitial bypass logic.



Warning Reasons

Certificate warnings occur when the browser cannot validate the website’s TLS/SSL certificate. Common causes include:
  • Self-signed certificates (common in test, lab, or internal systems)
  • Expired certificates
  • Hostname mismatches
  • Missing or untrusted certificate authorities
Chromium may remove the “Proceed anyway” option entirely when:
  • The site enforces HTTP Strict Transport Security (HSTS), which tells browsers to never ignore certificate errors for that domain
  • Browser or enterprise policy restricts SSL error overrides
Google documents both HSTS behavior and enterprise controls that can prevent users from clicking through certificate errors.



If Bypass Does Not Work

If typing thisisunsafe has no effect, one or more of the following may apply:

  • Stricter Chromium or policy-level blocking is in effect, preventing all SSL overrides
  • The warning is not a standard certificate interstitial (some network or security blocks are not bypassable)
  • The browser window does not have focus when typing

In these cases, the recommended approach is to address the root cause:

  • Confirm whether the site uses HSTS and, therefore, intentionally disallows overrides
  • Validate whether the certificate can be corrected (for example, by installing a proper certificate chain in the test environment)
  • For repeated access, work with the site owner to deploy a valid certificate rather than relying on bypasses



When is it appropriate to use in Silo

Using thisisunsafe in Silo for Research is most appropriate when:
  • You are researching or investigating a known or intentionally misconfigured site
  • You expect certificate issues (malware infrastructure, phishing sites, lab systems, or takedown-related content)
  • You need to observe or analyze the site, not trust it
Because Silo isolates the browsing activity from your endpoint, this method is commonly used by analysts and researchers to continue investigations while maintaining strong local security boundaries. However, even within Silo, avoid entering real credentials or sensitive personal information on sites with certificate errors unless explicitly required and approved for your research workflow.



Isolation and Risk Model

In a traditional local browser, bypassing a certificate warning exposes your endpoint, network, and identity to potential risks such as interception, malware delivery, or credential theft.
Silo for Research operates differently:
  • Browsing occurs inside an isolated container running in Authentic8’s cloud infrastructure
  • Web content never executes directly on your local workstation
  • Downloads, scripts, and page activity are contained within the Silo environment
  • Your local device, network, and IP address are not directly exposed to the site
Because of this architecture, the endpoint risk of simply viewing a site is significantly reduced compared to clicking through the same warning in a standard desktop browser. That said, certificate warnings still indicate that the site’s identity cannot be cryptographically verified. Even in an isolated environment, users should remain cautious when entering credentials or interacting with sensitive workflows.


Key Takeaway

thisisunsafe is a Chromium-supported bypass mechanism used when the Proceed anyway option is unavailable. In Silo for Research, architectural isolation significantly reduces endpoint risk, making its use acceptable for investigation and analysis, subject to informed judgment regarding site trust and interaction.



Additional Reference


Please contact Support for any additional questions