Currently, only the common name is checked correctly. If the cert is not valid for the common name but is valid for the SAN, TLS-Scanner will print that the certificate is not valid for the given domain. SAN parsing is currently not implemented in X.509-Attacker. At least the common cases should be implemented to get rid of this false positive.
Currently, only the common name is checked correctly. If the cert is not valid for the common name but is valid for the SAN, TLS-Scanner will print that the certificate is not valid for the given domain. SAN parsing is currently not implemented in X.509-Attacker. At least the common cases should be implemented to get rid of this false positive.