thpt-phanboichau-daklak.edu.vn

THPT-Phan Bội Châu Huyện Krông Năng - Tỉnh Đaklak ...

This data was last updated from 23-08-2014 11:38:11  (update).

Overview Info



  • Domain Name
    thpt-phanboichau-daklak.edu.vn
  • Favicon
  • Alexa Rank
    #0
  • Google Page Rank
    2
  • Ip Address
    123.30.129.254
  • Page Size
    85.4 KB
  • Images
    0 GIF, 7 JPG, 12 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    11 0 0 0 0 0

Website Meta Analysis



  • Title
    Trường THPT Phan Bội Châu - ĐakLak
  • Meta Keyword
    THPT-PhanBoiChau-Daklak, Krong Nang, Daklak, THPT, Phan Boi Chau
  • Meta Description
    THPT-Phan Bội Châu Huyện Krông Năng - Tỉnh Đaklak

Technical Analysis



  • Webserver
    Apache
  • Ip Address
    123.30.129.254
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from thpt-phanboichau-daklak.edu.vn.

HTML Analysis

  • date: Sat, 23 Aug 2014 23:38:02 GMT
  • server: Apache
  • p3p: CP="NOI ADM DEV PSAi COM NAV OUR OTRo STP IND DEM"
  • expires: Mon, 1 Jan 2001 00:00:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • last-modified: Sat, 23 Aug 2014 23:38:04 GMT
  • connection: close
  • content-type: text/html; charset=utf-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for thpt-phanboichau-daklak.edu.vn

IP 123.30.129.254 Analysis

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

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 42 Errors
  • 16 Warnings
Ratio Text/Html
  • 0.820918215698379
Message Error
  • Error Line 22, Column 4: "endif" is not a reserved name
    <![endif]-->
  • Error Line 22, Column 9: character data is not allowed here
    <![endif]-->

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 32, Column 127: required attribute "alt" not specified
    …edu.vn/images/logo/banner_logo.jpg" border="0" width="150" height="150" /> </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 34, Column 58: an attribute specification must start with a name or name token
    <div class="flash_banner" style="width:800px;float:left;"">

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

  • Error Line 47, Column 45: end tag for "param" omitted, but OMITTAG NO was specified
    				<param name="wmode" value="transparent">

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

  • Info Line 47, Column 5: start tag was here
    				<param name="wmode" value="transparent">
  • Error Line 50, Column 16: there is no attribute "src"
    				<embed src="http://thpt-phanboichau-daklak.edu.vn/templates/ja_topaz/images…

    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 50, Column 104: there is no attribute "quality"
    …du.vn/templates/ja_topaz/images/bg-header.swf" quality="high" bgcolor="#ffffff"

    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 50, Column 119: there is no attribute "bgcolor"
    …du.vn/templates/ja_topaz/images/bg-header.swf" quality="high" bgcolor="#ffffff"

    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 52, Column 12: there is no attribute "height"
    				height="150" width="800" 

    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 52, Column 24: there is no attribute "width"
    				height="150" width="800" 

    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 54, Column 10: there is no attribute "name"
    				name="mymoviename" scale="noScale" wmode="transparent" align="" type="appli…

    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 54, Column 30: there is no attribute "scale"
    				name="mymoviename" scale="noScale" wmode="transparent" align="" type="appli…

    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 54, Column 46: there is no attribute "wmode"
    …e="mymoviename" scale="noScale" wmode="transparent" align="" type="application…

    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 54, Column 66: there is no attribute "align"
    …le="noScale" wmode="transparent" align="" type="application/x-shockwave-flash" 

    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 54, Column 74: there is no attribute "type"
    …le="noScale" wmode="transparent" align="" type="application/x-shockwave-flash" 

    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 56, Column 17: there is no attribute "pluginspage"
    				pluginspage="http://www.macromedia.com/go/getflashplayer"> 

    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 56, Column 62: element "embed" undefined
    				pluginspage="http://www.macromedia.com/go/getflashplayer"> 

    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).
  • Warning Line 201, Column 98: unclosed start-tag requires SHORTTAG YES
    …t_counter" style="margin-bottom:5px;>"<div><img src="http://thpt-phanboichau-d…

    The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.

  • Error Line 226, Column 123: required attribute "alt" not specified
    …en_HCM/02-tang%20co.jpg" border="" width="155" height="100" class="decs" /></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 797, Column 320: end tag for element "p" which is not open
    …t quả tốt nghiệp THPT năm 2013 tại Đăk Lăk" width="126" height="82"  /></a></p>

    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.

  • Warning Line 804, Column 43: cannot generate system identifier for general entity "ĐT"
    …	<a title="Sáng ngày 29/3/2013, Bộ GD&ĐT cho biết  thí sinh THPT thi tốt nghiệ…

    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 804, Column 43: general entity "ĐT" not defined and no default entity
    …	<a title="Sáng ngày 29/3/2013, Bộ GD&ĐT cho biết  thí sinh THPT thi tốt nghiệ…

    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 804, Column 45: reference not terminated by REFC delimiter
    …a title="Sáng ngày 29/3/2013, Bộ GD&ĐT cho biết  thí sinh THPT thi tốt nghiệp …

    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 804, Column 45: reference to external entity in attribute value
    …a title="Sáng ngày 29/3/2013, Bộ GD&ĐT cho biết  thí sinh THPT thi tốt nghiệp …

    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 804, Column 45: reference to entity "ĐT" for which no system identifier could be generated
    …a title="Sáng ngày 29/3/2013, Bộ GD&ĐT cho biết  thí sinh THPT thi tốt nghiệp …

    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 804, Column 42: entity was defined here
    …		<a title="Sáng ngày 29/3/2013, Bộ GD&ĐT cho biết  thí sinh THPT thi tốt nghi…
  • Warning Line 804, Column 818: reference not terminated by REFC delimiter
    … 4/6 với 6 môn thi bắt buộc. Bộ  GD&ĐT khẳng định nội dung thi nằm trong chươn…

    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 804, Column 818: reference to external entity in attribute value
    … 4/6 với 6 môn thi bắt buộc. Bộ  GD&ĐT khẳng định nội dung thi nằm trong chươn…

    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 804, Column 818: reference to entity "ĐT" for which no system identifier could be generated
    … 4/6 với 6 môn thi bắt buộc. Bộ  GD&ĐT khẳng định nội dung thi nằm trong chươn…

    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 804, Column 42: entity was defined here
    …		<a title="Sáng ngày 29/3/2013, Bộ GD&ĐT cho biết  thí sinh THPT thi tốt nghi…
  • Warning Line 808, Column 30: character "&" is the first character of a delimiter but occurred as data
      			<a title="  SỞ GIÁO DỤC & ĐÀO TẠO ĐẮK LẮK             CỘNG HOÀ XÃ HỘI CHỦ …

    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 808, Column 3497: cannot generate system identifier for general entity "SKHKI"
    … thực hiện theo kế hoạch số 114/KH-KT&SKHKI, ngày 22 tháng 11 năm 2012.  Trên …

    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 808, Column 3497: general entity "SKHKI" not defined and no default entity
    … thực hiện theo kế hoạch số 114/KH-KT&SKHKI, ngày 22 tháng 11 năm 2012.  Trên …

    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 808, Column 3502: reference not terminated by REFC delimiter
    … hiện theo kế hoạch số 114/KH-KT&SKHKI, ngày 22 tháng 11 năm 2012.  Trên đây l…

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

  • Warning Line 808, Column 3502: reference to external entity in attribute value
    … hiện theo kế hoạch số 114/KH-KT&SKHKI, ngày 22 tháng 11 năm 2012.  Trên đây l…

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

  • Error Line 808, Column 3502: reference to entity "SKHKI" for which no system identifier could be generated
    … hiện theo kế hoạch số 114/KH-KT&SKHKI, ngày 22 tháng 11 năm 2012.  Trên đây l…

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

  • Info Line 808, Column 3496: entity was defined here
    …c thực hiện theo kế hoạch số 114/KH-KT&SKHKI, ngày 22 tháng 11 năm 2012.  Trên…
  • Warning Line 812, Column 1591: cannot generate system identifier for general entity "DL"
    …   6   CĐ BÁCH VIỆT       7   CĐ VHNT&DL SÀI   GÒN       8   CĐ KT-KT VINATEX …

    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 812, Column 1591: general entity "DL" not defined and no default entity
    …   6   CĐ BÁCH VIỆT       7   CĐ VHNT&DL SÀI   GÒN       8   CĐ KT-KT VINATEX …

    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 812, Column 1593: reference not terminated by REFC delimiter
    … 6   CĐ BÁCH VIỆT       7   CĐ VHNT&DL SÀI   GÒN       8   CĐ KT-KT VINATEX   …

    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 812, Column 1593: reference to external entity in attribute value
    … 6   CĐ BÁCH VIỆT       7   CĐ VHNT&DL SÀI   GÒN       8   CĐ KT-KT VINATEX   …

    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 812, Column 1593: reference to entity "DL" for which no system identifier could be generated
    … 6   CĐ BÁCH VIỆT       7   CĐ VHNT&DL SÀI   GÒN       8   CĐ KT-KT VINATEX   …

    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 812, Column 1590: entity was defined here
    …    6   CĐ BÁCH VIỆT       7   CĐ VHNT&DL SÀI   GÒN       8   CĐ KT-KT VINATEX…
  • Error Line 836, Column 327: "HỌC" is not a member of a group specified for any attribute
    …20co.jpg" alt="HỘI THI KỂ CHUYỆN "HỌC TẬP VÀ LÀM THEO TẤM GƯƠNG ĐẠO ĐỨC HỒ CHÍ…
  • Error Line 836, Column 331: "TẬP" is not a member of a group specified for any attribute
    ….jpg" alt="HỘI THI KỂ CHUYỆN "HỌC TẬP VÀ LÀM THEO TẤM GƯƠNG ĐẠO ĐỨC HỒ CHÍ MIN…
  • Error Line 836, Column 334: "VÀ" is not a member of a group specified for any attribute
    …g" alt="HỘI THI KỂ CHUYỆN "HỌC TẬP VÀ LÀM THEO TẤM GƯƠNG ĐẠO ĐỨC HỒ CHÍ MINH" …
  • Error Line 836, Column 338: "LÀM" is not a member of a group specified for any attribute
    …lt="HỘI THI KỂ CHUYỆN "HỌC TẬP VÀ LÀM THEO TẤM GƯƠNG ĐẠO ĐỨC HỒ CHÍ MINH" CỤM …
  • Error Line 836, Column 343: "THEO" is not a member of a group specified for any attribute
    …ỘI THI KỂ CHUYỆN "HỌC TẬP VÀ LÀM THEO TẤM GƯƠNG ĐẠO ĐỨC HỒ CHÍ MINH" CỤM II" w…
  • Error Line 836, Column 347: "TẤM" is not a member of a group specified for any attribute
    …HI KỂ CHUYỆN "HỌC TẬP VÀ LÀM THEO TẤM GƯƠNG ĐẠO ĐỨC HỒ CHÍ MINH" CỤM II" width…
  • Error Line 836, Column 353: "GƯƠNG" is not a member of a group specified for any attribute
    …CHUYỆN "HỌC TẬP VÀ LÀM THEO TẤM GƯƠNG ĐẠO ĐỨC HỒ CHÍ MINH" CỤM II" width="126"…
  • Error Line 836, Column 357: "ĐẠO" is not a member of a group specified for any attribute
    …ỆN "HỌC TẬP VÀ LÀM THEO TẤM GƯƠNG ĐẠO ĐỨC HỒ CHÍ MINH" CỤM II" width="126" hei…
  • Error Line 836, Column 361: "ĐỨC" is not a member of a group specified for any attribute
    …HỌC TẬP VÀ LÀM THEO TẤM GƯƠNG ĐẠO ĐỨC HỒ CHÍ MINH" CỤM II" width="126" height=…
  • Error Line 836, Column 364: "HỒ" is not a member of a group specified for any attribute
    … TẬP VÀ LÀM THEO TẤM GƯƠNG ĐẠO ĐỨC HỒ CHÍ MINH" CỤM II" width="126" height="82…
  • Error Line 836, Column 368: "CHÍ" is not a member of a group specified for any attribute
    … VÀ LÀM THEO TẤM GƯƠNG ĐẠO ĐỨC HỒ CHÍ MINH" CỤM II" width="126" height="82"  /…
  • Error Line 836, Column 372: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …LÀM THEO TẤM GƯƠNG ĐẠO ĐỨC HỒ CHÍ MINH" CỤM II" width="126" height="82"  /></a…

    Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".

  • Error Line 836, Column 373: end tag for "img" omitted, but OMITTAG NO was specified
    …ÀM THEO TẤM GƯƠNG ĐẠO ĐỨC HỒ CHÍ MINH" CỤM II" width="126" height="82"  /></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 836, Column 243: start tag was here
    …7-hoi-thi-ke-chuyen-ho-chi-minh.html"><img src="/images/Hoithi_kechuyen_HCM/02…
  • Error Line 836, Column 416: end tag for element "p" which is not open
    …THEO TẤM GƯƠNG ĐẠO ĐỨC HỒ CHÍ MINH" CỤM II" width="126" height="82"  /></a></p>

    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.

  • Warning Line 843, Column 2528: character "&" is the first character of a delimiter but occurred as data
    …uyền Ảnh: Thi đấu môn bóng chuyền Bài & ảnh: Công Thành  &nbsp;" href="/tin-tu…

    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 851, Column 2865: character "&" is the first character of a delimiter but occurred as data
    …2013 - 2017 ra mắt, nhận nhiệm vụ.Bài & ảnh: Công Thành. &nbsp;" href="/tin-tu…

    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 877, Column 298: end tag for element "p" which is not open
    …tato.jpg" alt="Cây lai cà chua - khoai tây" width="126" height="82"  /></a></p>

    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 916, Column 414: end tag for element "p" which is not open
    …HỮNG ĐIỂM MỚI VỀ TUYỂN SINH ĐH-CĐ NĂM 2013" width="126" height="82"  /></a></p>

    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.

  • Warning Line 935, Column 5816: character "&" is the first character of a delimiter but occurred as data
    …chiếc cell phone để trong túi reo lên & phát hỏa khiến đùi và bụng dưới của an…

    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.

Visitor Analysis

Daily Visitor
  • 21 visits

In Page Analysis