10.000s of free videos, pictures and galleries of hot girls having sex in public or getting naked in public places. ...

nakedonthestreets.com
  • Domain Name
    nakedonthestreets.com
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #44581
  • Page Size
    63.8 KB
  • Ip Address
    108.162.206.159
  • Heading
    H1: 6, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    1 GIF, 39 JPG, 21 PNG

Website Meta Analysis

  • Title
    NakedOnTheStreets.com
  • Meta Keyword
    public sex, sex in public, public, public porn, tube ,porn tube, porn, free porn, porn videos, public nudity, streaking, flashing, naked, nude,nudists, pictures, photos, images, videos, video, galleries, gallery, streets, nakedonthestreets, naked on the streets, naked in the streets, free, free porn, adult, sex, xxx, movies, clips, amateur, streaking, chicks, babes, boobflash, fucking, fuck, outside, outdoor, outdoor sex
  • Meta Description
    10.000s of free videos, pictures and galleries of hot girls having sex in public or getting naked in public places.

Technical Analysis

  • Webserver
    cloudflare-nginx
  • Ip Address
    108.162.206.159
  • Domain Age
    7 Years, 4 Months, 23 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: cloudflare-nginx
  • date: Mon, 30 Sep 2013 19:00:05 GMT
  • content-type: text/html; charset=utf-8
  • connection: keep-alive
  • x-powered-by: PHP/5.3.3-7+squeeze15
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • cf-ray: b63276c49c8020c
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: NAKEDONTHESTREETS.COM
Created on: 17-May-06
Expires on: 17-May-14
Last Updated on: 19-Jan-12

Registrant:
Domains By Proxy, LLC
DomainsByProxy.com
14747 N Northsight Blvd Suite 111, PMB 309
Scottsdale, Arizona 85260
United States

Administrative Contact:
Private, Registration email
Domains By Proxy, LLC
DomainsByProxy.com
14747 N Northsight Blvd Suite 111, PMB 309
Scottsdale, Arizona 85260
United States
(480) 624-2599 Fax -- (480) 624-2598

Technical Contact:
Private, Registration email
Domains By Proxy, LLC
DomainsByProxy.com
14747 N Northsight Blvd Suite 111, PMB 309
Scottsdale, Arizona 85260
United States
(480) 624-2599 Fax -- (480) 624-2598

Domain servers in listed order:
NS31.DOMAINCONTROL.COM
NS32.DOMAINCONTROL.COM

DNS Analysis


DNS servers
ns31.domaincontrol.com [216.69.185.16]
ns32.domaincontrol.com [208.109.255.16]


DNS Records

Answer records
nakedonthestreets.com A 108.59.9.22 3600s
nakedonthestreets.com MX
preference: 0
exchange: smtp.secureserver.net
3600s
nakedonthestreets.com MX
preference: 10
exchange: mailstore1.secureserver.net
3600s
nakedonthestreets.com NS  ns31.domaincontrol.com 3600s
nakedonthestreets.com NS  ns32.domaincontrol.com 3600s
nakedonthestreets.com SOA
server: ns31.domaincontrol.com
email: dns@jomax.net
serial: 2012013001
refresh: 28800
retry: 7200
expire: 604800
minimum ttl: 3600
3600s

Authority records

Additional records

IP 108.162.206.159 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 107 Errors
  • 78 Warnings
Ratio Text/Html
  • 0.7610390406028396
Message Error
  • Error Line 2, Column 1: Missing xmlns attribute for element html. The value should be: http://www.w3.org/1999/xhtml
    <html>

    Many Document Types based on XML need a mandatory xmlns attribute on the root element. For example, the root element for XHTML might look like:
    <html xmlns="http://www.w3.org/1999/xhtml">

  • Error Line 5, Column 93: end tag for "link" omitted, but OMITTAG NO was specified
    …ylesheet" href="http://www.nakedonthestreets.com/css/main.css" type="text/css">

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

  • Info Line 5, Column 1: start tag was here
    <link rel="stylesheet" href="http://www.nakedonthestreets.com/css/main.css" typ…
  • Error Line 6, Column 18: there is no attribute "language"
    <script language="JavaScript" src="http://www.nakedonthestreets.com/scripts/com…

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

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

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

  • Error Line 7, Column 152: end tag for "meta" omitted, but OMITTAG NO was specified
    …alleries of hot girls having sex in public or getting naked in public places.">

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

  • Info Line 7, Column 1: start tag was here
    <meta name="description" content="10.000s of free videos, pictures and gallerie…
  • Error Line 8, Column 458: end tag for "meta" omitted, but OMITTAG NO was specified
    …aking, chicks, babes, boobflash, fucking, fuck, outside, outdoor, outdoor sex">

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

  • Info Line 8, Column 1: start tag was here
    <meta name="keywords" content="public sex, sex in public, public, public porn, …
  • Error Line 24, 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>.

  • Warning Line 28, Column 13: character "<" is the first character of a delimiter but occurred as data
      for(i=0;i < 20;i++) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 32, Column 56: an attribute value must be a literal unless it contains only name characters
    …"<img style='position: absolute;' src=/scj/cgi/user.php?code="+key+" width=0 h…

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

  • Error Line 32, Column 93: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …='position: absolute;' src=/scj/cgi/user.php?code="+key+" width=0 height=0/>");
  • Error Line 32, Column 102: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …='position: absolute;' src=/scj/cgi/user.php?code="+key+" width=0 height=0/>");
  • Error Line 32, Column 104: required attribute "alt" not specified
    …='position: absolute;' src=/scj/cgi/user.php?code="+key+" width=0 height=0/>");

    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 32, Column 104: document type does not allow element "img" here
    …='position: absolute;' src=/scj/cgi/user.php?code="+key+" width=0 height=0/>");

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

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

  • Error Line 71, Column 15: there is no attribute "bgcolor"
    <body bgcolor="#FFFFFF" text="#000000" leftmargin="0" topmargin="0" marginwidth…

    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 71, Column 30: there is no attribute "text"
    <body bgcolor="#FFFFFF" text="#000000" leftmargin="0" topmargin="0" marginwidth…

    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 71, Column 51: there is no attribute "leftmargin"
    …r="#FFFFFF" text="#000000" leftmargin="0" topmargin="0" marginwidth="0" margin…

    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 71, Column 65: there is no attribute "topmargin"
    …xt="#000000" leftmargin="0" topmargin="0" marginwidth="0" marginheight="0" bac…

    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 71, Column 81: there is no attribute "marginwidth"
    …tmargin="0" topmargin="0" marginwidth="0" marginheight="0" background="/img/bg…

    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 71, Column 98: there is no attribute "marginheight"
    …in="0" topmargin="0" marginwidth="0" marginheight="0" background="/img/bg.jpg">

    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 71, Column 113: there is no attribute "background"
    …in="0" topmargin="0" marginwidth="0" marginheight="0" background="/img/bg.jpg">

    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 73, Column 80: required attribute "type" not specified
    …nguage="JavaScript" src="http://www.nakedonthestreets.com/tooltip.js"></script>

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

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

  • Error Line 84, Column 57: there is no attribute "align"
    <table border="0" cellspacing="0" cellpadding="0" align="center" width="986">

    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 86, Column 27: there is no attribute "width"
        <td rowspan="2" width="8" background="http://www.nakedonthestreets.com/img/…

    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 86, Column 42: there is no attribute "background"
    … <td rowspan="2" width="8" background="http://www.nakedonthestreets.com/img/le…

    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 86, Column 203: required attribute "alt" not specified
    …//www.nakedonthestreets.com/img/leftshadowtop.jpg" width="9" height="690"></td>

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

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

  • Error Line 86, Column 208: end tag for "img" omitted, but OMITTAG NO was specified
    …//www.nakedonthestreets.com/img/leftshadowtop.jpg" width="9" height="690"></td>

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

  • Info Line 86, Column 115: start tag was here
    …mg/leftshadowbottom.jpg" valign="top"><img src="http://www.nakedonthestreets.c…
  • Error Line 87, Column 28: there is no attribute "height"
        <td width="980" height="150" background="http://www.nakedonthestreets.com/i…

    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 87, Column 111: there is no attribute "bgcolor"
    …nd="http://www.nakedonthestreets.com/img/site/aextrabar.gif" bgcolor="#FFFFFF">

    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 88, Column 77: there is no attribute "autocomplete"
    …st" action="/search.php" autocomplete="off"><input type="hidden" name="action"…

    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 88, Column 132: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …="hidden" name="action" value="search"><input type="text" name="search" value=…

    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 88, Column 133: end tag for "input" omitted, but OMITTAG NO was specified
    …"hidden" name="action" value="search"><input type="text" name="search" 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 88, Column 83: start tag was here
    …tion="/search.php" autocomplete="off"><input type="hidden" name="action" value…
  • Error Line 88, Column 344: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    ….value = 'Search for Public Sex'; }" /><input type="image" src="/img/search.pn…

    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 88, Column 388: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …for Public Sex'; }" /><input type="image" src="/img/search.png" /></form></div>

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

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

  • Error Line 89, Column 21: there is no attribute "onClick"
    <a href="#" onClick="window.external.AddFavorite('http://www.nakedonthestreets.…

    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 90, Column 163: there is no attribute "border"
    …kedontheStreets.com to your Favorites" width="980" height="150" border="0"></a>

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

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

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

  • Error Line 90, Column 170: end tag for "img" omitted, but OMITTAG NO was specified
    …kedontheStreets.com to your Favorites" width="980" height="150" border="0"></a>

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

  • Info Line 90, Column 2: start tag was here
    	<img src="http://www.nakedonthestreets.com/img/heads/rotate.php" alt="Click he…
  • Error Line 100, Column 68: there is no attribute "target"
    …avy-r.com/free_porn/rape.html" target="_blank" title="rape porn" class='btnlas…

    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 120, Column 153: there is no attribute "alt"
    …_masturbate_for_teammates_18165/" alt="Girl forced to masturbate for teammates…

    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.

  • Warning Line 168, Column 101: cannot generate system identifier for general entity "url"
    …treets.com/out.php?member=heavy-r.com&url=http://www.heavy-r.com/video/128826/…

    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 168, Column 101: general entity "url" not defined and no default entity
    …treets.com/out.php?member=heavy-r.com&url=http://www.heavy-r.com/video/128826/…

    This is usually a cascading error caused by 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 168, Column 104: reference not terminated by REFC delimiter
    …ets.com/out.php?member=heavy-r.com&url=http://www.heavy-r.com/video/128826/Pub…

    If you meant to include an entity that starts with "&", then you should terminate it 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 168, Column 104: reference to external entity in attribute value
    …ets.com/out.php?member=heavy-r.com&url=http://www.heavy-r.com/video/128826/Pub…

    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 168, Column 104: reference to entity "url" for which no system identifier could be generated
    …ets.com/out.php?member=heavy-r.com&url=http://www.heavy-r.com/video/128826/Pub…

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

  • Info Line 168, Column 100: entity was defined here
    …streets.com/out.php?member=heavy-r.com&url=http://www.heavy-r.com/video/128826…
  • Error Line 168, Column 403: end tag for "img" omitted, but OMITTAG NO was specified
    …ont of school girls ()" border="0"></a><div id="description_9785" class="notin…

    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 168, Column 198: start tag was here
    …ront_Of_Schoolgirls/" target="_blank"><img class="gradualshine" src="/content/…
  • Warning Line 169, Column 112: reference not terminated by REFC delimiter
    …out.php?member=homemade-voyeur.com&url=http://www.homemade-voyeur.com/tube/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 169, Column 112: reference to external entity in attribute value
    …out.php?member=homemade-voyeur.com&url=http://www.homemade-voyeur.com/tube/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 169, Column 112: reference to entity "url" for which no system identifier could be generated
    …out.php?member=homemade-voyeur.com&url=http://www.homemade-voyeur.com/tube/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 168, Column 100: entity was defined here
    …streets.com/out.php?member=heavy-r.com&url=http://www.heavy-r.com/video/128826…
  • Error Line 169, Column 401: end tag for "img" omitted, but OMITTAG NO was specified
    …busted masturbating ()" border="0"></a><div id="description_9784" class="notin…

    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 169, Column 214: start tag was here
    …ing-z3iihiEZ1UX.html" target="_blank"><img class="gradualshine" src="/content/…
  • Error Line 170, Column 291: end tag for "img" omitted, but OMITTAG NO was specified
    …abe sucking my dick ()" border="0"></a><div id="description_9783" class="notin…

    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 170, Column 99: start tag was here
    …estreets.com/out.php" target="_blank"><img class="gradualshine" src="/content/…
  • Error Line 171, Column 330: end tag for "img" omitted, but OMITTAG NO was specified
    …hem taking a shower ()" border="0"></a><div id="description_9782" class="notin…

    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 171, Column 99: start tag was here
    …estreets.com/out.php" target="_blank"><img class="gradualshine" src="/content/…
  • Warning Line 172, Column 108: reference not terminated by REFC delimiter
    …com/out.php?member=fuckinghard.net&url=http://www.fuckinghard.net/hosted/media…

    If you meant to include an entity that starts with "&", then you should terminate it 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 172, Column 108: reference to external entity in attribute value
    …com/out.php?member=fuckinghard.net&url=http://www.fuckinghard.net/hosted/media…

    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 172, Column 108: reference to entity "url" for which no system identifier could be generated
    …com/out.php?member=fuckinghard.net&url=http://www.fuckinghard.net/hosted/media…

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

  • Info Line 168, Column 100: entity was defined here
    …streets.com/out.php?member=heavy-r.com&url=http://www.heavy-r.com/video/128826…
  • Error Line 172, Column 442: end tag for "img" omitted, but OMITTAG NO was specified
    … the girl next door ()" border="0"></a><div id="description_9781" class="notin…

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

  • Info Line 172, Column 231: start tag was here
    …y-girlfriend,386.php" target="_blank"><img class="gradualshine" src="/content/…
  • Warning Line 173, Column 104: reference not terminated by REFC delimiter
    …ets.com/out.php?member=heavy-r.com&url=http://www.heavy-r.com/video/128566/You…

    If you meant to include an entity that starts with "&", then you should terminate it 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 173, Column 104: reference to external entity in attribute value
    …ets.com/out.php?member=heavy-r.com&url=http://www.heavy-r.com/video/128566/You…

    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 173, Column 104: reference to entity "url" for which no system identifier could be generated
    …ets.com/out.php?member=heavy-r.com&url=http://www.heavy-r.com/video/128566/You…

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

  • Info Line 168, Column 100: entity was defined here
    …streets.com/out.php?member=heavy-r.com&url=http://www.heavy-r.com/video/128826…
  • Error Line 173, Column 371: end tag for "img" omitted, but OMITTAG NO was specified
    …l fucking for money ()" border="0"></a><div id="description_9780" class="notin…

    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 173, Column 188: start tag was here
    …l_Fucking_For_Money/" target="_blank"><img class="gradualshine" src="/content/…
  • Warning Line 174, Column 103: reference not terminated by REFC delimiter
    …eets.com/out.php?member=theync.com&url=http://theync.com/underground_features.…

    If you meant to include an entity that starts with "&", then you should terminate it 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 174, Column 103: reference to external entity in attribute value
    …eets.com/out.php?member=theync.com&url=http://theync.com/underground_features.…

    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 174, Column 103: reference to entity "url" for which no system identifier could be generated
    …eets.com/out.php?member=theync.com&url=http://theync.com/underground_features.…

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

  • Info Line 168, Column 100: entity was defined here
    …streets.com/out.php?member=heavy-r.com&url=http://www.heavy-r.com/video/128826…
  • Warning Line 174, Column 165: cannot generate system identifier for general entity "utm_source"
    …ground_features.php?name=23823-mother&utm_source=ug&utm_medium=Banner&utm_cont…

    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 174, Column 165: general entity "utm_source" not defined and no default entity
    …ground_features.php?name=23823-mother&utm_source=ug&utm_medium=Banner&utm_cont…

    This is usually a cascading error caused by 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 174, Column 175: reference not terminated by REFC delimiter
    …tures.php?name=23823-mother&utm_source=ug&utm_medium=Banner&utm_content=Banner…

    If you meant to include an entity that starts with "&", then you should terminate it 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 174, Column 175: reference to external entity in attribute value
    …tures.php?name=23823-mother&utm_source=ug&utm_medium=Banner&utm_content=Banner…

    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 174, Column 175: reference to entity "utm_source" for which no system identifier could be generated
    …tures.php?name=23823-mother&utm_source=ug&utm_medium=Banner&utm_content=Banner…

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

  • Info Line 174, Column 164: entity was defined here
    …rground_features.php?name=23823-mother&utm_source=ug&utm_medium=Banner&utm_con…
  • Warning Line 174, Column 179: cannot generate system identifier for general entity "utm_medium"
    …s.php?name=23823-mother&utm_source=ug&utm_medium=Banner&utm_content=BannerAd1&…

    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 174, Column 179: general entity "utm_medium" not defined and no default entity
    …s.php?name=23823-mother&utm_source=ug&utm_medium=Banner&utm_content=BannerAd1&…

    This is usually a cascading error caused by 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 174, Column 189: reference not terminated by REFC delimiter
    …=23823-mother&utm_source=ug&utm_medium=Banner&utm_content=BannerAd1&utm_campai…

    If you meant to include an entity that starts with "&", then you should terminate it 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 174, Column 189: reference to external entity in attribute value
    …=23823-mother&utm_source=ug&utm_medium=Banner&utm_content=BannerAd1&utm_campai…

    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 174, Column 189: reference to entity "utm_medium" for which no system identifier could be generated
    …=23823-mother&utm_source=ug&utm_medium=Banner&utm_content=BannerAd1&utm_campai…

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

  • Info Line 174, Column 178: entity was defined here
    …es.php?name=23823-mother&utm_source=ug&utm_medium=Banner&utm_content=BannerAd1…
  • Warning Line 174, Column 197: cannot generate system identifier for general entity "utm_content"
    …other&utm_source=ug&utm_medium=Banner&utm_content=BannerAd1&utm_campaign=Under…

    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 174, Column 197: general entity "utm_content" not defined and no default entity
    …other&utm_source=ug&utm_medium=Banner&utm_content=BannerAd1&utm_campaign=Under…

    This is usually a cascading error caused by 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 174, Column 208: reference not terminated by REFC delimiter
    …ource=ug&utm_medium=Banner&utm_content=BannerAd1&utm_campaign=Underground <htt…

    If you meant to include an entity that starts with "&", then you should terminate it 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 174, Column 208: reference to external entity in attribute value
    …ource=ug&utm_medium=Banner&utm_content=BannerAd1&utm_campaign=Underground <htt…

    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 174, Column 208: reference to entity "utm_content" for which no system identifier could be generated
    …ource=ug&utm_medium=Banner&utm_content=BannerAd1&utm_campaign=Underground <htt…

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

  • Info Line 174, Column 196: entity was defined here
    …mother&utm_source=ug&utm_medium=Banner&utm_content=BannerAd1&utm_campaign=Unde…
  • Warning Line 174, Column 219: cannot generate system identifier for general entity "utm_campaign"
    …m_medium=Banner&utm_content=BannerAd1&utm_campaign=Underground <http://theync.…

    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 174, Column 219: general entity "utm_campaign" not defined and no default entity
    …m_medium=Banner&utm_content=BannerAd1&utm_campaign=Underground <http://theync.…

    This is usually a cascading error caused by 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 174, Column 231: reference not terminated by REFC delimiter
    …ner&utm_content=BannerAd1&utm_campaign=Underground <http://theync.com/undergro…

    If you meant to include an entity that starts with "&", then you should terminate it 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 174, Column 231: reference to external entity in attribute value
    …ner&utm_content=BannerAd1&utm_campaign=Underground <http://theync.com/undergro…

    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 174, Column 231: reference to entity "utm_campaign" for which no system identifier could be generated
    …ner&utm_content=BannerAd1&utm_campaign=Underground <http://theync.com/undergro…

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

  • Info Line 174, Column 218: entity was defined here
    …tm_medium=Banner&utm_content=BannerAd1&utm_campaign=Underground <http://theync…
  • Warning Line 174, Column 244: character "<" is the first character of a delimiter but occurred as data
    …nt=BannerAd1&utm_campaign=Underground <http://theync.com/underground_features.…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 174, Column 500: end tag for "img" omitted, but OMITTAG NO was specified
    …rrupts teen blowjob ()" border="0"></a><div id="description_9779" class="notin…

    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 174, Column 314: start tag was here
    …eatures.php?name=223" target="_blank"><img class="gradualshine" src="/content/…
  • Warning Line 175, Column 110: reference not terminated by REFC delimiter
    …m/out.php?member=dreamamateurs.com&url=http://www.dreamamateurs.com/Amateur/15…

    If you meant to include an entity that starts with "&", then you should terminate it 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 175, Column 110: reference to external entity in attribute value
    …m/out.php?member=dreamamateurs.com&url=http://www.dreamamateurs.com/Amateur/15…

    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 175, Column 110: reference to entity "url" for which no system identifier could be generated
    …m/out.php?member=dreamamateurs.com&url=http://www.dreamamateurs.com/Amateur/15…

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

  • Info Line 168, Column 100: entity was defined here
    …streets.com/out.php?member=heavy-r.com&url=http://www.heavy-r.com/video/128826…
  • Error Line 175, Column 400: end tag for "img" omitted, but OMITTAG NO was specified
    …s rough make up sex ()" border="0"></a><div id="description_9778" class="notin…

    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 175, Column 211: start tag was here
    …udent_Fuck_Tape.html" target="_blank"><img class="gradualshine" src="/content/…
  • Warning Line 176, Column 104: reference not terminated by REFC delimiter
    …tegories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzznots" target="_…

    If you meant to include an entity that starts with "&", then you should terminate it 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 176, Column 104: reference to external entity in attribute value
    …tegories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzznots" target="_…

    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 176, Column 104: reference to entity "utm_medium" for which no system identifier could be generated
    …tegories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzznots" target="_…

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

  • Info Line 174, Column 178: entity was defined here
    …es.php?name=23823-mother&utm_source=ug&utm_medium=Banner&utm_content=BannerAd1…
  • Warning Line 176, Column 120: reference not terminated by REFC delimiter
    …rce=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzznots" target="_blank"><img clas…

    If you meant to include an entity that starts with "&", then you should terminate it 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 176, Column 120: reference to external entity in attribute value
    …rce=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzznots" target="_blank"><img clas…

    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 176, Column 120: reference to entity "utm_campaign" for which no system identifier could be generated
    …rce=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzznots" target="_blank"><img clas…

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

  • Info Line 174, Column 218: entity was defined here
    …tm_medium=Banner&utm_content=BannerAd1&utm_campaign=Underground <http://theync…
  • Error Line 176, Column 360: end tag for "img" omitted, but OMITTAG NO was specified
    …bused by fat nigger ()" border="0"></a><div id="description_9777" class="notin…

    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 176, Column 151: start tag was here
    …ampaign=Pauluzzznots" target="_blank"><img class="gradualshine" src="/content/…
  • Warning Line 177, Column 112: reference not terminated by REFC delimiter
    …out.php?member=homemade-voyeur.com&url=http://www.homemade-voyeur.com/tube/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 177, Column 112: reference to external entity in attribute value
    …out.php?member=homemade-voyeur.com&url=http://www.homemade-voyeur.com/tube/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 177, Column 112: reference to entity "url" for which no system identifier could be generated
    …out.php?member=homemade-voyeur.com&url=http://www.homemade-voyeur.com/tube/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 168, Column 100: entity was defined here
    …streets.com/out.php?member=heavy-r.com&url=http://www.heavy-r.com/video/128826…
  • Error Line 177, Column 426: end tag for "img" omitted, but OMITTAG NO was specified
    … by their son, oops ()" border="0"></a><div id="description_9776" class="notin…

    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 177, Column 203: start tag was here
    …son-7zH3Ge5a2bP.html" target="_blank"><img class="gradualshine" src="/content/…
  • Warning Line 178, Column 104: reference not terminated by REFC delimiter
    …ets.com/out.php?member=heavy-r.com&url=http://www.heavy-r.com/video/128542/Out…

    If you meant to include an entity that starts with "&", then you should terminate it 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 178, Column 104: reference to external entity in attribute value
    …ets.com/out.php?member=heavy-r.com&url=http://www.heavy-r.com/video/128542/Out…

    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 178, Column 104: reference to entity "url" for which no system identifier could be generated
    …ets.com/out.php?member=heavy-r.com&url=http://www.heavy-r.com/video/128542/Out…

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

  • Info Line 168, Column 100: entity was defined here
    …streets.com/out.php?member=heavy-r.com&url=http://www.heavy-r.com/video/128826…
  • Error Line 178, Column 342: end tag for "img" omitted, but OMITTAG NO was specified
    …now blowjob outdoor ()" border="0"></a><div id="description_9775" class="notin…

    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 178, Column 175: start tag was here
    …542/Outdoor_Blowjob/" target="_blank"><img class="gradualshine" src="/content/…
  • Warning Line 179, Column 112: reference not terminated by REFC delimiter
    …out.php?member=homemade-voyeur.com&url=http://www.homemade-voyeur.com/tube/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 179, Column 112: reference to external entity in attribute value
    …out.php?member=homemade-voyeur.com&url=http://www.homemade-voyeur.com/tube/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 179, Column 112: reference to entity "url" for which no system identifier could be generated
    …out.php?member=homemade-voyeur.com&url=http://www.homemade-voyeur.com/tube/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 168, Column 100: entity was defined here
    …streets.com/out.php?member=heavy-r.com&url=http://www.heavy-r.com/video/128826…
  • Error Line 179, Column 406: end tag for "img" omitted, but OMITTAG NO was specified
    …cousin masturbating ()" border="0"></a><div id="description_9774" class="notin…

    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 179, Column 206: start tag was here
    …pee-hEG9xEHfFvo.html" target="_blank"><img class="gradualshine" src="/content/…
  • Warning Line 180, Column 103: reference not terminated by REFC delimiter
    …eets.com/out.php?member=theync.com&url=http://theync.com/underground.php?name=…

    If you meant to include an entity that starts with "&", then you should terminate it 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 180, Column 103: reference to external entity in attribute value
    …eets.com/out.php?member=theync.com&url=http://theync.com/underground.php?name=…

    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 180, Column 103: reference to entity "url" for which no system identifier could be generated
    …eets.com/out.php?member=theync.com&url=http://theync.com/underground.php?name=…

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

  • Info Line 168, Column 100: entity was defined here
    …streets.com/out.php?member=heavy-r.com&url=http://www.heavy-r.com/video/128826…
  • Error Line 180, Column 378: end tag for "img" omitted, but OMITTAG NO was specified
    …ting innocent girls ()" border="0"></a><div id="description_9773" class="notin…

    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 180, Column 172: start tag was here
    …php?name=23816-sleep" target="_blank"><img class="gradualshine" src="/content/…
  • Error Line 648, Column 145: there is no attribute "onMouseOver"
    …?id=9785" target="_blank" onMouseOver="Tip('<img src=/content/thumbs/th_7769_h…

    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.

  • Warning Line 648, Column 151: character "<" is the first character of a delimiter but occurred as data
    …85" target="_blank" onMouseOver="Tip('<img src=/content/thumbs/th_7769_heavy_r…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 648, Column 300: there is no attribute "onMouseOut"
    … WIDTH, 185, BGCOLOR, '')" onMouseOut="UnTip()">Public cumshot in front of sch…

    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.

  • Warning Line 648, Column 504: character "<" is the first character of a delimiter but occurred as data
    …84" target="_blank" onMouseOver="Tip('<img src=/content/thumbs/th_1058_homemad…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 649, Column 151: character "<" is the first character of a delimiter but occurred as data
    …83" target="_blank" onMouseOver="Tip('<img src=/content/thumbs/th_4078_stolenv…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 649, Column 500: character "<" is the first character of a delimiter but occurred as data
    …82" target="_blank" onMouseOver="Tip('<img src=/content/thumbs/th_7671_sponsor…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 650, Column 151: character "<" is the first character of a delimiter but occurred as data
    …81" target="_blank" onMouseOver="Tip('<img src=/content/thumbs/th_4152_fucking…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 650, Column 509: character "<" is the first character of a delimiter but occurred as data
    …80" target="_blank" onMouseOver="Tip('<img src=/content/thumbs/th_2856_heavy_r…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 651, Column 151: character "<" is the first character of a delimiter but occurred as data
    …79" target="_blank" onMouseOver="Tip('<img src=/content/thumbs/th_2001_theync.…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 651, Column 494: character "<" is the first character of a delimiter but occurred as data
    …78" target="_blank" onMouseOver="Tip('<img src=/content/thumbs/th_2292_dreamam…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 652, Column 151: character "<" is the first character of a delimiter but occurred as data
    …77" target="_blank" onMouseOver="Tip('<img src=/content/thumbs/th_4902_sponsor…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 652, Column 506: character "<" is the first character of a delimiter but occurred as data
    …76" target="_blank" onMouseOver="Tip('<img src=/content/thumbs/th_7613_homemad…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 653, Column 151: character "<" is the first character of a delimiter but occurred as data
    …75" target="_blank" onMouseOver="Tip('<img src=/content/thumbs/th_5466_heavy_r…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 653, Column 485: character "<" is the first character of a delimiter but occurred as data
    …74" target="_blank" onMouseOver="Tip('<img src=/content/thumbs/th_2037_homemad…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 654, Column 151: character "<" is the first character of a delimiter but occurred as data
    …73" target="_blank" onMouseOver="Tip('<img src=/content/thumbs/th_1036_theync.…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 654, Column 504: character "<" is the first character of a delimiter but occurred as data
    …72" target="_blank" onMouseOver="Tip('<img src=/content/thumbs/th_5623_sponsor…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 655, Column 151: character "<" is the first character of a delimiter but occurred as data
    …71" target="_blank" onMouseOver="Tip('<img src=/content/thumbs/th_1103_homemad…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 655, Column 489: character "<" is the first character of a delimiter but occurred as data
    …70" target="_blank" onMouseOver="Tip('<img src=/content/thumbs/th_4634_heavy_r…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 656, Column 151: character "<" is the first character of a delimiter but occurred as data
    …69" target="_blank" onMouseOver="Tip('<img src=/content/thumbs/th_homemade_voy…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 656, Column 501: character "<" is the first character of a delimiter but occurred as data
    …68" target="_blank" onMouseOver="Tip('<img src=/content/thumbs/th_6355_pornyfi…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 657, Column 151: character "<" is the first character of a delimiter but occurred as data
    …67" target="_blank" onMouseOver="Tip('<img src=/content/thumbs/th_8702_sponsor…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 657, Column 515: character "<" is the first character of a delimiter but occurred as data
    …66" target="_blank" onMouseOver="Tip('<img src=/content/thumbs/th_1627_homemad…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 665, Column 17: there is no attribute "src"
        <iframe src="http://www.nakedonthestreets.com/ads/aff01.html" height="250" …

    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 665, Column 74: there is no attribute "height"
    …thestreets.com/ads/aff01.html" height="250" width="900" frameborder="no" borde…

    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 665, Column 86: there is no attribute "width"
    …om/ads/aff01.html" height="250" width="900" frameborder="no" border="0" margin…

    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 665, Column 104: there is no attribute "frameborder"
    … height="250" width="900" frameborder="no" border="0" marginwidth="0" marginhe…

    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 665, Column 116: there is no attribute "border"
    …" width="900" frameborder="no" border="0" marginwidth="0" marginheight="0" scr…

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

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

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

  • Error Line 665, Column 132: there is no attribute "marginwidth"
    …ameborder="no" border="0" marginwidth="0" marginheight="0" scrolling="No"></if…

    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 665, Column 149: there is no attribute "marginheight"
    …order="no" border="0" marginwidth="0" marginheight="0" scrolling="No"></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 665, Column 163: there is no attribute "scrolling"
    …order="no" border="0" marginwidth="0" marginheight="0" scrolling="No"></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 665, Column 167: element "iframe" undefined
    …order="no" border="0" marginwidth="0" marginheight="0" scrolling="No"></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 736, Column 18: end tag for element "div" which is not open
                </div>

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

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

  • Error Line 739, Column 205: required attribute "alt" not specified
    …/www.nakedonthestreets.com/img/rightshadowtop.jpg" width="9" height="690"></td>

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

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

  • Error Line 739, Column 210: end tag for "img" omitted, but OMITTAG NO was specified
    …/www.nakedonthestreets.com/img/rightshadowtop.jpg" width="9" height="690"></td>

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

  • Info Line 739, Column 116: start tag was here
    …treets.com/img/rightshadowbottom.jpg"><img src="http://www.nakedonthestreets.c…
  • Error Line 743, Column 18: there is no attribute "align"
          <div align="center">

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

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

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

  • Error Line 748, Column 59: there is no attribute "size"
    …d height="40" align="left"><font size="1"><a href="http://www.nakedonthestreet…

    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 748, Column 62: element "font" undefined
    …eight="40" align="left"><font size="1"><a href="http://www.nakedonthestreets.c…

    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 748, Column 231: there is no attribute "align"
    …dth="28" height="13" border="0" align="absmiddle" /></a> <a href="http://www.n…

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

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

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

  • Error Line 748, Column 244: required attribute "alt" not specified
    …ht="13" border="0" align="absmiddle" /></a> <a href="http://www.nakedonthestre…

    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 749, Column 35: element "font" undefined
                        <font size="1"><a href="/report.php" style="color: #ff02d6;…

    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 750, Column 33: element "font" undefined
                      <font size="1">&copy;2012 NakedOnTheStreets.com</font> / <a h…

    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 750, Column 168: element "font" undefined
    …arget="_blank" title="public sex"><font size="1">Public Sex</font></a><br></td>

    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 750, Column 198: end tag for "br" omitted, but OMITTAG NO was specified
    …arget="_blank" title="public sex"><font size="1">Public Sex</font></a><br></td>

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

  • Info Line 750, Column 190: start tag was here
    …arget="_blank" title="public sex"><font size="1">Public Sex</font></a><br></td>
  • Error Line 782, Column 53: document type does not allow element "script" here
    <script type="text/javascript" language="JavaScript"><!-- 

    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 785, Column 53: document type does not allow element "script" here
    <script type="text/javascript" language="JavaScript"><!-- 

    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 788, Column 53: document type does not allow element "script" here
    <script type="text/javascript" language="JavaScript"><!-- 

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

Visitor Analysis

Daily Visitor
  • 4.083 visits