Summary of www.hancockwhitney.com [Desktop version] Website Security Test
Provided "as is" without any warranty of any kind.
Date/Time:Nov 6th, 2026 05:16 GMT+0
Server IP:199.60.103.30
Reverse DNS:-
Location:Mount Hope, United States
Version:for desktop
Your final score:
- A
- B
- C
- F
C
Test Results Summary for www.hancockwhitney.com
- 11 third-party web software dependancies were identified, including 9 outdated dependancies. A total of 8 known vulnerabilities were detected. No Content Management System (CMS) was identified. The following CMS components, JS-libraries or frameworks were identified: bootstrap, jquery, jquery, and others. Show details.
- Potential GDPR compliance issues were identified related to Website Security, Cookie Disclaimer. Show details.
- The website is compliant with PCI DSS Requirement 6.4, while being non-compliant with Requirement 6.3. Show details.
- Issues were identified with key security headers: missing X-Content-Type-Options, X-Frame-Options; misconfigured Content-Security-Policy. An optional HTTP header may not be properly configured: Report-To. Show details.
- Content-Security-Policy is enforced but configuration issues were identified: directive errors. A report-only Content-Security-Policy is not present. Show details.
- 17 cookies detected; ___so32171, _ga_LS73HEVZHR, __hssrc, _uetsid, _evga_da6e, _sfid_250c, _fbp, __spdt, _gcl_au, __hstc, _uetvid, __hssc, _ga, LSESSIONID, hubspotutk have security or privacy-related configuration issues. Show details.
- 123 external requests detected; 17 requests failed. SRI is not used for 47 third-party JavaScript and CSS files. Show details.
- No significant anti-scraping protections were detected. Show details.
- DNS CNAME record detected; DNSSEC signatures are not present. Show details.
Compliance Summary for www.hancockwhitney.com
- GDPR Compliance Failed: Potential GDPR compliance issues were identified related to Website Security, Cookie Disclaimer.
- PCI DSS Compliance Failed: The website is compliant with PCI DSS Requirement 6.4, while being non-compliant with Requirement 6.3.