Q. The scan is stuck on external links and gives a response code "N/A". Why is this happening?
N/A is the common response code we get for requests that are not resolved.
When a URL is typed in the URL address bar, the client (in this case the browser) sends a request to the server which hosts the asset (a page, an image, or a document).
The scan makes the same request during the scanning process. If the server takes more than 60 seconds to find the right resource, the response can be a time-out or may not resolve.
-
This can happen when the page, image, or asset is housed in the server, but the server may be down when the request happened.
-
The link may point to a third-party website that blocks our IP.
-
The site may use fingerprinting to identify and block our crawler.
The scanning process is lengthy and often takes hours to complete. When the crawler scans a link to an asset hosted by a server that is down, we cannot determine if the response is a 404 (client), 500 (internal server error), or 300 (redirect issue), and the response code is N/A (Not Available).
For more help, please contact support.
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.