2Sao.vn cập nhật thông tin, hình ảnh, video về hoạt động của Sao, Âm nhạc, Thời trang, Điện ảnh, Sự kiện xã hội, Đời sống xã hội, thể thao, chuyện lạ. ...

2sao.vn
  • Domain Name
    2sao.vn
  • Favicon
  • Google Page Rank
    6
  • Alexa Rank
    #13913
  • Page Size
    75.7 KB
  • Ip Address
    183.91.14.7
  • Heading
    H1: 0, H2: 0, H3: 36, H4: 0, H5: 0, H6: 0
  • Images
    28 GIF, 46 JPG, 0 PNG

Website Meta Analysis

  • Title
    Trang thông tin giải trí | 2sao | 2sao.vn
  • Meta Keyword
    Thông tin giải trí, tin giải trí, tin sao, tin âm nhạc, tin điện ảnh, tin thời trang, tin truyện sách, tin đồn, hỏi đáp, tin mới, tin nóng, tin hot, tiêu điểm
  • Meta Description
    2Sao.vn cập nhật thông tin, hình ảnh, video về hoạt động của Sao, Âm nhạc, Thời trang, Điện ảnh, Sự kiện xã hội, Đời sống xã hội, thể thao, chuyện lạ.

Technical Analysis

  • Webserver
    Microsoft-IIS/7.5
  • Ip Address
    183.91.14.7
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from 2sao.vn.

HTML Analysis

  • cache-control: private
  • content-type: text/html; charset=utf-8
  • content-encoding: gzip
  • server: Microsoft-IIS/7.5
  • x-aspnet-version: 4.0.30319
  • x-powered-by: ASP.NET
  • date: Sat, 17 Aug 2013 02:32:45 GMT
  • content-length: 19463
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for 2sao.vn

DNS Analysis


DNS servers
dns2.srv.vietnamnet.vn [203.162.71.38]
dns1.srv.vietnamnet.vn [123.30.184.3]

DNS Records

Answer records
2sao.vn SOA
server: dns1.srv.vietnamnet.vn
email: sysadmin@vietnamnet.vn
serial: 1290439585
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 38400
38400s
2sao.vn NS  dns1.srv.vietnamnet.vn 38400s
2sao.vn NS  dns2.srv.vietnamnet.vn 38400s
2sao.vn A 183.91.14.7 38400s
2sao.vn A 183.91.14.17 38400s
2sao.vn A 183.91.14.5 38400s

Authority records

Additional records
dns1.srv.vietnamnet.vn A 123.30.184.3 3600s
dns2.srv.vietnamnet.vn A 203.162.71.38 3600s

IP 183.91.14.7 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 111 Errors
  • 121 Warnings
Ratio Text/Html
  • 0.716902044238086
Message Error
  • Error Line 6, Column 52: required attribute "content" not specified
    … id="description" name="description" /><meta id="keywords" name="keywords" CON…

    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 6, Column 97: there is no attribute "CONTENT"
    …id="keywords" name="keywords" CONTENT="Thông tin giải trí, tin giải trí, tin s…

    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 6, Column 262: required attribute "content" not specified
    …ới, tin nóng, tin hot, tiêu điểm, …" /><meta content="INDEX,FOLLOW" name="robo…

    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 23, Column 30: required attribute "type" not specified
    <script language='javascript'>RandomTheme();</script></head>

    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 38, Column 54: required attribute "alt" not specified
      <img src="http://static.2sao.vn/Images/blank.gif" /></a></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 39, Column 173: cannot generate system identifier for general entity "id"
    …hai-hoi-tu-tet-quy-ty-tren-mytv%2f473&id=868' target='_blank'><img src="http:/…

    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 39, Column 173: general entity "id" not defined and no default entity
    …hai-hoi-tu-tet-quy-ty-tren-mytv%2f473&id=868' target='_blank'><img src="http:/…

    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 39, Column 175: reference not terminated by REFC delimiter
    …i-hoi-tu-tet-quy-ty-tren-mytv%2f473&id=868' target='_blank'><img src="http://2…

    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 39, Column 175: reference to external entity in attribute value
    …i-hoi-tu-tet-quy-ty-tren-mytv%2f473&id=868' target='_blank'><img src="http://2…

    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 39, Column 175: reference to entity "id" for which no system identifier could be generated
    …i-hoi-tu-tet-quy-ty-tren-mytv%2f473&id=868' target='_blank'><img src="http://2…

    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 39, Column 172: entity was defined here
    …-hai-hoi-tu-tet-quy-ty-tren-mytv%2f473&id=868' target='_blank'><img src="http:…
  • Error Line 39, Column 307: required attribute "alt" not specified
    …3/01/15/11/10/mytvtet728x90.jpg" border="0" height='90' width="728"/></a></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 95, Column 178: required attribute "alt" not specified
    …_blank'><img src='http://static.2sao.vn/Images/vietnamnet.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 98, Column 92: required attribute "alt" not specified
    …ic.2sao.vn/Images/blank.gif" width="54px" height="26px" border="0" /></a><input

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

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

  • Error Line 99, Column 35: there is no attribute "first"
       onfocus="ShowText(this)" first="1" value="Tìm kiếm" onkeypress="return doCli…

    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 102, Column 56: required attribute "alt" not specified
      style="cursor: pointer; width: 16px; height: 16px;" />

    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 108, Column 155: cannot generate system identifier for general entity "ext"
    …=0e9043c1-4f14-4cc5-ac07-b832adf03391&ext=5580991b-9fb4-473a-9e0e-c49cd1cf7473…

    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 108, Column 155: general entity "ext" not defined and no default entity
    …=0e9043c1-4f14-4cc5-ac07-b832adf03391&ext=5580991b-9fb4-473a-9e0e-c49cd1cf7473…

    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 108, Column 158: reference not terminated by REFC delimiter
    …9043c1-4f14-4cc5-ac07-b832adf03391&ext=5580991b-9fb4-473a-9e0e-c49cd1cf7473&do…

    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 108, Column 158: reference to external entity in attribute value
    …9043c1-4f14-4cc5-ac07-b832adf03391&ext=5580991b-9fb4-473a-9e0e-c49cd1cf7473&do…

    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 108, Column 158: reference to entity "ext" for which no system identifier could be generated
    …9043c1-4f14-4cc5-ac07-b832adf03391&ext=5580991b-9fb4-473a-9e0e-c49cd1cf7473&do…

    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 108, Column 154: entity was defined here
    …n=0e9043c1-4f14-4cc5-ac07-b832adf03391&ext=5580991b-9fb4-473a-9e0e-c49cd1cf747…
  • Warning Line 108, Column 196: cannot generate system identifier for general entity "domain"
    …&ext=5580991b-9fb4-473a-9e0e-c49cd1cf7473&domain=http://2sao.vn/cat0"></script>

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

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

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

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

  • Error Line 108, Column 196: general entity "domain" not defined and no default entity
    …&ext=5580991b-9fb4-473a-9e0e-c49cd1cf7473&domain=http://2sao.vn/cat0"></script>

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

  • Warning Line 108, Column 202: reference not terminated by REFC delimiter
    …&ext=5580991b-9fb4-473a-9e0e-c49cd1cf7473&domain=http://2sao.vn/cat0"></script>

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

  • Warning Line 108, Column 202: reference to external entity in attribute value
    …&ext=5580991b-9fb4-473a-9e0e-c49cd1cf7473&domain=http://2sao.vn/cat0"></script>

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

  • Error Line 108, Column 202: reference to entity "domain" for which no system identifier could be generated
    …&ext=5580991b-9fb4-473a-9e0e-c49cd1cf7473&domain=http://2sao.vn/cat0"></script>

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

  • Info Line 108, Column 195: entity was defined here
    …&ext=5580991b-9fb4-473a-9e0e-c49cd1cf7473&domain=http://2sao.vn/cat0"></script>
  • Error Line 115, Column 22: an attribute specification must start with a name or name token
     document.write('<scr' + 'ipt src="' + src + '"></scr' + 'ipt>');

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 115, Column 22: element "scr" undefined
     document.write('<scr' + 'ipt src="' + src + '"></scr' + 'ipt>');

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 115, Column 54: delimiter "'" invalid: only S separators and TAGC allowed here
     document.write('<scr' + 'ipt src="' + src + '"></scr' + 'ipt>');
  • Error Line 177, Column 71: required attribute "alt" not specified
     <a id="cat1000" href="/p0c1000/Sao.vnn"><img src="/Images/blank.gif"/></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 179, Column 662: there is no attribute "onerror"
    …4/07/38/220213vayava_120.jpg" onerror="LoadImage(this,'http://imgthumb.2sao.vi…

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

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

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

  • Warning Line 179, Column 825: cannot generate system identifier for general entity "width"
    …f02%2f24%2f07%2f38%2f220213vayava.jpg&width=120')" title="Mỹ nh&#226;n H&#224;…

    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 179, Column 825: general entity "width" not defined and no default entity
    …f02%2f24%2f07%2f38%2f220213vayava.jpg&width=120')" title="Mỹ nh&#226;n H&#224;…

    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 179, Column 830: reference not terminated by REFC delimiter
    …f24%2f07%2f38%2f220213vayava.jpg&width=120')" title="Mỹ nh&#226;n H&#224;n v&#…

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

  • Warning Line 179, Column 830: reference to external entity in attribute value
    …f24%2f07%2f38%2f220213vayava.jpg&width=120')" title="Mỹ nh&#226;n H&#224;n v&#…

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

  • Error Line 179, Column 830: reference to entity "width" for which no system identifier could be generated
    …f24%2f07%2f38%2f220213vayava.jpg&width=120')" title="Mỹ nh&#226;n H&#224;n v&#…

    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 179, Column 824: entity was defined here
    …2f02%2f24%2f07%2f38%2f220213vayava.jpg&width=120')" title="Mỹ nh&#226;n H&#224…
  • Warning Line 179, Column 1969: reference not terminated by REFC delimiter
    …2f24%2f07%2f32%2f230213qkava.jpg&width=120')" title="Ảnh qu&#225; khứ của Han …

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

  • Warning Line 179, Column 1969: reference to external entity in attribute value
    …2f24%2f07%2f32%2f230213qkava.jpg&width=120')" title="Ảnh qu&#225; khứ của Han …

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

  • Error Line 179, Column 1969: reference to entity "width" for which no system identifier could be generated
    …2f24%2f07%2f32%2f230213qkava.jpg&width=120')" title="Ảnh qu&#225; khứ của Han …

    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 179, Column 824: entity was defined here
    …2f02%2f24%2f07%2f38%2f220213vayava.jpg&width=120')" title="Mỹ nh&#226;n H&#224…
  • Error Line 186, Column 62: required attribute "alt" not specified
        <img src="/Images/blank.gif" width="10px" height="10px" />

    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 191, Column 82: required attribute "alt" not specified
    …"cat1048" href="/p0c1048/su-kien-xa-hoi.vnn"><img src="/Images/blank.gif"/></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>.

  • Warning Line 193, Column 677: reference not terminated by REFC delimiter
    …013%2f02%2f23%2f11%2f24%2ftc.jpg&width=120')" title="L&#225;i thu&#234; xe con…

    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 193, Column 677: reference to external entity in attribute value
    …013%2f02%2f23%2f11%2f24%2ftc.jpg&width=120')" title="L&#225;i thu&#234; xe con…

    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 193, Column 677: reference to entity "width" for which no system identifier could be generated
    …013%2f02%2f23%2f11%2f24%2ftc.jpg&width=120')" title="L&#225;i thu&#234; xe con…

    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 179, Column 824: entity was defined here
    …2f02%2f24%2f07%2f38%2f220213vayava.jpg&width=120')" title="Mỹ nh&#226;n H&#224…
  • Warning Line 193, Column 1604: reference not terminated by REFC delimiter
    …013%2f02%2f23%2f10%2f14%2flr.jpg&width=120')" title="Đứng chờ xe bu&#253;t, 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 193, Column 1604: reference to external entity in attribute value
    …013%2f02%2f23%2f10%2f14%2flr.jpg&width=120')" title="Đứng chờ xe bu&#253;t, 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 193, Column 1604: reference to entity "width" for which no system identifier could be generated
    …013%2f02%2f23%2f10%2f14%2flr.jpg&width=120')" title="Đứng chờ xe bu&#253;t, 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 179, Column 824: entity was defined here
    …2f02%2f24%2f07%2f38%2f220213vayava.jpg&width=120')" title="Mỹ nh&#226;n H&#224…
  • Error Line 212, Column 62: required attribute "alt" not specified
        <img src="/Images/blank.gif" width="10px" height="10px" />

    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 219, Column 85: required attribute "alt" not specified
    …t1049" href="/p0c1049/doi-song-gioi-tre.vnn"><img src="/Images/blank.gif"/></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>.

  • Warning Line 221, Column 763: reference not terminated by REFC delimiter
    …013%2f02%2f23%2f11%2f43%2fta.jpg&width=120')" title="Ch&#224;ng trai 25 tuổi v…

    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 221, Column 763: reference to external entity in attribute value
    …013%2f02%2f23%2f11%2f43%2fta.jpg&width=120')" title="Ch&#224;ng trai 25 tuổi v…

    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 221, Column 763: reference to entity "width" for which no system identifier could be generated
    …013%2f02%2f23%2f11%2f43%2fta.jpg&width=120')" title="Ch&#224;ng trai 25 tuổi v…

    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 179, Column 824: entity was defined here
    …2f02%2f24%2f07%2f38%2f220213vayava.jpg&width=120')" title="Mỹ nh&#226;n H&#224…
  • Warning Line 221, Column 1790: reference not terminated by REFC delimiter
    …13%2f02%2f23%2f11%2f36%2fgta.jpg&width=120')" title="Giới trẻ phẫu thuật chuyể…

    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 221, Column 1790: reference to external entity in attribute value
    …13%2f02%2f23%2f11%2f36%2fgta.jpg&width=120')" title="Giới trẻ phẫu thuật chuyể…

    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 221, Column 1790: reference to entity "width" for which no system identifier could be generated
    …13%2f02%2f23%2f11%2f36%2fgta.jpg&width=120')" title="Giới trẻ phẫu thuật chuyể…

    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 179, Column 824: entity was defined here
    …2f02%2f24%2f07%2f38%2f220213vayava.jpg&width=120')" title="Mỹ nh&#226;n H&#224…
  • Error Line 230, Column 78: required attribute "alt" not specified
    … id="cat1004" href="/p0c1004/thoi-trang.vnn"><img src="/Images/blank.gif"/></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>.

  • Warning Line 232, Column 637: reference not terminated by REFC delimiter
    …13%2f02%2f24%2f07%2f52%2fava.jpg&width=120')" title="Diễn vi&#234;n Nhất chi 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 232, Column 637: reference to external entity in attribute value
    …13%2f02%2f24%2f07%2f52%2fava.jpg&width=120')" title="Diễn vi&#234;n Nhất chi 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 232, Column 637: reference to entity "width" for which no system identifier could be generated
    …13%2f02%2f24%2f07%2f52%2fava.jpg&width=120')" title="Diễn vi&#234;n Nhất chi 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 179, Column 824: entity was defined here
    …2f02%2f24%2f07%2f38%2f220213vayava.jpg&width=120')" title="Mỹ nh&#226;n H&#224…
  • Warning Line 232, Column 1590: reference not terminated by REFC delimiter
    …f24%2f07%2f21%2f240213saoava.jpg&width=120')" title="Soi v&#225;y h&#224;ng hi…

    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 232, Column 1590: reference to external entity in attribute value
    …f24%2f07%2f21%2f240213saoava.jpg&width=120')" title="Soi v&#225;y h&#224;ng hi…

    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 232, Column 1590: reference to entity "width" for which no system identifier could be generated
    …f24%2f07%2f21%2f240213saoava.jpg&width=120')" title="Soi v&#225;y h&#224;ng hi…

    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 179, Column 824: entity was defined here
    …2f02%2f24%2f07%2f38%2f220213vayava.jpg&width=120')" title="Mỹ nh&#226;n H&#224…
  • Error Line 251, Column 62: required attribute "alt" not specified
        <img src="/Images/blank.gif" width="10px" height="10px" />

    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 261, Column 62: required attribute "alt" not specified
        <img src="/Images/blank.gif" width="10px" height="10px" />

    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 268, Column 75: required attribute "alt" not specified
     <a id="cat1001" href="/p0c1001/Am-nhac.vnn"><img src="/Images/blank.gif"/></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>.

  • Warning Line 270, Column 596: reference not terminated by REFC delimiter
    …2%2f23%2f09%2f08%2f2302MTAva.jpg&width=120')" title="V-Pop: Ca sĩ khốn đốn với…

    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 270, Column 596: reference to external entity in attribute value
    …2%2f23%2f09%2f08%2f2302MTAva.jpg&width=120')" title="V-Pop: Ca sĩ khốn đốn với…

    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 270, Column 596: reference to entity "width" for which no system identifier could be generated
    …2%2f23%2f09%2f08%2f2302MTAva.jpg&width=120')" title="V-Pop: Ca sĩ khốn đốn với…

    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 179, Column 824: entity was defined here
    …2f02%2f24%2f07%2f38%2f220213vayava.jpg&width=120')" title="Mỹ nh&#226;n H&#224…
  • Warning Line 270, Column 1507: reference not terminated by REFC delimiter
    …f02%2f22%2f11%2f18%2fGMTQava.jpg&width=120')" title=" Mỹ Linh, Đức Huy đấu khẩ…

    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 270, Column 1507: reference to external entity in attribute value
    …f02%2f22%2f11%2f18%2fGMTQava.jpg&width=120')" title=" Mỹ Linh, Đức Huy đấu khẩ…

    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 270, Column 1507: reference to entity "width" for which no system identifier could be generated
    …f02%2f22%2f11%2f18%2fGMTQava.jpg&width=120')" title=" Mỹ Linh, Đức Huy đấu khẩ…

    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 179, Column 824: entity was defined here
    …2f02%2f24%2f07%2f38%2f220213vayava.jpg&width=120')" title="Mỹ nh&#226;n H&#224…
  • Error Line 279, Column 72: required attribute "alt" not specified
     <a id="cat1002" href="/p0c1002/phim.vnn"><img src="/Images/blank.gif"/></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>.

  • Warning Line 281, Column 733: reference not terminated by REFC delimiter
    …13%2f02%2f22%2f14%2f16%2fava.jpg&width=120')" title="Khoảnh khắc đ&#225;ng y&#…

    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 281, Column 733: reference to external entity in attribute value
    …13%2f02%2f22%2f14%2f16%2fava.jpg&width=120')" title="Khoảnh khắc đ&#225;ng y&#…

    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 281, Column 733: reference to entity "width" for which no system identifier could be generated
    …13%2f02%2f22%2f14%2f16%2fava.jpg&width=120')" title="Khoảnh khắc đ&#225;ng y&#…

    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 179, Column 824: entity was defined here
    …2f02%2f24%2f07%2f38%2f220213vayava.jpg&width=120')" title="Mỹ nh&#226;n H&#224…
  • Warning Line 281, Column 1764: reference not terminated by REFC delimiter
    …13%2f02%2f21%2f14%2f50%2fava.jpg&width=120')" title="Tạo h&#236;nh với sườn x&…

    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 281, Column 1764: reference to external entity in attribute value
    …13%2f02%2f21%2f14%2f50%2fava.jpg&width=120')" title="Tạo h&#236;nh với sườn x&…

    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 281, Column 1764: reference to entity "width" for which no system identifier could be generated
    …13%2f02%2f21%2f14%2f50%2fava.jpg&width=120')" title="Tạo h&#236;nh với sườn x&…

    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 179, Column 824: entity was defined here
    …2f02%2f24%2f07%2f38%2f220213vayava.jpg&width=120')" title="Mỹ nh&#226;n H&#224…
  • Error Line 300, Column 62: required attribute "alt" not specified
        <img src="/Images/blank.gif" width="10px" height="10px" />

    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 307, Column 76: required attribute "alt" not specified
     <a id="cat1051" href="/p0c1051/the-thao.vnn"><img src="/Images/blank.gif"/></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>.

  • Warning Line 309, Column 618: reference not terminated by REFC delimiter
    …13%2f02%2f23%2f10%2f48%2fbca.jpg&width=120')" title="Bồ cũ Forlan “e thẹn” kho…

    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 309, Column 618: reference to external entity in attribute value
    …13%2f02%2f23%2f10%2f48%2fbca.jpg&width=120')" title="Bồ cũ Forlan “e thẹn” kho…

    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 309, Column 618: reference to entity "width" for which no system identifier could be generated
    …13%2f02%2f23%2f10%2f48%2fbca.jpg&width=120')" title="Bồ cũ Forlan “e thẹn” kho…

    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 179, Column 824: entity was defined here
    …2f02%2f24%2f07%2f38%2f220213vayava.jpg&width=120')" title="Mỹ nh&#226;n H&#224…
  • Warning Line 309, Column 1442: reference not terminated by REFC delimiter
    …f02%2f23%2f10%2f40%2ftna+(2).jpg&width=120')" title="Oscar Pistorius được tại …

    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 309, Column 1442: reference to external entity in attribute value
    …f02%2f23%2f10%2f40%2ftna+(2).jpg&width=120')" title="Oscar Pistorius được tại …

    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 309, Column 1442: reference to entity "width" for which no system identifier could be generated
    …f02%2f23%2f10%2f40%2ftna+(2).jpg&width=120')" title="Oscar Pistorius được tại …

    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 179, Column 824: entity was defined here
    …2f02%2f24%2f07%2f38%2f220213vayava.jpg&width=120')" title="Mỹ nh&#226;n H&#224…
  • Error Line 318, Column 77: required attribute "alt" not specified
    …a id="cat1052" href="/p0c1052/chuyen-la.vnn"><img src="/Images/blank.gif"/></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>.

  • Warning Line 320, Column 570: reference not terminated by REFC delimiter
    …13%2f02%2f23%2f11%2f08%2fCHA.jpg&width=120')" title="10 chuồng nhốt… người kiể…

    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 320, Column 570: reference to external entity in attribute value
    …13%2f02%2f23%2f11%2f08%2fCHA.jpg&width=120')" title="10 chuồng nhốt… người kiể…

    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 320, Column 570: reference to entity "width" for which no system identifier could be generated
    …13%2f02%2f23%2f11%2f08%2fCHA.jpg&width=120')" title="10 chuồng nhốt… người kiể…

    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 179, Column 824: entity was defined here
    …2f02%2f24%2f07%2f38%2f220213vayava.jpg&width=120')" title="Mỹ nh&#226;n H&#224…
  • Warning Line 320, Column 1438: reference not terminated by REFC delimiter
    …013%2f02%2f23%2f09%2f29%2fch.jpg&width=120')" title="Ch&#243; tử vong trong l&…

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

  • Warning Line 320, Column 1438: reference to external entity in attribute value
    …013%2f02%2f23%2f09%2f29%2fch.jpg&width=120')" title="Ch&#243; tử vong trong l&…

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

  • Error Line 320, Column 1438: reference to entity "width" for which no system identifier could be generated
    …013%2f02%2f23%2f09%2f29%2fch.jpg&width=120')" title="Ch&#243; tử vong trong l&…

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

  • Info Line 179, Column 824: entity was defined here
    …2f02%2f24%2f07%2f38%2f220213vayava.jpg&width=120')" title="Mỹ nh&#226;n H&#224…
  • Error Line 339, Column 62: required attribute "alt" not specified
        <img src="/Images/blank.gif" width="10px" height="10px" />

    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 346, Column 75: required attribute "alt" not specified
     <a id="cat1005" href="/p0c1005/hoi-dap.vnn"><img src="/Images/blank.gif"/></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>.

  • Warning Line 348, Column 563: reference not terminated by REFC delimiter
    …f02%2f23%2f10%2f59%2fHUA+(2).jpg&width=120')" title="H&#244;n h&#237;t... t&#2…

    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 348, Column 563: reference to external entity in attribute value
    …f02%2f23%2f10%2f59%2fHUA+(2).jpg&width=120')" title="H&#244;n h&#237;t... t&#2…

    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 348, Column 563: reference to entity "width" for which no system identifier could be generated
    …f02%2f23%2f10%2f59%2fHUA+(2).jpg&width=120')" title="H&#244;n h&#237;t... t&#2…

    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 179, Column 824: entity was defined here
    …2f02%2f24%2f07%2f38%2f220213vayava.jpg&width=120')" title="Mỹ nh&#226;n H&#224…
  • Warning Line 349, Column 655: reference not terminated by REFC delimiter
    …13%2f02%2f23%2f10%2f11%2ftva.jpg&width=120')" title="Ch&#249;m ảnh: Tự do bay …

    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 349, Column 655: reference to external entity in attribute value
    …13%2f02%2f23%2f10%2f11%2ftva.jpg&width=120')" title="Ch&#249;m ảnh: Tự do bay …

    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 349, Column 655: reference to entity "width" for which no system identifier could be generated
    …13%2f02%2f23%2f10%2f11%2ftva.jpg&width=120')" title="Ch&#249;m ảnh: Tự do bay …

    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 179, Column 824: entity was defined here
    …2f02%2f24%2f07%2f38%2f220213vayava.jpg&width=120')" title="Mỹ nh&#226;n H&#224…
  • Warning Line 360, Column 159: cannot generate system identifier for general entity "utm_medium"
    …//tintuconline.com.vn?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_conten…

    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 360, Column 159: general entity "utm_medium" not defined and no default entity
    …//tintuconline.com.vn?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_conten…

    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 360, Column 169: reference not terminated by REFC delimiter
    …line.com.vn?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm…

    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 360, Column 169: reference to external entity in attribute value
    …line.com.vn?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm…

    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 360, Column 169: reference to entity "utm_medium" for which no system identifier could be generated
    …line.com.vn?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm…

    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 360, Column 158: entity was defined here
    …://tintuconline.com.vn?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_conte…
  • Warning Line 360, Column 175: cannot generate system identifier for general entity "utm_term"
    …om.vn?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campa…

    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 360, Column 175: general entity "utm_term" not defined and no default entity
    …om.vn?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campa…

    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 360, Column 183: reference not terminated by REFC delimiter
    …m_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao…

    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 360, Column 183: reference to external entity in attribute value
    …m_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao…

    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 360, Column 183: reference to entity "utm_term" for which no system identifier could be generated
    …m_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao…

    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 360, Column 174: entity was defined here
    …com.vn?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_camp…
  • Warning Line 360, Column 189: cannot generate system identifier for general entity "utm_content"
    …ce=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao"><img…

    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 360, Column 189: general entity "utm_content" not defined and no default entity
    …ce=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao"><img…

    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 360, Column 200: reference not terminated by REFC delimiter
    …_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao"><img src="/Imag…

    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 360, Column 200: reference to external entity in attribute value
    …_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao"><img src="/Imag…

    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 360, Column 200: reference to entity "utm_content" for which no system identifier could be generated
    …_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao"><img src="/Imag…

    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 360, Column 188: entity was defined here
    …rce=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao"><im…
  • Warning Line 360, Column 206: cannot generate system identifier for general entity "utm_campaign"
    …m=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao"><img src="/Images/bla…

    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 360, Column 206: general entity "utm_campaign" not defined and no default entity
    …m=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao"><img src="/Images/bla…

    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 360, Column 218: reference not terminated by REFC delimiter
    …erm=2Sao&utm_content=2Sao&utm_campaign=2Sao"><img src="/Images/blank.gif"/></a…

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

  • Warning Line 360, Column 218: reference to external entity in attribute value
    …erm=2Sao&utm_content=2Sao&utm_campaign=2Sao"><img src="/Images/blank.gif"/></a…

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

  • Error Line 360, Column 218: reference to entity "utm_campaign" for which no system identifier could be generated
    …erm=2Sao&utm_content=2Sao&utm_campaign=2Sao"><img src="/Images/blank.gif"/></a…

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

  • Info Line 360, Column 205: entity was defined here
    …um=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao"><img src="/Images/bl…
  • Error Line 360, Column 254: required attribute "alt" not specified
    …erm=2Sao&utm_content=2Sao&utm_campaign=2Sao"><img src="/Images/blank.gif"/></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>.

  • Warning Line 362, Column 155: reference not terminated by REFC delimiter
    …i-song.html?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm…

    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 362, Column 155: reference to external entity in attribute value
    …i-song.html?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm…

    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 362, Column 155: reference to entity "utm_medium" for which no system identifier could be generated
    …i-song.html?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm…

    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 360, Column 158: entity was defined here
    …://tintuconline.com.vn?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_conte…
  • Warning Line 362, Column 169: reference not terminated by REFC delimiter
    …m_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao…

    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 362, Column 169: reference to external entity in attribute value
    …m_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao…

    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 362, Column 169: reference to entity "utm_term" for which no system identifier could be generated
    …m_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao…

    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 360, Column 174: entity was defined here
    …com.vn?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_camp…
  • Warning Line 362, Column 186: reference not terminated by REFC delimiter
    …_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao" 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 362, Column 186: reference to external entity in attribute value
    …_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao" 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 362, Column 186: reference to entity "utm_content" for which no system identifier could be generated
    …_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao" 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 360, Column 188: entity was defined here
    …rce=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao"><im…
  • Warning Line 362, Column 204: reference not terminated by REFC delimiter
    …erm=2Sao&utm_content=2Sao&utm_campaign=2Sao" target="_blank" class="title_home…

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

  • Warning Line 362, Column 204: reference to external entity in attribute value
    …erm=2Sao&utm_content=2Sao&utm_campaign=2Sao" target="_blank" class="title_home…

    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 362, Column 204: reference to entity "utm_campaign" for which no system identifier could be generated
    …erm=2Sao&utm_content=2Sao&utm_campaign=2Sao" target="_blank" class="title_home…

    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 360, Column 205: entity was defined here
    …um=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao"><img src="/Images/bl…
  • Warning Line 362, Column 583: reference not terminated by REFC delimiter
    …i-song.html?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm…

    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 362, Column 583: reference to external entity in attribute value
    …i-song.html?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm…

    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 362, Column 583: reference to entity "utm_medium" for which no system identifier could be generated
    …i-song.html?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm…

    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 360, Column 158: entity was defined here
    …://tintuconline.com.vn?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_conte…
  • Warning Line 362, Column 597: reference not terminated by REFC delimiter
    …m_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao…

    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 362, Column 597: reference to external entity in attribute value
    …m_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao…

    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 362, Column 597: reference to entity "utm_term" for which no system identifier could be generated
    …m_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao…

    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 360, Column 174: entity was defined here
    …com.vn?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_camp…
  • Warning Line 362, Column 614: reference not terminated by REFC delimiter
    …_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao"><img src="http:…

    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 362, Column 614: reference to external entity in attribute value
    …_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao"><img src="http:…

    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 362, Column 614: reference to entity "utm_content" for which no system identifier could be generated
    …_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao"><img src="http:…

    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 360, Column 188: entity was defined here
    …rce=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao"><im…
  • Warning Line 362, Column 632: reference not terminated by REFC delimiter
    …erm=2Sao&utm_content=2Sao&utm_campaign=2Sao"><img src="http://imgthumb.2sao.vi…

    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 362, Column 632: reference to external entity in attribute value
    …erm=2Sao&utm_content=2Sao&utm_campaign=2Sao"><img src="http://imgthumb.2sao.vi…

    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 362, Column 632: reference to entity "utm_campaign" for which no system identifier could be generated
    …erm=2Sao&utm_content=2Sao&utm_campaign=2Sao"><img src="http://imgthumb.2sao.vi…

    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 360, Column 205: entity was defined here
    …um=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao"><img src="/Images/bl…
  • Warning Line 362, Column 920: reference not terminated by REFC delimiter
    …013%2f02%2f23%2f21%2f14%2f14.jpg&width=120')" title=" Giết mẹ bạn g&#225;i, d&…

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

  • Warning Line 362, Column 920: reference to external entity in attribute value
    …013%2f02%2f23%2f21%2f14%2f14.jpg&width=120')" title=" Giết mẹ bạn g&#225;i, d&…

    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 362, Column 920: reference to entity "width" for which no system identifier could be generated
    …013%2f02%2f23%2f21%2f14%2f14.jpg&width=120')" title=" Giết mẹ bạn g&#225;i, d&…

    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 179, Column 824: entity was defined here
    …2f02%2f24%2f07%2f38%2f220213vayava.jpg&width=120')" title="Mỹ nh&#226;n H&#224…
  • Error Line 362, Column 1004: required attribute "alt" not specified
    … x&#225;c dưới s&#244;ng " border="0"/></a><p> Bị mẹ người yêu ngăn cấm tình c…

    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 364, Column 162: reference not terminated by REFC delimiter
    …-xuong.html?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm…

    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 364, Column 162: reference to external entity in attribute value
    …-xuong.html?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm…

    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 364, Column 162: reference to entity "utm_medium" for which no system identifier could be generated
    …-xuong.html?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm…

    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 360, Column 158: entity was defined here
    …://tintuconline.com.vn?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_conte…
  • Warning Line 364, Column 176: reference not terminated by REFC delimiter
    …m_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao…

    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 364, Column 176: reference to external entity in attribute value
    …m_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao…

    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 364, Column 176: reference to entity "utm_term" for which no system identifier could be generated
    …m_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao…

    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 360, Column 174: entity was defined here
    …com.vn?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_camp…
  • Warning Line 364, Column 193: reference not terminated by REFC delimiter
    …_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao" 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 364, Column 193: reference to external entity in attribute value
    …_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao" 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 364, Column 193: reference to entity "utm_content" for which no system identifier could be generated
    …_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao" 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 360, Column 188: entity was defined here
    …rce=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao"><im…
  • Warning Line 364, Column 211: reference not terminated by REFC delimiter
    …erm=2Sao&utm_content=2Sao&utm_campaign=2Sao" target="_blank" title=" Đinh Mạ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 364, Column 211: reference to external entity in attribute value
    …erm=2Sao&utm_content=2Sao&utm_campaign=2Sao" target="_blank" title=" Đinh Mạ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 364, Column 211: reference to entity "utm_campaign" for which no system identifier could be generated
    …erm=2Sao&utm_content=2Sao&utm_campaign=2Sao" target="_blank" title=" Đinh Mạ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 360, Column 205: entity was defined here
    …um=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao"><img src="/Images/bl…
  • Warning Line 364, Column 527: reference not terminated by REFC delimiter
    …uy-hon.html?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm…

    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 364, Column 527: reference to external entity in attribute value
    …uy-hon.html?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm…

    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 364, Column 527: reference to entity "utm_medium" for which no system identifier could be generated
    …uy-hon.html?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm…

    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 360, Column 158: entity was defined here
    …://tintuconline.com.vn?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_conte…
  • Warning Line 364, Column 541: reference not terminated by REFC delimiter
    …m_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao…

    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 364, Column 541: reference to external entity in attribute value
    …m_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao…

    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 364, Column 541: reference to entity "utm_term" for which no system identifier could be generated
    …m_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao…

    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 360, Column 174: entity was defined here
    …com.vn?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_camp…
  • Warning Line 364, Column 558: reference not terminated by REFC delimiter
    …_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao" 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 364, Column 558: reference to external entity in attribute value
    …_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao" 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 364, Column 558: reference to entity "utm_content" for which no system identifier could be generated
    …_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao" 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 360, Column 188: entity was defined here
    …rce=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao"><im…
  • Warning Line 364, Column 576: reference not terminated by REFC delimiter
    …erm=2Sao&utm_content=2Sao&utm_campaign=2Sao" target="_blank" title=" Tạt acid …

    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 364, Column 576: reference to external entity in attribute value
    …erm=2Sao&utm_content=2Sao&utm_campaign=2Sao" target="_blank" title=" Tạt acid …

    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 364, Column 576: reference to entity "utm_campaign" for which no system identifier could be generated
    …erm=2Sao&utm_content=2Sao&utm_campaign=2Sao" target="_blank" title=" Tạt acid …

    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 360, Column 205: entity was defined here
    …um=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao"><img src="/Images/bl…
  • Warning Line 364, Column 890: reference not terminated by REFC delimiter
    …h-tiet.html?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm…

    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 364, Column 890: reference to external entity in attribute value
    …h-tiet.html?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm…

    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 364, Column 890: reference to entity "utm_medium" for which no system identifier could be generated
    …h-tiet.html?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm…

    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 360, Column 158: entity was defined here
    …://tintuconline.com.vn?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_conte…
  • Warning Line 364, Column 904: reference not terminated by REFC delimiter
    …m_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao…

    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 364, Column 904: reference to external entity in attribute value
    …m_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao…

    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 364, Column 904: reference to entity "utm_term" for which no system identifier could be generated
    …m_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao…

    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 360, Column 174: entity was defined here
    …com.vn?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_camp…
  • Warning Line 364, Column 921: reference not terminated by REFC delimiter
    …_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao" 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 364, Column 921: reference to external entity in attribute value
    …_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao" 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 364, Column 921: reference to entity "utm_content" for which no system identifier could be generated
    …_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao" 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 360, Column 188: entity was defined here
    …rce=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao"><im…
  • Warning Line 364, Column 939: reference not terminated by REFC delimiter
    …erm=2Sao&utm_content=2Sao&utm_campaign=2Sao" target="_blank" title=" Nực cười …

    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 364, Column 939: reference to external entity in attribute value
    …erm=2Sao&utm_content=2Sao&utm_campaign=2Sao" target="_blank" title=" Nực cười …

    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 364, Column 939: reference to entity "utm_campaign" for which no system identifier could be generated
    …erm=2Sao&utm_content=2Sao&utm_campaign=2Sao" target="_blank" title=" Nực cười …

    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 360, Column 205: entity was defined here
    …um=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao"><img src="/Images/bl…
  • Warning Line 364, Column 1258: reference not terminated by REFC delimiter
    …1-tuoi.html?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm…

    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 364, Column 1258: reference to external entity in attribute value
    …1-tuoi.html?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm…

    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 364, Column 1258: reference to entity "utm_medium" for which no system identifier could be generated
    …1-tuoi.html?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm…

    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 360, Column 158: entity was defined here
    …://tintuconline.com.vn?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_conte…
  • Warning Line 364, Column 1272: reference not terminated by REFC delimiter
    …m_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao…

    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 364, Column 1272: reference to external entity in attribute value
    …m_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao…

    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 364, Column 1272: reference to entity "utm_term" for which no system identifier could be generated
    …m_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao…

    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 360, Column 174: entity was defined here
    …com.vn?utm_source=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_camp…
  • Warning Line 364, Column 1289: reference not terminated by REFC delimiter
    …_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao" 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 364, Column 1289: reference to external entity in attribute value
    …_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao" 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 364, Column 1289: reference to entity "utm_content" for which no system identifier could be generated
    …_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao" 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 360, Column 188: entity was defined here
    …rce=2Sao&utm_medium=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao"><im…
  • Warning Line 364, Column 1307: reference not terminated by REFC delimiter
    …erm=2Sao&utm_content=2Sao&utm_campaign=2Sao" target="_blank" title=" Lời chứng…

    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 364, Column 1307: reference to external entity in attribute value
    …erm=2Sao&utm_content=2Sao&utm_campaign=2Sao" target="_blank" title=" Lời chứng…

    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 364, Column 1307: reference to entity "utm_campaign" for which no system identifier could be generated
    …erm=2Sao&utm_content=2Sao&utm_campaign=2Sao" target="_blank" title=" Lời chứng…

    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 360, Column 205: entity was defined here
    …um=2Sao&utm_term=2Sao&utm_content=2Sao&utm_campaign=2Sao"><img src="/Images/bl…
  • Error Line 380, Column 62: required attribute "alt" not specified
        <img src="/Images/blank.gif" width="10px" height="10px" />

    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 392, Column 62: required attribute "alt" not specified
        <img src="/Images/blank.gif" width="10px" height="10px" />

    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 400, Column 160: reference not terminated by REFC delimiter
    …9043c1-4f14-4cc5-ac07-b832adf03391&ext=8e269091-a362-4b97-a59d-9c122d4dc25a&do…

    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 400, Column 160: reference to external entity in attribute value
    …9043c1-4f14-4cc5-ac07-b832adf03391&ext=8e269091-a362-4b97-a59d-9c122d4dc25a&do…

    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 400, Column 160: reference to entity "ext" for which no system identifier could be generated
    …9043c1-4f14-4cc5-ac07-b832adf03391&ext=8e269091-a362-4b97-a59d-9c122d4dc25a&do…

    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 108, Column 154: entity was defined here
    …n=0e9043c1-4f14-4cc5-ac07-b832adf03391&ext=5580991b-9fb4-473a-9e0e-c49cd1cf747…
  • Warning Line 400, Column 204: reference not terminated by REFC delimiter
    …&ext=8e269091-a362-4b97-a59d-9c122d4dc25a&domain=http://2sao.vn/cat0"></script>

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

  • Warning Line 400, Column 204: reference to external entity in attribute value
    …&ext=8e269091-a362-4b97-a59d-9c122d4dc25a&domain=http://2sao.vn/cat0"></script>

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

  • Error Line 400, Column 204: reference to entity "domain" for which no system identifier could be generated
    …&ext=8e269091-a362-4b97-a59d-9c122d4dc25a&domain=http://2sao.vn/cat0"></script>

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

  • Info Line 108, Column 195: entity was defined here
    …&ext=5580991b-9fb4-473a-9e0e-c49cd1cf7473&domain=http://2sao.vn/cat0"></script>
  • Warning Line 418, Column 160: reference not terminated by REFC delimiter
    …9043c1-4f14-4cc5-ac07-b832adf03391&ext=be7599e2-9b43-4d4a-ad1e-5c5d4e8de87e&do…

    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 418, Column 160: reference to external entity in attribute value
    …9043c1-4f14-4cc5-ac07-b832adf03391&ext=be7599e2-9b43-4d4a-ad1e-5c5d4e8de87e&do…

    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 418, Column 160: reference to entity "ext" for which no system identifier could be generated
    …9043c1-4f14-4cc5-ac07-b832adf03391&ext=be7599e2-9b43-4d4a-ad1e-5c5d4e8de87e&do…

    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 108, Column 154: entity was defined here
    …n=0e9043c1-4f14-4cc5-ac07-b832adf03391&ext=5580991b-9fb4-473a-9e0e-c49cd1cf747…
  • Warning Line 418, Column 204: reference not terminated by REFC delimiter
    …&ext=be7599e2-9b43-4d4a-ad1e-5c5d4e8de87e&domain=http://2sao.vn/cat0"></script>

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

  • Warning Line 418, Column 204: reference to external entity in attribute value
    …&ext=be7599e2-9b43-4d4a-ad1e-5c5d4e8de87e&domain=http://2sao.vn/cat0"></script>

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

  • Error Line 418, Column 204: reference to entity "domain" for which no system identifier could be generated
    …&ext=be7599e2-9b43-4d4a-ad1e-5c5d4e8de87e&domain=http://2sao.vn/cat0"></script>

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

  • Info Line 108, Column 195: entity was defined here
    …&ext=5580991b-9fb4-473a-9e0e-c49cd1cf7473&domain=http://2sao.vn/cat0"></script>
  • Error Line 434, Column 31: ID "id0" already defined
      <li><a href="/home.vnn" id="id0">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 52, Column 31: ID "id0" first defined here
      <li><a href="/home.vnn" id="id0"><span>Trang chủ</span></a></li>
  • Error Line 438, Column 50: ID "id1000" already defined
    …li><a href="/p0c1000/sao.vnn" title="Sao" id="id1000"><span>Sao</span></a></li>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 55, Column 50: ID "id1000" first defined here
    …li><a href="/p0c1000/sao.vnn" title="Sao" id="id1000"><span>Sao</span></a></li>
  • Error Line 442, Column 58: ID "id1001" already defined
    …/p0c1001/am-nhac.vnn" title="Âm Nhạc" id="id1001"><span>Âm Nhạc</span></a></li>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 59, Column 58: ID "id1001" first defined here
    …/p0c1001/am-nhac.vnn" title="Âm Nhạc" id="id1001"><span>Âm Nhạc</span></a></li>
  • Error Line 446, Column 64: ID "id1004" already defined
    …thoi-trang.vnn" title="Thời Trang" id="id1004"><span>Thời Trang</span></a></li>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 63, Column 64: ID "id1004" first defined here
    …thoi-trang.vnn" title="Thời Trang" id="id1004"><span>Thời Trang</span></a></li>
  • Error Line 449, Column 52: ID "id1002" already defined
    …ref="/p0c1002/phim.vnn" title="Phim" id="id1002"><span>Điện Ảnh</span></a></li>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 66, Column 52: ID "id1002" first defined here
    …ref="/p0c1002/phim.vnn" title="Phim" id="id1002"><span>Điện Ảnh</span></a></li>
  • Error Line 453, Column 72: ID "id1048" already defined
    …a-hoi.vnn" title="Sự kiện xã hội" id="id1048"><span>Sự kiện xã hội</span></a><…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 70, Column 72: ID "id1048" first defined here
    … href="/p0c1048/su-kien-xa-hoi.vnn" title="Sự kiện xã hội" id="id1048"><span>Sự
  • Error Line 457, Column 78: ID "id1049" already defined
    …re.vnn" title="Đời sống giới trẻ" id="id1049"><span>Đời sống giới trẻ</span></…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 75, Column 78: ID "id1049" first defined here
    …f="/p0c1049/doi-song-gioi-tre.vnn" title="Đời sống giới trẻ" id="id1049"><span>
  • Error Line 461, Column 58: ID "id1005" already defined
    …/p0c1005/hoi-dap.vnn" title="Alo2Sao" id="id1005"><span>Alo2Sao</span></a></li>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 80, Column 58: ID "id1005" first defined here
    …/p0c1005/hoi-dap.vnn" title="Alo2Sao" id="id1005"><span>Alo2Sao</span></a></li>
  • Error Line 465, Column 60: ID "id1051" already defined
    …c1051/the-thao.vnn" title="Thể Thao" id="id1051"><span>Thể thao</span></a></li>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 84, Column 60: ID "id1051" first defined here
    …c1051/the-thao.vnn" title="Thể Thao" id="id1051"><span>Thể thao</span></a></li>
  • Error Line 470, Column 63: ID "id1052" already defined
    …52/chuyen-la.vnn" title="Chuyện lạ" id="id1052"><span>Chuyện lạ</span></a></li>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 88, Column 62: ID "id1052" first defined here
    …52/chuyen-la.vnn" title="Chuyện lạ" id="id1052"><span>Chuyện lạ</span></a></li>
  • Error Line 482, Column 30: required attribute "type" not specified
    <script language='javascript'>SetFocusMenu('id0','active','child0')</script><br…

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

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

  • Error Line 484, Column 92: required attribute "alt" not specified
    …none" src="http://thongke.2sao.vietnamnet.vn/Handler.ashx?articleId=0"></img>  

    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 487, Column 59: required attribute "type" not specified
    <script src="http://www.vietad.vn/keyword.aspx?pubid=5371"></script>

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

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

  • Error Line 488, Column 51: required attribute "type" not specified
    <script src="http://embed.vietad.vn/MagicWords.js"></script>

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

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

  • Warning Line 507, Column 158: reference not terminated by REFC delimiter
    …9043c1-4f14-4cc5-ac07-b832adf03391&ext=2a22f3a8-1c39-4959-9c9e-0c046d86be94&do…

    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 507, Column 158: reference to external entity in attribute value
    …9043c1-4f14-4cc5-ac07-b832adf03391&ext=2a22f3a8-1c39-4959-9c9e-0c046d86be94&do…

    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 507, Column 158: reference to entity "ext" for which no system identifier could be generated
    …9043c1-4f14-4cc5-ac07-b832adf03391&ext=2a22f3a8-1c39-4959-9c9e-0c046d86be94&do…

    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 108, Column 154: entity was defined here
    …n=0e9043c1-4f14-4cc5-ac07-b832adf03391&ext=5580991b-9fb4-473a-9e0e-c49cd1cf747…
  • Warning Line 507, Column 202: reference not terminated by REFC delimiter
    …&ext=2a22f3a8-1c39-4959-9c9e-0c046d86be94&domain=http://2sao.vn/cat0"></script>

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

  • Warning Line 507, Column 202: reference to external entity in attribute value
    …&ext=2a22f3a8-1c39-4959-9c9e-0c046d86be94&domain=http://2sao.vn/cat0"></script>

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

  • Error Line 507, Column 202: reference to entity "domain" for which no system identifier could be generated
    …&ext=2a22f3a8-1c39-4959-9c9e-0c046d86be94&domain=http://2sao.vn/cat0"></script>

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

  • Info Line 108, Column 195: entity was defined here
    …&ext=5580991b-9fb4-473a-9e0e-c49cd1cf7473&domain=http://2sao.vn/cat0"></script>
  • Warning Line 510, Column 158: reference not terminated by REFC delimiter
    …9043c1-4f14-4cc5-ac07-b832adf03391&ext=90300619-242e-4ed8-9574-f285a4933761&do…

    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 510, Column 158: reference to external entity in attribute value
    …9043c1-4f14-4cc5-ac07-b832adf03391&ext=90300619-242e-4ed8-9574-f285a4933761&do…

    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 510, Column 158: reference to entity "ext" for which no system identifier could be generated
    …9043c1-4f14-4cc5-ac07-b832adf03391&ext=90300619-242e-4ed8-9574-f285a4933761&do…

    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 108, Column 154: entity was defined here
    …n=0e9043c1-4f14-4cc5-ac07-b832adf03391&ext=5580991b-9fb4-473a-9e0e-c49cd1cf747…
  • Warning Line 510, Column 202: reference not terminated by REFC delimiter
    …&ext=90300619-242e-4ed8-9574-f285a4933761&domain=http://2sao.vn/cat0"></script>

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

  • Warning Line 510, Column 202: reference to external entity in attribute value
    …&ext=90300619-242e-4ed8-9574-f285a4933761&domain=http://2sao.vn/cat0"></script>

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

  • Error Line 510, Column 202: reference to entity "domain" for which no system identifier could be generated
    …&ext=90300619-242e-4ed8-9574-f285a4933761&domain=http://2sao.vn/cat0"></script>

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

  • Info Line 108, Column 195: entity was defined here
    …&ext=5580991b-9fb4-473a-9e0e-c49cd1cf7473&domain=http://2sao.vn/cat0"></script>

Visitor Analysis

Daily Visitor
  • 13.067 visits