Videos Gratis Hombres, Videos y fotos de hombres gays muy guapos follando, gay sex picture, sex with boys ...

videosgratishombres.com
  • Domain Name
    videosgratishombres.com
  • Favicon
  • Google Page Rank
    1
  • Alexa Rank
    #651695
  • Page Size
    47.8 KB
  • Ip Address
    95.211.190.77
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    3 GIF, 8 JPG, 0 PNG

Website Meta Analysis

  • Title
    Videos Gratis Hombres - Video gay gratuitas. Videos y Fotos Gay
  • Meta Keyword
    videosgratishombres.com, Videos Gratis Hombres, hombres, hombres gays, hombres negros, hombres guapos, hombres gratis, videos de hombres, videos gays, fotos hombres, fotos gays, gays follando, penis, homosexuality, hunks, muscle men, homosexuals, twink, gay, hunk, cock, homo, penises, dick, stud, big cock, black cock, men, studs, male, hairy men, gay personals, gay dating, big penis, boy, gay rights, man, male models, penis pictures, boys, free cock, hot boy, straight men, boys men, hot boys, huge penis, muscle man, huge cock, mens, big boy, big cocks, men pics, hunky, males, guys, straight, men's, huge, muscle, underwear, enlargement, cum, mans, man's, jerking
  • Meta Description
    Videos Gratis Hombres, Videos y fotos de hombres gays muy guapos follando, gay sex picture, sex with boys

Technical Analysis

  • Webserver
    nginx/1.1.19
  • Ip Address
    95.211.190.77
  • Domain Age
    3 Years, 4 Months, 10 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from videosgratishombres.com.

HTML Analysis

  • server: nginx/1.1.19
  • date: Wed, 11 Sep 2013 13:22:20 GMT
  • content-type: text/html
  • content-length: 9165
  • connection: keep-alive
  • x-powered-by: PHP/5.2.17
  • cache-control: no-cache, must-revalidate
  • pragma: no-cache
  • vary: Accept-Encoding
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

Domain Name: VIDEOSGRATISHOMBRES.COM

Abuse email: email

Registrant:
WhoisProtectService.net PROTECTSERVICE, LTD. email
27 Old Gloucester Street
London WC1N 3AX
United Kingdom
+44.02074195061

Registered Through:
AHnames.com http://www.AHnames.com/

Administrative Contact:
WhoisProtectService.net PROTECTSERVICE, LTD. email
27 Old Gloucester Street
London WC1N 3AX
United Kingdom
+44.02074195061

Technical Contact:
WhoisProtectService.net PROTECTSERVICE, LTD. email
27 Old Gloucester Street
London WC1N 3AX
United Kingdom
+44.02074195061

Billing Contact:
WhoisProtectService.net PROTECTSERVICE, LTD. email
27 Old Gloucester Street
London WC1N 3AX
United Kingdom
+44.02074195061

Name Server: NS1.CULOPELOSO.COM
Name Server: NS2.CULOPELOSO.COM

DNS Analysis


DNS servers
ns1.culopeloso.com [95.211.190.77]
ns2.culopeloso.com [95.211.190.77]


DNS Records

Answer records
videosgratishombres.com SOA
server: localhost
email: root@localhost
serial: 2013022101
refresh: 43200
retry: 3600
expire: 604800
minimum ttl: 3600
86400s
videosgratishombres.com NS  ns1.culopeloso.com 86400s
videosgratishombres.com NS  ns2.culopeloso.com 86400s
videosgratishombres.com A 95.211.190.77 86400s

Authority records

Additional records
ns1.culopeloso.com A 95.211.190.77 86400s
ns2.culopeloso.com A 95.211.190.77 86400s

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 211 Errors
  • 89 Warnings
Ratio Text/Html
  • 0.8693085486671432
Message Error
  • Error Line 1, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
    <html>

    The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.

  • Error Line 9, Column 7: required attribute "TYPE" not specified
    <style>

    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>.

  • Error Line 58, Column 30: required attribute "TYPE" not specified
    <script language="javascript">

    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>.

  • Error Line 99, Column 60: end tag for element "DIV" which is not open
    <a href="link.php?h" style="display:none;">Gallery</a></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.

  • Warning Line 102, Column 35: cannot generate system identifier for general entity "cu"
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…

    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.

  • Error Line 102, Column 35: general entity "cu" not defined and no default entity
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…

    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.

  • Error Line 102, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Warning Line 102, Column 167: cannot generate system identifier for general entity "l"
    …vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='ht…

    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.

  • Error Line 102, Column 167: general entity "l" not defined and no default entity
    …vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='ht…

    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.

  • Error Line 102, Column 168: reference to entity "l" for which no system identifier could be generated
    …d19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 102, Column 471: NET-enabling start-tag requires SHORTTAG YES
    …umbs/35721.jpg?1361883349" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 103, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=28720&cu=aHR0cDovL3d3dy5nYXl0dWJlZGVtb24uY29tLzEtNy…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 103, Column 104: reference to entity "l" for which no system identifier could be generated
    …b24uY29tLzEtNy0wLzI2LzAzLzEyMS5odG0=&l=block1" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 103, Column 360: NET-enabling start-tag requires SHORTTAG YES
    …umbs/28720.jpg?1361917424" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 104, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38851&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 104, Column 140: reference to entity "l" for which no system identifier could be generated
    …cmVlZC10b2lsZXRzZXgvZWhndXkuaHRtbA==&l=block1" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 104, Column 422: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38851.jpg?1362153480" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 105, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=34081&cu=aHR0cDovL3d3dy5wbGF5aW5ndHdpbmtzLmNvbS9nYX…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 105, Column 112: reference to entity "l" for which no system identifier could be generated
    …bS9nYXlwb3JuLzIzOTEvaW5kZXguaHRtbA==&l=block1" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 105, Column 373: NET-enabling start-tag requires SHORTTAG YES
    …umbs/34081.jpg?1361917421" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 108, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=31357&cu=aHR0cDovL3d3dy5tYWxlcG9ybnZpZHMuY29tLzAwNi…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 108, Column 108: reference to entity "l" for which no system identifier could be generated
    …Y29tLzAwNi9kaWNrZG9ybS8xOC8xMi5odG0=&l=block1" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 108, Column 367: NET-enabling start-tag requires SHORTTAG YES
    …umbs/31357.jpg?1362368729" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 109, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38457&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 109, Column 164: reference to entity "l" for which no system identifier could be generated
    …aHVua21vdmllc19pbG92ZWdheXouaHRtbA==&l=block1" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 109, Column 464: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38457.jpg?1362218006" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 110, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=37818&cu=aHR0cDovL3d3dy55Z2F5cG9ybi5jb20vY3VzdG9tXz…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 110, Column 112: reference to entity "l" for which no system identifier could be generated
    …dG9tXzIwMTEvbWVuL3MvMS9pbmRleC5odG0=&l=block1" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 110, Column 374: NET-enabling start-tag requires SHORTTAG YES
    …umbs/37818.jpg?1361995407" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 111, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=36104&cu=aHR0cDovL3d3dy5tYWxlcG9ybnZpZHMuY29tLzAwOC…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 111, Column 116: reference to entity "l" for which no system identifier could be generated
    …OC9pdHNnb25uYWh1cnQvMDMvNDMwMC5odG0=&l=block1" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 111, Column 381: NET-enabling start-tag requires SHORTTAG YES
    …umbs/36104.jpg?1362199391" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 114, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=34209&cu=aHR0cDovL3d3dy53ZWxvdmVib3l6LmNvbS9nYXlib3…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 114, Column 172: reference to entity "l" for which no system identifier could be generated
    …bm93X2dheXZpZGVvdGdwX2hlbG9yZC5odG1s&l=block1" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 114, Column 480: NET-enabling start-tag requires SHORTTAG YES
    …umbs/34209.jpg?1362199388" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 115, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38821&cu=aHR0cDovL3d3dy5nYXl0ZWFjaGVyLm5ldC9waG90by…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 115, Column 104: reference to entity "l" for which no system identifier could be generated
    …Lm5ldC9waG90by1ib290aC1mdW4tdmlkZW8v&l=block1" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 115, Column 350: NET-enabling start-tag requires SHORTTAG YES
    …bres.com/thumbs/38821.jpg" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 116, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=24050&cu=aHR0cDovL3d3dy5ib3lzcGF0cm9sLmNvbS8wMzgvZ2…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 116, Column 112: reference to entity "l" for which no system identifier could be generated
    …MzgvZ2F5LWtvZG8yMWNpaS1ib3lzLmh0bWw=&l=block1" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 116, Column 374: NET-enabling start-tag requires SHORTTAG YES
    …umbs/24050.jpg?1362199389" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 117, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=30038&cu=aHR0cDovL2NsaWNrc2FnZW50LmNvbS9pbi8xZmVycm…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 117, Column 88: reference to entity "l" for which no system identifier could be generated
    …aWNrc2FnZW50LmNvbS9pbi8xZmVycmg5cw==&l=block1" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 117, Column 348: NET-enabling start-tag requires SHORTTAG YES
    …umbs/30038.jpg?1362368730" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 120, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38079&cu=aHR0cDovL2NsaWNrc2FnZW50LmNvbS9pbi8xZmVycm…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 120, Column 88: reference to entity "l" for which no system identifier could be generated
    …aWNrc2FnZW50LmNvbS9pbi8xZmVycmg5cw==&l=block1" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 120, Column 392: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38079.jpg?1362276374" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 121, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=34476&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 121, Column 132: reference to entity "l" for which no system identifier could be generated
    …YXNpYW5ib3lnYXlkYWRzL2VoZ3V5Lmh0bWw=&l=block1" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 121, Column 409: NET-enabling start-tag requires SHORTTAG YES
    …umbs/34476.jpg?1362040065" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 122, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38474&cu=aHR0cDovL2dhbGxlcnkuZGFuaWVsMTkuY29tL3dtdi…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 122, Column 100: reference to entity "l" for which no system identifier could be generated
    …aWVsMTkuY29tL3dtdi82MC9pbmRleC5odG1s&l=block1" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 122, Column 343: NET-enabling start-tag requires SHORTTAG YES
    …bres.com/thumbs/38474.jpg" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 123, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=37423&cu=aHR0cDovL3d3dy5tYWxlcG9ybnZpZHMuY29tLzEyMD…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 123, Column 108: reference to entity "l" for which no system identifier could be generated
    …Y29tLzEyMDExL21lbi8xNi9pbmRleC5odG0=&l=block1" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 123, Column 367: NET-enabling start-tag requires SHORTTAG YES
    …umbs/37423.jpg?1361892323" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 126, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38643&cu=aHR0cDovL3d3dy5zZXhob3VuZGxpbmtzLmNvbS9waW…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 126, Column 128: reference to entity "l" for which no system identifier could be generated
    …L2JlbnRsZXktc3Ryb2tlcy1kaWNrLmh0bWw=&l=block1" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 126, Column 391: NET-enabling start-tag requires SHORTTAG YES
    …bres.com/thumbs/38643.jpg" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 127, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=36602&cu=aHR0cDovL3NlY3VyZS5leHRyYWJpZ2RpY2tzLmNvbS…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 127, Column 152: reference to entity "l" for which no system identifier could be generated
    …akF1TVRFd01UZzNOamd5TUM0d0xqQXVNQQ==&l=block1" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 127, Column 443: NET-enabling start-tag requires SHORTTAG YES
    …umbs/36602.jpg?1361920740" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 128, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=36532&cu=aHR0cDovL3d3dy5tYWNob2Z1Y2tlci5jb20vZnJlZX…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 128, Column 128: reference to entity "l" for which no system identifier could be generated
    …cmVhL1BHbmV3aGFpdGltb25zdGVyMDIuaHRt&l=block1" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 128, Column 403: NET-enabling start-tag requires SHORTTAG YES
    …umbs/36532.jpg?1361883350" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 129, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=34435&cu=aHR0cDovL2NsaWNrc2FnZW50LmNvbS9pbi8xZmVycm…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 129, Column 88: reference to entity "l" for which no system identifier could be generated
    …aWNrc2FnZW50LmNvbS9pbi8xZmVycmg5cw==&l=block1" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 129, Column 366: NET-enabling start-tag requires SHORTTAG YES
    …umbs/34435.jpg?1362368730" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 132, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38803&cu=aHR0cDovL3d3dy5iYWRjb3dib3lzLm5ldC93bTYwMz…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 132, Column 148: reference to entity "l" for which no system identifier could be generated
    …bmQtYXNzLXRpZ2h0bmVzcy9pbmRleC5odG1s&l=block1" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 132, Column 438: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38803.jpg?1362364678" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 133, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=37288&cu=aHR0cDovL2NsaWNrc2FnZW50LmNvbS9pbi8xZmVycm…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 133, Column 88: reference to entity "l" for which no system identifier could be generated
    …aWNrc2FnZW50LmNvbS9pbi8xZmVycmg5cw==&l=block1" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 133, Column 377: NET-enabling start-tag requires SHORTTAG YES
    …umbs/37288.jpg?1362276372" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 134, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38708&cu=aHR0cDovL3d3dy53ZWxvdmVib3l6LmNvbS9nYXlib3…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 134, Column 132: reference to entity "l" for which no system identifier could be generated
    …cmlzLWV2YW5zLXBvcm4vcHJpbW94Lmh0bWw=&l=block1" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 134, Column 398: NET-enabling start-tag requires SHORTTAG YES
    …bres.com/thumbs/38708.jpg" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 135, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=37751&cu=aHR0cDovL3d3dy55Z2F5cG9ybi5jb20vY3VzdG9tXz…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 135, Column 164: reference to entity "l" for which no system identifier could be generated
    …LVNob3AtRnVja2luZy9nYWxsZXJ5Mi5odG0=&l=block1" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 135, Column 465: NET-enabling start-tag requires SHORTTAG YES
    …umbs/37751.jpg?1362013854" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 139, Column 143: required attribute "ALT" not specified
    …artnership.com/pink-twink/468-80-3.gif" width="468" height="80" 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>.

  • Error Line 145, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38452&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 145, Column 164: reference to entity "l" for which no system identifier could be generated
    …ZF9odW5rbW92aWVzX2lsb3ZlZ2F5ei5odG1s&l=block2" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 145, Column 466: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38452.jpg?1362364659" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 146, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38696&cu=aHR0cDovL3d3dy5tYWxlcG9ybnZpZHMuY29tLzAxMC…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 146, Column 100: reference to entity "l" for which no system identifier could be generated
    …bnZpZHMuY29tLzAxMC83MDMvMTIxLmh0bQ==&l=block2" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 146, Column 341: NET-enabling start-tag requires SHORTTAG YES
    …bres.com/thumbs/38696.jpg" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 147, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38868&cu=aHR0cDovL2NsaWNrc2FnZW50LmNvbS9pbi8xZmVycm…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 147, Column 88: reference to entity "l" for which no system identifier could be generated
    …aWNrc2FnZW50LmNvbS9pbi8xZmVycmg5cw==&l=block2" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 147, Column 355: NET-enabling start-tag requires SHORTTAG YES
    …bres.com/thumbs/38868.jpg" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 148, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=30217&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 148, Column 120: reference to entity "l" for which no system identifier could be generated
    …dnMvbWVuL2NsZWFuZXIvZWhndXkuaHRtbA==&l=block2" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 148, Column 387: NET-enabling start-tag requires SHORTTAG YES
    …umbs/30217.jpg?1361917423" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 151, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38919&cu=aHR0cDovL3d3dy5jb29sZ2F5bW92aWVzLmNvbS93YX…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 151, Column 132: reference to entity "l" for which no system identifier could be generated
    …VGN4TlRGay9CYW5nQmFuZ0JveXMtdmlkZW8=&l=block2" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 151, Column 398: NET-enabling start-tag requires SHORTTAG YES
    …bres.com/thumbs/38919.jpg" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 152, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=34272&cu=aHR0cDovL2NsaWNrc2FnZW50LmNvbS9pbi8xZmVycm…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 152, Column 88: reference to entity "l" for which no system identifier could be generated
    …aWNrc2FnZW50LmNvbS9pbi8xZmVycmg5cw==&l=block2" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 152, Column 363: NET-enabling start-tag requires SHORTTAG YES
    …umbs/34272.jpg?1362040064" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 153, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=36058&cu=aHR0cDovL3d3dy55Z2F5cG9ybi5jb20vY3VzdG9tXz…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 153, Column 160: reference to entity "l" for which no system identifier could be generated
    …enktSW4tVGhlLUNsdWIvZ2FsbGVyeTQuaHRt&l=block2" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 153, Column 459: NET-enabling start-tag requires SHORTTAG YES
    …umbs/36058.jpg?1361917425" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 154, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38946&cu=aHR0cDovL3d3dy5jb29sZ2F5bW92aWVzLmNvbS93YX…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 154, Column 132: reference to entity "l" for which no system identifier could be generated
    …VE0wTVRobC9CZWxBbWlPbmxpbmUtdmlkZW8=&l=block2" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 154, Column 398: NET-enabling start-tag requires SHORTTAG YES
    …bres.com/thumbs/38946.jpg" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 157, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38824&cu=aHR0cDovL3d3dy5lZGVuZ2F5LmNvbS9nYWxsZXJ5Lz…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 157, Column 124: reference to entity "l" for which no system identifier could be generated
    …MDEvamltbXktYm9kaW5lL2luZGV4LnBocA==&l=block2" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 157, Column 394: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38824.jpg?1362328067" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 158, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=29175&cu=aHR0cDovL2NsaWNrc2FnZW50LmNvbS9pbi8xZmVycm…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 158, Column 88: reference to entity "l" for which no system identifier could be generated
    …aWNrc2FnZW50LmNvbS9pbi8xZmVycmg5cw==&l=block2" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 158, Column 346: NET-enabling start-tag requires SHORTTAG YES
    …umbs/29175.jpg?1362199391" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 159, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38863&cu=aHR0cDovL3d3dy5tZW5tb3ZpZXNob3cuY29tL3ZpZG…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 159, Column 112: reference to entity "l" for which no system identifier could be generated
    …L3ZpZGVvL2JzYm4vbTE0MjkvZWhuZXcuaHRt&l=block2" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 159, Column 375: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38863.jpg?1362359939" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 160, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=34741&cu=aHR0cDovL2NsaWNrc2FnZW50LmNvbS9pbi8xZmVycm…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 160, Column 88: reference to entity "l" for which no system identifier could be generated
    …aWNrc2FnZW50LmNvbS9pbi8xZmVycmg5cw==&l=block2" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 160, Column 343: NET-enabling start-tag requires SHORTTAG YES
    …umbs/34741.jpg?1362203592" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 163, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38721&cu=aHR0cDovL3d3dy5zdW5ueS10aHVtYnMuY29tL2dhbG…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 163, Column 136: reference to entity "l" for which no system identifier could be generated
    …bGl4c3R1ZGlvcy8xMi8wMS9ybW92cy5odG1s&l=block2" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 163, Column 417: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38721.jpg?1362321912" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 164, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38677&cu=aHR0cDovL3d3dy5nYXlhcm15bm93LmNvbS9odXJ0L2…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 164, Column 156: reference to entity "l" for which no system identifier could be generated
    …X2h1bmttb3ZpZXNfaWxvdmVnYXl6Lmh0bQ==&l=block2" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 164, Column 450: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38677.jpg?1362355796" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 165, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=37983&cu=aHR0cDovL2NsaWNrc2FnZW50LmNvbS9pbi8xZmVycm…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 165, Column 88: reference to entity "l" for which no system identifier could be generated
    …aWNrc2FnZW50LmNvbS9pbi8xZmVycmg5cw==&l=block2" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 165, Column 401: NET-enabling start-tag requires SHORTTAG YES
    …umbs/37983.jpg?1362018918" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 166, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38416&cu=aHR0cDovL3d3dy5nYXl0ZWFjaGVyLm5ldC9DcnVpc2…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 166, Column 120: reference to entity "l" for which no system identifier could be generated
    …Zy1mb3ItaGFyZENvY2svaW5kZXhwci5odG1s&l=block2" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 166, Column 389: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38416.jpg?1362355795" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 169, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38710&cu=aHR0cDovL2NsaWNrc2FnZW50LmNvbS9pbi8xZmVycm…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 169, Column 88: reference to entity "l" for which no system identifier could be generated
    …aWNrc2FnZW50LmNvbS9pbi8xZmVycmg5cw==&l=block2" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 169, Column 356: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38710.jpg?1362340132" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 170, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38122&cu=aHR0cDovL2dhbGxlcnkubWF0dXJlb250d2lua3MuY2…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 170, Column 120: reference to entity "l" for which no system identifier could be generated
    …LzU0My9pbmRleC5odG1sP2lkPWZtZWRpYQ==&l=block2" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 170, Column 387: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38122.jpg?1361940734" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 171, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38419&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 171, Column 116: reference to entity "l" for which no system identifier could be generated
    …eW1vdnMvbWF2ZXIvc2FuZC9laGd1eS5odG1s&l=block2" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 171, Column 382: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38419.jpg?1362293153" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 172, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38466&cu=aHR0cDovL2NsaWNrc2FnZW50LmNvbS9pbi8xZmVycm…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 172, Column 88: reference to entity "l" for which no system identifier could be generated
    …aWNrc2FnZW50LmNvbS9pbi8xZmVycmg5cw==&l=block2" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 172, Column 391: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38466.jpg?1362340157" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 181, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38763&cu=aHR0cDovL2NsaWNrc2FnZW50LmNvbS9pbi8xZmVycm…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 181, Column 88: reference to entity "l" for which no system identifier could be generated
    …aWNrc2FnZW50LmNvbS9pbi8xZmVycmg5cw==&l=block3" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 181, Column 345: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38763.jpg?1362364568" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 182, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38690&cu=aHR0cDovL2NsaWNrc2FnZW50LmNvbS9pbi8xZmVycm…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 182, Column 88: reference to entity "l" for which no system identifier could be generated
    …aWNrc2FnZW50LmNvbS9pbi8xZmVycmg5cw==&l=block3" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 182, Column 358: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38690.jpg?1362189060" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 183, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38864&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 183, Column 136: reference to entity "l" for which no system identifier could be generated
    …cG9ybnN0YXJvcmFsc2V4L2VoZ3V5Lmh0bWw=&l=block3" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 183, Column 416: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38864.jpg?1362208171" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 184, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=36740&cu=aHR0cDovL3d3dy5nYXl0ZWFjaGVyLm5ldC9UaGUtV2…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 184, Column 128: reference to entity "l" for which no system identifier could be generated
    …dC0xLVNjZW5lLTA0L2luZGV4cHIuaHRtbA==&l=block3" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 184, Column 401: NET-enabling start-tag requires SHORTTAG YES
    …umbs/36740.jpg?1361948283" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 187, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=37743&cu=aHR0cDovL3d3dy5tYWxlcG9ybnZpZHMuY29tLzAwNC…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 187, Column 108: reference to entity "l" for which no system identifier could be generated
    …Y29tLzAwNC9iZWxhbWkvMTkvaW5kZXguaHRt&l=block3" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 187, Column 368: NET-enabling start-tag requires SHORTTAG YES
    …umbs/37743.jpg?1361929565" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 188, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38702&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 188, Column 140: reference to entity "l" for which no system identifier could be generated
    …cmVlZC10b2lsZXRzZXgvcHJpbW94Lmh0bWw=&l=block3" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 188, Column 423: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38702.jpg?1362354881" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 189, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38794&cu=aHR0cDovL2NsaWNrc2FnZW50LmNvbS9pbi8xZmVycm…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 189, Column 88: reference to entity "l" for which no system identifier could be generated
    …aWNrc2FnZW50LmNvbS9pbi8xZmVycmg5cw==&l=block3" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 189, Column 375: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38794.jpg?1362301462" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 190, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38781&cu=aHR0cDovL2NsaWNrc2FnZW50LmNvbS9pbi8xZmVycm…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 190, Column 88: reference to entity "l" for which no system identifier could be generated
    …aWNrc2FnZW50LmNvbS9pbi8xZmVycmg5cw==&l=block3" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 190, Column 427: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38781.jpg?1362276391" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 193, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38425&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 193, Column 132: reference to entity "l" for which no system identifier could be generated
    …b2NrbWFzc2FnZXBvcm4vZWhndXkuaHRtbA==&l=block3" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 193, Column 408: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38425.jpg?1362239122" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 194, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38459&cu=aHR0cDovL2NsaWNrc2FnZW50LmNvbS9pbi8xZmVycm…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 194, Column 88: reference to entity "l" for which no system identifier could be generated
    …aWNrc2FnZW50LmNvbS9pbi8xZmVycmg5cw==&l=block3" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 194, Column 352: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38459.jpg?1362281721" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 195, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38000&cu=aHR0cDovL3d3dy5nYXl0dWJlZGVtb24uY29tLzEtNy…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 195, Column 104: reference to entity "l" for which no system identifier could be generated
    …b24uY29tLzEtNy0wL2EvOC8zLzI2Ny5odG0=&l=block3" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 195, Column 360: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38000.jpg?1362192455" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 196, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38460&cu=aHR0cDovL2NsaWNrc2FnZW50LmNvbS9pbi8xZmVycm…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 196, Column 88: reference to entity "l" for which no system identifier could be generated
    …aWNrc2FnZW50LmNvbS9pbi8xZmVycmg5cw==&l=block3" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 196, Column 355: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38460.jpg?1362261694" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 199, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=37648&cu=aHR0cDovL2NsaWNrc2FnZW50LmNvbS9pbi8xZmVycm…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 199, Column 88: reference to entity "l" for which no system identifier could be generated
    …aWNrc2FnZW50LmNvbS9pbi8xZmVycmg5cw==&l=block3" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 199, Column 369: NET-enabling start-tag requires SHORTTAG YES
    …umbs/37648.jpg?1362350228" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 200, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38479&cu=aHR0cDovL2dhbGxlcnkuZGFuaWVsMTkuY29tL3dtdi…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 200, Column 100: reference to entity "l" for which no system identifier could be generated
    …aWVsMTkuY29tL3dtdi8yMS9pbmRleC5odG1s&l=block3" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 200, Column 354: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38479.jpg?1362359921" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 201, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38475&cu=aHR0cDovL2dhbGxlcnkuYXJjaGllMTkuY29tLzE4L2…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 201, Column 96: reference to entity "l" for which no system identifier could be generated
    …YXJjaGllMTkuY29tLzE4L2luZGV4Lmh0bWw=&l=block3" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 201, Column 346: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38475.jpg?1362189048" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 202, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=37752&cu=aHR0cDovL2NsaWNrc2FnZW50LmNvbS9pbi8xZmVycm…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 202, Column 88: reference to entity "l" for which no system identifier could be generated
    …aWNrc2FnZW50LmNvbS9pbi8xZmVycmg5cw==&l=block3" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 202, Column 354: NET-enabling start-tag requires SHORTTAG YES
    …umbs/37752.jpg?1362239107" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 205, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=37473&cu=aHR0cDovL3d3dy5mcmVlZ2F5cG9ybmNsdWIuY29tLz…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 205, Column 108: reference to entity "l" for which no system identifier could be generated
    …dWIuY29tLzExYXVnMTEtMTIvaW5kZXguaHRt&l=block3" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 205, Column 368: NET-enabling start-tag requires SHORTTAG YES
    …umbs/37473.jpg?1362067844" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 206, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38018&cu=aHR0cDovL2NsaWNrc2FnZW50LmNvbS9pbi8xZmVycm…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 206, Column 88: reference to entity "l" for which no system identifier could be generated
    …aWNrc2FnZW50LmNvbS9pbi8xZmVycmg5cw==&l=block3" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 206, Column 348: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38018.jpg?1362195762" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 207, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=36891&cu=aHR0cDovL3d3dy5zdW5ueS10aHVtYnMuY29tL2dhbG…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 207, Column 140: reference to entity "l" for which no system identifier could be generated
    …c3R1ZGlvcy8xMC8xNy9ybW92c2lvLmh0bWw=&l=block3" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 207, Column 423: NET-enabling start-tag requires SHORTTAG YES
    …umbs/36891.jpg?1361917426" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 208, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38850&cu=aHR0cDovL2NsaWNrc2FnZW50LmNvbS9pbi8xZmVycm…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 208, Column 88: reference to entity "l" for which no system identifier could be generated
    …aWNrc2FnZW50LmNvbS9pbi8xZmVycmg5cw==&l=block3" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 208, Column 356: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38850.jpg?1362287427" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 212, Column 143: required attribute "ALT" not specified
    …artnership.com/pink-twink/468-60-1.gif" width="468" height="60" 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>.

  • Error Line 218, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38433&cu=aHR0cDovL2NsaWNrc2FnZW50LmNvbS9pbi8xZmVycm…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 218, Column 88: reference to entity "l" for which no system identifier could be generated
    …aWNrc2FnZW50LmNvbS9pbi8xZmVycmg5cw==&l=block4" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 218, Column 347: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38433.jpg?1362245758" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 219, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38342&cu=aHR0cDovL3d3dy5mdGJveXMuY29tL3Bvcm5nYXkvaG…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 219, Column 116: reference to entity "l" for which no system identifier could be generated
    …aGVsaXgvMDAwMS0zNTA1L2luZGV4Lmh0bWw=&l=block4" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 219, Column 381: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38342.jpg?1361984304" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 220, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=37642&cu=aHR0cDovL2NsaWNrc2FnZW50LmNvbS9pbi8xZmVycm…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 220, Column 88: reference to entity "l" for which no system identifier could be generated
    …aWNrc2FnZW50LmNvbS9pbi8xZmVycmg5cw==&l=block4" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 220, Column 338: NET-enabling start-tag requires SHORTTAG YES
    …umbs/37642.jpg?1362215933" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 221, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=36595&cu=aHR0cDovL2NsaWNrc2FnZW50LmNvbS9pbi8xZmVycm…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 221, Column 88: reference to entity "l" for which no system identifier could be generated
    …aWNrc2FnZW50LmNvbS9pbi8xZmVycmg5cw==&l=block4" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 221, Column 371: NET-enabling start-tag requires SHORTTAG YES
    …umbs/36595.jpg?1362199390" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 224, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38440&cu=aHR0cDovL2NsaWNrc2FnZW50LmNvbS9pbi8xZmVycm…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 224, Column 88: reference to entity "l" for which no system identifier could be generated
    …aWNrc2FnZW50LmNvbS9pbi8xZmVycmg5cw==&l=block4" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 224, Column 363: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38440.jpg?1362311871" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 225, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=37536&cu=aHR0cDovL2NsaWNrc2FnZW50LmNvbS9pbi8xZmVycm…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 225, Column 88: reference to entity "l" for which no system identifier could be generated
    …aWNrc2FnZW50LmNvbS9pbi8xZmVycmg5cw==&l=block4" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 225, Column 346: NET-enabling start-tag requires SHORTTAG YES
    …umbs/37536.jpg?1362101447" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 226, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38420&cu=aHR0cDovL3d3dy53ZWxvdmVnYXltZW4uY29tL2dhbG…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 226, Column 120: reference to entity "l" for which no system identifier could be generated
    …L3N1aXRlMi9kYXZpZDQ3NS9laGd1eS5odG1s&l=block4" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 226, Column 389: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38420.jpg?1362364676" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 227, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38104&cu=aHR0cDovL2NsaWNrc2FnZW50LmNvbS9pbi8xZmVycm…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 227, Column 88: reference to entity "l" for which no system identifier could be generated
    …aWNrc2FnZW50LmNvbS9pbi8xZmVycmg5cw==&l=block4" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 227, Column 370: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38104.jpg?1362042646" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 230, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38417&cu=aHR0cDovL3d3dy5tYWxlcG9ybnZpZHMuY29tLzAwOC…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 230, Column 108: reference to entity "l" for which no system identifier could be generated
    …Y29tLzAwOC9oZWxpeC8yMC80MzAwLmh0bQ==&l=block4" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 230, Column 366: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38417.jpg?1362170079" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 231, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38448&cu=aHR0cDovL2NsaWNrc2FnZW50LmNvbS9pbi8xZmVycm…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 231, Column 88: reference to entity "l" for which no system identifier could be generated
    …aWNrc2FnZW50LmNvbS9pbi8xZmVycmg5cw==&l=block4" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 231, Column 198: cannot generate system identifier for general entity "p"
    …video/MTc1MTVs/BrokeCollegeBoys-video&p=80'; return true;" onmouseout="window.…

    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.

  • Error Line 231, Column 198: general entity "p" not defined and no default entity
    …video/MTc1MTVs/BrokeCollegeBoys-video&p=80'; return true;" onmouseout="window.…

    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.

  • Error Line 231, Column 199: reference to entity "p" for which no system identifier could be generated
    …ideo/MTc1MTVs/BrokeCollegeBoys-video&p=80'; return true;" onmouseout="window.s…

    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.

  • Info Line 231, Column 197: entity was defined here
    …/video/MTc1MTVs/BrokeCollegeBoys-video&p=80'; return true;" onmouseout="window…
  • Warning Line 231, Column 374: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38448.jpg?1362355783" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 232, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38846&cu=aHR0cDovL2NsaWNrc2FnZW50LmNvbS9pbi8xZmVycm…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 232, Column 88: reference to entity "l" for which no system identifier could be generated
    …aWNrc2FnZW50LmNvbS9pbi8xZmVycmg5cw==&l=block4" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 232, Column 359: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38846.jpg?1362351301" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 233, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38689&cu=aHR0cDovL2NsaWNrc2FnZW50LmNvbS9pbi8xZmVycm…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 233, Column 88: reference to entity "l" for which no system identifier could be generated
    …aWNrc2FnZW50LmNvbS9pbi8xZmVycmg5cw==&l=block4" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 233, Column 352: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38689.jpg?1362256136" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 236, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38822&cu=aHR0cDovL2NsaWNrc2FnZW50LmNvbS9pbi8xZmVycm…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 236, Column 88: reference to entity "l" for which no system identifier could be generated
    …aWNrc2FnZW50LmNvbS9pbi8xZmVycmg5cw==&l=block4" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 236, Column 368: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38822.jpg?1362359951" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 237, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38783&cu=aHR0cDovL2NsaWNrc2FnZW50LmNvbS9pbi8xZmVycm…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 237, Column 88: reference to entity "l" for which no system identifier could be generated
    …aWNrc2FnZW50LmNvbS9pbi8xZmVycmg5cw==&l=block4" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 237, Column 427: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38783.jpg?1362364567" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 238, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=37205&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 238, Column 124: reference to entity "l" for which no system identifier could be generated
    …cm9vbS9iaWdnYXljb2NrL3ByaW1veC5odG1s&l=block4" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 238, Column 396: NET-enabling start-tag requires SHORTTAG YES
    …umbs/37205.jpg?1361984294" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 239, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=37981&cu=aHR0cDovL2NsaWNrc2FnZW50LmNvbS9pbi8xZmVycm…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 239, Column 88: reference to entity "l" for which no system identifier could be generated
    …aWNrc2FnZW50LmNvbS9pbi8xZmVycmg5cw==&l=block4" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 239, Column 370: NET-enabling start-tag requires SHORTTAG YES
    …umbs/37981.jpg?1361976242" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 242, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38862&cu=aHR0cDovL2NsaWNrc2FnZW50LmNvbS9pbi8xZmVycm…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 242, Column 88: reference to entity "l" for which no system identifier could be generated
    …aWNrc2FnZW50LmNvbS9pbi8xZmVycmg5cw==&l=block4" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 242, Column 355: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38862.jpg?1362347044" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 243, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38472&cu=aHR0cDovL2NsaWNrc2FnZW50LmNvbS9pbi8xZmVycm…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 243, Column 88: reference to entity "l" for which no system identifier could be generated
    …aWNrc2FnZW50LmNvbS9pbi8xZmVycmg5cw==&l=block4" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 243, Column 336: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38472.jpg?1362203606" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 244, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38699&cu=aHR0cDovL2NsaWNrc2FnZW50LmNvbS9pbi8xZmVycm…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 244, Column 88: reference to entity "l" for which no system identifier could be generated
    …aWNrc2FnZW50LmNvbS9pbi8xZmVycmg5cw==&l=block4" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 244, Column 385: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38699.jpg?1362360445" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 245, Column 37: reference to entity "cu" for which no system identifier could be generated
        <td><a href="link.php?g=38101&cu=aHR0cDovL2NsaWNrc2FnZW50LmNvbS9pbi8xZmVycm…

    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.

  • Info Line 102, Column 34: entity was defined here
        <td><a href="link.php?g=35721&cu=aHR0cDovL3d3dy5nYXlkYW5keS5jb20vZnJlZWdheW…
  • Error Line 245, Column 88: reference to entity "l" for which no system identifier could be generated
    …aWNrc2FnZW50LmNvbS9pbi8xZmVycmg5cw==&l=block4" onmouseover="window.status='htt…

    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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Warning Line 245, Column 362: NET-enabling start-tag requires SHORTTAG YES
    …umbs/38101.jpg?1361892331" width="250" height="300" alt="" title="" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 280, Column 59: reference to entity "l" for which no system identifier could be generated
    …rong> <a href="link.php?t=hugecockmens.com&l=toptrader">Huge Cock Mens</a> <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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Error Line 281, Column 56: reference to entity "l" for which no system identifier could be generated
    …>2.</strong> <a href="link.php?t=mannsucht.com&l=toptrader">Mann Sucht</a> <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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Error Line 282, Column 57: reference to entity "l" for which no system identifier could be generated
    …</strong> <a href="link.php?t=dickmengay.com&l=toptrader">Dick Men Gay</a> <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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Error Line 283, Column 59: reference to entity "l" for which no system identifier could be generated
    …rong> <a href="link.php?t=hotpenismale.com&l=toptrader">Hot penis male</a> <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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Error Line 284, Column 58: reference to entity "l" for which no system identifier could be generated
    …</strong> <a href="link.php?t=hotgaysguys.com&l=toptrader">HotGaysGuys</a> <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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Error Line 285, Column 57: reference to entity "l" for which no system identifier could be generated
    ….</strong> <a href="link.php?t=uominifoto.com&l=toptrader">Uomini Foto</a> <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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Error Line 286, Column 56: reference to entity "l" for which no system identifier could be generated
    …g>7.</strong> <a href="link.php?t=avechomme.com&l=toptrader">AvecHomme</a> <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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Error Line 287, Column 57: reference to entity "l" for which no system identifier could be generated
    …</strong> <a href="link.php?t=boygayslut.com&l=toptrader">Boy Gay Slut</a> <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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Error Line 288, Column 58: reference to entity "l" for which no system identifier could be generated
    …strong> <a href="link.php?t=clipsgaymen.com&l=toptrader">Clips Gay Men</a> <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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Error Line 289, Column 55: reference to entity "l" for which no system identifier could be generated
    …rong>10.</strong> <a href="link.php?t=mannern.com&l=toptrader">Mannern</a> <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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Error Line 291, Column 59: reference to entity "l" for which no system identifier could be generated
    …/strong> <a href="link.php?t=uominivideo.com&l=toptrader">Uomini Video</a> <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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Error Line 292, Column 56: reference to entity "l" for which no system identifier could be generated
    …g>12.</strong> <a href="link.php?t=gayhouse.biz&l=toptrader">Gay House</a> <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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Error Line 293, Column 58: reference to entity "l" for which no system identifier could be generated
    …</strong> <a href="link.php?t=boywithboy.net&l=toptrader">Boy with Boy</a> <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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Error Line 294, Column 59: reference to entity "l" for which no system identifier could be generated
    …/strong> <a href="link.php?t=ragazzifoto.com&l=toptrader">Ragazzi Foto</a> <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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Error Line 295, Column 60: reference to entity "l" for which no system identifier could be generated
    …rong> <a href="link.php?t=penismalegay.com&l=toptrader">Penis male gay</a> <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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Error Line 296, Column 61: reference to entity "l" for which no system identifier could be generated
    …rong> <a href="link.php?t=gay-boys-tube.com&l=toptrader">Gay Boys Tube</a> <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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Error Line 297, Column 59: reference to entity "l" for which no system identifier could be generated
    …strong> <a href="link.php?t=gaymanspics.com&l=toptrader">Gay Mens Pics</a> <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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Error Line 298, Column 59: reference to entity "l" for which no system identifier could be generated
    …strong> <a href="link.php?t=boygayvideo.net&l=toptrader">Boy Gay Video</a> <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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Error Line 299, Column 57: reference to entity "l" for which no system identifier could be generated
    …19.</strong> <a href="link.php?t=uominiblu.com&l=toptrader">Uomini Blu</a> <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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Error Line 300, Column 61: reference to entity "l" for which no system identifier could be generated
    …ng> <a href="link.php?t=sexgaypicture.com&l=toptrader">Sex Gay Picture</a> <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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Error Line 301, Column 59: reference to entity "l" for which no system identifier could be generated
    …strong> <a href="link.php?t=tubeboysgay.com&l=toptrader">Tube Boys Gay</a> <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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Error Line 302, Column 60: reference to entity "l" for which no system identifier could be generated
    …strong> <a href="link.php?t=rich-gay-men.com&l=toptrader">Rich Gay Men</a> <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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Error Line 303, Column 60: reference to entity "l" for which no system identifier could be generated
    …rong> <a href="link.php?t=gaybadyfresh.com&l=toptrader">Gay Bady Fresh</a> <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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Error Line 304, Column 56: reference to entity "l" for which no system identifier could be generated
    …ng>24.</strong> <a href="link.php?t=unehomme.com&l=toptrader">UneHomme</a> <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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Error Line 305, Column 70: reference to entity "l" for which no system identifier could be generated
    …ink.php?t=jungle-juice-gaymovies.com&l=toptrader">Gaymovies von Jungle Juice 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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Error Line 307, Column 58: reference to entity "l" for which no system identifier could be generated
    …ong> <a href="link.php?t=gaytopporn.net&l=toptrader">GAY TOP PORN TUBE</a> <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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Error Line 308, Column 59: reference to entity "l" for which no system identifier could be generated
    …strong> <a href="link.php?t=clipsgaymen.net&l=toptrader">Clips Gay Men</a> <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.

  • Info Line 102, Column 166: entity was defined here
    …5vd19nYXl2aWRlb3RncF9oZWxvcmQuaHRtbA==&l=block1" onmouseover="window.status='h…
  • Error Line 324, Column 138: required attribute "ALT" not specified
    …tnership.com/pink-twink/200-300-2.gif" width="200" height="300" 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>.

  • Error Line 331, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <P><SPAN>&copy; <A href="http://videosgratishombres.com/">videosgratishombres.c…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 332, Column 7: end tag for "FONT" omitted, but its declaration does not permit this
    </body>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 330, Column 1: start tag was here
    <font size="2" Color="#F0F8FF"  face="georgia">		
  • Error Line 332, Column 7: end tag for "CENTER" omitted, but its declaration does not permit this
    </body>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 329, Column 1: start tag was here
    <center>
  • Error Line 332, Column 7: end tag for "DIV" omitted, but its declaration does not permit this
    </body>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 211, Column 1: start tag was here
    <div align="center"> <a href="http://unehomme.com/">UneHomme </a> - <a href="ht…
  • Error Line 332, Column 7: end tag for "DIV" omitted, but its declaration does not permit this
    </body>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 176, Column 1: start tag was here
    <div align="center"> <a href="http://uominiblu.com/">Uomini Blu</a> - <a href="…
  • Error Line 332, Column 7: end tag for "CENTER" omitted, but its declaration does not permit this
    </body>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 64, Column 1: start tag was here
    <center>

Visitor Analysis

Daily Visitor
  • 222 visits