You could be running a different version of curl, e.g. homebrew. Try `which curl` and `/usr/bin/curl <url>`.
replyUname is not enough here to identify what has or has not been done to your system to deal with the compromised certificates.
replyNo, no, I meant it to show that the machine is running the current/latest macOS, and the results I am getting from curl on the two URLs.
replyMaybe you have another curl in your path?
reply $ uname -a
Darwin MacBook 27.2.0 Darwin Kernel Version 27.2.0: Wed Oct 14 23:47:21 PDT 2026; root:xnu-13432.41.4~25/RELEASE_ARM64_T6030 arm64 arm Darwin
$ which curl
/usr/bin/curl
$ curl https://dv-g3b-emudhra.we-have-a-problem.com/
Your client successfully connected to the site. That's bad!Aha! Touche! Indeed, I am using brew's curl ("/opt/homebrew/opt/curl/bin/curl"). That's why; the one at "/usr/bin" connects just fine (facepalm).
reply