Validation Output: 871 Errors

1. Line 25, Column 61: cannot generate system identifier for general entity "u"

   …ge.src= 'http://www.pro.fuchs-world.de/index.php?a=out&u=' + username;

   ✉

   An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

   Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.

   If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

   Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

2. Line 25, Column 61: general entity "u" not defined and no default entity

   …ge.src= 'http://www.pro.fuchs-world.de/index.php?a=out&u=' + username;

   ✉

   This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

3. Line 25, Column 62: reference not terminated by REFC delimiter

   ….src= 'http://www.pro.fuchs-world.de/index.php?a=out&u=' + username;

   ✉

   If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

4. Line 25, Column 62: reference to entity "u" for which no system identifier could be generated

   ….src= 'http://www.pro.fuchs-world.de/index.php?a=out&u=' + username;

   ✉

   This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

5. Line 25, Column 59: entity was defined here

     image.src= 'http://www.pro.fuchs-world.de/index.php?a=out&u=' + username;

6. Line 37, Column 19: Attribute "height" exists, but can not be used for this element.

   							<tr height="73">

   ✉

   You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

   This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

   How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

7. Line 89, Column 93: character "&amp;" is the first character of a delimiter but occurred as data

   …ldCounter.de/counter11.php?Dominicki&6917"></script>

   ✉

   This message may appear in several cases:

   • You tried to include the "<" character in your page: you should escape it as "&lt;"
   • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
   • Another possibility is that you forgot to close quotes in a previous tag.
8. Line 89, Column 99: required attribute "type" not specified

   …ter.de/counter11.php?Dominicki&6917"></script>

   ✉

   The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

   Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

9. Line 95, Column 83: cannot generate system identifier for general entity "eba"

   …://maxi-ad.de/ma/mad2.php?Dominicki&eba=frame" width="160" height="600" name=

   ✉

   An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

   Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

   If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

   Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

10. Line 95, Column 83: general entity "eba" not defined and no default entity

    …://maxi-ad.de/ma/mad2.php?Dominicki&eba=frame" width="160" height="600" name=

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

11. Line 95, Column 86: reference not terminated by REFC delimiter

    …maxi-ad.de/ma/mad2.php?Dominicki&eba=frame" width="160" height="600" name="ma

    ✉

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

12. Line 95, Column 86: reference to external entity in attribute value

    …maxi-ad.de/ma/mad2.php?Dominicki&eba=frame" width="160" height="600" name="ma

    ✉

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

13. Line 95, Column 86: reference to entity "eba" for which no system identifier could be generated

    …maxi-ad.de/ma/mad2.php?Dominicki&eba=frame" width="160" height="600" name="ma

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

14. Line 95, Column 81: entity was defined here

    …tp://maxi-ad.de/ma/mad2.php?Dominicki&eba=frame" width="160" height="600" nam

15. Line 95, Column 151: Attribute "allowtransparency" is not a valid attribute

    …00" name="maxiad" allowtransparency="true" frameborder="0" scrolling=no margi

    ✉

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

16. Line 95, Column 184: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

    …cy="true" frameborder="0" scrolling=no marginheight="0" marginwidth="0"></ifr

    ✉

17. Line 121, Column 86: cannot generate system identifier for general entity "ti"

    …tebesucher.de/textads.php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&i

    ✉

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

18. Line 121, Column 86: general entity "ti" not defined and no default entity

    …tebesucher.de/textads.php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&i

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

19. Line 121, Column 88: reference not terminated by REFC delimiter

    …besucher.de/textads.php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=

    ✉

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

20. Line 121, Column 88: reference to external entity in attribute value

    …besucher.de/textads.php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=

    ✉

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

21. Line 121, Column 88: reference to entity "ti" for which no system identifier could be generated

    …besucher.de/textads.php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

22. Line 121, Column 84: entity was defined here

    …chtebesucher.de/textads.php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1

23. Line 121, Column 96: cannot generate system identifier for general entity "txt"

    ….de/textads.php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c=

    ✉

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

24. Line 121, Column 96: general entity "txt" not defined and no default entity

    ….de/textads.php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c=

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

25. Line 121, Column 99: reference not terminated by REFC delimiter

    …/textads.php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="><

    ✉

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

26. Line 121, Column 99: reference to external entity in attribute value

    …/textads.php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="><

    ✉

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

27. Line 121, Column 99: reference to entity "txt" for which no system identifier could be generated

    …/textads.php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="><

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

28. Line 121, Column 94: entity was defined here

    …er.de/textads.php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&

29. Line 121, Column 107: cannot generate system identifier for general entity "bg"

    ….php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

    ✉

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

30. Line 121, Column 107: general entity "bg" not defined and no default entity

    ….php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

31. Line 121, Column 109: reference not terminated by REFC delimiter

    …hp?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

    ✉

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

32. Line 121, Column 109: reference to external entity in attribute value

    …hp?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

    ✉

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

33. Line 121, Column 109: reference to entity "bg" for which no system identifier could be generated

    …hp?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

34. Line 121, Column 105: entity was defined here

    …ds.php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></scri…

35. Line 121, Column 117: cannot generate system identifier for general entity "s"

    …00ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

    ✉

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

36. Line 121, Column 117: general entity "s" not defined and no default entity

    …00ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

37. Line 121, Column 118: reference not terminated by REFC delimiter

    …0ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

    ✉

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

38. Line 121, Column 118: reference to external entity in attribute value

    …0ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

    ✉

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

39. Line 121, Column 118: reference to entity "s" for which no system identifier could be generated

    …0ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

40. Line 121, Column 115: entity was defined here

    …0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

41. Line 121, Column 121: cannot generate system identifier for general entity "nw"

    …&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

    ✉

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

42. Line 121, Column 121: general entity "nw" not defined and no default entity

    …&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

43. Line 121, Column 123: reference not terminated by REFC delimiter

    …i=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

    ✉

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

44. Line 121, Column 123: reference to external entity in attribute value

    …i=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

    ✉

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

45. Line 121, Column 123: reference to entity "nw" for which no system identifier could be generated

    …i=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

46. Line 121, Column 119: entity was defined here

    …ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

47. Line 121, Column 126: cannot generate system identifier for general entity "id"

    …00000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

    ✉

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

48. Line 121, Column 126: general entity "id" not defined and no default entity

    …00000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

49. Line 121, Column 128: reference not terminated by REFC delimiter

    …000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

    ✉

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

50. Line 121, Column 128: reference to external entity in attribute value

    …000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

    ✉

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

51. Line 121, Column 128: reference to entity "id" for which no system identifier could be generated

    …000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

52. Line 121, Column 124: entity was defined here

    …=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

53. Line 121, Column 135: cannot generate system identifier for general entity "c"

    …=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

    ✉

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

54. Line 121, Column 135: general entity "c" not defined and no default entity

    …=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

55. Line 121, Column 136: reference not terminated by REFC delimiter

    …000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

    ✉

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

56. Line 121, Column 136: reference to external entity in attribute value

    …000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

    ✉

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

57. Line 121, Column 136: reference to entity "c" for which no system identifier could be generated

    …000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

58. Line 121, Column 133: entity was defined here

    …xt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

59. Line 121, Column 138: required attribute "type" not specified

    …0000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

60. Line 146, Column 28: document type does not allow element "div" here

    								<div align="center"><tr>

    ✉

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

61. Line 146, Column 32: document type does not allow element "tr" here; assuming missing "table" start-tag

    								<div align="center"><tr>

    ✉

62. Line 148, Column 88: reference not terminated by REFC delimiter

    …maxi-ad.de/ma/mad8.php?Dominicki&eba=frame" width="160" height="500" name="ma

    ✉

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

63. Line 148, Column 88: reference to external entity in attribute value

    …maxi-ad.de/ma/mad8.php?Dominicki&eba=frame" width="160" height="500" name="ma

    ✉

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

64. Line 148, Column 88: reference to entity "eba" for which no system identifier could be generated

    …maxi-ad.de/ma/mad8.php?Dominicki&eba=frame" width="160" height="500" name="ma

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

65. Line 95, Column 81: entity was defined here

    …tp://maxi-ad.de/ma/mad2.php?Dominicki&eba=frame" width="160" height="600" nam

66. Line 148, Column 186: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

    …cy="true" frameborder="0" scrolling=no marginheight="0" marginwidth="0"></ifr

    ✉

67. Line 151, Column 19: end tag for "table" omitted, but OMITTAG NO was specified

    								</tr></div>

    ✉

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

68. Line 146, Column 28: start tag was here

    								<div align="center"><tr>

69. Line 166, Column 71: reference not terminated by REFC delimiter

    …://www.pro.fuchs-world.de/index.php?a=page&id=Kontaktformular">Kontakt</a></li>

    ✉

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

70. Line 166, Column 71: reference to external entity in attribute value

    …://www.pro.fuchs-world.de/index.php?a=page&id=Kontaktformular">Kontakt</a></li>

    ✉

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

71. Line 166, Column 71: reference to entity "id" for which no system identifier could be generated

    …://www.pro.fuchs-world.de/index.php?a=page&id=Kontaktformular">Kontakt</a></li>

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

72. Line 121, Column 124: entity was defined here

    …=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

73. Line 167, Column 71: reference not terminated by REFC delimiter

    …://www.pro.fuchs-world.de/index.php?a=page&id=Impressum">Impressum/Regeln</a></li>

    ✉

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

74. Line 167, Column 71: reference to external entity in attribute value

    …://www.pro.fuchs-world.de/index.php?a=page&id=Impressum">Impressum/Regeln</a></li>

    ✉

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

75. Line 167, Column 71: reference to entity "id" for which no system identifier could be generated

    …://www.pro.fuchs-world.de/index.php?a=page&id=Impressum">Impressum/Regeln</a></li>

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

76. Line 121, Column 124: entity was defined here

    …=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

77. Line 170, Column 78: Attribute "height" exists, but can not be used for this element.

    …ellspacing="0" cellpadding="0" height="100">

    ✉

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

78. Line 181, Column 134: cannot generate system identifier for general entity "key"

    …"http://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.langfrist

    ✉

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

79. Line 181, Column 134: general entity "key" not defined and no default entity

    …"http://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.langfrist

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

80. Line 181, Column 137: reference not terminated by REFC delimiter

    …tp://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.langfristig-

    ✉

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

81. Line 181, Column 137: reference to external entity in attribute value

    …tp://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.langfristig-

    ✉

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

82. Line 181, Column 137: reference to entity "key" for which no system identifier could be generated

    …tp://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.langfristig-

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

83. Line 181, Column 132: entity was defined here

    …c="http://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.langfri

84. Line 181, Column 151: cannot generate system identifier for general entity "url"

    …bsnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.langfristig-werben.de" alt

    ✉

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

85. Line 181, Column 151: general entity "url" not defined and no default entity

    …bsnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.langfristig-werben.de" alt

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

86. Line 181, Column 154: reference not terminated by REFC delimiter

    …apr.com/?size=T&key=lesC6OlfA9u4&url=http://www.langfristig-werben.de" alt=""

    ✉

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

87. Line 181, Column 154: reference to external entity in attribute value

    …apr.com/?size=T&key=lesC6OlfA9u4&url=http://www.langfristig-werben.de" alt=""

    ✉

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

88. Line 181, Column 154: reference to entity "url" for which no system identifier could be generated

    …apr.com/?size=T&key=lesC6OlfA9u4&url=http://www.langfristig-werben.de" alt=""

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

89. Line 181, Column 149: entity was defined here

    …websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.langfristig-werben.de" a

90. Line 181, Column 233: end tag for "img" omitted, but OMITTAG NO was specified

    …eight="70" width="92" border="0"></a></div>

    ✉

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

91. Line 181, Column 88: start tag was here

    …ick="out('werben');" target="_blank"><img src="http://images.websnapr.com/?si

92. Line 183, Column 7: end tag for "tr" omitted, but OMITTAG NO was specified

    		</td>

    ✉

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

93. Line 175, Column 1: start tag was here

    	<tr>

94. Line 183, Column 7: end tag for "table" omitted, but OMITTAG NO was specified

    		</td>

    ✉

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

95. Line 174: start tag was here

    c<table width="245" align="center" cellpadding="1" cellspacing="1" bgcolor="#8d9c

96. Line 183, Column 7: end tag for "div" omitted, but OMITTAG NO was specified

    		</td>

    ✉

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

97. Line 173, Column 11: start tag was here

    											<div align="center"><!-- Begin featured_member.html -->

98. Line 191, Column 15: end tag for "div" omitted, but OMITTAG NO was specified

    										</td>

    ✉

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

99. Line 158, Column 6: start tag was here

    						<div id="main">

100. Line 273, Column 13: end tag for element "div" which is not open

     							</div>

     ✉

     The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

     If this error occurred in a script section of your document, you should probably read this FAQ entry.

101. Line 276, Column 71: reference not terminated by REFC delimiter

     …o.fuchs-world.de/index.php?a=page&id=Zeitbanner">Zeitbanner/Plugboards</a></…

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

102. Line 276, Column 71: reference to external entity in attribute value

     …o.fuchs-world.de/index.php?a=page&id=Zeitbanner">Zeitbanner/Plugboards</a></…

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

103. Line 276, Column 71: reference to entity "id" for which no system identifier could be generated

     …o.fuchs-world.de/index.php?a=page&id=Zeitbanner">Zeitbanner/Plugboards</a></…

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

104. Line 121, Column 124: entity was defined here

     …=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

105. Line 277, Column 71: reference not terminated by REFC delimiter

     …o.fuchs-world.de/index.php?a=page&id=Screenshotzeitbanner">Screenshotzeitbann

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

106. Line 277, Column 71: reference to external entity in attribute value

     …o.fuchs-world.de/index.php?a=page&id=Screenshotzeitbanner">Screenshotzeitbann

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

107. Line 277, Column 71: reference to entity "id" for which no system identifier could be generated

     …o.fuchs-world.de/index.php?a=page&id=Screenshotzeitbanner">Screenshotzeitbann

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

108. Line 121, Column 124: entity was defined here

     …=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

109. Line 283, Column 20: ID "menu_left" already defined

     											<ul id="menu_left">

     ✉

     An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

110. Line 274, Column 15: ID "menu_left" first defined here

     							<ul id="menu_left">

111. Line 284, Column 75: reference not terminated by REFC delimiter

     …o.fuchs-world.de/index.php?a=page&id=Bannerrotation">Bannerrotation/Bannerbat

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

112. Line 284, Column 75: reference to external entity in attribute value

     …o.fuchs-world.de/index.php?a=page&id=Bannerrotation">Bannerrotation/Bannerbat

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

113. Line 284, Column 75: reference to entity "id" for which no system identifier could be generated

     …o.fuchs-world.de/index.php?a=page&id=Bannerrotation">Bannerrotation/Bannerbat

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

114. Line 121, Column 124: entity was defined here

     …=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

115. Line 285, Column 75: reference not terminated by REFC delimiter

     …o.fuchs-world.de/index.php?a=page&id=Linkkatalog">Linkkatalog <font size="1">

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

116. Line 285, Column 75: reference to external entity in attribute value

     …o.fuchs-world.de/index.php?a=page&id=Linkkatalog">Linkkatalog <font size="1">

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

117. Line 285, Column 75: reference to entity "id" for which no system identifier could be generated

     …o.fuchs-world.de/index.php?a=page&id=Linkkatalog">Linkkatalog <font size="1">

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

118. Line 121, Column 124: entity was defined here

     …=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

119. Line 286, Column 75: reference not terminated by REFC delimiter

     …o.fuchs-world.de/index.php?a=page&id=Linkroboter">Linkroboter/Spamen</a></li>

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

120. Line 286, Column 75: reference to external entity in attribute value

     …o.fuchs-world.de/index.php?a=page&id=Linkroboter">Linkroboter/Spamen</a></li>

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

121. Line 286, Column 75: reference to entity "id" for which no system identifier could be generated

     …o.fuchs-world.de/index.php?a=page&id=Linkroboter">Linkroboter/Spamen</a></li>

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

122. Line 121, Column 124: entity was defined here

     …=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

123. Line 287, Column 75: reference not terminated by REFC delimiter

     …ww.pro.fuchs-world.de/index.php?a=page&id=ExterneZB">Externe Zeitbanner</a></li>

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

124. Line 287, Column 75: reference to external entity in attribute value

     …ww.pro.fuchs-world.de/index.php?a=page&id=ExterneZB">Externe Zeitbanner</a></li>

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

125. Line 287, Column 75: reference to entity "id" for which no system identifier could be generated

     …ww.pro.fuchs-world.de/index.php?a=page&id=ExterneZB">Externe Zeitbanner</a></li>

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

126. Line 121, Column 124: entity was defined here

     …=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

127. Line 288, Column 75: reference not terminated by REFC delimiter

     …ww.pro.fuchs-world.de/index.php?a=page&id=Spiderliste">Spiderliste</a></li>

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

128. Line 288, Column 75: reference to external entity in attribute value

     …ww.pro.fuchs-world.de/index.php?a=page&id=Spiderliste">Spiderliste</a></li>

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

129. Line 288, Column 75: reference to entity "id" for which no system identifier could be generated

     …ww.pro.fuchs-world.de/index.php?a=page&id=Spiderliste">Spiderliste</a></li>

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

130. Line 121, Column 124: entity was defined here

     …=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

131. Line 289, Column 75: reference not terminated by REFC delimiter

     …ww.pro.fuchs-world.de/index.php?a=page&id=Napping">Zeitbannernapping</a></li>

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

132. Line 289, Column 75: reference to external entity in attribute value

     …ww.pro.fuchs-world.de/index.php?a=page&id=Napping">Zeitbannernapping</a></li>

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

133. Line 289, Column 75: reference to entity "id" for which no system identifier could be generated

     …ww.pro.fuchs-world.de/index.php?a=page&id=Napping">Zeitbannernapping</a></li>

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

134. Line 121, Column 124: entity was defined here

     …=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

135. Line 290, Column 75: reference not terminated by REFC delimiter

     …o.fuchs-world.de/index.php?a=page&id=Promotionseiten">Zeitbanner-/Promotionse

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

136. Line 290, Column 75: reference to external entity in attribute value

     …o.fuchs-world.de/index.php?a=page&id=Promotionseiten">Zeitbanner-/Promotionse

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

137. Line 290, Column 75: reference to entity "id" for which no system identifier could be generated

     …o.fuchs-world.de/index.php?a=page&id=Promotionseiten">Zeitbanner-/Promotionse

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

138. Line 121, Column 124: entity was defined here

     …=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

139. Line 291, Column 75: reference not terminated by REFC delimiter

     …ww.pro.fuchs-world.de/index.php?a=page&id=Besuchertausch">Besuchertausch</a></li>

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

140. Line 291, Column 75: reference to external entity in attribute value

     …ww.pro.fuchs-world.de/index.php?a=page&id=Besuchertausch">Besuchertausch</a></li>

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

141. Line 291, Column 75: reference to entity "id" for which no system identifier could be generated

     …ww.pro.fuchs-world.de/index.php?a=page&id=Besuchertausch">Besuchertausch</a></li>

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

142. Line 121, Column 124: entity was defined here

     …=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

143. Line 292, Column 75: reference not terminated by REFC delimiter

     …ww.pro.fuchs-world.de/index.php?a=page&id=Bannerpartner">Bannerpartner</a></li>

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

144. Line 292, Column 75: reference to external entity in attribute value

     …ww.pro.fuchs-world.de/index.php?a=page&id=Bannerpartner">Bannerpartner</a></li>

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

145. Line 292, Column 75: reference to entity "id" for which no system identifier could be generated

     …ww.pro.fuchs-world.de/index.php?a=page&id=Bannerpartner">Bannerpartner</a></li>

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

146. Line 121, Column 124: entity was defined here

     …=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

147. Line 293, Column 75: reference not terminated by REFC delimiter

     …ww.pro.fuchs-world.de/index.php?a=page&id=Werbemittel">Werbemittel</a></li>

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

148. Line 293, Column 75: reference to external entity in attribute value

     …ww.pro.fuchs-world.de/index.php?a=page&id=Werbemittel">Werbemittel</a></li>

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

149. Line 293, Column 75: reference to entity "id" for which no system identifier could be generated

     …ww.pro.fuchs-world.de/index.php?a=page&id=Werbemittel">Werbemittel</a></li>

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

150. Line 121, Column 124: entity was defined here

     …=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

151. Line 307, Column 160: Attribute "border" exists, but can not be used for this element.

     …ginheight="0" scrolling="no" border="0" frameborder="0" src="http://www.pro.f

     ✉

     You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

     This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

     How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

152. Line 320, Column 79: required attribute "alt" not specified

     …s/banner_gruen_234x60.gif" border="0"></a>

     ✉

     The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

     Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

153. Line 320, Column 83: end tag for "img" omitted, but OMITTAG NO was specified

     …ner_gruen_234x60.gif" border="0"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

154. Line 320: start tag was here

     <<img src="http://www.emailknecht.de/images/banner_gruen_234x60.gif" border="0"><

155. Line 349, Column 115: character "&amp;" is the first character of a delimiter but occurred as data

     …/s103.histats.com/stats/0.gif?851228&1" alt="free hit counter" border="0"><…

     ✉

     This message may appear in several cases:

     • You tried to include the "<" character in your page: you should escape it as "&lt;"
     • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
     • Another possibility is that you forgot to close quotes in a previous tag.
156. Line 349, Column 156: end tag for "img" omitted, but OMITTAG NO was specified

     …lt="free hit counter" border="0"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

157. Line 349, Column 61: start tag was here

     …p://www.histats.com" target="_blank"><img  src="http://s103.histats.com/stats

158. Line 372, Column 25: Attribute "type" exists, but can not be used for this element.

     											<SCRIPT type='text/javascript' language='JavaScript' src='http://xslt

     ✉

     You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

     This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

     How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

159. Line 372, Column 52: Attribute "language" exists, but can not be used for this element.

     …IPT type='text/javascript' language='JavaScript' src='http://xslt.alexa.com/s

     ✉

     You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

     This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

     How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

160. Line 372, Column 69: Attribute "src" exists, but can not be used for this element.

     …vascript' language='JavaScript' src='http://xslt.alexa.com/site_stats/js/s/a?

     ✉

     You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

     This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

     How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

161. Line 372, Column 137: element "SCRIPT" undefined. Did you mean "script"?

     …s/js/s/a?url=www.pro.fuchs-world.de'></SCRIPT>

     ✉

     You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

     • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
     • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
     • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
162. Line 411, Column 22: Attribute "src" exists, but can not be used for this element.

     										<EMBED src='http://www.space-link.de/counter.swf?idnr=5849' quality=hi

     ✉

     You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

     This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

     How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

163. Line 411, Column 79: Attribute "quality" is not a valid attribute

     …k.de/counter.swf?idnr=5849' quality=high bgcolor=#000000  wmode=transparent  

     ✉

     You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

     This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

     How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

164. Line 411, Column 79: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

     …k.de/counter.swf?idnr=5849' quality=high bgcolor=#000000  wmode=transparent  

     ✉

165. Line 411, Column 92: Attribute "bgcolor" exists, but can not be used for this element.

     …swf?idnr=5849' quality=high bgcolor=#000000  wmode=transparent  menu=false WI

     ✉

     You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

     This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

     How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

166. Line 411, Column 92: an attribute value must be a literal unless it contains only name characters

     …swf?idnr=5849' quality=high bgcolor=#000000  wmode=transparent  menu=false WI

     ✉

     You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

167. Line 411, Column 107: Attribute "wmode" is not a valid attribute. Did you mean "code" or "frameborder"?

     …quality=high bgcolor=#000000  wmode=transparent  menu=false WIDTH=120 HEIGHT=

     ✉

     You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

     This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

     How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

168. Line 411, Column 107: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

     …quality=high bgcolor=#000000  wmode=transparent  menu=false WIDTH=120 HEIGHT=

     ✉

169. Line 411, Column 125: Attribute "menu" is not a valid attribute. Did you mean "onmouseup" or "onmouseout"?

     …or=#000000  wmode=transparent  menu=false WIDTH=120 HEIGHT=50 TYPE='applicati

     ✉

     You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

     This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

     How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

170. Line 411, Column 125: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

     …or=#000000  wmode=transparent  menu=false WIDTH=120 HEIGHT=50 TYPE='applicati

     ✉

171. Line 411, Column 137: Attribute "WIDTH" is not a valid attribute. Did you mean "width"?

     …wmode=transparent  menu=false WIDTH=120 HEIGHT=50 TYPE='application/x-shockwa

     ✉

     You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

     This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

     How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

172. Line 411, Column 137: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

     …wmode=transparent  menu=false WIDTH=120 HEIGHT=50 TYPE='application/x-shockwa

     ✉

173. Line 411, Column 148: Attribute "HEIGHT" is not a valid attribute. Did you mean "height"?

     …parent  menu=false WIDTH=120 HEIGHT=50 TYPE='application/x-shockwave-flash'><

     ✉

     You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

     This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

     How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

174. Line 411, Column 148: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

     …parent  menu=false WIDTH=120 HEIGHT=50 TYPE='application/x-shockwave-flash'><

     ✉

175. Line 411, Column 156: Attribute "TYPE" is not a valid attribute. Did you mean "type"?

     …menu=false WIDTH=120 HEIGHT=50 TYPE='application/x-shockwave-flash'></EMBED>

     ✉

     You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

     This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

     How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

176. Line 411, Column 187: element "EMBED" undefined. Did you mean "meta" or "em"?

     …TYPE='application/x-shockwave-flash'></EMBED>

     ✉

     You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

     • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
     • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
     • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
177. Line 441, Column 186: end tag for "img" omitted, but OMITTAG NO was specified

     …ight="60" width="468" border="0"></a></td>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

178. Line 441, Column 83: start tag was here

     …tp://www.trokey.org" target="_blank"><img src="http://www.pro.fuchs-world.de/

179. Line 444, Column 125: reference not terminated by REFC delimiter

     …tp://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.trokey.org" 

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

180. Line 444, Column 125: reference to external entity in attribute value

     …tp://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.trokey.org" 

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

181. Line 444, Column 125: reference to entity "key" for which no system identifier could be generated

     …tp://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.trokey.org" 

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

182. Line 181, Column 132: entity was defined here

     …c="http://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.langfri

183. Line 444, Column 142: reference not terminated by REFC delimiter

     …apr.com/?size=T&key=lesC6OlfA9u4&url=http://www.trokey.org" alt="" height="70

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

184. Line 444, Column 142: reference to external entity in attribute value

     …apr.com/?size=T&key=lesC6OlfA9u4&url=http://www.trokey.org" alt="" height="70

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

185. Line 444, Column 142: reference to entity "url" for which no system identifier could be generated

     …apr.com/?size=T&key=lesC6OlfA9u4&url=http://www.trokey.org" alt="" height="70

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

186. Line 181, Column 149: entity was defined here

     …websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.langfristig-werben.de" a

187. Line 444, Column 210: end tag for "img" omitted, but OMITTAG NO was specified

     …eight="70" width="92" border="0"></a></div>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

188. Line 444, Column 76: start tag was here

     …lick="out('ahmet');" target="_blank"><img src="http://images.websnapr.com/?si

189. Line 448, Column 132: cannot generate system identifier for general entity "ri"

     …//www.id-societe.com/rank.php?im=16&ri=http://www.trokey.org" border="0" alt=

     ✉

     An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

     Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

     If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

     Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

190. Line 448, Column 132: general entity "ri" not defined and no default entity

     …//www.id-societe.com/rank.php?im=16&ri=http://www.trokey.org" border="0" alt=

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

191. Line 448, Column 134: reference not terminated by REFC delimiter

     …www.id-societe.com/rank.php?im=16&ri=http://www.trokey.org" border="0" alt="P

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

192. Line 448, Column 134: reference to external entity in attribute value

     …www.id-societe.com/rank.php?im=16&ri=http://www.trokey.org" border="0" alt="P

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

193. Line 448, Column 134: reference to entity "ri" for which no system identifier could be generated

     …www.id-societe.com/rank.php?im=16&ri=http://www.trokey.org" border="0" alt="P

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

194. Line 448, Column 130: entity was defined here

     …p://www.id-societe.com/rank.php?im=16&ri=http://www.trokey.org" border="0" al

195. Line 476, Column 188: end tag for "img" omitted, but OMITTAG NO was specified

     …dth="468" height="60" border="0"></a></div>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

196. Line 476, Column 60: start tag was here

     …minicki.orbilook.de" target="_blank"><img src="http://orbilook.de/ol/img/olba

197. Line 520, Column 187: end tag for "img" omitted, but OMITTAG NO was specified

     …ight="60" width="468" border="0"></a></div>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

198. Line 520, Column 63: start tag was here

     …ixuma.de/?ref=18480" target="_blank"><img src="http://www.pro.fuchs-world.de/

199. Line 541, Column 206: end tag for "img" omitted, but OMITTAG NO was specified

     …ight="60" width="468" border="0"></a></td>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

200. Line 541, Column 86: start tag was here

     …//www.kauertweb.com" target="_blank"><img src="http://www.kauertweb.com/asset

201. Line 544, Column 128: reference not terminated by REFC delimiter

     …tp://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.kauertweb.co

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

202. Line 544, Column 128: reference to external entity in attribute value

     …tp://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.kauertweb.co

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

203. Line 544, Column 128: reference to entity "key" for which no system identifier could be generated

     …tp://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.kauertweb.co

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

204. Line 181, Column 132: entity was defined here

     …c="http://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.langfri

205. Line 544, Column 145: reference not terminated by REFC delimiter

     …apr.com/?size=T&key=lesC6OlfA9u4&url=http://www.kauertweb.com" alt="" height=

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

206. Line 544, Column 145: reference to external entity in attribute value

     …apr.com/?size=T&key=lesC6OlfA9u4&url=http://www.kauertweb.com" alt="" height=

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

207. Line 544, Column 145: reference to entity "url" for which no system identifier could be generated

     …apr.com/?size=T&key=lesC6OlfA9u4&url=http://www.kauertweb.com" alt="" height=

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

208. Line 181, Column 149: entity was defined here

     …websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.langfristig-werben.de" a

209. Line 544, Column 216: end tag for "img" omitted, but OMITTAG NO was specified

     …eight="70" width="92" border="0"></a></div>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

210. Line 544, Column 79: start tag was here

     …lick="out('howie');" target="_blank"><img src="http://images.websnapr.com/?si

211. Line 548, Column 134: reference not terminated by REFC delimiter

     …www.id-societe.com/rank.php?im=16&ri=http://www.kauertweb.com" border="0" alt

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

212. Line 548, Column 134: reference to external entity in attribute value

     …www.id-societe.com/rank.php?im=16&ri=http://www.kauertweb.com" border="0" alt

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

213. Line 548, Column 134: reference to entity "ri" for which no system identifier could be generated

     …www.id-societe.com/rank.php?im=16&ri=http://www.kauertweb.com" border="0" alt

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

214. Line 448, Column 130: entity was defined here

     …p://www.id-societe.com/rank.php?im=16&ri=http://www.trokey.org" border="0" al

215. Line 575, Column 185: end tag for "img" omitted, but OMITTAG NO was specified

     …ight="60" width="468" border="0"></a></td>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

216. Line 575, Column 82: start tag was here

     …ttp://www.soyle.net" target="_blank"><img src="http://www.pro.fuchs-world.de/

217. Line 578, Column 130: reference not terminated by REFC delimiter

     …tp://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.soyle.net" a

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

218. Line 578, Column 130: reference to external entity in attribute value

     …tp://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.soyle.net" a

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

219. Line 578, Column 130: reference to entity "key" for which no system identifier could be generated

     …tp://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.soyle.net" a

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

220. Line 181, Column 132: entity was defined here

     …c="http://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.langfri

221. Line 578, Column 147: reference not terminated by REFC delimiter

     …apr.com/?size=T&key=lesC6OlfA9u4&url=http://www.soyle.net" alt="" height="70"

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

222. Line 578, Column 147: reference to external entity in attribute value

     …apr.com/?size=T&key=lesC6OlfA9u4&url=http://www.soyle.net" alt="" height="70"

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

223. Line 578, Column 147: reference to entity "url" for which no system identifier could be generated

     …apr.com/?size=T&key=lesC6OlfA9u4&url=http://www.soyle.net" alt="" height="70"

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

224. Line 181, Column 149: entity was defined here

     …websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.langfristig-werben.de" a

225. Line 578, Column 214: end tag for "img" omitted, but OMITTAG NO was specified

     …eight="70" width="92" border="0"></a></div>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

226. Line 578, Column 81: start tag was here

     …out('datinglinks');" target="_blank"><img src="http://images.websnapr.com/?si

227. Line 582, Column 134: reference not terminated by REFC delimiter

     …www.id-societe.com/rank.php?im=16&ri=http://www.soyle.net" border="0" alt="Pa

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

228. Line 582, Column 134: reference to external entity in attribute value

     …www.id-societe.com/rank.php?im=16&ri=http://www.soyle.net" border="0" alt="Pa

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

229. Line 582, Column 134: reference to entity "ri" for which no system identifier could be generated

     …www.id-societe.com/rank.php?im=16&ri=http://www.soyle.net" border="0" alt="Pa

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

230. Line 448, Column 130: entity was defined here

     …p://www.id-societe.com/rank.php?im=16&ri=http://www.trokey.org" border="0" al

231. Line 609, Column 191: end tag for "img" omitted, but OMITTAG NO was specified

     …ight="60" width="468" border="0"></a></td>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

232. Line 609, Column 88: start tag was here

     …www.damarsohbet.com" target="_blank"><img src="http://www.pro.fuchs-world.de/

233. Line 612, Column 134: reference not terminated by REFC delimiter

     …tp://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.damarsohbet.

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

234. Line 612, Column 134: reference to external entity in attribute value

     …tp://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.damarsohbet.

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

235. Line 612, Column 134: reference to entity "key" for which no system identifier could be generated

     …tp://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.damarsohbet.

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

236. Line 181, Column 132: entity was defined here

     …c="http://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.langfri

237. Line 612, Column 151: reference not terminated by REFC delimiter

     …apr.com/?size=T&key=lesC6OlfA9u4&url=http://www.damarsohbet.com" alt="" heigh

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

238. Line 612, Column 151: reference to external entity in attribute value

     …apr.com/?size=T&key=lesC6OlfA9u4&url=http://www.damarsohbet.com" alt="" heigh

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

239. Line 612, Column 151: reference to entity "url" for which no system identifier could be generated

     …apr.com/?size=T&key=lesC6OlfA9u4&url=http://www.damarsohbet.com" alt="" heigh

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

240. Line 181, Column 149: entity was defined here

     …websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.langfristig-werben.de" a

241. Line 612, Column 224: end tag for "img" omitted, but OMITTAG NO was specified

     …eight="70" width="92" border="0"></a></div>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

242. Line 612, Column 85: start tag was here

     …="out('dasd54a54');" target="_blank"><img src="http://images.websnapr.com/?si

243. Line 616, Column 134: reference not terminated by REFC delimiter

     …www.id-societe.com/rank.php?im=16&ri=http://www.damarsohbet.com" border="0" a

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

244. Line 616, Column 134: reference to external entity in attribute value

     …www.id-societe.com/rank.php?im=16&ri=http://www.damarsohbet.com" border="0" a

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

245. Line 616, Column 134: reference to entity "ri" for which no system identifier could be generated

     …www.id-societe.com/rank.php?im=16&ri=http://www.damarsohbet.com" border="0" a

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

246. Line 448, Column 130: entity was defined here

     …p://www.id-societe.com/rank.php?im=16&ri=http://www.trokey.org" border="0" al

247. Line 643, Column 192: end tag for "img" omitted, but OMITTAG NO was specified

     …ight="60" width="468" border="0"></a></td>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

248. Line 643, Column 84: start tag was here

     …p://www.m-mauser.de" target="_blank"><img src="http://www.m-mauser.de/aubanne

249. Line 646, Column 127: reference not terminated by REFC delimiter

     …tp://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.m-mauser.de"

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

250. Line 646, Column 127: reference to external entity in attribute value

     …tp://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.m-mauser.de"

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

251. Line 646, Column 127: reference to entity "key" for which no system identifier could be generated

     …tp://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.m-mauser.de"

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

252. Line 181, Column 132: entity was defined here

     …c="http://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.langfri

253. Line 646, Column 144: reference not terminated by REFC delimiter

     …apr.com/?size=T&key=lesC6OlfA9u4&url=http://www.m-mauser.de" alt="" height="7

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

254. Line 646, Column 144: reference to external entity in attribute value

     …apr.com/?size=T&key=lesC6OlfA9u4&url=http://www.m-mauser.de" alt="" height="7

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

255. Line 646, Column 144: reference to entity "url" for which no system identifier could be generated

     …apr.com/?size=T&key=lesC6OlfA9u4&url=http://www.m-mauser.de" alt="" height="7

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

256. Line 181, Column 149: entity was defined here

     …websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.langfristig-werben.de" a

257. Line 646, Column 213: end tag for "img" omitted, but OMITTAG NO was specified

     …eight="70" width="92" border="0"></a></div>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

258. Line 646, Column 78: start tag was here

     …ick="out('mauser');" target="_blank"><img src="http://images.websnapr.com/?si

259. Line 650, Column 134: reference not terminated by REFC delimiter

     …www.id-societe.com/rank.php?im=16&ri=http://www.m-mauser.de" border="0" alt="

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

260. Line 650, Column 134: reference to external entity in attribute value

     …www.id-societe.com/rank.php?im=16&ri=http://www.m-mauser.de" border="0" alt="

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

261. Line 650, Column 134: reference to entity "ri" for which no system identifier could be generated

     …www.id-societe.com/rank.php?im=16&ri=http://www.m-mauser.de" border="0" alt="

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

262. Line 448, Column 130: entity was defined here

     …p://www.id-societe.com/rank.php?im=16&ri=http://www.trokey.org" border="0" al

263. Line 678, Column 188: end tag for "img" omitted, but OMITTAG NO was specified

     …dth="468" height="60" border="0"></a></div>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

264. Line 678, Column 60: start tag was here

     …minicki.orbilook.de" target="_blank"><img src="http://orbilook.de/ol/img/olba

265. Line 722, Column 187: end tag for "img" omitted, but OMITTAG NO was specified

     …ight="60" width="468" border="0"></a></div>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

266. Line 722, Column 63: start tag was here

     …ixuma.de/?ref=18480" target="_blank"><img src="http://www.pro.fuchs-world.de/

267. Line 743, Column 235: end tag for "img" omitted, but OMITTAG NO was specified

     …ight="60" width="468" border="0"></a></td>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

268. Line 743, Column 116: start tag was here

     ….php?toplistid=3668" target="_blank"><img src="http://img136.imageshack.us/im

269. Line 746, Column 166: reference not terminated by REFC delimiter

     …tp://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.meinetoplist

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

270. Line 746, Column 166: reference to external entity in attribute value

     …tp://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.meinetoplist

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

271. Line 746, Column 166: reference to entity "key" for which no system identifier could be generated

     …tp://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.meinetoplist

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

272. Line 181, Column 132: entity was defined here

     …c="http://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.langfri

273. Line 746, Column 183: reference not terminated by REFC delimiter

     …apr.com/?size=T&key=lesC6OlfA9u4&url=http://www.meinetopliste.de/toplist.php?

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

274. Line 746, Column 183: reference to external entity in attribute value

     …apr.com/?size=T&key=lesC6OlfA9u4&url=http://www.meinetopliste.de/toplist.php?

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

275. Line 746, Column 183: reference to entity "url" for which no system identifier could be generated

     …apr.com/?size=T&key=lesC6OlfA9u4&url=http://www.meinetopliste.de/toplist.php?

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

276. Line 181, Column 149: entity was defined here

     …websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.langfristig-werben.de" a

277. Line 746, Column 284: end tag for "img" omitted, but OMITTAG NO was specified

     …eight="70" width="92" border="0"></a></div>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

278. Line 746, Column 117: start tag was here

     …t('sexyladyswelt');" target="_blank"><img src="http://images.websnapr.com/?si

279. Line 750, Column 134: reference not terminated by REFC delimiter

     …www.id-societe.com/rank.php?im=16&ri=http://www.meinetopliste.de/toplist.php?

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

280. Line 750, Column 134: reference to external entity in attribute value

     …www.id-societe.com/rank.php?im=16&ri=http://www.meinetopliste.de/toplist.php?

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

281. Line 750, Column 134: reference to entity "ri" for which no system identifier could be generated

     …www.id-societe.com/rank.php?im=16&ri=http://www.meinetopliste.de/toplist.php?

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

282. Line 448, Column 130: entity was defined here

     …p://www.id-societe.com/rank.php?im=16&ri=http://www.trokey.org" border="0" al

283. Line 777, Column 205: end tag for "img" omitted, but OMITTAG NO was specified

     …ight="60" width="468" border="0"></a></td>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

284. Line 777, Column 90: start tag was here

     …w.mauser-werbung.de" target="_blank"><img src="http://www.mauser-werbung.de/a

285. Line 780, Column 134: reference not terminated by REFC delimiter

     …tp://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.mauser-werbu

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

286. Line 780, Column 134: reference to external entity in attribute value

     …tp://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.mauser-werbu

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

287. Line 780, Column 134: reference to entity "key" for which no system identifier could be generated

     …tp://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.mauser-werbu

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

288. Line 181, Column 132: entity was defined here

     …c="http://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.langfri

289. Line 780, Column 151: reference not terminated by REFC delimiter

     …apr.com/?size=T&key=lesC6OlfA9u4&url=http://www.mauser-werbung.de" alt="" hei

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

290. Line 780, Column 151: reference to external entity in attribute value

     …apr.com/?size=T&key=lesC6OlfA9u4&url=http://www.mauser-werbung.de" alt="" hei

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

291. Line 780, Column 151: reference to entity "url" for which no system identifier could be generated

     …apr.com/?size=T&key=lesC6OlfA9u4&url=http://www.mauser-werbung.de" alt="" hei

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

292. Line 181, Column 149: entity was defined here

     …websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.langfristig-werben.de" a

293. Line 780, Column 226: end tag for "img" omitted, but OMITTAG NO was specified

     …eight="70" width="92" border="0"></a></div>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

294. Line 780, Column 85: start tag was here

     …ck="out('werbung');" target="_blank"><img src="http://images.websnapr.com/?si

295. Line 784, Column 134: reference not terminated by REFC delimiter

     …www.id-societe.com/rank.php?im=16&ri=http://www.mauser-werbung.de" border="0"

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

296. Line 784, Column 134: reference to external entity in attribute value

     …www.id-societe.com/rank.php?im=16&ri=http://www.mauser-werbung.de" border="0"

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

297. Line 784, Column 134: reference to entity "ri" for which no system identifier could be generated

     …www.id-societe.com/rank.php?im=16&ri=http://www.mauser-werbung.de" border="0"

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

298. Line 448, Column 130: entity was defined here

     …p://www.id-societe.com/rank.php?im=16&ri=http://www.trokey.org" border="0" al

299. Line 811, Column 199: end tag for "img" omitted, but OMITTAG NO was specified

     …ight="60" width="468" border="0"></a></td>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

300. Line 811, Column 88: start tag was here

     …www.Wissen-Leben.de" target="_blank"><img src="http://www.wissen-leben.de/7Ge

301. Line 814, Column 130: reference not terminated by REFC delimiter

     …tp://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.Wissen-Leben

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

302. Line 814, Column 130: reference to external entity in attribute value

     …tp://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.Wissen-Leben

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

303. Line 814, Column 130: reference to entity "key" for which no system identifier could be generated

     …tp://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.Wissen-Leben

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

304. Line 181, Column 132: entity was defined here

     …c="http://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.langfri

305. Line 814, Column 147: reference not terminated by REFC delimiter

     …apr.com/?size=T&key=lesC6OlfA9u4&url=http://www.Wissen-Leben.de" alt="" heigh

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

306. Line 814, Column 147: reference to external entity in attribute value

     …apr.com/?size=T&key=lesC6OlfA9u4&url=http://www.Wissen-Leben.de" alt="" heigh

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

307. Line 814, Column 147: reference to entity "url" for which no system identifier could be generated

     …apr.com/?size=T&key=lesC6OlfA9u4&url=http://www.Wissen-Leben.de" alt="" heigh

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

308. Line 181, Column 149: entity was defined here

     …websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.langfristig-werben.de" a

309. Line 814, Column 220: end tag for "img" omitted, but OMITTAG NO was specified

     …eight="70" width="92" border="0"></a></div>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

310. Line 814, Column 81: start tag was here

     …lick="out('Degen');" target="_blank"><img src="http://images.websnapr.com/?si

311. Line 818, Column 134: reference not terminated by REFC delimiter

     …www.id-societe.com/rank.php?im=16&ri=http://www.Wissen-Leben.de" border="0" a

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

312. Line 818, Column 134: reference to external entity in attribute value

     …www.id-societe.com/rank.php?im=16&ri=http://www.Wissen-Leben.de" border="0" a

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

313. Line 818, Column 134: reference to entity "ri" for which no system identifier could be generated

     …www.id-societe.com/rank.php?im=16&ri=http://www.Wissen-Leben.de" border="0" a

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

314. Line 448, Column 130: entity was defined here

     …p://www.id-societe.com/rank.php?im=16&ri=http://www.trokey.org" border="0" al

315. Line 845, Column 195: end tag for "img" omitted, but OMITTAG NO was specified

     …ight="60" width="468" border="0"></a></td>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

316. Line 845, Column 83: start tag was here

     …tp://www.bsk1.de.vu" target="_blank"><img src="http://www.repage3.de/memberda

317. Line 848, Column 129: reference not terminated by REFC delimiter

     …tp://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.bsk1.de.vu" 

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

318. Line 848, Column 129: reference to external entity in attribute value

     …tp://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.bsk1.de.vu" 

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

319. Line 848, Column 129: reference to entity "key" for which no system identifier could be generated

     …tp://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.bsk1.de.vu" 

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

320. Line 181, Column 132: entity was defined here

     …c="http://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.langfri

321. Line 848, Column 146: reference not terminated by REFC delimiter

     …apr.com/?size=T&key=lesC6OlfA9u4&url=http://www.bsk1.de.vu" alt="" height="70

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

322. Line 848, Column 146: reference to external entity in attribute value

     …apr.com/?size=T&key=lesC6OlfA9u4&url=http://www.bsk1.de.vu" alt="" height="70

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

323. Line 848, Column 146: reference to entity "url" for which no system identifier could be generated

     …apr.com/?size=T&key=lesC6OlfA9u4&url=http://www.bsk1.de.vu" alt="" height="70

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

324. Line 181, Column 149: entity was defined here

     …websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.langfristig-werben.de" a

325. Line 848, Column 214: end tag for "img" omitted, but OMITTAG NO was specified

     …eight="70" width="92" border="0"></a></div>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

326. Line 848, Column 80: start tag was here

     …="out('Mikesch88');" target="_blank"><img src="http://images.websnapr.com/?si

327. Line 852, Column 134: reference not terminated by REFC delimiter

     …www.id-societe.com/rank.php?im=16&ri=http://www.bsk1.de.vu" border="0" alt="P

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

328. Line 852, Column 134: reference to external entity in attribute value

     …www.id-societe.com/rank.php?im=16&ri=http://www.bsk1.de.vu" border="0" alt="P

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

329. Line 852, Column 134: reference to entity "ri" for which no system identifier could be generated

     …www.id-societe.com/rank.php?im=16&ri=http://www.bsk1.de.vu" border="0" alt="P

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

330. Line 448, Column 130: entity was defined here

     …p://www.id-societe.com/rank.php?im=16&ri=http://www.trokey.org" border="0" al

331. Line 879, Column 197: end tag for "img" omitted, but OMITTAG NO was specified

     …ight="60" width="468" border="0"></a></td>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

332. Line 879, Column 94: start tag was here

     …ngfristig-werben.de" target="_blank"><img src="http://www.pro.fuchs-world.de/

333. Line 882, Column 137: reference not terminated by REFC delimiter

     …tp://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.langfristig-

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

334. Line 882, Column 137: reference to external entity in attribute value

     …tp://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.langfristig-

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

335. Line 882, Column 137: reference to entity "key" for which no system identifier could be generated

     …tp://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.langfristig-

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

336. Line 181, Column 132: entity was defined here

     …c="http://images.websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.langfri

337. Line 882, Column 154: reference not terminated by REFC delimiter

     …apr.com/?size=T&key=lesC6OlfA9u4&url=http://www.langfristig-werben.de" alt=""

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

338. Line 882, Column 154: reference to external entity in attribute value

     …apr.com/?size=T&key=lesC6OlfA9u4&url=http://www.langfristig-werben.de" alt=""

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

339. Line 882, Column 154: reference to entity "url" for which no system identifier could be generated

     …apr.com/?size=T&key=lesC6OlfA9u4&url=http://www.langfristig-werben.de" alt=""

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

340. Line 181, Column 149: entity was defined here

     …websnapr.com/?size=T&key=lesC6OlfA9u4&url=http://www.langfristig-werben.de" a

341. Line 882, Column 233: end tag for "img" omitted, but OMITTAG NO was specified

     …eight="70" width="92" border="0"></a></div>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

342. Line 882, Column 88: start tag was here

     …ick="out('werben');" target="_blank"><img src="http://images.websnapr.com/?si

343. Line 886, Column 134: reference not terminated by REFC delimiter

     …www.id-societe.com/rank.php?im=16&ri=http://www.langfristig-werben.de" border

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

344. Line 886, Column 134: reference to external entity in attribute value

     …www.id-societe.com/rank.php?im=16&ri=http://www.langfristig-werben.de" border

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

345. Line 886, Column 134: reference to entity "ri" for which no system identifier could be generated

     …www.id-societe.com/rank.php?im=16&ri=http://www.langfristig-werben.de" border

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

346. Line 448, Column 130: entity was defined here

     …p://www.id-societe.com/rank.php?im=16&ri=http://www.trokey.org" border="0" al

347. Line 914, Column 188: end tag for "img" omitted, but OMITTAG NO was specified

     …dth="468" height="60" border="0"></a></div>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

348. Line 914, Column 60: start tag was here

     …minicki.orbilook.de" target="_blank"><img src="http://orbilook.de/ol/img/olba

349. Line 958, Column 187: end tag for "img" omitted, but OMITTAG NO was specified

     …ight="60" width="468" border="0"></a></div>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

350. Line 958, Column 63: start tag was here

     …ixuma.de/?ref=18480" target="_blank"><img src="http://www.pro.fuchs-world.de/

351. Line 1064, Column 79: required attribute "alt" not specified

     …s/banner_gruen_468x60.gif" border="0"></a>

     ✉

     The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

     Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

352. Line 1064, Column 83: end tag for "img" omitted, but OMITTAG NO was specified

     …ner_gruen_468x60.gif" border="0"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

353. Line 1064: start tag was here

     <<img src="http://www.emailknecht.de/images/banner_gruen_468x60.gif" border="0"><

354. Line 1092, Column 6: end tag for "br" omitted, but OMITTAG NO was specified

     	<…

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

355. Line 1092, Column 1: start tag was here

     	<br>

356. Line 1162, Column 110: cannot generate system identifier for general entity "einfach"

     … onclick="out('xamax');"><b>schnell&einfach Geld im Internet verdienen</b></a

     ✉

     An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

     Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

     If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

     Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

357. Line 1162, Column 110: general entity "einfach" not defined and no default entity

     … onclick="out('xamax');"><b>schnell&einfach Geld im Internet verdienen</b></a

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

358. Line 1162, Column 117: reference not terminated by REFC delimiter

     …k="out('xamax');"><b>schnell&einfach Geld im Internet verdienen</b></a> - sch

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

359. Line 1162, Column 117: reference to entity "einfach" for which no system identifier could be generated

     …k="out('xamax');"><b>schnell&einfach Geld im Internet verdienen</b></a> - sch

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

360. Line 1162, Column 108: entity was defined here

     …l" onclick="out('xamax');"><b>schnell&einfach Geld im Internet verdienen</b><

361. Line 1162, Column 170: reference not terminated by REFC delimiter

     … verdienen</b></a> - schnell&einfach Geld im Internet verdienen<br />

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

362. Line 1162, Column 170: reference to entity "einfach" for which no system identifier could be generated

     … verdienen</b></a> - schnell&einfach Geld im Internet verdienen<br />

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

363. Line 1162, Column 108: entity was defined here

     …l" onclick="out('xamax');"><b>schnell&einfach Geld im Internet verdienen</b><

364. Line 1197, Column 79: required attribute "alt" not specified

     …s/banner_gruen_468x60.gif" border="0"></a>

     ✉

     The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

     Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

365. Line 1197, Column 83: end tag for "img" omitted, but OMITTAG NO was specified

     …ner_gruen_468x60.gif" border="0"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

366. Line 1197: start tag was here

     <<img src="http://www.emailknecht.de/images/banner_gruen_468x60.gif" border="0"><

367. Line 1225, Column 6: end tag for "br" omitted, but OMITTAG NO was specified

     	<…

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

368. Line 1225, Column 1: start tag was here

     	<br>

369. Line 1360, Column 16: ID "footer" already defined

     						<div id="footer" align="center">

     ✉

     An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

370. Line 1352, Column 16: ID "footer" first defined here

     							<div id="footer">

371. Line 1361, Column 63: reference not terminated by REFC delimiter

     …maxi-ad.de/ma/mad6.php?Dominicki&eba=frame" width="468" height="90" name="max

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

372. Line 1361, Column 63: reference to external entity in attribute value

     …maxi-ad.de/ma/mad6.php?Dominicki&eba=frame" width="468" height="90" name="max

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

373. Line 1361, Column 63: reference to entity "eba" for which no system identifier could be generated

     …maxi-ad.de/ma/mad6.php?Dominicki&eba=frame" width="468" height="90" name="max

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

374. Line 95, Column 81: entity was defined here

     …tp://maxi-ad.de/ma/mad2.php?Dominicki&eba=frame" width="160" height="600" nam

375. Line 1361, Column 160: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

     …cy="true" frameborder="0" scrolling=no marginheight="0" marginwidth="0"></ifr

     ✉

376. Line 1377, Column 194: Attribute "bordercolor" is not a valid attribute

     …hr Besucher" border="1" bordercolor="0"></a>

     ✉

     You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

     This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

     How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

377. Line 1377, Column 201: end tag for "img" omitted, but OMITTAG NO was specified

     …cher" border="1" bordercolor="0"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

378. Line 1377, Column 99: start tag was here

     …e/top-promotion.htm" target="_blank"><img src="http://www.1a-sites.de/banner/

379. Line 1381, Column 153: reference not terminated by REFC delimiter

     …n.at/script/count.php?liste=19499&id=150619" height="31" width="88" border=0>

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

380. Line 1381, Column 153: reference to external entity in attribute value

     …n.at/script/count.php?liste=19499&id=150619" height="31" width="88" border=0>

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

381. Line 1381, Column 153: reference to entity "id" for which no system identifier could be generated

     …n.at/script/count.php?liste=19499&id=150619" height="31" width="88" border=0>

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

382. Line 121, Column 124: entity was defined here

     …=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

383. Line 1381, Column 192: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

     …0619" height="31" width="88" border=0></a>

     ✉

384. Line 1381, Column 193: required attribute "alt" not specified

     …619" height="31" width="88" border=0></a>

     ✉

     The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

     Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

385. Line 1381, Column 197: end tag for "img" omitted, but OMITTAG NO was specified

     … height="31" width="88" border=0></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

386. Line 1381, Column 82: start tag was here

     …/www.topsites100.de" target="_blank"><img src="http://www.free-toplisten.at/s

387. Line 1385, Column 153: reference not terminated by REFC delimiter

     …n.at/script/count.php?liste=19486&id=150620" height="31" width="88" border=0>

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

388. Line 1385, Column 153: reference to external entity in attribute value

     …n.at/script/count.php?liste=19486&id=150620" height="31" width="88" border=0>

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

389. Line 1385, Column 153: reference to entity "id" for which no system identifier could be generated

     …n.at/script/count.php?liste=19486&id=150620" height="31" width="88" border=0>

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

390. Line 121, Column 124: entity was defined here

     …=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

391. Line 1385, Column 192: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

     …0620" height="31" width="88" border=0></a>

     ✉

392. Line 1385, Column 193: required attribute "alt" not specified

     …620" height="31" width="88" border=0></a>

     ✉

     The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

     Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

393. Line 1385, Column 197: end tag for "img" omitted, but OMITTAG NO was specified

     … height="31" width="88" border=0></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

394. Line 1385, Column 82: start tag was here

     …/www.topsites100.de" target="_blank"><img src="http://www.free-toplisten.at/s

395. Line 1389, Column 86: cannot generate system identifier for general entity "tl"

     …6.topsites24.de/ts/ts.cgi?klick=339&tl=Oesi" target="_blank"><img src="http:/

     ✉

     An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

     Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

     If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

     Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

396. Line 1389, Column 86: general entity "tl" not defined and no default entity

     …6.topsites24.de/ts/ts.cgi?klick=339&tl=Oesi" target="_blank"><img src="http:/

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

397. Line 1389, Column 88: reference not terminated by REFC delimiter

     …topsites24.de/ts/ts.cgi?klick=339&tl=Oesi" target="_blank"><img src="http://i

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

398. Line 1389, Column 88: reference to external entity in attribute value

     …topsites24.de/ts/ts.cgi?klick=339&tl=Oesi" target="_blank"><img src="http://i

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

399. Line 1389, Column 88: reference to entity "tl" for which no system identifier could be generated

     …topsites24.de/ts/ts.cgi?klick=339&tl=Oesi" target="_blank"><img src="http://i

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

400. Line 1389, Column 84: entity was defined here

     …ww6.topsites24.de/ts/ts.cgi?klick=339&tl=Oesi" target="_blank"><img src="http

401. Line 1389, Column 224: end tag for "img" omitted, but OMITTAG NO was specified

     …eight="31" width="88" border="0"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

402. Line 1389, Column 110: start tag was here

     …i?klick=339&tl=Oesi" target="_blank"><img src="http://i34.tinypic.com/2a0ao0y

403. Line 1403, Column 60: required attribute "type" not specified

     …enter"><script language="JavaScript">function hit(hitlink) {if(document.image

     ✉

     The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

     Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

404. Line 1405, Column 13: NET-enabling start-tag not immediately followed by null end-tag

     border="0" / ></a>

     ✉

     This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

405. Line 1405, Column 13: end tag for "img" omitted, but OMITTAG NO was specified

     border="0" / ></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

406. Line 1404, Column 149: start tag was here

     …/pa/in.php?id=117')" target="_blank"><img src="http://mauser-auktion.de/partn

407. Line 1413, Column 118: cannot generate system identifier for general entity "account"

     …itoplist/toplist.pl?action=click_in&account=Pro4Free" target="_blank">

     ✉

     An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

     Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

     If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

     Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

408. Line 1413, Column 118: general entity "account" not defined and no default entity

     …itoplist/toplist.pl?action=click_in&account=Pro4Free" target="_blank">

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

409. Line 1413, Column 125: reference not terminated by REFC delimiter

     …t/toplist.pl?action=click_in&account=Pro4Free" target="_blank">

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

410. Line 1413, Column 125: reference to external entity in attribute value

     …t/toplist.pl?action=click_in&account=Pro4Free" target="_blank">

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

411. Line 1413, Column 125: reference to entity "account" for which no system identifier could be generated

     …t/toplist.pl?action=click_in&account=Pro4Free" target="_blank">

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

412. Line 1413, Column 116: entity was defined here

     …initoplist/toplist.pl?action=click_in&account=Pro4Free" target="_blank">

413. Line 1414, Column 124: end tag for "img" omitted, but OMITTAG NO was specified

     …ght="31" alt="Herberts Mini-Top10…

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

414. Line 1414: start tag was here

     "<img border="0" src="http://www.minitopliste.herbertlaass.de/button.gif" width="

415. Line 1424, Column 134: Attribute "src" exists, but can not be used for this element.

     …ing :: BR" target="_blank"><IMG src="http://www.BannerRank.de/br.php?HREF=htt

     ✉

     You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

     This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

     How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

416. Line 1424, Column 202: cannot generate system identifier for general entity "SEC"

     …?HREF=http://www.pro.fuchs-world.de&SEC=183" alt="BannerRank :: Banner-Rankin

     ✉

     An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

     Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

     If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

     Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

417. Line 1424, Column 202: general entity "SEC" not defined and no default entity

     …?HREF=http://www.pro.fuchs-world.de&SEC=183" alt="BannerRank :: Banner-Rankin

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

418. Line 1424, Column 205: reference not terminated by REFC delimiter

     …EF=http://www.pro.fuchs-world.de&SEC=183" alt="BannerRank :: Banner-Ranking :

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

419. Line 1424, Column 205: reference to external entity in attribute value

     …EF=http://www.pro.fuchs-world.de&SEC=183" alt="BannerRank :: Banner-Ranking :

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

420. Line 1424, Column 205: reference to entity "SEC" for which no system identifier could be generated

     …EF=http://www.pro.fuchs-world.de&SEC=183" alt="BannerRank :: Banner-Ranking :

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

421. Line 1424, Column 200: entity was defined here

     …hp?HREF=http://www.pro.fuchs-world.de&SEC=183" alt="BannerRank :: Banner-Rank

422. Line 1424, Column 215: Attribute "alt" exists, but can not be used for this element.

     …www.pro.fuchs-world.de&SEC=183" alt="BannerRank :: Banner-Ranking :: BR" heig

     ✉

     You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

     This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

     How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

423. Line 1424, Column 259: Attribute "height" exists, but can not be used for this element.

     …ank :: Banner-Ranking :: BR" height="31" width="88" border=0></a>

     ✉

     You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

     This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

     How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

424. Line 1424, Column 270: Attribute "width" exists, but can not be used for this element.

     …er-Ranking :: BR" height="31" width="88" border=0></a>

     ✉

     You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

     This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

     How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

425. Line 1424, Column 282: Attribute "border" exists, but can not be used for this element.

     …: BR" height="31" width="88" border=0></a>

     ✉

     You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

     This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

     How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

426. Line 1424, Column 282: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

     …: BR" height="31" width="88" border=0></a>

     ✉

427. Line 1424, Column 283: element "IMG" undefined. Did you mean "img"?

     … BR" height="31" width="88" border=0></a>

     ✉

     You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

     • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
     • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
     • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
428. Line 1424, Column 287: end tag for "IMG" omitted, but OMITTAG NO was specified

     … height="31" width="88" border=0></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

429. Line 1424, Column 124: start tag was here

     …anner-Ranking :: BR" target="_blank"><IMG src="http://www.BannerRank.de/br.ph

430. Line 1432, Column 60: required attribute "type" not specified

     …enter"><script language="JavaScript">function hit(hitlink) {if(document.image

     ✉

     The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

     Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

431. Line 1433, Column 233: end tag for "img" omitted, but OMITTAG NO was specified

     …f" alt="Toplist 2009" border="0"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

432. Line 1433, Column 139: start tag was here

     …ist/in.php?id=198')" target="_blank"><img src="http://www.bannerdreams.de/ban

433. Line 1463, Column 89: reference not terminated by REFC delimiter

     …c.de/topliste/count.php?liste=417&id=38081" target="_blank"><img src="http://

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

434. Line 1463, Column 89: reference to external entity in attribute value

     …c.de/topliste/count.php?liste=417&id=38081" target="_blank"><img src="http://

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

435. Line 1463, Column 89: reference to entity "id" for which no system identifier could be generated

     …c.de/topliste/count.php?liste=417&id=38081" target="_blank"><img src="http://

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

436. Line 121, Column 124: entity was defined here

     …=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

437. Line 1463, Column 187: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

     ….gif" height="31" width="88" border=0></a>

     ✉

438. Line 1463, Column 188: required attribute "alt" not specified

     …gif" height="31" width="88" border=0></a>

     ✉

     The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

     Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

439. Line 1463, Column 192: end tag for "img" omitted, but OMITTAG NO was specified

     … height="31" width="88" border=0></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

440. Line 1463, Column 112: start tag was here

     …?liste=417&id=38081" target="_blank"><img src="http://www.mercedes6.de/eden.g

441. Line 1467, Column 60: required attribute "type" not specified

     …enter"><script language="JavaScript">function hit(hitlink) {if(document.image

     ✉

     The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

     Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

442. Line 1468, Column 209: end tag for "img" omitted, but OMITTAG NO was specified

     …if" alt="MetaTopList" border="0"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

443. Line 1468, Column 122: start tag was here

     …n.de/in.php?id=60')" target="_blank"><img src="http://topliste.metaman.de/img

444. Line 1472, Column 60: required attribute "type" not specified

     …enter"><script language="JavaScript">function hit(hitlink) {if(document.image

     ✉

     The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

     Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

445. Line 1473, Column 212: end tag for "img" omitted, but OMITTAG NO was specified

     …wk.gif" alt="PAGE100" border="0"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

446. Line 1473, Column 113: start tag was here

     ….de/in.php?id=194')" target="_blank"><img src="http://s3.directupload.net/ima

447. Line 1477, Column 237: end tag for "img" omitted, but OMITTAG NO was specified

     …8" height="31" border="0" alt=""></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

448. Line 1477, Column 122: start tag was here

     …in.cgi?4B4D3D3838264C734B3D31333133"><img src="http://www.toplistenhoster.com

449. Line 1481, Column 247: end tag for "img" omitted, but OMITTAG NO was specified

     …lt="Wasserringe~Net Vote-Button"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

450. Line 1481, Column 114: start tag was here

     …gi?6D773D36313426556B7A3D3139303130"><img src="http://www.wasserringe.net/gra

451. Line 1487, Column 263: end tag for "img" omitted, but OMITTAG NO was specified

     …" alt="Zur Hexenkessel-Topliste"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

452. Line 1487, Column 114: start tag was here

     …gi?55733D37393226554D713D3139303131"><img src="http://i220.photobucket.com/al

453. Line 1495, Column 60: required attribute "type" not specified

     …enter"><script language="JavaScript">function hit(hitlink) {if(document.image

     ✉

     The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

     Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

454. Line 1496, Column 266: end tag for "img" omitted, but OMITTAG NO was specified

     …" alt="Jacks Toplist" border="0"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

455. Line 1496, Column 149: start tag was here

     …st6/in.php?id=145')" target="_blank"><img src="http://traffic-trade.de/=host=

456. Line 1520, Column 216: value of attribute "align" cannot be "BOTTOM"; must be one of "top", "middle", "bottom", "left", "right"

     …height="29" width="88" align="BOTTOM" border="0"></a>

     ✉

     The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

457. Line 1520, Column 228: required attribute "alt" not specified

     …width="88" align="BOTTOM" border="0"></a>

     ✉

     The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

     Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

458. Line 1520, Column 232: end tag for "img" omitted, but OMITTAG NO was specified

     …h="88" align="BOTTOM" border="0"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

459. Line 1520, Column 113: start tag was here

     …ner/rein.php?id=230" target="_blank"><img src="http://www.mastermax.de/promo/

460. Line 1527, Column 226: end tag for "img" omitted, but OMITTAG NO was specified

     …="Kostenlos und effektiv werben"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

461. Line 1527, Column 78: start tag was here

     …et="_blank" title="Kostenlos werben"><img src="http://www.besucherland.de/par

462. Line 1607, Column 97: cannot generate system identifier for general entity "b"

     …tes.de/banner/linklist/in.php?id=55&b=2" target="_blank"><img src="http://www

     ✉

     An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

     Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

     If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

     Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

463. Line 1607, Column 97: general entity "b" not defined and no default entity

     …tes.de/banner/linklist/in.php?id=55&b=2" target="_blank"><img src="http://www

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

464. Line 1607, Column 98: reference not terminated by REFC delimiter

     …es.de/banner/linklist/in.php?id=55&b=2" target="_blank"><img src="http://www.

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

465. Line 1607, Column 98: reference to external entity in attribute value

     …es.de/banner/linklist/in.php?id=55&b=2" target="_blank"><img src="http://www.

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

466. Line 1607, Column 98: reference to entity "b" for which no system identifier could be generated

     …es.de/banner/linklist/in.php?id=55&b=2" target="_blank"><img src="http://www.

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

467. Line 1607, Column 95: entity was defined here

     …sites.de/banner/linklist/in.php?id=55&b=2" target="_blank"><img src="http://w

468. Line 1607, Column 229: required attribute "alt" not specified

     … height="15" width="88" border="0" /></a>

     ✉

     The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

     Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

469. Line 1611, Column 80: reference not terminated by REFC delimiter

     …://www.liverank.org/index.php?a=in&u=Pro4Free" target="_blank"><img src="http

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

470. Line 1611, Column 80: reference to external entity in attribute value

     …://www.liverank.org/index.php?a=in&u=Pro4Free" target="_blank"><img src="http

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

471. Line 1611, Column 80: reference to entity "u" for which no system identifier could be generated

     …://www.liverank.org/index.php?a=in&u=Pro4Free" target="_blank"><img src="http

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

472. Line 25, Column 59: entity was defined here

       image.src= 'http://www.pro.fuchs-world.de/index.php?a=out&u=' + username;

473. Line 1619, Column 363: end tag for "img" omitted, but OMITTAG NO was specified

     …icherplatz, Counter und mehr..."></a><!-- Backlink Topliste Ende -->

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

474. Line 1619, Column 201: start tag was here

     …, Free-Counter, Domains und mehr..."><img src="http://www.adm24.net/pr-toplis

475. Line 1623, Column 224: end tag for "img" omitted, but OMITTAG NO was specified

     …eight="15" width="88" border="0"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

476. Line 1623, Column 95: start tag was here

     …de" title="Pagerank" target="_blank"><img src="http://www.mr-rank.de/mr.php?r

477. Line 1627, Column 183: cannot generate system identifier for general entity "style"

     …al.de/pr.php?ref=pro.fuchs-world.de&style=1"

     ✉

     An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

     Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

     If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

     Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

478. Line 1627, Column 183: general entity "style" not defined and no default entity

     …al.de/pr.php?ref=pro.fuchs-world.de&style=1"

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

479. Line 1627, Column 188: reference not terminated by REFC delimiter

     …/pr.php?ref=pro.fuchs-world.de&style=1"

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

480. Line 1627, Column 188: reference to external entity in attribute value

     …/pr.php?ref=pro.fuchs-world.de&style=1"

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

481. Line 1627, Column 188: reference to entity "style" for which no system identifier could be generated

     …/pr.php?ref=pro.fuchs-world.de&style=1"

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

482. Line 1627, Column 181: entity was defined here

     …laal.de/pr.php?ref=pro.fuchs-world.de&style=1"

483. Line 1628, Column 84: end tag for "img" omitted, but OMITTAG NO was specified

     …eight="15" width="88" border="0"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

484. Line 1627, Column 123: start tag was here

     …nzeige ohne Toolbar" target="_blank"><img src="http://www.laal.de/pr.php?ref=

485. Line 1636, Column 327: reference not terminated by REFC delimiter

     …/pr.php?ref=pro.fuchs-world.de&style=1" alt="ss4w.de Tool:  kostenloser Count

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

486. Line 1636, Column 327: reference to external entity in attribute value

     …/pr.php?ref=pro.fuchs-world.de&style=1" alt="ss4w.de Tool:  kostenloser Count

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

487. Line 1636, Column 327: reference to entity "style" for which no system identifier could be generated

     …/pr.php?ref=pro.fuchs-world.de&style=1" alt="ss4w.de Tool:  kostenloser Count

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

488. Line 1627, Column 181: entity was defined here

     …laal.de/pr.php?ref=pro.fuchs-world.de&style=1"

489. Line 1640, Column 229: reference not terminated by REFC delimiter

     …/pr.php?ref=pro.fuchs-world.de&style=1" 

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

490. Line 1640, Column 229: reference to external entity in attribute value

     …/pr.php?ref=pro.fuchs-world.de&style=1" 

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

491. Line 1640, Column 229: reference to entity "style" for which no system identifier could be generated

     …/pr.php?ref=pro.fuchs-world.de&style=1" 

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

492. Line 1627, Column 181: entity was defined here

     …laal.de/pr.php?ref=pro.fuchs-world.de&style=1"

493. Line 1641, Column 127: end tag for "img" omitted, but OMITTAG NO was specified

     …eight="15" width="88" border="0"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

494. Line 1640, Column 164: start tag was here

     …nzeige ohne Toolbar" target="_blank"><img src="http://www.zuuk.de/pr.php?ref=

495. Line 1651, Column 450: end tag for "img" omitted, but OMITTAG NO was specified

     …i http://www.backlink-clever.de"></a><!-- http://www.backlink-clever.de Backl

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

496. Line 1651, Column 209: start tag was here

     …s bei http://www.backlink-clever.de"><img src="http://www.backlink-clever.de/

497. Line 1663, Column 377: end tag for "img" omitted, but OMITTAG NO was specified

     …eight="15" width="88" border="0"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

498. Line 1663, Column 176: start tag was here

     …se Pagerank Service" target="_blank"><img src="http://www.promotion-center.de

499. Line 1667, Column 122: character "&amp;" is the first character of a delimiter but occurred as data

     ….net - Kostenlose Seitenstatistiken & mehr!" target="_blank"><img src="http:/

     ✉

     This message may appear in several cases:

     • You tried to include the "<" character in your page: you should escape it as "&lt;"
     • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
     • Another possibility is that you forgot to close quotes in a previous tag.
500. Line 1667, Column 271: character "&amp;" is the first character of a delimiter but occurred as data

     ….net - Kostenlose Seitenstatistiken & mehr!" height="15" width="88" border="0

     ✉

     This message may appear in several cases:

     • You tried to include the "<" character in your page: you should escape it as "&lt;"
     • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
     • Another possibility is that you forgot to close quotes in a previous tag.
501. Line 1667, Column 317: end tag for "img" omitted, but OMITTAG NO was specified

     …eight="15" width="88" border="0"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

502. Line 1667, Column 146: start tag was here

     …statistiken & mehr!" target="_blank"><img src="http://www.online-team.net/pr.

503. Line 1671, Column 209: reference not terminated by REFC delimiter

     …/pr.php?ref=pro.fuchs-world.de&style=1"

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

504. Line 1671, Column 209: reference to external entity in attribute value

     …/pr.php?ref=pro.fuchs-world.de&style=1"

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

505. Line 1671, Column 209: reference to entity "style" for which no system identifier could be generated

     …/pr.php?ref=pro.fuchs-world.de&style=1"

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

506. Line 1627, Column 181: entity was defined here

     …laal.de/pr.php?ref=pro.fuchs-world.de&style=1"

507. Line 1672, Column 91: end tag for "img" omitted, but OMITTAG NO was specified

     …eight="15" width="88" border="0"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

508. Line 1671, Column 137: start tag was here

     …nzeige ohne Toolbar" target="_blank"><img src="http://www.lerchendal.org/pr.p

509. Line 1680, Column 39: Attribute "HREF" is not a valid attribute. Did you mean "href"?

     										<div align="center"><A HREF='http://www.linkpartner.findet-sucht.de' T

     ✉

     You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

     This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

     How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

510. Line 1680, Column 87: Attribute "TARGET" is not a valid attribute. Did you mean "target"?

     …linkpartner.findet-sucht.de' TARGET='_blank'><IMG SRC='http://www.linkpartner

     ✉

     You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

     This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

     How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

511. Line 1680, Column 95: element "A" undefined. Did you mean "a"?

     …ner.findet-sucht.de' TARGET='_blank'><IMG SRC='http://www.linkpartner.findet-

     ✉

     You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

     • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
     • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
     • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
512. Line 1680, Column 105: Attribute "SRC" is not a valid attribute. Did you mean "src"?

     …-sucht.de' TARGET='_blank'><IMG SRC='http://www.linkpartner.findet-sucht.de/8

     ✉

     You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

     This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

     How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

513. Line 1680, Column 157: Attribute "ALT" is not a valid attribute. Did you mean "alt"?

     …partner.findet-sucht.de/80.gif' ALT='suchen - finden - gefunden werden.' heig

     ✉

     You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

     This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

     How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

514. Line 1680, Column 224: Attribute "BORDER" is not a valid attribute. Did you mean "border"?

     …den.' height="15" width="88" BORDER=0></a>

     ✉

     You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

     This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

     How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

515. Line 1680, Column 224: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

     …den.' height="15" width="88" BORDER=0></a>

     ✉

516. Line 1680, Column 225: element "IMG" undefined. Did you mean "img"?

     …en.' height="15" width="88" BORDER=0></a>

     ✉

     You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

     • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
     • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
     • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
517. Line 1680, Column 229: end tag for element "a" which is not open

     … height="15" width="88" BORDER=0></a>

     ✉

     The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

     If this error occurred in a script section of your document, you should probably read this FAQ entry.

518. Line 1681, Column 17: end tag for "IMG" omitted, but OMITTAG NO was specified

     											</div>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

519. Line 1680, Column 95: start tag was here

     …ner.findet-sucht.de' TARGET='_blank'><IMG SRC='http://www.linkpartner.findet-

520. Line 1681, Column 17: end tag for "A" omitted, but OMITTAG NO was specified

     											</div>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

521. Line 1680, Column 30: start tag was here

     										<div align="center"><A HREF='http://www.linkpartner.findet-sucht.de' T

522. Line 1686, Column 95: reference not terminated by REFC delimiter

     …p/toplist.pl?action=click_in&account=Pro4Free" target="_blank">

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

523. Line 1686, Column 95: reference to external entity in attribute value

     …p/toplist.pl?action=click_in&account=Pro4Free" target="_blank">

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

524. Line 1686, Column 95: reference to entity "account" for which no system identifier could be generated

     …p/toplist.pl?action=click_in&account=Pro4Free" target="_blank">

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

525. Line 1413, Column 116: entity was defined here

     …initoplist/toplist.pl?action=click_in&account=Pro4Free" target="_blank">

526. Line 1687, Column 119: end tag for "img" omitted, but OMITTAG NO was specified

     …"15" alt="Vote für meine Seite !…

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

527. Line 1687: start tag was here

     h<img border="0" src="http://www.megatop.findet-sucht.de/80.gif" width="88" heigh

528. Line 1693, Column 265: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

     …b!!!" height="15" width="88" border=0></a>

     ✉

529. Line 1693, Column 270: end tag for "img" omitted, but OMITTAG NO was specified

     … height="15" width="88" border=0></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

530. Line 1693, Column 115: start tag was here

     …php?site=1254606860" target="_blank"><img src="http://www.tophits.free-topsit

531. Line 1699, Column 256: cannot generate system identifier for general entity "logo"

     …e.php?url_do=www.pro.fuchs-world.de&logo=12" border="0" width="80" height="15

     ✉

     An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

     Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

     If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

     Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

532. Line 1699, Column 256: general entity "logo" not defined and no default entity

     …e.php?url_do=www.pro.fuchs-world.de&logo=12" border="0" width="80" height="15

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

533. Line 1699, Column 260: reference not terminated by REFC delimiter

     …p?url_do=www.pro.fuchs-world.de&logo=12" border="0" width="80" height="15" ti

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

534. Line 1699, Column 260: reference to external entity in attribute value

     …p?url_do=www.pro.fuchs-world.de&logo=12" border="0" width="80" height="15" ti

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

535. Line 1699, Column 260: reference to entity "logo" for which no system identifier could be generated

     …p?url_do=www.pro.fuchs-world.de&logo=12" border="0" width="80" height="15" ti

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

536. Line 1699, Column 254: entity was defined here

     …ste.php?url_do=www.pro.fuchs-world.de&logo=12" border="0" width="80" height="

537. Line 1699, Column 331: required attribute "alt" not specified

     …15" title="Suchmaschinenoptimierung"></a><!-- Backlink Ende -->

     ✉

     The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

     Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

538. Line 1699, Column 335: end tag for "img" omitted, but OMITTAG NO was specified

     …title="Suchmaschinenoptimierung"></a><!-- Backlink Ende -->

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

539. Line 1699, Column 168: start tag was here

     …Ranking-PR Suchmaschinenoptimierung"><img src="http://www.ranklord.de/ranking

540. Line 1703, Column 156: cannot generate system identifier for general entity "domain"

     …"http://www.linkadd.de/pr.php?ani=6&domain=www.pro.fuchs-world.de" height="15

     ✉

     An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

     Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

     If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

     Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

541. Line 1703, Column 156: general entity "domain" not defined and no default entity

     …"http://www.linkadd.de/pr.php?ani=6&domain=www.pro.fuchs-world.de" height="15

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

542. Line 1703, Column 162: reference not terminated by REFC delimiter

     …//www.linkadd.de/pr.php?ani=6&domain=www.pro.fuchs-world.de" height="15" widt

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

543. Line 1703, Column 162: reference to external entity in attribute value

     …//www.linkadd.de/pr.php?ani=6&domain=www.pro.fuchs-world.de" height="15" widt

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

544. Line 1703, Column 162: reference to entity "domain" for which no system identifier could be generated

     …//www.linkadd.de/pr.php?ani=6&domain=www.pro.fuchs-world.de" height="15" widt

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

545. Line 1703, Column 154: entity was defined here

     …c="http://www.linkadd.de/pr.php?ani=6&domain=www.pro.fuchs-world.de" height="

546. Line 1703, Column 255: end tag for "img" omitted, but OMITTAG NO was specified

     …" alt="Suchmaschinenoptimierung"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

547. Line 1703, Column 110: start tag was here

     …ank" title="Suchmaschinen Marketing"><img src="http://www.linkadd.de/pr.php?a

548. Line 1707, Column 171: cannot generate system identifier for general entity "ref"

     ….pagerank-server7.de/pr.php?style=2&ref=pro.fuchs-world.de" 

     ✉

     An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

     Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

     If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

     Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

549. Line 1707, Column 171: general entity "ref" not defined and no default entity

     ….pagerank-server7.de/pr.php?style=2&ref=pro.fuchs-world.de" 

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

550. Line 1707, Column 174: reference not terminated by REFC delimiter

     …gerank-server7.de/pr.php?style=2&ref=pro.fuchs-world.de" 

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

551. Line 1707, Column 174: reference to external entity in attribute value

     …gerank-server7.de/pr.php?style=2&ref=pro.fuchs-world.de" 

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

552. Line 1707, Column 174: reference to entity "ref" for which no system identifier could be generated

     …gerank-server7.de/pr.php?style=2&ref=pro.fuchs-world.de" 

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

553. Line 1707, Column 169: entity was defined here

     …ww.pagerank-server7.de/pr.php?style=2&ref=pro.fuchs-world.de" 

554. Line 1708, Column 63: end tag for "img" omitted, but OMITTAG NO was specified

     …rank - Server7" height="15" width="88" border="0"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

555. Line 1707, Column 114: start tag was here

     …"Pagerank - Server7" target="_blank"><img src="http://www.pagerank-server7.de

556. Line 1712, Column 290: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

     … !!!" height="15" width="88" border=0></a>

     ✉

557. Line 1712, Column 295: end tag for "img" omitted, but OMITTAG NO was specified

     … height="15" width="88" border=0></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

558. Line 1712, Column 126: start tag was here

     …php?site=1254606518" target="_blank"><img src="http://www.list-host.free-tops

559. Line 1716, Column 84: cannot generate system identifier for general entity "bild"

     …://www.spidermich.net/pr.php?id=202&bild=15&extra=1"></script>

     ✉

     An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

     Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

     If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

     Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

560. Line 1716, Column 84: general entity "bild" not defined and no default entity

     …://www.spidermich.net/pr.php?id=202&bild=15&extra=1"></script>

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

561. Line 1716, Column 88: reference not terminated by REFC delimiter

     …ww.spidermich.net/pr.php?id=202&bild=15&extra=1"></script>

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

562. Line 1716, Column 88: reference to external entity in attribute value

     …ww.spidermich.net/pr.php?id=202&bild=15&extra=1"></script>

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

563. Line 1716, Column 88: reference to entity "bild" for which no system identifier could be generated

     …ww.spidermich.net/pr.php?id=202&bild=15&extra=1"></script>

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

564. Line 1716, Column 82: entity was defined here

     …tp://www.spidermich.net/pr.php?id=202&bild=15&extra=1"></script>

565. Line 1716, Column 92: cannot generate system identifier for general entity "extra"

     …pidermich.net/pr.php?id=202&bild=15&extra=1"></script>

     ✉

     An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

     Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

     If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

     Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

566. Line 1716, Column 92: general entity "extra" not defined and no default entity

     …pidermich.net/pr.php?id=202&bild=15&extra=1"></script>

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

567. Line 1716, Column 97: reference not terminated by REFC delimiter

     …mich.net/pr.php?id=202&bild=15&extra=1"></script>

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

568. Line 1716, Column 97: reference to external entity in attribute value

     …mich.net/pr.php?id=202&bild=15&extra=1"></script>

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

569. Line 1716, Column 97: reference to entity "extra" for which no system identifier could be generated

     …mich.net/pr.php?id=202&bild=15&extra=1"></script>

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

570. Line 1716, Column 90: entity was defined here

     ….spidermich.net/pr.php?id=202&bild=15&extra=1"></script>

571. Line 1716, Column 100: required attribute "type" not specified

     …h.net/pr.php?id=202&bild=15&extra=1"></script>

     ✉

     The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

     Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

572. Line 1720, Column 212: reference not terminated by REFC delimiter

     …ter.php?ref=pro.fuchs-world.de&style=a" alt="Spider mich - Seo Pagerank Count

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

573. Line 1720, Column 212: reference to external entity in attribute value

     …ter.php?ref=pro.fuchs-world.de&style=a" alt="Spider mich - Seo Pagerank Count

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

574. Line 1720, Column 212: reference to entity "style" for which no system identifier could be generated

     …ter.php?ref=pro.fuchs-world.de&style=a" alt="Spider mich - Seo Pagerank Count

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

575. Line 1627, Column 181: entity was defined here

     …laal.de/pr.php?ref=pro.fuchs-world.de&style=1"

576. Line 1742, Column 194: reference not terminated by REFC delimiter

     …g.de/pr.php?ref=fuchs-world.de&style=1" alt="Pagerank Backlink - Pagerank Anz

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

577. Line 1742, Column 194: reference to external entity in attribute value

     …g.de/pr.php?ref=fuchs-world.de&style=1" alt="Pagerank Backlink - Pagerank Anz

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

578. Line 1742, Column 194: reference to entity "style" for which no system identifier could be generated

     …g.de/pr.php?ref=fuchs-world.de&style=1" alt="Pagerank Backlink - Pagerank Anz

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

579. Line 1627, Column 181: entity was defined here

     …laal.de/pr.php?ref=pro.fuchs-world.de&style=1"

580. Line 1746, Column 235: reference not terminated by REFC delimiter

     …profi24.info/counter.php?style=1&ref=fuchs-world.de" alt="Backlinkprofi24.inf

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

581. Line 1746, Column 235: reference to external entity in attribute value

     …profi24.info/counter.php?style=1&ref=fuchs-world.de" alt="Backlinkprofi24.inf

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

582. Line 1746, Column 235: reference to entity "ref" for which no system identifier could be generated

     …profi24.info/counter.php?style=1&ref=fuchs-world.de" alt="Backlinkprofi24.inf

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

583. Line 1707, Column 169: entity was defined here

     …ww.pagerank-server7.de/pr.php?style=2&ref=pro.fuchs-world.de" 

584. Line 1754, Column 179: reference not terminated by REFC delimiter

     …k-server7.de/counter.php?style=1&ref=fuchs-world.de" alt="Pagerank - Server7"

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

585. Line 1754, Column 179: reference to external entity in attribute value

     …k-server7.de/counter.php?style=1&ref=fuchs-world.de" alt="Pagerank - Server7"

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

586. Line 1754, Column 179: reference to entity "ref" for which no system identifier could be generated

     …k-server7.de/counter.php?style=1&ref=fuchs-world.de" alt="Pagerank - Server7"

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

587. Line 1707, Column 169: entity was defined here

     …ww.pagerank-server7.de/pr.php?style=2&ref=pro.fuchs-world.de" 

588. Line 1758, Column 208: reference not terminated by REFC delimiter

     ….com/pr.php?ref=fuchs-world.de&style=1" 

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

589. Line 1758, Column 208: reference to external entity in attribute value

     ….com/pr.php?ref=fuchs-world.de&style=1" 

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

590. Line 1758, Column 208: reference to entity "style" for which no system identifier could be generated

     ….com/pr.php?ref=fuchs-world.de&style=1" 

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

591. Line 1627, Column 181: entity was defined here

     …laal.de/pr.php?ref=pro.fuchs-world.de&style=1"

592. Line 1759, Column 94: end tag for "img" omitted, but OMITTAG NO was specified

     …eight="15" width="88" border="0"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

593. Line 1758, Column 140: start tag was here

     …nzeige ohne Toolbar" target="_blank"><img src="http://www.321-prview.com/pr.p

594. Line 1763, Column 247: reference not terminated by REFC delimiter

     …link/pr.php?ref=fuchs-world.de&style=1" 

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

595. Line 1763, Column 247: reference to external entity in attribute value

     …link/pr.php?ref=fuchs-world.de&style=1" 

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

596. Line 1763, Column 247: reference to entity "style" for which no system identifier could be generated

     …link/pr.php?ref=fuchs-world.de&style=1" 

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

597. Line 1627, Column 181: entity was defined here

     …laal.de/pr.php?ref=pro.fuchs-world.de&style=1"

598. Line 1764, Column 111: end tag for "img" omitted, but OMITTAG NO was specified

     …eight="15" width="88" border="0"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

599. Line 1763, Column 168: start tag was here

     …nzeige ohne Toolbar" target="_blank"><img src="http://www.amores24-shop.de/ba

600. Line 1768, Column 240: reference not terminated by REFC delimiter

     …link/pr.php?ref=fuchs-world.de&style=1" 

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

601. Line 1768, Column 240: reference to external entity in attribute value

     …link/pr.php?ref=fuchs-world.de&style=1" 

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

602. Line 1768, Column 240: reference to entity "style" for which no system identifier could be generated

     …link/pr.php?ref=fuchs-world.de&style=1" 

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

603. Line 1627, Column 181: entity was defined here

     …laal.de/pr.php?ref=pro.fuchs-world.de&style=1"

604. Line 1769, Column 116: end tag for "img" omitted, but OMITTAG NO was specified

     …eight="15" width="88" border="0"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

605. Line 1768, Column 167: start tag was here

     …nzeige ohne Toolbar" target="_blank"><img src="http://www.wasoft.org/backlink

606. Line 1773, Column 208: reference not terminated by REFC delimiter

     …info/pr.php?ref=fuchs-world.de&style=1"

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

607. Line 1773, Column 208: reference to external entity in attribute value

     …info/pr.php?ref=fuchs-world.de&style=1"

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

608. Line 1773, Column 208: reference to entity "style" for which no system identifier could be generated

     …info/pr.php?ref=fuchs-world.de&style=1"

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

609. Line 1627, Column 181: entity was defined here

     …laal.de/pr.php?ref=pro.fuchs-world.de&style=1"

610. Line 1774, Column 92: end tag for "img" omitted, but OMITTAG NO was specified

     …eight="15" width="88" border="0"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

611. Line 1773, Column 139: start tag was here

     …nzeige ohne Toolbar" target="_blank"><img src="http://www.rankinghit.info/pr.

612. Line 1778, Column 232: reference not terminated by REFC delimiter

     …link/pr.php?ref=fuchs-world.de&style=1" 

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

613. Line 1778, Column 232: reference to external entity in attribute value

     …link/pr.php?ref=fuchs-world.de&style=1" 

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

614. Line 1778, Column 232: reference to entity "style" for which no system identifier could be generated

     …link/pr.php?ref=fuchs-world.de&style=1" 

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

615. Line 1627, Column 181: entity was defined here

     …laal.de/pr.php?ref=pro.fuchs-world.de&style=1"

616. Line 1779, Column 106: end tag for "img" omitted, but OMITTAG NO was specified

     …eight="15" width="88" border="0"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

617. Line 1778, Column 158: start tag was here

     …nzeige ohne Toolbar" target="_blank"><img src="http://www.lifedate.de/backlin

618. Line 1783, Column 217: reference not terminated by REFC delimiter

     …talog.de/pagerank/pr.php?style=1&ref=fuchs-world.de" 

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

619. Line 1783, Column 217: reference to external entity in attribute value

     …talog.de/pagerank/pr.php?style=1&ref=fuchs-world.de" 

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

620. Line 1783, Column 217: reference to entity "ref" for which no system identifier could be generated

     …talog.de/pagerank/pr.php?style=1&ref=fuchs-world.de" 

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

621. Line 1707, Column 169: entity was defined here

     …ww.pagerank-server7.de/pr.php?style=2&ref=pro.fuchs-world.de" 

622. Line 1784, Column 94: end tag for "img" omitted, but OMITTAG NO was specified

     …eight="15" width="88" border="0"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

623. Line 1783, Column 151: start tag was here

     …nzeige ohne Toolbar" target="_blank"><img src="http://www.eu-webkatalog.de/pa

624. Line 1790, Column 239: reference not terminated by REFC delimiter

     …w.de/pr.php?ref=fuchs-world.de&style=1" 

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

625. Line 1790, Column 239: reference to external entity in attribute value

     …w.de/pr.php?ref=fuchs-world.de&style=1" 

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

626. Line 1790, Column 239: reference to entity "style" for which no system identifier could be generated

     …w.de/pr.php?ref=fuchs-world.de&style=1" 

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

627. Line 1627, Column 181: entity was defined here

     …laal.de/pr.php?ref=pro.fuchs-world.de&style=1"

628. Line 1791, Column 139: end tag for "img" omitted, but OMITTAG NO was specified

     …eight="15" width="88" border="0"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

629. Line 1790, Column 178: start tag was here

     …atistik von ss4w.de" target="_blank"><img src="http://www.ss4w.de/pr.php?ref=

630. Line 1795, Column 202: reference not terminated by REFC delimiter

     …l.eu/pr.php?ref=fuchs-world.de&style=1" 

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

631. Line 1795, Column 202: reference to external entity in attribute value

     …l.eu/pr.php?ref=fuchs-world.de&style=1" 

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

632. Line 1795, Column 202: reference to entity "style" for which no system identifier could be generated

     …l.eu/pr.php?ref=fuchs-world.de&style=1" 

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

633. Line 1627, Column 181: entity was defined here

     …laal.de/pr.php?ref=pro.fuchs-world.de&style=1"

634. Line 1796, Column 94: end tag for "img" omitted, but OMITTAG NO was specified

     …eight="15" width="88" border="0"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

635. Line 1795, Column 137: start tag was here

     …nzeige ohne Toolbar" target="_blank"><img src="http://www.rank4all.eu/pr.php?

636. Line 1800, Column 206: reference not terminated by REFC delimiter

     …chleuder.net/counter.php?style=1&ref=fuchs-world.de" 

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

637. Line 1800, Column 206: reference to external entity in attribute value

     …chleuder.net/counter.php?style=1&ref=fuchs-world.de" 

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

638. Line 1800, Column 206: reference to entity "ref" for which no system identifier could be generated

     …chleuder.net/counter.php?style=1&ref=fuchs-world.de" 

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

639. Line 1707, Column 169: entity was defined here

     …ww.pagerank-server7.de/pr.php?style=2&ref=pro.fuchs-world.de" 

640. Line 1801, Column 94: end tag for "img" omitted, but OMITTAG NO was specified

     …eight="15" width="88" border="0"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

641. Line 1800, Column 143: start tag was here

     …nzeige ohne Toolbar" target="_blank"><img src="http://www.url-schleuder.net/c

642. Line 1805, Column 178: reference not terminated by REFC delimiter

     …l.de/pr.php?ref=fuchs-world.de&style=1" 

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

643. Line 1805, Column 178: reference to external entity in attribute value

     …l.de/pr.php?ref=fuchs-world.de&style=1" 

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

644. Line 1805, Column 178: reference to entity "style" for which no system identifier could be generated

     …l.de/pr.php?ref=fuchs-world.de&style=1" 

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

645. Line 1627, Column 181: entity was defined here

     …laal.de/pr.php?ref=pro.fuchs-world.de&style=1"

646. Line 1806, Column 72: end tag for "img" omitted, but OMITTAG NO was specified

     …klink" height="15" width="88" border="0"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

647. Line 1805, Column 114: start tag was here

     …- Pagerank Backlink" target="_blank"><img src="http://www.hanywal.de/pr.php?r

648. Line 1810, Column 242: reference not terminated by REFC delimiter

     …r.de/pr.php?ref=fuchs-world.de&style=1"  alt="pagerank.promotion-booster.de -

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

649. Line 1810, Column 242: reference to external entity in attribute value

     …r.de/pr.php?ref=fuchs-world.de&style=1"  alt="pagerank.promotion-booster.de -

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

650. Line 1810, Column 242: reference to entity "style" for which no system identifier could be generated

     …r.de/pr.php?ref=fuchs-world.de&style=1"  alt="pagerank.promotion-booster.de -

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

651. Line 1627, Column 181: entity was defined here

     …laal.de/pr.php?ref=pro.fuchs-world.de&style=1"

652. Line 1810, Column 352: end tag for "img" omitted, but OMITTAG NO was specified

     …eight="15" width="88" border="0"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

653. Line 1810, Column 163: start tag was here

     …nzeige ohne Toolbar" target="_blank"><img src="http://pagerank.promotion-boos

654. Line 1814, Column 265: reference not terminated by REFC delimiter

     ….net/pr.php?ref=fuchs-world.de&style=1" 

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

655. Line 1814, Column 265: reference to external entity in attribute value

     ….net/pr.php?ref=fuchs-world.de&style=1" 

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

656. Line 1814, Column 265: reference to entity "style" for which no system identifier could be generated

     ….net/pr.php?ref=fuchs-world.de&style=1" 

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

657. Line 1627, Column 181: entity was defined here

     …laal.de/pr.php?ref=pro.fuchs-world.de&style=1"

658. Line 1815, Column 147: end tag for "img" omitted, but OMITTAG NO was specified

     …eight="15" width="88" border="0"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

659. Line 1814, Column 195: start tag was here

     … SEO Webmaster Tool" target="_blank"><img src="http://www.pagerank-seo.net/pr

660. Line 1819, Column 203: reference not terminated by REFC delimiter

     ….net/pr.php?ref=fuchs-world.de&style=1" 

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

661. Line 1819, Column 203: reference to external entity in attribute value

     ….net/pr.php?ref=fuchs-world.de&style=1" 

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

662. Line 1819, Column 203: reference to entity "style" for which no system identifier could be generated

     ….net/pr.php?ref=fuchs-world.de&style=1" 

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

663. Line 1627, Column 181: entity was defined here

     …laal.de/pr.php?ref=pro.fuchs-world.de&style=1"

664. Line 1820, Column 83: end tag for "img" omitted, but OMITTAG NO was specified

     …eight="15" width="88" border="0"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

665. Line 1819, Column 132: start tag was here

     … SEO Tools and more" target="_blank"><img src="http://www.domain-on-top.net/p

666. Line 1824, Column 81: character "&amp;" is the first character of a delimiter but occurred as data

     …//www.pimpmypr.de" title="Pagerank- & Counterservice" target="_blank"><img sr

     ✉

     This message may appear in several cases:

     • You tried to include the "<" character in your page: you should escape it as "&lt;"
     • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
     • Another possibility is that you forgot to close quotes in a previous tag.
667. Line 1824, Column 184: reference not terminated by REFC delimiter

     …counter.php?ref=fuchs-world.de&style=2" alt="Pagerank- & Counterservice" heig

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

668. Line 1824, Column 184: reference to external entity in attribute value

     …counter.php?ref=fuchs-world.de&style=2" alt="Pagerank- & Counterservice" heig

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

669. Line 1824, Column 184: reference to entity "style" for which no system identifier could be generated

     …counter.php?ref=fuchs-world.de&style=2" alt="Pagerank- & Counterservice" heig

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

670. Line 1627, Column 181: entity was defined here

     …laal.de/pr.php?ref=pro.fuchs-world.de&style=1"

671. Line 1824, Column 203: character "&amp;" is the first character of a delimiter but occurred as data

     …hs-world.de&style=2" alt="Pagerank- & Counterservice" height="15" width="88" 

     ✉

     This message may appear in several cases:

     • You tried to include the "<" character in your page: you should escape it as "&lt;"
     • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
     • Another possibility is that you forgot to close quotes in a previous tag.
672. Line 1828, Column 374: reference not terminated by REFC delimiter

     …counter.php?ref=fuchs-world.de&style=3" alt="list-ranking.com" height="15" wi

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

673. Line 1828, Column 374: reference to external entity in attribute value

     …counter.php?ref=fuchs-world.de&style=3" alt="list-ranking.com" height="15" wi

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

674. Line 1828, Column 374: reference to entity "style" for which no system identifier could be generated

     …counter.php?ref=fuchs-world.de&style=3" alt="list-ranking.com" height="15" wi

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

675. Line 1627, Column 181: entity was defined here

     …laal.de/pr.php?ref=pro.fuchs-world.de&style=1"

676. Line 1832, Column 136: reference not terminated by REFC delimiter

     …l.de/pr.php?ref=fuchs-world.de&style=1" alt="laal.de - Pagerank Anzeige ohne 

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

677. Line 1832, Column 136: reference to external entity in attribute value

     …l.de/pr.php?ref=fuchs-world.de&style=1" alt="laal.de - Pagerank Anzeige ohne 

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

678. Line 1832, Column 136: reference to entity "style" for which no system identifier could be generated

     …l.de/pr.php?ref=fuchs-world.de&style=1" alt="laal.de - Pagerank Anzeige ohne 

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

679. Line 1627, Column 181: entity was defined here

     …laal.de/pr.php?ref=pro.fuchs-world.de&style=1"

680. Line 1832, Column 223: end tag for "img" omitted, but OMITTAG NO was specified

     …eight="15" width="88" border="0"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

681. Line 1832, Column 75: start tag was here

     …"http://www.laal.de" target="_blank"><img src="http://www.laal.de/pr.php?ref=

682. Line 1839, Column 133: reference not terminated by REFC delimiter

     ….net/pr.php?ref=fuchs-world.de&style=1" alt="Vegaconcept.net - Pagerank Anzei

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

683. Line 1839, Column 133: reference to external entity in attribute value

     ….net/pr.php?ref=fuchs-world.de&style=1" alt="Vegaconcept.net - Pagerank Anzei

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

684. Line 1839, Column 133: reference to entity "style" for which no system identifier could be generated

     ….net/pr.php?ref=fuchs-world.de&style=1" alt="Vegaconcept.net - Pagerank Anzei

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

685. Line 1627, Column 181: entity was defined here

     …laal.de/pr.php?ref=pro.fuchs-world.de&style=1"

686. Line 1839, Column 228: end tag for "img" omitted, but OMITTAG NO was specified

     …eight="15" width="88" border="0"></a></div>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

687. Line 1839, Column 64: start tag was here

     …www.vegaconcept.net" target="_blank"><img src="http://www.vegaconcept.net/pr.

688. Line 1842, Column 208: reference not terminated by REFC delimiter

     …counter.php?ref=fuchs-world.de&style=a" alt="Spider mich - Seo Pagerank Count

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

689. Line 1842, Column 208: reference to external entity in attribute value

     …counter.php?ref=fuchs-world.de&style=a" alt="Spider mich - Seo Pagerank Count

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

690. Line 1842, Column 208: reference to entity "style" for which no system identifier could be generated

     …counter.php?ref=fuchs-world.de&style=a" alt="Spider mich - Seo Pagerank Count

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

691. Line 1627, Column 181: entity was defined here

     …laal.de/pr.php?ref=pro.fuchs-world.de&style=1"

692. Line 1846, Column 136: reference not terminated by REFC delimiter

     …y.de/pr.php?ref=fuchs-world.de&style=1" alt="PR4y.de - Pagerank Anzeige ohne 

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

693. Line 1846, Column 136: reference to external entity in attribute value

     …y.de/pr.php?ref=fuchs-world.de&style=1" alt="PR4y.de - Pagerank Anzeige ohne 

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

694. Line 1846, Column 136: reference to entity "style" for which no system identifier could be generated

     …y.de/pr.php?ref=fuchs-world.de&style=1" alt="PR4y.de - Pagerank Anzeige ohne 

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

695. Line 1627, Column 181: entity was defined here

     …laal.de/pr.php?ref=pro.fuchs-world.de&style=1"

696. Line 1846, Column 223: end tag for "img" omitted, but OMITTAG NO was specified

     …eight="15" width="88" border="0"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

697. Line 1846, Column 75: start tag was here

     …"http://www.pr4y.de" target="_blank"><img src="http://www.pr4y.de/pr.php?ref=

698. Line 1850, Column 220: end tag for "img" omitted, but OMITTAG NO was specified

     …eight="15" width="88" border="0"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

699. Line 1850, Column 95: start tag was here

     …de" title="Pagerank" target="_blank"><img src="http://www.mr-rank.de/mr.php?r

700. Line 1854, Column 144: reference not terminated by REFC delimiter

     ….net/pr.php?ref=fuchs-world.de&style=1" alt="Santez - Pagerank Anzeige ohne T

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

701. Line 1854, Column 144: reference to external entity in attribute value

     ….net/pr.php?ref=fuchs-world.de&style=1" alt="Santez - Pagerank Anzeige ohne T

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

702. Line 1854, Column 144: reference to entity "style" for which no system identifier could be generated

     ….net/pr.php?ref=fuchs-world.de&style=1" alt="Santez - Pagerank Anzeige ohne T

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

703. Line 1627, Column 181: entity was defined here

     …laal.de/pr.php?ref=pro.fuchs-world.de&style=1"

704. Line 1854, Column 230: end tag for "img" omitted, but OMITTAG NO was specified

     …eight="15" width="88" border="0"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

705. Line 1854, Column 80: start tag was here

     …://www.beraten24.de" target="_blank"><img src="http://www.santez.net/pr.php?r

706. Line 1963, Column 17: ID "footer" already defined

     							<div id="footer" align="center">

     ✉

     An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

707. Line 1352, Column 16: ID "footer" first defined here

     							<div id="footer">

708. Line 1979, Column 16: ID "footer" already defined

     						<div id="footer">

     ✉

     An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

709. Line 1352, Column 16: ID "footer" first defined here

     							<div id="footer">

710. Line 1984, Column 20: document type does not allow element "td" here

     					<td width="10"></td>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

711. Line 1985, Column 49: document type does not allow element "td" here

     					<td align="center" valign="top" width="120">

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

712. Line 1989, Column 219: end tag for "img" omitted, but OMITTAG NO was specified

     … border="0" alt="GeldCounter.de"></a>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

713. Line 1989, Column 105: start tag was here

     …x.php?ref=Dominicki" target="_blank"><img src="http://www.GeldCounter.de/bann

714. Line 1996, Column 74: cannot generate system identifier for general entity "site"

     …mm-counter.de/counter1.php?user=820&site=1711&bg=9eb1c9&txt=000000"></script>

     ✉

     An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

     Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

     If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

     Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

715. Line 1996, Column 74: general entity "site" not defined and no default entity

     …mm-counter.de/counter1.php?user=820&site=1711&bg=9eb1c9&txt=000000"></script>

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

716. Line 1996, Column 78: reference not terminated by REFC delimiter

     …-counter.de/counter1.php?user=820&site=1711&bg=9eb1c9&txt=000000"></script>

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

717. Line 1996, Column 78: reference to external entity in attribute value

     …-counter.de/counter1.php?user=820&site=1711&bg=9eb1c9&txt=000000"></script>

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

718. Line 1996, Column 78: reference to entity "site" for which no system identifier could be generated

     …-counter.de/counter1.php?user=820&site=1711&bg=9eb1c9&txt=000000"></script>

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

719. Line 1996, Column 72: entity was defined here

     …lamm-counter.de/counter1.php?user=820&site=1711&bg=9eb1c9&txt=000000"></scri…

720. Line 1996, Column 86: reference not terminated by REFC delimiter

     …e/counter1.php?user=820&site=1711&bg=9eb1c9&txt=000000"></script>

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

721. Line 1996, Column 86: reference to external entity in attribute value

     …e/counter1.php?user=820&site=1711&bg=9eb1c9&txt=000000"></script>

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

722. Line 1996, Column 86: reference to entity "bg" for which no system identifier could be generated

     …e/counter1.php?user=820&site=1711&bg=9eb1c9&txt=000000"></script>

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

723. Line 121, Column 105: entity was defined here

     …ds.php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></scri…

724. Line 1996, Column 97: reference not terminated by REFC delimiter

     …php?user=820&site=1711&bg=9eb1c9&txt=000000"></script>

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

725. Line 1996, Column 97: reference to external entity in attribute value

     …php?user=820&site=1711&bg=9eb1c9&txt=000000"></script>

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

726. Line 1996, Column 97: reference to entity "txt" for which no system identifier could be generated

     …php?user=820&site=1711&bg=9eb1c9&txt=000000"></script>

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

727. Line 121, Column 94: entity was defined here

     …er.de/textads.php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&

728. Line 1996, Column 105: required attribute "type" not specified

     …=820&site=1711&bg=9eb1c9&txt=000000"></script>

     ✉

     The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

     Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

729. Line 2019, Column 86: reference not terminated by REFC delimiter

     …maxi-ad.de/ma/mad8.php?Dominicki&eba=frame" width="160" height="500" name="ma

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

730. Line 2019, Column 86: reference to external entity in attribute value

     …maxi-ad.de/ma/mad8.php?Dominicki&eba=frame" width="160" height="500" name="ma

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

731. Line 2019, Column 86: reference to entity "eba" for which no system identifier could be generated

     …maxi-ad.de/ma/mad8.php?Dominicki&eba=frame" width="160" height="500" name="ma

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

732. Line 95, Column 81: entity was defined here

     …tp://maxi-ad.de/ma/mad2.php?Dominicki&eba=frame" width="160" height="600" nam

733. Line 2019, Column 184: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

     …cy="true" frameborder="0" scrolling=no marginheight="0" marginwidth="0"></ifr

     ✉

734. Line 2037, Column 86: reference not terminated by REFC delimiter

     …maxi-ad.de/ma/mad2.php?Dominicki&eba=frame" width="160" height="600" name="ma

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

735. Line 2037, Column 86: reference to external entity in attribute value

     …maxi-ad.de/ma/mad2.php?Dominicki&eba=frame" width="160" height="600" name="ma

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

736. Line 2037, Column 86: reference to entity "eba" for which no system identifier could be generated

     …maxi-ad.de/ma/mad2.php?Dominicki&eba=frame" width="160" height="600" name="ma

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

737. Line 95, Column 81: entity was defined here

     …tp://maxi-ad.de/ma/mad2.php?Dominicki&eba=frame" width="160" height="600" nam

738. Line 2037, Column 184: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

     …cy="true" frameborder="0" scrolling=no marginheight="0" marginwidth="0"></ifr

     ✉

739. Line 2072, Column 88: reference not terminated by REFC delimiter

     …besucher.de/textads.php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

740. Line 2072, Column 88: reference to external entity in attribute value

     …besucher.de/textads.php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

741. Line 2072, Column 88: reference to entity "ti" for which no system identifier could be generated

     …besucher.de/textads.php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

742. Line 121, Column 84: entity was defined here

     …chtebesucher.de/textads.php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1

743. Line 2072, Column 99: reference not terminated by REFC delimiter

     …/textads.php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="><

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

744. Line 2072, Column 99: reference to external entity in attribute value

     …/textads.php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="><

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

745. Line 2072, Column 99: reference to entity "txt" for which no system identifier could be generated

     …/textads.php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="><

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

746. Line 121, Column 94: entity was defined here

     …er.de/textads.php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&

747. Line 2072, Column 109: reference not terminated by REFC delimiter

     …hp?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

748. Line 2072, Column 109: reference to external entity in attribute value

     …hp?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

749. Line 2072, Column 109: reference to entity "bg" for which no system identifier could be generated

     …hp?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

750. Line 121, Column 105: entity was defined here

     …ds.php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></scri…

751. Line 2072, Column 118: reference not terminated by REFC delimiter

     …0ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

752. Line 2072, Column 118: reference to external entity in attribute value

     …0ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

753. Line 2072, Column 118: reference to entity "s" for which no system identifier could be generated

     …0ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

754. Line 121, Column 115: entity was defined here

     …0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

755. Line 2072, Column 123: reference not terminated by REFC delimiter

     …i=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

756. Line 2072, Column 123: reference to external entity in attribute value

     …i=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

757. Line 2072, Column 123: reference to entity "nw" for which no system identifier could be generated

     …i=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

758. Line 121, Column 119: entity was defined here

     …ff&ti=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

759. Line 2072, Column 128: reference not terminated by REFC delimiter

     …000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

760. Line 2072, Column 128: reference to external entity in attribute value

     …000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

761. Line 2072, Column 128: reference to entity "id" for which no system identifier could be generated

     …000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

762. Line 121, Column 124: entity was defined here

     …=000000&txt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

763. Line 2072, Column 136: reference not terminated by REFC delimiter

     …000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

764. Line 2072, Column 136: reference to external entity in attribute value

     …000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

765. Line 2072, Column 136: reference to entity "c" for which no system identifier could be generated

     …000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

766. Line 121, Column 133: entity was defined here

     …xt=000000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

767. Line 2072, Column 138: required attribute "type" not specified

     …0000&bg=ffffcc&s=6&nw=1&id=59895&c="></script>

     ✉

     The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

     Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

768. Line 25, Column 61: XML Parsing Error: EntityRef: expecting ';'

     …ge.src= 'http://www.pro.fuchs-world.de/index.php?a=out&u=' + username;

     ✉

769. Line 89, Column > 80: XML Parsing Error: xmlParseEntityRef: no name

     …http://www.GeldCounter.de/counter11.php?Dominicki&6917"></script>…

     ✉

770. Line 95, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …ttp://maxi-ad.de/ma/mad2.php?Dominicki&eba=frame" width="160" height="600" na…

     ✉

771. Line 95, Column > 80: XML Parsing Error: AttValue: " or ' expected

     …ttp://maxi-ad.de/ma/mad2.php?Dominicki&eba=frame" width="160" height="600" na…

     ✉

772. Line 95, Column > 80: XML Parsing Error: attributes construct error

     …ttp://maxi-ad.de/ma/mad2.php?Dominicki&eba=frame" width="160" height="600" na…

     ✉

773. Line 95, Column > 80: XML Parsing Error: Couldn't find end of Start Tag iframe line 95

     …ttp://maxi-ad.de/ma/mad2.php?Dominicki&eba=frame" width="160" height="600" na…

     ✉

774. Line 95, Column > 80: XML Parsing Error: Opening and ending tag mismatch: div line 95 and iframe

     …ttp://maxi-ad.de/ma/mad2.php?Dominicki&eba=frame" width="160" height="600" na…

     ✉

775. Line 96, Column 17: XML Parsing Error: Opening and ending tag mismatch: td line 94 and div

     											</div>

     ✉

776. Line 97, Column 13: XML Parsing Error: Opening and ending tag mismatch: tr line 93 and td

     								</td>

     ✉

777. Line 98, Column 12: XML Parsing Error: Opening and ending tag mismatch: table line 36 and tr

     							</tr>

     ✉

778. Line 121, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …ww.echtebesucher.de/textads.php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&…

     ✉

779. Line 121, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …ww.echtebesucher.de/textads.php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&…

     ✉

780. Line 121, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …ww.echtebesucher.de/textads.php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&…

     ✉

781. Line 121, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …ww.echtebesucher.de/textads.php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&…

     ✉

782. Line 121, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …ww.echtebesucher.de/textads.php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&…

     ✉

783. Line 121, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …ww.echtebesucher.de/textads.php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&…

     ✉

784. Line 121, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …ww.echtebesucher.de/textads.php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&…

     ✉

785. Line 148, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …"http://maxi-ad.de/ma/mad8.php?Dominicki&eba=frame" width="160" height="500" …

     ✉

786. Line 148, Column > 80: XML Parsing Error: AttValue: " or ' expected

     …"http://maxi-ad.de/ma/mad8.php?Dominicki&eba=frame" width="160" height="500" …

     ✉

787. Line 148, Column > 80: XML Parsing Error: attributes construct error

     …"http://maxi-ad.de/ma/mad8.php?Dominicki&eba=frame" width="160" height="500" …

     ✉

788. Line 148, Column > 80: XML Parsing Error: Couldn't find end of Start Tag iframe line 148

     …"http://maxi-ad.de/ma/mad8.php?Dominicki&eba=frame" width="160" height="500" …

     ✉

789. Line 148, Column > 80: XML Parsing Error: Opening and ending tag mismatch: div line 148 and iframe

     …"http://maxi-ad.de/ma/mad8.php?Dominicki&eba=frame" width="160" height="500" …

     ✉

790. Line 149, Column 18: XML Parsing Error: Opening and ending tag mismatch: td line 147 and div

     												</div>

     ✉

791. Line 150, Column 15: XML Parsing Error: Opening and ending tag mismatch: tr line 146 and td

     										</td>

     ✉

792. Line 151, Column 13: XML Parsing Error: Opening and ending tag mismatch: div line 146 and tr

     								</tr></div>

     ✉

793. Line 152, Column 15: XML Parsing Error: Opening and ending tag mismatch: td line 35 and table

     							</table>

     ✉

794. Line 154, Column 12: XML Parsing Error: Opening and ending tag mismatch: tr line 34 and div

     						</div>

     ✉

795. Line 155, Column 10: XML Parsing Error: Opening and ending tag mismatch: table line 33 and td

     					</td>

     ✉

796. Line 166, Column 70: XML Parsing Error: EntityRef: expecting ';'

     …tp://www.pro.fuchs-world.de/index.php?a=page&id=Kontaktformular">Kontakt</a></li>

     ✉

797. Line 167, Column 70: XML Parsing Error: EntityRef: expecting ';'

     …tp://www.pro.fuchs-world.de/index.php?a=page&id=Impressum">Impressum/Regeln</a></li>

     ✉

798. Line 181, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …de" onclick="out('werben');" target="_blank"><img src="http://images.websnapr…

     ✉

799. Line 181, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …de" onclick="out('werben');" target="_blank"><img src="http://images.websnapr…

     ✉

800. Line 181, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 181 and a

     …de" onclick="out('werben');" target="_blank"><img src="http://images.websnapr…

     ✉

801. Line 181, Column > 80: XML Parsing Error: Opening and ending tag mismatch: a line 181 and div

     …de" onclick="out('werben');" target="_blank"><img src="http://images.websnapr…

     ✉

802. Line 182, Column 7: XML Parsing Error: Opening and ending tag mismatch: div line 180 and td

     		</td>

     ✉

803. Line 276, Column 70: XML Parsing Error: EntityRef: expecting ';'

     …ro.fuchs-world.de/index.php?a=page&id=Zeitbanner">Zeitbanner/Plugboards</a></

     ✉

804. Line 277, Column 70: XML Parsing Error: EntityRef: expecting ';'

     …ro.fuchs-world.de/index.php?a=page&id=Screenshotzeitbanner">Screenshotzeitban

     ✉

805. Line 284, Column 74: XML Parsing Error: EntityRef: expecting ';'

     …ro.fuchs-world.de/index.php?a=page&id=Bannerrotation">Bannerrotation/Bannerba

     ✉

806. Line 285, Column 74: XML Parsing Error: EntityRef: expecting ';'

     …ro.fuchs-world.de/index.php?a=page&id=Linkkatalog">Linkkatalog <font size="1"

     ✉

807. Line 286, Column 74: XML Parsing Error: EntityRef: expecting ';'

     …ro.fuchs-world.de/index.php?a=page&id=Linkroboter">Linkroboter/Spamen</a></…

     ✉

808. Line 287, Column 74: XML Parsing Error: EntityRef: expecting ';'

     …/www.pro.fuchs-world.de/index.php?a=page&id=ExterneZB">Externe Zeitbanner</a></li>

     ✉

809. Line 288, Column 74: XML Parsing Error: EntityRef: expecting ';'

     …/www.pro.fuchs-world.de/index.php?a=page&id=Spiderliste">Spiderliste</a></li>

     ✉

810. Line 289, Column 74: XML Parsing Error: EntityRef: expecting ';'

     …/www.pro.fuchs-world.de/index.php?a=page&id=Napping">Zeitbannernapping</a></li>

     ✉

811. Line 290, Column 74: XML Parsing Error: EntityRef: expecting ';'

     …ro.fuchs-world.de/index.php?a=page&id=Promotionseiten">Zeitbanner-/Promotions

     ✉

812. Line 291, Column 74: XML Parsing Error: EntityRef: expecting ';'

     …ro.fuchs-world.de/index.php?a=page&id=Besuchertausch">Besuchertausch</a></li>

     ✉

813. Line 292, Column 74: XML Parsing Error: EntityRef: expecting ';'

     …/www.pro.fuchs-world.de/index.php?a=page&id=Bannerpartner">Bannerpartner</a></li>

     ✉

814. Line 293, Column 74: XML Parsing Error: EntityRef: expecting ';'

     …/www.pro.fuchs-world.de/index.php?a=page&id=Werbemittel">Werbemittel</a></li>

     ✉

815. Line 320, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 320 and a

     …banner_gruen_234x60.gif" border="0"></a>…

     ✉

816. Line 322, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 319 and div

     											</div>

     ✉

817. Line 323, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 318 and td

     									</td>

     ✉

818. Line 324, Column 13: XML Parsing Error: Opening and ending tag mismatch: td line 317 and tr

     								</tr>

     ✉

819. Line 349, Column > 80: XML Parsing Error: xmlParseEntityRef: no name

     …" target="_blank"><img  src="http://s103.histats.com/stats/0.gif?851228&1" al…

     ✉

820. Line 349, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 349 and a

     …" target="_blank"><img  src="http://s103.histats.com/stats/0.gif?851228&1" al…

     ✉

821. Line 350, Column 22: XML Parsing Error: Opening and ending tag mismatch: a line 349 and noscript

     											</noscript>

     ✉

822. Line 351, Column 43: XML Parsing Error: Opening and ending tag mismatch: noscript line 348 and div

     											<!-- Histats.com  END  --></div>

     ✉

823. Line 352, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 340 and td

     									</td>

     ✉

824. Line 353, Column 13: XML Parsing Error: Opening and ending tag mismatch: td line 339 and tr

     								</tr>

     ✉

825. Line 411, Column 78: XML Parsing Error: AttValue: " or ' expected

     …nk.de/counter.swf?idnr=5849' quality=high bgcolor=#000000  wmode=transparent 

     ✉

826. Line 411, Column 78: XML Parsing Error: attributes construct error

     …nk.de/counter.swf?idnr=5849' quality=high bgcolor=#000000  wmode=transparent 

     ✉

827. Line 411, Column 78: XML Parsing Error: Couldn't find end of Start Tag EMBED line 411

     …nk.de/counter.swf?idnr=5849' quality=high bgcolor=#000000  wmode=transparent 

     ✉

828. Line 411, Column > 80: XML Parsing Error: Opening and ending tag mismatch: div line 410 and EMBED

     ….de/counter.swf?idnr=5849' quality=high bgcolor=#000000  wmode=transparent  m…

     ✉

829. Line 412, Column 17: XML Parsing Error: Opening and ending tag mismatch: td line 409 and div

     											</div>

     ✉

830. Line 413, Column 14: XML Parsing Error: Opening and ending tag mismatch: tr line 408 and td

     									</td>

     ✉

831. Line 415, Column 15: XML Parsing Error: Opening and ending tag mismatch: tr line 316 and table

     							</table>

     ✉

832. Line 423, Column 13: XML Parsing Error: Opening and ending tag mismatch: table line 303 and div

     							</div>

     ✉

833. Line 441, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 441 and a

     …"http://www.trokey.org" target="_blank"><img src="http://www.pro.fuchs-world.…

     ✉

834. Line 441, Column > 80: XML Parsing Error: Opening and ending tag mismatch: a line 441 and td

     …"http://www.trokey.org" target="_blank"><img src="http://www.pro.fuchs-world.…

     ✉

835. Line 444, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …="out('ahmet');" target="_blank"><img src="http://images.websnapr.com/?size=T…

     ✉

836. Line 444, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …="out('ahmet');" target="_blank"><img src="http://images.websnapr.com/?size=T…

     ✉

837. Line 444, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 444 and a

     …="out('ahmet');" target="_blank"><img src="http://images.websnapr.com/?size=T…

     ✉

838. Line 444, Column > 80: XML Parsing Error: Opening and ending tag mismatch: a line 444 and div

     …="out('ahmet');" target="_blank"><img src="http://images.websnapr.com/?size=T…

     ✉

839. Line 445, Column 7: XML Parsing Error: Opening and ending tag mismatch: div line 443 and td

     		</td>

     ✉

840. Line 448, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …get="_blank" title="PageRank button"><img src="http://www.id-societe.com/rank…

     ✉

841. Line 450, Column 6: XML Parsing Error: Opening and ending tag mismatch: td line 442 and tr

     	</tr>

     ✉

842. Line 462, Column 13: XML Parsing Error: Opening and ending tag mismatch: td line 441 and table

     </tr></table>

     ✉

843. Line 476, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 476 and a

     … target="_blank"><img src="http://orbilook.de/ol/img/olbanner1.png" title="Or…

     ✉

844. Line 476, Column > 80: XML Parsing Error: Opening and ending tag mismatch: a line 476 and div

     … target="_blank"><img src="http://orbilook.de/ol/img/olbanner1.png" title="Or…

     ✉

845. Line 477, Column 8: XML Parsing Error: Opening and ending tag mismatch: div line 475 and td

     			</td>

     ✉

846. Line 478, Column 7: XML Parsing Error: Opening and ending tag mismatch: td line 474 and tr

     		</tr>

     ✉

847. Line 520, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 520 and a

     …80" target="_blank"><img src="http://www.pro.fuchs-world.de/Werbung/Eigene_We…

     ✉

848. Line 520, Column > 80: XML Parsing Error: Opening and ending tag mismatch: a line 520 and div

     …80" target="_blank"><img src="http://www.pro.fuchs-world.de/Werbung/Eigene_We…

     ✉

849. Line 521, Column 8: XML Parsing Error: Opening and ending tag mismatch: div line 519 and td

     			</td>

     ✉

850. Line 522, Column 7: XML Parsing Error: Opening and ending tag mismatch: td line 518 and tr

     		</tr>

     ✉

851. Line 523, Column 9: XML Parsing Error: Opening and ending tag mismatch: tr line 517 and table

     	</table>

     ✉

852. Line 524, Column 9: XML Parsing Error: Opening and ending tag mismatch: tr line 473 and center

     </center><br />

     ✉

853. Line 541, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 541 and a

     …"http://www.kauertweb.com" target="_blank"><img src="http://www.kauertweb.com…

     ✉

854. Line 541, Column > 80: XML Parsing Error: Opening and ending tag mismatch: a line 541 and td

     …"http://www.kauertweb.com" target="_blank"><img src="http://www.kauertweb.com…

     ✉

855. Line 544, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …ick="out('howie');" target="_blank"><img src="http://images.websnapr.com/?siz…

     ✉

856. Line 544, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …ick="out('howie');" target="_blank"><img src="http://images.websnapr.com/?siz…

     ✉

857. Line 544, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 544 and a

     …ick="out('howie');" target="_blank"><img src="http://images.websnapr.com/?siz…

     ✉

858. Line 544, Column > 80: XML Parsing Error: Opening and ending tag mismatch: a line 544 and div

     …ick="out('howie');" target="_blank"><img src="http://images.websnapr.com/?siz…

     ✉

859. Line 545, Column 7: XML Parsing Error: Opening and ending tag mismatch: div line 543 and td

     		</td>

     ✉

860. Line 548, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …get="_blank" title="PageRank button"><img src="http://www.id-societe.com/rank…

     ✉

861. Line 550, Column 6: XML Parsing Error: Opening and ending tag mismatch: td line 542 and tr

     	</tr>

     ✉

862. Line 562, Column 13: XML Parsing Error: Opening and ending tag mismatch: td line 541 and table

     </tr></table>

     ✉

863. Line 575, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 575 and a

     …"http://www.soyle.net" target="_blank"><img src="http://www.pro.fuchs-world.d…

     ✉

864. Line 575, Column > 80: XML Parsing Error: Opening and ending tag mismatch: a line 575 and td

     …"http://www.soyle.net" target="_blank"><img src="http://www.pro.fuchs-world.d…

     ✉

865. Line 578, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …"out('datinglinks');" target="_blank"><img src="http://images.websnapr.com/?s…

     ✉

866. Line 578, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …"out('datinglinks');" target="_blank"><img src="http://images.websnapr.com/?s…

     ✉

867. Line 578, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 578 and a

     …"out('datinglinks');" target="_blank"><img src="http://images.websnapr.com/?s…

     ✉

868. Line 578, Column > 80: XML Parsing Error: Opening and ending tag mismatch: a line 578 and div

     …"out('datinglinks');" target="_blank"><img src="http://images.websnapr.com/?s…

     ✉

869. Line 579, Column 7: XML Parsing Error: Opening and ending tag mismatch: div line 577 and td

     		</td>

     ✉

870. Line 582, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …get="_blank" title="PageRank button"><img src="http://www.id-societe.com/rank…

     ✉

871. Line 584, Column 6: XML Parsing Error: Opening and ending tag mismatch: td line 576 and tr

     	</tr>

     ✉

872. Line 596, Column 13: XML Parsing Error: Opening and ending tag mismatch: td line 575 and table

     </tr></table>

     ✉

873. Line 609, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 609 and a

     …"http://www.damarsohbet.com" target="_blank"><img src="http://www.pro.fuchs-w…

     ✉

874. Line 609, Column > 80: XML Parsing Error: Opening and ending tag mismatch: a line 609 and td

     …"http://www.damarsohbet.com" target="_blank"><img src="http://www.pro.fuchs-w…

     ✉

875. Line 612, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …click="out('dasd54a54');" target="_blank"><img src="http://images.websnapr.co…

     ✉

876. Line 612, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …click="out('dasd54a54');" target="_blank"><img src="http://images.websnapr.co…

     ✉

877. Line 612, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 612 and a

     …click="out('dasd54a54');" target="_blank"><img src="http://images.websnapr.co…

     ✉

878. Line 612, Column > 80: XML Parsing Error: Opening and ending tag mismatch: a line 612 and div

     …click="out('dasd54a54');" target="_blank"><img src="http://images.websnapr.co…

     ✉

879. Line 613, Column 7: XML Parsing Error: Opening and ending tag mismatch: div line 611 and td

     		</td>

     ✉

880. Line 616, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …get="_blank" title="PageRank button"><img src="http://www.id-societe.com/rank…

     ✉

881. Line 618, Column 6: XML Parsing Error: Opening and ending tag mismatch: td line 610 and tr

     	</tr>

     ✉

882. Line 630, Column 13: XML Parsing Error: Opening and ending tag mismatch: td line 609 and table

     </tr></table>

     ✉

883. Line 643, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 643 and a

     …"http://www.m-mauser.de" target="_blank"><img src="http://www.m-mauser.de/aub…

     ✉

884. Line 643, Column > 80: XML Parsing Error: Opening and ending tag mismatch: a line 643 and td

     …"http://www.m-mauser.de" target="_blank"><img src="http://www.m-mauser.de/aub…

     ✉

885. Line 646, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …k="out('mauser');" target="_blank"><img src="http://images.websnapr.com/?size…

     ✉

886. Line 646, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …k="out('mauser');" target="_blank"><img src="http://images.websnapr.com/?size…

     ✉

887. Line 646, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 646 and a

     …k="out('mauser');" target="_blank"><img src="http://images.websnapr.com/?size…

     ✉

888. Line 646, Column > 80: XML Parsing Error: Opening and ending tag mismatch: a line 646 and div

     …k="out('mauser');" target="_blank"><img src="http://images.websnapr.com/?size…

     ✉

889. Line 647, Column 7: XML Parsing Error: Opening and ending tag mismatch: div line 645 and td

     		</td>

     ✉

890. Line 650, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …get="_blank" title="PageRank button"><img src="http://www.id-societe.com/rank…

     ✉

891. Line 652, Column 6: XML Parsing Error: Opening and ending tag mismatch: td line 644 and tr

     	</tr>

     ✉

892. Line 664, Column 13: XML Parsing Error: Opening and ending tag mismatch: td line 643 and table

     </tr></table>

     ✉

893. Line 678, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 678 and a

     … target="_blank"><img src="http://orbilook.de/ol/img/olbanner1.png" title="Or…

     ✉

894. Line 678, Column > 80: XML Parsing Error: Opening and ending tag mismatch: a line 678 and div

     … target="_blank"><img src="http://orbilook.de/ol/img/olbanner1.png" title="Or…

     ✉

895. Line 679, Column 8: XML Parsing Error: Opening and ending tag mismatch: div line 677 and td

     			</td>

     ✉

896. Line 680, Column 7: XML Parsing Error: Opening and ending tag mismatch: td line 676 and tr

     		</tr>

     ✉

897. Line 722, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 722 and a

     …80" target="_blank"><img src="http://www.pro.fuchs-world.de/Werbung/Eigene_We…

     ✉

898. Line 722, Column > 80: XML Parsing Error: Opening and ending tag mismatch: a line 722 and div

     …80" target="_blank"><img src="http://www.pro.fuchs-world.de/Werbung/Eigene_We…

     ✉

899. Line 723, Column 8: XML Parsing Error: Opening and ending tag mismatch: div line 721 and td

     			</td>

     ✉

900. Line 724, Column 7: XML Parsing Error: Opening and ending tag mismatch: td line 720 and tr

     		</tr>

     ✉

901. Line 725, Column 9: XML Parsing Error: Opening and ending tag mismatch: tr line 719 and table

     	</table>

     ✉

902. Line 726, Column 9: XML Parsing Error: Opening and ending tag mismatch: tr line 675 and center

     </center><br />

     ✉

903. Line 743, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 743 and a

     …"http://www.meinetopliste.de/toplist.php?toplistid=3668" target="_blank"><img…

     ✉

904. Line 743, Column > 80: XML Parsing Error: Opening and ending tag mismatch: a line 743 and td

     …"http://www.meinetopliste.de/toplist.php?toplistid=3668" target="_blank"><img…

     ✉

905. Line 746, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …plist.php?toplistid=3668" onclick="out('sexyladyswelt');" target="_blank"><im…

     ✉

906. Line 746, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …plist.php?toplistid=3668" onclick="out('sexyladyswelt');" target="_blank"><im…

     ✉

907. Line 746, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 746 and a

     …plist.php?toplistid=3668" onclick="out('sexyladyswelt');" target="_blank"><im…

     ✉

908. Line 746, Column > 80: XML Parsing Error: Opening and ending tag mismatch: a line 746 and div

     …plist.php?toplistid=3668" onclick="out('sexyladyswelt');" target="_blank"><im…

     ✉

909. Line 747, Column 7: XML Parsing Error: Opening and ending tag mismatch: div line 745 and td

     		</td>

     ✉

910. Line 750, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …get="_blank" title="PageRank button"><img src="http://www.id-societe.com/rank…

     ✉

911. Line 752, Column 6: XML Parsing Error: Opening and ending tag mismatch: td line 744 and tr

     	</tr>

     ✉

912. Line 764, Column 13: XML Parsing Error: Opening and ending tag mismatch: td line 743 and table

     </tr></table>

     ✉

913. Line 777, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 777 and a

     …"http://www.mauser-werbung.de" target="_blank"><img src="http://www.mauser-we…

     ✉

914. Line 777, Column > 80: XML Parsing Error: Opening and ending tag mismatch: a line 777 and td

     …"http://www.mauser-werbung.de" target="_blank"><img src="http://www.mauser-we…

     ✉

915. Line 780, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …onclick="out('werbung');" target="_blank"><img src="http://images.websnapr.co…

     ✉

916. Line 780, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …onclick="out('werbung');" target="_blank"><img src="http://images.websnapr.co…

     ✉

917. Line 780, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 780 and a

     …onclick="out('werbung');" target="_blank"><img src="http://images.websnapr.co…

     ✉

918. Line 780, Column > 80: XML Parsing Error: Opening and ending tag mismatch: a line 780 and div

     …onclick="out('werbung');" target="_blank"><img src="http://images.websnapr.co…

     ✉

919. Line 781, Column 7: XML Parsing Error: Opening and ending tag mismatch: div line 779 and td

     		</td>

     ✉

920. Line 784, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …get="_blank" title="PageRank button"><img src="http://www.id-societe.com/rank…

     ✉

921. Line 786, Column 6: XML Parsing Error: Opening and ending tag mismatch: td line 778 and tr

     	</tr>

     ✉

922. Line 798, Column 13: XML Parsing Error: Opening and ending tag mismatch: td line 777 and table

     </tr></table>

     ✉

923. Line 811, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 811 and a

     …"http://www.Wissen-Leben.de" target="_blank"><img src="http://www.wissen-lebe…

     ✉

924. Line 811, Column > 80: XML Parsing Error: Opening and ending tag mismatch: a line 811 and td

     …"http://www.Wissen-Leben.de" target="_blank"><img src="http://www.wissen-lebe…

     ✉

925. Line 814, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …click="out('Degen');" target="_blank"><img src="http://images.websnapr.com/?s…

     ✉

926. Line 814, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …click="out('Degen');" target="_blank"><img src="http://images.websnapr.com/?s…

     ✉

927. Line 814, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 814 and a

     …click="out('Degen');" target="_blank"><img src="http://images.websnapr.com/?s…

     ✉

928. Line 814, Column > 80: XML Parsing Error: Opening and ending tag mismatch: a line 814 and div

     …click="out('Degen');" target="_blank"><img src="http://images.websnapr.com/?s…

     ✉

929. Line 815, Column 7: XML Parsing Error: Opening and ending tag mismatch: div line 813 and td

     		</td>

     ✉

930. Line 818, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …get="_blank" title="PageRank button"><img src="http://www.id-societe.com/rank…

     ✉

931. Line 820, Column 6: XML Parsing Error: Opening and ending tag mismatch: td line 812 and tr

     	</tr>

     ✉

932. Line 832, Column 13: XML Parsing Error: Opening and ending tag mismatch: td line 811 and table

     </tr></table>

     ✉

933. Line 845, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 845 and a

     …"http://www.bsk1.de.vu" target="_blank"><img src="http://www.repage3.de/membe…

     ✉

934. Line 845, Column > 80: XML Parsing Error: Opening and ending tag mismatch: a line 845 and td

     …"http://www.bsk1.de.vu" target="_blank"><img src="http://www.repage3.de/membe…

     ✉

935. Line 848, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …="out('Mikesch88');" target="_blank"><img src="http://images.websnapr.com/?si…

     ✉

936. Line 848, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …="out('Mikesch88');" target="_blank"><img src="http://images.websnapr.com/?si…

     ✉

937. Line 848, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 848 and a

     …="out('Mikesch88');" target="_blank"><img src="http://images.websnapr.com/?si…

     ✉

938. Line 848, Column > 80: XML Parsing Error: Opening and ending tag mismatch: a line 848 and div

     …="out('Mikesch88');" target="_blank"><img src="http://images.websnapr.com/?si…

     ✉

939. Line 849, Column 7: XML Parsing Error: Opening and ending tag mismatch: div line 847 and td

     		</td>

     ✉

940. Line 852, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …get="_blank" title="PageRank button"><img src="http://www.id-societe.com/rank…

     ✉

941. Line 854, Column 6: XML Parsing Error: Opening and ending tag mismatch: td line 846 and tr

     	</tr>

     ✉

942. Line 866, Column 13: XML Parsing Error: Opening and ending tag mismatch: td line 845 and table

     </tr></table>

     ✉

943. Line 879, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 879 and a

     …"http://www.langfristig-werben.de" target="_blank"><img src="http://www.pro.f…

     ✉

944. Line 879, Column > 80: XML Parsing Error: Opening and ending tag mismatch: a line 879 and td

     …"http://www.langfristig-werben.de" target="_blank"><img src="http://www.pro.f…

     ✉

945. Line 882, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …de" onclick="out('werben');" target="_blank"><img src="http://images.websnapr…

     ✉

946. Line 882, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …de" onclick="out('werben');" target="_blank"><img src="http://images.websnapr…

     ✉

947. Line 882, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 882 and a

     …de" onclick="out('werben');" target="_blank"><img src="http://images.websnapr…

     ✉

948. Line 882, Column > 80: XML Parsing Error: Opening and ending tag mismatch: a line 882 and div

     …de" onclick="out('werben');" target="_blank"><img src="http://images.websnapr…

     ✉

949. Line 883, Column 7: XML Parsing Error: Opening and ending tag mismatch: div line 881 and td

     		</td>

     ✉

950. Line 886, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …get="_blank" title="PageRank button"><img src="http://www.id-societe.com/rank…

     ✉

951. Line 888, Column 6: XML Parsing Error: Opening and ending tag mismatch: td line 880 and tr

     	</tr>

     ✉

952. Line 900, Column 13: XML Parsing Error: Opening and ending tag mismatch: td line 879 and table

     </tr></table>

     ✉

953. Line 914, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 914 and a

     … target="_blank"><img src="http://orbilook.de/ol/img/olbanner1.png" title="Or…

     ✉

954. Line 914, Column > 80: XML Parsing Error: Opening and ending tag mismatch: a line 914 and div

     … target="_blank"><img src="http://orbilook.de/ol/img/olbanner1.png" title="Or…

     ✉

955. Line 915, Column 8: XML Parsing Error: Opening and ending tag mismatch: div line 913 and td

     			</td>

     ✉

956. Line 916, Column 7: XML Parsing Error: Opening and ending tag mismatch: td line 912 and tr

     		</tr>

     ✉

957. Line 958, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 958 and a

     …80" target="_blank"><img src="http://www.pro.fuchs-world.de/Werbung/Eigene_We…

     ✉

958. Line 958, Column > 80: XML Parsing Error: Opening and ending tag mismatch: a line 958 and div

     …80" target="_blank"><img src="http://www.pro.fuchs-world.de/Werbung/Eigene_We…

     ✉

959. Line 959, Column 8: XML Parsing Error: Opening and ending tag mismatch: div line 957 and td

     			</td>

     ✉

960. Line 960, Column 7: XML Parsing Error: Opening and ending tag mismatch: td line 956 and tr

     		</tr>

     ✉

961. Line 961, Column 9: XML Parsing Error: Opening and ending tag mismatch: tr line 955 and table

     	</table>

     ✉

962. Line 962, Column 9: XML Parsing Error: Opening and ending tag mismatch: tr line 911 and center

     </center><br />

     ✉

963. Line 1064, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1064 and a

     …banner_gruen_468x60.gif" border="0"></a>…

     ✉

964. Line 1066, Column 11: XML Parsing Error: Opening and ending tag mismatch: a line 1063 and div

     					</div>

     ✉

965. Line 1067, Column 8: XML Parsing Error: Opening and ending tag mismatch: div line 1062 and td

     			</td>

     ✉

966. Line 1068, Column 7: XML Parsing Error: Opening and ending tag mismatch: td line 1061 and tr

     		</tr>

     ✉

967. Line 1091, Column 9: XML Parsing Error: Opening and ending tag mismatch: tr line 1060 and table

     	</table>

     ✉

968. Line 1093, Column 6: XML Parsing Error: Opening and ending tag mismatch: br line 1092 and div

     </div>

     ✉

969. Line 1162, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …://einfachestaschengeld.de.tl" onclick="out('xamax');"><b>schnell&einfach Gel…

     ✉

970. Line 1162, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …://einfachestaschengeld.de.tl" onclick="out('xamax');"><b>schnell&einfach Gel…

     ✉

971. Line 1197, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1197 and a

     …banner_gruen_468x60.gif" border="0"></a>…

     ✉

972. Line 1199, Column 11: XML Parsing Error: Opening and ending tag mismatch: a line 1196 and div

     					</div>

     ✉

973. Line 1200, Column 8: XML Parsing Error: Opening and ending tag mismatch: div line 1195 and td

     			</td>

     ✉

974. Line 1201, Column 7: XML Parsing Error: Opening and ending tag mismatch: td line 1194 and tr

     		</tr>

     ✉

975. Line 1224, Column 9: XML Parsing Error: Opening and ending tag mismatch: tr line 1193 and table

     	</table>

     ✉

976. Line 1226, Column 6: XML Parsing Error: Opening and ending tag mismatch: br line 1225 and div

     </div>

     ✉

977. Line 1308, Column 6: XML Parsing Error: Opening and ending tag mismatch: table line 1177 and div

     </div>

     ✉

978. Line 1351, Column 13: XML Parsing Error: Opening and ending tag mismatch: table line 1044 and div

     							</div>

     ✉

979. Line 1361, Column 62: XML Parsing Error: EntityRef: expecting ';'

     …/maxi-ad.de/ma/mad6.php?Dominicki&eba=frame" width="468" height="90" name="ma

     ✉

980. Line 1361, Column > 80: XML Parsing Error: AttValue: " or ' expected

     …6.php?Dominicki&eba=frame" width="468" height="90" name="maxiad" allowtranspa…

     ✉

981. Line 1361, Column > 80: XML Parsing Error: attributes construct error

     …6.php?Dominicki&eba=frame" width="468" height="90" name="maxiad" allowtranspa…

     ✉

982. Line 1361, Column > 80: XML Parsing Error: Couldn't find end of Start Tag iframe line 1361

     …6.php?Dominicki&eba=frame" width="468" height="90" name="maxiad" allowtranspa…

     ✉

983. Line 1361, Column > 80: XML Parsing Error: Opening and ending tag mismatch: div line 1360 and iframe

     …6.php?Dominicki&eba=frame" width="468" height="90" name="maxiad" allowtranspa…

     ✉

984. Line 1365, Column 70: XML Parsing Error: attributes construct error

     …href="http://toplist.files-load.com/"target="_blank"><img src="http://toplist

     ✉

985. Line 1365, Column 70: XML Parsing Error: Couldn't find end of Start Tag a line 1365

     …href="http://toplist.files-load.com/"target="_blank"><img src="http://toplist

     ✉

986. Line 1365, Column > 80: XML Parsing Error: attributes construct error

     …://toplist.files-load.com/"target="_blank"><img src="http://toplist.files-loa…

     ✉

987. Line 1365, Column > 80: XML Parsing Error: Couldn't find end of Start Tag img line 1365

     …://toplist.files-load.com/"target="_blank"><img src="http://toplist.files-loa…

     ✉

988. Line 1365, Column > 80: XML Parsing Error: Opening and ending tag mismatch: div line 1365 and a

     …://toplist.files-load.com/"target="_blank"><img src="http://toplist.files-loa…

     ✉

989. Line 1366, Column 17: XML Parsing Error: Opening and ending tag mismatch: td line 1364 and div

     											</div>

     ✉

990. Line 1367, Column 14: XML Parsing Error: Opening and ending tag mismatch: tr line 1363 and td

     									</td>

     ✉

991. Line 1373, Column 71: XML Parsing Error: attributes construct error

     …ref="http://www.european-toplist.de/"target="_blank"><img src="http://www.eur

     ✉

992. Line 1373, Column 71: XML Parsing Error: Couldn't find end of Start Tag a line 1373

     …ref="http://www.european-toplist.de/"target="_blank"><img src="http://www.eur

     ✉

993. Line 1373, Column > 80: XML Parsing Error: Opening and ending tag mismatch: div line 1373 and a

     …://www.european-toplist.de/"target="_blank"><img src="http://www.european-top…

     ✉

994. Line 1374, Column 17: XML Parsing Error: Opening and ending tag mismatch: td line 1372 and div

     											</div>

     ✉

995. Line 1375, Column 14: XML Parsing Error: Opening and ending tag mismatch: table line 1362 and td

     									</td>

     ✉

996. Line 1377, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1377 and a

     …://topliste.a-b-c.de/top-promotion.htm" target="_blank"><img src="http://www.…

     ✉

997. Line 1378, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1377 and div

     											</div>

     ✉

998. Line 1379, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1377 and td

     									</td>

     ✉

999. Line 1381, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …://www.topsites100.de" target="_blank"><img src="http://www.free-toplisten.at…

     ✉

1000. Line 1381, Column > 80: XML Parsing Error: AttValue: " or ' expected

      …://www.topsites100.de" target="_blank"><img src="http://www.free-toplisten.at…

      ✉

1001. Line 1381, Column > 80: XML Parsing Error: attributes construct error

      …://www.topsites100.de" target="_blank"><img src="http://www.free-toplisten.at…

      ✉

1002. Line 1381, Column > 80: XML Parsing Error: Couldn't find end of Start Tag img line 1381

      …://www.topsites100.de" target="_blank"><img src="http://www.free-toplisten.at…

      ✉

1003. Line 1385, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …://www.topsites100.de" target="_blank"><img src="http://www.free-toplisten.at…

      ✉

1004. Line 1385, Column > 80: XML Parsing Error: AttValue: " or ' expected

      …://www.topsites100.de" target="_blank"><img src="http://www.free-toplisten.at…

      ✉

1005. Line 1385, Column > 80: XML Parsing Error: attributes construct error

      …://www.topsites100.de" target="_blank"><img src="http://www.free-toplisten.at…

      ✉

1006. Line 1385, Column > 80: XML Parsing Error: Couldn't find end of Start Tag img line 1385

      …://www.topsites100.de" target="_blank"><img src="http://www.free-toplisten.at…

      ✉

1007. Line 1389, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …://www6.topsites24.de/ts/ts.cgi?klick=339&tl=Oesi" target="_blank"><img src="…

      ✉

1008. Line 1389, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1389 and a

      …://www6.topsites24.de/ts/ts.cgi?klick=339&tl=Oesi" target="_blank"><img src="…

      ✉

1009. Line 1390, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1389 and div

      											</div>

      ✉

1010. Line 1391, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1389 and td

      									</td>

      ✉

1011. Line 1393, Column 75: XML Parsing Error: attributes construct error

      …"http://backlinks-top.condor-bbs.com"target="_blank"><img src="http://backlin

      ✉

1012. Line 1393, Column 75: XML Parsing Error: Couldn't find end of Start Tag a line 1393

      …"http://backlinks-top.condor-bbs.com"target="_blank"><img src="http://backlin

      ✉

1013. Line 1393, Column > 80: XML Parsing Error: Opening and ending tag mismatch: div line 1393 and a

      …://backlinks-top.condor-bbs.com"target="_blank"><img src="http://backlinks-to…

      ✉

1014. Line 1394, Column 17: XML Parsing Error: Opening and ending tag mismatch: td line 1392 and div

      											</div>

      ✉

1015. Line 1400, Column 13: XML Parsing Error: Opening and ending tag mismatch: td line 1376 and tr

      								</tr>

      ✉

1016. Line 1405, Column 11: XML Parsing Error: error parsing attribute name

      border="0" / ></a>

      ✉

1017. Line 1405, Column 11: XML Parsing Error: attributes construct error

      border="0" / ></a>

      ✉

1018. Line 1405, Column 11: XML Parsing Error: Couldn't find end of Start Tag img line 1404

      border="0" / ></a>

      ✉

1019. Line 1413, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …://www.world-of-herbert.de/cgi-bin/minitoplist/toplist.pl?action=click_in&acc…

      ✉

1020. Line 1415, Column 4: XML Parsing Error: Opening and ending tag mismatch: img line 1414 and a

      </a>

      ✉

1021. Line 1417, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1413 and div

      											</div>

      ✉

1022. Line 1418, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1413 and td

      									</td>

      ✉

1023. Line 1420, Column 77: XML Parsing Error: attributes construct error

      …ttp://www.zweckesschatzinsel.eu/top/"target="_blank"><img src="http://www.zwe

      ✉

1024. Line 1420, Column 77: XML Parsing Error: Couldn't find end of Start Tag a line 1420

      …ttp://www.zweckesschatzinsel.eu/top/"target="_blank"><img src="http://www.zwe

      ✉

1025. Line 1420, Column > 80: XML Parsing Error: attributes construct error

      …://www.zweckesschatzinsel.eu/top/"target="_blank"><img src="http://www.zwecke…

      ✉

1026. Line 1420, Column > 80: XML Parsing Error: Couldn't find end of Start Tag img line 1420

      …://www.zweckesschatzinsel.eu/top/"target="_blank"><img src="http://www.zwecke…

      ✉

1027. Line 1420, Column > 80: XML Parsing Error: Opening and ending tag mismatch: div line 1420 and a

      …://www.zweckesschatzinsel.eu/top/"target="_blank"><img src="http://www.zwecke…

      ✉

1028. Line 1421, Column 17: XML Parsing Error: Opening and ending tag mismatch: td line 1419 and div

      											</div>

      ✉

1029. Line 1424, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …://www.BannerRank.de" title="BannerRank :: Banner-Ranking :: BR" target="_bla…

      ✉

1030. Line 1424, Column > 80: XML Parsing Error: AttValue: " or ' expected

      …://www.BannerRank.de" title="BannerRank :: Banner-Ranking :: BR" target="_bla…

      ✉

1031. Line 1424, Column > 80: XML Parsing Error: attributes construct error

      …://www.BannerRank.de" title="BannerRank :: Banner-Ranking :: BR" target="_bla…

      ✉

1032. Line 1424, Column > 80: XML Parsing Error: Couldn't find end of Start Tag IMG line 1424

      …://www.BannerRank.de" title="BannerRank :: Banner-Ranking :: BR" target="_bla…

      ✉

1033. Line 1433, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1433 and a

      …/" onmousedown="return hit('http://www.bannerdreams.de/toplist/in.php?id=198'…

      ✉

1034. Line 1434, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1433 and div

      											</div>

      ✉

1035. Line 1435, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1432 and td

      									</td>

      ✉

1036. Line 1437, Column 73: XML Parsing Error: attributes construct error

      …f="http://www.elke-stieler.de/liste/"target="_blank"><img src="http://www.elk

      ✉

1037. Line 1437, Column 73: XML Parsing Error: Couldn't find end of Start Tag a line 1437

      …f="http://www.elke-stieler.de/liste/"target="_blank"><img src="http://www.elk

      ✉

1038. Line 1437, Column > 80: XML Parsing Error: Opening and ending tag mismatch: div line 1437 and a

      …://www.elke-stieler.de/liste/"target="_blank"><img src="http://www.elke-stiel…

      ✉

1039. Line 1438, Column 17: XML Parsing Error: Opening and ending tag mismatch: td line 1436 and div

      											</div>

      ✉

1040. Line 1463, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …://www.88c.de/topliste/count.php?liste=417&id=38081" target="_blank"><img src…

      ✉

1041. Line 1463, Column > 80: XML Parsing Error: AttValue: " or ' expected

      …://www.88c.de/topliste/count.php?liste=417&id=38081" target="_blank"><img src…

      ✉

1042. Line 1463, Column > 80: XML Parsing Error: attributes construct error

      …://www.88c.de/topliste/count.php?liste=417&id=38081" target="_blank"><img src…

      ✉

1043. Line 1463, Column > 80: XML Parsing Error: Couldn't find end of Start Tag img line 1463

      …://www.88c.de/topliste/count.php?liste=417&id=38081" target="_blank"><img src…

      ✉

1044. Line 1468, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1468 and a

      …sedown="return hit('http://topliste.metaman.de/in.php?id=60')" target="_blank…

      ✉

1045. Line 1469, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1468 and div

      											</div>

      ✉

1046. Line 1470, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1467 and td

      									</td>

      ✉

1047. Line 1473, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1473 and a

      …n="return hit('http://www.page100.de/in.php?id=194')" target="_blank"><img sr…

      ✉

1048. Line 1474, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1473 and div

      											</div>

      ✉

1049. Line 1475, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1472 and td

      									</td>

      ✉

1050. Line 1477, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1477 and a

      …://www.toplistenhoster.com/cgi-bin/listen/in.cgi?4B4D3D3838264C734B3D31333133…

      ✉

1051. Line 1478, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1477 and div

      											</div>

      ✉

1052. Line 1479, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1477 and td

      									</td>

      ✉

1053. Line 1481, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1481 and a

      …://www.topklix.de/cgi-bin/top/in.cgi?6D773D36313426556B7A3D3139303130"><img s…

      ✉

1054. Line 1482, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1481 and div

      											</div>

      ✉

1055. Line 1483, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1481 and td

      									</td>

      ✉

1056. Line 1484, Column 13: XML Parsing Error: Opening and ending tag mismatch: td line 1480 and tr

      								</tr>

      ✉

1057. Line 1487, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1487 and a

      …://www.topklix.de/cgi-bin/top/in.cgi?55733D37393226554D713D3139303131"><img s…

      ✉

1058. Line 1488, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1487 and div

      											</div>

      ✉

1059. Line 1489, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1487 and td

      									</td>

      ✉

1060. Line 1491, Column 67: XML Parsing Error: attributes construct error

      …<a href="http://www.rally-world.net/"target="_blank"><img src="http://www.ral

      ✉

1061. Line 1491, Column 67: XML Parsing Error: Couldn't find end of Start Tag a line 1491

      …<a href="http://www.rally-world.net/"target="_blank"><img src="http://www.ral

      ✉

1062. Line 1491, Column > 80: XML Parsing Error: attributes construct error

      …://www.rally-world.net/"target="_blank"><img src="http://www.rally-world.net/…

      ✉

1063. Line 1491, Column > 80: XML Parsing Error: Couldn't find end of Start Tag img line 1491

      …://www.rally-world.net/"target="_blank"><img src="http://www.rally-world.net/…

      ✉

1064. Line 1491, Column > 80: XML Parsing Error: Opening and ending tag mismatch: div line 1491 and a

      …://www.rally-world.net/"target="_blank"><img src="http://www.rally-world.net/…

      ✉

1065. Line 1492, Column 17: XML Parsing Error: Opening and ending tag mismatch: td line 1490 and div

      											</div>

      ✉

1066. Line 1496, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1496 and a

      …list6/" onmousedown="return hit('http://traffic-trade.de/=host=/toplist6/in.p…

      ✉

1067. Line 1497, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1496 and div

      											</div>

      ✉

1068. Line 1498, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1495 and td

      									</td>

      ✉

1069. Line 1520, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1520 and a

      …://www.mastermax.de/promo/top-banner/rein.php?id=230" target="_blank"><img sr…

      ✉

1070. Line 1521, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1520 and div

      											</div>

      ✉

1071. Line 1522, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1520 and td

      									</td>

      ✉

1072. Line 1523, Column 13: XML Parsing Error: Opening and ending tag mismatch: td line 1519 and tr

      								</tr>

      ✉

1073. Line 1527, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1527 and a

      …="_blank" title="Kostenlos werben"><img src="http://www.besucherland.de/partn…

      ✉

1074. Line 1530, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1527 and div

      											</div>

      ✉

1075. Line 1531, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1526 and td

      									</td>

      ✉

1076. Line 1564, Column 13: XML Parsing Error: Opening and ending tag mismatch: td line 1525 and tr

      								</tr>

      ✉

1077. Line 1603, Column 15: XML Parsing Error: Opening and ending tag mismatch: tr line 1524 and table

      							</table>

      ✉

1078. Line 1607, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …://www.free-topsites.de/banner/linklist/in.php?id=55&b=2" target="_blank"><im…

      ✉

1079. Line 1611, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …://www.liverank.org/index.php?a=in&u=Pro4Free" target="_blank"><img src="http…

      ✉

1080. Line 1619, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1619 and a

      … Topliste Anfang --><a href="http://www.adm24.net/pagerank-topliste.php" targ…

      ✉

1081. Line 1620, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1619 and div

      											</div>

      ✉

1082. Line 1621, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1619 and td

      									</td>

      ✉

1083. Line 1623, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1623 and a

      …://www.mr-rank.de" title="Pagerank" target="_blank"><img src="http://www.mr-r…

      ✉

1084. Line 1624, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1623 and div

      											</div>

      ✉

1085. Line 1625, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1623 and td

      									</td>

      ✉

1086. Line 1627, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …://www.laal.de" title="laal.de - Pagerank Anzeige ohne Toolbar" target="_blan…

      ✉

1087. Line 1628, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1627 and a

      …r" height="15" width="88" border="0"></a>…

      ✉

1088. Line 1629, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1627 and div

      											</div>

      ✉

1089. Line 1630, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1627 and td

      									</td>

      ✉

1090. Line 1636, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …://www.ss4w.de" title="ss4w.de Tool:  kostenloser Counter + Pagerank Service …

      ✉

1091. Line 1640, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …://www.zuuk.de" title="ZUUK.DE Kostenloser PageRank Service im Internet - Pag…

      ✉

1092. Line 1641, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1640 and a

      … im Internet - Pagerank Anzeige ohne Toolbar" height="15" width="88" border="…

      ✉

1093. Line 1642, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1640 and div

      											</div>

      ✉

1094. Line 1643, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1640 and td

      									</td>

      ✉

1095. Line 1645, Column 76: XML Parsing Error: attributes construct error

      …http://www.server-seven.de/linkindex"target="_blank"><img src="http://www.ser

      ✉

1096. Line 1645, Column 76: XML Parsing Error: Couldn't find end of Start Tag a line 1645

      …http://www.server-seven.de/linkindex"target="_blank"><img src="http://www.ser

      ✉

1097. Line 1645, Column > 80: XML Parsing Error: Opening and ending tag mismatch: div line 1645 and a

      …://www.server-seven.de/linkindex"target="_blank"><img src="http://www.server-…

      ✉

1098. Line 1646, Column 17: XML Parsing Error: Opening and ending tag mismatch: td line 1644 and div

      											</div>

      ✉

1099. Line 1648, Column 13: XML Parsing Error: Opening and ending tag mismatch: td line 1626 and tr

      								</tr>

      ✉

1100. Line 1651, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1651 and a

      …ww.backlink-clever.de Backlink-Liste Anfang --><a href="http://www.backlink-c…

      ✉

1101. Line 1652, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1651 and div

      											</div>

      ✉

1102. Line 1653, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1651 and td

      									</td>

      ✉

1103. Line 1655, Column 76: XML Parsing Error: attributes construct error

      …http://www.server-seven.de/backlinks"target="_blank"><img src="http://www.ser

      ✉

1104. Line 1655, Column 76: XML Parsing Error: Couldn't find end of Start Tag a line 1655

      …http://www.server-seven.de/backlinks"target="_blank"><img src="http://www.ser

      ✉

1105. Line 1655, Column > 80: XML Parsing Error: Opening and ending tag mismatch: div line 1655 and a

      …://www.server-seven.de/backlinks"target="_blank"><img src="http://www.server-…

      ✉

1106. Line 1656, Column 17: XML Parsing Error: Opening and ending tag mismatch: td line 1654 and div

      											</div>

      ✉

1107. Line 1663, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1663 and a

      …://www.promotion-center.de/" title="promotion-center.de - Homepage bekannt ma…

      ✉

1108. Line 1664, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1663 and div

      											</div>

      ✉

1109. Line 1665, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1663 and td

      									</td>

      ✉

1110. Line 1667, Column > 80: XML Parsing Error: xmlParseEntityRef: no name

      …://www.online-team.net" title="online-team.net - Kostenlose Seitenstatistiken…

      ✉

1111. Line 1667, Column > 80: XML Parsing Error: xmlParseEntityRef: no name

      …://www.online-team.net" title="online-team.net - Kostenlose Seitenstatistiken…

      ✉

1112. Line 1667, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1667 and a

      …://www.online-team.net" title="online-team.net - Kostenlose Seitenstatistiken…

      ✉

1113. Line 1668, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1667 and div

      											</div>

      ✉

1114. Line 1669, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1667 and td

      									</td>

      ✉

1115. Line 1671, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …://www.lerchendal.org" title="Lerchendal.org - Pagerank Anzeige ohne Toolbar"…

      ✉

1116. Line 1672, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1671 and a

      … Toolbar" height="15" width="88" border="0"></a>…

      ✉

1117. Line 1673, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1671 and div

      											</div>

      ✉

1118. Line 1674, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1671 and td

      									</td>

      ✉

1119. Line 1680, Column > 80: XML Parsing Error: AttValue: " or ' expected

      …://www.linkpartner.findet-sucht.de' TARGET='_blank'><IMG SRC='http://www.link…

      ✉

1120. Line 1680, Column > 80: XML Parsing Error: attributes construct error

      …://www.linkpartner.findet-sucht.de' TARGET='_blank'><IMG SRC='http://www.link…

      ✉

1121. Line 1680, Column > 80: XML Parsing Error: Couldn't find end of Start Tag IMG line 1680

      …://www.linkpartner.findet-sucht.de' TARGET='_blank'><IMG SRC='http://www.link…

      ✉

1122. Line 1680, Column > 80: XML Parsing Error: Opening and ending tag mismatch: A line 1680 and a

      …://www.linkpartner.findet-sucht.de' TARGET='_blank'><IMG SRC='http://www.link…

      ✉

1123. Line 1686, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …/cgi-bin/megatop/toplist.pl?action=click_in&account=Pro4Free" target="_blan……

      ✉

1124. Line 1688, Column 4: XML Parsing Error: Opening and ending tag mismatch: img line 1687 and a

      </a></center>

      ✉

1125. Line 1688, Column 13: XML Parsing Error: Opening and ending tag mismatch: a line 1686 and center

      </a></center>

      ✉

1126. Line 1690, Column 17: XML Parsing Error: Opening and ending tag mismatch: center line 1685 and div

      											</div>

      ✉

1127. Line 1691, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1684 and td

      									</td>

      ✉

1128. Line 1693, Column > 80: XML Parsing Error: AttValue: " or ' expected

      …://www.tophits.free-topsites.de/in.php?site=1254606860" target="_blank"><img …

      ✉

1129. Line 1693, Column > 80: XML Parsing Error: attributes construct error

      …://www.tophits.free-topsites.de/in.php?site=1254606860" target="_blank"><img …

      ✉

1130. Line 1693, Column > 80: XML Parsing Error: Couldn't find end of Start Tag img line 1693

      …://www.tophits.free-topsites.de/in.php?site=1254606860" target="_blank"><img …

      ✉

1131. Line 1696, Column 13: XML Parsing Error: Opening and ending tag mismatch: td line 1683 and tr

      								</tr>

      ✉

1132. Line 1699, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      … Anfang --><a href="http://www.ranklord.de/ranking.php" target="_blank" title…

      ✉

1133. Line 1699, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1699 and a

      … Anfang --><a href="http://www.ranklord.de/ranking.php" target="_blank" title…

      ✉

1134. Line 1700, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1699 and div

      											</div>

      ✉

1135. Line 1701, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1699 and td

      									</td>

      ✉

1136. Line 1703, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …://www.linkadd.de" target="_blank" title="Suchmaschinen Marketing"><img src="…

      ✉

1137. Line 1703, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1703 and a

      …://www.linkadd.de" target="_blank" title="Suchmaschinen Marketing"><img src="…

      ✉

1138. Line 1704, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1703 and div

      											</div>

      ✉

1139. Line 1705, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1703 and td

      									</td>

      ✉

1140. Line 1707, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …://www.pagerank-server7.de" title="Pagerank - Server7" target="_blank"><img s…

      ✉

1141. Line 1708, Column 63: XML Parsing Error: Opening and ending tag mismatch: img line 1707 and a

      …rank - Server7" height="15" width="88" border="0"></a>

      ✉

1142. Line 1709, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1707 and div

      											</div>

      ✉

1143. Line 1710, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1707 and td

      									</td>

      ✉

1144. Line 1712, Column > 80: XML Parsing Error: AttValue: " or ' expected

      …://www.list-host.free-topsites.de/topsites/in.php?site=1254606518" target="_b…

      ✉

1145. Line 1712, Column > 80: XML Parsing Error: attributes construct error

      …://www.list-host.free-topsites.de/topsites/in.php?site=1254606518" target="_b…

      ✉

1146. Line 1712, Column > 80: XML Parsing Error: Couldn't find end of Start Tag img line 1712

      …://www.list-host.free-topsites.de/topsites/in.php?site=1254606518" target="_b…

      ✉

1147. Line 1716, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …http://www.spidermich.net/pr.php?id=202&bild=15&extra=1"></script>…

      ✉

1148. Line 1716, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …http://www.spidermich.net/pr.php?id=202&bild=15&extra=1"></script>…

      ✉

1149. Line 1720, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …://www.spider-mich.com" title="Spider mich - Seo Pagerank Counter Service" ta…

      ✉

1150. Line 1739, Column 13: XML Parsing Error: Opening and ending tag mismatch: td line 1706 and tr

      								</tr>

      ✉

1151. Line 1742, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …://www.kt-g.de" title="Pagerank Backlink - Pagerank Anzeige ohne Toolbar" tar…

      ✉

1152. Line 1746, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …://www.backlinkprofi24.info" title="Backlinkprofi24.info - Pagerank Backlink …

      ✉

1153. Line 1754, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …://www.pagerank-server7.de" title="Pagerank - Server7" target="_blank"><img s…

      ✉

1154. Line 1758, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …://www.321-prview.com" title="Pagerank Backlink - Pagerank Anzeige ohne Toolb…

      ✉

1155. Line 1759, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1758 and a

      …hne Toolbar" height="15" width="88" border="0"></a>…

      ✉

1156. Line 1760, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1758 and div

      											</div>

      ✉

1157. Line 1761, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1758 and td

      									</td>

      ✉

1158. Line 1763, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …://www.amores24-shop.de/backlink" title="Amores24-Shop.de Pagerank Backlink -…

      ✉

1159. Line 1764, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1763 and a

      …agerank Anzeige ohne Toolbar" height="15" width="88" border="0"></a>…

      ✉

1160. Line 1765, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1763 and div

      											</div>

      ✉

1161. Line 1766, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1763 and td

      									</td>

      ✉

1162. Line 1768, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …://www.wasoft.org/backlink" title="Pagerank Backlink Linktausch WaSoft.org - …

      ✉

1163. Line 1769, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1768 and a

      …g - Pagerank Anzeige ohne Toolbar" height="15" width="88" border="0"></a>…

      ✉

1164. Line 1770, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1768 and div

      											</div>

      ✉

1165. Line 1771, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1768 and td

      									</td>

      ✉

1166. Line 1773, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …://www.rankinghit.info" title="Rankinghit.info - Pagerank Anzeige ohne Toolba…

      ✉

1167. Line 1774, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1773 and a

      …e Toolbar" height="15" width="88" border="0"></a>…

      ✉

1168. Line 1775, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1773 and div

      											</div>

      ✉

1169. Line 1776, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1773 and td

      									</td>

      ✉

1170. Line 1778, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …://www.lifedate.de/backlink" title="Pagerank Backlink Lifedate.de - Pagerank …

      ✉

1171. Line 1779, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1778 and a

      …nk Anzeige ohne Toolbar" height="15" width="88" border="0"></a>…

      ✉

1172. Line 1780, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1778 and div

      											</div>

      ✉

1173. Line 1781, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1778 and td

      									</td>

      ✉

1174. Line 1783, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …://www.eu-webkatalog.de/pagerank" title="Pagerank Backlink - Pagerank Anzeige…

      ✉

1175. Line 1784, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1783 and a

      …hne Toolbar" height="15" width="88" border="0"></a>…

      ✉

1176. Line 1785, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1783 and div

      											</div>

      ✉

1177. Line 1786, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1783 and td

      									</td>

      ✉

1178. Line 1787, Column 13: XML Parsing Error: Opening and ending tag mismatch: td line 1782 and tr

      								</tr>

      ✉

1179. Line 1790, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …://www.ss4w.de" title="Pagerank Backlink Linktausch ss4w.de - Pagerank Anzeig…

      ✉

1180. Line 1791, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1790 and a

      … Pagerank Anzeige ohne Toolbar mit Statistik von ss4w.de" height="15" width="…

      ✉

1181. Line 1792, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1790 and div

      											</div>

      ✉

1182. Line 1793, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1790 and td

      									</td>

      ✉

1183. Line 1795, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …://www.rank4all.eu" title="Pagerank Backlink - Pagerank Anzeige ohne Toolbar"…

      ✉

1184. Line 1796, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1795 and a

      …hne Toolbar" height="15" width="88" border="0"></a>…

      ✉

1185. Line 1797, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1795 and div

      											</div>

      ✉

1186. Line 1798, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1795 and td

      									</td>

      ✉

1187. Line 1800, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …://www.url-schleuder.net" title="Pagerank Backlink - Pagerank Anzeige ohne To…

      ✉

1188. Line 1801, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1800 and a

      …hne Toolbar" height="15" width="88" border="0"></a>…

      ✉

1189. Line 1802, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1800 and div

      											</div>

      ✉

1190. Line 1803, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1800 and td

      									</td>

      ✉

1191. Line 1805, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …://www.hanywal.de" title="Nordsee - Pagerank Backlink" target="_blank"><img s…

      ✉

1192. Line 1806, Column 72: XML Parsing Error: Opening and ending tag mismatch: img line 1805 and a

      …klink" height="15" width="88" border="0"></a>

      ✉

1193. Line 1807, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1805 and div

      											</div>

      ✉

1194. Line 1808, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1805 and td

      									</td>

      ✉

1195. Line 1810, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …://pagerank.promotion-booster.de" title="pagerank.promotion-booster.de - Page…

      ✉

1196. Line 1810, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1810 and a

      …://pagerank.promotion-booster.de" title="pagerank.promotion-booster.de - Page…

      ✉

1197. Line 1811, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1810 and div

      											</div>

      ✉

1198. Line 1812, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1810 and td

      									</td>

      ✉

1199. Line 1814, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …://www.pagerank-seo.net" title="Pagerank Backlink - Pagerank Anzeige ohne Too…

      ✉

1200. Line 1815, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1814 and a

      …hne Toolbar - mehr Besucher - Link Exchange - SEO Webmaster Tool" height="15"…

      ✉

1201. Line 1816, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1814 and div

      											</div>

      ✉

1202. Line 1817, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1814 and td

      									</td>

      ✉

1203. Line 1819, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …://www.domain-on-top.net" title="Pagerank Backlink - SEO Tools and more" targ…

      ✉

1204. Line 1820, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1819 and a

      …" height="15" width="88" border="0"></a>…

      ✉

1205. Line 1821, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1819 and div

      											</div>

      ✉

1206. Line 1822, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1819 and td

      									</td>

      ✉

1207. Line 1824, Column > 80: XML Parsing Error: xmlParseEntityRef: no name

      …://www.pimpmypr.de" title="Pagerank- & Counterservice" target="_blank"><img s…

      ✉

1208. Line 1824, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …://www.pimpmypr.de" title="Pagerank- & Counterservice" target="_blank"><img s…

      ✉

1209. Line 1824, Column > 80: XML Parsing Error: xmlParseEntityRef: no name

      …://www.pimpmypr.de" title="Pagerank- & Counterservice" target="_blank"><img s…

      ✉

1210. Line 1828, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …://list-ranking.com" title="list-ranking.com - pagerank, mehr pagerank, pager…

      ✉

1211. Line 1832, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …://www.laal.de" target="_blank"><img src="http://www.laal.de/pr.php?ref=fuchs…

      ✉

1212. Line 1832, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1832 and a

      …://www.laal.de" target="_blank"><img src="http://www.laal.de/pr.php?ref=fuchs…

      ✉

1213. Line 1833, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1832 and div

      											</div>

      ✉

1214. Line 1834, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1832 and td

      									</td>

      ✉

1215. Line 1835, Column 13: XML Parsing Error: Opening and ending tag mismatch: td line 1831 and tr

      								</tr>

      ✉

1216. Line 1839, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …net" target="_blank"><img src="http://www.vegaconcept.net/pr.php?ref=fuchs-wo…

      ✉

1217. Line 1839, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1839 and a

      …net" target="_blank"><img src="http://www.vegaconcept.net/pr.php?ref=fuchs-wo…

      ✉

1218. Line 1839, Column > 80: XML Parsing Error: Opening and ending tag mismatch: a line 1839 and div

      …net" target="_blank"><img src="http://www.vegaconcept.net/pr.php?ref=fuchs-wo…

      ✉

1219. Line 1840, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1838 and td

      									</td>

      ✉

1220. Line 1842, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …://www.spider-mich.com" title="Spider mich - Seo Pagerank Counter Service" ta…

      ✉

1221. Line 1846, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …://www.pr4y.de" target="_blank"><img src="http://www.pr4y.de/pr.php?ref=fuchs…

      ✉

1222. Line 1846, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1846 and a

      …://www.pr4y.de" target="_blank"><img src="http://www.pr4y.de/pr.php?ref=fuchs…

      ✉

1223. Line 1847, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1846 and div

      											</div>

      ✉

1224. Line 1848, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1846 and td

      									</td>

      ✉

1225. Line 1850, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1850 and a

      …://www.mr-rank.de" title="Pagerank" target="_blank"><img src="http://www.mr-r…

      ✉

1226. Line 1851, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1850 and div

      											</div>

      ✉

1227. Line 1852, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1850 and td

      									</td>

      ✉

1228. Line 1854, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …://www.beraten24.de" target="_blank"><img src="http://www.santez.net/pr.php?r…

      ✉

1229. Line 1854, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1854 and a

      …://www.beraten24.de" target="_blank"><img src="http://www.santez.net/pr.php?r…

      ✉

1230. Line 1855, Column 17: XML Parsing Error: Opening and ending tag mismatch: a line 1854 and div

      											</div>

      ✉

1231. Line 1856, Column 14: XML Parsing Error: Opening and ending tag mismatch: div line 1854 and td

      									</td>

      ✉

1232. Line 1877, Column 13: XML Parsing Error: Opening and ending tag mismatch: td line 1853 and tr

      								</tr>

      ✉

1233. Line 1962, Column 15: XML Parsing Error: Opening and ending tag mismatch: td line 1849 and table

      							</table>

      ✉

1234. Line 1989, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 1989 and a

      …//www.GeldCounter.de/index.php?ref=Dominicki" target="_blank"><img src="http:…

      ✉

1235. Line 1990, Column 16: XML Parsing Error: Opening and ending tag mismatch: a line 1989 and div

      										</div>

      ✉

1236. Line 1991, Column 13: XML Parsing Error: Opening and ending tag mismatch: div line 1989 and td

      								</td>

      ✉

1237. Line 1992, Column 13: XML Parsing Error: Opening and ending tag mismatch: td line 1988 and tr

      								</tr>

      ✉

1238. Line 1996, Column 77: XML Parsing Error: EntityRef: expecting ';'

      …mm-counter.de/counter1.php?user=820&site=1711&bg=9eb1c9&txt=000000"></script>

      ✉

1239. Line 1996, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …nter.de/counter1.php?user=820&site=1711&bg=9eb1c9&txt=000000"></script>…

      ✉

1240. Line 1996, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …nter.de/counter1.php?user=820&site=1711&bg=9eb1c9&txt=000000"></script>…

      ✉

1241. Line 2019, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …ttp://maxi-ad.de/ma/mad8.php?Dominicki&eba=frame" width="160" height="500" na…

      ✉

1242. Line 2019, Column > 80: XML Parsing Error: AttValue: " or ' expected

      …ttp://maxi-ad.de/ma/mad8.php?Dominicki&eba=frame" width="160" height="500" na…

      ✉

1243. Line 2019, Column > 80: XML Parsing Error: attributes construct error

      …ttp://maxi-ad.de/ma/mad8.php?Dominicki&eba=frame" width="160" height="500" na…

      ✉

1244. Line 2019, Column > 80: XML Parsing Error: Couldn't find end of Start Tag iframe line 2019

      …ttp://maxi-ad.de/ma/mad8.php?Dominicki&eba=frame" width="160" height="500" na…

      ✉

1245. Line 2019, Column > 80: XML Parsing Error: Opening and ending tag mismatch: div line 2019 and iframe

      …ttp://maxi-ad.de/ma/mad8.php?Dominicki&eba=frame" width="160" height="500" na…

      ✉

1246. Line 2020, Column 16: XML Parsing Error: Opening and ending tag mismatch: td line 2018 and div

      										</div>

      ✉

1247. Line 2021, Column 13: XML Parsing Error: Opening and ending tag mismatch: tr line 2017 and td

      								</td>

      ✉

1248. Line 2037, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …ttp://maxi-ad.de/ma/mad2.php?Dominicki&eba=frame" width="160" height="600" na…

      ✉

1249. Line 2037, Column > 80: XML Parsing Error: AttValue: " or ' expected

      …ttp://maxi-ad.de/ma/mad2.php?Dominicki&eba=frame" width="160" height="600" na…

      ✉

1250. Line 2037, Column > 80: XML Parsing Error: attributes construct error

      …ttp://maxi-ad.de/ma/mad2.php?Dominicki&eba=frame" width="160" height="600" na…

      ✉

1251. Line 2037, Column > 80: XML Parsing Error: Couldn't find end of Start Tag iframe line 2037

      …ttp://maxi-ad.de/ma/mad2.php?Dominicki&eba=frame" width="160" height="600" na…

      ✉

1252. Line 2037, Column > 80: XML Parsing Error: Opening and ending tag mismatch: div line 2037 and iframe

      …ttp://maxi-ad.de/ma/mad2.php?Dominicki&eba=frame" width="160" height="600" na…

      ✉

1253. Line 2038, Column 16: XML Parsing Error: Opening and ending tag mismatch: td line 2036 and div

      										</div>

      ✉

1254. Line 2039, Column 13: XML Parsing Error: Opening and ending tag mismatch: tr line 2035 and td

      								</td>

      ✉

1255. Line 2040, Column 12: XML Parsing Error: Opening and ending tag mismatch: table line 1986 and tr

      							</tr>

      ✉

1256. Line 2072, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …ww.echtebesucher.de/textads.php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&…

      ✉

1257. Line 2072, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …ww.echtebesucher.de/textads.php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&…

      ✉

1258. Line 2072, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …ww.echtebesucher.de/textads.php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&…

      ✉

1259. Line 2072, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …ww.echtebesucher.de/textads.php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&…

      ✉

1260. Line 2072, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …ww.echtebesucher.de/textads.php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&…

      ✉

1261. Line 2072, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …ww.echtebesucher.de/textads.php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&…

      ✉

1262. Line 2072, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …ww.echtebesucher.de/textads.php?bo=0000ff&ti=000000&txt=000000&bg=ffffcc&s=6&…

      ✉

1263. Line 2077, Column 14: XML Parsing Error: Opening and ending tag mismatch: td line 1985 and table

      						</table>

      ✉

1264. Line 2086, Column 12: XML Parsing Error: Opening and ending tag mismatch: td line 1837 and div

      						</div>

      ✉

1265. Line 2087, Column 8: XML Parsing Error: Opening and ending tag mismatch: tr line 1836 and body

      	</body>

      ✉

1266. Line 2088, Column 7: XML Parsing Error: Opening and ending tag mismatch: td line 1818 and html

      </html>

      ✉

1267. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag td line 1813

      </html>

      ✉

1268. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag td line 1809

      </html>

      ✉

1269. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag td line 1804

      </html>

      ✉

1270. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag td line 1799

      </html>

      ✉

1271. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag td line 1794

      </html>

      ✉

1272. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag td line 1789

      </html>

      ✉

1273. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag tr line 1788

      </html>

      ✉

1274. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag td line 1777

      </html>

      ✉

1275. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag td line 1772

      </html>

      ✉

1276. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag td line 1767

      </html>

      ✉

1277. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag td line 1762

      </html>

      ✉

1278. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag td line 1757

      </html>

      ✉

1279. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag tr line 1740

      </html>

      ✉

1280. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag td line 1702

      </html>

      ✉

1281. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag td line 1698

      </html>

      ✉

1282. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag tr line 1697

      </html>

      ✉

1283. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag td line 1670

      </html>

      ✉

1284. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag td line 1666

      </html>

      ✉

1285. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag td line 1662

      </html>

      ✉

1286. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag tr line 1649

      </html>

      ✉

1287. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag td line 1622

      </html>

      ✉

1288. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag td line 1618

      </html>

      ✉

1289. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag tr line 1605

      </html>

      ✉

1290. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag table line 1604

      </html>

      ✉

1291. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag td line 1494

      </html>

      ✉

1292. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag tr line 1485

      </html>

      ✉

1293. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag td line 1476

      </html>

      ✉

1294. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag td line 1471

      </html>

      ✉

1295. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag td line 1466

      </html>

      ✉

1296. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag tr line 1445

      </html>

      ✉

1297. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag div line 1043

      </html>

      ✉

1298. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag table line 910

      </html>

      ✉

1299. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag center line 909

      </html>

      ✉

1300. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag tr line 878

      </html>

      ✉

1301. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag table line 871

      </html>

      ✉

1302. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag tr line 844

      </html>

      ✉

1303. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag table line 837

      </html>

      ✉

1304. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag tr line 810

      </html>

      ✉

1305. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag table line 803

      </html>

      ✉

1306. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag tr line 776

      </html>

      ✉

1307. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag table line 769

      </html>

      ✉

1308. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag tr line 742

      </html>

      ✉

1309. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag table line 735

      </html>

      ✉

1310. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag table line 674

      </html>

      ✉

1311. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag center line 673

      </html>

      ✉

1312. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag tr line 642

      </html>

      ✉

1313. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag table line 635

      </html>

      ✉

1314. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag tr line 608

      </html>

      ✉

1315. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag table line 601

      </html>

      ✉

1316. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag tr line 574

      </html>

      ✉

1317. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag table line 567

      </html>

      ✉

1318. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag tr line 540

      </html>

      ✉

1319. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag table line 533

      </html>

      ✉

1320. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag table line 472

      </html>

      ✉

1321. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag center line 471

      </html>

      ✉

1322. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag tr line 440

      </html>

      ✉

1323. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag table line 433

      </html>

      ✉

1324. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag div line 427

      </html>

      ✉

1325. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag div line 425

      </html>

      ✉

1326. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag div line 424

      </html>

      ✉

1327. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag div line 279

      </html>

      ✉

1328. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag td line 157

      </html>

      ✉

1329. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag div line 32

      </html>

      ✉

1330. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag body line 31

      </html>

      ✉

1331. Line 2088, Column 7: XML Parsing Error: Premature end of data in tag html line 3

      </html>

      ✉