hotpornshow.com

hotpornshow.com has Alexa Rank 4.363 and Google Page Rank is 2

Display Widget for this domain on your website. Click Here
Processing update domain...

Overview Info

  • Domain Name
    hotpornshow.com
  • Favicon
  • Alexa Rank
    #4363
  • Google Page Rank
    PR 2
  • Ip Address
    46.229.169.36
  • Page Size
    43.7 KB
  • Images
    1 GIF, 40 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 0 0 0 0

Website Meta Analysis



  • Meta Keyword

Technical Analysis



  • Webserver
    Apache/2.2.23 (Unix) PHP/5.2.17
  • Ip Address
    46.229.169.36
  • Domain Age
    5 Years, 9 Months, 28 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Fri, 13 Sep 2013 14:43:36 GMT
  • server: Apache/2.2.23 (Unix) PHP/5.2.17
  • x-powered-by: PHP/5.2.17
  • 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
  • x-frame-options: DENY
  • connection: close
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: HOTPORNSHOW.COM

Registrant:
HPSWeb Inc
Mario Fernandez ( email )
#5 Calle Eusebio A. Morales
Panama City
Panamá,8477
PA
Tel. +507.264015

Creation Date: 17-Dec-2007
Expiration Date: 17-Dec-2013

Domain servers in listed order:
ns5.public-ns.com
ns6.public-ns.com


Administrative Contact:
HPSWeb Inc
Mario Fernandez ( email )
#5 Calle Eusebio A. Morales
Panama City
Panamá,8477
PA
Tel. +507.264015

Technical Contact:
HPSWeb Inc
Mario Fernandez ( email )
#5 Calle Eusebio A. Morales
Panama City
Panamá,8477
PA
Tel. +507.264015

Billing Contact:
HPSWeb Inc
Mario Fernandez ( email )
#5 Calle Eusebio A. Morales
Panama City
Panamá,8477
PA
Tel. +507.264015

Status:ACTIVE

DNS Analysis


DNS servers
ns5.public-ns.com [207.226.173.74]
ns6.public-ns.com [88.208.58.214]

DNS Records

Answer records
hotpornshow.com SOA
server: ns5.public-ns.com
email: admin@hotpornshow.com
serial: 1274198931
refresh: 21600
retry: 3600
expire: 691200
minimum ttl: 38400
1200s
hotpornshow.com NS  ns5.public-ns.com 1200s
hotpornshow.com NS  ns6.public-ns.com 1200s
hotpornshow.com MX
preference: 10
exchange: mail.hotpornshow.com
1200s
hotpornshow.com MX
preference: 20
exchange: mail2.hotpornshow.com
1200s
hotpornshow.com A 213.174.152.171 1200s

Authority records

Additional records
ns5.public-ns.com A 207.226.173.74 1200s
ns6.public-ns.com A 88.208.58.214 1200s
mail.hotpornshow.com A 206.161.193.141 1200s
mail2.hotpornshow.com A 205.252.166.180 1200s

IP 46.229.169.36 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 490 Errors
  • 230 Warnings
Ratio Text/Html
  • 0.7776262242296856
Message Error
  • Error Line 4, Column 6: element "HTML" undefined
    <HTML>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 5, Column 6: element "HEAD" undefined
    <HEAD>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 6, Column 8: element "TITLE" undefined
    	<TITLE>Free Porn Videos, XXX Sex, Porn Tube, Full Free Porn Movies</TITLE>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 7, Column 14: there is no attribute "NAME"
    		<META NAME="description" CONTENT="Hot Porn Show - Free Porn Videos updated da…

    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 7, Column 36: there is no attribute "CONTENT"
    		<META NAME="description" CONTENT="Hot Porn Show - Free Porn Videos updated da…

    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 7, Column 134: element "META" undefined
    …e Porn Videos updated daily - The best rated tons of downloadable porn movies">

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

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

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

  • Info Line 8, Column 2: start tag was here
    	<meta name="verify-v1" content="o60cwxoXjteQjbDUf2Mg/ZfMmdHNjknEjuU82agf2rc=" >
  • Error Line 9, Column 81: end tag for "meta" omitted, but OMITTAG NO was specified
    	<meta name="verify-v1" content="f/64VafGPuPFB3egr6OOxyWetfTyq/CDeph8DenEncY=" >

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

  • Info Line 9, Column 2: start tag was here
    	<meta name="verify-v1" content="f/64VafGPuPFB3egr6OOxyWetfTyq/CDeph8DenEncY=" >
  • Error Line 11, Column 84: end tag for "link" omitted, but OMITTAG NO was specified
    …nk rel="icon" type="image/png" href="http://s.hotpornshow.com/img/favicon.png">

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

  • Info Line 11, Column 2: start tag was here
    	<link rel="icon" type="image/png" href="http://s.hotpornshow.com/img/favicon.p…
  • Error Line 12, Column 92: end tag for "link" omitted, but OMITTAG NO was specified
    …"http://s.hotpornshow.com/css/hps_style4.css" rel="stylesheet" type="text/css">

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

  • Info Line 12, Column 2: start tag was here
    	<link href="http://s.hotpornshow.com/css/hps_style4.css" rel="stylesheet" type…
  • Error Line 20, Column 7: end tag for "META" omitted, but OMITTAG NO was specified
    </HEAD>

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

  • Info Line 7, Column 3: start tag was here
    		<META NAME="description" CONTENT="Hot Porn Show - Free Porn Videos updated da…
  • Error Line 22, Column 20: there is no attribute "MARGINHEIGHT"
    <BODY MARGINHEIGHT="0" MARGINWIDTH="0" TOPMARGIN="0" LEFTMARGIN="0">

    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 22, Column 36: there is no attribute "MARGINWIDTH"
    <BODY MARGINHEIGHT="0" MARGINWIDTH="0" TOPMARGIN="0" LEFTMARGIN="0">

    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 22, Column 50: there is no attribute "TOPMARGIN"
    <BODY MARGINHEIGHT="0" MARGINWIDTH="0" TOPMARGIN="0" LEFTMARGIN="0">

    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 22, Column 65: there is no attribute "LEFTMARGIN"
    <BODY MARGINHEIGHT="0" MARGINWIDTH="0" TOPMARGIN="0" LEFTMARGIN="0">

    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 22, Column 68: element "BODY" undefined
    <BODY MARGINHEIGHT="0" MARGINWIDTH="0" TOPMARGIN="0" LEFTMARGIN="0">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 26, Column 84: there is no attribute "SRC"
    …'http://www.hotpornshow.com'><IMG SRC="http://s.hotpornshow.com/img/hps_logo.g…

    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 26, Column 134: there is no attribute "WIDTH"
    …tpornshow.com/img/hps_logo.gif" WIDTH="466" HEIGHT="96" BORDER="0" alt="Hot Po…

    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 26, Column 147: there is no attribute "HEIGHT"
    …/img/hps_logo.gif" WIDTH="466" HEIGHT="96" BORDER="0" alt="Hot Porn Show"></a>…

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

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

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

  • Error Line 26, Column 159: there is no attribute "BORDER"
    …hps_logo.gif" WIDTH="466" HEIGHT="96" BORDER="0" alt="Hot Porn Show"></a></div>

    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 26, Column 167: there is no attribute "alt"
    …hps_logo.gif" WIDTH="466" HEIGHT="96" BORDER="0" alt="Hot Porn Show"></a></div>

    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 26, Column 182: element "IMG" undefined
    …hps_logo.gif" WIDTH="466" HEIGHT="96" BORDER="0" alt="Hot Porn Show"></a></div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 26, Column 186: end tag for "IMG" omitted, but OMITTAG NO was specified
    …hps_logo.gif" WIDTH="466" HEIGHT="96" BORDER="0" alt="Hot Porn Show"></a></div>

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

  • Info Line 26, Column 75: start tag was here
    …><a href='http://www.hotpornshow.com'><IMG SRC="http://s.hotpornshow.com/img/h…
  • Error Line 27, Column 50: end tag for "br" omitted, but OMITTAG NO was specified
    …sign_login"><br style="font-size:5px"><a href="http://www.hotpornshow.com/">Ho…

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

  • Info Line 27, Column 24: start tag was here
    		<div id="sign_login"><br style="font-size:5px"><a href="http://www.hotpornsho…
  • Error Line 28, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><BR style="font-size:10px"><nobr><FORM NAME="search_form" ACTION="http://ww…

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

  • Info Line 28, Column 1: start tag was here
    <br><BR style="font-size:10px"><nobr><FORM NAME="search_form" ACTION="http://ww…
  • Error Line 28, Column 15: there is no attribute "style"
    <br><BR style="font-size:10px"><nobr><FORM NAME="search_form" ACTION="http://ww…

    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 28, Column 31: element "BR" undefined
    <br><BR style="font-size:10px"><nobr><FORM NAME="search_form" ACTION="http://ww…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 28, Column 37: element "nobr" undefined
    <br><BR style="font-size:10px"><nobr><FORM NAME="search_form" ACTION="http://ww…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 28, Column 49: there is no attribute "NAME"
    …yle="font-size:10px"><nobr><FORM NAME="search_form" ACTION="http://www.hotporn…

    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 28, Column 70: there is no attribute "ACTION"
    …<nobr><FORM NAME="search_form" ACTION="http://www.hotpornshow.com/search/" MET…

    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 28, Column 114: there is no attribute "METHOD"
    …ttp://www.hotpornshow.com/search/" METHOD="get"><script type="text/javascript">

    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 28, Column 119: element "FORM" undefined
    …ttp://www.hotpornshow.com/search/" METHOD="get"><script type="text/javascript">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 40, Column 37: there is no attribute "onChange"
    <select id='niches_header' onChange='niches_select_change();'>

    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 41, Column 20: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    <option  selected  value=''>Choose category</option>

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Error Line 84, Column 19: there is no attribute "size"
    &nbsp;<INPUT size=25 tabIndex=1 maxLength=64 name="q" value="">&nbsp;<input typ…

    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 84, Column 19: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    &nbsp;<INPUT size=25 tabIndex=1 maxLength=64 name="q" value="">&nbsp;<input typ…
  • Error Line 84, Column 31: there is no attribute "tabIndex"
    &nbsp;<INPUT size=25 tabIndex=1 maxLength=64 name="q" value="">&nbsp;<input typ…

    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 84, Column 31: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    &nbsp;<INPUT size=25 tabIndex=1 maxLength=64 name="q" value="">&nbsp;<input typ…
  • Error Line 84, Column 43: there is no attribute "maxLength"
    …p;<INPUT size=25 tabIndex=1 maxLength=64 name="q" value="">&nbsp;<input type="…

    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 84, Column 43: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …p;<INPUT size=25 tabIndex=1 maxLength=64 name="q" value="">&nbsp;<input type="…
  • Error Line 84, Column 51: there is no attribute "name"
    … size=25 tabIndex=1 maxLength=64 name="q" value="">&nbsp;<input type="submit" …

    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 84, Column 61: there is no attribute "value"
    …abIndex=1 maxLength=64 name="q" value="">&nbsp;<input type="submit" value="Sea…

    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 84, Column 63: element "INPUT" undefined
    …Index=1 maxLength=64 name="q" value="">&nbsp;<input type="submit" value="Searc…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 84, Column 112: end tag for "input" omitted, but OMITTAG NO was specified
    …ame="q" value="">&nbsp;<input type="submit" value="Search"></FORM></nobr></div>

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

  • Info Line 84, Column 70: start tag was here
    … maxLength=64 name="q" value="">&nbsp;<input type="submit" value="Search"></FO…
  • Error Line 84, Column 112: end tag for "INPUT" omitted, but OMITTAG NO was specified
    …ame="q" value="">&nbsp;<input type="submit" value="Search"></FORM></nobr></div>

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

  • Info Line 84, Column 7: start tag was here
    &nbsp;<INPUT size=25 tabIndex=1 maxLength=64 name="q" value="">&nbsp;<input typ…
  • Error Line 84, Column 125: end tag for "BR" omitted, but OMITTAG NO was specified
    …ame="q" value="">&nbsp;<input type="submit" value="Search"></FORM></nobr></div>

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

  • Info Line 28, Column 5: start tag was here
    <br><BR style="font-size:10px"><nobr><FORM NAME="search_form" ACTION="http://ww…
  • Error Line 85, Column 58: end tag for "br" omitted, but OMITTAG NO was specified
    		<div style="clear:both"><br style="font-size:5px"></div>

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

  • Info Line 85, Column 27: start tag was here
    		<div style="clear:both"><br style="font-size:5px"></div>
  • Error Line 96, Column 95: there is no attribute "target"
    …b_left" style="font-size:13px" target="_blank">Family Sex<br><img src="http://…

    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 96, Column 118: end tag for "br" omitted, but OMITTAG NO was specified
    …e:13px" target="_blank">Family Sex<br><img src="http://s.hotpornshow.com/thumb…

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

  • Info Line 96, Column 114: start tag was here
    …-size:13px" target="_blank">Family Sex<br><img src="http://s.hotpornshow.com/t…
  • Error Line 96, Column 200: there is no attribute "border"
    …//s.hotpornshow.com/thumbs/004.jpg" width="100" height="75" border="0"></a><BR>

    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 96, Column 203: required attribute "alt" not specified
    …//s.hotpornshow.com/thumbs/004.jpg" width="100" height="75" border="0"></a><BR>

    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 96, Column 207: end tag for "img" omitted, but OMITTAG NO was specified
    …//s.hotpornshow.com/thumbs/004.jpg" width="100" height="75" border="0"></a><BR>

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

  • Info Line 96, Column 118: start tag was here
    …e:13px" target="_blank">Family Sex<br><img src="http://s.hotpornshow.com/thumb…
  • Error Line 96, Column 211: element "BR" undefined
    …//s.hotpornshow.com/thumbs/004.jpg" width="100" height="75" border="0"></a><BR>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 97, Column 114: end tag for "br" omitted, but OMITTAG NO was specified
    …3px" target="_blank">Home Sex Tape<br><img src="http://s.hotpornshow.com/thumb…

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

  • Info Line 97, Column 110: start tag was here
    …ze:13px" target="_blank">Home Sex Tape<br><img src="http://s.hotpornshow.com/t…
  • Error Line 97, Column 199: required attribute "alt" not specified
    …//s.hotpornshow.com/thumbs/014.jpg" width="100" height="75" border="0"></a><BR>

    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 97, Column 203: end tag for "img" omitted, but OMITTAG NO was specified
    …//s.hotpornshow.com/thumbs/014.jpg" width="100" height="75" border="0"></a><BR>

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

  • Info Line 97, Column 114: start tag was here
    …3px" target="_blank">Home Sex Tape<br><img src="http://s.hotpornshow.com/thumb…
  • Error Line 97, Column 207: element "BR" undefined
    …//s.hotpornshow.com/thumbs/014.jpg" width="100" height="75" border="0"></a><BR>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 98, Column 44: reference not terminated by REFC delimiter
    …ref="/cgi-bin/at3/out.cgi?id=369&trade=http://xhamstermom.com/" class="sb_left…

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

  • Error Line 98, Column 137: end tag for "br" omitted, but OMITTAG NO was specified
    …ize:13px" target="_blank">XHamster<br><img src="http://s.hotpornshow.com/thumb…

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

  • Info Line 98, Column 133: start tag was here
    …nt-size:13px" target="_blank">XHamster<br><img src="http://s.hotpornshow.com/t…
  • Error Line 98, Column 222: required attribute "alt" not specified
    …//s.hotpornshow.com/thumbs/002.jpg" width="100" height="75" border="0"></a><BR>

    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 98, Column 226: end tag for "img" omitted, but OMITTAG NO was specified
    …//s.hotpornshow.com/thumbs/002.jpg" width="100" height="75" border="0"></a><BR>

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

  • Info Line 98, Column 137: start tag was here
    …ize:13px" target="_blank">XHamster<br><img src="http://s.hotpornshow.com/thumb…
  • Error Line 98, Column 230: element "BR" undefined
    …//s.hotpornshow.com/thumbs/002.jpg" width="100" height="75" border="0"></a><BR>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 99, Column 44: reference not terminated by REFC delimiter
    …ref="/cgi-bin/at3/out.cgi?id=100&trade=http://www.momsandlovers.com/" class="s…

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

  • Error Line 99, Column 147: end tag for "br" omitted, but OMITTAG NO was specified
    …13px" target="_blank">Wives Lovers<br><img src="http://s.hotpornshow.com/thumb…

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

  • Info Line 99, Column 143: start tag was here
    …ize:13px" target="_blank">Wives Lovers<br><img src="http://s.hotpornshow.com/t…
  • Error Line 99, Column 232: required attribute "alt" not specified
    …//s.hotpornshow.com/thumbs/003.jpg" width="100" height="75" border="0"></a><BR>

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

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

  • Error Line 99, Column 236: end tag for "img" omitted, but OMITTAG NO was specified
    …//s.hotpornshow.com/thumbs/003.jpg" width="100" height="75" border="0"></a><BR>

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

  • Info Line 99, Column 147: start tag was here
    …13px" target="_blank">Wives Lovers<br><img src="http://s.hotpornshow.com/thumb…
  • Error Line 99, Column 240: element "BR" undefined
    …//s.hotpornshow.com/thumbs/003.jpg" width="100" height="75" border="0"></a><BR>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 100, Column 44: reference not terminated by REFC delimiter
    …ref="/cgi-bin/at3/out.cgi?id=390&trade=http://www.sexmomfree.com/" class="sb_l…

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

  • Error Line 100, Column 139: end tag for "br" omitted, but OMITTAG NO was specified
    …size:13px" target="_blank">Mom Sex<br><img src="http://s.hotpornshow.com/thumb…

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

  • Info Line 100, Column 135: start tag was here
    …ont-size:13px" target="_blank">Mom Sex<br><img src="http://s.hotpornshow.com/t…
  • Error Line 100, Column 224: required attribute "alt" not specified
    …//s.hotpornshow.com/thumbs/001.jpg" width="100" height="75" border="0"></a><BR>

    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 100, Column 228: end tag for "img" omitted, but OMITTAG NO was specified
    …//s.hotpornshow.com/thumbs/001.jpg" width="100" height="75" border="0"></a><BR>

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

  • Info Line 100, Column 139: start tag was here
    …size:13px" target="_blank">Mom Sex<br><img src="http://s.hotpornshow.com/thumb…
  • Error Line 100, Column 232: element "BR" undefined
    …//s.hotpornshow.com/thumbs/001.jpg" width="100" height="75" border="0"></a><BR>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 101, Column 44: reference not terminated by REFC delimiter
    …ref="/cgi-bin/at3/out.cgi?id=395&trade=http://www.crazyoldmomtube.com/" class=…

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

  • Error Line 101, Column 146: end tag for "br" omitted, but OMITTAG NO was specified
    …ze:13px" target="_blank">Crazy Mom<br><img src="http://s.hotpornshow.com/thumb…

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

  • Info Line 101, Column 142: start tag was here
    …t-size:13px" target="_blank">Crazy Mom<br><img src="http://s.hotpornshow.com/t…
  • Error Line 101, Column 231: required attribute "alt" not specified
    …//s.hotpornshow.com/thumbs/005.jpg" width="100" height="75" border="0"></a><BR>

    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 101, Column 235: end tag for "img" omitted, but OMITTAG NO was specified
    …//s.hotpornshow.com/thumbs/005.jpg" width="100" height="75" border="0"></a><BR>

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

  • Info Line 101, Column 146: start tag was here
    …ze:13px" target="_blank">Crazy Mom<br><img src="http://s.hotpornshow.com/thumb…
  • Error Line 101, Column 239: element "BR" undefined
    …//s.hotpornshow.com/thumbs/005.jpg" width="100" height="75" border="0"></a><BR>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 102, Column 44: reference not terminated by REFC delimiter
    …ref="/cgi-bin/at3/out.cgi?id=253&trade=http://newmothertube.com/" class="sb_le…

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

  • Error Line 102, Column 141: end tag for "br" omitted, but OMITTAG NO was specified
    …e:13px" target="_blank">New Mother<br><img src="http://s.hotpornshow.com/thumb…

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

  • Info Line 102, Column 137: start tag was here
    …-size:13px" target="_blank">New Mother<br><img src="http://s.hotpornshow.com/t…
  • Error Line 102, Column 226: required attribute "alt" not specified
    …//s.hotpornshow.com/thumbs/006.jpg" width="100" height="75" border="0"></a><BR>

    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 102, Column 230: end tag for "img" omitted, but OMITTAG NO was specified
    …//s.hotpornshow.com/thumbs/006.jpg" width="100" height="75" border="0"></a><BR>

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

  • Info Line 102, Column 141: start tag was here
    …e:13px" target="_blank">New Mother<br><img src="http://s.hotpornshow.com/thumb…
  • Error Line 102, Column 234: element "BR" undefined
    …//s.hotpornshow.com/thumbs/006.jpg" width="100" height="75" border="0"></a><BR>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 103, Column 44: reference not terminated by REFC delimiter
    …ref="/cgi-bin/at3/out.cgi?id=360&trade=http://momsexservant.com/" class="sb_le…

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

  • Error Line 103, Column 142: end tag for "br" omitted, but OMITTAG NO was specified
    …:13px" target="_blank">Sex Servant<br><img src="http://s.hotpornshow.com/thumb…

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

  • Info Line 103, Column 138: start tag was here
    …size:13px" target="_blank">Sex Servant<br><img src="http://s.hotpornshow.com/t…
  • Error Line 103, Column 227: required attribute "alt" not specified
    …//s.hotpornshow.com/thumbs/007.jpg" width="100" height="75" border="0"></a><BR>

    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 103, Column 231: end tag for "img" omitted, but OMITTAG NO was specified
    …//s.hotpornshow.com/thumbs/007.jpg" width="100" height="75" border="0"></a><BR>

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

  • Info Line 103, Column 142: start tag was here
    …:13px" target="_blank">Sex Servant<br><img src="http://s.hotpornshow.com/thumb…
  • Error Line 103, Column 235: element "BR" undefined
    …//s.hotpornshow.com/thumbs/007.jpg" width="100" height="75" border="0"></a><BR>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 104, Column 44: reference not terminated by REFC delimiter
    …ref="/cgi-bin/at3/out.cgi?id=283&trade=http://ohmomtube.com/" class="sb_left" …

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

  • Error Line 104, Column 138: end tag for "br" omitted, but OMITTAG NO was specified
    …:13px" target="_blank">Oh Mom Tube<br><img src="http://s.hotpornshow.com/thumb…

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

  • Info Line 104, Column 134: start tag was here
    …size:13px" target="_blank">Oh Mom Tube<br><img src="http://s.hotpornshow.com/t…
  • Error Line 104, Column 223: required attribute "alt" not specified
    …//s.hotpornshow.com/thumbs/008.jpg" width="100" height="75" border="0"></a><BR>

    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 104, Column 227: end tag for "img" omitted, but OMITTAG NO was specified
    …//s.hotpornshow.com/thumbs/008.jpg" width="100" height="75" border="0"></a><BR>

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

  • Info Line 104, Column 138: start tag was here
    …:13px" target="_blank">Oh Mom Tube<br><img src="http://s.hotpornshow.com/thumb…
  • Error Line 104, Column 231: element "BR" undefined
    …//s.hotpornshow.com/thumbs/008.jpg" width="100" height="75" border="0"></a><BR>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 105, Column 44: reference not terminated by REFC delimiter
    …ref="/cgi-bin/at3/out.cgi?id=338&trade=http://ohvintagetube.com/" class="sb_le…

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

  • Error Line 105, Column 139: end tag for "br" omitted, but OMITTAG NO was specified
    …ize:13px" target="_blank">Oh Retro<br><img src="http://s.hotpornshow.com/thumb…

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

  • Info Line 105, Column 135: start tag was here
    …nt-size:13px" target="_blank">Oh Retro<br><img src="http://s.hotpornshow.com/t…
  • Error Line 105, Column 224: required attribute "alt" not specified
    …//s.hotpornshow.com/thumbs/009.jpg" width="100" height="75" border="0"></a><BR>

    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 105, Column 228: end tag for "img" omitted, but OMITTAG NO was specified
    …//s.hotpornshow.com/thumbs/009.jpg" width="100" height="75" border="0"></a><BR>

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

  • Info Line 105, Column 139: start tag was here
    …ize:13px" target="_blank">Oh Retro<br><img src="http://s.hotpornshow.com/thumb…
  • Error Line 105, Column 232: element "BR" undefined
    …//s.hotpornshow.com/thumbs/009.jpg" width="100" height="75" border="0"></a><BR>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 106, Column 44: reference not terminated by REFC delimiter
    …ref="/cgi-bin/at3/out.cgi?id=341&trade=http://xmomsex.com/" class="sb_left" st…

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

  • Error Line 106, Column 135: end tag for "br" omitted, but OMITTAG NO was specified
    …e:13px" target="_blank">Busty Moms<br><img src="http://s.hotpornshow.com/thumb…

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

  • Info Line 106, Column 131: start tag was here
    …-size:13px" target="_blank">Busty Moms<br><img src="http://s.hotpornshow.com/t…
  • Error Line 106, Column 220: required attribute "alt" not specified
    …//s.hotpornshow.com/thumbs/010.jpg" width="100" height="75" border="0"></a><BR>

    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 106, Column 224: end tag for "img" omitted, but OMITTAG NO was specified
    …//s.hotpornshow.com/thumbs/010.jpg" width="100" height="75" border="0"></a><BR>

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

  • Info Line 106, Column 135: start tag was here
    …e:13px" target="_blank">Busty Moms<br><img src="http://s.hotpornshow.com/thumb…
  • Error Line 106, Column 228: element "BR" undefined
    …//s.hotpornshow.com/thumbs/010.jpg" width="100" height="75" border="0"></a><BR>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 107, Column 44: reference not terminated by REFC delimiter
    …ref="/cgi-bin/at3/out.cgi?id=336&trade=http://cuntssexporn.com/" class="sb_lef…

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

  • Error Line 107, Column 138: end tag for "br" omitted, but OMITTAG NO was specified
    …ize:13px" target="_blank">Cunt Mom<br><img src="http://s.hotpornshow.com/thumb…

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

  • Info Line 107, Column 134: start tag was here
    …nt-size:13px" target="_blank">Cunt Mom<br><img src="http://s.hotpornshow.com/t…
  • Error Line 107, Column 223: required attribute "alt" not specified
    …//s.hotpornshow.com/thumbs/011.jpg" width="100" height="75" border="0"></a><BR>

    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 107, Column 227: end tag for "img" omitted, but OMITTAG NO was specified
    …//s.hotpornshow.com/thumbs/011.jpg" width="100" height="75" border="0"></a><BR>

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

  • Info Line 107, Column 138: start tag was here
    …ize:13px" target="_blank">Cunt Mom<br><img src="http://s.hotpornshow.com/thumb…
  • Error Line 107, Column 231: element "BR" undefined
    …//s.hotpornshow.com/thumbs/011.jpg" width="100" height="75" border="0"></a><BR>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 108, Column 44: reference not terminated by REFC delimiter
    …ref="/cgi-bin/at3/out.cgi?id=325&trade=http://hdsexmom.com/" class="sb_left" s…

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

  • Error Line 108, Column 136: end tag for "br" omitted, but OMITTAG NO was specified
    …e:13px" target="_blank">HD Sex Mom<br><img src="http://s.hotpornshow.com/thumb…

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

  • Info Line 108, Column 132: start tag was here
    …-size:13px" target="_blank">HD Sex Mom<br><img src="http://s.hotpornshow.com/t…
  • Error Line 108, Column 221: required attribute "alt" not specified
    …//s.hotpornshow.com/thumbs/012.jpg" width="100" height="75" border="0"></a><BR>

    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 108, Column 225: end tag for "img" omitted, but OMITTAG NO was specified
    …//s.hotpornshow.com/thumbs/012.jpg" width="100" height="75" border="0"></a><BR>

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

  • Info Line 108, Column 136: start tag was here
    …e:13px" target="_blank">HD Sex Mom<br><img src="http://s.hotpornshow.com/thumb…
  • Error Line 108, Column 229: element "BR" undefined
    …//s.hotpornshow.com/thumbs/012.jpg" width="100" height="75" border="0"></a><BR>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 109, Column 44: reference not terminated by REFC delimiter
    …ref="/cgi-bin/at3/out.cgi?id=156&trade=http://www.bigmothertube.com/" class="s…

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

  • Error Line 109, Column 145: end tag for "br" omitted, but OMITTAG NO was specified
    …e:13px" target="_blank">Big Mother<br><img src="http://s.hotpornshow.com/thumb…

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

  • Info Line 109, Column 141: start tag was here
    …-size:13px" target="_blank">Big Mother<br><img src="http://s.hotpornshow.com/t…
  • Error Line 109, Column 230: required attribute "alt" not specified
    …//s.hotpornshow.com/thumbs/013.jpg" width="100" height="75" border="0"></a><BR>

    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 109, Column 234: end tag for "img" omitted, but OMITTAG NO was specified
    …//s.hotpornshow.com/thumbs/013.jpg" width="100" height="75" border="0"></a><BR>

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

  • Info Line 109, Column 145: start tag was here
    …e:13px" target="_blank">Big Mother<br><img src="http://s.hotpornshow.com/thumb…
  • Error Line 109, Column 238: element "BR" undefined
    …//s.hotpornshow.com/thumbs/013.jpg" width="100" height="75" border="0"></a><BR>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 110, Column 43: reference not terminated by REFC delimiter
    …href="/cgi-bin/at3/out.cgi?id=12&trade=http://www.home-made-videos.com" class=…

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

  • Error Line 110, Column 147: end tag for "br" omitted, but OMITTAG NO was specified
    …:13px" target="_blank">Home Movies<br><img src="http://s.hotpornshow.com/thumb…

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

  • Info Line 110, Column 143: start tag was here
    …size:13px" target="_blank">Home Movies<br><img src="http://s.hotpornshow.com/t…
  • Error Line 110, Column 232: required attribute "alt" not specified
    …//s.hotpornshow.com/thumbs/018.jpg" width="100" height="75" border="0"></a><br>

    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 110, Column 236: end tag for "img" omitted, but OMITTAG NO was specified
    …//s.hotpornshow.com/thumbs/018.jpg" width="100" height="75" border="0"></a><br>

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

  • Info Line 110, Column 147: start tag was here
    …:13px" target="_blank">Home Movies<br><img src="http://s.hotpornshow.com/thumb…
  • Error Line 110, Column 241: end tag for "br" omitted, but OMITTAG NO was specified
    …//s.hotpornshow.com/thumbs/018.jpg" width="100" height="75" border="0"></a><br>

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

  • Info Line 110, Column 237: start tag was here
    …//s.hotpornshow.com/thumbs/018.jpg" width="100" height="75" border="0"></a><br>
  • Error Line 111, Column 121: end tag for "br" omitted, but OMITTAG NO was specified
    …" target="_blank">Amateur Porn</a><br><a href="/cgi-bin/at3/out.cgi?id=343&tra…

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

  • Info Line 111, Column 117: start tag was here
    …13px" target="_blank">Amateur Porn</a><br><a href="/cgi-bin/at3/out.cgi?id=343…
  • Warning Line 111, Column 163: reference not terminated by REFC delimiter
    …ref="/cgi-bin/at3/out.cgi?id=343&trade=http://www.cuckold69.com" class="sb_lef…

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

  • Error Line 111, Column 330: required attribute "alt" not specified
    …//s.hotpornshow.com/thumbs/017.jpg" width="100" height="75" border="0"></a><br>

    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 111, Column 334: end tag for "img" omitted, but OMITTAG NO was specified
    …//s.hotpornshow.com/thumbs/017.jpg" width="100" height="75" border="0"></a><br>

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

  • Info Line 111, Column 245: start tag was here
    …tyle="font-size:13px" target="_blank"><img src="http://s.hotpornshow.com/thumb…
  • Error Line 111, Column 339: end tag for "br" omitted, but OMITTAG NO was specified
    …//s.hotpornshow.com/thumbs/017.jpg" width="100" height="75" border="0"></a><br>

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

  • Info Line 111, Column 335: start tag was here
    …//s.hotpornshow.com/thumbs/017.jpg" width="100" height="75" border="0"></a><br>
  • Error Line 112, Column 12: end tag for "BR" omitted, but OMITTAG NO was specified
    						</div>

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

  • Info Line 109, Column 235: start tag was here
    …//s.hotpornshow.com/thumbs/013.jpg" width="100" height="75" border="0"></a><BR>
  • Error Line 112, Column 12: end tag for "BR" omitted, but OMITTAG NO was specified
    						</div>

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

  • Info Line 108, Column 226: start tag was here
    …//s.hotpornshow.com/thumbs/012.jpg" width="100" height="75" border="0"></a><BR>
  • Error Line 112, Column 12: end tag for "BR" omitted, but OMITTAG NO was specified
    						</div>

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

  • Info Line 107, Column 228: start tag was here
    …//s.hotpornshow.com/thumbs/011.jpg" width="100" height="75" border="0"></a><BR>
  • Error Line 112, Column 12: end tag for "BR" omitted, but OMITTAG NO was specified
    						</div>

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

  • Info Line 106, Column 225: start tag was here
    …//s.hotpornshow.com/thumbs/010.jpg" width="100" height="75" border="0"></a><BR>
  • Error Line 112, Column 12: end tag for "BR" omitted, but OMITTAG NO was specified
    						</div>

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

  • Info Line 105, Column 229: start tag was here
    …//s.hotpornshow.com/thumbs/009.jpg" width="100" height="75" border="0"></a><BR>
  • Error Line 112, Column 12: end tag for "BR" omitted, but OMITTAG NO was specified
    						</div>

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

  • Info Line 104, Column 228: start tag was here
    …//s.hotpornshow.com/thumbs/008.jpg" width="100" height="75" border="0"></a><BR>
  • Error Line 112, Column 12: end tag for "BR" omitted, but OMITTAG NO was specified
    						</div>

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

  • Info Line 103, Column 232: start tag was here
    …//s.hotpornshow.com/thumbs/007.jpg" width="100" height="75" border="0"></a><BR>
  • Error Line 112, Column 12: end tag for "BR" omitted, but OMITTAG NO was specified
    						</div>

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

  • Info Line 102, Column 231: start tag was here
    …//s.hotpornshow.com/thumbs/006.jpg" width="100" height="75" border="0"></a><BR>
  • Error Line 112, Column 12: end tag for "BR" omitted, but OMITTAG NO was specified
    						</div>

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

  • Info Line 101, Column 236: start tag was here
    …//s.hotpornshow.com/thumbs/005.jpg" width="100" height="75" border="0"></a><BR>
  • Error Line 112, Column 12: end tag for "BR" omitted, but OMITTAG NO was specified
    						</div>

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

  • Info Line 100, Column 229: start tag was here
    …//s.hotpornshow.com/thumbs/001.jpg" width="100" height="75" border="0"></a><BR>
  • Error Line 112, Column 12: end tag for "BR" omitted, but OMITTAG NO was specified
    						</div>

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

  • Info Line 99, Column 237: start tag was here
    …//s.hotpornshow.com/thumbs/003.jpg" width="100" height="75" border="0"></a><BR>
  • Error Line 112, Column 12: end tag for "BR" omitted, but OMITTAG NO was specified
    						</div>

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

  • Info Line 98, Column 227: start tag was here
    …//s.hotpornshow.com/thumbs/002.jpg" width="100" height="75" border="0"></a><BR>
  • Error Line 112, Column 12: end tag for "BR" omitted, but OMITTAG NO was specified
    						</div>

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

  • Info Line 97, Column 204: start tag was here
    …//s.hotpornshow.com/thumbs/014.jpg" width="100" height="75" border="0"></a><BR>
  • Error Line 112, Column 12: end tag for "BR" omitted, but OMITTAG NO was specified
    						</div>

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

  • Info Line 96, Column 208: start tag was here
    …//s.hotpornshow.com/thumbs/004.jpg" width="100" height="75" border="0"></a><BR>
  • Error Line 115, Column 49: there is no attribute "style"
    …="sort_panel">&nbsp;&nbsp;<font style="color:#757575"><b>sort by</b></font> &n…

    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 115, Column 64: element "font" undefined
    …nbsp;&nbsp;<font style="color:#757575"><b>sort by</b></font> &nbsp;&nbsp;&nbsp…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 121, Column 173: value of attribute "id" invalid: "2" cannot start a name
    …hotpornshow.com/03/2295203/1.jpg" id="2295203" width="160" height="120" border…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 121, Column 437: end tag for "img" omitted, but OMITTAG NO was specified
    …utiful Blonde Girl In Pink Molly Bennett Having So Beautiful Sex On Video"></a>

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

  • Info Line 121, Column 111: start tag was here
    …aving-so-beautiful-sex-on-video.html"><img src="http://t-us-1.hotpornshow.com/…
  • Error Line 127, Column 33: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=335&trade=…
  • Warning Line 127, Column 79: reference not terminated by REFC delimiter
    …ref="/cgi-bin/at3/out.cgi?id=335&trade=http://coolsexmom.com/">Cool Sex Mom</a…

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

  • Error Line 129, Column 10: ID "video_element" already defined
    <div id="video_element">

    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 119, Column 10: ID "video_element" first defined here
    <div id="video_element">
  • Error Line 130, Column 11: ID "video_title" already defined
    	<div id="video_title"><a href="/watch/2295199/wild-white-granny-getting-fucked…

    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 120, Column 11: ID "video_title" first defined here
    	<div id="video_title"><a href="/watch/2295203/beautiful-blonde-girl-in-pink-mo…
  • Error Line 131, Column 171: value of attribute "id" invalid: "2" cannot start a name
    …hotpornshow.com/99/2295199/6.jpg" id="2295199" width="160" height="120" border…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 131, Column 433: end tag for "img" omitted, but OMITTAG NO was specified
    …ild White Granny Getting Fucked By Strong Younger Black Dude On The Couch"></a>

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

  • Info Line 131, Column 109: start tag was here
    …younger-black-dude-on-the-couch.html"><img src="http://t-us-1.hotpornshow.com/…
  • Error Line 133, Column 13: ID "length" already defined
    			<div id="length">21:02</div><div id="rating">4.99 / 5.00</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 123, Column 13: ID "length" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 133, Column 41: ID "rating" already defined
    			<div id="length">21:02</div><div id="rating">4.99 / 5.00</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 123, Column 41: ID "rating" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 136, Column 12: ID "by" already defined
    		<div id="by">go&nbsp;&nbsp;</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 126, Column 12: ID "by" first defined here
    		<div id="by">go&nbsp;&nbsp;</div>
  • Error Line 137, Column 12: ID "submitter" already defined
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=238&trade=…

    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 127, Column 12: ID "submitter" first defined here
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=335&trade=…
  • Error Line 137, Column 33: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=238&trade=…
  • Warning Line 137, Column 79: reference not terminated by REFC delimiter
    …ref="/cgi-bin/at3/out.cgi?id=238&trade=http://hardmomstube.com/">Hard Moms Tub…

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

  • Error Line 139, Column 10: ID "video_element" already defined
    <div id="video_element">

    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 119, Column 10: ID "video_element" first defined here
    <div id="video_element">
  • Error Line 140, Column 11: ID "video_title" already defined
    	<div id="video_title"><a href="/watch/2295197/mom-came-to-say-good-morning-and…

    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 120, Column 11: ID "video_title" first defined here
    	<div id="video_title"><a href="/watch/2295203/beautiful-blonde-girl-in-pink-mo…
  • Error Line 141, Column 164: value of attribute "id" invalid: "2" cannot start a name
    …hotpornshow.com/97/2295197/5.jpg" id="2295197" width="160" height="120" border…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 141, Column 419: end tag for "img" omitted, but OMITTAG NO was specified
    … alt="Mom Came To Say Good Morning And Wake Up With Passionate Sex Action"></a>

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

  • Info Line 141, Column 102: start tag was here
    …e-up-with-passionate-sex-action.html"><img src="http://t-us-1.hotpornshow.com/…
  • Error Line 143, Column 13: ID "length" already defined
    			<div id="length">19:06</div><div id="rating">4.88 / 5.00</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 123, Column 13: ID "length" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 143, Column 41: ID "rating" already defined
    			<div id="length">19:06</div><div id="rating">4.88 / 5.00</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 123, Column 41: ID "rating" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 146, Column 12: ID "by" already defined
    		<div id="by">go&nbsp;&nbsp;</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 126, Column 12: ID "by" first defined here
    		<div id="by">go&nbsp;&nbsp;</div>
  • Error Line 147, Column 12: ID "submitter" already defined
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=74&trade=h…

    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 127, Column 12: ID "submitter" first defined here
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=335&trade=…
  • Error Line 147, Column 33: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=74&trade=h…
  • Warning Line 147, Column 78: reference not terminated by REFC delimiter
    …href="/cgi-bin/at3/out.cgi?id=74&trade=http://www.maturewifetube.com/">Mature …

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

  • Error Line 149, Column 10: ID "video_element" already defined
    <div id="video_element" style="margin-right:0px">

    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 119, Column 10: ID "video_element" first defined here
    <div id="video_element">
  • Error Line 150, Column 11: ID "video_title" already defined
    	<div id="video_title"><a href="/watch/2295195/prisoner-fucks-a-hot-escort-righ…

    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 120, Column 11: ID "video_title" first defined here
    	<div id="video_title"><a href="/watch/2295203/beautiful-blonde-girl-in-pink-mo…
  • Error Line 151, Column 138: value of attribute "id" invalid: "2" cannot start a name
    …hotpornshow.com/95/2295195/8.jpg" id="2295195" width="160" height="120" border…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 151, Column 367: end tag for "img" omitted, but OMITTAG NO was specified
    …sol.thr.stop('2295195',8)" alt="Prisoner Fucks A Hot Escort Right In Cell"></a>

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

  • Info Line 151, Column 76: start tag was here
    …ucks-a-hot-escort-right-in-cell.html"><img src="http://t-us-1.hotpornshow.com/…
  • Error Line 153, Column 13: ID "length" already defined
    			<div id="length">15:33</div><div id="rating">4.95 / 5.00</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 123, Column 13: ID "length" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 153, Column 41: ID "rating" already defined
    			<div id="length">15:33</div><div id="rating">4.95 / 5.00</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 123, Column 41: ID "rating" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 156, Column 12: ID "by" already defined
    		<div id="by">go&nbsp;&nbsp;</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 126, Column 12: ID "by" first defined here
    		<div id="by">go&nbsp;&nbsp;</div>
  • Error Line 157, Column 12: ID "submitter" already defined
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=318&trade=…

    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 127, Column 12: ID "submitter" first defined here
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=335&trade=…
  • Error Line 157, Column 33: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=318&trade=…
  • Warning Line 157, Column 79: reference not terminated by REFC delimiter
    …ref="/cgi-bin/at3/out.cgi?id=318&trade=http://hqsexmom.com/">HQ Sex Mom</a></d…

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

  • Error Line 159, Column 53: ID "video_row" already defined
    <div style='clear:both;'>&nbsp;</div></div><div id="video_row">

    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 118, Column 10: ID "video_row" first defined here
    <div id="video_row">
  • Error Line 160, Column 10: ID "video_element" already defined
    <div id="video_element">

    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 119, Column 10: ID "video_element" first defined here
    <div id="video_element">
  • Error Line 161, Column 11: ID "video_title" already defined
    	<div id="video_title"><a href="/watch/2295191/chubby-mature-cougars-caught-and…

    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 120, Column 11: ID "video_title" first defined here
    	<div id="video_title"><a href="/watch/2295203/beautiful-blonde-girl-in-pink-mo…
  • Error Line 162, Column 152: value of attribute "id" invalid: "2" cannot start a name
    …hotpornshow.com/91/2295191/4.jpg" id="2295191" width="160" height="120" border…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 162, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …2295191',4)" alt="Chubby Mature Cougars Caught And Fucked A Lucky Student"></a>

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

  • Info Line 162, Column 90: start tag was here
    …ught-and-fucked-a-lucky-student.html"><img src="http://t-us-1.hotpornshow.com/…
  • Error Line 164, Column 13: ID "length" already defined
    			<div id="length">12:14</div><div id="rating">4.99 / 5.00</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 123, Column 13: ID "length" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 164, Column 41: ID "rating" already defined
    			<div id="length">12:14</div><div id="rating">4.99 / 5.00</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 123, Column 41: ID "rating" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 167, Column 12: ID "by" already defined
    		<div id="by">go&nbsp;&nbsp;</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 126, Column 12: ID "by" first defined here
    		<div id="by">go&nbsp;&nbsp;</div>
  • Error Line 168, Column 12: ID "submitter" already defined
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=373&trade=…

    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 127, Column 12: ID "submitter" first defined here
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=335&trade=…
  • Error Line 168, Column 33: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=373&trade=…
  • Warning Line 168, Column 79: reference not terminated by REFC delimiter
    …ref="/cgi-bin/at3/out.cgi?id=373&trade=http://lessonmaturetube.com/">Mature Le…

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

  • Error Line 170, Column 10: ID "video_element" already defined
    <div id="video_element">

    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 119, Column 10: ID "video_element" first defined here
    <div id="video_element">
  • Error Line 171, Column 11: ID "video_title" already defined
    	<div id="video_title"><a href="/watch/2295186/vintage-classic-adult-video---so…

    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 120, Column 11: ID "video_title" first defined here
    	<div id="video_title"><a href="/watch/2295203/beautiful-blonde-girl-in-pink-mo…
  • Error Line 172, Column 169: value of attribute "id" invalid: "2" cannot start a name
    …hotpornshow.com/86/2295186/9.jpg" id="2295186" width="160" height="120" border…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 172, Column 429: end tag for "img" omitted, but OMITTAG NO was specified
    …"Vintage Classic Adult Video - So Hot And Natural Feelings Of Sensual Sex"></a>

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

  • Info Line 172, Column 107: start tag was here
    …natural-feelings-of-sensual-sex.html"><img src="http://t-us-1.hotpornshow.com/…
  • Error Line 174, Column 13: ID "length" already defined
    			<div id="length">01:49:27</div><div id="rating">4.99 / 5.00</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 123, Column 13: ID "length" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 174, Column 44: ID "rating" already defined
    			<div id="length">01:49:27</div><div id="rating">4.99 / 5.00</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 123, Column 41: ID "rating" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 177, Column 12: ID "by" already defined
    		<div id="by">go&nbsp;&nbsp;</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 126, Column 12: ID "by" first defined here
    		<div id="by">go&nbsp;&nbsp;</div>
  • Error Line 178, Column 12: ID "submitter" already defined
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=387&trade=…

    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 127, Column 12: ID "submitter" first defined here
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=335&trade=…
  • Error Line 178, Column 33: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=387&trade=…
  • Warning Line 178, Column 79: reference not terminated by REFC delimiter
    …ref="/cgi-bin/at3/out.cgi?id=387&trade=http://www.videosexmoms.com/">Video Sex…

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

  • Error Line 180, Column 10: ID "video_element" already defined
    <div id="video_element">

    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 119, Column 10: ID "video_element" first defined here
    <div id="video_element">
  • Error Line 181, Column 11: ID "video_title" already defined
    	<div id="video_title"><a href="/watch/2295169/lesbain-sex-between-samantha-rya…

    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 120, Column 11: ID "video_title" first defined here
    	<div id="video_title"><a href="/watch/2295203/beautiful-blonde-girl-in-pink-mo…
  • Error Line 182, Column 148: value of attribute "id" invalid: "2" cannot start a name
    …hotpornshow.com/69/2295169/1.jpg" id="2295169" width="160" height="120" border…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 182, Column 387: end tag for "img" omitted, but OMITTAG NO was specified
    …op('2295169',1)" alt="Lesbain Sex Between Samantha Ryan And Charley Chase"></a>

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

  • Info Line 182, Column 86: start tag was here
    …samantha-ryan-and-charley-chase.html"><img src="http://t-us-1.hotpornshow.com/…
  • Error Line 184, Column 13: ID "length" already defined
    			<div id="length">29:01</div><div id="rating">4.98 / 5.00</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 123, Column 13: ID "length" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 184, Column 41: ID "rating" already defined
    			<div id="length">29:01</div><div id="rating">4.98 / 5.00</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 123, Column 41: ID "rating" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 187, Column 12: ID "by" already defined
    		<div id="by">go&nbsp;&nbsp;</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 126, Column 12: ID "by" first defined here
    		<div id="by">go&nbsp;&nbsp;</div>
  • Error Line 188, Column 12: ID "submitter" already defined
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=292&trade=…

    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 127, Column 12: ID "submitter" first defined here
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=335&trade=…
  • Error Line 188, Column 33: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=292&trade=…
  • Warning Line 188, Column 79: reference not terminated by REFC delimiter
    …ref="/cgi-bin/at3/out.cgi?id=292&trade=http://youngmommyfuckers.com/">Mommy Fu…

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

  • Error Line 190, Column 10: ID "video_element" already defined
    <div id="video_element" style="margin-right:0px">

    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 119, Column 10: ID "video_element" first defined here
    <div id="video_element">
  • Error Line 191, Column 11: ID "video_title" already defined
    	<div id="video_title"><a href="/watch/2295166/ex-striptease-dancing-girls-jane…

    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 120, Column 11: ID "video_title" first defined here
    	<div id="video_title"><a href="/watch/2295203/beautiful-blonde-girl-in-pink-mo…
  • Error Line 192, Column 235: value of attribute "id" invalid: "2" cannot start a name
    …hotpornshow.com/66/2295166/2.jpg" id="2295166" width="160" height="120" border…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 192, Column 561: end tag for "img" omitted, but OMITTAG NO was specified
    …racial Ffmm Group Sex Orgy Sucking Black And White Cocks And Fucking Hard"></a>

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

  • Info Line 192, Column 173: start tag was here
    …nd-white-cocks-and-fucking-hard.html"><img src="http://t-us-1.hotpornshow.com/…
  • Error Line 194, Column 13: ID "length" already defined
    			<div id="length">25:46</div><div id="rating">4.99 / 5.00</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 123, Column 13: ID "length" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 194, Column 41: ID "rating" already defined
    			<div id="length">25:46</div><div id="rating">4.99 / 5.00</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 123, Column 41: ID "rating" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 197, Column 12: ID "by" already defined
    		<div id="by">go&nbsp;&nbsp;</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 126, Column 12: ID "by" first defined here
    		<div id="by">go&nbsp;&nbsp;</div>
  • Error Line 198, Column 12: ID "submitter" already defined
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=328&trade=…

    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 127, Column 12: ID "submitter" first defined here
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=335&trade=…
  • Error Line 198, Column 33: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=328&trade=…
  • Warning Line 198, Column 79: reference not terminated by REFC delimiter
    …ref="/cgi-bin/at3/out.cgi?id=328&trade=http://boommature.com/">Boom Mature</a>…

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

  • Error Line 200, Column 53: ID "video_row" already defined
    <div style='clear:both;'>&nbsp;</div></div><div id="video_row">

    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 118, Column 10: ID "video_row" first defined here
    <div id="video_row">
  • Error Line 201, Column 10: ID "video_element" already defined
    <div id="video_element">

    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 119, Column 10: ID "video_element" first defined here
    <div id="video_element">
  • Error Line 202, Column 11: ID "video_title" already defined
    	<div id="video_title"><a href="/watch/2295163/playing-with-sweet-pussy-of-hot-…

    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 120, Column 11: ID "video_title" first defined here
    	<div id="video_title"><a href="/watch/2295203/beautiful-blonde-girl-in-pink-mo…
  • Error Line 203, Column 150: value of attribute "id" invalid: "2" cannot start a name
    …hotpornshow.com/63/2295163/1.jpg" id="2295163" width="160" height="120" border…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 203, Column 391: end tag for "img" omitted, but OMITTAG NO was specified
    …('2295163',1)" alt="Playing With Sweet Pussy Of Hot Brunette And Her Feet"></a>

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

  • Info Line 203, Column 88: start tag was here
    …sy-of-hot-brunette-and-her-feet.html"><img src="http://t-us-1.hotpornshow.com/…
  • Error Line 205, Column 13: ID "length" already defined
    			<div id="length">23:04</div><div id="rating">4.96 / 5.00</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 123, Column 13: ID "length" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 205, Column 41: ID "rating" already defined
    			<div id="length">23:04</div><div id="rating">4.96 / 5.00</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 123, Column 41: ID "rating" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 208, Column 12: ID "by" already defined
    		<div id="by">go&nbsp;&nbsp;</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 126, Column 12: ID "by" first defined here
    		<div id="by">go&nbsp;&nbsp;</div>
  • Error Line 209, Column 12: ID "submitter" already defined
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=162&trade=…

    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 127, Column 12: ID "submitter" first defined here
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=335&trade=…
  • Error Line 209, Column 33: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=162&trade=…
  • Warning Line 209, Column 79: reference not terminated by REFC delimiter
    …ref="/cgi-bin/at3/out.cgi?id=162&trade=http://www.nicemothertube.com/">Nice Mo…

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

  • Error Line 211, Column 10: ID "video_element" already defined
    <div id="video_element">

    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 119, Column 10: ID "video_element" first defined here
    <div id="video_element">
  • Error Line 212, Column 11: ID "video_title" already defined
    	<div id="video_title"><a href="/watch/2295157/sugar-bbw-girls-tera-and-april-g…

    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 120, Column 11: ID "video_title" first defined here
    	<div id="video_title"><a href="/watch/2295203/beautiful-blonde-girl-in-pink-mo…
  • Error Line 213, Column 185: value of attribute "id" invalid: "2" cannot start a name
    …hotpornshow.com/57/2295157/5.jpg" id="2295157" width="160" height="120" border…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 213, Column 461: end tag for "img" omitted, but OMITTAG NO was specified
    … Tera And April Giving Handjob Titjob And Fucking That Lucky Guy Together"></a>

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

  • Info Line 213, Column 123: start tag was here
    …fucking-that-lucky-guy-together.html"><img src="http://t-us-1.hotpornshow.com/…
  • Error Line 215, Column 13: ID "length" already defined
    			<div id="length">21:19</div><div id="rating">4.98 / 5.00</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 123, Column 13: ID "length" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 215, Column 41: ID "rating" already defined
    			<div id="length">21:19</div><div id="rating">4.98 / 5.00</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 123, Column 41: ID "rating" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 218, Column 12: ID "by" already defined
    		<div id="by">go&nbsp;&nbsp;</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 126, Column 12: ID "by" first defined here
    		<div id="by">go&nbsp;&nbsp;</div>
  • Error Line 219, Column 12: ID "submitter" already defined
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=315&trade=…

    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 127, Column 12: ID "submitter" first defined here
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=335&trade=…
  • Error Line 219, Column 33: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=315&trade=…
  • Warning Line 219, Column 79: reference not terminated by REFC delimiter
    …ref="/cgi-bin/at3/out.cgi?id=315&trade=http://sexpornmom.com/">Sex Porn Mom</a…

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

  • Error Line 221, Column 10: ID "video_element" already defined
    <div id="video_element">

    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 119, Column 10: ID "video_element" first defined here
    <div id="video_element">
  • Error Line 222, Column 11: ID "video_title" already defined
    	<div id="video_title"><a href="/watch/2295146/very-hot-brunette-milfs-having-g…

    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 120, Column 11: ID "video_title" first defined here
    	<div id="video_title"><a href="/watch/2295203/beautiful-blonde-girl-in-pink-mo…
  • Error Line 223, Column 214: value of attribute "id" invalid: "2" cannot start a name
    …hotpornshow.com/46/2295146/7.jpg" id="2295146" width="160" height="120" border…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 223, Column 519: end tag for "img" omitted, but OMITTAG NO was specified
    …h One Strong Man Who Fucks Them Together And Fully Satisfies Female Flesh"></a>

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

  • Info Line 223, Column 152: start tag was here
    …nd-fully-satisfies-female-flesh.html"><img src="http://t-us-1.hotpornshow.com/…
  • Error Line 225, Column 13: ID "length" already defined
    			<div id="length">25:37</div><div id="rating">4.98 / 5.00</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 123, Column 13: ID "length" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 225, Column 41: ID "rating" already defined
    			<div id="length">25:37</div><div id="rating">4.98 / 5.00</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 123, Column 41: ID "rating" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 228, Column 12: ID "by" already defined
    		<div id="by">go&nbsp;&nbsp;</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 126, Column 12: ID "by" first defined here
    		<div id="by">go&nbsp;&nbsp;</div>
  • Error Line 229, Column 12: ID "submitter" already defined
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=320&trade=…

    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 127, Column 12: ID "submitter" first defined here
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=335&trade=…
  • Error Line 229, Column 33: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=320&trade=…
  • Warning Line 229, Column 79: reference not terminated by REFC delimiter
    …ref="/cgi-bin/at3/out.cgi?id=320&trade=http://lovemothertube.com/">Love Moms T…

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

  • Error Line 231, Column 10: ID "video_element" already defined
    <div id="video_element" style="margin-right:0px">

    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 119, Column 10: ID "video_element" first defined here
    <div id="video_element">
  • Error Line 232, Column 11: ID "video_title" already defined
    	<div id="video_title"><a href="/watch/2295140/wild-bitch-mouth-fucked-hard.htm…

    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 120, Column 11: ID "video_title" first defined here
    	<div id="video_title"><a href="/watch/2295203/beautiful-blonde-girl-in-pink-mo…
  • Error Line 233, Column 125: value of attribute "id" invalid: "2" cannot start a name
    …hotpornshow.com/40/2295140/6.jpg" id="2295140" width="160" height="120" border…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 233, Column 341: end tag for "img" omitted, but OMITTAG NO was specified
    … onmouseout="sol.thr.stop('2295140',6)" alt="Wild Bitch Mouth Fucked Hard"></a>

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

  • Info Line 233, Column 63: start tag was here
    …40/wild-bitch-mouth-fucked-hard.html"><img src="http://t-us-1.hotpornshow.com/…
  • Error Line 235, Column 13: ID "length" already defined
    			<div id="length">12:36</div><div id="rating">4.99 / 5.00</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 123, Column 13: ID "length" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 235, Column 41: ID "rating" already defined
    			<div id="length">12:36</div><div id="rating">4.99 / 5.00</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 123, Column 41: ID "rating" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 238, Column 12: ID "by" already defined
    		<div id="by">go&nbsp;&nbsp;</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 126, Column 12: ID "by" first defined here
    		<div id="by">go&nbsp;&nbsp;</div>
  • Error Line 239, Column 12: ID "submitter" already defined
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=41&trade=h…

    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 127, Column 12: ID "submitter" first defined here
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=335&trade=…
  • Error Line 239, Column 33: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=41&trade=h…
  • Warning Line 239, Column 78: reference not terminated by REFC delimiter
    …href="/cgi-bin/at3/out.cgi?id=41&trade=http://www.homemadeporntubes.com/">Home…

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

  • Error Line 241, Column 53: ID "video_row" already defined
    <div style='clear:both;'>&nbsp;</div></div><div id="video_row">

    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 118, Column 10: ID "video_row" first defined here
    <div id="video_row">
  • Error Line 242, Column 10: ID "video_element" already defined
    <div id="video_element">

    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 119, Column 10: ID "video_element" first defined here
    <div id="video_element">
  • Error Line 243, Column 11: ID "video_title" already defined
    	<div id="video_title"><a href="/watch/2295138/white-middle-aged-wife-gets-her-…

    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 120, Column 11: ID "video_title" first defined here
    	<div id="video_title"><a href="/watch/2295203/beautiful-blonde-girl-in-pink-mo…
  • Error Line 244, Column 187: value of attribute "id" invalid: "2" cannot start a name
    …hotpornshow.com/38/2295138/4.jpg" id="2295138" width="160" height="120" border…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 244, Column 465: end tag for "img" omitted, but OMITTAG NO was specified
    … Wife Gets Her Very Tight Ass Fucked By Big Black Cock Of Her Ebony Lover"></a>

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

  • Info Line 244, Column 125: start tag was here
    …g-black-cock-of-her-ebony-lover.html"><img src="http://t-us-1.hotpornshow.com/…
  • Error Line 246, Column 13: ID "length" already defined
    			<div id="length">35:32</div><div id="rating">4.99 / 5.00</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 123, Column 13: ID "length" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 246, Column 41: ID "rating" already defined
    			<div id="length">35:32</div><div id="rating">4.99 / 5.00</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 123, Column 41: ID "rating" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 249, Column 12: ID "by" already defined
    		<div id="by">go&nbsp;&nbsp;</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 126, Column 12: ID "by" first defined here
    		<div id="by">go&nbsp;&nbsp;</div>
  • Error Line 250, Column 12: ID "submitter" already defined
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=313&trade=…

    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 127, Column 12: ID "submitter" first defined here
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=335&trade=…
  • Error Line 250, Column 33: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=313&trade=…
  • Warning Line 250, Column 79: reference not terminated by REFC delimiter
    …ref="/cgi-bin/at3/out.cgi?id=313&trade=http://www.oldcunttube.com/">Old Cunt T…

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

  • Error Line 252, Column 10: ID "video_element" already defined
    <div id="video_element">

    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 119, Column 10: ID "video_element" first defined here
    <div id="video_element">
  • Error Line 253, Column 11: ID "video_title" already defined
    	<div id="video_title"><a href="/watch/2295135/beautiful-blonde-hottie-dressed-…

    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 120, Column 11: ID "video_title" first defined here
    	<div id="video_title"><a href="/watch/2295203/beautiful-blonde-girl-in-pink-mo…
  • Error Line 254, Column 172: value of attribute "id" invalid: "2" cannot start a name
    …hotpornshow.com/35/2295135/3.jpg" id="2295135" width="160" height="120" border…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 254, Column 435: end tag for "img" omitted, but OMITTAG NO was specified
    …autiful Blonde Hottie Dressed In Pink Swimsuit Stripping Outdoors For You"></a>

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

  • Info Line 254, Column 110: start tag was here
    …suit-stripping-outdoors-for-you.html"><img src="http://t-us-1.hotpornshow.com/…
  • Error Line 256, Column 13: ID "length" already defined
    			<div id="length">08:34</div><div id="rating">4.97 / 5.00</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 123, Column 13: ID "length" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 256, Column 41: ID "rating" already defined
    			<div id="length">08:34</div><div id="rating">4.97 / 5.00</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 123, Column 41: ID "rating" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 259, Column 12: ID "by" already defined
    		<div id="by">go&nbsp;&nbsp;</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 126, Column 12: ID "by" first defined here
    		<div id="by">go&nbsp;&nbsp;</div>
  • Error Line 260, Column 12: ID "submitter" already defined
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=185&trade=…

    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 127, Column 12: ID "submitter" first defined here
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=335&trade=…
  • Error Line 260, Column 33: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=185&trade=…
  • Warning Line 260, Column 79: reference not terminated by REFC delimiter
    …ref="/cgi-bin/at3/out.cgi?id=185&trade=http://topmaturetube.com/">Top Mature T…

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

  • Error Line 262, Column 10: ID "video_element" already defined
    <div id="video_element">

    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 119, Column 10: ID "video_element" first defined here
    <div id="video_element">
  • Error Line 263, Column 11: ID "video_title" already defined
    	<div id="video_title"><a href="/watch/2295132/beautiful-blonde-lesbian-girlfri…

    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 120, Column 11: ID "video_title" first defined here
    	<div id="video_title"><a href="/watch/2295203/beautiful-blonde-girl-in-pink-mo…
  • Error Line 264, Column 164: value of attribute "id" invalid: "2" cannot start a name
    …otpornshow.com/32/2295132/10.jpg" id="2295132" width="160" height="120" border…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 264, Column 419: end tag for "img" omitted, but OMITTAG NO was specified
    …" alt="Beautiful Blonde Lesbian Girlfriends Having Sensual Sex On The Bed"></a>

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

  • Info Line 264, Column 101: start tag was here
    …s-having-sensual-sex-on-the-bed.html"><img src="http://t-us-1.hotpornshow.com/…
  • Error Line 266, Column 13: ID "length" already defined
    			<div id="length">32:39</div><div id="rating">4.89 / 5.00</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 123, Column 13: ID "length" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 266, Column 41: ID "rating" already defined
    			<div id="length">32:39</div><div id="rating">4.89 / 5.00</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 123, Column 41: ID "rating" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 269, Column 12: ID "by" already defined
    		<div id="by">go&nbsp;&nbsp;</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 126, Column 12: ID "by" first defined here
    		<div id="by">go&nbsp;&nbsp;</div>
  • Error Line 270, Column 12: ID "submitter" already defined
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=356&trade=…

    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 127, Column 12: ID "submitter" first defined here
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=335&trade=…
  • Error Line 270, Column 33: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=356&trade=…
  • Warning Line 270, Column 79: reference not terminated by REFC delimiter
    …href="/cgi-bin/at3/out.cgi?id=356&trade=http://sexlend.com/">Sex Lend</a></div>

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

  • Error Line 272, Column 10: ID "video_element" already defined
    <div id="video_element" style="margin-right:0px">

    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 119, Column 10: ID "video_element" first defined here
    <div id="video_element">
  • Error Line 273, Column 11: ID "video_title" already defined
    	<div id="video_title"><a href="/watch/2295130/happy-satisfied-mistress-jerking…

    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 120, Column 11: ID "video_title" first defined here
    	<div id="video_title"><a href="/watch/2295203/beautiful-blonde-girl-in-pink-mo…
  • Error Line 274, Column 194: value of attribute "id" invalid: "2" cannot start a name
    …hotpornshow.com/30/2295130/8.jpg" id="2295130" width="160" height="120" border…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 274, Column 479: end tag for "img" omitted, but OMITTAG NO was specified
    … Jerking Big Cock Of Her Lover By Strong Skillful Hands - Awesome Handjob"></a>

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

  • Info Line 274, Column 132: start tag was here
    …killful-hands---awesome-handjob.html"><img src="http://t-us-1.hotpornshow.com/…
  • Error Line 276, Column 13: ID "length" already defined
    			<div id="length">06:34</div><div id="rating">4.98 / 5.00</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 123, Column 13: ID "length" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 276, Column 41: ID "rating" already defined
    			<div id="length">06:34</div><div id="rating">4.98 / 5.00</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 123, Column 41: ID "rating" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 279, Column 12: ID "by" already defined
    		<div id="by">go&nbsp;&nbsp;</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 126, Column 12: ID "by" first defined here
    		<div id="by">go&nbsp;&nbsp;</div>
  • Error Line 280, Column 12: ID "submitter" already defined
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=229&trade=…

    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 127, Column 12: ID "submitter" first defined here
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=335&trade=…
  • Error Line 280, Column 33: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=229&trade=…
  • Warning Line 280, Column 79: reference not terminated by REFC delimiter
    …ref="/cgi-bin/at3/out.cgi?id=229&trade=http://bigretrotube.com/">Big Retro Tub…

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

  • Error Line 282, Column 53: ID "video_row" already defined
    <div style='clear:both;'>&nbsp;</div></div><div id="video_row">

    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 118, Column 10: ID "video_row" first defined here
    <div id="video_row">
  • Error Line 283, Column 10: ID "video_element" already defined
    <div id="video_element">

    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 119, Column 10: ID "video_element" first defined here
    <div id="video_element">
  • Error Line 284, Column 11: ID "video_title" already defined
    	<div id="video_title"><a href="/watch/2295128/slim-blonde-colege-girl-with-big…

    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 120, Column 11: ID "video_title" first defined here
    	<div id="video_title"><a href="/watch/2295203/beautiful-blonde-girl-in-pink-mo…
  • Error Line 285, Column 157: value of attribute "id" invalid: "2" cannot start a name
    …hotpornshow.com/28/2295128/7.jpg" id="2295128" width="160" height="120" border…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 285, Column 405: end tag for "img" omitted, but OMITTAG NO was specified
    …28',7)" alt="Slim Blonde Colege Girl With Big Tits Fucking During Lection"></a>

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

  • Info Line 285, Column 95: start tag was here
    …big-tits-fucking-during-lection.html"><img src="http://t-us-1.hotpornshow.com/…
  • Error Line 287, Column 13: ID "length" already defined
    			<div id="length">29:16</div><div id="rating">4.98 / 5.00</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 123, Column 13: ID "length" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 287, Column 41: ID "rating" already defined
    			<div id="length">29:16</div><div id="rating">4.98 / 5.00</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 123, Column 41: ID "rating" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 290, Column 12: ID "by" already defined
    		<div id="by">go&nbsp;&nbsp;</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 126, Column 12: ID "by" first defined here
    		<div id="by">go&nbsp;&nbsp;</div>
  • Error Line 291, Column 12: ID "submitter" already defined
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=276&trade=…

    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 127, Column 12: ID "submitter" first defined here
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=335&trade=…
  • Error Line 291, Column 33: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=276&trade=…
  • Warning Line 291, Column 79: reference not terminated by REFC delimiter
    …ref="/cgi-bin/at3/out.cgi?id=276&trade=http://oldmatureladiestube.com/">Old Ma…

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

  • Error Line 293, Column 10: ID "video_element" already defined
    <div id="video_element">

    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 119, Column 10: ID "video_element" first defined here
    <div id="video_element">
  • Error Line 294, Column 11: ID "video_title" already defined
    	<div id="video_title"><a href="/watch/2295123/sugar-mom-with-big-fuckable-ass-…

    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 120, Column 11: ID "video_title" first defined here
    	<div id="video_title"><a href="/watch/2295203/beautiful-blonde-girl-in-pink-mo…
  • Error Line 295, Column 140: value of attribute "id" invalid: "2" cannot start a name
    …hotpornshow.com/23/2295123/5.jpg" id="2295123" width="160" height="120" border…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 295, Column 371: end tag for "img" omitted, but OMITTAG NO was specified
    …l.thr.stop('2295123',5)" alt="Sugar Mom With Big Fuckable Ass Riding Cock"></a>

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

  • Info Line 295, Column 78: start tag was here
    …th-big-fuckable-ass-riding-cock.html"><img src="http://t-us-1.hotpornshow.com/…
  • Error Line 297, Column 13: ID "length" already defined
    			<div id="length">22:25</div><div id="rating">4.99 / 5.00</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 123, Column 13: ID "length" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 297, Column 41: ID "rating" already defined
    			<div id="length">22:25</div><div id="rating">4.99 / 5.00</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 123, Column 41: ID "rating" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 300, Column 12: ID "by" already defined
    		<div id="by">go&nbsp;&nbsp;</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 126, Column 12: ID "by" first defined here
    		<div id="by">go&nbsp;&nbsp;</div>
  • Error Line 301, Column 12: ID "submitter" already defined
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=273&trade=…

    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 127, Column 12: ID "submitter" first defined here
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=335&trade=…
  • Error Line 301, Column 33: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=273&trade=…
  • Warning Line 301, Column 79: reference not terminated by REFC delimiter
    …ref="/cgi-bin/at3/out.cgi?id=273&trade=http://bigmatureladiestube.com/">Big Ma…

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

  • Error Line 303, Column 10: ID "video_element" already defined
    <div id="video_element">

    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 119, Column 10: ID "video_element" first defined here
    <div id="video_element">
  • Error Line 304, Column 11: ID "video_title" already defined
    	<div id="video_title"><a href="/watch/2295117/cute-blonde-german-girl-fucking-…

    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 120, Column 11: ID "video_title" first defined here
    	<div id="video_title"><a href="/watch/2295203/beautiful-blonde-girl-in-pink-mo…
  • Error Line 305, Column 145: value of attribute "id" invalid: "2" cannot start a name
    …hotpornshow.com/17/2295117/4.jpg" id="2295117" width="160" height="120" border…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 305, Column 381: end tag for "img" omitted, but OMITTAG NO was specified
    ….stop('2295117',4)" alt="Cute Blonde German Girl Fucking Friend In Forest"></a>

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

  • Info Line 305, Column 83: start tag was here
    …n-girl-fucking-friend-in-forest.html"><img src="http://t-us-1.hotpornshow.com/…
  • Error Line 307, Column 13: ID "length" already defined
    			<div id="length">22:10</div><div id="rating">5.00 / 5.00</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 123, Column 13: ID "length" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 307, Column 41: ID "rating" already defined
    			<div id="length">22:10</div><div id="rating">5.00 / 5.00</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 123, Column 41: ID "rating" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 310, Column 12: ID "by" already defined
    		<div id="by">go&nbsp;&nbsp;</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 126, Column 12: ID "by" first defined here
    		<div id="by">go&nbsp;&nbsp;</div>
  • Error Line 311, Column 12: ID "submitter" already defined
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=293&trade=…

    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 127, Column 12: ID "submitter" first defined here
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=335&trade=…
  • Error Line 311, Column 33: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=293&trade=…
  • Warning Line 311, Column 79: reference not terminated by REFC delimiter
    …ref="/cgi-bin/at3/out.cgi?id=293&trade=http://beautifulmaturetube.com/">Beauti…

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

  • Error Line 313, Column 10: ID "video_element" already defined
    <div id="video_element" style="margin-right:0px">

    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 119, Column 10: ID "video_element" first defined here
    <div id="video_element">
  • Error Line 314, Column 11: ID "video_title" already defined
    	<div id="video_title"><a href="/watch/2295115/accidental-fuck-in-dvd-store.htm…

    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 120, Column 11: ID "video_title" first defined here
    	<div id="video_title"><a href="/watch/2295203/beautiful-blonde-girl-in-pink-mo…
  • Error Line 315, Column 126: value of attribute "id" invalid: "2" cannot start a name
    …otpornshow.com/15/2295115/10.jpg" id="2295115" width="160" height="120" border…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 315, Column 343: end tag for "img" omitted, but OMITTAG NO was specified
    …onmouseout="sol.thr.stop('2295115',10)" alt="Accidental Fuck In Dvd Store"></a>

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

  • Info Line 315, Column 63: start tag was here
    …15/accidental-fuck-in-dvd-store.html"><img src="http://t-us-1.hotpornshow.com/…
  • Error Line 317, Column 13: ID "length" already defined
    			<div id="length">09:41</div><div id="rating">4.97 / 5.00</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 123, Column 13: ID "length" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 317, Column 41: ID "rating" already defined
    			<div id="length">09:41</div><div id="rating">4.97 / 5.00</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 123, Column 41: ID "rating" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 320, Column 12: ID "by" already defined
    		<div id="by">go&nbsp;&nbsp;</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 126, Column 12: ID "by" first defined here
    		<div id="by">go&nbsp;&nbsp;</div>
  • Error Line 321, Column 12: ID "submitter" already defined
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=81&trade=h…

    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 127, Column 12: ID "submitter" first defined here
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=335&trade=…
  • Error Line 321, Column 33: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=81&trade=h…
  • Warning Line 321, Column 78: reference not terminated by REFC delimiter
    …href="/cgi-bin/at3/out.cgi?id=81&trade=http://www.hotmomsex.net/">Hot sexy mom…

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

  • Error Line 323, Column 53: ID "video_row" already defined
    <div style='clear:both;'>&nbsp;</div></div><div id="video_row">

    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 118, Column 10: ID "video_row" first defined here
    <div id="video_row">
  • Error Line 324, Column 10: ID "video_element" already defined
    <div id="video_element">

    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 119, Column 10: ID "video_element" first defined here
    <div id="video_element">
  • Error Line 325, Column 11: ID "video_title" already defined
    	<div id="video_title"><a href="/watch/2295111/sarah-twain-getting-double-penet…

    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 120, Column 11: ID "video_title" first defined here
    	<div id="video_title"><a href="/watch/2295203/beautiful-blonde-girl-in-pink-mo…
  • Error Line 326, Column 177: value of attribute "id" invalid: "2" cannot start a name
    …hotpornshow.com/11/2295111/4.jpg" id="2295111" width="160" height="120" border…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 326, Column 445: end tag for "img" omitted, but OMITTAG NO was specified
    …wain Getting Double Penetrated - Fucked In Ass And Pussy At The Same Time"></a>

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

  • Info Line 326, Column 115: start tag was here
    …-ass-and-pussy-at-the-same-time.html"><img src="http://t-us-1.hotpornshow.com/…
  • Error Line 328, Column 13: ID "length" already defined
    			<div id="length">23:30</div><div id="rating">4.97 / 5.00</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 123, Column 13: ID "length" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 328, Column 41: ID "rating" already defined
    			<div id="length">23:30</div><div id="rating">4.97 / 5.00</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 123, Column 41: ID "rating" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 331, Column 12: ID "by" already defined
    		<div id="by">go&nbsp;&nbsp;</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 126, Column 12: ID "by" first defined here
    		<div id="by">go&nbsp;&nbsp;</div>
  • Error Line 332, Column 12: ID "submitter" already defined
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=177&trade=…

    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 127, Column 12: ID "submitter" first defined here
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=335&trade=…
  • Error Line 332, Column 33: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=177&trade=…
  • Warning Line 332, Column 79: reference not terminated by REFC delimiter
    …ref="/cgi-bin/at3/out.cgi?id=177&trade=http://goldmotherstube.com/">Gold Mothe…

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

  • Error Line 334, Column 10: ID "video_element" already defined
    <div id="video_element">

    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 119, Column 10: ID "video_element" first defined here
    <div id="video_element">
  • Error Line 335, Column 11: ID "video_title" already defined
    	<div id="video_title"><a href="/watch/2295106/wild-fucking-russian-ass-of-desp…

    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 120, Column 11: ID "video_title" first defined here
    	<div id="video_title"><a href="/watch/2295203/beautiful-blonde-girl-in-pink-mo…
  • Error Line 336, Column 151: value of attribute "id" invalid: "2" cannot start a name
    …hotpornshow.com/06/2295106/4.jpg" id="2295106" width="160" height="120" border…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 336, Column 393: end tag for "img" omitted, but OMITTAG NO was specified
    …'2295106',4)" alt="Wild Fucking Russian Ass Of Desperate Immigrant Blonde"></a>

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

  • Info Line 336, Column 89: start tag was here
    …s-of-desperate-immigrant-blonde.html"><img src="http://t-us-1.hotpornshow.com/…
  • Error Line 338, Column 13: ID "length" already defined
    			<div id="length">19:40</div><div id="rating">5.00 / 5.00</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 123, Column 13: ID "length" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 338, Column 41: ID "rating" already defined
    			<div id="length">19:40</div><div id="rating">5.00 / 5.00</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 123, Column 41: ID "rating" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 341, Column 12: ID "by" already defined
    		<div id="by">go&nbsp;&nbsp;</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 126, Column 12: ID "by" first defined here
    		<div id="by">go&nbsp;&nbsp;</div>
  • Error Line 342, Column 12: ID "submitter" already defined
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=308&trade=…

    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 127, Column 12: ID "submitter" first defined here
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=335&trade=…
  • Error Line 342, Column 33: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=308&trade=…
  • Warning Line 342, Column 79: reference not terminated by REFC delimiter
    …ref="/cgi-bin/at3/out.cgi?id=308&trade=http://tubematurefuck.com/">Mature Fuck…

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

  • Error Line 344, Column 10: ID "video_element" already defined
    <div id="video_element">

    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 119, Column 10: ID "video_element" first defined here
    <div id="video_element">
  • Error Line 345, Column 11: ID "video_title" already defined
    	<div id="video_title"><a href="/watch/2295104/sugar-asian-woman-mika-tan-sprea…

    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 120, Column 11: ID "video_title" first defined here
    	<div id="video_title"><a href="/watch/2295203/beautiful-blonde-girl-in-pink-mo…
  • Error Line 346, Column 191: value of attribute "id" invalid: "2" cannot start a name
    …hotpornshow.com/04/2295104/8.jpg" id="2295104" width="160" height="120" border…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 346, Column 473: end tag for "img" omitted, but OMITTAG NO was specified
    …a Tan Spreading Legs Wide Opens Her Hairy Pussy And Asks To Fuck Her Good"></a>

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

  • Info Line 346, Column 129: start tag was here
    …pussy-and-asks-to-fuck-her-good.html"><img src="http://t-us-1.hotpornshow.com/…
  • Error Line 348, Column 13: ID "length" already defined
    			<div id="length">16:11</div><div id="rating">5.00 / 5.00</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 123, Column 13: ID "length" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 348, Column 41: ID "rating" already defined
    			<div id="length">16:11</div><div id="rating">5.00 / 5.00</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 123, Column 41: ID "rating" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 351, Column 12: ID "by" already defined
    		<div id="by">go&nbsp;&nbsp;</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 126, Column 12: ID "by" first defined here
    		<div id="by">go&nbsp;&nbsp;</div>
  • Error Line 352, Column 12: ID "submitter" already defined
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=133&trade=…

    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 127, Column 12: ID "submitter" first defined here
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=335&trade=…
  • Error Line 352, Column 33: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=133&trade=…
  • Warning Line 352, Column 79: reference not terminated by REFC delimiter
    …ref="/cgi-bin/at3/out.cgi?id=133&trade=http://www.fuckedoldmoms.com/">Fucked O…

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

  • Error Line 354, Column 10: ID "video_element" already defined
    <div id="video_element" style="margin-right:0px">

    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 119, Column 10: ID "video_element" first defined here
    <div id="video_element">
  • Error Line 355, Column 11: ID "video_title" already defined
    	<div id="video_title"><a href="/watch/2295100/xmas-outdoor-fuck-with-santas-cu…

    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 120, Column 11: ID "video_title" first defined here
    	<div id="video_title"><a href="/watch/2295203/beautiful-blonde-girl-in-pink-mo…
  • Error Line 356, Column 146: value of attribute "id" invalid: "2" cannot start a name
    …otpornshow.com/00/2295100/10.jpg" id="2295100" width="160" height="120" border…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 356, Column 383: end tag for "img" omitted, but OMITTAG NO was specified
    …stop('2295100',10)" alt="Xmas Outdoor Fuck With Santas Cute Brunette Girl"></a>

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

  • Info Line 356, Column 83: start tag was here
    …-with-santas-cute-brunette-girl.html"><img src="http://t-us-1.hotpornshow.com/…
  • Error Line 358, Column 13: ID "length" already defined
    			<div id="length">34:33</div><div id="rating">4.94 / 5.00</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 123, Column 13: ID "length" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 358, Column 41: ID "rating" already defined
    			<div id="length">34:33</div><div id="rating">4.94 / 5.00</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 123, Column 41: ID "rating" first defined here
    			<div id="length">24:28</div><div id="rating">4.92 / 5.00</div>
  • Error Line 361, Column 12: ID "by" already defined
    		<div id="by">go&nbsp;&nbsp;</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 126, Column 12: ID "by" first defined here
    		<div id="by">go&nbsp;&nbsp;</div>
  • Error Line 362, Column 12: ID "submitter" already defined
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=304&trade=…

    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 127, Column 12: ID "submitter" first defined here
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=335&trade=…
  • Error Line 362, Column 33: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<div id="submitter"><a target=_blank href="/cgi-bin/at3/out.cgi?id=304&trade=…
  • Warning Line 362, Column 79: reference not terminated by REFC delimiter
    …ref="/cgi-bin/at3/out.cgi?id=304&trade=http://momscooltube.com/">Moms Cool Tub…

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

  • Error Line 364, Column 51: element "center" undefined
    <div style='clear:both;'>&nbsp;</div></div><center>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 365, Column 23: there is no attribute "align"
    <div id='pages' align='center'>

    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 377, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br>

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

  • Info Line 377, Column 1: start tag was here
    <br><br>
  • Error Line 377, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br>

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

  • Info Line 377, Column 5: start tag was here
    <br><br>
  • Error Line 381, Column 16: there is no attribute "hspace"
    <iframe hspace=0 vspace=0 border=0 frameborder=0 marginheight=0 marginwidth=0 w…

    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 381, Column 16: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe hspace=0 vspace=0 border=0 frameborder=0 marginheight=0 marginwidth=0 w…
  • Error Line 381, Column 25: there is no attribute "vspace"
    <iframe hspace=0 vspace=0 border=0 frameborder=0 marginheight=0 marginwidth=0 w…

    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 381, Column 25: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe hspace=0 vspace=0 border=0 frameborder=0 marginheight=0 marginwidth=0 w…
  • Error Line 381, Column 34: there is no attribute "border"
    <iframe hspace=0 vspace=0 border=0 frameborder=0 marginheight=0 marginwidth=0 w…

    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 381, Column 34: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe hspace=0 vspace=0 border=0 frameborder=0 marginheight=0 marginwidth=0 w…
  • Error Line 381, Column 48: there is no attribute "frameborder"
    …space=0 vspace=0 border=0 frameborder=0 marginheight=0 marginwidth=0 width=158…

    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 381, Column 48: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …space=0 vspace=0 border=0 frameborder=0 marginheight=0 marginwidth=0 width=158…
  • Error Line 381, Column 63: there is no attribute "marginheight"
    …0 border=0 frameborder=0 marginheight=0 marginwidth=0 width=158 height=168 scr…

    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 381, Column 63: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …0 border=0 frameborder=0 marginheight=0 marginwidth=0 width=158 height=168 scr…
  • Error Line 381, Column 77: there is no attribute "marginwidth"
    …meborder=0 marginheight=0 marginwidth=0 width=158 height=168 scrolling=no allo…

    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 381, Column 77: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginheight=0 marginwidth=0 width=158 height=168 scrolling=no allo…
  • Error Line 381, Column 85: there is no attribute "width"
    …=0 marginheight=0 marginwidth=0 width=158 height=168 scrolling=no allowtranspa…

    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 381, Column 85: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=0 marginheight=0 marginwidth=0 width=158 height=168 scrolling=no allowtranspa…
  • Error Line 381, Column 96: there is no attribute "height"
    …ight=0 marginwidth=0 width=158 height=168 scrolling=no allowtransparency=true …

    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 381, Column 96: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ight=0 marginwidth=0 width=158 height=168 scrolling=no allowtransparency=true …
  • Error Line 381, Column 110: there is no attribute "scrolling"
    …idth=0 width=158 height=168 scrolling=no allowtransparency=true src=http://ads…

    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 381, Column 110: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …idth=0 width=158 height=168 scrolling=no allowtransparency=true src=http://ads…
  • Error Line 381, Column 131: there is no attribute "allowtransparency"
    …ht=168 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/ad…

    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 381, Column 131: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ht=168 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/ad…
  • Error Line 381, Column 140: there is no attribute "src"
    …rolling=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?…

    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 381, Column 140: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rolling=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?…
  • Error Line 381, Column 146: NET-enabling start-tag not immediately followed by null end-tag
    …g=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?adzone…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 381, Column 146: element "iframe" undefined
    …g=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?adzone…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 381, Column 201: end tag for element "iframe" which is not open
    …parency=true src=http://adserver.juicyads.com/adshow.php?adzone=24659></iframe>

    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 383, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

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

  • Info Line 383, Column 1: start tag was here
    <br>
  • Warning Line 394, Column 172: cannot generate system identifier for general entity "login"
    …ion.exoclick.com/ads.php?type=120x600&login=hpsweb&cat=2&search=&ad_title_colo…

    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 394, Column 172: general entity "login" not defined and no default entity
    …ion.exoclick.com/ads.php?type=120x600&login=hpsweb&cat=2&search=&ad_title_colo…

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

  • Warning Line 394, Column 177: reference not terminated by REFC delimiter
    …xoclick.com/ads.php?type=120x600&login=hpsweb&cat=2&search=&ad_title_color=000…

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

  • Warning Line 394, Column 177: reference to external entity in attribute value
    …xoclick.com/ads.php?type=120x600&login=hpsweb&cat=2&search=&ad_title_color=000…

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

  • Error Line 394, Column 177: reference to entity "login" for which no system identifier could be generated
    …xoclick.com/ads.php?type=120x600&login=hpsweb&cat=2&search=&ad_title_color=000…

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

  • Info Line 394, Column 171: entity was defined here
    …tion.exoclick.com/ads.php?type=120x600&login=hpsweb&cat=2&search=&ad_title_col…
  • Warning Line 394, Column 185: cannot generate system identifier for general entity "cat"
    …com/ads.php?type=120x600&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgco…

    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 394, Column 185: general entity "cat" not defined and no default entity
    …com/ads.php?type=120x600&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgco…

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

  • Warning Line 394, Column 188: reference not terminated by REFC delimiter
    …/ads.php?type=120x600&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor…

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

  • Warning Line 394, Column 188: reference to external entity in attribute value
    …/ads.php?type=120x600&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor…

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

  • Error Line 394, Column 188: reference to entity "cat" for which no system identifier could be generated
    …/ads.php?type=120x600&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor…

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

  • Info Line 394, Column 184: entity was defined here
    ….com/ads.php?type=120x600&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgc…
  • Warning Line 394, Column 191: cannot generate system identifier for general entity "search"
    …s.php?type=120x600&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FF…

    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 394, Column 191: general entity "search" not defined and no default entity
    …s.php?type=120x600&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FF…

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

  • Warning Line 394, Column 197: reference not terminated by REFC delimiter
    …type=120x600&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Warning Line 394, Column 197: reference to external entity in attribute value
    …type=120x600&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Error Line 394, Column 197: reference to entity "search" for which no system identifier could be generated
    …type=120x600&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Info Line 394, Column 190: entity was defined here
    …ds.php?type=120x600&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=F…
  • Warning Line 394, Column 199: cannot generate system identifier for general entity "ad_title_color"
    …pe=120x600&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&bor…

    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 394, Column 199: general entity "ad_title_color" not defined and no default entity
    …pe=120x600&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&bor…

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

  • Warning Line 394, Column 213: reference not terminated by REFC delimiter
    …in=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Warning Line 394, Column 213: reference to external entity in attribute value
    …in=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Error Line 394, Column 213: reference to entity "ad_title_color" for which no system identifier could be generated
    …in=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_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 394, Column 198: entity was defined here
    …ype=120x600&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&bo…
  • Warning Line 394, Column 221: cannot generate system identifier for general entity "bgcolor"
    …b&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000…

    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 394, Column 221: general entity "bgcolor" not defined and no default entity
    …b&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000…

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

  • Warning Line 394, Column 228: reference not terminated by REFC delimiter
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

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

  • Warning Line 394, Column 228: reference to external entity in attribute value
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

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

  • Error Line 394, Column 228: reference to entity "bgcolor" for which no system identifier could be generated
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

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

  • Info Line 394, Column 220: entity was defined here
    …eb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=00…
  • Warning Line 394, Column 236: cannot generate system identifier for general entity "border"
    …&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block…

    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 394, Column 236: general entity "border" not defined and no default entity
    …&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block…

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

  • Warning Line 394, Column 242: reference not terminated by REFC delimiter
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

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

  • Warning Line 394, Column 242: reference to external entity in attribute value
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

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

  • Error Line 394, Column 242: reference to entity "border" for which no system identifier could be generated
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

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

  • Info Line 394, Column 235: entity was defined here
    …=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&bloc…
  • Warning Line 394, Column 245: cannot generate system identifier for general entity "border_color"
    …_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords…

    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 394, Column 245: general entity "border_color" not defined and no default entity
    …_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords…

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

  • Warning Line 394, Column 257: reference not terminated by REFC delimiter
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

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

  • Warning Line 394, Column 257: reference to external entity in attribute value
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

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

  • Error Line 394, Column 257: reference to entity "border_color" for which no system identifier could be generated
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

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

  • Info Line 394, Column 244: entity was defined here
    …e_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keyword…
  • Warning Line 394, Column 265: cannot generate system identifier for general entity "font"
    …r=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=0000…

    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 394, Column 265: general entity "font" not defined and no default entity
    …r=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=0000…

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

  • Warning Line 394, Column 269: reference not terminated by REFC delimiter
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&a…

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

  • Warning Line 394, Column 269: reference to external entity in attribute value
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&a…

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

  • Error Line 394, Column 269: reference to entity "font" for which no system identifier could be generated
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&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 394, Column 264: entity was defined here
    …or=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000…
  • Warning Line 394, Column 271: cannot generate system identifier for general entity "block_keywords"
    …FF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&ad_…

    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 394, Column 271: general entity "block_keywords" not defined and no default entity
    …FF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&ad_…

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

  • Warning Line 394, Column 285: reference not terminated by REFC delimiter
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

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

  • Warning Line 394, Column 285: reference to external entity in attribute value
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

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

  • Error Line 394, Column 285: reference to entity "block_keywords" for which no system identifier could be generated
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

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

  • Info Line 394, Column 270: entity was defined here
    …FFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&ad…
  • Warning Line 394, Column 287: cannot generate system identifier for general entity "ad_text_color"
    …er_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=00800…

    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 394, Column 287: general entity "ad_text_color" not defined and no default entity
    …er_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=00800…

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

  • Warning Line 394, Column 300: reference not terminated by REFC delimiter
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

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

  • Warning Line 394, Column 300: reference to external entity in attribute value
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

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

  • Error Line 394, Column 300: reference to entity "ad_text_color" for which no system identifier could be generated
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&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 394, Column 286: entity was defined here
    …der_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=0080…
  • Warning Line 394, Column 308: cannot generate system identifier for general entity "ad_durl_color"
    …&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_o…

    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 394, Column 308: general entity "ad_durl_color" not defined and no default entity
    …&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_o…

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

  • Warning Line 394, Column 321: reference not terminated by REFC delimiter
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

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

  • Warning Line 394, Column 321: reference to external entity in attribute value
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

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

  • Error Line 394, Column 321: reference to entity "ad_durl_color" for which no system identifier could be generated
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

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

  • Info Line 394, Column 307: entity was defined here
    …=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_…
  • Warning Line 394, Column 329: cannot generate system identifier for general entity "adult"
    …ext_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idz…

    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 394, Column 329: general entity "adult" not defined and no default entity
    …ext_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idz…

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

  • Warning Line 394, Column 334: reference not terminated by REFC delimiter
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=4…

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

  • Warning Line 394, Column 334: reference to external entity in attribute value
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=4…

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

  • Error Line 394, Column 334: reference to entity "adult" for which no system identifier could be generated
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=4…

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

  • Info Line 394, Column 328: entity was defined here
    …text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&id…
  • Warning Line 394, Column 340: reference not terminated by REFC delimiter
    …00000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=414626&…

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

  • Warning Line 394, Column 342: cannot generate system identifier for general entity "text_only"
    …000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=414626&id…

    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 394, Column 342: general entity "text_only" not defined and no default entity
    …000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=414626&id…

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

  • Warning Line 394, Column 351: reference not terminated by REFC delimiter
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=414626&idsite=1020…

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

  • Warning Line 394, Column 351: reference to external entity in attribute value
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=414626&idsite=1020…

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

  • Error Line 394, Column 351: reference to entity "text_only" for which no system identifier could be generated
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=414626&idsite=1020…

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

  • Info Line 394, Column 341: entity was defined here
    …0000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=414626&i…
  • Warning Line 394, Column 354: cannot generate system identifier for general entity "show_thumb"
    …color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=414626&idsite=102070"…

    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 394, Column 354: general entity "show_thumb" not defined and no default entity
    …color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=414626&idsite=102070"…

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

  • Warning Line 394, Column 364: reference not terminated by REFC delimiter
    …00&adult=0&sub=&text_only=0&show_thumb=&idzone=414626&idsite=102070"></script>…

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

  • Warning Line 394, Column 364: reference to external entity in attribute value
    …00&adult=0&sub=&text_only=0&show_thumb=&idzone=414626&idsite=102070"></script>…

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

  • Error Line 394, Column 364: reference to entity "show_thumb" for which no system identifier could be generated
    …00&adult=0&sub=&text_only=0&show_thumb=&idzone=414626&idsite=102070"></script>…

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

  • Info Line 394, Column 353: entity was defined here
    …_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=414626&idsite=102070…
  • Warning Line 394, Column 366: cannot generate system identifier for general entity "idzone"
    …&adult=0&sub=&text_only=0&show_thumb=&idzone=414626&idsite=102070"></script><n…

    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 394, Column 366: general entity "idzone" not defined and no default entity
    …&adult=0&sub=&text_only=0&show_thumb=&idzone=414626&idsite=102070"></script><n…

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

  • Warning Line 394, Column 372: reference not terminated by REFC delimiter
    …=0&sub=&text_only=0&show_thumb=&idzone=414626&idsite=102070"></script><noscrip…

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

  • Warning Line 394, Column 372: reference to external entity in attribute value
    …=0&sub=&text_only=0&show_thumb=&idzone=414626&idsite=102070"></script><noscrip…

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

  • Error Line 394, Column 372: reference to entity "idzone" for which no system identifier could be generated
    …=0&sub=&text_only=0&show_thumb=&idzone=414626&idsite=102070"></script><noscrip…

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

  • Info Line 394, Column 365: entity was defined here
    …0&adult=0&sub=&text_only=0&show_thumb=&idzone=414626&idsite=102070"></script><…
  • Warning Line 394, Column 380: cannot generate system identifier for general entity "idsite"
    …text_only=0&show_thumb=&idzone=414626&idsite=102070"></script><noscript>Your b…

    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 394, Column 380: general entity "idsite" not defined and no default entity
    …text_only=0&show_thumb=&idzone=414626&idsite=102070"></script><noscript>Your b…

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

  • Warning Line 394, Column 386: reference not terminated by REFC delimiter
    …nly=0&show_thumb=&idzone=414626&idsite=102070"></script><noscript>Your browser…

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

  • Warning Line 394, Column 386: reference to external entity in attribute value
    …nly=0&show_thumb=&idzone=414626&idsite=102070"></script><noscript>Your browser…

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

  • Error Line 394, Column 386: reference to entity "idsite" for which no system identifier could be generated
    …nly=0&show_thumb=&idzone=414626&idsite=102070"></script><noscript>Your browser…

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

  • Info Line 394, Column 379: entity was defined here
    …&text_only=0&show_thumb=&idzone=414626&idsite=102070"></script><noscript>Your …
  • Error Line 394, Column 414: character data is not allowed here
    …626&idsite=102070"></script><noscript>Your browser does not support JavaScript…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Warning Line 397, Column 177: reference not terminated by REFC delimiter
    …xoclick.com/ads.php?type=120x600&login=hpsweb&cat=2&search=&ad_title_color=000…

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

  • Warning Line 397, Column 177: reference to external entity in attribute value
    …xoclick.com/ads.php?type=120x600&login=hpsweb&cat=2&search=&ad_title_color=000…

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

  • Error Line 397, Column 177: reference to entity "login" for which no system identifier could be generated
    …xoclick.com/ads.php?type=120x600&login=hpsweb&cat=2&search=&ad_title_color=000…

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

  • Info Line 394, Column 171: entity was defined here
    …tion.exoclick.com/ads.php?type=120x600&login=hpsweb&cat=2&search=&ad_title_col…
  • Warning Line 397, Column 188: reference not terminated by REFC delimiter
    …/ads.php?type=120x600&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor…

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

  • Warning Line 397, Column 188: reference to external entity in attribute value
    …/ads.php?type=120x600&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor…

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

  • Error Line 397, Column 188: reference to entity "cat" for which no system identifier could be generated
    …/ads.php?type=120x600&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor…

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

  • Info Line 394, Column 184: entity was defined here
    ….com/ads.php?type=120x600&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgc…
  • Warning Line 397, Column 197: reference not terminated by REFC delimiter
    …type=120x600&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Warning Line 397, Column 197: reference to external entity in attribute value
    …type=120x600&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Error Line 397, Column 197: reference to entity "search" for which no system identifier could be generated
    …type=120x600&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Info Line 394, Column 190: entity was defined here
    …ds.php?type=120x600&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=F…
  • Warning Line 397, Column 213: reference not terminated by REFC delimiter
    …in=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Warning Line 397, Column 213: reference to external entity in attribute value
    …in=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Error Line 397, Column 213: reference to entity "ad_title_color" for which no system identifier could be generated
    …in=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_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 394, Column 198: entity was defined here
    …ype=120x600&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&bo…
  • Warning Line 397, Column 228: reference not terminated by REFC delimiter
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

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

  • Warning Line 397, Column 228: reference to external entity in attribute value
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

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

  • Error Line 397, Column 228: reference to entity "bgcolor" for which no system identifier could be generated
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

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

  • Info Line 394, Column 220: entity was defined here
    …eb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=00…
  • Warning Line 397, Column 242: reference not terminated by REFC delimiter
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

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

  • Warning Line 397, Column 242: reference to external entity in attribute value
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

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

  • Error Line 397, Column 242: reference to entity "border" for which no system identifier could be generated
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

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

  • Info Line 394, Column 235: entity was defined here
    …=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&bloc…
  • Warning Line 397, Column 257: reference not terminated by REFC delimiter
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

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

  • Warning Line 397, Column 257: reference to external entity in attribute value
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

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

  • Error Line 397, Column 257: reference to entity "border_color" for which no system identifier could be generated
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

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

  • Info Line 394, Column 244: entity was defined here
    …e_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keyword…
  • Warning Line 397, Column 269: reference not terminated by REFC delimiter
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&a…

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

  • Warning Line 397, Column 269: reference to external entity in attribute value
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&a…

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

  • Error Line 397, Column 269: reference to entity "font" for which no system identifier could be generated
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&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 394, Column 264: entity was defined here
    …or=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000…
  • Warning Line 397, Column 285: reference not terminated by REFC delimiter
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

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

  • Warning Line 397, Column 285: reference to external entity in attribute value
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

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

  • Error Line 397, Column 285: reference to entity "block_keywords" for which no system identifier could be generated
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

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

  • Info Line 394, Column 270: entity was defined here
    …FFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&ad…
  • Warning Line 397, Column 300: reference not terminated by REFC delimiter
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

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

  • Warning Line 397, Column 300: reference to external entity in attribute value
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

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

  • Error Line 397, Column 300: reference to entity "ad_text_color" for which no system identifier could be generated
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&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 394, Column 286: entity was defined here
    …der_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=0080…
  • Warning Line 397, Column 321: reference not terminated by REFC delimiter
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

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

  • Warning Line 397, Column 321: reference to external entity in attribute value
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

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

  • Error Line 397, Column 321: reference to entity "ad_durl_color" for which no system identifier could be generated
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

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

  • Info Line 394, Column 307: entity was defined here
    …=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_…
  • Warning Line 397, Column 334: reference not terminated by REFC delimiter
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=4…

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

  • Warning Line 397, Column 334: reference to external entity in attribute value
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=4…

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

  • Error Line 397, Column 334: reference to entity "adult" for which no system identifier could be generated
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=4…

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

  • Info Line 394, Column 328: entity was defined here
    …text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&id…
  • Warning Line 397, Column 340: reference not terminated by REFC delimiter
    …00000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=414668&…

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

  • Warning Line 397, Column 351: reference not terminated by REFC delimiter
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=414668&idsite=1020…

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

  • Warning Line 397, Column 351: reference to external entity in attribute value
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=414668&idsite=1020…

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

  • Error Line 397, Column 351: reference to entity "text_only" for which no system identifier could be generated
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=414668&idsite=1020…

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

  • Info Line 394, Column 341: entity was defined here
    …0000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=414626&i…
  • Warning Line 397, Column 364: reference not terminated by REFC delimiter
    …00&adult=0&sub=&text_only=0&show_thumb=&idzone=414668&idsite=102070"></script>…

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

  • Warning Line 397, Column 364: reference to external entity in attribute value
    …00&adult=0&sub=&text_only=0&show_thumb=&idzone=414668&idsite=102070"></script>…

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

  • Error Line 397, Column 364: reference to entity "show_thumb" for which no system identifier could be generated
    …00&adult=0&sub=&text_only=0&show_thumb=&idzone=414668&idsite=102070"></script>…

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

  • Info Line 394, Column 353: entity was defined here
    …_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=414626&idsite=102070…
  • Warning Line 397, Column 372: reference not terminated by REFC delimiter
    …=0&sub=&text_only=0&show_thumb=&idzone=414668&idsite=102070"></script><noscrip…

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

  • Warning Line 397, Column 372: reference to external entity in attribute value
    …=0&sub=&text_only=0&show_thumb=&idzone=414668&idsite=102070"></script><noscrip…

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

  • Error Line 397, Column 372: reference to entity "idzone" for which no system identifier could be generated
    …=0&sub=&text_only=0&show_thumb=&idzone=414668&idsite=102070"></script><noscrip…

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

  • Info Line 394, Column 365: entity was defined here
    …0&adult=0&sub=&text_only=0&show_thumb=&idzone=414626&idsite=102070"></script><…
  • Warning Line 397, Column 386: reference not terminated by REFC delimiter
    …nly=0&show_thumb=&idzone=414668&idsite=102070"></script><noscript>Your browser…

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

  • Warning Line 397, Column 386: reference to external entity in attribute value
    …nly=0&show_thumb=&idzone=414668&idsite=102070"></script><noscript>Your browser…

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

  • Error Line 397, Column 386: reference to entity "idsite" for which no system identifier could be generated
    …nly=0&show_thumb=&idzone=414668&idsite=102070"></script><noscript>Your browser…

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

  • Info Line 394, Column 379: entity was defined here
    …&text_only=0&show_thumb=&idzone=414626&idsite=102070"></script><noscript>Your …
  • Error Line 397, Column 414: character data is not allowed here
    …668&idsite=102070"></script><noscript>Your browser does not support JavaScript…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 403, Column 59: end tag for "br" omitted, but OMITTAG NO was specified
    		<div style='clear:both;'><br style="font-size:5px"></div>

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

  • Info Line 403, Column 28: start tag was here
    		<div style='clear:both;'><br style="font-size:5px"></div>
  • Error Line 406, Column 6: end tag for "br" omitted, but OMITTAG NO was specified
    	<br>

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

  • Info Line 406, Column 2: start tag was here
    	<br>
  • Warning Line 421, Column 151: reference not terminated by REFC delimiter
    …xoclick.com/ads.php?type=300x250&login=hpsweb&cat=2&search=&ad_title_color=000…

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

  • Warning Line 421, Column 151: reference to external entity in attribute value
    …xoclick.com/ads.php?type=300x250&login=hpsweb&cat=2&search=&ad_title_color=000…

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

  • Error Line 421, Column 151: reference to entity "login" for which no system identifier could be generated
    …xoclick.com/ads.php?type=300x250&login=hpsweb&cat=2&search=&ad_title_color=000…

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

  • Info Line 394, Column 171: entity was defined here
    …tion.exoclick.com/ads.php?type=120x600&login=hpsweb&cat=2&search=&ad_title_col…
  • Warning Line 421, Column 162: reference not terminated by REFC delimiter
    …/ads.php?type=300x250&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor…

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

  • Warning Line 421, Column 162: reference to external entity in attribute value
    …/ads.php?type=300x250&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor…

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

  • Error Line 421, Column 162: reference to entity "cat" for which no system identifier could be generated
    …/ads.php?type=300x250&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor…

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

  • Info Line 394, Column 184: entity was defined here
    ….com/ads.php?type=120x600&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgc…
  • Warning Line 421, Column 171: reference not terminated by REFC delimiter
    …type=300x250&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Warning Line 421, Column 171: reference to external entity in attribute value
    …type=300x250&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Error Line 421, Column 171: reference to entity "search" for which no system identifier could be generated
    …type=300x250&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Info Line 394, Column 190: entity was defined here
    …ds.php?type=120x600&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=F…
  • Warning Line 421, Column 187: reference not terminated by REFC delimiter
    …in=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Warning Line 421, Column 187: reference to external entity in attribute value
    …in=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Error Line 421, Column 187: reference to entity "ad_title_color" for which no system identifier could be generated
    …in=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_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 394, Column 198: entity was defined here
    …ype=120x600&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&bo…
  • Warning Line 421, Column 202: reference not terminated by REFC delimiter
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

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

  • Warning Line 421, Column 202: reference to external entity in attribute value
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

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

  • Error Line 421, Column 202: reference to entity "bgcolor" for which no system identifier could be generated
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

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

  • Info Line 394, Column 220: entity was defined here
    …eb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=00…
  • Warning Line 421, Column 216: reference not terminated by REFC delimiter
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

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

  • Warning Line 421, Column 216: reference to external entity in attribute value
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

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

  • Error Line 421, Column 216: reference to entity "border" for which no system identifier could be generated
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

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

  • Info Line 394, Column 235: entity was defined here
    …=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&bloc…
  • Warning Line 421, Column 231: reference not terminated by REFC delimiter
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

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

  • Warning Line 421, Column 231: reference to external entity in attribute value
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

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

  • Error Line 421, Column 231: reference to entity "border_color" for which no system identifier could be generated
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

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

  • Info Line 394, Column 244: entity was defined here
    …e_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keyword…
  • Warning Line 421, Column 243: reference not terminated by REFC delimiter
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&a…

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

  • Warning Line 421, Column 243: reference to external entity in attribute value
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&a…

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

  • Error Line 421, Column 243: reference to entity "font" for which no system identifier could be generated
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&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 394, Column 264: entity was defined here
    …or=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000…
  • Warning Line 421, Column 259: reference not terminated by REFC delimiter
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

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

  • Warning Line 421, Column 259: reference to external entity in attribute value
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

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

  • Error Line 421, Column 259: reference to entity "block_keywords" for which no system identifier could be generated
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

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

  • Info Line 394, Column 270: entity was defined here
    …FFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&ad…
  • Warning Line 421, Column 274: reference not terminated by REFC delimiter
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

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

  • Warning Line 421, Column 274: reference to external entity in attribute value
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

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

  • Error Line 421, Column 274: reference to entity "ad_text_color" for which no system identifier could be generated
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&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 394, Column 286: entity was defined here
    …der_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=0080…
  • Warning Line 421, Column 295: reference not terminated by REFC delimiter
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

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

  • Warning Line 421, Column 295: reference to external entity in attribute value
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

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

  • Error Line 421, Column 295: reference to entity "ad_durl_color" for which no system identifier could be generated
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

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

  • Info Line 394, Column 307: entity was defined here
    …=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_…
  • Warning Line 421, Column 308: reference not terminated by REFC delimiter
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=4…

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

  • Warning Line 421, Column 308: reference to external entity in attribute value
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=4…

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

  • Error Line 421, Column 308: reference to entity "adult" for which no system identifier could be generated
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=4…

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

  • Info Line 394, Column 328: entity was defined here
    …text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&id…
  • Warning Line 421, Column 314: reference not terminated by REFC delimiter
    …00000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=414628&…

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

  • Warning Line 421, Column 325: reference not terminated by REFC delimiter
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=414628&idsite=1020…

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

  • Warning Line 421, Column 325: reference to external entity in attribute value
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=414628&idsite=1020…

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

  • Error Line 421, Column 325: reference to entity "text_only" for which no system identifier could be generated
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=414628&idsite=1020…

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

  • Info Line 394, Column 341: entity was defined here
    …0000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=414626&i…
  • Warning Line 421, Column 338: reference not terminated by REFC delimiter
    …00&adult=0&sub=&text_only=0&show_thumb=&idzone=414628&idsite=102070"></script>…

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

  • Warning Line 421, Column 338: reference to external entity in attribute value
    …00&adult=0&sub=&text_only=0&show_thumb=&idzone=414628&idsite=102070"></script>…

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

  • Error Line 421, Column 338: reference to entity "show_thumb" for which no system identifier could be generated
    …00&adult=0&sub=&text_only=0&show_thumb=&idzone=414628&idsite=102070"></script>…

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

  • Info Line 394, Column 353: entity was defined here
    …_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=414626&idsite=102070…
  • Warning Line 421, Column 346: reference not terminated by REFC delimiter
    …=0&sub=&text_only=0&show_thumb=&idzone=414628&idsite=102070"></script><noscrip…

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

  • Warning Line 421, Column 346: reference to external entity in attribute value
    …=0&sub=&text_only=0&show_thumb=&idzone=414628&idsite=102070"></script><noscrip…

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

  • Error Line 421, Column 346: reference to entity "idzone" for which no system identifier could be generated
    …=0&sub=&text_only=0&show_thumb=&idzone=414628&idsite=102070"></script><noscrip…

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

  • Info Line 394, Column 365: entity was defined here
    …0&adult=0&sub=&text_only=0&show_thumb=&idzone=414626&idsite=102070"></script><…
  • Warning Line 421, Column 360: reference not terminated by REFC delimiter
    …nly=0&show_thumb=&idzone=414628&idsite=102070"></script><noscript>Your browser…

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

  • Warning Line 421, Column 360: reference to external entity in attribute value
    …nly=0&show_thumb=&idzone=414628&idsite=102070"></script><noscript>Your browser…

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

  • Error Line 421, Column 360: reference to entity "idsite" for which no system identifier could be generated
    …nly=0&show_thumb=&idzone=414628&idsite=102070"></script><noscript>Your browser…

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

  • Info Line 394, Column 379: entity was defined here
    …&text_only=0&show_thumb=&idzone=414626&idsite=102070"></script><noscript>Your …
  • Error Line 421, Column 388: character data is not allowed here
    …628&idsite=102070"></script><noscript>Your browser does not support JavaScript…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Warning Line 422, Column 151: reference not terminated by REFC delimiter
    …xoclick.com/ads.php?type=300x250&login=hpsweb&cat=2&search=&ad_title_color=000…

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

  • Warning Line 422, Column 151: reference to external entity in attribute value
    …xoclick.com/ads.php?type=300x250&login=hpsweb&cat=2&search=&ad_title_color=000…

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

  • Error Line 422, Column 151: reference to entity "login" for which no system identifier could be generated
    …xoclick.com/ads.php?type=300x250&login=hpsweb&cat=2&search=&ad_title_color=000…

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

  • Info Line 394, Column 171: entity was defined here
    …tion.exoclick.com/ads.php?type=120x600&login=hpsweb&cat=2&search=&ad_title_col…
  • Warning Line 422, Column 162: reference not terminated by REFC delimiter
    …/ads.php?type=300x250&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor…

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

  • Warning Line 422, Column 162: reference to external entity in attribute value
    …/ads.php?type=300x250&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor…

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

  • Error Line 422, Column 162: reference to entity "cat" for which no system identifier could be generated
    …/ads.php?type=300x250&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor…

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

  • Info Line 394, Column 184: entity was defined here
    ….com/ads.php?type=120x600&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgc…
  • Warning Line 422, Column 171: reference not terminated by REFC delimiter
    …type=300x250&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Warning Line 422, Column 171: reference to external entity in attribute value
    …type=300x250&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Error Line 422, Column 171: reference to entity "search" for which no system identifier could be generated
    …type=300x250&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Info Line 394, Column 190: entity was defined here
    …ds.php?type=120x600&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=F…
  • Warning Line 422, Column 187: reference not terminated by REFC delimiter
    …in=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Warning Line 422, Column 187: reference to external entity in attribute value
    …in=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Error Line 422, Column 187: reference to entity "ad_title_color" for which no system identifier could be generated
    …in=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_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 394, Column 198: entity was defined here
    …ype=120x600&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&bo…
  • Warning Line 422, Column 202: reference not terminated by REFC delimiter
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

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

  • Warning Line 422, Column 202: reference to external entity in attribute value
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

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

  • Error Line 422, Column 202: reference to entity "bgcolor" for which no system identifier could be generated
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

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

  • Info Line 394, Column 220: entity was defined here
    …eb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=00…
  • Warning Line 422, Column 216: reference not terminated by REFC delimiter
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

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

  • Warning Line 422, Column 216: reference to external entity in attribute value
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

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

  • Error Line 422, Column 216: reference to entity "border" for which no system identifier could be generated
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

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

  • Info Line 394, Column 235: entity was defined here
    …=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&bloc…
  • Warning Line 422, Column 231: reference not terminated by REFC delimiter
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

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

  • Warning Line 422, Column 231: reference to external entity in attribute value
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

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

  • Error Line 422, Column 231: reference to entity "border_color" for which no system identifier could be generated
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

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

  • Info Line 394, Column 244: entity was defined here
    …e_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keyword…
  • Warning Line 422, Column 243: reference not terminated by REFC delimiter
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&a…

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

  • Warning Line 422, Column 243: reference to external entity in attribute value
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&a…

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

  • Error Line 422, Column 243: reference to entity "font" for which no system identifier could be generated
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&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 394, Column 264: entity was defined here
    …or=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000…
  • Warning Line 422, Column 259: reference not terminated by REFC delimiter
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

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

  • Warning Line 422, Column 259: reference to external entity in attribute value
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

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

  • Error Line 422, Column 259: reference to entity "block_keywords" for which no system identifier could be generated
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

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

  • Info Line 394, Column 270: entity was defined here
    …FFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&ad…
  • Warning Line 422, Column 274: reference not terminated by REFC delimiter
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

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

  • Warning Line 422, Column 274: reference to external entity in attribute value
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

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

  • Error Line 422, Column 274: reference to entity "ad_text_color" for which no system identifier could be generated
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&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 394, Column 286: entity was defined here
    …der_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=0080…
  • Warning Line 422, Column 295: reference not terminated by REFC delimiter
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

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

  • Warning Line 422, Column 295: reference to external entity in attribute value
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

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

  • Error Line 422, Column 295: reference to entity "ad_durl_color" for which no system identifier could be generated
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

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

  • Info Line 394, Column 307: entity was defined here
    …=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_…
  • Warning Line 422, Column 308: reference not terminated by REFC delimiter
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=4…

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

  • Warning Line 422, Column 308: reference to external entity in attribute value
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=4…

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

  • Error Line 422, Column 308: reference to entity "adult" for which no system identifier could be generated
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=4…

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

  • Info Line 394, Column 328: entity was defined here
    …text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&id…
  • Warning Line 422, Column 314: reference not terminated by REFC delimiter
    …00000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=414630&…

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

  • Warning Line 422, Column 325: reference not terminated by REFC delimiter
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=414630&idsite=1020…

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

  • Warning Line 422, Column 325: reference to external entity in attribute value
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=414630&idsite=1020…

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

  • Error Line 422, Column 325: reference to entity "text_only" for which no system identifier could be generated
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=414630&idsite=1020…

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

  • Info Line 394, Column 341: entity was defined here
    …0000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=414626&i…
  • Warning Line 422, Column 338: reference not terminated by REFC delimiter
    …00&adult=0&sub=&text_only=0&show_thumb=&idzone=414630&idsite=102070"></script>…

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

  • Warning Line 422, Column 338: reference to external entity in attribute value
    …00&adult=0&sub=&text_only=0&show_thumb=&idzone=414630&idsite=102070"></script>…

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

  • Error Line 422, Column 338: reference to entity "show_thumb" for which no system identifier could be generated
    …00&adult=0&sub=&text_only=0&show_thumb=&idzone=414630&idsite=102070"></script>…

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

  • Info Line 394, Column 353: entity was defined here
    …_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=414626&idsite=102070…
  • Warning Line 422, Column 346: reference not terminated by REFC delimiter
    …=0&sub=&text_only=0&show_thumb=&idzone=414630&idsite=102070"></script><noscrip…

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

  • Warning Line 422, Column 346: reference to external entity in attribute value
    …=0&sub=&text_only=0&show_thumb=&idzone=414630&idsite=102070"></script><noscrip…

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

  • Error Line 422, Column 346: reference to entity "idzone" for which no system identifier could be generated
    …=0&sub=&text_only=0&show_thumb=&idzone=414630&idsite=102070"></script><noscrip…

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

  • Info Line 394, Column 365: entity was defined here
    …0&adult=0&sub=&text_only=0&show_thumb=&idzone=414626&idsite=102070"></script><…
  • Warning Line 422, Column 360: reference not terminated by REFC delimiter
    …nly=0&show_thumb=&idzone=414630&idsite=102070"></script><noscript>Your browser…

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

  • Warning Line 422, Column 360: reference to external entity in attribute value
    …nly=0&show_thumb=&idzone=414630&idsite=102070"></script><noscript>Your browser…

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

  • Error Line 422, Column 360: reference to entity "idsite" for which no system identifier could be generated
    …nly=0&show_thumb=&idzone=414630&idsite=102070"></script><noscript>Your browser…

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

  • Info Line 394, Column 379: entity was defined here
    …&text_only=0&show_thumb=&idzone=414626&idsite=102070"></script><noscript>Your …
  • Error Line 422, Column 388: character data is not allowed here
    …630&idsite=102070"></script><noscript>Your browser does not support JavaScript…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Warning Line 423, Column 151: reference not terminated by REFC delimiter
    …xoclick.com/ads.php?type=300x250&login=hpsweb&cat=2&search=&ad_title_color=000…

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

  • Warning Line 423, Column 151: reference to external entity in attribute value
    …xoclick.com/ads.php?type=300x250&login=hpsweb&cat=2&search=&ad_title_color=000…

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

  • Error Line 423, Column 151: reference to entity "login" for which no system identifier could be generated
    …xoclick.com/ads.php?type=300x250&login=hpsweb&cat=2&search=&ad_title_color=000…

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

  • Info Line 394, Column 171: entity was defined here
    …tion.exoclick.com/ads.php?type=120x600&login=hpsweb&cat=2&search=&ad_title_col…
  • Warning Line 423, Column 162: reference not terminated by REFC delimiter
    …/ads.php?type=300x250&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor…

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

  • Warning Line 423, Column 162: reference to external entity in attribute value
    …/ads.php?type=300x250&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor…

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

  • Error Line 423, Column 162: reference to entity "cat" for which no system identifier could be generated
    …/ads.php?type=300x250&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor…

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

  • Info Line 394, Column 184: entity was defined here
    ….com/ads.php?type=120x600&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgc…
  • Warning Line 423, Column 171: reference not terminated by REFC delimiter
    …type=300x250&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Warning Line 423, Column 171: reference to external entity in attribute value
    …type=300x250&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Error Line 423, Column 171: reference to entity "search" for which no system identifier could be generated
    …type=300x250&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Info Line 394, Column 190: entity was defined here
    …ds.php?type=120x600&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=F…
  • Warning Line 423, Column 187: reference not terminated by REFC delimiter
    …in=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Warning Line 423, Column 187: reference to external entity in attribute value
    …in=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Error Line 423, Column 187: reference to entity "ad_title_color" for which no system identifier could be generated
    …in=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_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 394, Column 198: entity was defined here
    …ype=120x600&login=hpsweb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&bo…
  • Warning Line 423, Column 202: reference not terminated by REFC delimiter
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

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

  • Warning Line 423, Column 202: reference to external entity in attribute value
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

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

  • Error Line 423, Column 202: reference to entity "bgcolor" for which no system identifier could be generated
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

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

  • Info Line 394, Column 220: entity was defined here
    …eb&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=00…
  • Warning Line 423, Column 216: reference not terminated by REFC delimiter
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

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

  • Warning Line 423, Column 216: reference to external entity in attribute value
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

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

  • Error Line 423, Column 216: reference to entity "border" for which no system identifier could be generated
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

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

  • Info Line 394, Column 235: entity was defined here
    …=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&bloc…
  • Warning Line 423, Column 231: reference not terminated by REFC delimiter
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

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

  • Warning Line 423, Column 231: reference to external entity in attribute value
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

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

  • Error Line 423, Column 231: reference to entity "border_color" for which no system identifier could be generated
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

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

  • Info Line 394, Column 244: entity was defined here
    …e_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keyword…
  • Warning Line 423, Column 243: reference not terminated by REFC delimiter
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&a…

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

  • Warning Line 423, Column 243: reference to external entity in attribute value
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&a…

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

  • Error Line 423, Column 243: reference to entity "font" for which no system identifier could be generated
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&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 394, Column 264: entity was defined here
    …or=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000…
  • Warning Line 423, Column 259: reference not terminated by REFC delimiter
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

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

  • Warning Line 423, Column 259: reference to external entity in attribute value
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

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

  • Error Line 423, Column 259: reference to entity "block_keywords" for which no system identifier could be generated
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

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

  • Info Line 394, Column 270: entity was defined here
    …FFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&ad…
  • Warning Line 423, Column 274: reference not terminated by REFC delimiter
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

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

  • Warning Line 423, Column 274: reference to external entity in attribute value
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

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

  • Error Line 423, Column 274: reference to entity "ad_text_color" for which no system identifier could be generated
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&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 394, Column 286: entity was defined here
    …der_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=0080…
  • Warning Line 423, Column 295: reference not terminated by REFC delimiter
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

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

  • Warning Line 423, Column 295: reference to external entity in attribute value
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

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

  • Error Line 423, Column 295: reference to entity "ad_durl_color" for which no system identifier could be generated
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

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

  • Info Line 394, Column 307: entity was defined here
    …=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_…
  • Warning Line 423, Column 308: reference not terminated by REFC delimiter
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=4…

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

  • Warning Line 423, Column 308: reference to external entity in attribute value
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=4…

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

  • Error Line 423, Column 308: reference to entity "adult" for which no system identifier could be generated
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=4…

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

  • Info Line 394, Column 328: entity was defined here
    …text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&id…
  • Warning Line 423, Column 314: reference not terminated by REFC delimiter
    …00000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=414632&…

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

  • Warning Line 423, Column 325: reference not terminated by REFC delimiter
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=414632&idsite=1020…

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

  • Warning Line 423, Column 325: reference to external entity in attribute value
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=414632&idsite=1020…

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

  • Error Line 423, Column 325: reference to entity "text_only" for which no system identifier could be generated
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=414632&idsite=1020…

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

  • Info Line 394, Column 341: entity was defined here
    …0000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=414626&i…
  • Warning Line 423, Column 338: reference not terminated by REFC delimiter
    …00&adult=0&sub=&text_only=0&show_thumb=&idzone=414632&idsite=102070"></script>…

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

  • Warning Line 423, Column 338: reference to external entity in attribute value
    …00&adult=0&sub=&text_only=0&show_thumb=&idzone=414632&idsite=102070"></script>…

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

  • Error Line 423, Column 338: reference to entity "show_thumb" for which no system identifier could be generated
    …00&adult=0&sub=&text_only=0&show_thumb=&idzone=414632&idsite=102070"></script>…

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

  • Info Line 394, Column 353: entity was defined here
    …_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=414626&idsite=102070…
  • Warning Line 423, Column 346: reference not terminated by REFC delimiter
    …=0&sub=&text_only=0&show_thumb=&idzone=414632&idsite=102070"></script><noscrip…

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

  • Warning Line 423, Column 346: reference to external entity in attribute value
    …=0&sub=&text_only=0&show_thumb=&idzone=414632&idsite=102070"></script><noscrip…

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

  • Error Line 423, Column 346: reference to entity "idzone" for which no system identifier could be generated
    …=0&sub=&text_only=0&show_thumb=&idzone=414632&idsite=102070"></script><noscrip…

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

  • Info Line 394, Column 365: entity was defined here
    …0&adult=0&sub=&text_only=0&show_thumb=&idzone=414626&idsite=102070"></script><…
  • Warning Line 423, Column 360: reference not terminated by REFC delimiter
    …nly=0&show_thumb=&idzone=414632&idsite=102070"></script><noscript>Your browser…

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

  • Warning Line 423, Column 360: reference to external entity in attribute value
    …nly=0&show_thumb=&idzone=414632&idsite=102070"></script><noscript>Your browser…

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

  • Error Line 423, Column 360: reference to entity "idsite" for which no system identifier could be generated
    …nly=0&show_thumb=&idzone=414632&idsite=102070"></script><noscript>Your browser…

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

  • Info Line 394, Column 379: entity was defined here
    …&text_only=0&show_thumb=&idzone=414626&idsite=102070"></script><noscript>Your …
  • Error Line 423, Column 388: character data is not allowed here
    …632&idsite=102070"></script><noscript>Your browser does not support JavaScript…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Warning Line 433, Column 92: reference not terminated by REFC delimiter
    …n.exoclick.com/splash.php?cat=2&idsite=102070&idzone=414634&login=hpsweb&type=…

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

  • Warning Line 433, Column 92: reference to external entity in attribute value
    …n.exoclick.com/splash.php?cat=2&idsite=102070&idzone=414634&login=hpsweb&type=…

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

  • Error Line 433, Column 92: reference to entity "idsite" for which no system identifier could be generated
    …n.exoclick.com/splash.php?cat=2&idsite=102070&idzone=414634&login=hpsweb&type=…

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

  • Info Line 394, Column 379: entity was defined here
    …&text_only=0&show_thumb=&idzone=414626&idsite=102070"></script><noscript>Your …
  • Warning Line 433, Column 106: reference not terminated by REFC delimiter
    …com/splash.php?cat=2&idsite=102070&idzone=414634&login=hpsweb&type=3"></script>

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

  • Warning Line 433, Column 106: reference to external entity in attribute value
    …com/splash.php?cat=2&idsite=102070&idzone=414634&login=hpsweb&type=3"></script>

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

  • Error Line 433, Column 106: reference to entity "idzone" for which no system identifier could be generated
    …com/splash.php?cat=2&idsite=102070&idzone=414634&login=hpsweb&type=3"></script>

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

  • Info Line 394, Column 365: entity was defined here
    …0&adult=0&sub=&text_only=0&show_thumb=&idzone=414626&idsite=102070"></script><…
  • Warning Line 433, Column 119: reference not terminated by REFC delimiter
    …com/splash.php?cat=2&idsite=102070&idzone=414634&login=hpsweb&type=3"></script>

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

  • Warning Line 433, Column 119: reference to external entity in attribute value
    …com/splash.php?cat=2&idsite=102070&idzone=414634&login=hpsweb&type=3"></script>

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

  • Error Line 433, Column 119: reference to entity "login" for which no system identifier could be generated
    …com/splash.php?cat=2&idsite=102070&idzone=414634&login=hpsweb&type=3"></script>

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

  • Info Line 394, Column 171: entity was defined here
    …tion.exoclick.com/ads.php?type=120x600&login=hpsweb&cat=2&search=&ad_title_col…
  • Warning Line 433, Column 127: cannot generate system identifier for general entity "type"
    …com/splash.php?cat=2&idsite=102070&idzone=414634&login=hpsweb&type=3"></script>

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

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

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

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

  • Error Line 433, Column 127: general entity "type" not defined and no default entity
    …com/splash.php?cat=2&idsite=102070&idzone=414634&login=hpsweb&type=3"></script>

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

  • Warning Line 433, Column 131: reference not terminated by REFC delimiter
    …com/splash.php?cat=2&idsite=102070&idzone=414634&login=hpsweb&type=3"></script>

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

  • Warning Line 433, Column 131: reference to external entity in attribute value
    …com/splash.php?cat=2&idsite=102070&idzone=414634&login=hpsweb&type=3"></script>

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

  • Error Line 433, Column 131: reference to entity "type" for which no system identifier could be generated
    …com/splash.php?cat=2&idsite=102070&idzone=414634&login=hpsweb&type=3"></script>

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

  • Info Line 433, Column 126: entity was defined here
    …com/splash.php?cat=2&idsite=102070&idzone=414634&login=hpsweb&type=3"></script>
  • Error Line 438, Column 6: end tag for "br" omitted, but OMITTAG NO was specified
    	<br><br>

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

  • Info Line 438, Column 2: start tag was here
    	<br><br>
  • Error Line 438, Column 10: end tag for "br" omitted, but OMITTAG NO was specified
    	<br><br>

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

  • Info Line 438, Column 6: start tag was here
    	<br><br>
  • Error Line 440, Column 68: element "font" undefined
    …:15px;font-family:arial;color:#333333">If you have any questions, suggestions,…

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

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

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

  • Info Line 443, Column 2: start tag was here
    	<br>
  • Error Line 445, Column 30: element "font" undefined
    		<font style="color:#555555">2008-2012 <b>Hot Porn Show</b> - The best free po…

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

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

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

  • Info Line 448, Column 1: start tag was here
    <br>
  • Error Line 450, Column 6: end tag for element "div" which is not open
    </div><!--main div-->

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

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

  • Error Line 462, Column 8: no document element
    </HTML>

Visitor Analysis

Daily Visitor
  • 19.833 visits

In Page Analysis