Something has changed in the postman-echo.com site and now it only supports TLS 1.3 - see at SSL Server Test: postman-echo.com (Powered by Qualys SSL Labs)
Was this planned? I have unit tests that are now failing because they use a TLS 1.2 supporting client?
Hey @DanAvni 
Thanks for raising this question.
Could you provide a little more information around how this is impacting your unit tests, please?
Is the Postman Echo service part of those internal tests?
@danny-dainton , Some of my tests call out to postman-echo with various requets to check failure handling and response parsing on my side. I am calling the site from C# using some 3rd party HTTP component
Hey @DanAvni 
I can’t see that anything was changed or released for that service recently, I’ll check with the team though.
Hooking a third-party API into your unit tests can be a great way to validate that your application works well with external systems. That said, it’s worth remembering that those APIs can change or go offline without notice, which can make your tests unreliable. 
Hello @danny-dainton
I am not sure to understand, you seem to say that there was no modification about TLS on postman echo. But I got the same problem, since the 8-9th october, my tests are in error because now postman-echo accept only TLS 1.3.
We use winhttp from a windows 2016 server (which is still supported by microsoft until 12 jan 2027).
If nothing should have changed, it may be a bug ?
Welcome to the Postman Community! 
I mentioned that I wasn’t aware of any recent changes or releases, so I reached out to the team to confirm. Since I’m not directly involved in the development or maintenance of that service, I wanted to make sure I had the most accurate information.
Around October 8th (or slightly before), the Echo service was moved behind Cloudflare, which could be related to what we’re seeing here. I’m still in touch with the team to gather more details about this change, and once I have that information, I’ll follow up with a more complete update.
Thank you for your response @danny-dainton
I will wait for further details but I am already reassured that it seems to be a side effect and not a deliberate move 
Hey @DanAvni / @thomasgustinesker
The team has made a change on Cloudflare for the Echo service - would you be able to confirm that this solves your issue, please.
It is all good for me ! Thank you @danny-dainton (and the dev team ofc) 
That’s great to hear. Appreciate you confirming! 