hello,
Our website www.norwii.com is on your blacklist.
We have update our file nda.exe in our website.
https://www.norwii.com/downloads/presenter/windows/nda.exe.
When the user inserts our flip pen USB, our driver will download and launch nda.exe, remind the user to download relevant software.
Now nda.exe has no malicious behavior and has passed your inspection
Please re-check our website and remove from your blacklist.
thank you very much.
Avast didn’t alert when I went to your site. I found some others that do, though.
https://www.virustotal.com/gui/url/5ca77050b979369df93d70b29f0a55434f51a0c4f580ed21fdbb8c7ff1799630/detection
https://sitecheck.sucuri.net/results/www.norwii.com
Yes, http://www.norwii.com is not blocked,
But http://www.norwii.com/downloads/presenter/windows/nda.exe is blocked.
And the file nda.exe has just passed avast inspection.
We are also applying to cancel the blacklist of other companies.
Report a false positive (select file or website)
Click this link >> https://www.avast.com/false-positive-file-form.php
How to report >> https://forum.avast.com/index.php?topic=14433.msg1289438#msg1289438
@ eric.dai
See https://sitecheck.sucuri.net/results/norwii.com which shows others blocking the site and considers it a Critical Security Risk.
It would appear that you have other issues to consider, also see https://webhint.io/scanner/9c47fe9f-2233-4a16-969e-1d470d83de2e
Existing website risks:
Website Risks
-http://norwii.com
failed
Insecure SSL/TLS versions available
Any version of the SSL protocol, and TLS prior to version 1.2, are now considered insecure.
The server should disable support for these old protocols.
failed
HTTP Strict Transport Security (HSTS) not enforced
Without HSTS enforced, people browsing this site are more susceptible to man-in-the-middle attacks. The server should be configured to support HSTS.
Email Security
-http://norwii.com
failed
DMARC policy not found
DMARC policy was not found. This makes it easier for attackers to send email from this domain.
A DMARC policy should be deployed for this domain.
failed
SPF policy uses ~all
Sender Policy Framework (SPF) record is too lenient as to which domains are allowed to send email on the domain’s behalf.
This record should preferably not use the ~all mechanism, as this does not instruct the mail receiver to reject messages from unauthorised sources. When DMARC is not being enforced, -all should be used on the SPF record.
polonus