Kết quả xổ số. Tường thuật trực tiếp kết quả xổ số miền bắc, xổ số miền nam, xổ số miền trung nhanh nhất Việt Nam. Thống kê, dự đoán kết quả chính ...

ketquaveso.com
  • Domain Name
    ketquaveso.com
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #251235
  • Page Size
    123.4 KB
  • Ip Address
    210.211.101.198
  • Heading
    H1: 1, H2: 8, H3: 4, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 24 PNG

Website Meta Analysis

  • Title
    Ket qua xo so | ket qua xo so truc tiep | ket qua xo so hom nay
  • Meta Keyword
    ket qua ve so, ket qua xo so, xo so mien bac, xo so mien nam, xo so mien trung
  • Meta Description
    Kết quả xổ số. Tường thuật trực tiếp kết quả xổ số miền bắc, xổ số miền nam, xổ số miền trung nhanh nhất Việt Nam. Thống kê, dự đoán kết quả chính xác nhất.

Technical Analysis

  • Webserver
    nginx
  • Ip Address
    210.211.101.198
  • Domain Age
    2 Years, 5 Months, 11 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx
  • date: Sun, 18 Aug 2013 19:40:13 GMT
  • content-type: text/html; charset=UTF-8
  • content-length: 16245
  • connection: keep-alive
  • x-powered-by: PHP/5.3.3
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • vary: Accept-Encoding
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for ketquaveso.com

DNS Analysis


DNS servers
ns29.domaincontrol.com [216.69.185.15]
ns30.domaincontrol.com [208.109.255.15]

DNS Records

Answer records
ketquaveso.com A 210.211.97.13 3600s
ketquaveso.com MX
preference: 0
exchange: smtp.secureserver.net
3600s
ketquaveso.com MX
preference: 10
exchange: mailstore1.secureserver.net
3600s
ketquaveso.com NS  ns29.domaincontrol.com 3600s
ketquaveso.com NS  ns30.domaincontrol.com 3600s
ketquaveso.com SOA
server: ns29.domaincontrol.com
email: dns@jomax.net
serial: 2012111800
refresh: 28800
retry: 7200
expire: 604800
minimum ttl: 3600
3600s

Authority records

Additional records

IP 210.211.101.198 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 86 Errors
  • 11 Warnings
Ratio Text/Html
  • 0.5341024180275984
Message Error
  • Error Line 2, Column 50: there is no attribute "style"
    <html xmlns="http://www.w3.org/1999/xhtml" style="">

    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 4, Column 38: required attribute "type" not specified
            <script language="javascript">

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

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

  • Error Line 16, Column 29: there is no attribute "value"
    <meta name="verify-a" value="daebc63a43f3d0676870">

    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 16, Column 51: required attribute "content" not specified
    <meta name="verify-a" value="daebc63a43f3d0676870">

    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 16, Column 52: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="verify-a" value="daebc63a43f3d0676870">

    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 16, Column 1: start tag was here
    <meta name="verify-a" value="daebc63a43f3d0676870">
  • Warning Line 66, Column 17: character "<" is the first character of a delimiter but occurred as data
            if(time < 16){

    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 69, Column 27: character "&" is the first character of a delimiter but occurred as data
                if(time >= 18 && time < 19){

    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 69, Column 28: character "&" is the first character of a delimiter but occurred as data
                if(time >= 18 && time < 19){

    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 69, Column 35: character "<" is the first character of a delimiter but occurred as data
                if(time >= 18 && time < 19){

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 86, Column 62: required attribute "type" not specified
            <script src="http://adbroker.zing.vn/res1/crystal.js"></script>   

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

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

  • Error Line 142, Column 23: document type does not allow element "style" here
    <style type="text/css">

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

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

  • Warning Line 177, Column 79: cannot generate system identifier for general entity "callback"
    …er.zing.vn/lview?loc=_adb_22_10002534&callback=crystal2.addStaticSlot"></scrip…

    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 177, Column 79: general entity "callback" not defined and no default entity
    …er.zing.vn/lview?loc=_adb_22_10002534&callback=crystal2.addStaticSlot"></scrip…

    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 177, Column 87: reference not terminated by REFC delimiter
    …vn/lview?loc=_adb_22_10002534&callback=crystal2.addStaticSlot"></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 177, Column 87: reference to external entity in attribute value
    …vn/lview?loc=_adb_22_10002534&callback=crystal2.addStaticSlot"></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 177, Column 87: reference to entity "callback" for which no system identifier could be generated
    …vn/lview?loc=_adb_22_10002534&callback=crystal2.addStaticSlot"></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 177, Column 78: entity was defined here
    …ker.zing.vn/lview?loc=_adb_22_10002534&callback=crystal2.addStaticSlot"></scri…
  • Error Line 177, Column 111: required attribute "type" not specified
    …/lview?loc=_adb_22_10002534&callback=crystal2.addStaticSlot"></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 186, Column 59: required attribute "action" not specified
                            <form method="get" id="login_form">

    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 328, Column 30: ID "itemt_menu" already defined
                        <div id="itemt_menu" class="menu_thongke">

    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 264, Column 26: ID "itemt_menu" first defined here
                    <div id="itemt_menu">
  • Error Line 370, Column 26: ID "itemt_menu" already defined
                    <div id="itemt_menu" class="menu_lodogame">

    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 264, Column 26: ID "itemt_menu" first defined here
                    <div id="itemt_menu">
  • Error Line 417, Column 26: ID "itemt_menu" already defined
                    <div id="itemt_menu" class="menu_quayso">

    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 264, Column 26: ID "itemt_menu" first defined here
                    <div id="itemt_menu">
  • Error Line 440, Column 26: ID "itemt_menu" already defined
                    <div id="itemt_menu" class="menu_soicau">

    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 264, Column 26: ID "itemt_menu" first defined here
                    <div id="itemt_menu">
  • Error Line 469, Column 26: ID "itemt_menu" already defined
                    <div id="itemt_menu" class="menu_vip">

    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 264, Column 26: ID "itemt_menu" first defined here
                    <div id="itemt_menu">
  • Error Line 476, Column 71: duplicate specification of attribute "target"
    …        <li><a target="_blank" target="_blank" href="/tro-giup.html">Lợi ích k…

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

  • Error Line 529, Column 101: duplicate specification of attribute "class"
    …ss="" href="/mien-nam/An-Giang-p2.html" class=""><span>An Giang</span></a></li>

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

  • Error Line 530, Column 105: duplicate specification of attribute "class"
    …ss="" href="/mien-nam/Bac-Lieu-p3.html" class=""><span>Bạc Liêu</span></a></li>

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

  • Error Line 531, Column 104: duplicate specification of attribute "class"
    …lass="" href="/mien-nam/Ben-Tre-p4.html" class=""><span>Bến Tre</span></a></li>

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

  • Error Line 532, Column 107: duplicate specification of attribute "class"
    …" href="/mien-nam/Binh-Duong-p5.html" class=""><span>Bình Dương</span></a></li>

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

  • Error Line 533, Column 107: duplicate specification of attribute "class"
    …" href="/mien-nam/Binh-Phuoc-p6.html" class=""><span>Bình Phước</span></a></li>

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

  • Error Line 534, Column 107: duplicate specification of attribute "class"
    …" href="/mien-nam/Binh-Thuan-p7.html" class=""><span>Bình Thuận</span></a></li>

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

  • Error Line 535, Column 103: duplicate specification of attribute "class"
    … class="" href="/mien-nam/Ca-Mau-p8.html" class=""><span>Cà Mau</span></a></li>

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

  • Error Line 536, Column 104: duplicate specification of attribute "class"
    …lass="" href="/mien-nam/Can-Tho-p9.html" class=""><span>Cần Thơ</span></a></li>

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

  • Error Line 537, Column 104: duplicate specification of attribute "class"
    …class="" href="/mien-nam/Da-Lat-p10.html" class=""><span>Đà Lạt</span></a></li>

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

  • Error Line 538, Column 106: duplicate specification of attribute "class"
    …s="" href="/mien-nam/Dong-Nai-p11.html" class=""><span>Đồng Nai</span></a></li>

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

  • Error Line 539, Column 107: duplicate specification of attribute "class"
    …"" href="/mien-nam/Dong-Thap-p12.html" class=""><span>Đồng Tháp</span></a></li>

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

  • Error Line 540, Column 107: duplicate specification of attribute "class"
    …"" href="/mien-nam/Hau-Giang-p13.html" class=""><span>Hậu Giang</span></a></li>

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

  • Error Line 541, Column 109: duplicate specification of attribute "class"
    …ref="/mien-nam/Ho-Chi-Minh-p14.html" class=""><span>Hồ Chí Minh</span></a></li>

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

  • Error Line 542, Column 108: duplicate specification of attribute "class"
    … href="/mien-nam/Kien-Giang-p15.html" class=""><span>Kiên Giang</span></a></li>

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

  • Error Line 543, Column 105: duplicate specification of attribute "class"
    …ass="" href="/mien-nam/Long-An-p16.html" class=""><span>Long An</span></a></li>

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

  • Error Line 544, Column 107: duplicate specification of attribute "class"
    …"" href="/mien-nam/Soc-Trang-p17.html" class=""><span>Sóc Trăng</span></a></li>

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

  • Error Line 545, Column 106: duplicate specification of attribute "class"
    …s="" href="/mien-nam/Tay-Ninh-p18.html" class=""><span>Tây Ninh</span></a></li>

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

  • Error Line 546, Column 108: duplicate specification of attribute "class"
    … href="/mien-nam/Tien-Giang-p19.html" class=""><span>Tiền Giang</span></a></li>

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

  • Error Line 547, Column 106: duplicate specification of attribute "class"
    …s="" href="/mien-nam/Tra-Vinh-p20.html" class=""><span>Trà Vinh</span></a></li>

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

  • Error Line 548, Column 107: duplicate specification of attribute "class"
    …"" href="/mien-nam/Vinh-Long-p21.html" class=""><span>Vĩnh Long</span></a></li>

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

  • Error Line 549, Column 106: duplicate specification of attribute "class"
    …s="" href="/mien-nam/Vung-Tau-p22.html" class=""><span>Vũng Tàu</span></a></li>

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

  • Error Line 555, Column 105: duplicate specification of attribute "class"
    … href="/mien-trung/Binh-Dinh-p23.html" class=""><span>Bình Định</span></a></li>

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

  • Error Line 556, Column 107: duplicate specification of attribute "class"
    …s="" href="/mien-trung/Da-Nang-p24.html" class=""><span>Đà Nẵng</span></a></li>

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

  • Error Line 557, Column 107: duplicate specification of attribute "class"
    …s="" href="/mien-trung/Dac-Lac-p25.html" class=""><span>Đắc Lắc</span></a></li>

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

  • Error Line 558, Column 108: duplicate specification of attribute "class"
    …"" href="/mien-trung/Dac-Nong-p26.html" class=""><span>Đắc Nông</span></a></li>

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

  • Error Line 559, Column 107: duplicate specification of attribute "class"
    …s="" href="/mien-trung/Gia-Lai-p27.html" class=""><span>Gia Lai</span></a></li>

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

  • Error Line 560, Column 109: duplicate specification of attribute "class"
    … href="/mien-trung/Khanh-Hoa-p28.html" class=""><span>Khánh Hòa</span></a></li>

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

  • Error Line 561, Column 107: duplicate specification of attribute "class"
    …s="" href="/mien-trung/Kon-Tum-p29.html" class=""><span>Kon Tum</span></a></li>

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

  • Error Line 562, Column 110: duplicate specification of attribute "class"
    …ref="/mien-trung/Ninh-Thuan-p30.html" class=""><span>Ninh Thuận</span></a></li>

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

  • Error Line 563, Column 107: duplicate specification of attribute "class"
    …s="" href="/mien-trung/Phu-Yen-p31.html" class=""><span>Phú Yên</span></a></li>

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

  • Error Line 564, Column 110: duplicate specification of attribute "class"
    …ref="/mien-trung/Quang-Binh-p32.html" class=""><span>Quảng Bình</span></a></li>

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

  • Error Line 565, Column 110: duplicate specification of attribute "class"
    …ref="/mien-trung/Quang-Ngai-p33.html" class=""><span>Quảng Ngãi</span></a></li>

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

  • Error Line 566, Column 109: duplicate specification of attribute "class"
    … href="/mien-trung/Quang-Nam-p34.html" class=""><span>Quảng Nam</span></a></li>

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

  • Error Line 567, Column 109: duplicate specification of attribute "class"
    … href="/mien-trung/Quang-Tri-p35.html" class=""><span>Quảng Trị</span></a></li>

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

  • Error Line 568, Column 114: duplicate specification of attribute "class"
    …en-trung/Thua-Thien-Hue-p36.html" class=""><span>Thừa Thiên Huế</span></a></li>

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

  • Warning Line 685, Column 99: cannot generate system identifier for general entity "page"
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=1A"></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 685, Column 99: general entity "page" not defined and no default entity
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=1A"></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 685, Column 103: reference not terminated by REFC delimiter
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=1A"></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 685, Column 103: reference to external entity in attribute value
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=1A"></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 685, Column 103: reference to entity "page" for which no system identifier could be generated
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=1A"></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 685, Column 98: entity was defined here
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=1A"></script>
  • Warning Line 685, Column 110: cannot generate system identifier for general entity "position"
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=1A"></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 685, Column 110: general entity "position" not defined and no default entity
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=1A"></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 685, Column 118: reference not terminated by REFC delimiter
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=1A"></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 685, Column 118: reference to external entity in attribute value
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=1A"></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 685, Column 118: reference to entity "position" for which no system identifier could be generated
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=1A"></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 685, Column 109: entity was defined here
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=1A"></script>
  • Warning Line 687, Column 103: reference not terminated by REFC delimiter
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=1B"></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 687, Column 103: reference to external entity in attribute value
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=1B"></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 687, Column 103: reference to entity "page" for which no system identifier could be generated
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=1B"></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 685, Column 98: entity was defined here
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=1A"></script>
  • Warning Line 687, Column 118: reference not terminated by REFC delimiter
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=1B"></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 687, Column 118: reference to external entity in attribute value
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=1B"></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 687, Column 118: reference to entity "position" for which no system identifier could be generated
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=1B"></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 685, Column 109: entity was defined here
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=1A"></script>
  • Warning Line 689, Column 103: reference not terminated by REFC delimiter
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=1C"></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 689, Column 103: reference to external entity in attribute value
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=1C"></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 689, Column 103: reference to entity "page" for which no system identifier could be generated
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=1C"></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 685, Column 98: entity was defined here
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=1A"></script>
  • Warning Line 689, Column 118: reference not terminated by REFC delimiter
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=1C"></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 689, Column 118: reference to external entity in attribute value
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=1C"></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 689, Column 118: reference to entity "position" for which no system identifier could be generated
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=1C"></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 685, Column 109: entity was defined here
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=1A"></script>
  • Warning Line 706, Column 111: reference not terminated by REFC delimiter
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=2A"></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 706, Column 111: reference to external entity in attribute value
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=2A"></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 706, Column 111: reference to entity "page" for which no system identifier could be generated
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=2A"></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 685, Column 98: entity was defined here
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=1A"></script>
  • Warning Line 706, Column 126: reference not terminated by REFC delimiter
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=2A"></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 706, Column 126: reference to external entity in attribute value
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=2A"></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 706, Column 126: reference to entity "position" for which no system identifier could be generated
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=2A"></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 685, Column 109: entity was defined here
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=1A"></script>
  • Error Line 737, Column 40: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
                            <div class="fl">

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

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

  • Error Line 746, Column 40: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
                            <div class="fr">

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

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

  • Error Line 750, Column 22: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
        <div id="fb-root"></div>

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

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

  • Error Line 751, Column 13: required attribute "type" not specified
         <script>(function(d, s, id) {

    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 755, Column 67: cannot generate system identifier for general entity "appId"
    …  js.src = "//connect.facebook.net/vi_VN/all.js#xfbml=1&appId=333239236692655";

    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 755, Column 67: general entity "appId" not defined and no default entity
    …  js.src = "//connect.facebook.net/vi_VN/all.js#xfbml=1&appId=333239236692655";

    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 755, Column 72: reference not terminated by REFC delimiter
    …  js.src = "//connect.facebook.net/vi_VN/all.js#xfbml=1&appId=333239236692655";

    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 755, Column 72: reference to entity "appId" for which no system identifier could be generated
    …  js.src = "//connect.facebook.net/vi_VN/all.js#xfbml=1&appId=333239236692655";

    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 755, Column 66: entity was defined here
    …  js.src = "//connect.facebook.net/vi_VN/all.js#xfbml=1&appId=333239236692655";
  • Error Line 758, Column 36: there is no attribute "data-href"
        <div class="fb-like" data-href="http://www.facebook.com/ketquaveso" data-se…

    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 758, Column 83: there is no attribute "data-send"
    …ww.facebook.com/ketquaveso" data-send="false" data-layout="button_count" data-…

    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 758, Column 103: there is no attribute "data-layout"
    …uaveso" data-send="false" data-layout="button_count" data-width="50" data-show…

    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 758, Column 129: there is no attribute "data-width"
    …alse" data-layout="button_count" data-width="50" data-show-faces="false"></div>

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

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

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

  • Error Line 758, Column 150: there is no attribute "data-show-faces"
    …alse" data-layout="button_count" data-width="50" data-show-faces="false"></div>

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

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

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

  • Error Line 758, Column 157: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …alse" data-layout="button_count" data-width="50" data-show-faces="false"></div>

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

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

  • Error Line 761, Column 21: there is no attribute "size"
        <g:plusone size="medium" annotation="none" href="https://plus.google.com/10…

    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 761, Column 41: there is no attribute "annotation"
    …  <g:plusone size="medium" annotation="none" href="https://plus.google.com/109…

    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 761, Column 53: there is no attribute "href"
    … size="medium" annotation="none" href="https://plus.google.com/109214100437853…

    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 761, Column 100: element "g:plusone" undefined
    …tation="none" href="https://plus.google.com/109214100437853834973"></g:plusone>

    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 1517, Column 100: end tag for "tbody" which is not finished
    …                                                                       </tbody>

    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 1531, Column 81: end tag for element "br" which is not open
    …d width="25%"><strong class="s12">Đầu </br> (hai số cuối giải ĐB)</strong></td>

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

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

  • Error Line 1532, Column 82: end tag for element "br" which is not open
    … width="26%"><strong class="s12">Đuôi </br> (hai số cuối giải ĐB)</strong></td>

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

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

  • Error Line 1711, Column 100: end tag for "tbody" which is not finished
    …                                                                       </tbody>

    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 1805, Column 100: end tag for "tbody" which is not finished
    …                                                                       </tbody>

    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 1811, Column 100: end tag for "tbody" which is not finished
    …                                                                       </tbody>

    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 1830, Column 8: required attribute "type" not specified
    <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 1845, Column 42: cannot generate system identifier for general entity "ngay_quay"
            var url = "/in-ve-do.html?mien=1&ngay_quay=27-02-2013";

    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 1845, Column 42: general entity "ngay_quay" not defined and no default entity
            var url = "/in-ve-do.html?mien=1&ngay_quay=27-02-2013";

    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 1845, Column 51: reference not terminated by REFC delimiter
            var url = "/in-ve-do.html?mien=1&ngay_quay=27-02-2013";

    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 1845, Column 51: reference to entity "ngay_quay" for which no system identifier could be generated
            var url = "/in-ve-do.html?mien=1&ngay_quay=27-02-2013";

    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 1845, Column 41: entity was defined here
            var url = "/in-ve-do.html?mien=1&ngay_quay=27-02-2013";
  • Warning Line 1848, Column 31: cannot generate system identifier for general entity "name"
                window.open(url+"&name="+name);

    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 1848, Column 31: general entity "name" not defined and no default entity
                window.open(url+"&name="+name);

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

  • Warning Line 1848, Column 35: reference not terminated by REFC delimiter
                window.open(url+"&name="+name);

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

  • Error Line 1848, Column 35: reference to entity "name" for which no system identifier could be generated
                window.open(url+"&name="+name);

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

  • Info Line 1848, Column 30: entity was defined here
                window.open(url+"&name="+name);
  • Warning Line 1859, Column 23: character "&" is the first character of a delimiter but occurred as data
            if(time >= 18 && time <=20){

    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 1859, Column 24: character "&" is the first character of a delimiter but occurred as data
            if(time >= 18 && time <=20){

    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 1859, Column 31: character "<" is the first character of a delimiter but occurred as data
            if(time >= 18 && time <=20){

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 1988, Column 8: required attribute "type" not specified
    <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 2032, Column 95: reference not terminated by REFC delimiter
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=3A"></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 2032, Column 95: reference to external entity in attribute value
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=3A"></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 2032, Column 95: reference to entity "page" for which no system identifier could be generated
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=3A"></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 685, Column 98: entity was defined here
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=1A"></script>
  • Warning Line 2032, Column 110: reference not terminated by REFC delimiter
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=3A"></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 2032, Column 110: reference to external entity in attribute value
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=3A"></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 2032, Column 110: reference to entity "position" for which no system identifier could be generated
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=3A"></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 685, Column 109: entity was defined here
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=1A"></script>
  • Warning Line 2036, Column 95: reference not terminated by REFC delimiter
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=3B"></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 2036, Column 95: reference to external entity in attribute value
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=3B"></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 2036, Column 95: reference to entity "page" for which no system identifier could be generated
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=3B"></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 685, Column 98: entity was defined here
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=1A"></script>
  • Warning Line 2036, Column 110: reference not terminated by REFC delimiter
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=3B"></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 2036, Column 110: reference to external entity in attribute value
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=3B"></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 2036, Column 110: reference to entity "position" for which no system identifier could be generated
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=3B"></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 685, Column 109: entity was defined here
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=1A"></script>
  • Warning Line 2043, Column 111: reference not terminated by REFC delimiter
    …24.vn/banner/showBann?domain=kqvs&page=all&position=2B"></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 2043, Column 111: reference to external entity in attribute value
    …24.vn/banner/showBann?domain=kqvs&page=all&position=2B"></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 2043, Column 111: reference to entity "page" for which no system identifier could be generated
    …24.vn/banner/showBann?domain=kqvs&page=all&position=2B"></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 685, Column 98: entity was defined here
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=1A"></script>
  • Warning Line 2043, Column 124: reference not terminated by REFC delimiter
    …er/showBann?domain=kqvs&page=all&position=2B"></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 2043, Column 124: reference to external entity in attribute value
    …er/showBann?domain=kqvs&page=all&position=2B"></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 2043, Column 124: reference to entity "position" for which no system identifier could be generated
    …er/showBann?domain=kqvs&page=all&position=2B"></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 685, Column 109: entity was defined here
    …http://ad.az24.vn/banner/showBann?domain=kqvs&page=other&position=1A"></script>
  • Error Line 2043, Column 128: document type does not allow element "script" here; assuming missing "li" start-tag
    …er/showBann?domain=kqvs&page=all&position=2B"></script>                        
  • Error Line 2044, Column 25: end tag for "li" omitted, but OMITTAG NO was specified
                        </ul>

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

  • Info Line 2043, Column 25: start tag was here
                            <script type="text/javascript" src="http://ad.az24.vn/b…
  • Error Line 2078, Column 8: required attribute "type" not specified
    <script>var _wau = _wau || []; _wau.push(["tab", "6hzufl2wwxke", "pnd", "left-l…

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

Visitor Analysis

Daily Visitor
  • 292 visits