badssl.com

:lock: Memorable site for testing clients against bad SSL configs. (by chromium)

Badssl.com Alternatives

Similar projects and alternatives to badssl.com

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better badssl.com alternative or higher similarity.

badssl.com reviews and mentions

Posts with mentions or reviews of badssl.com. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-03-02.
  • Badssl.com
    2 projects | news.ycombinator.com | 2 Mar 2024
  • Netsec területen jártas arcok, mi a véleményetek az alábbi LifeProTip-ről?
    2 projects | /r/askhungary | 30 Jun 2023
  • Please Someone give me some website links that say "The site ahead contains harmful programs" or "the site ahead contains malware" on a red screen. Give the direct links. And if you can "the site ahead may charge you money".
    1 project | /r/chrome | 25 Jun 2023
    Probably to demo it? I wish Google had "this link will always be considered harmful", like the stuff on https://badssl.com/.
  • Intune Management ADMX
    3 projects | /r/brave_browser | 21 Feb 2023
    With SSLVersionMin, I think TLS 1.0 and TLS 1.1 protocols are already disabled (they were originally going to be disabled in 2020, but it was postponed). If I try going to test pages on https://badssl.com/ that use those protocols, Brave displays an "Unsupported protocol" error page with error code ERR_SSL_VERSION_OR_CIPHER_MISMATCH – with no option for the user to bypass the error page. However, I'm not sure why InTune won't allow you to configure it to TLS 1.2 minimum version anyway.
  • is using a private dns safe ?
    1 project | /r/ask | 19 Feb 2023
    See https://badssl.com/, or for a simple example of what happen when you access a page redirected by naughty DNS, set your private DNS to family.adguard-dns.com, then try opening PornHub.
  • Ignore Certificate Errors
    2 projects | /r/PowerShell | 8 Feb 2023
    .DESCRIPTION This cmdlet tests a URI for connectivity, and checks whether the TLS certificate is valid, expired, expiring soon, and returns information about the certificate when used with InformationLevel 'Detailed'. .PARAMETER Uri Specifies an HTTP/HTTPS URI. For example, https://www.powershellgallery.com .PARAMETER InformationLevel Specifies whether to return detailed information, or a simple $true or $false. .EXAMPLE Test-Uri https://badssl.com/ Returns a detailed TestUriResult with an IsTrusted property value of $true under normal circumstances. .EXAMPLE Test-Uri https://badssl.com/ -InformationLevel Quiet Returns a value of $true under normal circumstances. .EXAMPLE Test-Uri https://expired.badssl.com/ Returns a detailed TestUriResult with an IsExpired property value of $true .EXAMPLE Test-Uri https://expired.badssl.com/ Returns a detailed TestUriResult with an IsExpired property value of $true .EXAMPLE Test-Uri https://tls-v1-1.badssl.com:1011/ -SslProtocol Tls11 Returns a detailed TestUriResult where IsTrusted and UriTestSucceeded are $true, because we've specified to use SslProtocol Tls11. .EXAMPLE Test-Uri https://tls-v1-1.badssl.com:1011/ Returns a detailed TestUriResult where IsTrusted and UriTestSucceeded are $false, because only Tls12 and Tls13 are trusted by default. #> [CmdletBinding()] param ( [Parameter(Mandatory, ValueFromPipeline, ValueFromPipelineByPropertyName, Position = 0)] [uri[]] $Uri, [Parameter()] [System.Security.Authentication.SslProtocols[]] $SslProtocol = @([System.Security.Authentication.SslProtocols]::Tls12, [System.Security.Authentication.SslProtocols]::Tls13), [Parameter()] [ValidateSet('Detailed', 'Quiet')] [string] $InformationLevel = 'Detailed' ) process { [System.Security.Authentication.SslProtocols]$trustedProtocols = 0 $SslProtocol | Foreach-Object { $trustedProtocols = $trustedProtocols -bor $_ } foreach ($address in $Uri) { $result = [pscustomobject]@{ PSTypeName = 'TestUriResult' Uri = $address RemoteAddress = $null RemotePort = $null SourceAddress = $null RemoteCertificate = $null CipherAlgorithm = $null HashAlgorithm = $null SslProtocol = $null TcpTestSucceeded = $false UriTestSucceeded = $false IsExpired = $false IsExpiring = $false IsTrusted = $false } try { $tcpClient = [net.sockets.tcpclient]::new($address.Host, $address.Port) $result.TcpTestSucceeded = $true $result.RemoteAddress = $tcpClient.Client.RemoteEndPoint.Address $result.RemotePort = $tcpClient.Client.RemoteEndPoint.Port $result.SourceAddress = $tcpclient.Client.LocalEndPoint.Address if ($address.Scheme -eq 'https') { $stream = $tcpClient.GetStream() $sslStream = [net.security.sslstream]::new($stream, $false, { $true }) $protocols = 0; [enum]::GetValues([System.Security.Authentication.SslProtocols]) | Where-Object { $_ -match '(Ssl|Tls)' } | Foreach-Object { $protocols = $protocols -bor $_ } $sslStream.AuthenticateAsClient($address.Host, $null, $protocols, $true) $certInfo = [security.cryptography.x509certificates.x509certificate2]::new($sslStream.RemoteCertificate) $result.SslProtocol = $sslStream.SslProtocol $result.RemoteCertificate = $certInfo $result.CipherAlgorithm = $sslStream.CipherAlgorithm $result.HashAlgorithm = $sslStream.HashAlgorithm $result.IsExpired = $certInfo.NotAfter -le (Get-Date) $result.IsExpiring = $certInfo.NotAfter -le (Get-Date).AddDays(30) $result.IsTrusted = $certInfo.Verify() -and ($sslStream.SslProtocol -band $trustedProtocols) $result.UriTestSucceeded = $result.IsTrusted -and !$result.IsExpired -and ($sslStream.SslProtocol -band $trustedProtocols) if (-not ($sslStream.SslProtocol -band $trustedProtocols)) { Write-Warning "The transport layer security protocol $($sslStream.SslProtocol) is not in the list of trusted protocols: $trustedProtocols." } if ($result.IsExpired) { Write-Warning "Certificate for '$address' is expired. Subject='$($result.RemoteCertificate.Subject)'; NotAfter='$($result.RemoteCertificate.NotAfter.ToString('o'))'" } elseif ($result.IsExpiring) { Write-Warning "Certificate for '$address' expires in 30 days or less. Subject='$($result.RemoteCertificate.Subject)'; NotAfter='$($result.RemoteCertificate.NotAfter.ToString('o'))'" } } } catch { Write-Error -ErrorRecord $_ } finally { if ($sslStream) { $sslStream.Dispose() } if ($stream) { $stream.Dispose() } if ($tcpClient) { $tcpClient.Dispose() } } if ($InformationLevel -eq 'Quiet') { $result.UriTestSucceeded } else { $result } } }
  • How Does VPN Protect for Man-in-the-Middle?
    2 projects | /r/VPN | 7 Feb 2023
    Just use https://badssl.com/ to test the various errors.
  • hello guys.I am working on a project and I need an expired digital certificate.Anyone with an expired digital certificate kindly inbox
    1 project | /r/ComputerSecurity | 28 Jan 2023
    For developers needing to test responses to various SSL issues there is https://badssl.com. Not my site, but one I use frequently to demonstrate the result of bad/incorrectly configured certificates.
  • Expired SSL/TLS Certificate - consequences/outage?
    2 projects | /r/sysadmin | 15 Jan 2023
    https://badssl.com/ is a nice website, it shows all the ways ssl can be misconfigured. So you can see how it affects connections.
  • Privaxy: Opensource, extension-less adblocker, manifest v3 resistant
    2 projects | /r/chrome | 9 Jan 2023
    Modern Web Browsers implement robust, thorough control over SSL/TLS connections, including trust list management, protocol downgrade protection, etc. Using an HTTPS interception proxy therefore means the proxy has to implement all those controls, properly. At the very least, this shouldn't have any problems connecting to https://badssl.com/ (Google's test site, although I don't think this is currently maintained).
  • A note from our sponsor - SaaSHub
    www.saashub.com | 24 Apr 2024
    SaaSHub helps you find the best software and product alternatives Learn more →

Stats

Basic badssl.com repo stats
34
2,734
2.7
9 months ago

Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com