Summary of www.sectigo.com [Desktop version] Website Security Test
Provided "as is" without any warranty of any kind.
Date/Time:Nov 6th, 2026 18:10 GMT+0
Server IP:104.19.255.155
Reverse DNS:-
Location:N/A
Version:for desktop
Your final score:
- A
- B
- C
- F
C
Test Results Summary for www.sectigo.com
- 5 third-party web software dependancies were identified, including 5 outdated dependancies. A total of 6 known vulnerabilities were detected. No Content Management System (CMS) was identified. The following CMS components, JS-libraries or frameworks were identified: moment, dompurify, nuxt.js, and others. Show details.
- Potential GDPR compliance issues were identified related to Website Security. 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 Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options; misconfigured Content-Security-Policy. Optional HTTP headers appear to be properly configured: Server, Access-Control-Allow-Origin, Cache-Control. 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.
- 8 cookies detected; _ga_EHVGHK7M57, _ga_NYEQRRQYHM, _ga, _gcl_au, _zitok, __stripe_sid, __stripe_mid have security or privacy-related configuration issues. Show details.
- 75 external requests detected; 6 requests failed. SRI is not used for 32 third-party JavaScript and CSS files. Show details.
- 1 User-Agent block and 1 bot protection mechanism detected. No protection detected via robots.txt rules or meta restrictions. Additional anti-scraping protection appears to be provided by external infrastructure. Show details.
Compliance Summary for www.sectigo.com
- GDPR Compliance Failed: Potential GDPR compliance issues were identified related to Website Security.
- PCI DSS Compliance Failed: The website is compliant with PCI DSS Requirement 6.4, while being non-compliant with Requirement 6.3.