blogviet.com.vn

Blog Radio kênh giải trí hàng đầu được phát triển bởi VNNPlus. Blog Radio (blogviet) đã đăng ký Bản quyền Tác giả cho VNNplus. Nghe - download blog radio mới nhất. ...

Display Widget for this domain on your website. Click Here
Processing update domain...

Overview Info

  • Domain Name
    blogviet.com.vn
  • Favicon
  • Alexa Rank
    #259536
  • Google Page Rank
    PR 2
  • Ip Address
    183.91.14.101
  • Page Size
    91.4 KB
  • Images
    11 GIF, 27 JPG, 6 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 20 20 0 0 0

Website Meta Analysis



  • Title
    Blog Radio, Nghe Blogviet online, Download Blog Radio, Blogviet
  • Meta Keyword
    blog radio, nghe blog radio, download blog radio, blog radio moi nhat
  • Meta Description
    Blog Radio kênh giải trí hàng đầu được phát triển bởi VNNPlus. Blog Radio (blogviet) đã đăng ký Bản quyền Tác giả cho VNNplus. Nghe - download blog radio mới nhất.

Technical Analysis



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

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

HTML Analysis

  • cache-control: private
  • date: Sat, 14 Sep 2013 14:48:01 GMT
  • content-type: text/html; charset=utf-8
  • server: Microsoft-IIS/6.0
  • x-powered-by: ASP.NET
  • x-aspnet-version: 4.0.30319
  • x-aspnetmvc-version: 3.0
  • content-encoding: gzip
  • vary: Accept-Encoding
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for blogviet.com.vn

DNS Analysis


DNS servers
ns1.vdconline.vn [123.30.176.242]
ns2.vdconline.vn [123.30.176.243]


DNS Records

Answer records
blogviet.com.vn SOA
server: ns1.vdconline.vn
email: vdconline@tld
serial: 2012110106
refresh: 28800
retry: 7200
expire: 12096
minimum ttl: 864
864s
blogviet.com.vn A 183.91.14.101 864s
blogviet.com.vn NS  ns2.vdconline.vn 864s
blogviet.com.vn NS  ns1.vdconline.vn 864s

Authority records

Additional records
ns1.vdconline.vn A 123.30.176.242 86400s
ns2.vdconline.vn A 123.30.176.243 86400s

IP 183.91.14.101 Analysis

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

    inetnum: 183.91.10.0 - 183.91.15.255
    netname: Leasedline-NET
    country: vn
    descr: Leased line service
    admin-c: NPK4-AP
    tech-c: NTN2-AP
    status: ALLOCATED NON-PORTABLE
    changed: hm-changed@vnnic.net.vn20110215 20110215
    mnt-by: MAINT-VN-VNNIC
    mnt-irt: IRT-VNNIC-AP
    source: APNIC

    person: Nguyen Phu Kieu
    nic-hdl: NPK4-AP
    e-mail: admin@cmcti.vn
    address: CMC Telecom Infrastructure Company
    address: Tang 3, 16 Lieu Giai str, Ba Dinh, Ha Noi
    phone: +84-4-37674688
    country: VN
    changed: hm-changed@vnnic.net.vn 20101004
    mnt-by: MAINT-VN-VNNIC
    source: APNIC

    person: Nguyen Thanh Nam
    nic-hdl: NTN2-AP
    e-mail: nam.nt@cmcti.vn
    address: CMC Telecom Infrastructure Company
    address: Tang 3, 16 Lieu Giai str, Ba Dinh, Ha Noi
    phone: +84-4-37674688
    country: VN
    changed: hm-changed@vnnic.net.vn 20091120
    mnt-by: MAINT-VN-VNNIC
    source: APNIC


Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 92 Errors
  • 49 Warnings
Ratio Text/Html
  • 0.5095876354774578
Message Error
  • Error Line 122, Column 43: document type does not allow element "style" here
                        <style type="text/css">

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

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

  • Error Line 174, Column 37: there is no attribute "onmouseout"
                    <marquee onmouseout="this.start()" onmouseover="this.stop()">

    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 174, Column 64: there is no attribute "onmouseover"
                    <marquee onmouseout="this.start()" onmouseover="this.stop()">

    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 174, Column 77: element "marquee" undefined
                    <marquee onmouseout="this.start()" onmouseover="this.stop()">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 186, Column 46: there is no attribute "data-position"
    …     <div class="Slide" data-position="20,200" data-width="400" data-caption_b…

    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 186, Column 66: there is no attribute "data-width"
    …"Slide" data-position="20,200" data-width="400" data-caption_bg_color="#665543"

    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 186, Column 94: there is no attribute "data-caption_bg_color"
    …"Slide" data-position="20,200" data-width="400" data-caption_bg_color="#665543"

    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 187, Column 41: there is no attribute "data-caption_bg_opacity"
                    data-caption_bg_opacity="0.5">

    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 245, Column 92: required attribute "alt" not specified
    …     <img src="/Content/Domain/blogviet/images/title_thiviet.jpg" 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 278, Column 193: required attribute "alt" not specified
    …Ngay_2/dung-lai1-td.jpg" style="width:300px;height:195px;overflow:hidden;"></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 278, Column 197: end tag for "img" omitted, but OMITTAG NO was specified
    …Ngay_2/dung-lai1-td.jpg" style="width:300px;height:195px;overflow:hidden;"></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 278, Column 37: start tag was here
                                        <img border="0" src="http://media.nhacvietp…
  • Error Line 306, Column 198: required attribute "alt" not specified
    …22/thi-tham-233--1.jpg" style="width:300px;height:200px;overflow:hidden;"/></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 331, Column 213: required attribute "alt" not specified
    …bang-ca-yeu-thuong.jpg" style="width:300px;height:200px;overflow:hidden;"/></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 356, Column 204: required attribute "alt" not specified
    …1053298_c13db697ce.jpg" style="width:300px;height:200px;overflow:hidden;"/></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 384, Column 196: required attribute "alt" not specified
    …y_29/mie1327338238.jpg" style="width:300px;height:200px;overflow:hidden;"/></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 410, Column 191: required attribute "alt" not specified
    …1/Ngay_31/duong-td.jpg" style="width:300px;height:200px;overflow:hidden;"/></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 433, Column 123: required attribute "alt" not specified
    …<img border="0" src="/content/domain/blogviet/images/bat-dc-tinh-yeu1.gif"></a>

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

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

  • Error Line 433, Column 127: end tag for "img" omitted, but OMITTAG NO was specified
    …<img border="0" src="/content/domain/blogviet/images/bat-dc-tinh-yeu1.gif"></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 433, Column 49: start tag was here
    <img border="0" src="/content/domain/blo…
  • Error Line 443, Column 194: required attribute "alt" not specified
    …gay_22/rain_couple.jpg" style="width:300px;height:200px;overflow:hidden;"/></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 468, Column 200: required attribute "alt" not specified
    …hoa222 (188 x 125).jpg" style="width:300px;height:200px;overflow:hidden;"/></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 493, Column 185: required attribute "alt" not specified
    …Thang_2/Ngay_22/40.jpg" style="width:300px;height:200px;overflow:hidden;"/></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 518, Column 195: required attribute "alt" not specified
    …ay_20/Images/47-td.JPG" style="width:300px;height:200px;overflow:hidden;"/></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 542, Column 202: required attribute "alt" not specified
    …at-duoc-tinh-yeu-5.jpg" style="width:300px;height:200px;overflow:hidden;"/></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 566, Column 218: required attribute "alt" not specified
    …me_thu (188 x 125).jpg" style="width:300px;height:200px;overflow:hidden;"/></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 590, Column 188: required attribute "alt" not specified
    …ng_2/Ngay_8/doitay.jpg" style="width:300px;height:200px;overflow:hidden;"/></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 614, Column 204: required attribute "alt" not specified
    …oc-song-la-nhu-the.jpg" style="width:300px;height:200px;overflow:hidden;"/></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 635, Column 122: required attribute "alt" not specified
    … <img border="0" src="/content/domain/blogviet/images/Tet-PCS-640x100.gif"></a>

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

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

  • Error Line 635, Column 126: end tag for "img" omitted, but OMITTAG NO was specified
    … <img border="0" src="/content/domain/blogviet/images/Tet-PCS-640x100.gif"></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 635, Column 49: start tag was here
    <img border="0" src="/content/domain/blo…
  • Error Line 641, Column 23: document type does not allow element "style" here
    <style type="text/css">

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

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

  • Warning Line 745, Column 73: cannot generate system identifier for general entity "body"
    …         <td> <a href="mailto:blogviet@dalink.vn?subject=Hi-Blog-Viet&body=Hi">

    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 745, Column 73: general entity "body" not defined and no default entity
    …         <td> <a href="mailto:blogviet@dalink.vn?subject=Hi-Blog-Viet&body=Hi">

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

  • Warning Line 745, Column 77: reference not terminated by REFC delimiter
    …         <td> <a href="mailto:blogviet@dalink.vn?subject=Hi-Blog-Viet&body=Hi">

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

  • Warning Line 745, Column 77: reference to external entity in attribute value
    …         <td> <a href="mailto:blogviet@dalink.vn?subject=Hi-Blog-Viet&body=Hi">

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

  • Error Line 745, Column 77: reference to entity "body" for which no system identifier could be generated
    …         <td> <a href="mailto:blogviet@dalink.vn?subject=Hi-Blog-Viet&body=Hi">

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

  • Info Line 745, Column 72: entity was defined here
    …         <td> <a href="mailto:blogviet@dalink.vn?subject=Hi-Blog-Viet&body=Hi">
  • Error Line 746, Column 83: required attribute "alt" not specified
    …    <img border="0" src="/content/domain/blogviet/images/icon_guibai.gif"/></a>

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

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

  • Error Line 750, Column 83: required attribute "alt" not specified
    …       <img border="0" src="/content/domain/blogviet/images/icon_yh.gif"/></a> 

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

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

  • Error Line 754, Column 88: required attribute "alt" not specified
    …       <img border="0" src="/content/domain/blogviet/images/icon_rss.gif"/></a>

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

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

  • Error Line 772, Column 237: end tag for "input" omitted, but OMITTAG NO was specified
    …) this.value='';" onblur="if (this.value=='') this.value='Tìm kiếm...';"></div>

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

  • Info Line 772, Column 13: start tag was here
                <input type="text" value="Tìm kiếm..." name="keyword" class="input-…
  • Error Line 888, Column 204: required attribute "type" not specified
    …annel=yeublogradio&amp;synd=open&amp;w=311&amp;h=350&amp;title=&amp;output=js">

    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 896, Column 32: required attribute "type" not specified
                            <script>

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

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

  • Error Line 907, Column 99: there is no attribute "data-href"
    … width:300px; border:none;" data-href="http://www.facebook.com/yeublogviet" da…

    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 907, Column 170: there is no attribute "data-show-faces"
    …iet" data-width="315" data-show-faces="true" data-stream="false" data-header="…

    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 907, Column 189: there is no attribute "data-stream"
    …5" data-show-faces="true" data-stream="false" data-header="false" border-color…

    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 907, Column 209: there is no attribute "data-header"
    …show-faces="true" data-stream="false" data-header="false" border-color="false">

    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 907, Column 230: there is no attribute "border-color"
    …show-faces="true" data-stream="false" data-header="false" border-color="false">

    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 990, Column 226: required attribute "alt" not specified
    …idth="313px" style="-moz-border-radius: 10px;-webkit-border-radius: 10px;"></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 990, Column 230: end tag for "img" omitted, but OMITTAG NO was specified
    …idth="313px" style="-moz-border-radius: 10px;-webkit-border-radius: 10px;"></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 990, Column 29: start tag was here
                                <img border="0" src="http://media.nhacvietplus.com.…
  • Error Line 1010, Column 195: required attribute "alt" not specified
    …idth="313px" style="-moz-border-radius: 10px;-webkit-border-radius: 10px;"></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 1010, Column 199: end tag for "img" omitted, but OMITTAG NO was specified
    …idth="313px" style="-moz-border-radius: 10px;-webkit-border-radius: 10px;"></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 1010, Column 21: start tag was here
                        <img border="0" src="/content/domain/blogviet/images/banner…
  • Error Line 1016, Column 50: character "/" is not allowed in the value of attribute "id"
    …         width="315" height="446" id="/content/domain/blogviet/images/315x446.…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 1017, Column 28: syntax of attribute value does not conform to declared value
                        align="">

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 1017, Column 28: value of attribute "align" cannot be ""; must be one of "top", "middle", "bottom", "left", "right"
                        align="">

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 1018, Column 93: end tag for "param" omitted, but OMITTAG NO was specified
    …       <param name="movie" value="/content/domain/blogviet/images/315x446.swf">

    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 1018, Column 21: start tag was here
                        <param name="movie" value="/content/domain/blogviet/images/…
  • Error Line 1019, Column 56: end tag for "param" omitted, but OMITTAG NO was specified
                        <param name="quality" value="high">

    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 1019, Column 21: start tag was here
                        <param name="quality" value="high">
  • Error Line 1020, Column 59: end tag for "param" omitted, but OMITTAG NO was specified
                        <param name="bgcolor" value="#333399">

    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 1020, Column 21: start tag was here
                        <param name="bgcolor" value="#333399">
  • Error Line 1021, Column 32: there is no attribute "src"
                        <embed src="/content/domain/blogviet/images/315x446.swf"

    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 1022, Column 33: there is no attribute "quality"
                            quality="high" bgcolor="#333399" width="315" height="44…

    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 1022, Column 48: there is no attribute "bgcolor"
    …               quality="high" bgcolor="#333399" width="315" height="446" name=…

    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 1022, Column 64: there is no attribute "width"
    …  quality="high" bgcolor="#333399" width="315" height="446" name="Yourfilename"

    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 1022, Column 77: there is no attribute "height"
    …  quality="high" bgcolor="#333399" width="315" height="446" name="Yourfilename"

    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 1022, Column 88: there is no attribute "name"
    …  quality="high" bgcolor="#333399" width="315" height="446" name="Yourfilename"

    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 1023, Column 31: there is no attribute "align"
                            align="" type="application/x-shockwave-flash" pluginspa…

    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 1023, Column 39: there is no attribute "type"
                            align="" type="application/x-shockwave-flash" pluginspa…

    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 1023, Column 83: there is no attribute "pluginspage"
    …cation/x-shockwave-flash" pluginspage="http://www.macromedia.com/go/getflashpl…

    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 1023, Column 128: element "embed" undefined
    …n/x-shockwave-flash" 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).
  • Error Line 1063, Column 23: ID "menu_tab_bottom" already defined
                 <div id="menu_tab_bottom" style="margin:0 0 0 50px;">

    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 1038, Column 14: ID "menu_tab_bottom" first defined here
        <div id="menu_tab_bottom" style="margin:0 0 0 20px;">
  • Warning Line 1161, Column 83: cannot generate system identifier for general entity "telco"
    …acvietplus.com.vn/NhacCho/99/266/0/1?&telco=viettel&key=&type=">Nhạc Chờ Viett…

    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 1161, Column 83: general entity "telco" not defined and no default entity
    …acvietplus.com.vn/NhacCho/99/266/0/1?&telco=viettel&key=&type=">Nhạc Chờ Viett…

    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 1161, Column 88: reference not terminated by REFC delimiter
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=viettel&key=&type=">Nhạc Chờ Viettel</a…

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

  • Warning Line 1161, Column 88: reference to external entity in attribute value
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=viettel&key=&type=">Nhạc Chờ Viettel</a…

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

  • Error Line 1161, Column 88: reference to entity "telco" for which no system identifier could be generated
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=viettel&key=&type=">Nhạc Chờ Viettel</a…

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

  • Info Line 1161, Column 82: entity was defined here
    …hacvietplus.com.vn/NhacCho/99/266/0/1?&telco=viettel&key=&type=">Nhạc Chờ Viet…
  • Warning Line 1161, Column 97: cannot generate system identifier for general entity "key"
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=viettel&key=&type=">Nhạc Chờ Viettel</a>

    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 1161, Column 97: general entity "key" not defined and no default entity
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=viettel&key=&type=">Nhạc Chờ Viettel</a>

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

  • Warning Line 1161, Column 100: reference not terminated by REFC delimiter
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=viettel&key=&type=">Nhạc Chờ Viettel</a>

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

  • Warning Line 1161, Column 100: reference to external entity in attribute value
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=viettel&key=&type=">Nhạc Chờ Viettel</a>

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

  • Error Line 1161, Column 100: reference to entity "key" for which no system identifier could be generated
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=viettel&key=&type=">Nhạc Chờ Viettel</a>

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

  • Info Line 1161, Column 96: entity was defined here
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=viettel&key=&type=">Nhạc Chờ Viettel</a>
  • Warning Line 1161, Column 102: cannot generate system identifier for general entity "type"
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=viettel&key=&type=">Nhạc Chờ Viettel</a>

    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 1161, Column 102: general entity "type" not defined and no default entity
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=viettel&key=&type=">Nhạc Chờ Viettel</a>

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

  • Warning Line 1161, Column 106: reference not terminated by REFC delimiter
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=viettel&key=&type=">Nhạc Chờ Viettel</a>

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

  • Warning Line 1161, Column 106: reference to external entity in attribute value
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=viettel&key=&type=">Nhạc Chờ Viettel</a>

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

  • Error Line 1161, Column 106: reference to entity "type" for which no system identifier could be generated
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=viettel&key=&type=">Nhạc Chờ Viettel</a>

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

  • Info Line 1161, Column 101: entity was defined here
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=viettel&key=&type=">Nhạc Chờ Viettel</a>
  • Warning Line 1163, Column 88: reference not terminated by REFC delimiter
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=mobilephone&key=&type=">Nhạc Chờ Mobifo…

    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 1163, Column 88: reference to external entity in attribute value
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=mobilephone&key=&type=">Nhạc Chờ Mobifo…

    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 1163, Column 88: reference to entity "telco" for which no system identifier could be generated
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=mobilephone&key=&type=">Nhạc Chờ Mobifo…

    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 1161, Column 82: entity was defined here
    …hacvietplus.com.vn/NhacCho/99/266/0/1?&telco=viettel&key=&type=">Nhạc Chờ Viet…
  • Warning Line 1163, Column 104: reference not terminated by REFC delimiter
    ….com.vn/NhacCho/99/266/0/1?&telco=mobilephone&key=&type=">Nhạc Chờ Mobifone</a>

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

  • Warning Line 1163, Column 104: reference to external entity in attribute value
    ….com.vn/NhacCho/99/266/0/1?&telco=mobilephone&key=&type=">Nhạc Chờ Mobifone</a>

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

  • Error Line 1163, Column 104: reference to entity "key" for which no system identifier could be generated
    ….com.vn/NhacCho/99/266/0/1?&telco=mobilephone&key=&type=">Nhạc Chờ Mobifone</a>

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

  • Info Line 1161, Column 96: entity was defined here
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=viettel&key=&type=">Nhạc Chờ Viettel</a>
  • Warning Line 1163, Column 110: reference not terminated by REFC delimiter
    ….com.vn/NhacCho/99/266/0/1?&telco=mobilephone&key=&type=">Nhạc Chờ Mobifone</a>

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

  • Warning Line 1163, Column 110: reference to external entity in attribute value
    ….com.vn/NhacCho/99/266/0/1?&telco=mobilephone&key=&type=">Nhạc Chờ Mobifone</a>

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

  • Error Line 1163, Column 110: reference to entity "type" for which no system identifier could be generated
    ….com.vn/NhacCho/99/266/0/1?&telco=mobilephone&key=&type=">Nhạc Chờ Mobifone</a>

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

  • Info Line 1161, Column 101: entity was defined here
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=viettel&key=&type=">Nhạc Chờ Viettel</a>
  • Warning Line 1165, Column 88: reference not terminated by REFC delimiter
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=vinaphone&key=&type=">Nhạc Chờ Vinaphon…

    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 1165, Column 88: reference to external entity in attribute value
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=vinaphone&key=&type=">Nhạc Chờ Vinaphon…

    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 1165, Column 88: reference to entity "telco" for which no system identifier could be generated
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=vinaphone&key=&type=">Nhạc Chờ Vinaphon…

    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 1161, Column 82: entity was defined here
    …hacvietplus.com.vn/NhacCho/99/266/0/1?&telco=viettel&key=&type=">Nhạc Chờ Viet…
  • Warning Line 1165, Column 102: reference not terminated by REFC delimiter
    …s.com.vn/NhacCho/99/266/0/1?&telco=vinaphone&key=&type=">Nhạc Chờ Vinaphone</a>

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

  • Warning Line 1165, Column 102: reference to external entity in attribute value
    …s.com.vn/NhacCho/99/266/0/1?&telco=vinaphone&key=&type=">Nhạc Chờ Vinaphone</a>

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

  • Error Line 1165, Column 102: reference to entity "key" for which no system identifier could be generated
    …s.com.vn/NhacCho/99/266/0/1?&telco=vinaphone&key=&type=">Nhạc Chờ Vinaphone</a>

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

  • Info Line 1161, Column 96: entity was defined here
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=viettel&key=&type=">Nhạc Chờ Viettel</a>
  • Warning Line 1165, Column 108: reference not terminated by REFC delimiter
    …s.com.vn/NhacCho/99/266/0/1?&telco=vinaphone&key=&type=">Nhạc Chờ Vinaphone</a>

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

  • Warning Line 1165, Column 108: reference to external entity in attribute value
    …s.com.vn/NhacCho/99/266/0/1?&telco=vinaphone&key=&type=">Nhạc Chờ Vinaphone</a>

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

  • Error Line 1165, Column 108: reference to entity "type" for which no system identifier could be generated
    …s.com.vn/NhacCho/99/266/0/1?&telco=vinaphone&key=&type=">Nhạc Chờ Vinaphone</a>

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

  • Info Line 1161, Column 101: entity was defined here
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=viettel&key=&type=">Nhạc Chờ Viettel</a>
  • Warning Line 1167, Column 88: reference not terminated by REFC delimiter
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=vietnammobile&key=&type=">Nhạc Chờ Viet…

    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 1167, Column 88: reference to external entity in attribute value
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=vietnammobile&key=&type=">Nhạc Chờ Viet…

    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 1167, Column 88: reference to entity "telco" for which no system identifier could be generated
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=vietnammobile&key=&type=">Nhạc Chờ Viet…

    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 1161, Column 82: entity was defined here
    …hacvietplus.com.vn/NhacCho/99/266/0/1?&telco=viettel&key=&type=">Nhạc Chờ Viet…
  • Warning Line 1167, Column 106: reference not terminated by REFC delimiter
    …NhacCho/99/266/0/1?&telco=vietnammobile&key=&type=">Nhạc Chờ Vietnam Mobile</a>

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

  • Warning Line 1167, Column 106: reference to external entity in attribute value
    …NhacCho/99/266/0/1?&telco=vietnammobile&key=&type=">Nhạc Chờ Vietnam Mobile</a>

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

  • Error Line 1167, Column 106: reference to entity "key" for which no system identifier could be generated
    …NhacCho/99/266/0/1?&telco=vietnammobile&key=&type=">Nhạc Chờ Vietnam Mobile</a>

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

  • Info Line 1161, Column 96: entity was defined here
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=viettel&key=&type=">Nhạc Chờ Viettel</a>
  • Warning Line 1167, Column 112: reference not terminated by REFC delimiter
    …NhacCho/99/266/0/1?&telco=vietnammobile&key=&type=">Nhạc Chờ Vietnam Mobile</a>

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

  • Warning Line 1167, Column 112: reference to external entity in attribute value
    …NhacCho/99/266/0/1?&telco=vietnammobile&key=&type=">Nhạc Chờ Vietnam Mobile</a>

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

  • Error Line 1167, Column 112: reference to entity "type" for which no system identifier could be generated
    …NhacCho/99/266/0/1?&telco=vietnammobile&key=&type=">Nhạc Chờ Vietnam Mobile</a>

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

  • Info Line 1161, Column 101: entity was defined here
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=viettel&key=&type=">Nhạc Chờ Viettel</a>
  • Warning Line 1168, Column 88: reference not terminated by REFC delimiter
    …ietplus.com.vn/NhacCho/99/266/0/1?&telco=sphone&key=&type=">Nhạc Chờ S-fone</a>

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

  • Warning Line 1168, Column 88: reference to external entity in attribute value
    …ietplus.com.vn/NhacCho/99/266/0/1?&telco=sphone&key=&type=">Nhạc Chờ S-fone</a>

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

  • Error Line 1168, Column 88: reference to entity "telco" for which no system identifier could be generated
    …ietplus.com.vn/NhacCho/99/266/0/1?&telco=sphone&key=&type=">Nhạc Chờ S-fone</a>

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

  • Info Line 1161, Column 82: entity was defined here
    …hacvietplus.com.vn/NhacCho/99/266/0/1?&telco=viettel&key=&type=">Nhạc Chờ Viet…
  • Warning Line 1168, Column 99: reference not terminated by REFC delimiter
    …ietplus.com.vn/NhacCho/99/266/0/1?&telco=sphone&key=&type=">Nhạc Chờ S-fone</a>

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

  • Warning Line 1168, Column 99: reference to external entity in attribute value
    …ietplus.com.vn/NhacCho/99/266/0/1?&telco=sphone&key=&type=">Nhạc Chờ S-fone</a>

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

  • Error Line 1168, Column 99: reference to entity "key" for which no system identifier could be generated
    …ietplus.com.vn/NhacCho/99/266/0/1?&telco=sphone&key=&type=">Nhạc Chờ S-fone</a>

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

  • Info Line 1161, Column 96: entity was defined here
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=viettel&key=&type=">Nhạc Chờ Viettel</a>
  • Warning Line 1168, Column 105: reference not terminated by REFC delimiter
    …ietplus.com.vn/NhacCho/99/266/0/1?&telco=sphone&key=&type=">Nhạc Chờ S-fone</a>

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

  • Warning Line 1168, Column 105: reference to external entity in attribute value
    …ietplus.com.vn/NhacCho/99/266/0/1?&telco=sphone&key=&type=">Nhạc Chờ S-fone</a>

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

  • Error Line 1168, Column 105: reference to entity "type" for which no system identifier could be generated
    …ietplus.com.vn/NhacCho/99/266/0/1?&telco=sphone&key=&type=">Nhạc Chờ S-fone</a>

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

  • Info Line 1161, Column 101: entity was defined here
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=viettel&key=&type=">Nhạc Chờ Viettel</a>
  • Warning Line 1170, Column 88: reference not terminated by REFC delimiter
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=beeline&key=&type=">Nhạc Chờ Beeline</a…

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

  • Warning Line 1170, Column 88: reference to external entity in attribute value
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=beeline&key=&type=">Nhạc Chờ Beeline</a…

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

  • Error Line 1170, Column 88: reference to entity "telco" for which no system identifier could be generated
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=beeline&key=&type=">Nhạc Chờ Beeline</a…

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

  • Info Line 1161, Column 82: entity was defined here
    …hacvietplus.com.vn/NhacCho/99/266/0/1?&telco=viettel&key=&type=">Nhạc Chờ Viet…
  • Warning Line 1170, Column 100: reference not terminated by REFC delimiter
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=beeline&key=&type=">Nhạc Chờ Beeline</a>

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

  • Warning Line 1170, Column 100: reference to external entity in attribute value
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=beeline&key=&type=">Nhạc Chờ Beeline</a>

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

  • Error Line 1170, Column 100: reference to entity "key" for which no system identifier could be generated
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=beeline&key=&type=">Nhạc Chờ Beeline</a>

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

  • Info Line 1161, Column 96: entity was defined here
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=viettel&key=&type=">Nhạc Chờ Viettel</a>
  • Warning Line 1170, Column 106: reference not terminated by REFC delimiter
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=beeline&key=&type=">Nhạc Chờ Beeline</a>

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

  • Warning Line 1170, Column 106: reference to external entity in attribute value
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=beeline&key=&type=">Nhạc Chờ Beeline</a>

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

  • Error Line 1170, Column 106: reference to entity "type" for which no system identifier could be generated
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=beeline&key=&type=">Nhạc Chờ Beeline</a>

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

  • Info Line 1161, Column 101: entity was defined here
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=viettel&key=&type=">Nhạc Chờ Viettel</a>
  • Warning Line 1172, Column 88: reference not terminated by REFC delimiter
    …/nhacvietplus.com.vn/NhacCho/99/266/0/1?&telco=evn&key=&type=">Nhạc Chờ EVN</a>

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

  • Warning Line 1172, Column 88: reference to external entity in attribute value
    …/nhacvietplus.com.vn/NhacCho/99/266/0/1?&telco=evn&key=&type=">Nhạc Chờ EVN</a>

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

  • Error Line 1172, Column 88: reference to entity "telco" for which no system identifier could be generated
    …/nhacvietplus.com.vn/NhacCho/99/266/0/1?&telco=evn&key=&type=">Nhạc Chờ EVN</a>

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

  • Info Line 1161, Column 82: entity was defined here
    …hacvietplus.com.vn/NhacCho/99/266/0/1?&telco=viettel&key=&type=">Nhạc Chờ Viet…
  • Warning Line 1172, Column 96: reference not terminated by REFC delimiter
    …/nhacvietplus.com.vn/NhacCho/99/266/0/1?&telco=evn&key=&type=">Nhạc Chờ EVN</a>

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

  • Warning Line 1172, Column 96: reference to external entity in attribute value
    …/nhacvietplus.com.vn/NhacCho/99/266/0/1?&telco=evn&key=&type=">Nhạc Chờ EVN</a>

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

  • Error Line 1172, Column 96: reference to entity "key" for which no system identifier could be generated
    …/nhacvietplus.com.vn/NhacCho/99/266/0/1?&telco=evn&key=&type=">Nhạc Chờ EVN</a>

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

  • Info Line 1161, Column 96: entity was defined here
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=viettel&key=&type=">Nhạc Chờ Viettel</a>
  • Warning Line 1172, Column 102: reference not terminated by REFC delimiter
    …/nhacvietplus.com.vn/NhacCho/99/266/0/1?&telco=evn&key=&type=">Nhạc Chờ EVN</a>

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

  • Warning Line 1172, Column 102: reference to external entity in attribute value
    …/nhacvietplus.com.vn/NhacCho/99/266/0/1?&telco=evn&key=&type=">Nhạc Chờ EVN</a>

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

  • Error Line 1172, Column 102: reference to entity "type" for which no system identifier could be generated
    …/nhacvietplus.com.vn/NhacCho/99/266/0/1?&telco=evn&key=&type=">Nhạc Chờ EVN</a>

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

  • Info Line 1161, Column 101: entity was defined here
    …tplus.com.vn/NhacCho/99/266/0/1?&telco=viettel&key=&type=">Nhạc Chờ Viettel</a>
  • Error Line 1264, Column 194: required attribute "alt" not specified
    …ery.adnetwork.vn/247/noscript/zid_1357631180/wid_1292558026/" /></a></noscript>

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

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

Visitor Analysis

Daily Visitor
  • 455 visits

In Page Analysis