It could be interesting to establish what kind of security layers have been implemented for a specific website.This apart from how the confidentiality of a site has been guaranteed, HTTPS has been implemeted correctly.
Apart from this we always have to harden and protect servers from known server exploits, wrong security settings and
against targeted phishing and malware attacks (but we have avast there, haven't we

).
We should be particularly aware of mail servers, that banners aren't speaking too loud about versions used, but pinging certain mailservers without version info will produce them anyway. So test non-invasively via banners and functional tests
for what ESMTP functions are being supported (when we find no transport encryption support this means that all will be transported in clear txt over the Internet). Some Firewalls and Outdated Security Policies will only support pure SMTP,
meaning less attack but lack of transport encryption of sorts.
Also read here:
https://blog.qualys.com/ssllabs/2016/09/06/is-http-public-key-pinning-deadWhat was being tested?
- Qualys SSL labs score?
- High Tech Bridge HTTPS score?
- High Tech Bridge web security score?
- HTTPS implemented?
- DNSSEC implemented?
- HTTP Strict Transport Security Policy implemented?
- Weak cyphers support?
- CSP implemented?
- Unknown jQuery security updates?
- HTTPOnly Security not being set for cookie?
- live-Twitter Javascript code?
- Google Analytics active?
- Live Google advertising?
- Live Google Javascript Code?
- Type HTTP redirect?
- Wildcard Certificate or many domain names in certificate?
- Extended Validation Certificate?
- Certificate Transparency Certificate?
- Perfect Forward Security supported?
- HSTS Preloading vulnerability?
- X-Frame Options implemented
- X-Powered by Header?
- Autocomplete set at password field (now obsolete)?
- Same Site Protection not set for cookie?
- Publication of Technical Info?
- Client-Initiated-Secure-Renegotiation supported?
- Subresource Integrety (SRI) implemented?
- TLS 1.0 supported?
- Vulnerable to BEAST attack?
- Vulnerable to DROWn attack?
- OCSP Alert Sample configured?
- Public-Key-pinning implemented? (see link, seems dead now)
- X-XSS-Protection implemented?
- X-Content-Type-Options implemented?
Scan proposal info - info credits go out to security researcher, Sijmen Ruwhof.
polonus (volunteer website security analyst and website error-hunter)