Xenu's Link Sleuth (TM) is a spidering software that checks Web sites for broken links. Link verification is done on "normal" links, images, frames, plug-ins, backgrounds, local image maps, style sheets, scripts and java applets. It displays a continously updated list of URLs which you can sort by different criteria. A report can be produced at any time.
Additional features:
By downloading you are acknowledging that:
System requirement: Microsoft Windows 95/98/NT/2000, WININET.DLL required (is usually included). No, it won't work on Windows 3.11, not even with Win32s. No, I won't make a MacOS, Linux, Beos or C64 version. Don't ask!
Attention CompuServe users: The old version of RPAWINET.DLL (e.g. from 18.9.1996) that came with the WinCIM 3.0 CD-ROM is deadly - go get the bugfix from CompuServe.
Ok, I have read all that, I want to download! (current version: 1.1a from 17.6.2000)
Getting started:
Unzip it and install it wherever you want. To check a site, click the toolbar icon on the left and enter a WWW address. If the address finishes with a directory name, don't forget to put a / at the end or you will possibly get the whole parent directory spidered.Incorrect:
http://www.host.com/~userCorrect:
http://www.host.com/~user/You can also click the "browse" button to check a local HTML file. If you do not already use IE for browsing and are sitting behind a firewall, don't forget to configure your proxy before you start. To find out what the software can do, simply try out the menu choices, the toolbar and the right mouse key.
Good luck! If you find the software useful, please click here.
Powered by ListBot |
If you like to use a button on your WWW page, link to this page
with this button:
The address of this web page is http://home.snafu.de/tilman/xenulink.html
See here.
Do you want to be a Knight of Xenu? Then join their team in the worldwide RC5-64 decryption effort. Join team #3504 after your decryption client has been working successfully for one day. (Attention: do not forget to configure the client with your own e-mail address, and remove any "(" or "<" from it). E-mail me if you have trouble setting up the client or configuring it.
Yes and No. Xenu's Link Sleuth (TM) does not have the graphic capabilities of WebAnalyzer 2.0 ("Wavefront view"). But here are some of the advantages of Xenu's Link Sleuth (TM):
Xenu sez: check your website both with this product and with another product (WebAnalyzer, Linkbot, InfoLink, LinkScan, LinkAlarm and Theseus offer trial versions), and decide what you need and what you are willing to pay.
Yes and No. IMO, Net Mechanic (a free WWW based service) is best to check very small web sites, but useless for the rest:
An advantage of Net Mechanic is that you don't waste bandwidth - you submit your site and get an e-mail later that points to a WWW page with the results.
No need to. If you feel the software is useful, you should support AFF, a nonprofit, tax-exempt research center and educational organization founded in 1979. AFF's mission is to study psychological manipulation and cultic groups, to educate the public and professionals, and to assist those who have been adversely affected by a cult-related experience. I suggest a donation of $20 for individuals and $200 for corporations. In the US, your donation can be deducted from your income. (AFF does not endorse this site in any way, did not develop this software, does not sell this software, and the use of this software does not depend whether or not you make a donation.)
Germans can make a tax deductible donation to the Dialog Zentrum Berlin e.V., Konto-Nr. 1551390051, Bank für Kirche und Diakonie BLZ 35060190.
Or visit the Xenu bookstore.
The key is the "../" part. It means you have e.g. a top level page that links to a page in a directory above, which doesn't exist. It is true that Mozilla will not have any problems with such a page; but I am less tolerant.
You can configure a proxy in the control application of Windows. Double-Click on the "internet" symbol, then click on the "card" of the dialog box that is named "Connection". You will need a proxy if you are sitting "behind a firewall". This is usually so in big corporate networks.
Either because you do have a space in the URL, or because you have a carriage return / newline in it. Although Mozilla tolerates this, I do not.
Re-edit the page, double-click on the picture, remove file: from the picture location and take care to uncheck "copy image to document's location" in the "properties" dialog box (at the bottom left) before you save and exit the dialog box.
There is no maximum. It is limited by the memory on your computer.
Since september 1998 (1.0n), you can do so without a local web server (your address would then be http://127.0.0.1). Use the "Browse" button in the "New" dialog box.
The results will not always be the same as a "remote" check:
A user of IE 4.0 reported that when not online, the software checks every "remote" URL like a local file. This is a problem of the newer version of the WININET.DLL; the version with IE 3.0 reports "no connection" or "no such host" instead, which is more logical.
One user said it worked fine after he copied a version of WININET.DLL from a Windows 95 system standing nearby, and put it into the directory where Xenu's Link Sleuth(TM) was installed.
Because it uses a (possibly patented, see patents here and here) technique known as preemptive multithreading. It means that the link checking software retrieves several web pages at the same time; the competition uses the same technique. The maximum count of threads is initially set to 30, but you can configure it to any number between 1 and 100. A number that is too high might result in failed connections, which means you will have to recheck the broken links. I get best results with 70.
Initial tests suggest that my software is faster than WebAnalyzer 2.0. This may also have to do with the fact that WebAnalyzer is wasting time by displaying more graphics.
Hahahahahaha!
Sure, make me "an offer I can't refuse".
I check my own web site every week on friday. Nevertheless there are always broken links:
Repairing broken links (i.e. getting the correct ones) is a difficult task that takes time, but with experience, you'll get faster and faster.
Starting with version 1.0k I have implemented a new ftp checking method that is 100% reliable. Sadly, this method does not work with proxies. The previous method I used (and still use for gopher) was unreliable, as it did not detect certain errors.
The method for checking gopher sites is still unreliable. When an ftp or gopher site is accessed through a proxy, this proxy builds up a web page. Sadly, it doesn't always bring up the information whether the URL exists or not. When you access a gopher site without a proxy, it brings an error message, but not an error code. This seems to be a bug of the OpenURL() function of WININET.DLL.
The output lists ftp and gopher sites as links, which allows you to make a manual check of these sites.
Starting with version 1.0g (Christmas 1997), URLs are launched with DDE ("dynamic data exchange", a windows method of communication between applications), to open many browser windows but to prevent the opening of several Netscape applications. This is done with the help of the Registry, by searching for HKEY_CLASSES_ROOT\http\shell\open. This has the path for the browser, the DDE application name (e.g. "Netscape"), the DDE topic (usually "WWW_OpenURL"), and a template for the DDE item (usually "%1"). If you cannot launch an URL, do not panic - export and e-mail me the segment of your registry (start REGEDIT.EXE, and search for "http").
The cause is usually that you have not installed Netscape properly (maybe you just transferred the files from another computer). Solution: reinstall Netscape over your current installation.
If you ask this, then you have configured your internet configuation to be asked before submitting a cookie, and get constantly requests. But sadly I am not responsible for this - it is a part of Microsoft's WININET.DLL. According to Cookie Central, there is not much you can do.
Since August 1998, the internet movie database prevents the software from checking on their site. Apparently, someone misused my software, which put a tremendous load on their server. It would be easy for me to fool their protection mechanism, but this would also mean that no websites could protect themselves; I want to be a good netizen, and I don't want to make it too easy for people to misuse my software.
If you have set your proxy correctly, try to connect with IE. If this doesn't work, read this usenet post for help. If this still doesn't work and you use Windows NT 4.0, install the latest NT service packs (up to SP5).
"Orphan files" are files that are not linked at all. I cannot do it, because one isn't always able to access the directory, usually for security reasons, so that people don't know what files are actually available. Even if I would implement such a search on the local disk, it would be useless for the remote server.
Some people have reported crashes. These problems were usually solved by installing IE 3.0 (or higher) or the following service packs:
One guy had problems with the WININET.DLL (v. 4.70.1300) installed with OEM Windows 95 (v. 95 4.00.950 C). Changing to version 4.70.1335 solved the problem; he said he found it at ftpsearch.lycos.com
A simpler solution is to go to http://windowsupdate.microsoft.com and install whatever they tell you (you need to have IE 4.0 or higher on your system)
Although I received many reports that it runs fine, one user reported a problem and a solution:
Windows 2000 automatically sets a configuration option to use HTTP 1.1 for connecting to web sites. Many, many web sites do not use that version but continue to use HTTP 1.0, so the automatic setting may prevent connections. This is the reason why Xenu would not run for me. When I disabled that setting, Xenu performed properly.
To disable that setting: Control Panel -> Internet Options -> Advanced (tab) -> HTTP 1.1 settings (list heading) -> Use HTTP 1.1 (checkbox: uncheck it)
Because I can't... It is hidden somewhere in the WININET.DLL, i.e. Microsoft doesn't allow users to configure it.
The software works pretty well, but here the list of things that shouldn't be.
If you find another bug, e-mail me a description, please include the URL you are checking, and if possible try to save your work in a .XEN file and attach it. Also check http://windowsupdate.microsoft.com to make sure that your system has all the updates. If you want to e-mail a suggestion, click here.
Things I will do in the future:
In April and May 1997 my employer assigned me on an out-of-town job, because another department needed a guy with MFC experience. So from monday to friday I was away, and on the evenings I was bored to death. Every week-end I was back home, and I usually checked my web site for broken links with WebAnalyzer. Sadly the software had a lot of bugs, and their support was ignoring my e-mails, and I was mad as hell, as I had spent quite a lot of money on a product that wasn't worth it. My job was also the first contact with VC++ 4.2 (previously I had only worked with VC++ 1.5, because our customers have a lot of 16bit systems), which had some easy-to-use Internet access classes. I had already experience with WINSOCK programming, but these classes would spare me a lot of time evaluating HTTP result headers and other annoying stuff. On an evening after an excellent italian food with a good chianti I took some hotel letter paper and wrote down a concept for checking links. A month later I took some time to install the development software on my computer and started working, with the help of that hotel-room concept. The work was done on some evenings, but mostly on week-ends, when I had more time.
My philosophy on software development has always been "smaller, simpler, cheaper", long before the NASA realized this. Because of that, I need no fancy (but totally useless) graphics like in WebAnalyzer. Just results. And they'd better be 100% correct or I'd have to kill myself :-)
The
application is written in VC++ 4.2b, and uses the MFC classes as much as
possible: CDocument, CView, CListView, CObArray, CArchive, CInternetSession,
CHttpFile, etc, etc. That saves me a lot of time. I am not planning
to switch to VC 5.0, as it would just fill my hard disk and doesn't bring
anything new except the "flat toolbar button design" which I
don't like.
Icons in EXE file: Martin Hunt and Paul Campbell; Icon on this page: Erik Plummer; Idea to use banners in report: Marc Cross; Xenu button logo: Fred C.; Volcano animated cursor: Juan C. Pradas-Bergnes
Volcano: see inside the VOLCANOE.ANI file. I'm using this without permission, as I didn't receive the file from the author and don't know whom to ask.
Xenu, Xenu's Link Sleuth and Link Sleuth are trademarks used by Tilman Hausherr for software products and services. These products are not associated in any way with services licensed by RTC, CoST, BPI, CSI, etc.
Home | $cientology | Magic | Mozilla | Tilman | Deutsch | Bookstore