EZTV, your one stop source for all your favorite TV shows. ...

eztv.it
  • Domain Name
    eztv.it
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #1049
  • Page Size
    205.3 KB
  • Ip Address
    185.19.104.80
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    1 GIF, 0 JPG, 158 PNG

Website Meta Analysis

  • Title
    EZTV - TV Torrents Online
  • Meta Keyword
    EZTV, EZ TV, EZTV Efnet, EZTV@EFnet, eztvefnet.org, eztv.it, Easy TV, Televison, 24, Prison Break, Lost, Stargate, Battlestar, Heroes, House, Dexter, Torrent, BitTorrent, Downloading,
  • Meta Description
    EZTV, your one stop source for all your favorite TV shows.

Technical Analysis

  • Webserver
    lighttpd/2.0.0
  • Ip Address
    185.19.104.80
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from eztv.it.

HTML Analysis

  • x-powered-by: PHP/5.5.1-2
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • content-type: text/html
  • vary: Accept-Encoding
  • content-encoding: gzip
  • date: Fri, 04 Oct 2013 11:15:59 GMT
  • server: lighttpd/2.0.0
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

*********************************************************************
* Please note that the following result could be a subgroup of *
* the data contained in the database. *
* *
* Additional information can be visualized at: *
* http://www.nic.it/cgi-bin/Whois/whois.cgi *
*********************************************************************

Domain: eztv.it
Status: ok
Created: 2007-06-14 11:46:17
Last Update: 2012-06-30 02:53:22
Expire Date: 2013-06-14

Registrant
Name: EuroDNS S.A.
Organization: EuroDNS S.A.
ContactID: EURO8
Address: 2, rue Leon Laval
Leudelange
3372
LUXEMBOURG
LU
Created: 2007-03-01 10:26:06
Last Update: 2009-11-24 14:15:08

Admin Contact
Name: EuroDNS S.A.
Organization: EuroDNS S.A.
ContactID: EURO8
Address: 2, rue Leon Laval
Leudelange
3372
LUXEMBOURG
LU
Created: 2007-03-01 10:26:06
Last Update: 2009-11-24 14:15:08

Technical Contacts
Name: King Nova
Organization: King Nova
ContactID: EDS-T4375001
Address: Ekensbergsvgen 91
SOLNA
16931
-
SE
Created: 2010-11-24 12:39:28
Last Update: 2011-04-24 16:46:59

Registrar
Organization: EuroDNS SA
Name: EURODNS-REG
Web: http://www.eurodns.com

Nameservers
ns1.ezdns.it
ns2.ezdns.it
ns3.ezdns.it
ns4.ezdns.it
ns5.ezdns.it

DNS Analysis


DNS servers
ns1.ezdns.it [192.121.121.14]
ns2.ezdns.it [78.138.97.33]
ns3.ezdns.it [85.17.200.248]
ns4.ezdns.it [95.211.32.161]
ns5.ezdns.it [72.232.162.197]

DNS Records

Answer records
eztv.it SOA
server: ns1.ezdns.it
email: webmaster@eztv.it
serial: 2012083101
refresh: 18000
retry: 18000
expire: 691200
minimum ttl: 18000
18000s
eztv.it NS  ns4.ezdns.it 18000s
eztv.it NS  ns3.ezdns.it 18000s
eztv.it NS  ns1.ezdns.it 18000s
eztv.it NS  ns2.ezdns.it 18000s
eztv.it NS  ns5.ezdns.it 18000s
eztv.it A 192.121.86.101 18000s
eztv.it MX
preference: 10
exchange: mail.eztv.it
18000s
eztv.it 28 [16 bytes] 18000s

Authority records

Additional records
ns1.ezdns.it A 192.121.86.100 18000s
ns2.ezdns.it A 78.138.97.33 18000s
ns3.ezdns.it A 78.138.98.82 18000s
ns4.ezdns.it A 72.232.162.197 18000s
ns5.ezdns.it A 192.121.121.14 18000s
mail.eztv.it A 72.232.162.195 18000s

IP 185.19.104.80 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • No whois ip data for 185.19.104.80

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 521 Errors
  • 137 Warnings
Ratio Text/Html
  • 0.880112050146721
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.

  • Warning Line 4, Column 96: NET-enabling start-tag requires SHORTTAG YES
    …iption" content="EZTV, your one stop source for all your favorite TV shows." />

    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.

  • Warning Line 5, Column 219: NET-enabling start-tag requires SHORTTAG YES
    …gate, Battlestar, Heroes, House, Dexter, Torrent, BitTorrent, Downloading, " />

    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 5, Column 219: document type does not allow element "META" here
    …gate, Battlestar, Heroes, House, Dexter, Torrent, BitTorrent, Downloading, " />

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

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

  • Warning Line 6, Column 69: NET-enabling start-tag requires SHORTTAG YES
    	<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />

    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 6, Column 69: document type does not allow element "META" here
    	<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />

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

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

  • Warning Line 7, Column 80: NET-enabling start-tag requires SHORTTAG YES
    …meta name="verify-v1" content="HfJckMzdut1OAtGdt9CiJPYlzbRAlmFMrZFEcGThxQ0=" />

    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 7, Column 80: document type does not allow element "META" here
    …meta name="verify-v1" content="HfJckMzdut1OAtGdt9CiJPYlzbRAlmFMrZFEcGThxQ0=" />

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

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

  • Warning Line 8, Column 48: NET-enabling start-tag requires SHORTTAG YES
    	<link rel="shortcut icon" href="/favicon.ico" />

    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 8, Column 48: document type does not allow element "LINK" here
    	<link rel="shortcut icon" href="/favicon.ico" />

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

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

  • Warning Line 9, Column 80: NET-enabling start-tag requires SHORTTAG YES
    …link rel="stylesheet" type="text/css" href="/styles/eztv.css" id="forum_css" />

    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 9, Column 80: document type does not allow element "LINK" here
    …link rel="stylesheet" type="text/css" href="/styles/eztv.css" id="forum_css" />

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

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

  • Warning Line 10, Column 88: NET-enabling start-tag requires SHORTTAG YES
    …="stylesheet" type="text/css" href="/styles/rating/eztv.css" id="rating_css" />

    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 10, Column 88: document type does not allow element "LINK" here
    …="stylesheet" type="text/css" href="/styles/rating/eztv.css" id="rating_css" />

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

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

  • Error Line 23, Column 8: end tag for element "HEAD" which is not open
    	</head>

    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.

  • Error Line 24, Column 7: document type does not allow element "BODY" here
    	<body>

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

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

  • Warning Line 26, Column 206: NET-enabling start-tag requires SHORTTAG YES
    … border="0" width="303" height="115" alt="EZTV.IT" title="EZTV.IT" /></a></div>

    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 48, Column 13: ID "GAP" already defined
    			<div id="gap"></div><table border="0" width="950" align="center" cellspacing…

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

  • Info Line 46, Column 13: ID "GAP" first defined here
    			<div id="gap"></div>
  • Error Line 48, Column 233: document type does not allow element "TABLE" here
    …50" align="center" class="forum_header_border" cellspacing="0" cellpadding="0">

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

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

  • Error Line 55, Column 88: there is no attribute "NAME"
    …lspacing="0" cellpadding="0"><tr name="hover"><td class="forum_thread_post_end…

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

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

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

  • Error Line 65, Column 115: there is no attribute "ALT"
    …rth-sharing/" class="thread_link" alt="Start your own TV site, software worth …

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

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

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

  • Error Line 113, Column 96: "THE" is not a member of a group specified for any attribute
    …y-cbs/" class="thread_link" alt=""The Job" fired by CBS" title=""The Job" fire…
  • Error Line 113, Column 99: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …bs/" class="thread_link" alt=""The Job" fired by CBS" title=""The Job" fired b…

    Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".

  • Error Line 144, Column 150: document type does not allow element "TABLE" here
    …" style="border-top: 0px; border-bottom: 0px;" cellspacing="0" cellpadding="0">

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

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

  • Warning Line 149, Column 5: NET-enabling start-tag requires SHORTTAG YES
    <BR />

    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 149, Column 5: document type does not allow element "BR" here; assuming missing "CAPTION" start-tag
    <BR />
  • Error Line 150, Column 105: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …50" align="center" class="forum_header_border" cellspacing="0" cellpadding="0">

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

  • Warning Line 156, Column 130: NET-enabling start-tag requires SHORTTAG YES
    …or new seeders who can <b>sustain 10mbit and/or higher upload</b> speeds!<BR />

    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.

  • Warning Line 157, Column 8: NET-enabling start-tag requires SHORTTAG YES
    			<BR />

    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.

  • Warning Line 158, Column 126: NET-enabling start-tag requires SHORTTAG YES
    …t least five new torrents a day, likes the thought of receiving the shows<BR />

    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.

  • Warning Line 159, Column 140: NET-enabling start-tag requires SHORTTAG YES
    …d have some free time - please stop by our IRC channel and contact an op.<BR />

    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.

  • Warning Line 172, Column 97: NET-enabling start-tag requires SHORTTAG YES
    …submit" name="submit" value="Login" id="login_submit" style="display: none;" />

    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 178, Column 32: ID "FORM_SUBMIT_BUTTON" already defined
    						<a href="/register/" id="form_submit_button" class="form_action_button_le…

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

  • Info Line 173, Column 41: ID "FORM_SUBMIT_BUTTON" first defined here
    …				<a href="javascript:void(0);" id="form_submit_button" class="form_action_b…
  • Error Line 192, Column 29: value of attribute "TYPE" cannot be "TXT"; must be one of "TEXT", "PASSWORD", "CHECKBOX", "RADIO", "SUBMIT", "RESET", "FILE", "HIDDEN", "IMAGE", "BUTTON"
    				Search: <input type="txt" name="SearchString1" size="47" value="" /> or&nbs…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Warning Line 192, Column 71: NET-enabling start-tag requires SHORTTAG YES
    …		Search: <input type="txt" name="SearchString1" size="47" value="" /> or&nbsp;

    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.

  • Warning Line 202, Column 96: NET-enabling start-tag requires SHORTTAG YES
    …bmit" value="Search" name="search" id="search_submit" style="display: none;" />

    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 203, Column 38: ID "FORM_SUBMIT_BUTTON" already defined
    			<a href="javascript:void(0);" id="form_submit_button" class="form_action_but…

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

  • Info Line 173, Column 41: ID "FORM_SUBMIT_BUTTON" first defined here
    …				<a href="javascript:void(0);" id="form_submit_button" class="form_action_b…
  • Warning Line 212, Column 5: NET-enabling start-tag requires SHORTTAG YES
    <BR />

    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 214, Column 105: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …50" align="center" class="forum_header_border" cellspacing="0" cellpadding="0">

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

  • Warning Line 220, Column 148: NET-enabling start-tag requires SHORTTAG YES
    …///ezimg.it/f/tpb_afk/thumbnail.png" width="215" height="125" border="0" /></a>

    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 148: required attribute "ALT" not specified
    …///ezimg.it/f/tpb_afk/thumbnail.png" width="215" height="125" 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>.

  • Warning Line 223, Column 81: NET-enabling start-tag requires SHORTTAG YES
    …<a href="/ep/41921/tpb-afk-2013-720p-h264-simonklose/"><b>TPB AFK</b></a><br />

    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 228, Column 15: syntax of attribute value does not conform to declared value
    		<td valign="" class="forum_header featured_links" rowspan="2">

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 228, Column 15: value of attribute "VALIGN" cannot be ""; must be one of "TOP", "MIDDLE", "BOTTOM", "BASELINE"
    		<td valign="" class="forum_header featured_links" rowspan="2">

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Warning Line 229, Column 587: cannot generate system identifier for general entity "name"
    …%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&s…

    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 229, Column 587: general entity "name" not defined and no default entity
    …%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&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.

  • Error Line 229, Column 591: reference to entity "name" for which no system identifier could be generated
    …racker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&subid…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Warning Line 229, Column 626: cannot generate system identifier for general entity "subid"
    …ame=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct Do…

    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 229, Column 626: general entity "subid" not defined and no default entity
    …ame=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct Do…

    This is usually a cascading error caused by 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 229, Column 631: reference to entity "subid" for which no system identifier could be generated
    …PB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct Downloa…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 229, Column 753: cannot generate system identifier for general entity "tr"
    …16060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/"…

    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 229, Column 753: general entity "tr" not defined and no default entity
    …16060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/"…

    This is usually a cascading error caused by 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 229, Column 755: reference to entity "tr" for which no system identifier could be generated
    …060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/" c…

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

  • Info Line 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 231, Column 153: value of attribute "ALIGN" cannot be "ABSMIDDLE"; must be one of "TOP", "MIDDLE", "BOTTOM", "LEFT", "RIGHT"
    …eight="16" border="0" align="absmiddle" title="Donate to this featured release…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Warning Line 231, Column 195: NET-enabling start-tag requires SHORTTAG YES
    …16" border="0" align="absmiddle" title="Donate to this featured release" /></a>

    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 195: required attribute "ALT" not specified
    …16" border="0" align="absmiddle" title="Donate to this featured release" /></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 234, Column 142: value of attribute "ALIGN" cannot be "ABSMIDDLE"; must be one of "TOP", "MIDDLE", "BOTTOM", "LEFT", "RIGHT"
    …eight="16" border="0" align="absmiddle" title="Promote this featured release" …

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Warning Line 234, Column 182: NET-enabling start-tag requires SHORTTAG YES
    …="16" border="0" align="absmiddle" title="Promote this featured release" /></a>

    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 234, Column 182: required attribute "ALT" not specified
    …="16" border="0" align="absmiddle" title="Promote this featured release" /></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 237, Column 172: value of attribute "ALIGN" cannot be "ABSMIDDLE"; must be one of "TOP", "MIDDLE", "BOTTOM", "LEFT", "RIGHT"
    …idth="16" height="16" align="absmiddle" alt="8 comments" title="8 forum commen…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Warning Line 237, Column 216: NET-enabling start-tag requires SHORTTAG YES
    … height="16" align="absmiddle" alt="8 comments" title="8 forum comments" /></a>

    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 143: value of attribute "ALIGN" cannot be "ABSMIDDLE"; must be one of "TOP", "MIDDLE", "BOTTOM", "LEFT", "RIGHT"
    …eight="16" border="0" align="absmiddle" title="Visit this featured releases we…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Warning Line 239, Column 190: NET-enabling start-tag requires SHORTTAG YES
    …order="0" align="absmiddle" title="Visit this featured releases website" /></a>

    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 190: required attribute "ALT" not specified
    …order="0" align="absmiddle" title="Visit this featured releases website" /></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>.

  • Warning Line 243, Column 5: NET-enabling start-tag requires SHORTTAG YES
    <br />

    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 49: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
        <table width="950" border="0" align="center">

    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 254, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    	<div id="tooltip" class="ajaxtooltip"></div>

    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 255, Column 106: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …50" align="center" cellspacing="0" cellpadding="0" class="forum_header_border">

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

  • Warning Line 278, Column 126: cannot generate system identifier for general entity "dn"
    …AC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1of…

    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 278, Column 126: general entity "dn" not defined and no default entity
    …AC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1of…

    This is usually a cascading error caused by 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 278, Column 128: reference to entity "dn" for which no system identifier could be generated
    …7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1of5.…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 278, Column 220: reference to entity "tr" for which no system identifier could be generated
    …he.Limit.720p.x264.AAC.HDTV-MVGroup&tr=http://www.mvgroup.org:2710/announce&tr…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 278, Column 260: reference to entity "tr" for which no system identifier could be generated
    …ttp://www.mvgroup.org:2710/announce&tr=udp://tracker.ccc.de:80/announce&tr=udp…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 278, Column 296: reference to entity "tr" for which no system identifier could be generated
    …tr=udp://tracker.ccc.de:80/announce&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 278, Column 335: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 278, Column 368: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 278, Column 1129: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=Attenboroughs%20Natural%20Curiosities%2…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 278, Column 1246: reference to entity "subid" for which no system identifier could be generated
    …720p%20x264%20AAC%20HDTV-MVGroup&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 280, Column 294: NET-enabling start-tag requires SHORTTAG YES
    …0" width="16" height="16" alt="2 comments" title="2 forum comments" /></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 287, Column 128: reference to entity "dn" for which no system identifier could be generated
    …F6B9B0B172940E2104DA733A27F1B65F6C4&dn=All.Aboard.06of12.Australia.The.Indian.…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 287, Column 205: reference to entity "tr" for which no system identifier could be generated
    ….Pacific.x264.720p.AC3.HDTV-MVGroup&tr=http://www.mvgroup.org:2710/announce&tr…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 287, Column 245: reference to entity "tr" for which no system identifier could be generated
    …ttp://www.mvgroup.org:2710/announce&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 287, Column 284: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 287, Column 317: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 287, Column 998: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=All%20Aboard%2006of12%20Australia%20The…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 287, Column 1098: reference to entity "subid" for which no system identifier could be generated
    …x264%20720p%20AC3%20HDTV-MVGroup&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 289, Column 279: NET-enabling start-tag requires SHORTTAG YES
    …0" width="16" height="16" alt="2 comments" title="2 forum comments" /></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 296, Column 128: reference to entity "dn" for which no system identifier could be generated
    …4981395AF750ECC309C52C74ECA3B6A8817&dn=Ch4.Lost.Worlds.The.Story.of.Archaeolog…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 296, Column 217: reference to entity "tr" for which no system identifier could be generated
    …Future.of.the.Past.XviD.AC3-MVGroup&tr=http://www.mvgroup.org:2710/announce&tr…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 296, Column 257: reference to entity "tr" for which no system identifier could be generated
    …ttp://www.mvgroup.org:2710/announce&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 296, Column 296: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 296, Column 329: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 296, Column 1034: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=Ch4%20Lost%20Worlds%20The%20Story%20of%…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 296, Column 1154: reference to entity "subid" for which no system identifier could be generated
    …0the%20Past%20XviD%20AC3-MVGroup&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 298, Column 291: NET-enabling start-tag requires SHORTTAG YES
    …0" width="16" height="16" alt="2 comments" title="2 forum comments" /></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.

  • Warning Line 301, Column 506: NET-enabling start-tag requires SHORTTAG YES
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></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 301, Column 506: required attribute "ALT" not specified
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></a></td>

    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 305, Column 120: reference to entity "dn" for which no system identifier could be generated
    …ih:4OBZH5BIRG4DHOHEQNNBUUMBQICULUXV&dn=Justified.S04E08.720p.HDTV.x264-EVOLVE&…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 305, Column 162: reference to entity "tr" for which no system identifier could be generated
    …tified.S04E08.720p.HDTV.x264-EVOLVE&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 305, Column 201: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 305, Column 234: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 305, Column 1335: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=Justified%20S04E08%20720p%20HDTV%20x264…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 305, Column 1388: reference to entity "subid" for which no system identifier could be generated
    …4E08%20720p%20HDTV%20x264-EVOLVE&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 307, Column 222: NET-enabling start-tag requires SHORTTAG YES
    …idth="16" height="16" alt="Discuss" title="Discuss about this show" /></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.

  • Warning Line 310, Column 514: NET-enabling start-tag requires SHORTTAG YES
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></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 310, Column 514: required attribute "ALT" not specified
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></a></td>

    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 314, Column 120: reference to entity "dn" for which no system identifier could be generated
    …ih:4KO2XZPERXO7UCVLR7VFA5FXEHJD3TRP&dn=Criminal.Minds.S08E16.HDTV.x264-LOL&tr=…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 314, Column 159: reference to entity "tr" for which no system identifier could be generated
    …Criminal.Minds.S08E16.HDTV.x264-LOL&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 314, Column 198: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 314, Column 231: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 314, Column 1323: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=Criminal%20Minds%20S08E16%20HDTV%20x264…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 314, Column 1373: reference to entity "subid" for which no system identifier could be generated
    …Minds%20S08E16%20HDTV%20x264-LOL&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 316, Column 222: NET-enabling start-tag requires SHORTTAG YES
    …idth="16" height="16" alt="Discuss" title="Discuss about this show" /></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.

  • Warning Line 319, Column 492: NET-enabling start-tag requires SHORTTAG YES
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></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 319, Column 492: required attribute "ALT" not specified
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></a></td>

    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 323, Column 120: reference to entity "dn" for which no system identifier could be generated
    …ih:2FQOB2AFQ5AQAF26OTSHLQHOJARMX6M5&dn=Smash.S02E04.720p.HDTV.X264-DIMENSION&t…

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

  • Info Line 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 323, Column 161: reference to entity "tr" for which no system identifier could be generated
    …ash.S02E04.720p.HDTV.X264-DIMENSION&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 323, Column 200: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 323, Column 233: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 323, Column 1331: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=Smash%20S02E04%20720p%20HDTV%20X264-DIM…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 323, Column 1383: reference to entity "subid" for which no system identifier could be generated
    …4%20720p%20HDTV%20X264-DIMENSION&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 325, Column 222: NET-enabling start-tag requires SHORTTAG YES
    …idth="16" height="16" alt="Discuss" title="Discuss about this show" /></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.

  • Warning Line 328, Column 497: NET-enabling start-tag requires SHORTTAG YES
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></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 328, Column 497: required attribute "ALT" not specified
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></a></td>

    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 332, Column 120: reference to entity "dn" for which no system identifier could be generated
    …ih:WQLLQMFL37VZGNQSL53HXZSKJWWX3LLO&dn=Cult.S01E02.720p.HDTV.X264-DIMENSION&tr…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 332, Column 160: reference to entity "tr" for which no system identifier could be generated
    …ult.S01E02.720p.HDTV.X264-DIMENSION&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 332, Column 199: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 332, Column 232: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 332, Column 1327: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=Cult%20S01E02%20720p%20HDTV%20X264-DIME…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 332, Column 1378: reference to entity "subid" for which no system identifier could be generated
    …2%20720p%20HDTV%20X264-DIMENSION&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 334, Column 222: NET-enabling start-tag requires SHORTTAG YES
    …idth="16" height="16" alt="Discuss" title="Discuss about this show" /></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.

  • Warning Line 337, Column 533: NET-enabling start-tag requires SHORTTAG YES
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></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 337, Column 533: required attribute "ALT" not specified
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></a></td>

    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 341, Column 120: reference to entity "dn" for which no system identifier could be generated
    …ih:HMBTWULZ4ZM4EGSBUWV6ECE2SGLX5SRD&dn=The.Lying.Game.S02E08.720p.HDTV.x264-IM…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 341, Column 168: reference to entity "tr" for which no system identifier could be generated
    ….Game.S02E08.720p.HDTV.x264-IMMERSE&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 341, Column 207: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 341, Column 240: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 341, Column 1359: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=The%20Lying%20Game%20S02E08%20720p%20HD…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 341, Column 1422: reference to entity "subid" for which no system identifier could be generated
    …E08%20720p%20HDTV%20x264-IMMERSE&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 343, Column 222: NET-enabling start-tag requires SHORTTAG YES
    …idth="16" height="16" alt="Discuss" title="Discuss about this show" /></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.

  • Warning Line 346, Column 554: NET-enabling start-tag requires SHORTTAG YES
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></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 346, Column 554: required attribute "ALT" not specified
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></a></td>

    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 350, Column 120: reference to entity "dn" for which no system identifier could be generated
    …ih:MXPSWCL4CIFHR5GUEU6YQHC622WD6LLK&dn=The.Colbert.Report.2013.02.26.Dr.Michio…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 350, Column 183: reference to entity "tr" for which no system identifier could be generated
    …02.26.Dr.Michio.Kaku.HDTV.x264-LMAO&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 350, Column 222: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 350, Column 255: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 350, Column 1419: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=The%20Colbert%20Report%202013%2002%2026…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 350, Column 1505: reference to entity "subid" for which no system identifier could be generated
    …Michio%20Kaku%20HDTV%20x264-LMAO&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 352, Column 273: NET-enabling start-tag requires SHORTTAG YES
    …0" width="16" height="16" alt="3 comments" title="3 forum comments" /></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.

  • Warning Line 355, Column 527: NET-enabling start-tag requires SHORTTAG YES
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></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 355, Column 527: required attribute "ALT" not specified
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></a></td>

    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 359, Column 120: reference to entity "dn" for which no system identifier could be generated
    …ih:QOD4J5FGQQGRBHWJ6EDZDU43EWMTGTYM&dn=Face.Off.S04E07.Howl.At.The.Moon.HDTV.x…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 359, Column 174: reference to entity "tr" for which no system identifier could be generated
    ….Howl.At.The.Moon.HDTV.x264-CRiMSON&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 359, Column 213: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 359, Column 246: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 359, Column 1383: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=Face%20Off%20S04E07%20Howl%20At%20The%2…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 359, Column 1456: reference to entity "subid" for which no system identifier could be generated
    …The%20Moon%20HDTV%20x264-CRiMSON&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 361, Column 222: NET-enabling start-tag requires SHORTTAG YES
    …idth="16" height="16" alt="Discuss" title="Discuss about this show" /></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.

  • Warning Line 364, Column 576: NET-enabling start-tag requires SHORTTAG YES
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></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 364, Column 576: required attribute "ALT" not specified
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></a></td>

    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 368, Column 120: reference to entity "dn" for which no system identifier could be generated
    …ih:PMSH4AI7X3TZ3HDMSTQUUHQPELAHXOQJ&dn=The.Daily.Show.2013.02.26.Lori.Silverbu…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 368, Column 200: reference to entity "tr" for which no system identifier could be generated
    ….and.Kristi.Jacobson.HDTV.x264-LMAO&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 368, Column 239: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 368, Column 272: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 368, Column 1487: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=The%20Daily%20Show%202013%2002%2026%20L…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 368, Column 1594: reference to entity "subid" for which no system identifier could be generated
    …ti%20Jacobson%20HDTV%20x264-LMAO&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 370, Column 222: NET-enabling start-tag requires SHORTTAG YES
    …idth="16" height="16" alt="Discuss" title="Discuss about this show" /></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.

  • Warning Line 373, Column 490: NET-enabling start-tag requires SHORTTAG YES
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></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 373, Column 490: required attribute "ALT" not specified
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></a></td>

    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 377, Column 120: reference to entity "dn" for which no system identifier could be generated
    …ih:BBGQWPLL54XPXTHSTWKMP4ZGZLU3SIDX&dn=Justified.S04E08.HDTV.x264-2HD&tr=udp:/…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 377, Column 154: reference to entity "tr" for which no system identifier could be generated
    …X&dn=Justified.S04E08.HDTV.x264-2HD&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 377, Column 193: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 377, Column 226: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 377, Column 1303: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=Justified%20S04E08%20HDTV%20x264-2HD&su…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 377, Column 1346: reference to entity "subid" for which no system identifier could be generated
    …ified%20S04E08%20HDTV%20x264-2HD&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 379, Column 222: NET-enabling start-tag requires SHORTTAG YES
    …idth="16" height="16" alt="Discuss" title="Discuss about this show" /></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.

  • Warning Line 387, Column 507: NET-enabling start-tag requires SHORTTAG YES
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></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 387, Column 507: required attribute "ALT" not specified
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></a></td>

    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 391, Column 120: reference to entity "dn" for which no system identifier could be generated
    …ih:IWUEPU6CI6F6NSFZA3LKDYTZHPR3AEIN&dn=White.Collar.S04E15.HDTV.x264-ASAP&tr=u…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 391, Column 158: reference to entity "tr" for which no system identifier could be generated
    …=White.Collar.S04E15.HDTV.x264-ASAP&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 391, Column 197: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 391, Column 230: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 391, Column 1319: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=White%20Collar%20S04E15%20HDTV%20x264-A…

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

  • Info Line 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 391, Column 1368: reference to entity "subid" for which no system identifier could be generated
    …llar%20S04E15%20HDTV%20x264-ASAP&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 393, Column 222: NET-enabling start-tag requires SHORTTAG YES
    …idth="16" height="16" alt="Discuss" title="Discuss about this show" /></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.

  • Warning Line 396, Column 470: NET-enabling start-tag requires SHORTTAG YES
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></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 396, Column 470: required attribute "ALT" not specified
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></a></td>

    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 400, Column 120: reference to entity "dn" for which no system identifier could be generated
    …ih:XLDBBTI7MQXPZUS3KBUFOWABEYGKNOE3&dn=Smash.S02E04.HDTV.x264-LOL&tr=udp://tra…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 400, Column 150: reference to entity "tr" for which no system identifier could be generated
    …KNOE3&dn=Smash.S02E04.HDTV.x264-LOL&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 400, Column 189: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 400, Column 222: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 400, Column 1287: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=Smash%20S02E04%20HDTV%20x264-LOL&subid=…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 400, Column 1326: reference to entity "subid" for which no system identifier could be generated
    …Smash%20S02E04%20HDTV%20x264-LOL&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 402, Column 222: NET-enabling start-tag requires SHORTTAG YES
    …idth="16" height="16" alt="Discuss" title="Discuss about this show" /></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.

  • Warning Line 405, Column 475: NET-enabling start-tag requires SHORTTAG YES
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></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 405, Column 475: required attribute "ALT" not specified
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></a></td>

    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 409, Column 120: reference to entity "dn" for which no system identifier could be generated
    …ih:D76B3B353ZMT3FZ3G3DG3HDJOUWAOQJL&dn=Cult.S01E02.HDTV.x264-LOL&tr=udp://trac…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 409, Column 149: reference to entity "tr" for which no system identifier could be generated
    …WAOQJL&dn=Cult.S01E02.HDTV.x264-LOL&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 409, Column 188: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 409, Column 221: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 409, Column 1283: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=Cult%20S01E02%20HDTV%20x264-LOL&subid=e…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 409, Column 1321: reference to entity "subid" for which no system identifier could be generated
    …=Cult%20S01E02%20HDTV%20x264-LOL&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 411, Column 222: NET-enabling start-tag requires SHORTTAG YES
    …idth="16" height="16" alt="Discuss" title="Discuss about this show" /></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.

  • Warning Line 414, Column 527: NET-enabling start-tag requires SHORTTAG YES
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></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 414, Column 527: required attribute "ALT" not specified
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></a></td>

    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 418, Column 120: reference to entity "dn" for which no system identifier could be generated
    …ih:77AKE6DBUB6ZQ6OZMA5V7PFEB525LPLJ&dn=The.Mindy.Project.S01E16.HDTV.x264-LOL&…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 418, Column 162: reference to entity "tr" for which no system identifier could be generated
    ….Mindy.Project.S01E16.HDTV.x264-LOL&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 418, Column 201: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 418, Column 234: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 418, Column 1335: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=The%20Mindy%20Project%20S01E16%20HDTV%2…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 418, Column 1390: reference to entity "subid" for which no system identifier could be generated
    …oject%20S01E16%20HDTV%20x264-LOL&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 420, Column 222: NET-enabling start-tag requires SHORTTAG YES
    …idth="16" height="16" alt="Discuss" title="Discuss about this show" /></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.

  • Warning Line 423, Column 526: NET-enabling start-tag requires SHORTTAG YES
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></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 423, Column 526: required attribute "ALT" not specified
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></a></td>

    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 427, Column 120: reference to entity "dn" for which no system identifier could be generated
    …ih:ZZECBQZQ36SA5VFJJ7O3VEHISLPFG4Y5&dn=NCIS.Los.Angeles.S04E16.HDTV.x264-2HD&t…

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

  • Info Line 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 427, Column 161: reference to entity "tr" for which no system identifier could be generated
    …IS.Los.Angeles.S04E16.HDTV.x264-2HD&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 427, Column 200: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 427, Column 233: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 427, Column 1331: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=NCIS%20Los%20Angeles%20S04E16%20HDTV%20…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 427, Column 1385: reference to entity "subid" for which no system identifier could be generated
    …geles%20S04E16%20HDTV%20x264-2HD&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 429, Column 222: NET-enabling start-tag requires SHORTTAG YES
    …idth="16" height="16" alt="Discuss" title="Discuss about this show" /></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.

  • Warning Line 432, Column 506: NET-enabling start-tag requires SHORTTAG YES
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></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 432, Column 506: required attribute "ALT" not specified
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></a></td>

    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 436, Column 120: reference to entity "dn" for which no system identifier could be generated
    …ih:2LKP5WZ56PONJ25Q6HLG6TEZGOAXCDFN&dn=Cougar.Town.S04E08.HDTV.x264-EVOLVE&tr=…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 436, Column 159: reference to entity "tr" for which no system identifier could be generated
    …Cougar.Town.S04E08.HDTV.x264-EVOLVE&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 436, Column 198: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 436, Column 231: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 436, Column 1323: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=Cougar%20Town%20S04E08%20HDTV%20x264-EV…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 436, Column 1373: reference to entity "subid" for which no system identifier could be generated
    …wn%20S04E08%20HDTV%20x264-EVOLVE&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 438, Column 222: NET-enabling start-tag requires SHORTTAG YES
    …idth="16" height="16" alt="Discuss" title="Discuss about this show" /></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.

  • Warning Line 441, Column 517: NET-enabling start-tag requires SHORTTAG YES
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></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 441, Column 517: required attribute "ALT" not specified
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></a></td>

    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 445, Column 120: reference to entity "dn" for which no system identifier could be generated
    …ih:GVSMLD5TQACTYO6WGRTO3PZHBCJUFSQY&dn=The.Lying.Game.S02E08.HDTV.x264-ASAP&tr…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 445, Column 160: reference to entity "tr" for which no system identifier could be generated
    …he.Lying.Game.S02E08.HDTV.x264-ASAP&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 445, Column 199: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 445, Column 232: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 445, Column 1194: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=The%20Lying%20Game%20S02E08%20HDTV%20x2…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 445, Column 1247: reference to entity "subid" for which no system identifier could be generated
    …Game%20S02E08%20HDTV%20x264-ASAP&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 447, Column 222: NET-enabling start-tag requires SHORTTAG YES
    …idth="16" height="16" alt="Discuss" title="Discuss about this show" /></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 454, Column 120: reference to entity "dn" for which no system identifier could be generated
    …ih:3TNVDE2SCW7HDR55E3XDSCPO4DSARATA&dn=Betty.Whites.Off.Their.Rockers.S02.Spec…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 454, Column 199: reference to entity "tr" for which no system identifier could be generated
    …al-The.Best.of.3.HDTV.x264-BAJSKORV&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 454, Column 238: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 454, Column 271: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 454, Column 1350: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=Betty%20Whites%20Off%20Their%20Rockers%…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 454, Column 1454: reference to entity "subid" for which no system identifier could be generated
    …%20of%203%20HDTV%20x264-BAJSKORV&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 456, Column 222: NET-enabling start-tag requires SHORTTAG YES
    …idth="16" height="16" alt="Discuss" title="Discuss about this show" /></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.

  • Warning Line 459, Column 465: NET-enabling start-tag requires SHORTTAG YES
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></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 459, Column 465: required attribute "ALT" not specified
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></a></td>

    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 463, Column 120: reference to entity "dn" for which no system identifier could be generated
    …ih:3NUBHFFFXKJ5CQTFFGU7XLE25P6FEQUW&dn=NCIS.S10E16.HDTV.x264-2HD&tr=udp://trac…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 463, Column 149: reference to entity "tr" for which no system identifier could be generated
    …6FEQUW&dn=NCIS.S10E16.HDTV.x264-2HD&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 463, Column 188: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 463, Column 221: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 463, Column 1150: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=NCIS%20S10E16%20HDTV%20x264-2HD&subid=e…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 463, Column 1188: reference to entity "subid" for which no system identifier could be generated
    …=NCIS%20S10E16%20HDTV%20x264-2HD&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 465, Column 222: NET-enabling start-tag requires SHORTTAG YES
    …idth="16" height="16" alt="Discuss" title="Discuss about this show" /></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.

  • Warning Line 468, Column 470: NET-enabling start-tag requires SHORTTAG YES
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></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 468, Column 470: required attribute "ALT" not specified
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></a></td>

    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 472, Column 120: reference to entity "dn" for which no system identifier could be generated
    …ih:LB5RBITBKOX4D7DP2BXKFYAXCQSSKR5Q&dn=Go.On.S01E17.HDTV.x264-LOL&tr=udp://tra…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 472, Column 150: reference to entity "tr" for which no system identifier could be generated
    …SKR5Q&dn=Go.On.S01E17.HDTV.x264-LOL&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 472, Column 189: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 472, Column 222: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 472, Column 1154: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=Go%20On%20S01E17%20HDTV%20x264-LOL&subi…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 472, Column 1195: reference to entity "subid" for which no system identifier could be generated
    …%20On%20S01E17%20HDTV%20x264-LOL&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 474, Column 222: NET-enabling start-tag requires SHORTTAG YES
    …idth="16" height="16" alt="Discuss" title="Discuss about this show" /></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.

  • Warning Line 477, Column 505: NET-enabling start-tag requires SHORTTAG YES
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></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 477, Column 505: required attribute "ALT" not specified
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></a></td>

    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 481, Column 120: reference to entity "dn" for which no system identifier could be generated
    …ih:A5MGJHJA67TC7VJPB4G7SF52RRN5UHT7&dn=Raising.Hope.S03E20.HDTV.x264-LOL&tr=ud…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 481, Column 157: reference to entity "tr" for which no system identifier could be generated
    …n=Raising.Hope.S03E20.HDTV.x264-LOL&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 481, Column 196: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 481, Column 229: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 481, Column 1182: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=Raising%20Hope%20S03E20%20HDTV%20x264-L…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 481, Column 1230: reference to entity "subid" for which no system identifier could be generated
    …0Hope%20S03E20%20HDTV%20x264-LOL&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 483, Column 222: NET-enabling start-tag requires SHORTTAG YES
    …idth="16" height="16" alt="Discuss" title="Discuss about this show" /></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.

  • Warning Line 486, Column 540: NET-enabling start-tag requires SHORTTAG YES
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></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 486, Column 540: required attribute "ALT" not specified
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></a></td>

    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 490, Column 120: reference to entity "dn" for which no system identifier could be generated
    …ih:4DKKUPG4MJ5AW2ZCERGKGDWLDJINKKG5&dn=Pretty.Little.Liars.S03E21.HDTV.x264-LO…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 490, Column 164: reference to entity "tr" for which no system identifier could be generated
    …y.Little.Liars.S03E21.HDTV.x264-LOL&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 490, Column 203: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 490, Column 236: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 490, Column 1210: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=Pretty%20Little%20Liars%20S03E21%20HDTV…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 490, Column 1267: reference to entity "subid" for which no system identifier could be generated
    …Liars%20S03E21%20HDTV%20x264-LOL&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 492, Column 222: NET-enabling start-tag requires SHORTTAG YES
    …idth="16" height="16" alt="Discuss" title="Discuss about this show" /></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.

  • Warning Line 495, Column 510: NET-enabling start-tag requires SHORTTAG YES
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></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 495, Column 510: required attribute "ALT" not specified
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></a></td>

    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 499, Column 120: reference to entity "dn" for which no system identifier could be generated
    …ih:NW3QEJ5QN3HFISK2UBRYKUOKD6NJITBE&dn=Hart.of.Dixie.S02E16.HDTV.x264-LOL&tr=u…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 499, Column 158: reference to entity "tr" for which no system identifier could be generated
    …=Hart.of.Dixie.S02E16.HDTV.x264-LOL&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 499, Column 197: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 499, Column 230: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 499, Column 1186: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=Hart%20of%20Dixie%20S02E16%20HDTV%20x26…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 499, Column 1237: reference to entity "subid" for which no system identifier could be generated
    …Dixie%20S02E16%20HDTV%20x264-LOL&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 501, Column 222: NET-enabling start-tag requires SHORTTAG YES
    …idth="16" height="16" alt="Discuss" title="Discuss about this show" /></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.

  • Warning Line 504, Column 515: NET-enabling start-tag requires SHORTTAG YES
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></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 504, Column 515: required attribute "ALT" not specified
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></a></td>

    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 508, Column 120: reference to entity "dn" for which no system identifier could be generated
    …ih:TQJTS5GNRD5Q25ZWVRRRTKBCPYH4B6L3&dn=The.Blue.Rose.S01E04.HDTV.x264-FiHTV&tr…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 508, Column 160: reference to entity "tr" for which no system identifier could be generated
    …he.Blue.Rose.S01E04.HDTV.x264-FiHTV&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 508, Column 199: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 508, Column 232: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 508, Column 1194: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=The%20Blue%20Rose%20S01E04%20HDTV%20x26…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 508, Column 1247: reference to entity "subid" for which no system identifier could be generated
    …ose%20S01E04%20HDTV%20x264-FiHTV&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 510, Column 222: NET-enabling start-tag requires SHORTTAG YES
    …idth="16" height="16" alt="Discuss" title="Discuss about this show" /></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.

  • Warning Line 513, Column 505: NET-enabling start-tag requires SHORTTAG YES
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></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 513, Column 505: required attribute "ALT" not specified
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></a></td>

    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 517, Column 120: reference to entity "dn" for which no system identifier could be generated
    …ih:WL2ZWLISUEAENWC42JDUTCWOBJYSLLMG&dn=Raising.Hope.S03E19.HDTV.x264-LOL&tr=ud…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 517, Column 157: reference to entity "tr" for which no system identifier could be generated
    …n=Raising.Hope.S03E19.HDTV.x264-LOL&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 517, Column 196: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 517, Column 229: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 517, Column 1182: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=Raising%20Hope%20S03E19%20HDTV%20x264-L…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 517, Column 1230: reference to entity "subid" for which no system identifier could be generated
    …0Hope%20S03E19%20HDTV%20x264-LOL&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 519, Column 247: NET-enabling start-tag requires SHORTTAG YES
    …0" width="16" height="16" alt="3 comments" title="3 forum comments" /></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 526, Column 128: reference to entity "dn" for which no system identifier could be generated
    …7B654105850DC121321E9A8BF01021570D9&dn=BBC.Wonders.of.Life.5of5.Home.PDTV.x264…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 526, Column 186: reference to entity "tr" for which no system identifier could be generated
    ….5of5.Home.PDTV.x264.AACmp4-MVGroup&tr=http://www.mvgroup.org:2710/announce&tr…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 526, Column 226: reference to entity "tr" for which no system identifier could be generated
    …ttp://www.mvgroup.org:2710/announce&tr=udp://tracker.ccc.de:80/announce&tr=udp…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 526, Column 262: reference to entity "tr" for which no system identifier could be generated
    …tr=udp://tracker.ccc.de:80/announce&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 526, Column 301: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 526, Column 334: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 526, Column 1024: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=BBC%20Wonders%20of%20Life%205of5%20Home…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 526, Column 1101: reference to entity "subid" for which no system identifier could be generated
    …e%20PDTV%20x264%20AACmp4-MVGroup&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 528, Column 260: NET-enabling start-tag requires SHORTTAG YES
    …0" width="16" height="16" alt="2 comments" title="2 forum comments" /></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 535, Column 128: reference to entity "dn" for which no system identifier could be generated
    …3EBC00A9EEB330BBA2D8D1F4947505FE41F&dn=All.Aboard.05of12.Turkey.Vangolu.Ekspre…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 535, Column 201: reference to entity "tr" for which no system identifier could be generated
    …kspressi.x264.720p.AC3.HDTV-MVGroup&tr=http://www.mvgroup.org:2710/announce&tr…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 535, Column 241: reference to entity "tr" for which no system identifier could be generated
    …ttp://www.mvgroup.org:2710/announce&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 535, Column 280: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 535, Column 313: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 535, Column 986: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=All%20Aboard%2005of12%20Turkey%20Vangol…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 535, Column 1080: reference to entity "subid" for which no system identifier could be generated
    …x264%20720p%20AC3%20HDTV-MVGroup&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 537, Column 275: NET-enabling start-tag requires SHORTTAG YES
    …0" width="16" height="16" alt="2 comments" title="2 forum comments" /></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 544, Column 128: reference to entity "dn" for which no system identifier could be generated
    …29295FA34A5378044F8FF58E6C81BEAF398&dn=All.Aboard.04of12.Argentina.El.Gran.Cap…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 544, Column 202: reference to entity "tr" for which no system identifier could be generated
    ….Capitan.x264.720p.AC3.HDTV-MVGroup&tr=http://www.mvgroup.org:2710/announce&tr…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 544, Column 242: reference to entity "tr" for which no system identifier could be generated
    …ttp://www.mvgroup.org:2710/announce&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 544, Column 281: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 544, Column 314: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 544, Column 989: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=All%20Aboard%2004of12%20Argentina%20El%…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 544, Column 1086: reference to entity "subid" for which no system identifier could be generated
    …x264%20720p%20AC3%20HDTV-MVGroup&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 546, Column 276: NET-enabling start-tag requires SHORTTAG YES
    …0" width="16" height="16" alt="2 comments" title="2 forum comments" /></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.

  • Warning Line 549, Column 500: NET-enabling start-tag requires SHORTTAG YES
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></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 549, Column 500: required attribute "ALT" not specified
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></a></td>

    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 553, Column 120: reference to entity "dn" for which no system identifier could be generated
    …ih:LWWKVZU35E2LFT7ZXEYXCJHE5O6E3PSF&dn=Conan.2013.02.25.Zooey.Deschanel.HDTV.x…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 553, Column 175: reference to entity "tr" for which no system identifier could be generated
    ….Zooey.Deschanel.HDTV.x264-BAJSKORV&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 553, Column 214: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 553, Column 247: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 553, Column 1254: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=Conan%202013%2002%2025%20Zooey%20Descha…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 553, Column 1326: reference to entity "subid" for which no system identifier could be generated
    …Deschanel%20HDTV%20x264-BAJSKORV&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 555, Column 265: NET-enabling start-tag requires SHORTTAG YES
    …0" width="16" height="16" alt="2 comments" title="2 forum comments" /></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 562, Column 128: reference to entity "dn" for which no system identifier could be generated
    …DAC81BA010A68C4BD77CBB505840D9CA1BE&dn=BBC.Wonders.of.Life.4of5.Size.Matters.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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 562, Column 194: reference to entity "tr" for which no system identifier could be generated
    …ze.Matters.PDTV.x264.AACmp4-MVGroup&tr=http://www.mvgroup.org:2710/announce&tr…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 562, Column 234: reference to entity "tr" for which no system identifier could be generated
    …ttp://www.mvgroup.org:2710/announce&tr=udp://tracker.ccc.de:80/announce&tr=udp…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 562, Column 270: reference to entity "tr" for which no system identifier could be generated
    …tr=udp://tracker.ccc.de:80/announce&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 562, Column 309: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 562, Column 342: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 562, Column 1048: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=BBC%20Wonders%20of%20Life%204of5%20Size…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 562, Column 1135: reference to entity "subid" for which no system identifier could be generated
    …s%20PDTV%20x264%20AACmp4-MVGroup&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 564, Column 268: NET-enabling start-tag requires SHORTTAG YES
    …0" width="16" height="16" alt="2 comments" title="2 forum comments" /></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 571, Column 128: reference to entity "dn" for which no system identifier could be generated
    …D7225564B863C9696F372B77A050E0F0E57&dn=Ch4.A.Great.British.Air.Disaster.PDTV.x…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 571, Column 189: reference to entity "tr" for which no system identifier could be generated
    …r.Disaster.PDTV.x264.AACmp4-MVGroup&tr=http://www.mvgroup.org:2710/announce&tr…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 571, Column 229: reference to entity "tr" for which no system identifier could be generated
    …ttp://www.mvgroup.org:2710/announce&tr=udp://tracker.ccc.de:80/announce&tr=udp…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 571, Column 265: reference to entity "tr" for which no system identifier could be generated
    …tr=udp://tracker.ccc.de:80/announce&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 571, Column 304: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 571, Column 337: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 571, Column 1033: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=Ch4%20A%20Great%20British%20Air%20Disas…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 571, Column 1113: reference to entity "subid" for which no system identifier could be generated
    …r%20PDTV%20x264%20AACmp4-MVGroup&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 573, Column 263: NET-enabling start-tag requires SHORTTAG YES
    …0" width="16" height="16" alt="2 comments" title="2 forum comments" /></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 580, Column 128: reference to entity "dn" for which no system identifier could be generated
    …C426F3D37AC98A51E7FFCB4E559EB208473&dn=Ch4.Lost.Worlds.The.Story.of.Archaeolog…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 580, Column 222: reference to entity "tr" for which no system identifier could be generated
    …rvice.of.the.State.XviD.AC3-MVGroup&tr=http://www.mvgroup.org:2710/announce&tr…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 580, Column 262: reference to entity "tr" for which no system identifier could be generated
    …ttp://www.mvgroup.org:2710/announce&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 580, Column 301: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 580, Column 334: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 580, Column 1049: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=Ch4%20Lost%20Worlds%20The%20Story%20of%…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 580, Column 1176: reference to entity "subid" for which no system identifier could be generated
    …the%20State%20XviD%20AC3-MVGroup&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 582, Column 296: NET-enabling start-tag requires SHORTTAG YES
    …0" width="16" height="16" alt="2 comments" title="2 forum comments" /></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.

  • Warning Line 585, Column 559: NET-enabling start-tag requires SHORTTAG YES
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></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 585, Column 559: required attribute "ALT" not specified
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></a></td>

    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 589, Column 120: reference to entity "dn" for which no system identifier could be generated
    …ih:CMR73OVBNXDY2JXFLNE3XBNQR4EOPVJZ&dn=Craig.Ferguson.2013.02.25.Keith.Olberma…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 589, Column 179: reference to entity "tr" for which no system identifier could be generated
    …02.25.Keith.Olbermann.HDTV.x264-FQM&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 589, Column 218: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 589, Column 251: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 589, Column 1270: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=Craig%20Ferguson%202013%2002%2025%20Kei…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 589, Column 1348: reference to entity "subid" for which no system identifier could be generated
    …th%20Olbermann%20HDTV%20x264-FQM&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 591, Column 222: NET-enabling start-tag requires SHORTTAG YES
    …idth="16" height="16" alt="Discuss" title="Discuss about this show" /></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 598, Column 128: reference to entity "dn" for which no system identifier could be generated
    …99633E953F2F849AAA2CBAD60687013AC53&dn=PBS.After.Newtown.The.Path.to.Violence.…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 598, Column 195: reference to entity "tr" for which no system identifier could be generated
    …o.Violence.540p.x264.AACmp4-MVGroup&tr=http://www.mvgroup.org:2710/announce&tr…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 598, Column 235: reference to entity "tr" for which no system identifier could be generated
    …ttp://www.mvgroup.org:2710/announce&tr=http://exodus.desync.com/announce&tr=ud…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 598, Column 272: reference to entity "tr" for which no system identifier could be generated
    …r=http://exodus.desync.com/announce&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 598, Column 311: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 598, Column 344: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 598, Column 1051: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=PBS%20After%20Newtown%20The%20Path%20to…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 598, Column 1139: reference to entity "subid" for which no system identifier could be generated
    …e%20540p%20x264%20AACmp4-MVGroup&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 600, Column 269: NET-enabling start-tag requires SHORTTAG YES
    …0" width="16" height="16" alt="2 comments" title="2 forum comments" /></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 607, Column 128: reference to entity "dn" for which no system identifier could be generated
    …13A7C82FE23DD134D6644F7C64FC2814B82&dn=BBC.Wonders.of.Life.3of5.Endless.Forms.…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 607, Column 210: reference to entity "tr" for which no system identifier could be generated
    ….Beautiful.PDTV.x264.AACmp4-MVGroup&tr=http://www.mvgroup.org:2710/announce&tr…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 607, Column 250: reference to entity "tr" for which no system identifier could be generated
    …ttp://www.mvgroup.org:2710/announce&tr=udp://tracker.ccc.de:80/announce&tr=udp…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 607, Column 286: reference to entity "tr" for which no system identifier could be generated
    …tr=udp://tracker.ccc.de:80/announce&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 607, Column 325: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 607, Column 358: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 607, Column 1096: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=BBC%20Wonders%20of%20Life%203of5%20Endl…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 607, Column 1203: reference to entity "subid" for which no system identifier could be generated
    …l%20PDTV%20x264%20AACmp4-MVGroup&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 609, Column 284: NET-enabling start-tag requires SHORTTAG YES
    …0" width="16" height="16" alt="2 comments" title="2 forum comments" /></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 616, Column 128: reference to entity "dn" for which no system identifier could be generated
    …5CFA9EEE12E71C054ED3B9991122266777F&dn=PBS.American.Experience.2013.The.Abolit…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 616, Column 208: reference to entity "tr" for which no system identifier could be generated
    …nists.2of3.540p.x264.AACmp4-MVGroup&tr=http://www.mvgroup.org:2710/announce&tr…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 616, Column 248: reference to entity "tr" for which no system identifier could be generated
    …ttp://www.mvgroup.org:2710/announce&tr=http://exodus.desync.com/announce&tr=ud…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 616, Column 285: reference to entity "tr" for which no system identifier could be generated
    …r=http://exodus.desync.com/announce&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 616, Column 324: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 616, Column 357: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 616, Column 1090: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=PBS%20American%20Experience%202013%20Th…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 616, Column 1191: reference to entity "subid" for which no system identifier could be generated
    …3%20540p%20x264%20AACmp4-MVGroup&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 618, Column 282: NET-enabling start-tag requires SHORTTAG YES
    …0" width="16" height="16" alt="2 comments" title="2 forum comments" /></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.

  • Warning Line 621, Column 554: NET-enabling start-tag requires SHORTTAG YES
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></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 621, Column 554: required attribute "ALT" not specified
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></a></td>

    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 625, Column 120: reference to entity "dn" for which no system identifier could be generated
    …ih:T52BEGU24OTVUW3BFIKOLBOGQONYOQWG&dn=The.Colbert.Report.2013.02.25.Simon.Gar…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 625, Column 183: reference to entity "tr" for which no system identifier could be generated
    …02.25.Simon.Garfield.HDTV.x264-LMAO&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 625, Column 222: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 625, Column 255: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 625, Column 1286: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=The%20Colbert%20Report%202013%2002%2025…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 625, Column 1370: reference to entity "subid" for which no system identifier could be generated
    …on%20Garfield%20HDTV%20x264-LMAO&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 627, Column 222: NET-enabling start-tag requires SHORTTAG YES
    …idth="16" height="16" alt="Discuss" title="Discuss about this show" /></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.

  • Warning Line 630, Column 536: NET-enabling start-tag requires SHORTTAG YES
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></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 630, Column 536: required attribute "ALT" not specified
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></a></td>

    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 634, Column 120: reference to entity "dn" for which no system identifier could be generated
    …ih:L2VRAFVNQSRCQXYLHKJS5CG4HHCEKWZX&dn=The.Daily.Show.2013.02.25.Donnie.Wahlbe…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 634, Column 180: reference to entity "tr" for which no system identifier could be generated
    …2.25.Donnie.Wahlberg.HDTV.x264-LMAO&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 634, Column 219: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 634, Column 252: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 634, Column 1274: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=The%20Daily%20Show%202013%2002%2025%20D…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 634, Column 1355: reference to entity "subid" for which no system identifier could be generated
    …ie%20Wahlberg%20HDTV%20x264-LMAO&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 636, Column 222: NET-enabling start-tag requires SHORTTAG YES
    …idth="16" height="16" alt="Discuss" title="Discuss about this show" /></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.

  • Warning Line 639, Column 532: NET-enabling start-tag requires SHORTTAG YES
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></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 639, Column 532: required attribute "ALT" not specified
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></a></td>

    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 643, Column 120: reference to entity "dn" for which no system identifier could be generated
    …ih:FSYXG2FSITEO65DHAUF6TBEBUP7RPKOH&dn=The.Following.S01E06.720p.HDTV.X264-DIM…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 643, Column 169: reference to entity "tr" for which no system identifier could be generated
    …ing.S01E06.720p.HDTV.X264-DIMENSION&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 643, Column 208: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 643, Column 241: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 643, Column 1230: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=The%20Following%20S01E06%20720p%20HDTV%…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 643, Column 1292: reference to entity "subid" for which no system identifier could be generated
    …6%20720p%20HDTV%20X264-DIMENSION&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 645, Column 222: NET-enabling start-tag requires SHORTTAG YES
    …idth="16" height="16" alt="Discuss" title="Discuss about this show" /></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.

  • Warning Line 653, Column 491: NET-enabling start-tag requires SHORTTAG YES
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></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 653, Column 491: required attribute "ALT" not specified
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></a></td>

    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 657, Column 120: reference to entity "dn" for which no system identifier could be generated
    …ih:PE5356R3XPZKUMM3WIVGTHEJC6UBZ27P&dn=Bones.S08E17.720p.HDTV.X264-DIMENSION&t…

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

  • Info Line 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 657, Column 161: reference to entity "tr" for which no system identifier could be generated
    …nes.S08E17.720p.HDTV.X264-DIMENSION&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 657, Column 200: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 657, Column 233: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 657, Column 1198: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=Bones%20S08E17%20720p%20HDTV%20X264-DIM…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 657, Column 1250: reference to entity "subid" for which no system identifier could be generated
    …7%20720p%20HDTV%20X264-DIMENSION&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 659, Column 222: NET-enabling start-tag requires SHORTTAG YES
    …idth="16" height="16" alt="Discuss" title="Discuss about this show" /></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.

  • Warning Line 662, Column 519: NET-enabling start-tag requires SHORTTAG YES
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></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 662, Column 519: required attribute "ALT" not specified
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></a></td>

    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 666, Column 120: reference to entity "dn" for which no system identifier could be generated
    …ih:MHBVL6B64OGBG2NZKLK2SL4GDV4Y2MVJ&dn=Monday.Mornings.S01E04.HDTV.x264-LOL&tr…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 666, Column 160: reference to entity "tr" for which no system identifier could be generated
    …onday.Mornings.S01E04.HDTV.x264-LOL&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 666, Column 199: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 666, Column 232: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 666, Column 1194: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=Monday%20Mornings%20S01E04%20HDTV%20x26…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 666, Column 1245: reference to entity "subid" for which no system identifier could be generated
    …nings%20S01E04%20HDTV%20x264-LOL&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 668, Column 250: NET-enabling start-tag requires SHORTTAG YES
    …0" width="16" height="16" alt="2 comments" title="2 forum comments" /></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.

  • Warning Line 671, Column 587: NET-enabling start-tag requires SHORTTAG YES
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></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 671, Column 587: required attribute "ALT" not specified
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></a></td>

    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 675, Column 120: reference to entity "dn" for which no system identifier could be generated
    …ih:VPNULFFUFL6SPRQLT42T5G36OIHYKHJC&dn=Totally.Biased.with.W.Kamau.Bell.S02E06…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 675, Column 177: reference to entity "tr" for which no system identifier could be generated
    …h.W.Kamau.Bell.S02E06.HDTV.x264-2HD&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 675, Column 216: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 675, Column 249: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 675, Column 1262: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=Totally%20Biased%20with%20W%20Kamau%20B…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 675, Column 1338: reference to entity "subid" for which no system identifier could be generated
    …0Bell%20S02E06%20HDTV%20x264-2HD&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 677, Column 222: NET-enabling start-tag requires SHORTTAG YES
    …idth="16" height="16" alt="Discuss" title="Discuss about this show" /></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.

  • Warning Line 680, Column 523: NET-enabling start-tag requires SHORTTAG YES
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></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 680, Column 523: required attribute "ALT" not specified
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></a></td>

    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 684, Column 120: reference to entity "dn" for which no system identifier could be generated
    …ih:ORK3JTGZA6PTT6LB7VIVYW3AEMVEBTUJ&dn=Being.Human.US.S03E07.HDTV.x264-EVOLVE&…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 684, Column 162: reference to entity "tr" for which no system identifier could be generated
    …ng.Human.US.S03E07.HDTV.x264-EVOLVE&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 684, Column 201: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 684, Column 234: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 684, Column 1202: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=Being%20Human%20US%20S03E07%20HDTV%20x2…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 684, Column 1257: reference to entity "subid" for which no system identifier could be generated
    …US%20S03E07%20HDTV%20x264-EVOLVE&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 686, Column 252: NET-enabling start-tag requires SHORTTAG YES
    …0" width="16" height="16" alt="2 comments" title="2 forum comments" /></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.

  • Warning Line 689, Column 491: NET-enabling start-tag requires SHORTTAG YES
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></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 689, Column 491: required attribute "ALT" not specified
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></a></td>

    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 693, Column 120: reference to entity "dn" for which no system identifier could be generated
    …ih:U6P6PUKZ7C3TVQTG2P6Z2JREWQI66RGW&dn=Bunheads.S01E18.HDTV.x264-2HD&tr=udp://…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 693, Column 153: reference to entity "tr" for which no system identifier could be generated
    …GW&dn=Bunheads.S01E18.HDTV.x264-2HD&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 693, Column 192: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 693, Column 225: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 693, Column 1166: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=Bunheads%20S01E18%20HDTV%20x264-2HD&sub…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 693, Column 1208: reference to entity "subid" for which no system identifier could be generated
    …heads%20S01E18%20HDTV%20x264-2HD&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 695, Column 222: NET-enabling start-tag requires SHORTTAG YES
    …idth="16" height="16" alt="Discuss" title="Discuss about this show" /></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.

  • Warning Line 698, Column 470: NET-enabling start-tag requires SHORTTAG YES
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></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 698, Column 470: required attribute "ALT" not specified
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></a></td>

    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 702, Column 120: reference to entity "dn" for which no system identifier could be generated
    …ih:QUXQRYIQ7I6N35M42GWBTLFSOBI3VU2Q&dn=90210.S05E15.HDTV.x264-ASAP&tr=udp://tr…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 702, Column 151: reference to entity "tr" for which no system identifier could be generated
    …VU2Q&dn=90210.S05E15.HDTV.x264-ASAP&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 702, Column 190: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 702, Column 223: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 702, Column 1158: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=90210%20S05E15%20HDTV%20x264-ASAP&subid…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 702, Column 1198: reference to entity "subid" for which no system identifier could be generated
    …0210%20S05E15%20HDTV%20x264-ASAP&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 704, Column 222: NET-enabling start-tag requires SHORTTAG YES
    …idth="16" height="16" alt="Discuss" title="Discuss about this show" /></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.

  • Warning Line 707, Column 502: NET-enabling start-tag requires SHORTTAG YES
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></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 707, Column 502: required attribute "ALT" not specified
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></a></td>

    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 711, Column 120: reference to entity "dn" for which no system identifier could be generated
    …ih:ABWGH3H5Y3DEKSLNSJ6K6DWISVQYSJ45&dn=Dallas.2012.S02E06.HDTV.x264-LOL&tr=udp…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 711, Column 156: reference to entity "tr" for which no system identifier could be generated
    …dn=Dallas.2012.S02E06.HDTV.x264-LOL&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 711, Column 195: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 711, Column 228: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 711, Column 1178: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=Dallas%202012%20S02E06%20HDTV%20x264-LO…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 711, Column 1225: reference to entity "subid" for which no system identifier could be generated
    …02012%20S02E06%20HDTV%20x264-LOL&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 713, Column 246: NET-enabling start-tag requires SHORTTAG YES
    …0" width="16" height="16" alt="2 comments" title="2 forum comments" /></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.

  • Warning Line 716, Column 495: NET-enabling start-tag requires SHORTTAG YES
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></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 716, Column 495: required attribute "ALT" not specified
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></a></td>

    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 720, Column 120: reference to entity "dn" for which no system identifier could be generated
    …ih:7NA226AWHYLVEI6KFADXWIULV25IEZD5&dn=Deception.S01E08.HDTV.x264-LOL&tr=udp:/…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 720, Column 154: reference to entity "tr" for which no system identifier could be generated
    …5&dn=Deception.S01E08.HDTV.x264-LOL&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 720, Column 193: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 720, Column 226: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 720, Column 1170: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=Deception%20S01E08%20HDTV%20x264-LOL&su…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 720, Column 1213: reference to entity "subid" for which no system identifier could be generated
    …ption%20S01E08%20HDTV%20x264-LOL&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 722, Column 222: NET-enabling start-tag requires SHORTTAG YES
    …idth="16" height="16" alt="Discuss" title="Discuss about this show" /></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.

  • Warning Line 725, Column 515: NET-enabling start-tag requires SHORTTAG YES
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></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 725, Column 515: required attribute "ALT" not specified
    …http://ezimg.it/s/2/1/tvrage.png" width="16" height="16" border="0" /></a></td>

    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 729, Column 120: reference to entity "dn" for which no system identifier could be generated
    …ih:FBOABBJQO77UMVLBTBPCUX75DSRVI7CV&dn=Mike.and.Molly.S03E16.HDTV.x264-LOL&tr=…

    This is usually a cascading error caused by 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 278, Column 125: entity was defined here
    …BAC7430D3D2B86EC8EDAAEDBF41DC8C8FFB7CB&dn=Attenboroughs.Natural.Curiosities.1o…
  • Error Line 729, Column 159: reference to entity "tr" for which no system identifier could be generated
    …Mike.and.Molly.S03E16.HDTV.x264-LOL&tr=udp://tracker.openbittorrent.com:80&tr=…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 729, Column 198: reference to entity "tr" for which no system identifier could be generated
    …udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 729, Column 231: reference to entity "tr" for which no system identifier could be generated
    …80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80" class="magn…

    This is usually a cascading error caused by 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 229, Column 752: entity was defined here
    …816060EA56D56F2A2148CD45705511079F9BCA&tr=udp://tracker.openbittorrent.com:80/…
  • Error Line 729, Column 1190: reference to entity "name" for which no system identifier could be generated
    …dp%3A%2F%2Ftracker.istole.it%3A80&name=Mike%20and%20Molly%20S03E16%20HDTV%20x2…

    This is usually a cascading error caused by 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 229, Column 586: entity was defined here
    …F%2Ftracker.openbittorrent.com%3A80%2F&name=TPB+AFK+2013+720p+h264-SimonKlose&…
  • Error Line 729, Column 1242: reference to entity "subid" for which no system identifier could be generated
    …Molly%20S03E16%20HDTV%20x264-LOL&subid=eztv" target="_blank" class="ddl" title…

    This is usually a cascading error caused by 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 229, Column 625: entity was defined here
    …name=TPB+AFK+2013+720p+h264-SimonKlose&subid=eztv" class="ddl" title="Direct D…
  • Warning Line 731, Column 222: NET-enabling start-tag requires SHORTTAG YES
    …idth="16" height="16" alt="Discuss" title="Discuss about this show" /></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 734, Column 49: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
        <table width="950" border="0" align="center">

    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 743, Column 8: end tag for "CAPTION" omitted, but its declaration does not permit this
    </table>		<div id="gap"></div>
    • 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 149, Column 1: start tag was here
    <BR />
  • Error Line 743, Column 8: end tag for "TABLE" which is not finished
    </table>		<div id="gap"></div>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 743, Column 20: ID "GAP" already defined
    </table>		<div id="gap"></div>

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

  • Info Line 46, Column 13: ID "GAP" first defined here
    			<div id="gap"></div>
  • Error Line 744, Column 12: ID "DIVIDER" already defined
    		<div id="divider"></div>

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

  • Info Line 47, Column 13: ID "DIVIDER" first defined here
    			<div id="divider"></div>
  • Error Line 745, Column 12: ID "GAP" already defined
    		<div id="gap"></div>

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

  • Info Line 46, Column 13: ID "GAP" first defined here
    			<div id="gap"></div>
  • Warning Line 747, Column 137: NET-enabling start-tag requires SHORTTAG YES
    …src="http://ezimg.it/s/1/2/kopimi.png" width="80" height="15" border="0" /></a>

    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 747, Column 137: required attribute "ALT" not specified
    …src="http://ezimg.it/s/1/2/kopimi.png" width="80" height="15" 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>.

  • Warning Line 748, Column 134: NET-enabling start-tag requires SHORTTAG YES
    …c="http://ezimg.it/s/1/2/lighttpd.png" width="80" height="15" border="0" /></a>

    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 748, Column 134: required attribute "ALT" not specified
    …c="http://ezimg.it/s/1/2/lighttpd.png" width="80" height="15" 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>.

  • Warning Line 749, Column 124: NET-enabling start-tag requires SHORTTAG YES
    …mg src="http://ezimg.it/s/1/2/php.png" width="80" height="15" border="0" /></a>

    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 749, Column 124: required attribute "ALT" not specified
    …mg src="http://ezimg.it/s/1/2/php.png" width="80" height="15" 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>.

  • Warning Line 750, Column 130: NET-enabling start-tag requires SHORTTAG YES
    …c="http://ezimg.it/s/1/2/bitsnoop.png" width="80" height="15" border="0" /></a>

    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 750, Column 130: required attribute "ALT" not specified
    …c="http://ezimg.it/s/1/2/bitsnoop.png" width="80" height="15" 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>.

  • Warning Line 751, Column 128: NET-enabling start-tag requires SHORTTAG YES
    …rc="http://ezimg.it/s/1/2/mvgroup.png" width="80" height="15" border="0" /></a>

    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 751, Column 128: required attribute "ALT" not specified
    …rc="http://ezimg.it/s/1/2/mvgroup.png" width="80" height="15" 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>.

  • Warning Line 752, Column 131: NET-enabling start-tag requires SHORTTAG YES
    …src="http://ezimg.it/s/1/2/btchat.png" width="80" height="15" border="0" /></a>

    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 752, Column 131: required attribute "ALT" not specified
    …src="http://ezimg.it/s/1/2/btchat.png" width="80" height="15" 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>.

  • Warning Line 753, Column 133: NET-enabling start-tag requires SHORTTAG YES
    …c="http://ezimg.it/s/1/2/mininova.png" width="80" height="15" border="0" /></a>

    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 753, Column 133: required attribute "ALT" not specified
    …c="http://ezimg.it/s/1/2/mininova.png" width="80" height="15" 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>.

  • Warning Line 754, Column 133: NET-enabling start-tag requires SHORTTAG YES
    …rc="http://ezimg.it/s/1/2/zoinkit.png" width="80" height="15" border="0" /></a>

    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 754, Column 133: required attribute "ALT" not specified
    …rc="http://ezimg.it/s/1/2/zoinkit.png" width="80" height="15" 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>.

  • Warning Line 755, Column 137: NET-enabling start-tag requires SHORTTAG YES
    …http://ezimg.it/s/1/2/torrentsnet.png" width="80" height="15" border="0" /></a>

    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 755, Column 137: required attribute "ALT" not specified
    …http://ezimg.it/s/1/2/torrentsnet.png" width="80" height="15" 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>.

  • Warning Line 756, Column 122: NET-enabling start-tag requires SHORTTAG YES
    …rc="http://ezimg.it/s/1/2/ssl_off.png" width="80" height="15" border="0" /></a>

    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 756, Column 122: required attribute "ALT" not specified
    …rc="http://ezimg.it/s/1/2/ssl_off.png" width="80" height="15" 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>.

  • Warning Line 757, Column 171: NET-enabling start-tag requires SHORTTAG YES
    …g" width="80" height="15" alt="ipv6 ready" title="ipv6 ready" border="0" /></a>

    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.

  • Warning Line 758, Column 129: NET-enabling start-tag requires SHORTTAG YES
    …rc="http://ezimg.it/s/1/2/ezrssit.png" width="80" height="15" border="0" /></a>

    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 758, Column 129: required attribute "ALT" not specified
    …rc="http://ezimg.it/s/1/2/ezrssit.png" width="80" height="15" 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>.

Visitor Analysis

Daily Visitor
  • 157.500 visits