phimsexnhatban.org

phim sex, phimsex, phim sex nhat, phim sex nhat ban, phim sex nhật bản, phim sex hay, phim sex hot, phim sex online, xnxx, xnxx.com, xvideos, xvideos.com - Phim Sex Nhat Ban, Phim ...

This data was last updated from 02-11-2014 02:36:31  (update).

Overview Info



  • Domain Name
    phimsexnhatban.org
  • Favicon
  • Alexa Rank
    #0
  • Google Page Rank
    0
  • Ip Address
    192.99.9.60
  • Page Size
    38.3 KB
  • Images
    12 GIF, 20 JPG, 3 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 1 0 0 0 0

Website Meta Analysis



  • Title
    Phim Sex Nhat Ban, Phim sex nhat, Phim sex, Phim sex hay
  • Meta Keyword
    phim sex, phimsex, phim sex nhat, phim sex nhat ban, phim sex nhật bản, phim sex hay, phim sex hot, xxx, phim sex online, xnxx, xvideos, xvideos, xvideos.com,Phim Sex Nhat Ban, Phim sex nhat, Phim sex, Phim sex hay
  • Meta Description
    phim sex, phimsex, phim sex nhat, phim sex nhat ban, phim sex nhật bản, phim sex hay, phim sex hot, phim sex online, xnxx, xnxx.com, xvideos, xvideos.com - Phim Sex Nhat Ban, Phim sex nhat, Phim sex, Phim sex hay

Technical Analysis



  • Webserver
    Apache/2.2.27 (Unix) mod_ssl/2.2.27 OpenSSL/1.0.1e-fips mod_bwlimited/1.4 mod_fcgid/2.3.9 mod_perl/2.0.6 Perl/v5.10.1
  • Ip Address
    192.99.9.60
  • Domain Age
  • Javascript Library
    jquery, yui
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from phimsexnhatban.org.

HTML Analysis

  • date: Sun, 02 Nov 2014 14:36:29 GMT
  • server: Apache/2.2.27 (Unix) mod_ssl/2.2.27 OpenSSL/1.0.1e-fips mod_bwlimited/1.4 mod_fcgid/2.3.9 mod_perl/2.0.6 Perl/v5.10.1
  • x-powered-by: PHP/5.3.28
  • 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
  • connection: close
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for phimsexnhatban.org

IP 192.99.9.60 Analysis

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

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 111 Errors
  • 22 Warnings
Ratio Text/Html
  • 0.8498981151299032
Message Error
  • Error Line 4, Column 69: end tag for "meta" omitted, but OMITTAG NO was specified
    	<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">

    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 4, Column 2: start tag was here
    	<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  • Error Line 7, Column 250: end tag for "meta" omitted, but OMITTAG NO was specified
    …ideos, xvideos.com - Phim Sex Nhat Ban, Phim sex nhat, Phim sex, Phim sex hay">

    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 2: start tag was here
    	<meta name="description" content="phim sex, phimsex, phim sex nhat, phim sex n…
  • Error Line 8, Column 249: end tag for "meta" omitted, but OMITTAG NO was specified
    …videos, xvideos.com,Phim Sex Nhat Ban, Phim sex nhat, Phim sex, Phim sex hay"> 

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

  • Info Line 8, Column 2: start tag was here
    	<meta name="keywords" content="phim sex, phimsex, phim sex nhat, phim sex nhat…
  • Error Line 30, Column 39: required attribute "action" not specified
        	<form name="enform" method="post">

    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 31, Column 62: end tag for "input" omitted, but OMITTAG NO was specified
            <input type="hidden" name="language" value="english">

    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 31, Column 9: start tag was here
            <input type="hidden" name="language" value="english">
  • Error Line 33, Column 42: required attribute "action" not specified
            <form name="esform" method="post">

    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 34, Column 62: end tag for "input" omitted, but OMITTAG NO was specified
            <input type="hidden" name="language" value="spanish">

    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 34, Column 9: start tag was here
            <input type="hidden" name="language" value="spanish">
  • Error Line 36, Column 42: required attribute "action" not specified
            <form name="frform" method="post">

    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 37, Column 61: end tag for "input" omitted, but OMITTAG NO was specified
            <input type="hidden" name="language" value="french">

    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 37, Column 9: start tag was here
            <input type="hidden" name="language" value="french">
  • Error Line 39, Column 42: required attribute "action" not specified
            <form name="pgform" method="post">

    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 40, Column 64: end tag for "input" omitted, but OMITTAG NO was specified
            <input type="hidden" name="language" value="portugese">

    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 40, Column 9: start tag was here
            <input type="hidden" name="language" value="portugese">
  • Error Line 46, Column 145: required attribute "alt" not specified
    …bmit()"><img src="http://www.phimsexnhatban.org/images/en.png" border="0"></a> 

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

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

  • Error Line 46, Column 149: end tag for "img" omitted, but OMITTAG NO was specified
    …bmit()"><img src="http://www.phimsexnhatban.org/images/en.png" 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 46, Column 80: start tag was here
    …#" onclick="document.enform.submit()"><img src="http://www.phimsexnhatban.org/…
  • Error Line 47, Column 129: required attribute "alt" not specified
    …ubmit()"><img src="http://www.phimsexnhatban.org/images/es.png" border="0"></a>

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

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

  • Error Line 47, Column 133: end tag for "img" omitted, but OMITTAG NO was specified
    …ubmit()"><img src="http://www.phimsexnhatban.org/images/es.png" 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 47, Column 64: start tag was here
    …#" onclick="document.esform.submit()"><img src="http://www.phimsexnhatban.org/…
  • Error Line 48, Column 129: required attribute "alt" not specified
    …bmit()"><img src="http://www.phimsexnhatban.org/images/fr.png" border="0"></a> 

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

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

  • Error Line 48, Column 133: end tag for "img" omitted, but OMITTAG NO was specified
    …bmit()"><img src="http://www.phimsexnhatban.org/images/fr.png" 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 48, Column 64: start tag was here
    …#" onclick="document.frform.submit()"><img src="http://www.phimsexnhatban.org/…
  • Error Line 49, Column 129: required attribute "alt" not specified
    …ubmit()"><img src="http://www.phimsexnhatban.org/images/pg.gif" border="0"></a>

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

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

  • Error Line 49, Column 133: end tag for "img" omitted, but OMITTAG NO was specified
    …ubmit()"><img src="http://www.phimsexnhatban.org/images/pg.gif" 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 49, Column 64: start tag was here
    …#" onclick="document.pgform.submit()"><img src="http://www.phimsexnhatban.org/…
  • Error Line 86, Column 114: required attribute "alt" not specified
    …"http://www.phimsexnhatban.org/images/spacer.gif" width="1" height="2" /></div>

    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 90, Column 112: required attribute "alt" not specified
    …"http://www.phimsexnhatban.org/images/spacer.gif" width="1" height="3" /></div>

    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 92, Column 124: required attribute "alt" not specified
    …"http://www.phimsexnhatban.org/images/spacer.gif" width="1" height="3" /></div>

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

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

  • Error Line 103, Column 129: required attribute "alt" not specified
    …c='http://phimsex.biz/qc/xvideo.gif' width='240' height='120' border='0' /></a>

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

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

  • Error Line 104, Column 121: required attribute "alt" not specified
    …src='http://phimsex.biz/qc/xnxx.gif' width='240' height='120' border='0' /></a>

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

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

  • Error Line 110, Column 124: required attribute "alt" not specified
    …"http://www.phimsexnhatban.org/images/spacer.gif" width="1" height="3" /></div>

    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 114, Column 35: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
                        	<script type=text/javascript>    
  • Error Line 114, Column 40: NET-enabling start-tag not immediately followed by null end-tag
                        	<script type=text/javascript>    

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

  • Error Line 114, Column 40: document type does not allow element "script" here; assuming missing "li" start-tag
                        	<script type=text/javascript>    
  • Error Line 155, Column 21: end tag for element "script" which is not open
    												</script>

    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 156, Column 58: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    						                                                <li>

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

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

  • Error Line 157, Column 331: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …%3Bn-m%26Atilde%3Bi-.html"><img width=160 height=120 border="0" src="http://ww…
  • Error Line 157, Column 342: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ilde%3Bi-.html"><img width=160 height=120 border="0" src="http://www.phimsexnh…
  • Error Line 161, Column 67: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                			                                                <li>

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

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

  • Error Line 162, Column 356: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lde%3Bm-%26Atilde%3B.html"><img width=160 height=120 border="0" src="http://ww…
  • Error Line 162, Column 367: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …Atilde%3B.html"><img width=160 height=120 border="0" src="http://www.phimsexnh…
  • Error Line 166, Column 67: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                			                                                <li>

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

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

  • Error Line 167, Column 351: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …Atilde%3B%26sup3%3Bc.html"><img width=160 height=120 border="0" src="http://ww…
  • Error Line 167, Column 362: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …6sup3%3Bc.html"><img width=160 height=120 border="0" src="http://www.phimsexnh…
  • Error Line 171, Column 67: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                			                                                <li>

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

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

  • Error Line 172, Column 341: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …%3Bm-%26Auml%3B%91o-.html"><img width=160 height=120 border="0" src="http://ww…
  • Error Line 172, Column 352: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …l%3B%91o-.html"><img width=160 height=120 border="0" src="http://www.phimsexnh…
  • Error Line 176, Column 67: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                			                                                <li>

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

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

  • Error Line 177, Column 344: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …26AElig%3B%9Di-da-tr.html"><img width=160 height=120 border="0" src="http://ww…
  • Error Line 177, Column 355: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …9Di-da-tr.html"><img width=160 height=120 border="0" src="http://www.phimsexnh…
  • Error Line 181, Column 67: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                			                                                <li>

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

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

  • Error Line 182, Column 375: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …-x%26Auml%3B%83m-por.html"><img width=160 height=120 border="0" src="http://ww…
  • Error Line 182, Column 386: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …B%83m-por.html"><img width=160 height=120 border="0" src="http://www.phimsexnh…
  • Error Line 186, Column 67: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                			                                                <li>

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

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

  • Error Line 187, Column 316: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …tilde%3B%26sup3%3Bc-.html"><img width=160 height=120 border="0" src="http://ww…
  • Error Line 187, Column 327: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …sup3%3Bc-.html"><img width=160 height=120 border="0" src="http://www.phimsexnh…
  • Error Line 191, Column 67: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                			                                                <li>

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

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

  • Error Line 192, Column 371: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …-%26Auml%3B%91%93-ch.html"><img width=160 height=120 border="0" src="http://ww…
  • Error Line 192, Column 382: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …%91%93-ch.html"><img width=160 height=120 border="0" src="http://www.phimsexnh…
  • Error Line 196, Column 67: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                			                                                <li>

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

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

  • Error Line 197, Column 334: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …Bnh-dc-bng-mi%87ng-m.html"><img width=160 height=120 border="0" src="http://ww…
  • Error Line 197, Column 345: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …mi%87ng-m.html"><img width=160 height=120 border="0" src="http://www.phimsexnh…
  • Error Line 201, Column 67: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                			                                                <li>

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

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

  • Error Line 202, Column 350: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …tilde%3B%26sup3%3Bc-.html"><img width=160 height=120 border="0" src="http://ww…
  • Error Line 202, Column 361: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …sup3%3Bc-.html"><img width=160 height=120 border="0" src="http://www.phimsexnh…
  • Error Line 206, Column 67: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                			                                                <li>

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

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

  • Error Line 207, Column 326: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …tilde%3B%26sup3%3Bc-.html"><img width=160 height=120 border="0" src="http://ww…
  • Error Line 207, Column 337: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …sup3%3Bc-.html"><img width=160 height=120 border="0" src="http://www.phimsexnh…
  • Error Line 211, Column 67: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                			                                                <li>

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

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

  • Error Line 212, Column 310: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …se-%7C-%7C--phim-sex.html"><img width=160 height=120 border="0" src="http://ww…
  • Error Line 212, Column 321: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …-phim-sex.html"><img width=160 height=120 border="0" src="http://www.phimsexnh…
  • Error Line 216, Column 67: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                			                                                <li>

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

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

  • Error Line 217, Column 333: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ilde%3B-v%87-sinh-nu.html"><img width=160 height=120 border="0" src="http://ww…
  • Error Line 217, Column 344: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …7-sinh-nu.html"><img width=160 height=120 border="0" src="http://www.phimsexnh…
  • Error Line 221, Column 67: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                			                                                <li>

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

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

  • Error Line 222, Column 385: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …91en-x%26Atilde%3Bu-.html"><img width=160 height=120 border="0" src="http://ww…
  • Error Line 222, Column 396: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ilde%3Bu-.html"><img width=160 height=120 border="0" src="http://www.phimsexnh…
  • Error Line 226, Column 67: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                			                                                <li>

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

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

  • Error Line 227, Column 375: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …B%91en-x%26Atilde%3B.html"><img width=160 height=120 border="0" src="http://ww…
  • Error Line 227, Column 386: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …Atilde%3B.html"><img width=160 height=120 border="0" src="http://www.phimsexnh…
  • Error Line 231, Column 67: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                			                                                <li>

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

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

  • Error Line 232, Column 328: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …Bm-%26Auml%3B%91o-co.html"><img width=160 height=120 border="0" src="http://ww…
  • Error Line 232, Column 339: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …3B%91o-co.html"><img width=160 height=120 border="0" src="http://www.phimsexnh…
  • Error Line 236, Column 67: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                			                                                <li>

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

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

  • Error Line 237, Column 287: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …g-mi%87ng-quan-h%87-.html"><img width=160 height=120 border="0" src="http://ww…
  • Error Line 237, Column 298: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …uan-h%87-.html"><img width=160 height=120 border="0" src="http://www.phimsexnh…
  • Error Line 241, Column 67: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                			                                                <li>

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

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

  • Error Line 242, Column 324: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …tilde%3B%26sup3%3Bc-.html"><img width=160 height=120 border="0" src="http://ww…
  • Error Line 242, Column 335: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …sup3%3Bc-.html"><img width=160 height=120 border="0" src="http://www.phimsexnh…
  • Error Line 246, Column 67: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                			                                                <li>

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

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

  • Error Line 247, Column 328: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …tilde%3Bm-bn-threeso.html"><img width=160 height=120 border="0" src="http://ww…
  • Error Line 247, Column 339: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …n-threeso.html"><img width=160 height=120 border="0" src="http://www.phimsexnh…
  • Error Line 251, Column 67: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                			                                                <li>

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

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

  • Error Line 252, Column 317: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ng-th-d%26Atilde%3Bm.html"><img width=160 height=120 border="0" src="http://ww…
  • Error Line 252, Column 328: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …tilde%3Bm.html"><img width=160 height=120 border="0" src="http://www.phimsexnh…
  • Error Line 256, Column 40: end tag for "li" omitted, but OMITTAG NO was specified
                			                    </ul>

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

  • Info Line 114, Column 22: start tag was here
                        	<script type=text/javascript>    
  • Warning Line 260, Column 100: cannot generate system identifier for general entity "page"
    …://www.phimsexnhatban.org/videos?o=mr&page=2'>2</a></li><li><a href='http://ww…

    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 260, Column 100: general entity "page" not defined and no default entity
    …://www.phimsexnhatban.org/videos?o=mr&page=2'>2</a></li><li><a href='http://ww…

    This is usually a cascading error caused by 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 260, Column 104: reference not terminated by REFC delimiter
    …ww.phimsexnhatban.org/videos?o=mr&page=2'>2</a></li><li><a href='http://www.ph…

    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 260, Column 104: reference to external entity in attribute value
    …ww.phimsexnhatban.org/videos?o=mr&page=2'>2</a></li><li><a href='http://www.ph…

    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 260, Column 104: reference to entity "page" for which no system identifier could be generated
    …ww.phimsexnhatban.org/videos?o=mr&page=2'>2</a></li><li><a href='http://www.ph…

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

  • Info Line 260, Column 99: entity was defined here
    …p://www.phimsexnhatban.org/videos?o=mr&page=2'>2</a></li><li><a href='http://w…
  • Warning Line 260, Column 177: reference not terminated by REFC delimiter
    …ww.phimsexnhatban.org/videos?o=mr&page=3'>3</a></li><li><a href='http://www.ph…

    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 260, Column 177: reference to external entity in attribute value
    …ww.phimsexnhatban.org/videos?o=mr&page=3'>3</a></li><li><a href='http://www.ph…

    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 260, Column 177: reference to entity "page" for which no system identifier could be generated
    …ww.phimsexnhatban.org/videos?o=mr&page=3'>3</a></li><li><a href='http://www.ph…

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

  • Info Line 260, Column 99: entity was defined here
    …p://www.phimsexnhatban.org/videos?o=mr&page=2'>2</a></li><li><a href='http://w…
  • Warning Line 260, Column 250: reference not terminated by REFC delimiter
    …ww.phimsexnhatban.org/videos?o=mr&page=4'>4</a></li><li><a href='http://www.ph…

    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 260, Column 250: reference to external entity in attribute value
    …ww.phimsexnhatban.org/videos?o=mr&page=4'>4</a></li><li><a href='http://www.ph…

    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 260, Column 250: reference to entity "page" for which no system identifier could be generated
    …ww.phimsexnhatban.org/videos?o=mr&page=4'>4</a></li><li><a href='http://www.ph…

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

  • Info Line 260, Column 99: entity was defined here
    …p://www.phimsexnhatban.org/videos?o=mr&page=2'>2</a></li><li><a href='http://w…
  • Warning Line 260, Column 323: reference not terminated by REFC delimiter
    …ww.phimsexnhatban.org/videos?o=mr&page=5'>5</a></li><li><a href='http://www.ph…

    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 260, Column 323: reference to external entity in attribute value
    …ww.phimsexnhatban.org/videos?o=mr&page=5'>5</a></li><li><a href='http://www.ph…

    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 260, Column 323: reference to entity "page" for which no system identifier could be generated
    …ww.phimsexnhatban.org/videos?o=mr&page=5'>5</a></li><li><a href='http://www.ph…

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

  • Info Line 260, Column 99: entity was defined here
    …p://www.phimsexnhatban.org/videos?o=mr&page=2'>2</a></li><li><a href='http://w…
  • Warning Line 260, Column 396: reference not terminated by REFC delimiter
    …ww.phimsexnhatban.org/videos?o=mr&page=6'>6</a></li><li><a href='http://www.ph…

    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 260, Column 396: reference to external entity in attribute value
    …ww.phimsexnhatban.org/videos?o=mr&page=6'>6</a></li><li><a href='http://www.ph…

    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 260, Column 396: reference to entity "page" for which no system identifier could be generated
    …ww.phimsexnhatban.org/videos?o=mr&page=6'>6</a></li><li><a href='http://www.ph…

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

  • Info Line 260, Column 99: entity was defined here
    …p://www.phimsexnhatban.org/videos?o=mr&page=2'>2</a></li><li><a href='http://w…
  • Warning Line 260, Column 469: reference not terminated by REFC delimiter
    …ww.phimsexnhatban.org/videos?o=mr&page=7'>7</a></li><li><a href='http://www.ph…

    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 260, Column 469: reference to external entity in attribute value
    …ww.phimsexnhatban.org/videos?o=mr&page=7'>7</a></li><li><a href='http://www.ph…

    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 260, Column 469: reference to entity "page" for which no system identifier could be generated
    …ww.phimsexnhatban.org/videos?o=mr&page=7'>7</a></li><li><a href='http://www.ph…

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

  • Info Line 260, Column 99: entity was defined here
    …p://www.phimsexnhatban.org/videos?o=mr&page=2'>2</a></li><li><a href='http://w…
  • Warning Line 260, Column 542: reference not terminated by REFC delimiter
    …ww.phimsexnhatban.org/videos?o=mr&page=8'>8</a></li><li><a href='http://www.ph…

    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 260, Column 542: reference to external entity in attribute value
    …ww.phimsexnhatban.org/videos?o=mr&page=8'>8</a></li><li><a href='http://www.ph…

    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 260, Column 542: reference to entity "page" for which no system identifier could be generated
    …ww.phimsexnhatban.org/videos?o=mr&page=8'>8</a></li><li><a href='http://www.ph…

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

  • Info Line 260, Column 99: entity was defined here
    …p://www.phimsexnhatban.org/videos?o=mr&page=2'>2</a></li><li><a href='http://w…
  • Warning Line 260, Column 615: reference not terminated by REFC delimiter
    …ww.phimsexnhatban.org/videos?o=mr&page=9'>9</a></li><li><a href='http://www.ph…

    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 260, Column 615: reference to external entity in attribute value
    …ww.phimsexnhatban.org/videos?o=mr&page=9'>9</a></li><li><a href='http://www.ph…

    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 260, Column 615: reference to entity "page" for which no system identifier could be generated
    …ww.phimsexnhatban.org/videos?o=mr&page=9'>9</a></li><li><a href='http://www.ph…

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

  • Info Line 260, Column 99: entity was defined here
    …p://www.phimsexnhatban.org/videos?o=mr&page=2'>2</a></li><li><a href='http://w…
  • Warning Line 260, Column 688: reference not terminated by REFC delimiter
    …ww.phimsexnhatban.org/videos?o=mr&page=10'>10</a></li><li><a href='http://www.…

    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 260, Column 688: reference to external entity in attribute value
    …ww.phimsexnhatban.org/videos?o=mr&page=10'>10</a></li><li><a href='http://www.…

    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 260, Column 688: reference to entity "page" for which no system identifier could be generated
    …ww.phimsexnhatban.org/videos?o=mr&page=10'>10</a></li><li><a href='http://www.…

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

  • Info Line 260, Column 99: entity was defined here
    …p://www.phimsexnhatban.org/videos?o=mr&page=2'>2</a></li><li><a href='http://w…
  • Warning Line 260, Column 763: reference not terminated by REFC delimiter
    …li><a href='http://www.phimsexnhatban.org/videos?o=mr&page=2'>&gt;&gt;</a></li>

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

  • Warning Line 260, Column 763: reference to external entity in attribute value
    …li><a href='http://www.phimsexnhatban.org/videos?o=mr&page=2'>&gt;&gt;</a></li>

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

  • Error Line 260, Column 763: reference to entity "page" for which no system identifier could be generated
    …li><a href='http://www.phimsexnhatban.org/videos?o=mr&page=2'>&gt;&gt;</a></li>

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

  • Info Line 260, Column 99: entity was defined here
    …p://www.phimsexnhatban.org/videos?o=mr&page=2'>2</a></li><li><a href='http://w…
  • Error Line 263, Column 124: required attribute "alt" not specified
    …"http://www.phimsexnhatban.org/images/spacer.gif" width="1" height="3" /></div>

    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 269, Column 43: there is no attribute "allowtransparency"
    …            <iframe allowtransparency='1' frameborder='0' height='600' id='plw…

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

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

  • Info Line 276, Column 10: start tag was here
            	<br>
  • Error Line 282, Column 46: document type does not allow element "div" here; assuming missing "li" start-tag
                        	<div class="ryt-box-ins">
  • Error Line 288, Column 29: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
            				<li class="last"><a href="http://www.phimsexnhatban.org/categories"…

    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 289, Column 16: end tag for "li" omitted, but OMITTAG NO was specified
            			</ul>

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

  • Info Line 282, Column 22: start tag was here
                        	<div class="ryt-box-ins">
  • Error Line 291, Column 123: required attribute "alt" not specified
    …"http://www.phimsexnhatban.org/images/spacer.gif" width="1" height="3" /></div>

    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 303, Column 111: required attribute "alt" not specified
    …"http://www.phimsexnhatban.org/images/spacer.gif" width="1" height="2" /></div>

    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 325, Column 112: character "&" is the first character of a delimiter but occurred as data
    …p://sstatic1.histats.com/0.gif?2145061&101" alt="site stats" border="0"></a></…

    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 325, Column 149: end tag for "img" omitted, but OMITTAG NO was specified
    …tic1.histats.com/0.gif?2145061&101" alt="site stats" border="0"></a></noscript>

    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 325, Column 60: start tag was here
    …tp://www.histats.com" target="_blank"><img  src="http://sstatic1.histats.com/0…
  • Error Line 333, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body>

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

  • Info Line 28, Column 1: start tag was here
    <div id="container">

Visitor Analysis

Daily Visitor
  • 0 visits

In Page Analysis