phim3x.tv

Tin tức, sự kiện Việt Nam và quốc tế nhanh, chính xác và cập nhật mới online 24h /7: Xã hội, Pháp luật, Kinh doanh, Giải trí, Thể thao, Đời sống, Sức khỏe, ...

This data was last updated from 12-12-2014 07:49:41  (update).

Overview Info



  • Domain Name
    phim3x.tv
  • Favicon
  • Alexa Rank
    #0
  • Google Page Rank
    1
  • Ip Address
    104.28.6.25
  • Page Size
    111.8 KB
  • Images
    0 GIF, 30 JPG, 24 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 3 26 0 0 0

Website Meta Analysis



  • Title
    Báo Dân trí | Tin tức Việt Nam và quốc tế nóng, nhanh, cập nhật 24h
  • Meta Keyword
    Dân trí, dantri, Việt Nam, Vietnam, net, báo, điện tử, vn, express, news, online, báo mạng, trực tuyến, tin tức, sự kiện, mới, nóng, nhanh, hot, video, clip, thời sự, xã hội, đời sống, quốc tế, thế giới, blog, pháp luật, vụ án, lao động, việc làm, kinh tế, kinh doanh, thể thao, bóng đá, tennis, văn hóa, giải trí, showbiz, sao Việt, tình yêu, giới tính, gia đình, chuyện lạ, xe, teen, tư vấn, giao lưu, công nghệ, di động, du học, tuyển sinh, du lịch, nhân ái, từ thiện, iphone, youtube, Trung Quốc, Mỹ, biển Đông
  • Meta Description
    Tin tức, sự kiện Việt Nam và quốc tế nhanh, chính xác và cập nhật mới online 24h /7: Xã hội, Pháp luật, Kinh doanh, Giải trí, Thể thao, Đời sống, Sức khỏe, Giáo dục, Công nghệ, Văn hóa, Ôtô, Xe máy, Tình yêu, Giới tính, Nhịp sống trẻ, Chuyện lạ, Blog, Nhân ái, Bạn đọc, Việc làm…

Technical Analysis



  • Webserver
    dantri-rl-86
  • Ip Address
    104.28.6.25
  • Domain Age
    4 Months, 17 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from phim3x.tv.

HTML Analysis

  • date: Fri, 12 Dec 2014 19:49:35 GMT
  • content-type: text/html; charset=UTF-8
  • content-length: 32889
  • connection: close
  • cache-control: private
  • server: dantri-rl-86
  • content-encoding: gzip
  • filterid: ft
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for phim3x.tv

IP 104.28.6.25 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 117 Errors
  • 15 Warnings
Ratio Text/Html
  • 0.6529908410676399
Message Error
  • Error Line 5, Column 51: there is no attribute "prefix"
    <html xmlns="http://www.w3.org/1999/xhtml" prefix="og: http://ogp.me/ns#">

    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 8, Column 593: there is no attribute "property"
    …me="vs_targetSchema" /><meta property="og:type" content="article" /><meta id="…

    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 8, Column 667: required attribute "content" not specified
    …id="ctl00_idOgUrl" property="og:url" /><meta property="og:site_name" content="…

    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 8, Column 765: required attribute "content" not specified
    …ctl00_idOgIitle" property="og:title" /><meta id="ctl00_idOgImg" property="og:i…

    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 8, Column 812: required attribute "content" not specified
    …="ctl00_idOgImg" property="og:image" /><meta id="ctl00_idOgDes" property="og:d…

    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 8, Column 1009: required attribute "content" not specified
    …e" property="article:published_time" /><meta id="ctl00_idmodified_time" proper…

    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 8, Column 1077: required attribute "content" not specified
    …me" property="article:modified_time" /><meta id="ctl00_idexpiration_time" prop…

    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 8, Column 1149: required attribute "content" not specified
    …" property="article:expiration_time" /><meta property="article:author" content…

    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 30, Column 12: required attribute "type" not specified
        <script>var _comscore = _comscore || []; _comscore.push({ c1: "2", c2: "177…

    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 31, Column 14: document type does not allow element "noscript" here; assuming missing "object" start-tag
        <noscript>
  • Warning Line 32, Column 57: cannot generate system identifier for general entity "c2"
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=17793284&cv=2.0&cj=1" />

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

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

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

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

  • Error Line 32, Column 57: general entity "c2" not defined and no default entity
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=17793284&cv=2.0&cj=1" />

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

  • Warning Line 32, Column 59: reference not terminated by REFC delimiter
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=17793284&cv=2.0&cj=1" />

    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 32, Column 59: reference to external entity in attribute value
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=17793284&cv=2.0&cj=1" />

    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 32, Column 59: reference to entity "c2" for which no system identifier could be generated
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=17793284&cv=2.0&cj=1" />

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

  • Info Line 32, Column 56: entity was defined here
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=17793284&cv=2.0&cj=1" />
  • Warning Line 32, Column 69: cannot generate system identifier for general entity "cv"
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=17793284&cv=2.0&cj=1" />

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

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

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

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

  • Error Line 32, Column 69: general entity "cv" not defined and no default entity
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=17793284&cv=2.0&cj=1" />

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

  • Warning Line 32, Column 71: reference not terminated by REFC delimiter
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=17793284&cv=2.0&cj=1" />

    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 32, Column 71: reference to external entity in attribute value
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=17793284&cv=2.0&cj=1" />

    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 32, Column 71: reference to entity "cv" for which no system identifier could be generated
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=17793284&cv=2.0&cj=1" />

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

  • Info Line 32, Column 68: entity was defined here
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=17793284&cv=2.0&cj=1" />
  • Warning Line 32, Column 76: cannot generate system identifier for general entity "cj"
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=17793284&cv=2.0&cj=1" />

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

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

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

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

  • Error Line 32, Column 76: general entity "cj" not defined and no default entity
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=17793284&cv=2.0&cj=1" />

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

  • Warning Line 32, Column 78: reference not terminated by REFC delimiter
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=17793284&cv=2.0&cj=1" />

    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 32, Column 78: reference to external entity in attribute value
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=17793284&cv=2.0&cj=1" />

    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 32, Column 78: reference to entity "cj" for which no system identifier could be generated
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=17793284&cv=2.0&cj=1" />

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

  • Info Line 32, Column 75: entity was defined here
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=17793284&cv=2.0&cj=1" />
  • Error Line 32, Column 83: required attribute "alt" not specified
    …    <img src="http://b.scorecardresearch.com/p?c1=2&c2=17793284&cv=2.0&cj=1" />

    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 36, Column 336: document type does not allow element "meta" here
    …, Blog, Nhân ái, Bạn đọc, Việc làm…" /><meta id="ctl00_metaKeywords" name="key…

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

  • Error Line 36, Column 909: document type does not allow element "meta" here
    … youtube, Trung Quốc, Mỹ, biển Đông" /><link href="http://m.dantri.com.vn" rel…

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

  • Error Line 36, Column 1006: document type does not allow element "link" here
    …"only screen and (max-width: 640px)" /><link href="http://m.dantri.com.vn" rel…

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

  • Error Line 36, Column 1077: document type does not allow element "link" here
    …><link href="http://m.dantri.com.vn" rel="alternate" media="handheld" /></head>

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

  • Error Line 36, Column 1084: end tag for "object" omitted, but OMITTAG NO was specified
    …><link href="http://m.dantri.com.vn" rel="alternate" media="handheld" /></head>

    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 31, Column 5: start tag was here
        <noscript>
  • Error Line 115, Column 69: there is no attribute "ref"
    …tl00_Header1_SubMenu1_lnkRss" class="icon-rss2" ref="nofollow" href="/rss"></a>

    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 121, Column 36: document type does not allow element "li" here
            ul_submenu.innerHTML = "<li><a href='http://duhoc.dantri.com.vn' target…

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

  • Error Line 125, Column 36: document type does not allow element "li" here
            ul_submenu.innerHTML = "<li><a target='_blank' href='/viec-lam.htm' >Vi…

    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 158, Column 56: cannot generate system identifier for general entity "XH"
    …       (Dân trí) - Bộ trưởng Bộ LĐ-TB&XH Phạm Thị Hải Chuyền vừa ký thông báo …

    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 158, Column 56: general entity "XH" not defined and no default entity
    …       (Dân trí) - Bộ trưởng Bộ LĐ-TB&XH Phạm Thị Hải Chuyền vừa ký thông báo …

    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 158, Column 58: reference not terminated by REFC delimiter
    …     (Dân trí) - Bộ trưởng Bộ LĐ-TB&XH Phạm Thị Hải Chuyền vừa ký thông báo cô…

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

  • Error Line 158, Column 58: reference to entity "XH" for which no system identifier could be generated
    …     (Dân trí) - Bộ trưởng Bộ LĐ-TB&XH Phạm Thị Hải Chuyền vừa ký thông báo cô…

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

  • Info Line 158, Column 55: entity was defined here
    …        (Dân trí) - Bộ trưởng Bộ LĐ-TB&XH Phạm Thị Hải Chuyền vừa ký thông báo…
  • Error Line 201, Column 99: required attribute "alt" not specified
    …c="http://dantri3.vcmedia.vn/App_Themes/Default/Images/ico_image3.png" />&nbsp;

    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 260, Column 212: duplicate specification of attribute "title"
    …t-bai-cua-viet-nam-1007184.htm" title="Giới chuy&#234;n m&#244;n trong nước ti…

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

  • Error Line 260, Column 1019: duplicate specification of attribute "title"
    …m-sao-biet-de-phat-1007076.htm" title="Xử phạt ATM hết tiền: Người d&#226;n kh…

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

  • Error Line 260, Column 1961: duplicate specification of attribute "title"
    …van-di-thi-quoc-te-1007219.htm" title="Bất chấp chưa được cấp ph&#233;p, người…

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

  • Error Line 263, Column 163: document type does not allow element "div" here
    …at:left;width:620px;padding:5px 0 0 0"><img src="http://dantri3.vcmedia.vn/App…

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

  • Error Line 263, Column 258: required attribute "alt" not specified
    …vcmedia.vn/App_Themes/Default/Images/blank.gif" width="0" height="0"/></div>');

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

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

  • Error Line 305, Column 285: end tag for "br" omitted, but OMITTAG NO was specified
    …vãn được nửa số ki ốt của chợ này.<br><a href='http://dantri.com.vn/xa-hoi/cha…

    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 305, Column 281: start tag was here
    …cứu vãn được nửa số ki ốt của chợ này.<br><a href='http://dantri.com.vn/xa-hoi…
  • Warning Line 311, Column 57: reference not terminated by REFC delimiter
    …  <li> <a  title="Giám đốc Sở LĐ-TB&XH Nghệ An “né” vấn đề XKLĐ “chui”" href="…

    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 311, Column 57: reference to external entity in attribute value
    …  <li> <a  title="Giám đốc Sở LĐ-TB&XH Nghệ An “né” vấn đề XKLĐ “chui”" href="…

    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 311, Column 57: reference to entity "XH" for which no system identifier could be generated
    …  <li> <a  title="Giám đốc Sở LĐ-TB&XH Nghệ An “né” vấn đề XKLĐ “chui”" href="…

    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 158, Column 55: entity was defined here
    …        (Dân trí) - Bộ trưởng Bộ LĐ-TB&XH Phạm Thị Hải Chuyền vừa ký thông báo…
  • Warning Line 311, Column 185: reference not terminated by REFC delimiter
    …chui-1007248.htm">Giám đốc Sở LĐ-TB&XH Nghệ An “né” vấn đề XKLĐ “chui”</a> </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.

  • Error Line 311, Column 185: reference to entity "XH" for which no system identifier could be generated
    …chui-1007248.htm">Giám đốc Sở LĐ-TB&XH Nghệ An “né” vấn đề XKLĐ “chui”</a> </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 158, Column 55: entity was defined here
    …        (Dân trí) - Bộ trưởng Bộ LĐ-TB&XH Phạm Thị Hải Chuyền vừa ký thông báo…
  • Error Line 319, Column 41: ID "nbm-sub-cat" already defined
                        <ul class="ul2" id="nbm-sub-cat">

    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 295, Column 41: ID "nbm-sub-cat" first defined here
                        <ul class="ul2" id="nbm-sub-cat">
  • Warning Line 321, Column 132: character "&" is the first character of a delimiter but occurred as data
    …ef="/the-gioi/eu--nga/trang-1.htm">EU & Nga</a></li><li><a  href="/the-gioi/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.
  • Error Line 335, Column 533: required attribute "alt" not specified
    …hemes/Default/Images/ico_image3.png" />&nbsp; <a  title="Mỹ: Cháy toà nhà 50 t…

    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 343, Column 41: ID "nbm-sub-cat" already defined
                        <ul class="ul2" id="nbm-sub-cat">

    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 295, Column 41: ID "nbm-sub-cat" first defined here
                        <ul class="ul2" id="nbm-sub-cat">
  • Error Line 353, Column 216: end tag for "br" omitted, but OMITTAG NO was specified
    … tra để đưa ra kết luận cuối cùng.<br><a href='http://dantri.com.vn/the-thao/t…

    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 353, Column 212: start tag was here
    …điều tra để đưa ra kết luận cuối cùng.<br><a href='http://dantri.com.vn/the-th…
  • Error Line 353, Column 413: end tag for "br" omitted, but OMITTAG NO was specified
    …ộ liệu có được nhiều tiền”</b></a><br><a href='http://dantri.com.vn/the-thao/v…

    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 353, Column 409: start tag was here
    …án độ liệu có được nhiều tiền”</b></a><br><a href='http://dantri.com.vn/the-th…
  • Error Line 367, Column 41: ID "nbm-sub-cat" already defined
                        <ul class="ul2" id="nbm-sub-cat">

    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 295, Column 41: ID "nbm-sub-cat" first defined here
                        <ul class="ul2" id="nbm-sub-cat">
  • Error Line 377, Column 283: end tag for "br" omitted, but OMITTAG NO was specified
    …ác em không lệ thuộc vào văn mẫu”.<br><a href='http://dantri.com.vn/giao-duc-k…

    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 377, Column 279: start tag was here
    …i, các em không lệ thuộc vào văn mẫu”.<br><a href='http://dantri.com.vn/giao-d…
  • Error Line 377, Column 460: end tag for "br" omitted, but OMITTAG NO was specified
    …áo viên dạy Văn tâm huyết?</b></a><br><a href='http://dantri.com.vn/giao-duc-k…

    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 377, Column 456: start tag was here
    …g giáo viên dạy Văn tâm huyết?</b></a><br><a href='http://dantri.com.vn/giao-d…
  • Error Line 377, Column 688: end tag for "br" omitted, but OMITTAG NO was specified
    …ực hay giả dối của môn Văn</b></a><br><a href='http://dantri.com.vn/giao-duc-k…

    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 377, Column 684: start tag was here
    …g thực hay giả dối của môn Văn</b></a><br><a href='http://dantri.com.vn/giao-d…
  • Error Line 383, Column 116: required attribute "alt" not specified
    …hemes/Default/Images/ico_image3.png" />&nbsp; <a  title="Chùm ảnh: Xót xa bữ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 383, Column 386: "Hũ" is not a member of a group specified for any attribute
    …ình Sáng</a> </li><li> <a  title=""Hũ gạo tình thương" thắm đượm tình quân dân…
  • Error Line 383, Column 390: "gạo" is not a member of a group specified for any attribute
    …Sáng</a> </li><li> <a  title=""Hũ gạo tình thương" thắm đượm tình quân dân vùn…
  • Error Line 383, Column 395: "tình" is not a member of a group specified for any attribute
    …/a> </li><li> <a  title=""Hũ gạo tình thương" thắm đượm tình quân dân vùng biê…
  • Error Line 383, Column 401: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …li><li> <a  title=""Hũ gạo tình thương" thắm đượm tình quân dân vùng biên" hre…

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

  • Error Line 391, Column 41: ID "nbm-sub-cat" already defined
                        <ul class="ul2" id="nbm-sub-cat">

    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 295, Column 41: ID "nbm-sub-cat" first defined here
                        <ul class="ul2" id="nbm-sub-cat">
  • Error Line 413, Column 36: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
                <div class="mt2" style=display:none >
  • Error Line 415, Column 41: ID "nbm-sub-cat" already defined
                        <ul class="ul2" id="nbm-sub-cat">

    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 295, Column 41: ID "nbm-sub-cat" first defined here
                        <ul class="ul2" id="nbm-sub-cat">
  • Error Line 418, Column 25: end tag for "ul" which is not finished
                        </ul>

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

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

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

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

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

  • Error Line 448, Column 225: required attribute "alt" not specified
    …b_w/250/dantri/tI0YUx18mEaF5kMsGHJxA/2014/12/11/Facebook-2014-602cc.jpg" /></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 454, Column 186: required attribute "alt" not specified
    …ia.vn//thumb_w/250/dantri/elVaF199bomfqIyKul5fw/2014/12/11/24-432de.jpg" /></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 458, Column 11: end tag for element "li" which is not open
    						</li>

    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 462, Column 203: required attribute "alt" not specified
    …/thumb_w/250/dantri/hBru1dLDczzwdZ6qEvP0Ag/2014/12/11/igg1214-c5b83.jpg" /></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 466, Column 11: end tag for element "li" which is not open
    						</li>

    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 470, Column 215: required attribute "alt" not specified
    …n//thumb_w/250/dantri/6DQQJ7yW5QPfG6EzuGalSQ/2014/12/11/drone-59e32.jpg" /></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 474, Column 11: end tag for element "li" which is not open
    						</li>

    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 484, Column 37: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
                <div class="mt2"  style=margin-top:301px>
  • Error Line 486, Column 41: ID "nbm-sub-cat" already defined
                        <ul class="ul2" id="nbm-sub-cat">

    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 295, Column 41: ID "nbm-sub-cat" first defined here
                        <ul class="ul2" id="nbm-sub-cat">
  • Error Line 494, Column 41: "Xẻ" is not a member of a group specified for any attribute
    …                  <h3> <a  title=""Xẻ thịt" sân Chi Lăng làm 10 sổ đỏ, đem thế…
  • Error Line 494, Column 45: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …              <h3> <a  title=""Xẻ thịt" sân Chi Lăng làm 10 sổ đỏ, đem thế chấ…

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

  • Error Line 510, Column 41: ID "nbm-sub-cat" already defined
                        <ul class="ul2" id="nbm-sub-cat">

    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 295, Column 41: ID "nbm-sub-cat" first defined here
                        <ul class="ul2" id="nbm-sub-cat">
  • Error Line 518, Column 147: required attribute "alt" not specified
    …/Default/Images/ico_text_video3.png" />&nbsp; <a  title="Triển lãm hình tượng …

    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 526, Column 147: required attribute "alt" not specified
    …/Default/Images/ico_text_video3.png" />&nbsp;<img  border="0" src="http://dant…

    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 526, Column 245: required attribute "alt" not specified
    …hemes/Default/Images/ico_image3.png" />&nbsp; <a  title="Lý Tiểu Long “tái thế…

    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 526, Column 838: required attribute "alt" not specified
    …hemes/Default/Images/ico_image3.png" />&nbsp; <a  title="Những bộ váy đắt giá …

    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 534, Column 41: ID "nbm-sub-cat" already defined
                        <ul class="ul2" id="nbm-sub-cat">

    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 295, Column 41: ID "nbm-sub-cat" first defined here
                        <ul class="ul2" id="nbm-sub-cat">
  • Error Line 542, Column 146: required attribute "alt" not specified
    …/Default/Images/ico_video_text3.png" />&nbsp; <a  title="Mila Kunis tái xuất r…

    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 550, Column 146: required attribute "alt" not specified
    …/Default/Images/ico_video_text3.png" />&nbsp;<img  border="0" src="http://dant…

    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 550, Column 244: required attribute "alt" not specified
    …hemes/Default/Images/ico_image3.png" />&nbsp; <a  title="Những ngôi sao đột ph…

    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 550, Column 505: required attribute "alt" not specified
    …hemes/Default/Images/ico_image3.png" />&nbsp; <a  title="Hoa hậu Mai Phương Th…

    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 550, Column 832: required attribute "alt" not specified
    …/Default/Images/ico_video_text3.png" />&nbsp; <a  title="Chia tay hoa hậu Jenn…

    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 558, Column 41: ID "nbm-sub-cat" already defined
                        <ul class="ul2" id="nbm-sub-cat">

    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 295, Column 41: ID "nbm-sub-cat" first defined here
                        <ul class="ul2" id="nbm-sub-cat">
  • Error Line 582, Column 41: ID "nbm-sub-cat" already defined
                        <ul class="ul2" id="nbm-sub-cat">

    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 295, Column 41: ID "nbm-sub-cat" first defined here
                        <ul class="ul2" id="nbm-sub-cat">
  • Error Line 590, Column 146: required attribute "alt" not specified
    …/Default/Images/ico_video_text3.png" />&nbsp; <a  title="Chuyện hoa hậu, AFF C…

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

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

  • Error Line 590, Column 208: "phong" is not a member of a group specified for any attribute
    …n hoa hậu, AFF Cup vào bản tin "phong cách Rap"" class="fon6" href="/nhip-song…
  • Error Line 590, Column 213: "cách" is not a member of a group specified for any attribute
    … hậu, AFF Cup vào bản tin "phong cách Rap"" class="fon6" href="/nhip-song-tre/…
  • Error Line 590, Column 216: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …u, AFF Cup vào bản tin "phong cách Rap"" class="fon6" href="/nhip-song-tre/chu…

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

  • Error Line 598, Column 116: required attribute "alt" not specified
    …hemes/Default/Images/ico_image3.png" />&nbsp; <a  title="Tuyệt đẹp bộ ảnh hai …

    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 606, Column 41: ID "nbm-sub-cat" already defined
                        <ul class="ul2" id="nbm-sub-cat">

    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 295, Column 41: ID "nbm-sub-cat" first defined here
                        <ul class="ul2" id="nbm-sub-cat">
  • Error Line 622, Column 147: required attribute "alt" not specified
    …/Default/Images/ico_text_video3.png" />&nbsp; <a  title="Vẻ bối rối đáng yêu c…

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

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

  • Error Line 630, Column 41: ID "nbm-sub-cat" already defined
                        <ul class="ul2" id="nbm-sub-cat">

    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 295, Column 41: ID "nbm-sub-cat" first defined here
                        <ul class="ul2" id="nbm-sub-cat">
  • Error Line 654, Column 41: ID "nbm-sub-cat" already defined
                        <ul class="ul2" id="nbm-sub-cat">

    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 295, Column 41: ID "nbm-sub-cat" first defined here
                        <ul class="ul2" id="nbm-sub-cat">
  • Error Line 678, Column 41: ID "nbm-sub-cat" already defined
                        <ul class="ul2" id="nbm-sub-cat">

    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 295, Column 41: ID "nbm-sub-cat" first defined here
                        <ul class="ul2" id="nbm-sub-cat">
  • Error Line 695, Column 116: required attribute "alt" not specified
    …hemes/Default/Images/ico_image3.png" />&nbsp; <a  title="Dàn mẫu xinh đẹp tại …

    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 703, Column 41: ID "nbm-sub-cat" already defined
                        <ul class="ul2" id="nbm-sub-cat">

    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 295, Column 41: ID "nbm-sub-cat" first defined here
                        <ul class="ul2" id="nbm-sub-cat">
  • Error Line 727, Column 41: ID "nbm-sub-cat" already defined
                        <ul class="ul2" id="nbm-sub-cat">

    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 295, Column 41: ID "nbm-sub-cat" first defined here
                        <ul class="ul2" id="nbm-sub-cat">
  • Error Line 751, Column 41: ID "nbm-sub-cat" already defined
                        <ul class="ul2" id="nbm-sub-cat">

    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 295, Column 41: ID "nbm-sub-cat" first defined here
                        <ul class="ul2" id="nbm-sub-cat">
  • Error Line 767, Column 90: "chơi" is not a member of a group specified for any attribute
    …Ngôi nhà độc đáo nhất thế giới: "chơi nhạc" khi trời mưa" href="/du-lich/ngoi-…
  • Error Line 767, Column 94: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    … nhà độc đáo nhất thế giới: "chơi nhạc" khi trời mưa" href="/du-lich/ngoi-nha-…

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

  • Error Line 767, Column 353: required attribute "alt" not specified
    …hemes/Default/Images/ico_image3.png" />&nbsp; <a target="_blank" title="Vẻ đẹp…

    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 767, Column 670: required attribute "alt" not specified
    …hemes/Default/Images/ico_image3.png" />&nbsp; <a target="_blank" title="Xem 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>.

  • Error Line 775, Column 41: ID "nbm-sub-cat" already defined
                        <ul class="ul2" id="nbm-sub-cat">

    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 295, Column 41: ID "nbm-sub-cat" first defined here
                        <ul class="ul2" id="nbm-sub-cat">
  • Error Line 799, Column 41: ID "nbm-sub-cat" already defined
                        <ul class="ul2" id="nbm-sub-cat">

    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 295, Column 41: ID "nbm-sub-cat" first defined here
                        <ul class="ul2" id="nbm-sub-cat">
  • Error Line 809, Column 356: end tag for "br" omitted, but OMITTAG NO was specified
    … liên tỉnh tại các địa phương này.<br><a href='http://dantri.com.vn/giao-duc-k…

    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 809, Column 352: start tag was here
    … thi liên tỉnh tại các địa phương này.<br><a href='http://dantri.com.vn/giao-d…
  • Error Line 823, Column 41: ID "nbm-sub-cat" already defined
                        <ul class="ul2" id="nbm-sub-cat">

    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 295, Column 41: ID "nbm-sub-cat" first defined here
                        <ul class="ul2" id="nbm-sub-cat">
  • Error Line 831, Column 116: required attribute "alt" not specified
    …hemes/Default/Images/ico_image3.png" />&nbsp; <a target="_blank" title="Mùa th…

    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 847, Column 41: ID "nbm-sub-cat" already defined
                        <ul class="ul2" id="nbm-sub-cat">

    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 295, Column 41: ID "nbm-sub-cat" first defined here
                        <ul class="ul2" id="nbm-sub-cat">
  • Error Line 855, Column 141: required attribute "alt" not specified
    …Themes/Default/Images/icon_blog.png" />&nbsp; <a  title="Lấy phiếu tín nhiệm c…

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

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

  • Error Line 857, Column 236: end tag for "br" omitted, but OMITTAG NO was specified
    … 16 HĐND TP.HCM khóa VIII vừa qua.<br><a href='http://dantri.com.vn/xa-hoi/lay…

    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 857, Column 232: start tag was here
    … thứ 16 HĐND TP.HCM khóa VIII vừa qua.<br><a href='http://dantri.com.vn/xa-hoi…
  • Error Line 857, Column 444: end tag for "br" omitted, but OMITTAG NO was specified
    …y nhất để đánh giá cán bộ”</b></a><br><a href='http://dantri.com.vn/xa-hoi/gia…

    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 857, Column 440: start tag was here
    …h duy nhất để đánh giá cán bộ”</b></a><br><a href='http://dantri.com.vn/xa-hoi…
  • Error Line 857, Column 661: end tag for "br" omitted, but OMITTAG NO was specified
    …h "đội sổ" phiếu tín nhiệm</b></a><br><a href='http://dantri.com.vn/xa-hoi/gd-…

    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 857, Column 657: start tag was here
    … tỉnh "đội sổ" phiếu tín nhiệm</b></a><br><a href='http://dantri.com.vn/xa-hoi…
  • Error Line 863, Column 141: required attribute "alt" not specified
    …Themes/Default/Images/icon_blog.png" />&nbsp; <a  title="Cổ động viên Việt Nam…

    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 863, Column 426: required attribute "alt" not specified
    …Themes/Default/Images/icon_blog.png" />&nbsp; <a  title="Từ chuyện ông Nghiên …

    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 863, Column 744: required attribute "alt" not specified
    …Themes/Default/Images/icon_blog.png" />&nbsp; <a  title="Một khi quan tỉnh cũn…

    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 871, Column 41: ID "nbm-sub-cat" already defined
                        <ul class="ul2" id="nbm-sub-cat">

    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 295, Column 41: ID "nbm-sub-cat" first defined here
                        <ul class="ul2" id="nbm-sub-cat">
  • Error Line 881, Column 124: end tag for "br" omitted, but OMITTAG NO was specified
    …hắc các lựa chọn một cách kỹ càng.<br><a href='http://dantri.com.vn/chung-toi-…

    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 881, Column 120: start tag was here
    …ân nhắc các lựa chọn một cách kỹ càng.<br><a href='http://dantri.com.vn/chung-…
  • Error Line 881, Column 332: end tag for "br" omitted, but OMITTAG NO was specified
    …ng suất cao nhất thế giới?</b></a><br><a href='http://dantri.com.vn/chung-toi-…

    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 881, Column 328: start tag was here
    …à năng suất cao nhất thế giới?</b></a><br><a href='http://dantri.com.vn/chung-…
  • Error Line 881, Column 549: end tag for "br" omitted, but OMITTAG NO was specified
    …chấm dứt hợp đồng lao động</b></a><br><a href='http://dantri.com.vn/chung-toi-…

    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 881, Column 545: start tag was here
    …khi chấm dứt hợp đồng lao động</b></a><br><a href='http://dantri.com.vn/chung-…
  • Error Line 897, Column 39: there is no attribute "name"
                                <div name='column' style='padding-bottom: 5px; floa…

    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 1012, Column 33: required attribute "alt" not specified
                        border="0" />

    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 1042, Column 11: end tag for "div" omitted, but OMITTAG NO was specified
        </form>

    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 145, Column 5: start tag was here
        <div class="wrapper">

Visitor Analysis

Daily Visitor
  • 114 visits

In Page Analysis