Summary of spar-international.com [Desktop version] Website Security Test
Provided "as is" without any warranty of any kind.
Date/Time:Nov 6th, 2026 23:23 GMT+0
Server IP:23.88.103.132
Reverse DNS:static.132.103.88.23.clients.your-server.de
Location:Nuremberg, Germany
Version:for desktop
Your final score:
- A
- B
- C
- F
B+
Test Results Summary for spar-international.com
- 9 third-party web software dependancies were identified, including 2 outdated dependancies. No known vulnerabilities were detected. 4 identified third-party web software dependancies have unknown versions. The CMS (WordPress) was identified, however, its version could not be determined. The following CMS components, JS-libraries or frameworks were identified: core-js, vanilla-lazyload, Google Analytics Dashboard Plugin for WordPress by MonsterInsights, and others. Show details.
- Potential GDPR compliance issues were identified related to Cookie Disclaimer. Show details.
- The website is compliant with PCI DSS Requirement 6.3, while being non-compliant with Requirement 6.4. Show details.
- Issues were identified with key security headers: missing Strict-Transport-Security, Content-Security-Policy, X-Content-Type-Options. An optional HTTP header may not be properly configured: Server. Show details.
- Content-Security-Policy headers are not present. Show details.
- 5 cookies detected; _ga_BPQQVWM9XW, _ga_FJ6G4GNHHG, _ga, _ga_P4RJCC192V, CookieConsent have security or privacy-related configuration issues. Show details.
- 15 external requests detected; 4 requests failed. SRI is implemented for 1 out of 8 third-party JavaScript and CSS files. Show details.
- No significant anti-scraping protections were detected. Show details.
- DNS A record detected; DNSSEC signatures are not present. Show details.
Compliance Summary for spar-international.com
- GDPR Compliance Failed: Potential GDPR compliance issues were identified related to Cookie Disclaimer.
- PCI DSS Compliance Failed: The website is compliant with PCI DSS Requirement 6.3, while being non-compliant with Requirement 6.4.