No Response to Norton Safe Web Dispute – Domain Incorrectly Flagged

Hello,

I would like to ask for help regarding a review request submitted to Norton Safe Web.

The affected domain is iqsoft.cz

More than a month ago, I submitted a dispute because our domain was incorrectly flagged as malicious. The website is legitimate, secure, and has not been compromised. Unfortunately, since submitting the dispute, there has been no response or status update, and the classification has not changed.

This incorrect rating is causing real issues for our business and users, so I would kindly ask if someone from the Norton team could review the case or advise on the next steps to move this forward.

If any additional information or verification is required from our side, I will be happy to provide it immediately.

Thank you in advance for your time and support.

Hello @darthsian

https://iqsoft.cz/


Dispute is already in progress.

=================================


55ba94530402

=================================


4d29f214ee2d/2026-02-10T19:25:29.572Z

=====================================

Submit a file or URL to Norton for review here

Note: after submitting dispute and waiting 48 business hours with no change.
Please contact Norton support and advise support that you’ve submitted dispute and waited 48 business hours. My understanding is…once you state that you have already submitted False Positive over the submission portal and waited 48 business hours…support agent shall take the URL and detection screenshot and advance the case.

Contact Chat Support and Norton Phone Number (related notes here)

https://iqsoft.cz/


https://www.php.net/ChangeLog-7.php#7.4.6

=================================

https://iqsoft.cz/

https://iqsoft.cz/

All: The PHP version shown on the website, version 7.4.2 is full of vulnerabilities that are outlined in the AI derived information below. It is also no longer support by its creator company. Wondering if Norton is nailing the site due to unpatched / upgraded PHP? The latest version is PHP version 8.5 .

*Note that AI can make mistakes

AI Overview

PHP 7.4.26, released in late 2021, is vulnerable to several security issues, most notably

CVE-2021-21707, which allows improper XML parsing (e.g., simplexml_load_file()) to read unintended files using URL-encoded NUL characters. Additionally, Docker images using this version show hundreds of vulnerabilities, and the entire PHP 7 branch is end-of-life.

[image]Snyk +3

Key vulnerabilities and security risks associated with PHP 7.4.26 include:

  • File Read Vulnerability (CVE-2021-21707): A flaw in XML functions allows attackers to bypass filename checks, potentially reading arbitrary files on the server.
  • End-of-Life (EOL) Status: PHP 7.4 is no longer supported, meaning no further security updates are released, leaving it vulnerable to all subsequently discovered, unpatched flaws.
  • Docker-Specific Vulnerabilities: Docker images based on PHP 7.4.26 (e.g., php:7.4.26-fpm) may contain hundreds of known vulnerabilities (over 300 reported in some versions).
  • Apache/System Vulnerabilities: Reports indicate potential issues with associated Apache modules (e.g., apache2-bin) affecting data authenticity in specific Docker configurations.

Recommendation: Upgrade to a supported version, such as PHP 8.2 or 8.3, to mitigate security risks

SA