Unknown means we cannot determine the information, eg for PHP version the server might not be exposing this in the headers (which is actually good) or your admin panel might be in non-standard location (which is good too). It's recommended you manually verify those unknown results to double check eg that you use SSL for admin panel or using up to date PHP ...
I faced the same issue. This issue seems to be from portal itself.
You can verify the code is added in your site from your browser by looking the source code of your website. search the code if you find the code simply submit the form in the portal. This will add your site and then you can run your scan by selecting the run scan from action column.
Its very easy to find the security patches that your website needs.Visit this link and click go to security scan.There you will have to enter your domain name and it will scan the site for you.It will help you find the security patches required and also improvements needed for the website.
You can also try it with https://www.magereport.com/scan/?s=https://...
When using a custom theme (never happens with a clean magento2 installation, at least for me), if you put the verification code following the tutorial, which will tell you to place the verification code in the "head", it will not work for whatever reason. This is confirmed by inspecting the code after you follow the tutorial, as the verification code will ...
We are seeing often this problem coming from web server/proxy/cache removing comments from the output before sending to the browser. If comment with verification ID is removed, the verification will not be successful.
The current suggestion is to work with your hosting provider to disable comment removal but Magento will try to enable alternative site ...
I have successfully completed the ownership of the site.
I have copied and pasted the conformation code as it is in "HTML Head(Miscellaneous Scripts)" and click on save config.
then i have click on "Verify Confirmation code" its working
As you're using an old version of Magento, you need to install the MSP Recaptcha extension (comes with latest Magento version) on your website.
You can use the MSP Recaptcha by running the following command in the terminal.
composer require msp/recaptcha:2.1.2
php bin/magento s:up
php bin/magento s:d:c
php bin/magento s:s:d
php bin/magento c:f
Hope it ...
Magento scan tool and Magereport performs the same work but in little different way. I would say Magereport is more flexible than Magento scanner. I'll give you an examples here:
One of my security patch was detected as failed by Magento and on the same time Magereport was saying passed. After investing a lot of effort and time we find out that Magento ...
It's probably easier to upgrade to the latest 126.96.36.199 which includes all security patches.
For Magento 188.8.131.52 you need the following patches.
See also this list by JH:
I am able to fix by below patch
diff --git a/vendor/magento/module-swagger/view/frontend/templates/swagger-ui/index.phtml b/vendor/magento/module-swagger/view/frontend/templates/swagger-ui/index.phtml
index b20da68..26ef484 100644
Depending on your host you may be able to sort yourself.
Do you have a cpanel login?
Check this demo
Under domains you may have the option to change your document root to /public_html/pub/
You do not need to modify any Magento files. If ...
I have found jQuery versions hidden in the following places while updating our client's sites.
Codebase (phtml/xml files)
Backend Config HEAD/Footer html areas
Modules / JS Libraries loading their own version of jQuery
First thing would be to check if its within the ...