# ssl established but no validation status **URL:** \ **Category:** Zeek\ **Created:** [October 31, 2019, 3:48pm UTC](https://community.zeek.org/t/ssl-established-but-no-validation-status/5883 "2019-10-31T15:48:32Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Palumbo\_Mauro](https://avatars.discourse-cdn.com/v4/letter/p/7c8e57/32.png) [@Palumbo\_Mauro](https://community.zeek.org/u/Palumbo_Mauro)\ **Post date:** [October 31, 2019, 3:48pm UTC](https://community.zeek.org/t/ssl-established-but-no-validation-status/5883/1 "2019-10-31T15:48:32Z")
Hi there, I have a question related to the ssl.log. As I am no expert of the SSL protocol, it is higly probable that I am missing something here. I noticed in the ssl.log several cases where the field “established” is T, but there is no certificate found (no fuids) and the field validation\_status in empty (-). In the code I saw that the field “established” is set to T if the event **ssl\_established** is generated. Is it possible to establish an ssl session without certificates? Is it because some sessions can be resumed with tickets as described in RFC 5077? I’d appreciate some help to save me some time… Mauro ---
**Author:** ![johanna](https://avatars.discourse-cdn.com/v4/letter/j/50afbb/32.png) [@johanna](https://community.zeek.org/u/johanna)\ **Post date:** [October 31, 2019, 9:15pm UTC](https://community.zeek.org/t/ssl-established-but-no-validation-status/5883/2 "2019-10-31T21:15:01Z")
Hi Mauro, it is probably resumed connections. An indication for that is that there are no server certificates present. Alternatively - for TLS 1.3 connections validation is not possible because the certificates are encrypted. Johanna ---
**Author:** ![system](https://canada1.discourse-cdn.com/flex011/uploads/zeek/original/1X/f09d732bc2cc7c7cc7e35db67cf4e1d5233ce7a7.png) [@system](https://community.zeek.org/u/system)\ **Post date:** [May 6, 2022, 3:46pm UTC](https://community.zeek.org/t/ssl-established-but-no-validation-status/5883/3 "2022-05-06T15:46:50Z")