certainly you have some data from the fetch, but it seems the body is missing, what i can see in the mumbo jumbo somewhere is a head tag. but no body, hence your find returns nothing.
i would say maybe take a backstep before using php dom, to trying to get the pages in correctly first. the html dom parser has two ways, of using its internal fetch (file_get_html)
or by using sending html to its parser via a new parser object.
i would think getting the html on your own, then passing it to the parse would be a lot easier,
as you would be able to diagnose each step should anything be wrong.
step (1) fetch the html
-----------------------
there are many ways to fetch text via PHP, file_get_contens is one, using cURL library is another. i would recommend the cURL library method.
there is a simple example at
http://www.jonasjohn.de/snippets/php/curl-example.htm
with it, you just go
$contents = DownloadUrl($Url);
( or you can use any other curl examples which there are quite many avialable online )
at this stage, you can check and ensure that you *are* getting html from the remote site
and that all is fine with html.
then send it to the html to the dom parser, using its object method.
step 2 - parse the html using the dom parser
-------------------------------------------
the API gives an example, and from that, it would be as follows...
( assuing you have included the parser somewhere before )
$html = new simple_html_dom();
// Load HTML from a string
$html->load($contents);
and from then on do the finds and whatever else with the dom.
the idea is if you already have valid text from the beginning, and your 'finds' in the dom reveals
nothing, then it is easy to suspect there may be bugs n the dom parser itself. especially so if you initial $contents is all cleally filled with the data/tables you wanted to fetch.
using the doms internal fetch mechanism complicates matters as you would not know if the complete html had been fetched correctly, and from your dump above, the dom parser does not appear to have done so correctly.
an alternative is to use php file_get_contents, which does the same job but you have only
limited control over sessions. the advantage of cURL is that you can also do posts and gets
and this would come in handy for site which requires post data ( search engines for example ).
anyways, good luck, hope you get some happy results. i have never used the dom parser, i am relying on its documentation. they seem to have quite good complete documentation, so that helps a lot.
i would go over to the dom parsers forum if ,
1. you have data in your fetch,
2. the parser cannot find it for some reason.
otherwise, the problem is still at your desk i think.
hope this helps.