Công cụ giúp bạn khám phá thế giới web dễ dàng và tin cậy Tìm kiếm Facebook Gmail Youtube Zing TIN MỚI Người dân sẽ không phải xếp hàng chờ tiêm vắc xin ...

laban.vn
  • Domain Name
    laban.vn
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #50696
  • Page Size
    14 KB
  • Ip Address
    120.138.69.77
  • Heading
    H1: 2, H2: 4, H3: 4, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 6 PNG

Website Meta Analysis

  • Title
    Laban.vn
  • Meta Keyword
  • Meta Description
    Công cụ giúp bạn khám phá thế giới web dễ dàng và tin cậy Tìm kiếm Facebook Gmail Youtube Zing TIN MỚI Người dân sẽ không phải xếp hàng chờ tiêm vắc xin Nạn trộm chó lên truyền hình Channel 4 của Anh Toa thuốc là “lệnh xé xác” Loạt smartphone ...

Technical Analysis

  • Webserver
    nginx
  • Ip Address
    120.138.69.77
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx
  • date: Wed, 08 Oct 2014 01:12:14 GMT
  • content-type: text/html;charset=UTF-8
  • connection: close
  • content-encoding: gzip
  • x-geo: US
  • x-geo3: USA
  • x-ip: 107.178.200.198
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for laban.vn

DNS Analysis


DNS servers
ns2.sonthuy.com.vn [203.162.163.61]
ns1.sonthuy.com.vn [118.102.5.135]


DNS Records

Answer records
laban.vn A 120.138.69.77 3600s
laban.vn NS  ns2.vng.vn 86400s
laban.vn NS  ns3.vng.vn 86400s
laban.vn NS  ns1.vng.vn 86400s
laban.vn SOA
server: ns1.game123.com.vn
email: dns-admin@game123.com.vn
serial: 2013012900
refresh: 3600
retry: 300
expire: 604800
minimum ttl: 300
3600s

Authority records

Additional records
ns2.vng.vn A 203.162.163.61 3600s
ns1.vng.vn A 118.102.5.135 86400s
ns3.vng.vn A 103.23.156.6 86400s

IP 120.138.69.77 Analysis

  • Country Code
    VN
  • Country Code3
    VNM
  • Country Name
    Vietnam
  • City
    Thang
  • Continent Code
    AS
  • Latitude
    19.75
  • Longitude
    105.3167
  • % [whois.apnic.net node-1]
    % Whois data copyright terms http://www.apnic.net/db/dbcopyright.html

    inetnum: 120.138.69.0 - 120.138.69.255
    netname: Framework-net
    descr: Cong ty Co phan Tap doan Vi Na
    descr: Vi NA GROUP CORPORATION
    descr: 268 To Hien Thanh, Dist 10, HCMC
    country: VN
    admin-c: TT280-AP
    tech-c: ND84-AP
    status: ASSIGNED NON-PORTABLE
    remarks: send spam and abuse report to phund@vng.com.vn
    mnt-by: MAINT-VN-VNNIC
    mnt-irt: IRT-VNNIC-AP
    changed: hm-changed@apnic.net 20101201
    source: APNIC

    person: Tran Thanh Hai
    nic-hdl: TT280-AP
    e-mail: jimmy@vinagame.com.vn
    address: 383A Dien Bien Phu str, Dist 3, HCMC
    phone: +84-883-28426
    fax-no: +84-883-28425
    country: vn
    changed: hm-changed@vnnic.net.vn 20061025
    mnt-by: MAINT-VN-VNNIC
    source: APNIC

    person: Nguyen Doan Phu
    nic-hdl: ND84-AP
    e-mail: phund@vinagame.com.vn
    address: 383A Dien Bien Phu, Dist 3, HCMC
    phone: +84-918-510100
    fax-no: +84-883-28425
    country: vn
    changed: hm-changed@vnnic.net.vn 20061025
    mnt-by: MAINT-VN-VNNIC
    source: APNIC


In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 23 Errors
  • 8 Warnings
Ratio Text/Html
  • 0.48099058249040805
Message Error
  • Error Line 39, Column 66: end tag for "ul" which is not finished
                        <ul id="cityList" style="display: none;"></ul>

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

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

  • Error Line 86, Column 76: there is no attribute "autocomplete"
    …="text" class="inp_box google" autocomplete="off" value="" id="txtSearchBox" />

    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 104, Column 93: required attribute "alt" not specified
    …60052705.jpg" width="13" height="12" /> Sử dụng Laban.vn trên Mobile cực kỳ ti…

    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 120, Column 128: required attribute "alt" not specified
    …aban_browser.jpg" width="45" height="45" title="LaBàn browser" class="ads_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 120, Column 129: end tag for "img" omitted, but OMITTAG NO was specified
    …aban_browser.jpg" width="45" height="45" title="LaBàn browser" class="ads_img">

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

  • Info Line 120, Column 9: start tag was here
            <img src="http://stc.laban.vn/v2/images/laban_browser.jpg" width="45" h…
  • Error Line 128, Column 255: required attribute "alt" not specified
    …vn/v2/images/down_android.jpg" width="112" height="26" title="Tải Android"></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 128, Column 259: end tag for "img" omitted, but OMITTAG NO was specified
    …vn/v2/images/down_android.jpg" width="112" height="26" title="Tải Android"></a>

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

  • Info Line 128, Column 154: start tag was here
    …t&amp;hl=vi" target="_blank" title=""><img src="http://stc.laban.vn/v2/images/…
  • Warning Line 219, Column 117: cannot generate system identifier for general entity "utm_medium"
    …/happyme.zing.vn/me/?utm_source=laban&utm_medium=home&utm_campaign=ob" title="…

    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 219, Column 117: general entity "utm_medium" not defined and no default entity
    …/happyme.zing.vn/me/?utm_source=laban&utm_medium=home&utm_campaign=ob" title="…

    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 219, Column 127: reference not terminated by REFC delimiter
    …ing.vn/me/?utm_source=laban&utm_medium=home&utm_campaign=ob" title="HappyMe"><…

    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 219, Column 127: reference to external entity in attribute value
    …ing.vn/me/?utm_source=laban&utm_medium=home&utm_campaign=ob" title="HappyMe"><…

    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 219, Column 127: reference to entity "utm_medium" for which no system identifier could be generated
    …ing.vn/me/?utm_source=laban&utm_medium=home&utm_campaign=ob" title="HappyMe"><…

    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 219, Column 116: entity was defined here
    …//happyme.zing.vn/me/?utm_source=laban&utm_medium=home&utm_campaign=ob" title=…
  • Warning Line 219, Column 133: cannot generate system identifier for general entity "utm_campaign"
    …/me/?utm_source=laban&utm_medium=home&utm_campaign=ob" title="HappyMe"><img wi…

    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 219, Column 133: general entity "utm_campaign" not defined and no default entity
    …/me/?utm_source=laban&utm_medium=home&utm_campaign=ob" title="HappyMe"><img wi…

    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 219, Column 145: reference not terminated by REFC delimiter
    …rce=laban&utm_medium=home&utm_campaign=ob" title="HappyMe"><img width="96" hei…

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

  • Warning Line 219, Column 145: reference to external entity in attribute value
    …rce=laban&utm_medium=home&utm_campaign=ob" title="HappyMe"><img width="96" hei…

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

  • Error Line 219, Column 145: reference to entity "utm_campaign" for which no system identifier could be generated
    …rce=laban&utm_medium=home&utm_campaign=ob" title="HappyMe"><img width="96" hei…

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

  • Info Line 219, Column 132: entity was defined here
    …n/me/?utm_source=laban&utm_medium=home&utm_campaign=ob" title="HappyMe"><img w…
  • Warning Line 220, Column 154: reference not terminated by REFC delimiter
    …ing.vn/me/?utm_source=laban&utm_medium=home&utm_campaign=ob" title="">HappyMe<…

    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 220, Column 154: reference to external entity in attribute value
    …ing.vn/me/?utm_source=laban&utm_medium=home&utm_campaign=ob" title="">HappyMe<…

    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 220, Column 154: reference to entity "utm_medium" for which no system identifier could be generated
    …ing.vn/me/?utm_source=laban&utm_medium=home&utm_campaign=ob" title="">HappyMe<…

    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 219, Column 116: entity was defined here
    …//happyme.zing.vn/me/?utm_source=laban&utm_medium=home&utm_campaign=ob" title=…
  • Warning Line 220, Column 172: reference not terminated by REFC delimiter
    …m_source=laban&utm_medium=home&utm_campaign=ob" title="">HappyMe</a></h3></div>

    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 220, Column 172: reference to external entity in attribute value
    …m_source=laban&utm_medium=home&utm_campaign=ob" title="">HappyMe</a></h3></div>

    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 220, Column 172: reference to entity "utm_campaign" for which no system identifier could be generated
    …m_source=laban&utm_medium=home&utm_campaign=ob" title="">HappyMe</a></h3></div>

    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 219, Column 132: entity was defined here
    …n/me/?utm_source=laban&utm_medium=home&utm_campaign=ob" title="HappyMe"><img w…
  • Error Line 254, Column 255: end tag for "img" omitted, but OMITTAG NO was specified
    …vi2013.net-1356931733.png" alt="" title="Tuvi2013.net" class="img_hotnews"></a>

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

  • Info Line 254, Column 112: start tag was here
    …//tuvi2013.net/" title="Tuvi2013.net"><img width="80" height="59"  src="http:/…
  • Error Line 264, Column 273: end tag for "img" omitted, but OMITTAG NO was specified
    …anh.vn-1361259444.png" alt="" title="Vui Truyện Tranh" class="img_hotnews"></a>

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

  • Info Line 264, Column 121: start tag was here
    …entranh.vn/" title="Vui Truyện Tranh"><img width="80" height="59"  src="http:/…
  • Error Line 274, Column 241: end tag for "img" omitted, but OMITTAG NO was specified
    …umbs/tamhoc.com-1361261781.png" alt="" title="Tâm học" class="img_hotnews"></a>

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

  • Info Line 274, Column 105: start tag was here
    …="http://tamhoc.com/" title="Tâm học"><img width="80" height="59"  src="http:/…
  • Error Line 284, Column 275: end tag for "img" omitted, but OMITTAG NO was specified
    …bs/www.123mua.vn-1361259349.png" alt="" title="123Mua" class="img_hotnews"></a>

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

  • Info Line 284, Column 137: start tag was here
    …m-hot-trong-tuan.html" title="123Mua"><img width="80" height="59"  src="http:/…
  • Error Line 293, Column 25: document type does not allow element "div" here; assuming missing "li" start-tag
            <div class="clr"></div>
  • Error Line 294, Column 6: end tag for "li" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 293, Column 9: start tag was here
            <div class="clr"></div>
  • Error Line 294, Column 6: end tag for "ul" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 251, Column 5: start tag was here
        <ul class="list_hot">
  • Error Line 308, Column 114: end tag for "img" omitted, but OMITTAG NO was specified
    …ight="16" src="http://stc.laban.vn/v2/images/icon_facebook.png" alt="Facebook">

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

  • Info Line 308, Column 17: start tag was here
                    <img width="16" height="16" src="http://stc.laban.vn/v2/images/…
  • Error Line 311, Column 119: end tag for "img" omitted, but OMITTAG NO was specified
    …"15" src="http://stc.laban.vn/v2/images/icon_googleplus.jpg" alt="Google Plus">

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

  • Info Line 311, Column 17: start tag was here
                    <img width="24" height="15" src="http://stc.laban.vn/v2/images/…
  • Error Line 314, Column 115: end tag for "img" omitted, but OMITTAG NO was specified
    …ght="16" src="http://stc.laban.vn/v2/images/small_zing_icon.png" alt="Zing Me">

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

  • Info Line 314, Column 17: start tag was here
                    <img width="16" height="16" src="http://stc.laban.vn/v2/images/…
  • Warning Line 377, Column 105: cannot generate system identifier for general entity "bannerid"
    …ttp://idtienhiep2.com.vn/?m=quickplay&bannerid=88" title="Webgame Tiên Hiệp Tr…

    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 377, Column 105: general entity "bannerid" not defined and no default entity
    …ttp://idtienhiep2.com.vn/?m=quickplay&bannerid=88" title="Webgame Tiên Hiệp Tr…

    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 377, Column 113: reference not terminated by REFC delimiter
    …tienhiep2.com.vn/?m=quickplay&bannerid=88" title="Webgame Tiên Hiệp Truyền Kỳ …

    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 377, Column 113: reference to external entity in attribute value
    …tienhiep2.com.vn/?m=quickplay&bannerid=88" title="Webgame Tiên Hiệp Truyền Kỳ …

    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 377, Column 113: reference to entity "bannerid" for which no system identifier could be generated
    …tienhiep2.com.vn/?m=quickplay&bannerid=88" title="Webgame Tiên Hiệp Truyền Kỳ …

    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 377, Column 104: entity was defined here
    …http://idtienhiep2.com.vn/?m=quickplay&bannerid=88" title="Webgame Tiên Hiệp T…
  • Warning Line 433, Column 114: cannot generate system identifier for general entity "jurl"
    ….thankhuc.com.vn/m.php?m=189.367.1513&jurl=http://imgs.thankhuc.com.vn/than-kh…

    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 433, Column 114: general entity "jurl" not defined and no default entity
    ….thankhuc.com.vn/m.php?m=189.367.1513&jurl=http://imgs.thankhuc.com.vn/than-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.

  • Warning Line 433, Column 118: reference not terminated by REFC delimiter
    …nkhuc.com.vn/m.php?m=189.367.1513&jurl=http://imgs.thankhuc.com.vn/than-khuc/h…

    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 433, Column 118: reference to external entity in attribute value
    …nkhuc.com.vn/m.php?m=189.367.1513&jurl=http://imgs.thankhuc.com.vn/than-khuc/h…

    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 433, Column 118: reference to entity "jurl" for which no system identifier could be generated
    …nkhuc.com.vn/m.php?m=189.367.1513&jurl=http://imgs.thankhuc.com.vn/than-khuc/h…

    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 433, Column 113: entity was defined here
    …s.thankhuc.com.vn/m.php?m=189.367.1513&jurl=http://imgs.thankhuc.com.vn/than-k…
  • Warning Line 447, Column 136: character "&" is the first character of a delimiter but occurred as data
    …p://movies.hdviet.com/?utm_source=laban" title="Xem phim HD Online & miễn phí">

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 489, Column 149: reference not terminated by REFC delimiter
    …/index.htm?utm_source=laban&utm_medium=banner&utm_campaign=laban" title="Tổ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 489, Column 149: reference to external entity in attribute value
    …/index.htm?utm_source=laban&utm_medium=banner&utm_campaign=laban" title="Tổ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 489, Column 149: reference to entity "utm_medium" for which no system identifier could be generated
    …/index.htm?utm_source=laban&utm_medium=banner&utm_campaign=laban" title="Tổ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 219, Column 116: entity was defined here
    …//happyme.zing.vn/me/?utm_source=laban&utm_medium=home&utm_campaign=ob" title=…
  • Warning Line 489, Column 169: reference not terminated by REFC delimiter
    …source=laban&utm_medium=banner&utm_campaign=laban" title="Tổng hợp game mini.">

    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 489, Column 169: reference to external entity in attribute value
    …source=laban&utm_medium=banner&utm_campaign=laban" title="Tổng hợp game mini.">

    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 489, Column 169: reference to entity "utm_campaign" for which no system identifier could be generated
    …source=laban&utm_medium=banner&utm_campaign=laban" title="Tổng hợp game mini.">

    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 219, Column 132: entity was defined here
    …n/me/?utm_source=laban&utm_medium=home&utm_campaign=ob" title="HappyMe"><img w…
  • Warning Line 620, Column 167: reference not terminated by REFC delimiter
    …/index.htm?utm_source=laban&utm_medium=banner&utm_campaign=laban"> Zing Play</…

    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 620, Column 167: reference to external entity in attribute value
    …/index.htm?utm_source=laban&utm_medium=banner&utm_campaign=laban"> Zing Play</…

    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 620, Column 167: reference to entity "utm_medium" for which no system identifier could be generated
    …/index.htm?utm_source=laban&utm_medium=banner&utm_campaign=laban"> Zing Play</…

    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 219, Column 116: entity was defined here
    …//happyme.zing.vn/me/?utm_source=laban&utm_medium=home&utm_campaign=ob" title=…
  • Warning Line 620, Column 187: reference not terminated by REFC delimiter
    ….htm?utm_source=laban&utm_medium=banner&utm_campaign=laban"> Zing Play</a></li>

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

  • Warning Line 620, Column 187: reference to external entity in attribute value
    ….htm?utm_source=laban&utm_medium=banner&utm_campaign=laban"> Zing Play</a></li>

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

  • Error Line 620, Column 187: reference to entity "utm_campaign" for which no system identifier could be generated
    ….htm?utm_source=laban&utm_medium=banner&utm_campaign=laban"> Zing Play</a></li>

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

  • Info Line 219, Column 132: entity was defined here
    …n/me/?utm_source=laban&utm_medium=home&utm_campaign=ob" title="HappyMe"><img w…
  • Warning Line 675, Column 75: cannot generate system identifier for general entity "Văn"
    …,67)" target="_blank" title="Thể thao&Văn hóa" href="http://thethaovanhoa.vn">…

    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 675, Column 75: general entity "Văn" not defined and no default entity
    …,67)" target="_blank" title="Thể thao&Văn hóa" href="http://thethaovanhoa.vn">…

    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 675, Column 78: reference not terminated by REFC delimiter
    …)" target="_blank" title="Thể thao&Văn hóa" href="http://thethaovanhoa.vn"> Th…

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

  • Warning Line 675, Column 78: reference to external entity in attribute value
    …)" target="_blank" title="Thể thao&Văn hóa" href="http://thethaovanhoa.vn"> Th…

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

  • Error Line 675, Column 78: reference to entity "Văn" for which no system identifier could be generated
    …)" target="_blank" title="Thể thao&Văn hóa" href="http://thethaovanhoa.vn"> Th…

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

  • Info Line 675, Column 74: entity was defined here
    …2,67)" target="_blank" title="Thể thao&Văn hóa" href="http://thethaovanhoa.vn"…
  • Warning Line 675, Column 128: reference not terminated by REFC delimiter
    …le="Thể thao&Văn hóa" href="http://thethaovanhoa.vn"> Thể thao&Văn hóa</a></li>

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

  • Error Line 675, Column 128: reference to entity "Văn" for which no system identifier could be generated
    …le="Thể thao&Văn hóa" href="http://thethaovanhoa.vn"> Thể thao&Văn hóa</a></li>

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

  • Info Line 675, Column 74: entity was defined here
    …2,67)" target="_blank" title="Thể thao&Văn hóa" href="http://thethaovanhoa.vn"…

Visitor Analysis

Daily Visitor
  • 21.117 visits