Summary of portal.payments.argenta.be [Desktop version] Website Security Test
Provided "as is" without any warranty of any kind.
Date/Time:Nov 6th, 2026 00:07 GMT+0
Server IP:3.120.122.241
Reverse DNS:ec2-3-120-122-241.eu-central-1.compute.amazonaws.com
Location:Frankfurt am Main, Germany
Version:for desktop
Your final score:
- A
- B
- C
- F
C
Test Results Summary for portal.payments.argenta.be
- 6 third-party web software dependancies were identified, including 5 outdated dependancies. A total of 9 known vulnerabilities were detected. One identified third-party web software dependancy has an unknown version. The CMS (Joomla!) was identified, however, its version could not be determined. The following CMS components, JS-libraries or frameworks were identified: bootstrap, highcharts, jquery-validation, 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 header misconfigured Content-Security-Policy. Optional HTTP headers appear to be properly configured: Server, Referrer-Policy, Cache-Control. Deprecated HTTP headers detected: X-XSS-Protection. Show details.
- Content-Security-Policy is enforced and appears to be properly configured. A report-only Content-Security-Policy is not present. Show details.
- One cookie detected; 81f30cf708470b974874c8a96a6bcdb2 has security or privacy-related configuration issues. Show details.
- No external requests were detected. Show details.
- No significant anti-scraping protections were detected. Show details.
- 3 DNS A records detected; DNSSEC signatures are not present. Show details.
Compliance Summary for portal.payments.argenta.be
- 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.