vinaphone.com.vn

VINAPHONE, VINAPORTAL, CHACHA, RINGTUNES, nhạc chuông chờ, nhà mạng, viễn thông, VNPT, SMS, MCA, call blocking, missed call alert,... ...

Display Widget for this domain on your website. Click Here
This data was last updated from 17-06-2013 04:51:14  (update).

Overview Info

  • Domain Name
    vinaphone.com.vn
  • Favicon
  • Alexa Rank
    #44182
  • Google Page Rank
    PR 6
  • Ip Address
    203.162.21.217
  • Page Size
    73.2 KB
  • Images
    6 GIF, 9 JPG, 6 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 6 0 0 0 0

Website Meta Analysis



  • Title
    VinaPortal: Home page
  • Meta Keyword
  • Meta Description
    VINAPHONE, VINAPORTAL, CHACHA, RINGTUNES, nhạc chuông chờ, nhà mạng, viễn thông, VNPT, SMS, MCA, call blocking, missed call alert,...

Technical Analysis



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

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

HTML Analysis

  • date: Mon, 17 Jun 2013 16:50:29 GMT
  • pragma: no-cache
  • content-type: text/html; charset=UTF-8
  • expires: Thu, 01 Jan 1970 00:00:00 GMT
  • cache-control: no-cache,no-store,must-revalidate,max-stale=0
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for vinaphone.com.vn

DNS Analysis


DNS servers
hcm-server1.vnn.vn [203.162.4.1]
vdc-hn01.vnn.vn [203.162.0.11]


DNS Records

Answer records
vinaphone.com.vn SOA
server: vdc-hn01.vnn.vn
email: postmaster@vnn.vn
serial: 2013011401
refresh: 900
retry: 900
expire: 604800
minimum ttl: 1800
1800s
vinaphone.com.vn A 203.162.21.217 1800s
vinaphone.com.vn MX
preference: 10
exchange: vnp.vinaphone.com.vn
1800s
vinaphone.com.vn NS  hcm-server1.vnn.vn 1800s
vinaphone.com.vn NS  vdc-hn01.vnn.vn 1800s

Authority records

Additional records
vnp.vinaphone.com.vn A 113.185.0.26 1800s
vdc-hn01.vnn.vn A 203.162.0.11 300s
hcm-server1.vnn.vn A 203.162.4.1 300s

IP 203.162.21.217 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-5]
    % Whois data copyright terms http://www.apnic.net/db/dbcopyright.html

    inetnum: 203.162.16.0 - 203.162.31.255
    netname: VDC-NET
    country: vn
    descr: VietNam Data Communication Company
    admin-c: VIG1-AP
    tech-c: VIG1-AP
    status: ALLOCATED NON-PORTABLE
    changed: hm-changed@vnnic.net.vn 20090325
    mnt-by: MAINT-VN-VNPT
    source: APNIC

    route: 203.162.16.0/20
    descr: VietNam Post and Telecom Corporation (VNPT)
    descr: VNPT-AS-AP
    country: VN
    origin: AS7643
    remarks: mailto:nhkhanh@vdc.com.vn,vangoc@vdc.com.vn,chinn@vdc.com.vn
    notify: hm-changed@vnnic.net.vn
    mnt-by: MAINT-VN-VNPT
    changed: hm-changed@vnnic.net.vn 20100114
    source: APNIC

    role: VDC IPADMIN GROUP
    address: Internet Building, Block II, Thang Long Inter Village
    address: Nguyen Phong Sac str, Cau Giay Dist, Ha Noi
    country: VN
    phone: +84-912-800008
    fax-no: +84-4-9430427
    e-mail: hathm@vdc.com.vn
    remarks: send spam reports to abuse@vdc.com.vn
    remarks: and abuse reports to abuse@vnn.vn
    admin-c: THMH1-AP
    tech-c: THMH1-AP
    nic-hdl: VIG1-AP
    notify: hm-changed@vnnic.net.vn
    mnt-by: MAINT-VN-VNPT
    changed: hm-changed@vnnic.net.vn 20090325
    source: APNIC
    changed: hm-changed@apnic.net 20111114


Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 111 Errors
  • 22 Warnings
Ratio Text/Html
  • 0.5862078161042148
Message Error
  • Error Line 6, Column 1: Missing xmlns attribute for element html. The value should be: http://www.w3.org/1999/xhtml
    <html>

    Many Document Types based on XML need a mandatory xmlns attribute on the root element. For example, the root element for XHTML might look like:
    <html xmlns="http://www.w3.org/1999/xhtml">

  • Error Line 13, Column 121: end tag for "link" omitted, but OMITTAG NO was specified
    …hone.com.vn/style/nivo-slider/nivo-slider.css" type="text/css" media="screen" >

    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 13, Column 1: start tag was here
    <link rel="stylesheet" href="http://vinaphone.com.vn/style/nivo-slider/nivo-sli…
  • Warning Line 128, Column 41: character "&" is the first character of a delimiter but occurred as data
    	  if(!$.browser.msie || ($.browser.msie&&$.browser.version>5)){

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 128, Column 42: character "&" is the first character of a delimiter but occurred as data
    	  if(!$.browser.msie || ($.browser.msie&&$.browser.version>5)){

    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 132, Column 53: document type does not allow element "span" here
    …er('<span class="customStyleSelectBox"><span class="customStyleSelectBoxInner"…

    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 142, Column 27: character "&" is the first character of a delimiter but occurred as data
    // Thanks to Juarez Filho & PaddyMurphy

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 178, Column 35: character "&" is the first character of a delimiter but occurred as data
            directionNav:true, //Next & Prev

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 185, Column 38: character "&" is the first character of a delimiter but occurred as data
            keyboardNav:true, //Use left & right arrows

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 201, Column 35: character "&" is the first character of a delimiter but occurred as data
            directionNav:true, //Next & Prev

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 208, Column 38: character "&" is the first character of a delimiter but occurred as data
            keyboardNav:true, //Use left & right arrows

    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 233, Column 170: document type does not allow element "meta" here
    …, nhà mạng, viễn thông, VNPT, SMS, MCA, call blocking, missed call alert,..."/>

    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 234, Column 73: document type does not allow element "link" here
    <link type="text/css" href="http://vinaphone.com.vn/style/css/ie6.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 235, Column 73: document type does not allow element "link" here
    <link type="text/css" href="http://vinaphone.com.vn/style/css/ie7.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 236, Column 73: document type does not allow element "link" here
    <link type="text/css" href="http://vinaphone.com.vn/style/css/ie8.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 237, Column 73: document type does not allow element "link" here
    <link type="text/css" href="http://vinaphone.com.vn/style/css/ie9.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 238, Column 13: there is no attribute "defer"
    <link defer="defer" type="text/javascript" href="http://vinaphone.com.vn/style/…

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

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

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

  • Error Line 238, Column 94: document type does not allow element "link" here
    …fer" type="text/javascript" href="http://vinaphone.com.vn/style/js/fixie6.js"/>

    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 239, Column 94: document type does not allow element "link" here
    …fer" type="text/javascript" href="http://vinaphone.com.vn/style/js/fixie7.js"/>

    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 240, Column 74: required attribute "type" not specified
    …ipt src='http://ringtunes.vinaphone.com.vn/advert/snowfall.jquery.js'></script>

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

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

  • Error Line 300, Column 62: required attribute "action" not specified
    			<form name="searchForm" method="post" id="cse-search-box" >

    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 126: there is no attribute "autocomplete"
    …"Nhập từ khóa " name="q" autocomplete="on" onKeyPress="return disableEnterKey(…

    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 305, Column 142: there is no attribute "onKeyPress"
    … khóa " name="q" autocomplete="on" onKeyPress="return disableEnterKey(event)"/>

    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 328, Column 46: required attribute "type" not specified
      <script defer="defer" language="JavaScript">

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

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

  • Error Line 349, Column 45: required attribute "type" not specified
     <script defer="defer" language="javascript">

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

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

  • Error Line 389, Column 251: "DOCTYPE" declaration not allowed in instance
    … Vinaphone News -->																	<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1…
  • Error Line 389, Column 438: document type does not allow element "meta" here
    …" content="text/html; charset=utf-8" /><link href="css/style.css" rel="stylesh…

    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 389, Column 500: document type does not allow element "link" here
    …ss" rel="stylesheet" type="text/css" />	  	<div class="right-box">				  		<div…

    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 389, Column 873: required attribute "alt" not specified
    …r:#8A8A8A; border-bottom-style:solid;"></div>								<a class="news-title" hre…

    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 389, Column 879: end tag for "img" omitted, but OMITTAG NO was specified
    …A8A; border-bottom-style:solid;"></div>								<a class="news-title" href="htt…

    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 389, Column 706: start tag was here
    …>								<div class="news-img fltlft"><img src="http://vinaphone.com.vn/mediad…
  • Warning Line 389, Column 2938: cannot generate system identifier for general entity "sms_subject_id"
    …mplate.do?sms_group_id="+smsGroupId+"&sms_subject_id="+smsSubjectId,"tinyWindo…

    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 389, Column 2938: general entity "sms_subject_id" not defined and no default entity
    …mplate.do?sms_group_id="+smsGroupId+"&sms_subject_id="+smsSubjectId,"tinyWindo…

    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 389, Column 2952: reference not terminated by REFC delimiter
    …group_id="+smsGroupId+"&sms_subject_id="+smsSubjectId,"tinyWindow",'resizable=…

    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 389, Column 2952: reference to entity "sms_subject_id" for which no system identifier could be generated
    …group_id="+smsGroupId+"&sms_subject_id="+smsSubjectId,"tinyWindow",'resizable=…

    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 389, Column 2937: entity was defined here
    …emplate.do?sms_group_id="+smsGroupId+"&sms_subject_id="+smsSubjectId,"tinyWind…
  • Error Line 389, Column 3984: end tag for "img" omitted, but OMITTAG NO was specified
    …','Contact')" alt="Sổ địa chỉ">																													</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 389, Column 3786: start tag was here
    …>                                    	<img src="/vnp_files/image/ContactIcon.j…
  • Error Line 389, Column 4228: there is no attribute "onKeyDown"
    …message" rows="5" cols="36" onKeyDown="limitText();" onKeyUp="limitText();"></…

    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 389, Column 4251: there is no attribute "onKeyUp"
    …"36" onKeyDown="limitText();" onKeyUp="limitText();"></textarea>										</di…

    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 389, Column 4556: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …ldText" style= "width:60px"  readonly/>										</div>									</li>									…

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Error Line 389, Column 4942: required attribute "alt" not specified
    …om.vn/anhtutao" width="50" height="30">    										</div>									</li>					…

    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 389, Column 4943: end tag for "img" omitted, but OMITTAG NO was specified
    …m.vn/anhtutao" width="50" height="30">    										</div>									</li>						…

    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 389, Column 4876: start tag was here
    …="fieldText" maxlength="3" value=""/>	<img src="http://vinaphone.com.vn/anhtut…
  • Error Line 389, Column 5012: document type does not allow element "table" here; assuming missing "li" start-tag
    …li>																		<table border="0">										<tr>											<td><input nam…
  • Error Line 389, Column 5079: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …><input name="note" value="FREE" type=radio onclick="updateCountdown();" check…
  • Error Line 389, Column 5315: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …nput name="note" value="HAS_FEE" type=radio onclick="updateCountdown();"/></td…
  • Error Line 389, Column 5523: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …	</table>									<li class="clearfix">										<input class="submit" type="s…

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

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

  • Error Line 389, Column 5662: end tag for "li" omitted, but OMITTAG NO was specified
    …																																		</ul>								</form>							</div>				  	</di…

    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 389, Column 4995: start tag was here
    …</div>									</li>																		<table border="0">										<tr>								…
  • Error Line 389, Column 5941: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …tle-box"><a class="title">Video clip<a></div>							<div class="content-box2">…

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

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

  • Error Line 389, Column 5947: end tag for "a" omitted, but OMITTAG NO was specified
    …x"><a class="title">Video clip<a></div>							<div class="content-box2">						…

    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 389, Column 5939: start tag was here
    …title-box"><a class="title">Video clip<a></div>							<div class="content-box2…
  • Error Line 389, Column 5947: end tag for "a" omitted, but OMITTAG NO was specified
    …x"><a class="title">Video clip<a></div>							<div class="content-box2">						…

    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 389, Column 5912: start tag was here
    …t-box">				  		<div class="title-box"><a class="title">Video clip<a></div>				…
  • Warning Line 389, Column 7043: character "&" is the first character of a delimiter but occurred as data
    …1;      }      if((currentState == 2) && (paused == false))      {        setT…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 389, Column 7044: character "&" is the first character of a delimiter but occurred as data
    …;      }      if((currentState == 2) && (paused == false))      {        setTi…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 389, Column 7227: character "&" is the first character of a delimiter but occurred as data
    …      {        if((pr1 > desiredLoad) && (bufferControl == true))        {    …

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 389, Column 7228: character "&" is the first character of a delimiter but occurred as data
    …     {        if((pr1 > desiredLoad) && (bufferControl == true))        {     …

    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 389, Column 8355: end tag for "img" omitted, but OMITTAG NO was specified
    …o.gif" alt="Cap doi hoan hao 2013"></a><a style="cursor:pointer" href="http://…

    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 389, Column 8255: start tag was here
    …i-hoan-hao-2013" class="nivo-prevNav"><img src="http://vinaphone.com.vn/style/…
  • Error Line 389, Column 8562: end tag for "img" omitted, but OMITTAG NO was specified
    …e/images/km/i1.jpg" alt="iPhone 5"></a><a style="cursor:pointer" href="http://…

    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 389, Column 8486: start tag was here
    …-5-tai-viet-nam" class="nivo-prevNav"><img src="http://vinaphone.com.vn/style/…
  • Error Line 389, Column 8769: end tag for "img" omitted, but OMITTAG NO was specified
    …e/images/km/i2.jpg" alt="iPhone 5"></a><a style="cursor:pointer" href="http://…

    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 389, Column 8693: start tag was here
    …-5-tai-viet-nam" class="nivo-prevNav"><img src="http://vinaphone.com.vn/style/…
  • Error Line 389, Column 8945: end tag for "img" omitted, but OMITTAG NO was specified
    …ages/km/funtalk.gif" alt="Funtalk"></a><!--<a style="cursor:pointer" href="htt…

    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 389, Column 8865: start tag was here
    …ervices/funtalk" class="nivo-prevNav"><img src="http://vinaphone.com.vn/style/…
  • Error Line 389, Column 9343: end tag for "img" omitted, but OMITTAG NO was specified
    …mages/zoota/zoota.gif" alt="Zoota"></a><a style="cursor:pointer" href="http://…

    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 389, Column 9264: start tag was here
    …-mang-vinaphone" class="nivo-prevNav"><img src="http://vinaphone.com.vn/style/…
  • Error Line 389, Column 9523: end tag for "img" omitted, but OMITTAG NO was specified
    …/donggopytuong1.jpg" alt="Y tuong"></a><a style="cursor:pointer" href="http://…

    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 389, Column 9436: start tag was here
    …n/idea/homepage" class="nivo-prevNav"><img src="http://vinaphone.com.vn/style/…
  • Error Line 389, Column 9703: end tag for "img" omitted, but OMITTAG NO was specified
    …/donggopytuong2.jpg" alt="Y tuong"></a><!--<a style="cursor:pointer" href="htt…

    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 389, Column 9616: start tag was here
    …n/idea/homepage" class="nivo-prevNav"><img src="http://vinaphone.com.vn/style/…
  • Error Line 389, Column 9964: invalid comment declaration: found name start character outside comment but inside comment declaration
    …com.vn/news/23440/thoa-suc-choi-game--khung-" class="nivo-prevNav"><img src="h…
  • Info Line 389, Column 9873: comment declaration started here
    …/noel2012.gif" alt="Noel 2012"></a>--><!--<a style="cursor:pointer" href="http…
  • Error Line 389, Column 10067: end tag for element "a" which is not open
    …yle/images/km/gbox.gif" alt="GBOX"></a>--><!--<a style="cursor:pointer" href="…

    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 389, Column 10067: end tag for "img" omitted, but OMITTAG NO was specified
    …yle/images/km/gbox.gif" alt="GBOX"></a>--><!--<a style="cursor:pointer" href="…

    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 389, Column 9993: start tag was here
    …oi-game--khung-" class="nivo-prevNav"><img src="http://vinaphone.com.vn/style/…
  • Error Line 389, Column 10719: invalid comment declaration: found name start character outside comment but inside comment declaration
    ….vn/news/22460/nhan-nhieu-uu-dai-voi--thoa-suc-alo--cua-vinaphone" class="nivo…
  • Info Line 389, Column 10625: comment declaration started here
    …ages/km/ezcom.gif" alt="ezCom"></a>--><!--<a style="cursor:pointer" href="http…
  • Error Line 389, Column 10864: end tag for element "a" which is not open
    …thoasucalo.gif" alt="Thoa suc alo"></a>--><!--<a style="cursor:pointer" href="…

    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 389, Column 10864: end tag for "img" omitted, but OMITTAG NO was specified
    …thoasucalo.gif" alt="Thoa suc alo"></a>--><!--<a style="cursor:pointer" href="…

    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 389, Column 10769: start tag was here
    …--cua-vinaphone" class="nivo-prevNav"><img src="http://vinaphone.com.vn/style/…
  • Error Line 389, Column 11612: invalid comment declaration: found name start character outside comment but inside comment declaration
    …://vinaphone.com.vn/news/23520/-rinh--iphone-4s-nho-choi-game" class="nivo-pre…
  • Info Line 389, Column 11534: comment declaration started here
    …g29102012.gif" alt="Ngay vang"></a>--><!--<a style="cursor:pointer" href="http…
  • Error Line 389, Column 11764: end tag for element "a" which is not open
    …nhca.gif" alt="Linh trieu binh ca"></a>--><!--<a style="cursor:pointer" href="…

    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 389, Column 11764: end tag for "img" omitted, but OMITTAG NO was specified
    …nhca.gif" alt="Linh trieu binh ca"></a>--><!--<a style="cursor:pointer" href="…

    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 389, Column 11658: start tag was here
    …s-nho-choi-game" class="nivo-prevNav"><img src="http://vinaphone.com.vn/style/…
  • Error Line 389, Column 13529: invalid comment declaration: found name start character outside comment but inside comment declaration
    …/vinaphone.com.vn/news/23240/de-dang--am--50-trieu-dong-khi-kinh-doanh-cung-vi…
  • Info Line 389, Column 13449: comment declaration started here
    …g29082012.gif" alt="Ngay vang"></a>--><!--<a style="cursor:pointer" href="http…
  • Error Line 389, Column 13697: end tag for element "a" which is not open
    …lblocking.gif" alt="Call Blocking"></a>--><!--<a style="cursor:pointer" href="…

    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 389, Column 13697: end tag for "img" omitted, but OMITTAG NO was specified
    …lblocking.gif" alt="Call Blocking"></a>--><!--<a style="cursor:pointer" href="…

    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 389, Column 13599: start tag was here
    …-cung-vinaphone" class="nivo-prevNav"><img src="http://vinaphone.com.vn/style/…
  • Error Line 389, Column 13779: invalid comment declaration: found name start character outside comment but inside comment declaration
    …://vinaphone.com.vn/news/23260/trung--de-khung--khi-dung-tien-ich-sim-vinaphon…
  • Info Line 389, Column 13701: comment declaration started here
    …cking.gif" alt="Call Blocking"></a>--><!--<a style="cursor:pointer" href="http…
  • Error Line 389, Column 13922: end tag for element "a" which is not open
    …mages/khuyenmai/iod.gif" alt="IOD"></a>--><!--<a style="cursor:pointer" href="…

    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 389, Column 13922: end tag for "img" omitted, but OMITTAG NO was specified
    …mages/khuyenmai/iod.gif" alt="IOD"></a>--><!--<a style="cursor:pointer" href="…

    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 389, Column 13843: start tag was here
    …h-sim-vinaphone" class="nivo-prevNav"><img src="http://vinaphone.com.vn/style/…
  • Error Line 389, Column 14930: invalid comment declaration: found name start character outside comment but inside comment declaration
    …20/vinaphone-trien-khai-chuong-trinh--sms-trieu-niem-vui-" class="nivo-prevNav…
  • Info Line 389, Column 14824: comment declaration started here
    …g12072012.gif" alt="Ngay vang"></a>--><!--<a style="cursor:pointer" href="http…
  • Error Line 389, Column 15069: end tag for element "a" which is not open
    …mvui.gif" alt="SMS Trieu niem vui"></a>--><!--<a style="cursor:pointer" href="…

    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 389, Column 15069: end tag for "img" omitted, but OMITTAG NO was specified
    …mvui.gif" alt="SMS Trieu niem vui"></a>--><!--<a style="cursor:pointer" href="…

    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 389, Column 14972: start tag was here
    …trieu-niem-vui-" class="nivo-prevNav"><img src="http://vinaphone.com.vn/style/…
  • Error Line 389, Column 18527: invalid comment declaration: found name start character outside comment but inside comment declaration
    …m.vn/news/21900/khuyen-mai-mobile-tv--dang-ky-goi-tivi-tang-goi-phim-hot" clas…
  • Info Line 389, Column 18434: comment declaration started here
    …images/mnews2.gif" alt="mNews"></a>--><!--<a style="cursor:pointer" href="http…
  • Error Line 389, Column 18672: end tag for element "a" which is not open
    …iletv-t022012.gif" alt="Mobile TV"></a>--><!--<a style="cursor:pointer" href="…

    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 389, Column 18672: end tag for "img" omitted, but OMITTAG NO was specified
    …iletv-t022012.gif" alt="Mobile TV"></a>--><!--<a style="cursor:pointer" href="…

    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 389, Column 18584: start tag was here
    …ng-goi-phim-hot" class="nivo-prevNav"><img src="http://vinaphone.com.vn/style/…
  • Error Line 389, Column 21606: invalid comment declaration: found name start character outside comment but inside comment declaration
    …1200/quay-thuong-tuan-3-chuong-trinh--trieu-phu-sms-" class="nivo-prevNav"><im…
  • Info Line 389, Column 21502: comment declaration started here
    …292-3.jpg" alt="Tong dai 9292"></a>--><!--<a style="cursor:pointer" href="http…
  • Error Line 389, Column 21730: end tag for element "a" which is not open
    …ieuphusms.gif" alt="trieu phu sms"></a>--><!--<a style="cursor:pointer" href="…

    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 389, Column 21730: end tag for "img" omitted, but OMITTAG NO was specified
    …ieuphusms.gif" alt="trieu phu sms"></a>--><!--<a style="cursor:pointer" href="…

    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 389, Column 21643: start tag was here
    …-trieu-phu-sms-" class="nivo-prevNav"><img src="http://vinaphone.com.vn/style/…
  • Error Line 389, Column 22248: invalid comment declaration: found name start character outside comment but inside comment declaration
    …80/-nap-nhanh-trung-lon-thuong-nhieu--voi-dich-vu-smartlink-topup" class="nivo…
  • Info Line 389, Column 22142: comment declaration started here
    …="DIch vu chia se anh Vishare"></a>--><!--<a style="cursor:pointer" href="http…
  • Error Line 389, Column 22383: end tag for element "a" which is not open
    …smartlink.gif" alt="trieu phu sms"></a>--><!--<a target="_blank" style="cursor…

    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 389, Column 22383: end tag for "img" omitted, but OMITTAG NO was specified
    …smartlink.gif" alt="trieu phu sms"></a>--><!--<a target="_blank" style="cursor…

    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 389, Column 22298: start tag was here
    …smartlink-topup" class="nivo-prevNav"><img src="http://vinaphone.com.vn/style/…
  • Error Line 389, Column 23891: invalid comment declaration: found name start character outside comment but inside comment declaration
    …naphone.com.vn/news/20920/khuyen-mai--tai-ringtunes---nhan-vang-lien-tay" clas…
  • Info Line 389, Column 23792: comment declaration started here
    …tyle/images/idd.gif" alt="IDD"></a>--><!--<a target="_blank" style="cursor:poi…
  • Error Line 389, Column 24034: end tag for element "a" which is not open
    …ingtunes-gold.gif" alt="ringtunes"></a>--><!--<a target="_blank" style="cursor…

    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 389, Column 24034: end tag for "img" omitted, but OMITTAG NO was specified
    …ingtunes-gold.gif" alt="ringtunes"></a>--><!--<a target="_blank" style="cursor…

    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 389, Column 23948: start tag was here
    …n-vang-lien-tay" class="nivo-prevNav"><img src="http://vinaphone.com.vn/style/…
  • Error Line 389, Column 24394: invalid comment declaration: found name character outside comment but inside comment declaration
    …e.com.vn/news/20240/TRAI-NGHIEM-MOMO---TIEN-VO-DAY-TUI" class="nivo-prevNav"><…
  • Info Line 389, Column 24289: comment declaration started here
    …g08112011.gif" alt="Ngay Vang"></a>--><!--<a target="_blank" style="cursor:poi…
  • Error Line 389, Column 24511: end tag for element "a" which is not open
    …images/Momo-082011.gif" alt="MoMo"></a>--><!--<a target="_blank" style="cursor…

    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 389, Column 24511: end tag for "img" omitted, but OMITTAG NO was specified
    …images/Momo-082011.gif" alt="MoMo"></a>--><!--<a target="_blank" style="cursor…

    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 389, Column 24433: start tag was here
    …TIEN-VO-DAY-TUI" class="nivo-prevNav"><img src="http://vinaphone.com.vn/style/…
  • Error Line 389, Column 25866: there is no attribute "WIDTH"
    …news">									        <MARQUEE WIDTH=490 align="center" direction="left" scro…

    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 389, Column 25866: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …news">									        <MARQUEE WIDTH=490 align="center" direction="left" scro…
  • Error Line 389, Column 25876: there is no attribute "align"
    …					        <MARQUEE WIDTH=490 align="center" direction="left" scrollamount="…

    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 389, Column 25895: there is no attribute "direction"
    …EE WIDTH=490 align="center" direction="left" scrollamount="2">												 <!D…

    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 389, Column 25915: there is no attribute "scrollamount"
    …center" direction="left" scrollamount="2">												 <!DOCTYPE html PUBLIC "…

    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 389, Column 25918: element "MARQUEE" undefined
    …ter" direction="left" scrollamount="2">												 <!DOCTYPE html PUBLIC "-//…

    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 389, Column 25934: "DOCTYPE" declaration not allowed in instance
    …left" scrollamount="2">												 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1…
  • Error Line 389, Column 32517: required attribute "alt" not specified
    …s/ezCom.jpg" width="124" height="79" /></a>								</td>								<td>								  …

    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 389, Column 33532: required attribute "alt" not specified
    …ges/alo.png" width="123" height="79" /></a>								</td>								<td>								  …

    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 389, Column 34410: required attribute "alt" not specified
    …ne-ipad.jpg" width="124" height="79" /></a>								</td>								<td>								  …

    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 389, Column 35449: required attribute "alt" not specified
    …ges/iod.jpg" width="124" height="79" /></a>								</td>								<td>								  …

    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 389, Column 36557: required attribute "alt" not specified
    …/chonso.jpg" width="124" height="79" /></a>								</td>								<td>								  …

    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 389, Column 37583: required attribute "alt" not specified
    …ratruoc.png" width="124" height="79" /></a>								</td>								<td>								  …

    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 389, Column 38795: required attribute "alt" not specified
    …-traSau.png" width="124" height="79" /></a>								</td>								<td>								  …

    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 389, Column 40128: required attribute "alt" not specified
    …uockhac.png" width="124" height="79" /></a>								</td>								<td>								  …

    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 389, Column 47404: NET-enabling start-tag not immediately followed by null end-tag
    ….com.vn/style/images/idea-312x90.gif"/ width="311" style="margin-right:11px;">…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 389, Column 47404: end tag for "img" omitted, but OMITTAG NO was specified
    ….com.vn/style/images/idea-312x90.gif"/ width="311" style="margin-right:11px;">…

    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 389, Column 47329: start tag was here
    …ttp://vinaphone.com.vn/ytuongsangtao"><img alt="IDEA" src="http://vinaphone.co…
  • Warning Line 444, Column 37: character "&" is the first character of a delimiter but occurred as data
    									<h2><a href="#">Khách hàng & đối tác </a></h2> 

    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 461, Column 49: there is no attribute "valign"
    <div class="social-bookmarking clearfix" valign="top">

    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 465, Column 65: required attribute "type" not specified
    …ect.facebook.net/en_US/all.js#xfbml=1"></script><fb:like href="http://www.face…

    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 465, Column 89: there is no attribute "href"
    …ll.js#xfbml=1"></script><fb:like href="http://www.facebook.com/pages/VinaPhone…

    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 465, Column 158: there is no attribute "show_faces"
    …es/VinaPhone/109753675772847" show_faces="false" width="450" font=""></fb:like>

    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 465, Column 172: there is no attribute "width"
    …es/VinaPhone/109753675772847" show_faces="false" width="450" font=""></fb:like>

    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 465, Column 183: there is no attribute "font"
    …es/VinaPhone/109753675772847" show_faces="false" width="450" font=""></fb:like>

    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 465, Column 185: element "fb:like" undefined
    …es/VinaPhone/109753675772847" show_faces="false" width="450" font=""></fb:like>

    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 485, Column 106: end tag for "br" omitted, but OMITTAG NO was specified
    …hát triển bởi <strong> VinaPhone</strong> 2005-2013. Bản quyền đã đăng ký. <br>

    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 485, Column 102: start tag was here
    …hát triển bởi <strong> VinaPhone</strong> 2005-2013. Bản quyền đã đăng ký. <br>
  • Warning Line 495, Column 77: cannot generate system identifier for general entity "dn"
    …n.com/splash?form_file=fdf/splash.fdf&dn=vinaphone.com.vn&lang=en" target="_bl…

    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 495, Column 77: general entity "dn" not defined and no default entity
    …n.com/splash?form_file=fdf/splash.fdf&dn=vinaphone.com.vn&lang=en" target="_bl…

    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 495, Column 79: reference not terminated by REFC delimiter
    …com/splash?form_file=fdf/splash.fdf&dn=vinaphone.com.vn&lang=en" target="_blan…

    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 495, Column 79: reference to external entity in attribute value
    …com/splash?form_file=fdf/splash.fdf&dn=vinaphone.com.vn&lang=en" target="_blan…

    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 495, Column 79: reference to entity "dn" for which no system identifier could be generated
    …com/splash?form_file=fdf/splash.fdf&dn=vinaphone.com.vn&lang=en" target="_blan…

    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 495, Column 76: entity was defined here
    …gn.com/splash?form_file=fdf/splash.fdf&dn=vinaphone.com.vn&lang=en" target="_b…
  • Warning Line 495, Column 101: reference not terminated by REFC delimiter
    …df/splash.fdf&dn=vinaphone.com.vn&lang=en" target="_blank"><img width="100" sr…

    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 495, Column 190: required attribute "alt" not specified
    …<img width="100" src="http://vinaphone.com.vn/style/images/ver1.png"></img></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>.

Visitor Analysis

Daily Visitor
  • 2.800 visits
Daily Visitor

In Page Analysis