It still looks exactly as it should to me. We seem to talk about different things here somehow... What is it you mean is wrong with the code and syntax?
Here is an explanation of the code:
This part is generated by the RRC:
<html>
<head>
<link rel="stylesheet" type="text/css" href="main.css">
</head>
<body>
<pre>
I admit that it isn't 100% correct in that there is no document type specified, and also that the head part should contain a <title>blabla</title> tag too. But those are minor errors which shouldn't cause any problem.
This part:
HTTP/1.1 200 OK
Content-Type: text/html
Server: DynDNS-CheckIP/1.0
Connection: close
Cache-Control: no-cache
Pragma: no-cache
Content-Length: 104
<html><head><title>Current IP Check</title></head><body>Current IP Address: 188.110.6.70
is what I called the "raw DynDNS reply", i.e the data exactly as the DynDYN system sends it, BUT with the necessary HTML entities <> etc correctly encoded so that they show on the page as <> etc instead of being interpreted as HTML code/tags by the browser.
The last part:
</pre>
</body>
</html>
is also generated by the RRC and ends the page tags.
All in all, what you see is a HTML page showing the raw content of another HTML page with its HTTP header(as DynDNS's replies are HTML code)
