tienlo.com.vn

Web game Tien Hiep 2, web game online, game web, game web moi, game online tren web, game web hay, game web online, web game moi nhat, web game Tien Hiep 2. ...

Display Widget for this domain on your website. Click Here
This data was last updated from 09-07-2013 08:13:15  (update).

Overview Info

  • Domain Name
    tienlo.com.vn
  • Favicon
  • Alexa Rank
    #19527970
  • Google Page Rank
    PR 0
  • Ip Address
    118.102.1.137
  • Page Size
    41.3 KB
  • Images
    0 GIF, 9 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 7 0 0 0 0

Website Meta Analysis



  • Title
    Tien Hiep 2 – Web Game, Web Game Hay, Web Game Moi, Webgame 2012
  • Meta Keyword
  • Meta Description
    Web game Tien Hiep 2, web game online, game web, game web moi, game online tren web, game web hay, game web online, web game moi nhat, web game Tien Hiep 2.

Technical Analysis



  • Webserver
    Generation X
  • Ip Address
    118.102.1.137
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Tue, 09 Jul 2013 20:13:06 GMT
  • content-type: text/html; charset=utf-8
  • connection: close
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • pragma: no-cache
  • content-encoding: gzip
  • vary: Accept-Encoding
  • server: Generation X
  • cache-control: private, no-cache, no-store, must-revalidate
  • x-powered-by: ZCODE-
  • debug: 10.30.7.33:80
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for tienlo.com.vn

IP 118.102.1.137 Analysis

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

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 61 Errors
  • 44 Warnings
Ratio Text/Html
  • 0.7726370041136696
Message Error
  • Error Line 65, Column 127: duplicate specification of attribute "class"
    …hong-ma.html" title="Tính năng đặc sắc" class="Last">Tính năng đặc sắc</a></li>

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

  • Error Line 84, Column 135: there is no attribute "onSubmit"
    …dex.php?method=xdomain_login" target="_blank" onSubmit="return checkingbt();" >

    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 92, Column 96: end tag for "input" omitted, but OMITTAG NO was specified
    …<input type="hidden" value="http://idtienhiep2.com.vn/?m=listserver" name="u1">

    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 92, Column 17: start tag was here
                    <input type="hidden" value="http://idtienhiep2.com.vn/?m=listse…
  • Error Line 93, Column 96: end tag for "input" omitted, but OMITTAG NO was specified
    …<input type="hidden" value="http://idtienhiep2.com.vn/?m=listserver" name="fp">

    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 93, Column 17: start tag was here
                    <input type="hidden" value="http://idtienhiep2.com.vn/?m=listse…
  • Error Line 94, Column 61: end tag for "input" omitted, but OMITTAG NO was specified
                    <input type="hidden" value="121" name="pid">

    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 94, Column 17: start tag was here
                    <input type="hidden" value="121" name="pid">
  • Error Line 99, Column 76: there is no attribute "onClick"
    …vn/forgotinfo/index.121.html" onClick="_gaq.push(['_trackEvent','Quen mat khau…

    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 109, Column 108: duplicate specification of attribute "class"
    …tml" class="LinkIntro" title="Xem chi tiết" class="NotScroll">Chi tiết</a></li>

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

  • Error Line 110, Column 107: duplicate specification of attribute "class"
    …tml" class="LinkIntro" title="Xem chi tiết" class="NotScroll">Chi tiết</a></li>

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

  • Error Line 111, Column 105: duplicate specification of attribute "class"
    …tml" class="LinkIntro" title="Xem chi tiết" class="NotScroll">Chi tiết</a></li>

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

  • Error Line 112, Column 108: duplicate specification of attribute "class"
    …tml" class="LinkIntro" title="Xem chi tiết" class="NotScroll">Chi tiết</a></li>

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

  • Error Line 153, Column 10: value of attribute "id" invalid: "4" cannot start a name
    	<li id="4-2" class="ListDate">

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

  • Error Line 164, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

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

  • Info Line 164, Column 1: start tag was here
    <br>
  • Error Line 197, Column 10: value of attribute "id" invalid: "1" cannot start a name
    	<li id="13-2" class="ListDate">

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

  • Error Line 208, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

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

  • Info Line 208, Column 1: start tag was here
    <br>
  • Error Line 244, Column 10: value of attribute "id" invalid: "2" cannot start a name
    	<li id="23-2" class="ListDate">

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

  • Error Line 255, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

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

  • Info Line 255, Column 1: start tag was here
    <br>
  • Error Line 290, Column 521: end tag for "img" omitted, but OMITTAG NO was specified
    …enlo/images/modules/banner-event/440x190/cap-nhat-phien-ban-t507.jpg"></a></li>

    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 290, Column 328: start tag was here
    …ank"><span class="BorderEvent"></span><img width="440" height="190" title="Cập…
  • Error Line 292, Column 474: end tag for "img" omitted, but OMITTAG NO was specified
    ….vn/tienlo/images/modules/banner-event/440x190/server-huan-huong.jpg"></a></li>

    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 292, Column 283: start tag was here
    …ơng"><span class="BorderEvent"></span><img width="440" height="190" title="Kha…
  • Error Line 294, Column 390: end tag for "img" omitted, but OMITTAG NO was specified
    …img.zing.vn/tienlo/images/modules/banner-event/440x190/csm-click.jpg"></a></li>

    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 294, Column 241: start tag was here
    …ick"><span class="BorderEvent"></span><img width="440" height="190" title="CSM…
  • Error Line 296, Column 412: end tag for "img" omitted, but OMITTAG NO was specified
    …img.zing.vn/tienlo/images/modules/banner-event/440x190/oan-tu-xi.jpg"></a></li>

    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 296, Column 245: start tag was here
    …iên"><span class="BorderEvent"></span><img width="440" height="190" title="Oẳn…
  • Error Line 298, Column 475: end tag for "img" omitted, but OMITTAG NO was specified
    …/tienlo/images/modules/banner-event/440x190/khai-mo-may-chu-moi.jpg "></a></li>

    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 298, Column 279: start tag was here
    …mới"><span class="BorderEvent"></span><img width="440" height="190" title="Sự …
  • Error Line 318, Column 188: there is no attribute "autocomplete"
    …xIVE1M --><form action="/tim-kiem/search.html" method="get" autocomplete="off">

    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 323, Column 186: duplicate specification of attribute "class"
    …e="Nhập nội dung tìm kiếm" title="Nhập nội dung tìm kiếm" class="TextInput"  />

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

  • Error Line 330, Column 127: duplicate specification of attribute "title"
    …r" title="Máy chủ mới" target="_blank" title="Máy chủ mới">Máy chủ mới</a></h2>

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

  • Warning Line 332, Column 60: cannot generate system identifier for general entity "i"
    …ef="http://idtienhiep2.com.vn/?m=play&i=s40&pid=121&eventid=1039&bannerid=381&…

    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 332, Column 60: general entity "i" not defined and no default entity
    …ef="http://idtienhiep2.com.vn/?m=play&i=s40&pid=121&eventid=1039&bannerid=381&…

    This is usually a cascading error caused by 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 332, Column 61: reference not terminated by REFC delimiter
    …f="http://idtienhiep2.com.vn/?m=play&i=s40&pid=121&eventid=1039&bannerid=381&t…

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

  • Warning Line 332, Column 61: reference to external entity in attribute value
    …f="http://idtienhiep2.com.vn/?m=play&i=s40&pid=121&eventid=1039&bannerid=381&t…

    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 332, Column 61: reference to entity "i" for which no system identifier could be generated
    …f="http://idtienhiep2.com.vn/?m=play&i=s40&pid=121&eventid=1039&bannerid=381&t…

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

  • Info Line 332, Column 59: entity was defined here
    …ref="http://idtienhiep2.com.vn/?m=play&i=s40&pid=121&eventid=1039&bannerid=381…
  • Warning Line 332, Column 66: cannot generate system identifier for general entity "pid"
    …tp://idtienhiep2.com.vn/?m=play&i=s40&pid=121&eventid=1039&bannerid=381&type=1…

    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 332, Column 66: general entity "pid" not defined and no default entity
    …tp://idtienhiep2.com.vn/?m=play&i=s40&pid=121&eventid=1039&bannerid=381&type=1…

    This is usually a cascading error caused by 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 332, Column 69: reference not terminated by REFC delimiter
    …//idtienhiep2.com.vn/?m=play&i=s40&pid=121&eventid=1039&bannerid=381&type=1068…

    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 332, Column 69: reference to external entity in attribute value
    …//idtienhiep2.com.vn/?m=play&i=s40&pid=121&eventid=1039&bannerid=381&type=1068…

    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 332, Column 69: reference to entity "pid" for which no system identifier could be generated
    …//idtienhiep2.com.vn/?m=play&i=s40&pid=121&eventid=1039&bannerid=381&type=1068…

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

  • Info Line 332, Column 65: entity was defined here
    …ttp://idtienhiep2.com.vn/?m=play&i=s40&pid=121&eventid=1039&bannerid=381&type=…
  • Warning Line 332, Column 74: cannot generate system identifier for general entity "eventid"
    …ienhiep2.com.vn/?m=play&i=s40&pid=121&eventid=1039&bannerid=381&type=1068" tit…

    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 332, Column 74: general entity "eventid" not defined and no default entity
    …ienhiep2.com.vn/?m=play&i=s40&pid=121&eventid=1039&bannerid=381&type=1068" tit…

    This is usually a cascading error caused by 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 332, Column 81: reference not terminated by REFC delimiter
    …2.com.vn/?m=play&i=s40&pid=121&eventid=1039&bannerid=381&type=1068" title="Ảnh…

    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 332, Column 81: reference to external entity in attribute value
    …2.com.vn/?m=play&i=s40&pid=121&eventid=1039&bannerid=381&type=1068" title="Ảnh…

    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 332, Column 81: reference to entity "eventid" for which no system identifier could be generated
    …2.com.vn/?m=play&i=s40&pid=121&eventid=1039&bannerid=381&type=1068" title="Ảnh…

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

  • Info Line 332, Column 73: entity was defined here
    …tienhiep2.com.vn/?m=play&i=s40&pid=121&eventid=1039&bannerid=381&type=1068" ti…
  • Warning Line 332, Column 87: cannot generate system identifier for general entity "bannerid"
    …vn/?m=play&i=s40&pid=121&eventid=1039&bannerid=381&type=1068" title="Ảnh Tộc" …

    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 332, Column 87: general entity "bannerid" not defined and no default entity
    …vn/?m=play&i=s40&pid=121&eventid=1039&bannerid=381&type=1068" title="Ảnh Tộc" …

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

  • Warning Line 332, Column 95: reference not terminated by REFC delimiter
    …ay&i=s40&pid=121&eventid=1039&bannerid=381&type=1068" title="Ảnh Tộc" 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 332, Column 95: reference to external entity in attribute value
    …ay&i=s40&pid=121&eventid=1039&bannerid=381&type=1068" title="Ảnh Tộc" 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 332, Column 95: reference to entity "bannerid" for which no system identifier could be generated
    …ay&i=s40&pid=121&eventid=1039&bannerid=381&type=1068" title="Ảnh Tộc" 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 332, Column 86: entity was defined here
    ….vn/?m=play&i=s40&pid=121&eventid=1039&bannerid=381&type=1068" title="Ảnh Tộc"…
  • Warning Line 332, Column 100: cannot generate system identifier for general entity "type"
    …s40&pid=121&eventid=1039&bannerid=381&type=1068" title="Ảnh Tộc" target="_blan…

    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 332, Column 100: general entity "type" not defined and no default entity
    …s40&pid=121&eventid=1039&bannerid=381&type=1068" title="Ảnh Tộc" target="_blan…

    This is usually a cascading error caused by 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 332, Column 104: reference not terminated by REFC delimiter
    …pid=121&eventid=1039&bannerid=381&type=1068" title="Ảnh Tộc" target="_blank">Ả…

    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 332, Column 104: reference to external entity in attribute value
    …pid=121&eventid=1039&bannerid=381&type=1068" title="Ảnh Tộc" target="_blank">Ả…

    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 332, Column 104: reference to entity "type" for which no system identifier could be generated
    …pid=121&eventid=1039&bannerid=381&type=1068" title="Ảnh Tộc" target="_blank">Ả…

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

  • Info Line 332, Column 99: entity was defined here
    …=s40&pid=121&eventid=1039&bannerid=381&type=1068" title="Ảnh Tộc" target="_bla…
  • Warning Line 333, Column 49: reference not terminated by REFC delimiter
    …f="http://idtienhiep2.com.vn/?m=play&i=s39&pid=121&eventid=1039&bannerid=381&t…

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

  • Warning Line 333, Column 49: reference to external entity in attribute value
    …f="http://idtienhiep2.com.vn/?m=play&i=s39&pid=121&eventid=1039&bannerid=381&t…

    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 333, Column 49: reference to entity "i" for which no system identifier could be generated
    …f="http://idtienhiep2.com.vn/?m=play&i=s39&pid=121&eventid=1039&bannerid=381&t…

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

  • Info Line 332, Column 59: entity was defined here
    …ref="http://idtienhiep2.com.vn/?m=play&i=s40&pid=121&eventid=1039&bannerid=381…
  • Warning Line 333, Column 57: reference not terminated by REFC delimiter
    …//idtienhiep2.com.vn/?m=play&i=s39&pid=121&eventid=1039&bannerid=381&type=1068…

    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 333, Column 57: reference to external entity in attribute value
    …//idtienhiep2.com.vn/?m=play&i=s39&pid=121&eventid=1039&bannerid=381&type=1068…

    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 333, Column 57: reference to entity "pid" for which no system identifier could be generated
    …//idtienhiep2.com.vn/?m=play&i=s39&pid=121&eventid=1039&bannerid=381&type=1068…

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

  • Info Line 332, Column 65: entity was defined here
    …ttp://idtienhiep2.com.vn/?m=play&i=s40&pid=121&eventid=1039&bannerid=381&type=…
  • Warning Line 333, Column 69: reference not terminated by REFC delimiter
    …2.com.vn/?m=play&i=s39&pid=121&eventid=1039&bannerid=381&type=1068" title="Mộc…

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

  • Warning Line 333, Column 69: reference to external entity in attribute value
    …2.com.vn/?m=play&i=s39&pid=121&eventid=1039&bannerid=381&type=1068" title="Mộc…

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

  • Error Line 333, Column 69: reference to entity "eventid" for which no system identifier could be generated
    …2.com.vn/?m=play&i=s39&pid=121&eventid=1039&bannerid=381&type=1068" title="Mộc…

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

  • Info Line 332, Column 73: entity was defined here
    …tienhiep2.com.vn/?m=play&i=s40&pid=121&eventid=1039&bannerid=381&type=1068" ti…
  • Warning Line 333, Column 83: reference not terminated by REFC delimiter
    …ay&i=s39&pid=121&eventid=1039&bannerid=381&type=1068" title="Mộc Tộc" 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 333, Column 83: reference to external entity in attribute value
    …ay&i=s39&pid=121&eventid=1039&bannerid=381&type=1068" title="Mộc Tộc" 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 333, Column 83: reference to entity "bannerid" for which no system identifier could be generated
    …ay&i=s39&pid=121&eventid=1039&bannerid=381&type=1068" title="Mộc Tộc" 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 332, Column 86: entity was defined here
    ….vn/?m=play&i=s40&pid=121&eventid=1039&bannerid=381&type=1068" title="Ảnh Tộc"…
  • Warning Line 333, Column 92: reference not terminated by REFC delimiter
    …pid=121&eventid=1039&bannerid=381&type=1068" title="Mộc Tộc" target="_blank">M…

    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 333, Column 92: reference to external entity in attribute value
    …pid=121&eventid=1039&bannerid=381&type=1068" title="Mộc Tộc" target="_blank">M…

    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 333, Column 92: reference to entity "type" for which no system identifier could be generated
    …pid=121&eventid=1039&bannerid=381&type=1068" title="Mộc Tộc" target="_blank">M…

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

  • Info Line 332, Column 99: entity was defined here
    …=s40&pid=121&eventid=1039&bannerid=381&type=1068" title="Ảnh Tộc" target="_bla…
  • Warning Line 334, Column 49: reference not terminated by REFC delimiter
    …f="http://idtienhiep2.com.vn/?m=play&i=s38&pid=121&eventid=1039&bannerid=381&t…

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

  • Warning Line 334, Column 49: reference to external entity in attribute value
    …f="http://idtienhiep2.com.vn/?m=play&i=s38&pid=121&eventid=1039&bannerid=381&t…

    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 334, Column 49: reference to entity "i" for which no system identifier could be generated
    …f="http://idtienhiep2.com.vn/?m=play&i=s38&pid=121&eventid=1039&bannerid=381&t…

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

  • Info Line 332, Column 59: entity was defined here
    …ref="http://idtienhiep2.com.vn/?m=play&i=s40&pid=121&eventid=1039&bannerid=381…
  • Warning Line 334, Column 57: reference not terminated by REFC delimiter
    …//idtienhiep2.com.vn/?m=play&i=s38&pid=121&eventid=1039&bannerid=381&type=1068…

    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 334, Column 57: reference to external entity in attribute value
    …//idtienhiep2.com.vn/?m=play&i=s38&pid=121&eventid=1039&bannerid=381&type=1068…

    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 334, Column 57: reference to entity "pid" for which no system identifier could be generated
    …//idtienhiep2.com.vn/?m=play&i=s38&pid=121&eventid=1039&bannerid=381&type=1068…

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

  • Info Line 332, Column 65: entity was defined here
    …ttp://idtienhiep2.com.vn/?m=play&i=s40&pid=121&eventid=1039&bannerid=381&type=…
  • Warning Line 334, Column 69: reference not terminated by REFC delimiter
    …2.com.vn/?m=play&i=s38&pid=121&eventid=1039&bannerid=381&type=1068" title="Phi…

    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 334, Column 69: reference to external entity in attribute value
    …2.com.vn/?m=play&i=s38&pid=121&eventid=1039&bannerid=381&type=1068" title="Phi…

    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 334, Column 69: reference to entity "eventid" for which no system identifier could be generated
    …2.com.vn/?m=play&i=s38&pid=121&eventid=1039&bannerid=381&type=1068" title="Phi…

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

  • Info Line 332, Column 73: entity was defined here
    …tienhiep2.com.vn/?m=play&i=s40&pid=121&eventid=1039&bannerid=381&type=1068" ti…
  • Warning Line 334, Column 83: reference not terminated by REFC delimiter
    …ay&i=s38&pid=121&eventid=1039&bannerid=381&type=1068" title="Phi Linh" 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 334, Column 83: reference to external entity in attribute value
    …ay&i=s38&pid=121&eventid=1039&bannerid=381&type=1068" title="Phi Linh" 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 334, Column 83: reference to entity "bannerid" for which no system identifier could be generated
    …ay&i=s38&pid=121&eventid=1039&bannerid=381&type=1068" title="Phi Linh" 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 332, Column 86: entity was defined here
    ….vn/?m=play&i=s40&pid=121&eventid=1039&bannerid=381&type=1068" title="Ảnh Tộc"…
  • Warning Line 334, Column 92: reference not terminated by REFC delimiter
    …pid=121&eventid=1039&bannerid=381&type=1068" title="Phi Linh" target="_blank">…

    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 334, Column 92: reference to external entity in attribute value
    …pid=121&eventid=1039&bannerid=381&type=1068" title="Phi Linh" target="_blank">…

    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 334, Column 92: reference to entity "type" for which no system identifier could be generated
    …pid=121&eventid=1039&bannerid=381&type=1068" title="Phi Linh" target="_blank">…

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

  • Info Line 332, Column 99: entity was defined here
    …=s40&pid=121&eventid=1039&bannerid=381&type=1068" title="Ảnh Tộc" target="_bla…
  • Warning Line 335, Column 49: reference not terminated by REFC delimiter
    …f="http://idtienhiep2.com.vn/?m=play&i=s37&pid=121&eventid=1039&bannerid=381&t…

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

  • Warning Line 335, Column 49: reference to external entity in attribute value
    …f="http://idtienhiep2.com.vn/?m=play&i=s37&pid=121&eventid=1039&bannerid=381&t…

    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 335, Column 49: reference to entity "i" for which no system identifier could be generated
    …f="http://idtienhiep2.com.vn/?m=play&i=s37&pid=121&eventid=1039&bannerid=381&t…

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

  • Info Line 332, Column 59: entity was defined here
    …ref="http://idtienhiep2.com.vn/?m=play&i=s40&pid=121&eventid=1039&bannerid=381…
  • Warning Line 335, Column 57: reference not terminated by REFC delimiter
    …//idtienhiep2.com.vn/?m=play&i=s37&pid=121&eventid=1039&bannerid=381&type=1068…

    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 335, Column 57: reference to external entity in attribute value
    …//idtienhiep2.com.vn/?m=play&i=s37&pid=121&eventid=1039&bannerid=381&type=1068…

    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 335, Column 57: reference to entity "pid" for which no system identifier could be generated
    …//idtienhiep2.com.vn/?m=play&i=s37&pid=121&eventid=1039&bannerid=381&type=1068…

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

  • Info Line 332, Column 65: entity was defined here
    …ttp://idtienhiep2.com.vn/?m=play&i=s40&pid=121&eventid=1039&bannerid=381&type=…
  • Warning Line 335, Column 69: reference not terminated by REFC delimiter
    …2.com.vn/?m=play&i=s37&pid=121&eventid=1039&bannerid=381&type=1068" title="Thá…

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

  • Warning Line 335, Column 69: reference to external entity in attribute value
    …2.com.vn/?m=play&i=s37&pid=121&eventid=1039&bannerid=381&type=1068" title="Thá…

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

  • Error Line 335, Column 69: reference to entity "eventid" for which no system identifier could be generated
    …2.com.vn/?m=play&i=s37&pid=121&eventid=1039&bannerid=381&type=1068" title="Thá…

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

  • Info Line 332, Column 73: entity was defined here
    …tienhiep2.com.vn/?m=play&i=s40&pid=121&eventid=1039&bannerid=381&type=1068" ti…
  • Warning Line 335, Column 83: reference not terminated by REFC delimiter
    …ay&i=s37&pid=121&eventid=1039&bannerid=381&type=1068" title="Thánh Đảo" 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 335, Column 83: reference to external entity in attribute value
    …ay&i=s37&pid=121&eventid=1039&bannerid=381&type=1068" title="Thánh Đảo" 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 335, Column 83: reference to entity "bannerid" for which no system identifier could be generated
    …ay&i=s37&pid=121&eventid=1039&bannerid=381&type=1068" title="Thánh Đảo" 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 332, Column 86: entity was defined here
    ….vn/?m=play&i=s40&pid=121&eventid=1039&bannerid=381&type=1068" title="Ảnh Tộc"…
  • Warning Line 335, Column 92: reference not terminated by REFC delimiter
    …pid=121&eventid=1039&bannerid=381&type=1068" title="Thánh Đảo" target="_blank"…

    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 335, Column 92: reference to external entity in attribute value
    …pid=121&eventid=1039&bannerid=381&type=1068" title="Thánh Đảo" target="_blank"…

    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 335, Column 92: reference to entity "type" for which no system identifier could be generated
    …pid=121&eventid=1039&bannerid=381&type=1068" title="Thánh Đảo" target="_blank"…

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

  • Info Line 332, Column 99: entity was defined here
    …=s40&pid=121&eventid=1039&bannerid=381&type=1068" title="Ảnh Tộc" target="_bla…
  • Warning Line 336, Column 49: reference not terminated by REFC delimiter
    …f="http://idtienhiep2.com.vn/?m=play&i=s36&pid=121&eventid=1039&bannerid=381&t…

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

  • Warning Line 336, Column 49: reference to external entity in attribute value
    …f="http://idtienhiep2.com.vn/?m=play&i=s36&pid=121&eventid=1039&bannerid=381&t…

    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 336, Column 49: reference to entity "i" for which no system identifier could be generated
    …f="http://idtienhiep2.com.vn/?m=play&i=s36&pid=121&eventid=1039&bannerid=381&t…

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

  • Info Line 332, Column 59: entity was defined here
    …ref="http://idtienhiep2.com.vn/?m=play&i=s40&pid=121&eventid=1039&bannerid=381…
  • Warning Line 336, Column 57: reference not terminated by REFC delimiter
    …//idtienhiep2.com.vn/?m=play&i=s36&pid=121&eventid=1039&bannerid=381&type=1068…

    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 336, Column 57: reference to external entity in attribute value
    …//idtienhiep2.com.vn/?m=play&i=s36&pid=121&eventid=1039&bannerid=381&type=1068…

    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 336, Column 57: reference to entity "pid" for which no system identifier could be generated
    …//idtienhiep2.com.vn/?m=play&i=s36&pid=121&eventid=1039&bannerid=381&type=1068…

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

  • Info Line 332, Column 65: entity was defined here
    …ttp://idtienhiep2.com.vn/?m=play&i=s40&pid=121&eventid=1039&bannerid=381&type=…
  • Warning Line 336, Column 69: reference not terminated by REFC delimiter
    …2.com.vn/?m=play&i=s36&pid=121&eventid=1039&bannerid=381&type=1068" title="Thi…

    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 336, Column 69: reference to external entity in attribute value
    …2.com.vn/?m=play&i=s36&pid=121&eventid=1039&bannerid=381&type=1068" title="Thi…

    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 336, Column 69: reference to entity "eventid" for which no system identifier could be generated
    …2.com.vn/?m=play&i=s36&pid=121&eventid=1039&bannerid=381&type=1068" title="Thi…

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

  • Info Line 332, Column 73: entity was defined here
    …tienhiep2.com.vn/?m=play&i=s40&pid=121&eventid=1039&bannerid=381&type=1068" ti…
  • Warning Line 336, Column 83: reference not terminated by REFC delimiter
    …ay&i=s36&pid=121&eventid=1039&bannerid=381&type=1068" title="Thiên Hồ" 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 336, Column 83: reference to external entity in attribute value
    …ay&i=s36&pid=121&eventid=1039&bannerid=381&type=1068" title="Thiên Hồ" 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 336, Column 83: reference to entity "bannerid" for which no system identifier could be generated
    …ay&i=s36&pid=121&eventid=1039&bannerid=381&type=1068" title="Thiên Hồ" 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 332, Column 86: entity was defined here
    ….vn/?m=play&i=s40&pid=121&eventid=1039&bannerid=381&type=1068" title="Ảnh Tộc"…
  • Warning Line 336, Column 92: reference not terminated by REFC delimiter
    …pid=121&eventid=1039&bannerid=381&type=1068" title="Thiên Hồ" target="_blank">…

    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 336, Column 92: reference to external entity in attribute value
    …pid=121&eventid=1039&bannerid=381&type=1068" title="Thiên Hồ" target="_blank">…

    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 336, Column 92: reference to entity "type" for which no system identifier could be generated
    …pid=121&eventid=1039&bannerid=381&type=1068" title="Thiên Hồ" target="_blank">…

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

  • Info Line 332, Column 99: entity was defined here
    …=s40&pid=121&eventid=1039&bannerid=381&type=1068" title="Ảnh Tộc" target="_bla…
  • Error Line 350, Column 41: end tag for "select" which is not finished
                                    </select>

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

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

  • Error Line 366, Column 77: end tag for "input" omitted, but OMITTAG NO was specified
                                    <input id="server" type="hidden" value="s1">

    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 366, Column 33: start tag was here
                                    <input id="server" type="hidden" value="s1">
  • Error Line 367, Column 52: end tag for "input" omitted, but OMITTAG NO was specified
    								<input id="type" type="hidden" value="102">

    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 367, Column 9: start tag was here
    								<input id="type" type="hidden" value="102">
  • Error Line 378, Column 33: end tag for "ul" which is not finished
                                </ul>

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

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

  • Warning Line 386, Column 92: cannot generate system identifier for general entity "img_pad_r"
    …t.me.zing.vn/vip/connect?uid=72451484&img_pad_r=16&img_pad_l=10&nof=06" width=…

    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 386, Column 92: general entity "img_pad_r" not defined and no default entity
    …t.me.zing.vn/vip/connect?uid=72451484&img_pad_r=16&img_pad_l=10&nof=06" width=…

    This is usually a cascading error caused by 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 386, Column 101: reference not terminated by REFC delimiter
    ….vn/vip/connect?uid=72451484&img_pad_r=16&img_pad_l=10&nof=06" width="239" hei…

    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 386, Column 101: reference to external entity in attribute value
    ….vn/vip/connect?uid=72451484&img_pad_r=16&img_pad_l=10&nof=06" width="239" hei…

    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 386, Column 101: reference to entity "img_pad_r" for which no system identifier could be generated
    ….vn/vip/connect?uid=72451484&img_pad_r=16&img_pad_l=10&nof=06" width="239" hei…

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

  • Info Line 386, Column 91: entity was defined here
    …ct.me.zing.vn/vip/connect?uid=72451484&img_pad_r=16&img_pad_l=10&nof=06" width…
  • Warning Line 386, Column 105: cannot generate system identifier for general entity "img_pad_l"
    …vip/connect?uid=72451484&img_pad_r=16&img_pad_l=10&nof=06" width="239" height=…

    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 386, Column 105: general entity "img_pad_l" not defined and no default entity
    …vip/connect?uid=72451484&img_pad_r=16&img_pad_l=10&nof=06" width="239" height=…

    This is usually a cascading error caused by 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 386, Column 114: reference not terminated by REFC delimiter
    …ct?uid=72451484&img_pad_r=16&img_pad_l=10&nof=06" width="239" height="260" sty…

    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 386, Column 114: reference to external entity in attribute value
    …ct?uid=72451484&img_pad_r=16&img_pad_l=10&nof=06" width="239" height="260" sty…

    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 386, Column 114: reference to entity "img_pad_l" for which no system identifier could be generated
    …ct?uid=72451484&img_pad_r=16&img_pad_l=10&nof=06" width="239" height="260" sty…

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

  • Info Line 386, Column 104: entity was defined here
    …/vip/connect?uid=72451484&img_pad_r=16&img_pad_l=10&nof=06" width="239" height…
  • Warning Line 386, Column 118: cannot generate system identifier for general entity "nof"
    …id=72451484&img_pad_r=16&img_pad_l=10&nof=06" width="239" height="260" style="…

    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 386, Column 118: general entity "nof" not defined and no default entity
    …id=72451484&img_pad_r=16&img_pad_l=10&nof=06" width="239" height="260" style="…

    This is usually a cascading error caused by 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 386, Column 121: reference not terminated by REFC delimiter
    …72451484&img_pad_r=16&img_pad_l=10&nof=06" width="239" height="260" style="bor…

    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 386, Column 121: reference to external entity in attribute value
    …72451484&img_pad_r=16&img_pad_l=10&nof=06" width="239" height="260" style="bor…

    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 386, Column 121: reference to entity "nof" for which no system identifier could be generated
    …72451484&img_pad_r=16&img_pad_l=10&nof=06" width="239" height="260" style="bor…

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

  • Info Line 386, Column 117: entity was defined here
    …uid=72451484&img_pad_r=16&img_pad_l=10&nof=06" width="239" height="260" style=…
  • Error Line 387, Column 472: there is no attribute "allowTransparency"
    …w:hidden; width:239px; height:260px;" allowTransparency="true"></iframe> </div>

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

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

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

  • Error Line 666, Column 25: end tag for "ul" which is not finished
                        </ul>

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

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

  • Error Line 683, Column 94: end tag for "input" omitted, but OMITTAG NO was specified
    …      <input type="hidden" value="http://idtienhiep2.com.vn/?m=home" name="u1">

    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 683, Column 21: start tag was here
                        <input type="hidden" value="http://idtienhiep2.com.vn/?m=ho…
  • Error Line 684, Column 86: end tag for "input" omitted, but OMITTAG NO was specified
    …              <input type="hidden" value="http://idtienhiep2.com.vn" name="fp">

    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 684, Column 21: start tag was here
                        <input type="hidden" value="http://idtienhiep2.com.vn" name…
  • Error Line 685, Column 65: end tag for "input" omitted, but OMITTAG NO was specified
                        <input type="hidden" value="121" name="pid">

    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 685, Column 21: start tag was here
                        <input type="hidden" value="121" name="pid">
  • Error Line 706, Column 76: there is no attribute "allowtransparency"
    …rameborder="0" width="430" height="400" allowtransparency="1" src="#"></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.

Visitor Analysis

Daily Visitor
  • 2 visits

In Page Analysis