When testing the ALPACA probe I see that the SNI name is set to "notarealtls-attackerhost.com" in the isSupportingStrictSni method, however on my server trace the SNI value is still set to the default (localhost). This causes the SNI mitigation test to fail for the server even though I have implemented strict SNI logic, it seems he SNI value is not being set correctly in the TLSScanner client.
When testing the ALPACA probe I see that the SNI name is set to "notarealtls-attackerhost.com" in the isSupportingStrictSni method, however on my server trace the SNI value is still set to the default (localhost). This causes the SNI mitigation test to fail for the server even though I have implemented strict SNI logic, it seems he SNI value is not being set correctly in the TLSScanner client.