Website Security Test of
exmail.ehealthtechnologies.com

Test Results Summary for exmail.ehealthtechnologies.com

• Web Software Security Test
  The CMS (Microsoft Outlook Web Access) was identified, however, its version could not be determined. No CMS components, JS-libraries or frameworks were identified. Show details.
• GDPR Compliance Test
  Potential GDPR compliance issues were identified related to Privacy Policy. The following checks were not performed, as no corresponding cookies with personal or tracking information seem to be sent by the website: Cookie Protection, Cookie Disclaimer. Show details.
• PCI DSS Compliance Test
  The website is compliant with PCI DSS Requirement 6.3, while being non-compliant with Requirement 6.4. Show details.
• HTTP Headers Security Test
  Issues were identified with key security headers: missing Strict-Transport-Security, Content-Security-Policy, X-Content-Type-Options. Some optional HTTP headers may not be properly configured: Server, X-AspNet-Version. Show details.
• Content Security Policy (CSP) Test
  Content-Security-Policy headers are not present. Show details.
• Cookies Privacy and Security Test
  One cookie detected; cookieTest has security or privacy-related configuration issues. Show details.
• External Content Security Test
  No external requests were detected. Show details.
• Protection from Data Scraping Test
  11 User-Agent blocks and 8 bot protection mechanisms detected. No protection detected via robots.txt rules or meta restrictions. Show details.
• DNSSEC Configuration Test
  DNS A record detected; DNSSEC signatures are not present. Show details.

Compliance Summary for exmail.ehealthtechnologies.com

• GDPR Compliance Failed: Potential GDPR compliance issues were identified related to Privacy Policy. The following checks were not performed, as no corresponding cookies with personal or tracking information seem to be sent by the website: Cookie Protection, Cookie Disclaimer.
• PCI DSS Compliance Failed: The website is compliant with PCI DSS Requirement 6.3, while being non-compliant with Requirement 6.4.