If are burning to watch exclusive sex tube videos, then koktube.com is here to help you. We have done much work to find the best exclusive porn movies from all over the Net ...

koktube.com
  • Domain Name
    koktube.com
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #151534
  • Page Size
    106.3 KB
  • Ip Address
    46.229.163.191
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 183 JPG, 0 PNG

Website Meta Analysis

  • Title
    KOK TUBE PORN, FREE SEX TUBE, LONG XXX VIDEOS, HD FUCK MOVIES
  • Meta Keyword
    kok tube, sex tube, porn tube, free porn, anal videos, amateur fuck, hardcore clips, xhamster, pornhub, asian films
  • Meta Description
    If are burning to watch exclusive sex tube videos, then koktube.com is here to help you. We have done much work to find the best exclusive porn movies from all over the Net for you to get real pleasure while watching!

Technical Analysis

  • Webserver
    nginx/1.4.1
  • Ip Address
    46.229.163.191
  • Domain Age
    4 Years, 10 Months, 29 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx/1.4.1
  • date: Wed, 17 Jul 2013 17:40:08 GMT
  • content-type: text/html
  • connection: keep-alive
  • vary: Accept-Encoding
  • expires: Wed, 17 Jul 2013 17:41:08 GMT
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain name: koktube.com

Administrative Contact:
Namecheap.com
Namecheap.com Namecheap.com ( email )
+1.5555555555
Fax: +1.5555555555
8939 S. Sepulveda Blvd. #110 - 732
Westchester, CA 90045
US

Technical Contact:
Namecheap.com
Namecheap.com Namecheap.com ( email )
+1.5555555555
Fax: +1.5555555555
8939 S. Sepulveda Blvd. #110 - 732
Westchester, CA 90045
US

Registrant Contact:
Namecheap.com
Namecheap.com Namecheap.com ()

Fax:
8939 S. Sepulveda Blvd. #110 - 732
Westchester, CA 90045
US

Status: Locked

Name Servers:
NS1.FUCKEZ.COM
NS2.FUCKEZ.COM

Creation date: 12 Sep 2008 09:52:00
Expiration date: 12 Sep 2013 09:52:00

DNS Analysis


DNS servers
ns1.fuckez.com [46.229.169.84]
ns2.fuckez.com [46.229.163.191]


DNS Records

Answer records
koktube.com SOA
server: fuckez.com
email: dns@fuckez.com
serial: 2013030502
refresh: 28800
retry: 7200
expire: 604800
minimum ttl: 86400
86400s
koktube.com NS  ns1.fuckez.com 86400s
koktube.com NS  ns2.fuckez.com 86400s
koktube.com MX
preference: 10
exchange: mx1.advancedhosters.com
86400s
koktube.com MX
preference: 20
exchange: mx2.advancedhosters.com
86400s
koktube.com A 46.229.163.191 86400s

Authority records

Additional records
ns1.fuckez.com A 46.229.169.84 86400s
ns2.fuckez.com A 46.229.163.191 86400s

IP 46.229.163.191 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    NA
  • Continent Code
    38° North
  • Latitude
    97.
  • Longitude
  • No whois ip data for 46.229.163.191

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 104 Errors
  • 101 Warnings
Ratio Text/Html
  • 0.7684609092830688
Message Error
  • Error Line 14, Column 18: there is no attribute "language"
    <script language='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 14, Column 30: required attribute "type" not specified
    <script language='JavaScript'><!--

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

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

  • Error Line 29, Column 14: there is no attribute "target"
    <base target="_blank">

    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 29, Column 22: required attribute "href" not specified
    <base target="_blank">

    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 29, Column 23: end tag for "base" omitted, but OMITTAG NO was specified
    <base target="_blank">

    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 29, Column 1: start tag was here
    <base target="_blank">
  • Error Line 56, Column 287: element "u" undefined
    …ing. Stay with us for more explicit <u>sex videos</u> that appear on the site …

    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 71, Column 46: document type does not allow element "form" here; missing one of "th", "td" start-tag
    …                     	<form action="/"><td style="vertical-align:top;"><input …

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

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

  • Error Line 71, Column 78: document type does not allow element "td" here
    …on="/"><td style="vertical-align:top;"><input type="hidden" name="ps" value="1…

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

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

  • Error Line 71, Column 120: end tag for "input" omitted, but OMITTAG NO was specified
    …put type="hidden" name="ps" value="1"><input type="text" name="s" value="" cla…

    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 71, Column 79: start tag was here
    …n="/"><td style="vertical-align:top;"><input type="hidden" name="ps" value="1"…
  • Error Line 72, Column 36: document type does not allow element "td" here
                                    <td><input type="image" src="/img/search-but.pn…

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

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

  • Error Line 73, Column 33: end tag for "tr" which is not finished
                                </tr>

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

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

  • Error Line 96, Column 77: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …option value="/f/0/0/0/0/1/1" selected>-all ages-</option><option value="/f/18…

    "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 98, Column 86: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …option value="/f/0/0/0/0/1/1" selected>-all countries-</option><option value="…

    "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 1474, Column 77: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …option value="/f/0/0/0/0/1/1" selected>-all ages-</option><option value="/f/18…

    "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 1476, Column 86: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …option value="/f/0/0/0/0/1/1" selected>-all countries-</option><option value="…

    "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 1490, Column 8: element "center" undefined
    <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 1491, Column 13: there is no attribute "src"
    <iframe src="http://koktube.com/ero.html" marginheight="0" marginwidth="0" 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 1491, Column 56: there is no attribute "marginheight"
    …://koktube.com/ero.html" marginheight="0" marginwidth="0" allowtransparency="t…

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

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

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

  • Error Line 1491, Column 72: there is no attribute "marginwidth"
    …ro.html" marginheight="0" marginwidth="0" allowtransparency="true" scrolling="…

    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 1491, Column 94: there is no attribute "allowtransparency"
    …"0" marginwidth="0" allowtransparency="true" scrolling="no" frameborder="0" st…

    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 1491, Column 111: there is no attribute "scrolling"
    …0" allowtransparency="true" scrolling="no" frameborder="0" style="background-c…

    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 1491, Column 128: there is no attribute "frameborder"
    …ncy="true" scrolling="no" frameborder="0" style="background-color:transparent"…

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

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

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

  • Error Line 1491, Column 138: there is no attribute "style"
    … scrolling="no" frameborder="0" style="background-color:transparent" scrolling…

    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 1491, Column 179: duplicate specification of attribute "scrolling"
    …ckground-color:transparent" scrolling="no" frameborder="0" width="926" height=…

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1491, Column 196: duplicate specification of attribute "frameborder"
    …:transparent" scrolling="no" frameborder="0" width="926" height="270"></iframe>

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1491, Column 206: there is no attribute "width"
    …:transparent" scrolling="no" frameborder="0" width="926" height="270"></iframe>

    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 1491, Column 219: there is no attribute "height"
    …:transparent" scrolling="no" frameborder="0" width="926" height="270"></iframe>

    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 1491, Column 224: element "iframe" undefined
    …:transparent" scrolling="no" frameborder="0" width="926" height="270"></iframe>

    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 1502, Column 47: document type does not allow element "form" here; assuming missing "li" start-tag
            	<ul class="search l"><form action="/">
  • Error Line 1503, Column 41: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
                    <li class="search-title">Search</li>

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

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

  • Error Line 1504, Column 41: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    …              <li class="search-input"><input type="hidden" name="ps" value="1…

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

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

  • Error Line 1504, Column 83: end tag for "input" omitted, but OMITTAG NO was specified
    …put type="hidden" name="ps" value="1"><input type="text" name="s" value=""/></…

    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 1504, Column 42: start tag was here
    …             <li class="search-input"><input type="hidden" name="ps" value="1"…
  • Error Line 1505, Column 39: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
                    <li class="search-but"><input type="image" src="/img/search-but…

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

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

  • Error Line 1506, Column 24: end tag for "li" omitted, but OMITTAG NO was specified
                </form></ul>

    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 1502, Column 31: start tag was here
            	<ul class="search l"><form action="/">
  • Error Line 1510, Column 9: document type does not allow element "tr" here
        	<tr>

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

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

  • Error Line 1841, Column 9: end tag for "tr" which is not finished
        </tr>

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

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

  • Error Line 1870, Column 8: element "center" undefined
    <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 1871, Column 180: duplicate specification of attribute "scrolling"
    …ckground-color:transparent" scrolling="no" frameborder="0" width="728" height=…

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1871, Column 197: duplicate specification of attribute "frameborder"
    …r:transparent" scrolling="no" frameborder="0" width="728" height="90"></iframe>

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1871, Column 224: element "iframe" undefined
    …r:transparent" scrolling="no" frameborder="0" width="728" height="90"></iframe>

    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 1882, Column 47: document type does not allow element "form" here; assuming missing "li" start-tag
            	<ul class="search l"><form action="/">
  • Error Line 1883, Column 41: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
                    <li class="search-title">Search</li>

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

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

  • Error Line 1884, Column 41: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    …              <li class="search-input"><input type="hidden" name="ps" value="1…

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

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

  • Error Line 1884, Column 83: end tag for "input" omitted, but OMITTAG NO was specified
    …put type="hidden" name="ps" value="1"><input type="text" name="s" value=""/></…

    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 1884, Column 42: start tag was here
    …             <li class="search-input"><input type="hidden" name="ps" value="1"…
  • Error Line 1885, Column 39: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
                    <li class="search-but"><input type="image" src="/img/search-but…

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

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

  • Error Line 1886, Column 24: end tag for "li" omitted, but OMITTAG NO was specified
                </form></ul>

    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 1882, Column 31: start tag was here
            	<ul class="search l"><form action="/">
  • Error Line 2179, Column 9: document type does not allow element "tr" here
        	<tr>

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

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

  • Error Line 2511, Column 9: end tag for "tr" which is not finished
        </tr>

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

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

  • Error Line 2820, Column 8: element "center" undefined
    <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 2821, Column 179: duplicate specification of attribute "scrolling"
    …ckground-color:transparent" scrolling="no" frameborder="0" width="740" height=…

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 2821, Column 196: duplicate specification of attribute "frameborder"
    …:transparent" scrolling="no" frameborder="0" width="740" height="100"></iframe>

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 2821, Column 224: element "iframe" undefined
    …:transparent" scrolling="no" frameborder="0" width="740" height="100"></iframe>

    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 2843, Column 52: cannot generate system identifier for general entity "u"
    …1 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a></…

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

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

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

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

  • Error Line 2843, Column 52: general entity "u" not defined and no default entity
    …1 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</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.

  • Warning Line 2843, Column 53: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a></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.

  • Warning Line 2843, Column 53: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a></l…

    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 2843, Column 53: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a></l…

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2844, Column 46: reference not terminated by REFC delimiter
    …2 <a href="/cgi-bin/a2/out.cgi?id=63&u=http://www.bulktube.com">Bulk Tube</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 2844, Column 46: reference to external entity in attribute value
    …2 <a href="/cgi-bin/a2/out.cgi?id=63&u=http://www.bulktube.com">Bulk Tube</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 2844, Column 46: reference to entity "u" for which no system identifier could be generated
    …2 <a href="/cgi-bin/a2/out.cgi?id=63&u=http://www.bulktube.com">Bulk Tube</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 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2845, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=538&u=http://www.hot-sex-tube.com">Hot Sex Tu…

    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 2845, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=538&u=http://www.hot-sex-tube.com">Hot Sex Tu…

    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 2845, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=538&u=http://www.hot-sex-tube.com">Hot Sex Tu…

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2846, Column 47: reference not terminated by REFC delimiter
    …4 <a href="/cgi-bin/a2/out.cgi?id=531&u=http://www.21pron.com">21 Pron</a></li>

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

  • Warning Line 2846, Column 47: reference to external entity in attribute value
    …4 <a href="/cgi-bin/a2/out.cgi?id=531&u=http://www.21pron.com">21 Pron</a></li>

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

  • Error Line 2846, Column 47: reference to entity "u" for which no system identifier could be generated
    …4 <a href="/cgi-bin/a2/out.cgi?id=531&u=http://www.21pron.com">21 Pron</a></li>

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2847, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=514&u=http://darkxxxtube.com/">Dark Xxx Tube<…

    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 2847, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=514&u=http://darkxxxtube.com/">Dark Xxx Tube<…

    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 2847, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=514&u=http://darkxxxtube.com/">Dark Xxx Tube<…

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2848, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=532&u=http://www.porn2012.com">Porn 2012</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 2848, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=532&u=http://www.porn2012.com">Porn 2012</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 2848, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=532&u=http://www.porn2012.com">Porn 2012</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 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2849, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=205&u=http://hardmatures.com">Hard Matures Po…

    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 2849, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=205&u=http://hardmatures.com">Hard Matures Po…

    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 2849, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=205&u=http://hardmatures.com">Hard Matures Po…

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2850, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=356&u=http://pornofucksex.com">Porno Fuck 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.

  • Warning Line 2850, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=356&u=http://pornofucksex.com">Porno Fuck Sex…

    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 2850, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=356&u=http://pornofucksex.com">Porno Fuck Sex…

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2851, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=193&u=http://freefuckmovs.com">Free Fuck Movs…

    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 2851, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=193&u=http://freefuckmovs.com">Free Fuck Movs…

    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 2851, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=193&u=http://freefuckmovs.com">Free Fuck Movs…

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2852, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=669&u=http://excellentporntube.com">Excellent…

    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 2852, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=669&u=http://excellentporntube.com">Excellent…

    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 2852, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=669&u=http://excellentporntube.com">Excellent…

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2872, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=217&u=http://sextubeanal.com">Sex Tube Anal</…

    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 2872, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=217&u=http://sextubeanal.com">Sex Tube Anal</…

    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 2872, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=217&u=http://sextubeanal.com">Sex Tube Anal</…

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2873, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=278&u=http://www.hugebootytube.com/">Huge Boo…

    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 2873, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=278&u=http://www.hugebootytube.com/">Huge Boo…

    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 2873, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=278&u=http://www.hugebootytube.com/">Huge Boo…

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2874, Column 47: reference not terminated by REFC delimiter
    …13 <a href="/cgi-bin/a2/out.cgi?id=160&u=http://magpost.com/">Mag Post</a></li>

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

  • Warning Line 2874, Column 47: reference to external entity in attribute value
    …13 <a href="/cgi-bin/a2/out.cgi?id=160&u=http://magpost.com/">Mag Post</a></li>

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

  • Error Line 2874, Column 47: reference to entity "u" for which no system identifier could be generated
    …13 <a href="/cgi-bin/a2/out.cgi?id=160&u=http://magpost.com/">Mag Post</a></li>

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2875, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=494&u=http://www.perfectmums.com/?koktube.com…

    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 2875, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=494&u=http://www.perfectmums.com/?koktube.com…

    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 2875, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=494&u=http://www.perfectmums.com/?koktube.com…

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2876, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=663&u=http://generalporntube.com/">General Po…

    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 2876, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=663&u=http://generalporntube.com/">General Po…

    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 2876, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=663&u=http://generalporntube.com/">General Po…

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2877, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=681&u=http://hqsextubes.com">HQ Sex Tubes</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 2877, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=681&u=http://hqsextubes.com">HQ Sex Tubes</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 2877, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=681&u=http://hqsextubes.com">HQ Sex Tubes</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 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2878, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=210&u=http://pornsextubex.com">Porn Sex Tube<…

    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 2878, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=210&u=http://pornsextubex.com">Porn Sex Tube<…

    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 2878, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=210&u=http://pornsextubex.com">Porn Sex Tube<…

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2879, Column 47: reference not terminated by REFC delimiter
    …18 <a href="/cgi-bin/a2/out.cgi?id=159&u=http://dtvideo.com/">DT Video</a></li>

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

  • Warning Line 2879, Column 47: reference to external entity in attribute value
    …18 <a href="/cgi-bin/a2/out.cgi?id=159&u=http://dtvideo.com/">DT Video</a></li>

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

  • Error Line 2879, Column 47: reference to entity "u" for which no system identifier could be generated
    …18 <a href="/cgi-bin/a2/out.cgi?id=159&u=http://dtvideo.com/">DT Video</a></li>

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2880, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=218&u=http://fetishtuber.com">Fetish Tube</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 2880, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=218&u=http://fetishtuber.com">Fetish Tube</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 2880, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=218&u=http://fetishtuber.com">Fetish Tube</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 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2881, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=477&u=http://epicporntube.com">Epic Porn Tube…

    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 2881, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=477&u=http://epicporntube.com">Epic Porn Tube…

    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 2881, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=477&u=http://epicporntube.com">Epic Porn Tube…

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2901, Column 55: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=190&u=http://fuckxvideos.com">Fuck X Videos</…

    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 2901, Column 55: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=190&u=http://fuckxvideos.com">Fuck X Videos</…

    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 2901, Column 55: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=190&u=http://fuckxvideos.com">Fuck X Videos</…

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2902, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=441&u=http://milftubefuck.com">Milf Tube 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.

  • Warning Line 2902, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=441&u=http://milftubefuck.com">Milf Tube Fuck…

    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 2902, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=441&u=http://milftubefuck.com">Milf Tube Fuck…

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2903, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=590&u=http://www.grannysextubez.com/">GrannyS…

    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 2903, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=590&u=http://www.grannysextubez.com/">GrannyS…

    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 2903, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=590&u=http://www.grannysextubez.com/">GrannyS…

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2904, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=182&u=http://allxxxtubes.com">All Xxx Tubes</…

    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 2904, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=182&u=http://allxxxtubes.com">All Xxx Tubes</…

    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 2904, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=182&u=http://allxxxtubes.com">All Xxx Tubes</…

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2905, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=493&u=http://corrupttube.com">Young Teen Porn…

    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 2905, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=493&u=http://corrupttube.com">Young Teen Porn…

    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 2905, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=493&u=http://corrupttube.com">Young Teen Porn…

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2906, Column 46: reference not terminated by REFC delimiter
    …6 <a href="/cgi-bin/a2/out.cgi?id=70&u=http://www.stvid.com">STream ViD</a></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.

  • Warning Line 2906, Column 46: reference to external entity in attribute value
    …6 <a href="/cgi-bin/a2/out.cgi?id=70&u=http://www.stvid.com">STream ViD</a></l…

    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 2906, Column 46: reference to entity "u" for which no system identifier could be generated
    …6 <a href="/cgi-bin/a2/out.cgi?id=70&u=http://www.stvid.com">STream ViD</a></l…

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2907, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=475&u=http://www.youratetube.com">Your Tube</…

    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 2907, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=475&u=http://www.youratetube.com">Your Tube</…

    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 2907, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=475&u=http://www.youratetube.com">Your Tube</…

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2908, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=637&u=http://www.yourtube.xxx/">Free Porn Vid…

    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 2908, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=637&u=http://www.yourtube.xxx/">Free Porn Vid…

    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 2908, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=637&u=http://www.yourtube.xxx/">Free Porn Vid…

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2909, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=480&u=http://www.tubemike.com">Mike's Free Tu…

    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 2909, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=480&u=http://www.tubemike.com">Mike's Free Tu…

    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 2909, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=480&u=http://www.tubemike.com">Mike's Free Tu…

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2910, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=255&u=http://hotanaltube.com">Hot Anal Tube</…

    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 2910, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=255&u=http://hotanaltube.com">Hot Anal Tube</…

    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 2910, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=255&u=http://hotanaltube.com">Hot Anal Tube</…

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2930, Column 48: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=537&u=http://paradisemovs.com/">Paradise Movs…

    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 2930, Column 48: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=537&u=http://paradisemovs.com/">Paradise Movs…

    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 2930, Column 48: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=537&u=http://paradisemovs.com/">Paradise Movs…

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2931, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=478&u=http://www.tubegoggles.com">Tube Google…

    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 2931, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=478&u=http://www.tubegoggles.com">Tube Google…

    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 2931, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=478&u=http://www.tubegoggles.com">Tube Google…

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2932, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=214&u=http://sexytubesex.com">Sexy Tube 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.

  • Warning Line 2932, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=214&u=http://sexytubesex.com">Sexy Tube Sex</…

    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 2932, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=214&u=http://sexytubesex.com">Sexy Tube Sex</…

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2933, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=375&u=http://hq-redtube.com">HQ Red Tube</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 2933, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=375&u=http://hq-redtube.com">HQ Red Tube</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 2933, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=375&u=http://hq-redtube.com">HQ Red Tube</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 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2934, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=371&u=http://largetube.net/">Large Tube</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 2934, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=371&u=http://largetube.net/">Large Tube</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 2934, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=371&u=http://largetube.net/">Large Tube</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 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2935, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=471&u=http://www.backupporn.com">Back Up Porn…

    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 2935, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=471&u=http://www.backupporn.com">Back Up Porn…

    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 2935, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=471&u=http://www.backupporn.com">Back Up Porn…

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2936, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=472&u=http://www.tubepornsearch.com">Tube Por…

    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 2936, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=472&u=http://www.tubepornsearch.com">Tube Por…

    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 2936, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=472&u=http://www.tubepornsearch.com">Tube Por…

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2937, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=473&u=http://www.orgasmicpages.com">Orgasmic …

    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 2937, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=473&u=http://www.orgasmicpages.com">Orgasmic …

    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 2937, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=473&u=http://www.orgasmicpages.com">Orgasmic …

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2938, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=474&u=http://www.youtubelike.com">You Tube Li…

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

  • Warning Line 2938, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=474&u=http://www.youtubelike.com">You Tube Li…

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

  • Error Line 2938, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=474&u=http://www.youtubelike.com">You Tube Li…

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2939, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=476&u=http://www.youpicktube.com">You Pic 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.

  • Warning Line 2939, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=476&u=http://www.youpicktube.com">You Pic Tub…

    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 2939, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=476&u=http://www.youpicktube.com">You Pic Tub…

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2959, Column 55: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=492&u=http://www.mixedporno.com">Mixed Porno<…

    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 2959, Column 55: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=492&u=http://www.mixedporno.com">Mixed Porno<…

    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 2959, Column 55: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=492&u=http://www.mixedporno.com">Mixed Porno<…

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2960, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=491&u=http://trannyhotsex.com">Tranny Hot 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.

  • Warning Line 2960, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=491&u=http://trannyhotsex.com">Tranny Hot Sex…

    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 2960, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=491&u=http://trannyhotsex.com">Tranny Hot Sex…

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2961, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=490&u=http://sexebonytube.com">Ebony Sex Tube…

    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 2961, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=490&u=http://sexebonytube.com">Ebony Sex Tube…

    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 2961, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=490&u=http://sexebonytube.com">Ebony Sex Tube…

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2962, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=489&u=http://xsexgay.com">Gay Sex Videos</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 2962, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=489&u=http://xsexgay.com">Gay Sex Videos</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 2962, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=489&u=http://xsexgay.com">Gay Sex Videos</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 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2963, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=488&u=http://porntubezz.com">Porn Tube Videos…

    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 2963, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=488&u=http://porntubezz.com">Porn Tube Videos…

    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 2963, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=488&u=http://porntubezz.com">Porn Tube Videos…

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2964, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=487&u=http://sextubelesbian.com">Sex Tube Les…

    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 2964, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=487&u=http://sextubelesbian.com">Sex Tube Les…

    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 2964, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=487&u=http://sextubelesbian.com">Sex Tube Les…

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2965, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=486&u=http://asianpornfuck.com">Asian Porn 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.

  • Warning Line 2965, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=486&u=http://asianpornfuck.com">Asian Porn Fu…

    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 2965, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=486&u=http://asianpornfuck.com">Asian Porn Fu…

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2966, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=479&u=http://www.tugmovies.com">Adult Tube Se…

    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 2966, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=479&u=http://www.tugmovies.com">Adult Tube Se…

    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 2966, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=479&u=http://www.tugmovies.com">Adult Tube Se…

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2967, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=485&u=http://porntubebot.com">Porn Tube Bot</…

    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 2967, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=485&u=http://porntubebot.com">Porn Tube Bot</…

    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 2967, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=485&u=http://porntubebot.com">Porn Tube Bot</…

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Warning Line 2968, Column 47: reference not terminated by REFC delimiter
    … <a href="/cgi-bin/a2/out.cgi?id=484&u=http://www.freshsextube.com">Fresh 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.

  • Warning Line 2968, Column 47: reference to external entity in attribute value
    … <a href="/cgi-bin/a2/out.cgi?id=484&u=http://www.freshsextube.com">Fresh Sex …

    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 2968, Column 47: reference to entity "u" for which no system identifier could be generated
    … <a href="/cgi-bin/a2/out.cgi?id=484&u=http://www.freshsextube.com">Fresh Sex …

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

  • Info Line 2843, Column 51: entity was defined here
    …01 <a href="/cgi-bin/a2/out.cgi?id=163&u=http://video-one.com/">Video One</a><…
  • Error Line 3035, Column 414: there is no attribute "target"
    … <a href="http://xhamster.com" target="_blank" title="Free Porn">Free Porn</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.

Visitor Analysis

Daily Visitor
  • 1.108 visits