### Expected Behavior

```
curl https://google.com

301 Moved

301 Moved

The document has moved
here.

```
### Actual Behavior

```
* Preparing request to https://google.com/
* Current time is 2025-10-14T07:11:03.443Z
* Enable automatic URL encoding
* Using default HTTP version
* Enable timeout of 30000ms
* Enable SSL validation
* Hostname google.com was found in DNS cache
* Trying 93.46.8.90:443...
* Connected to google.com (93.46.8.90) port 443 (#20)
* ALPN: offers h2
* ALPN: offers http/1.1
* CAfile: /etc/ssl/cert.pem
* CApath: none
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* (5454) (IN), , Unknown (72):
* error:0A00010B:SSL routines::wrong version number
* Closing connection 20
```

### Reproduction Steps

1. Create a new request in insomnia.
2. Click Send button

Version: Insomnia 11.6.1
Build date: 9/18/2025
OS: Darwin arm64 24.6.0
Electron: 37.2.6
Node: 22.17.1
Node ABI: 136
V8: 13.8.258.30-electron.0
Architecture: arm64

### Is there an existing issue for this?

- [x] I have searched the [issue tracker](https://www.github.com/Kong/insomnia/issues) for this problem.

### Which sync method do you use?

- [ ] Git sync.
- [ ] Insomnia Cloud sync.
- [x] Local only

### Additional Information

_No response_

### Insomnia Version

Insomnia 11.6.1

### What operating system are you using?

macOS

### Operating System Version

macOS Sequoia 15.6.1 (24G90)

### Installation method

homebrew

### Last Known Working Insomnia version

_No response_

Reproduce the request in Insomnia 11.6.1 on macOS Sequoia 15.6.1 using the reported steps, then compare its TLS negotiation and connection behavior with curl https://google.com. Trace the request path from the Send action and verify that the request completes with the expected 301 response instead of the reported OpenSSL error.

Written by the indexing model from the issue text.