RDPSchool is not a separate company or service. The brand has been retired and rdpschool.com now points here permanently.
Same team, same servers, same support — new name. Existing RDPSchool accounts, services and renewals continue exactly as before; only the name and the web address have changed.
Enter a page address and every link and image on it is tested from a VPSLake server. Dead links, redirects and blocked requests are sorted to the top, so you can see what needs fixing at a glance.
HOW TO USE IT
No crawler to install and no account. Point it at the page you care about and read the list.
Use the exact page you want to audit, such as a blog post, a resources page or your homepage. A bare domain like example.com is treated as https://example.com/.
Select Check Links. The server downloads the page, collects every <a href> and <img src>, and tests them in parallel within about ten seconds.
Broken links come first, then links that were refused or could not be confirmed, then redirects, then links that answered 200 OK. Use the filter buttons to focus on one group.
Update or remove each dead link, point redirected links at their final URL, and download the CSV if you need to hand the list to someone else. Run the scan again to confirm.
A link is marked broken when its final answer is a client or server error, such as 404 Not Found, 410 Gone or a 5xx error, or when there is no answer at all because the domain no longer resolves, the connection is refused, the TLS certificate is invalid or the request times out.
A redirect is not broken, but every extra hop costs your visitors time. Where a link redirects, the table shows the address it finally lands on so you can link there directly.
Large platforms often refuse automated requests from data-centre addresses. LinkedIn answers with its own 999 code, others return 403 Forbidden or 429 Too Many Requests, and social networks sometimes send a 400 even for a live page.
Those results are grouped as unsure instead of broken, because the page probably works in a normal browser. Open them yourself before deleting anything.
Internal 404s usually appear after a migration, a permalink change or a deleted page. On a VPS you fix them at the web server: add a return 301 rule in the Nginx server block, or a Redirect 301 line in Apache, from the old path to the closest live page.
Internal links matter more than outbound ones, because they carry crawlers and ranking signals between your own pages.
Each link is tried with a light HEAD request first. If the server rejects HEAD, the checker asks for only the first few kilobytes with a normal GET, so large files are never downloaded. Redirects are followed by hand, up to three hops, and each new address is checked before it is requested.
Links on the same host are tested a few at a time so the scan never floods one website.
The checker reads the HTML the server sends, so links that a page builds later with JavaScript are not seen. It tests the first 50 unique links and images on one page and stops at a ten-second time budget; anything left over is marked as not checked. Results come from one VPSLake server location, so a link that is geo-blocked or rate-limited may behave differently for your visitors.
FREQUENTLY ASKED QUESTIONS
<img> source on the page is tested alongside the links, including lazy-loaded images that keep their real address in data-src. CSS background images and files loaded by scripts are not included.