Web Security Checker troubleshooting

Available in Classic and VPC

This page lists problems you might run into when using Web Security Checker. Click on the error to see more details.

Troubleshooting common issues

The following are examples of common errors you might encounter:

URL Collection
URL is not being collected.
It is unclear whether the URL has been collected.

A specific domain is classified as "doNotScanned"
A specific domain has been classified as doNotScanned.

False positives detected
False positives have been detected. I want to exclude false positives from the report.

Diagnosis time
The diagnosis is taking too long. I’d like to know how long it takes to complete the diagnosis.

Authentication Issues

The following are examples of authentication-related issues you might encounter:

Logging out when viewing the authentication result screenshot
The authentication result screenshot is displayed as logged out.
The authentication result screenshot displays the pre-login state.

Authentication hash file errors occur when diagnosing a web server built on another CSP
An authentication hash file error occurs during the diagnosis of services hosted on another CSP.

Authentication Hash File Upload Issue
While using NAVER Cloud Platform's WAF LB, a message appears requesting an upload of an authentication hash file.

After applying WAF LB, the system recognizes it as a third-party web server
After applying WAF LB, the system recognizes it as a third-party web server during ownership verification.

Learning resources

We offer various materials for you to explore. To learn more about Web Security Checker, check out these helpful links:

• FAQs: Web Security Checker FAQs
• NAVER Cloud Platform Blog: Web Security Checker, which diagnoses web services and provides a security vulnerability report
• NAVER Cloud Platform Blog: "Web Security Checker" - A cloud service that inspects vulnerabilities in websites targeted by hackers