xem phim, xem phim tâm lý tình cảm có nội dung hay nhất mọi thời đại. zingphim.net cập nhật phim cấp 3 và các bộ phim hành động mỹ, Phim bom tấn mới ...

zingphim.net
  • Domain Name
    zingphim.net
  • Favicon
  • Google Page Rank
    0
  • Alexa Rank
    #286405
  • Page Size
    113.7 KB
  • Ip Address
    123.30.210.91
  • Heading
    H1: 1, H2: 2, H3: 8, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 79 JPG, 7 PNG

Website Meta Analysis

  • Title
    xem phim cấp 3, xem phim tâm lý tình cảm có nội dung hay nhất mọi thời đại
  • Meta Keyword
    xem phim, phim, xem phim cap 3, phim tam ly tinh cam, phim 18+, phim han quoc, phim thai lan, phim my
  • Meta Description
    xem phim, xem phim tâm lý tình cảm có nội dung hay nhất mọi thời đại. zingphim.net cập nhật phim cấp 3 và các bộ phim hành động mỹ, Phim bom tấn mới nhất, chúc các bạn xem phim vui vẻ

Technical Analysis

  • Webserver
    Apache/2.2.23 (CentOS)
  • Ip Address
    123.30.210.91
  • Domain Age
    1 Years, 0 Months, 7 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from zingphim.net.

HTML Analysis

  • date: Thu, 12 Sep 2013 17:17:36 GMT
  • server: Apache/2.2.23 (CentOS)
  • x-powered-by: PHP/5.2.17
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • connection: close
  • content-type: text/html; charset=UTF-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for zingphim.net

DNS Analysis


DNS servers
ns2.matbao.com [210.245.124.171]
ns1.matbao.com [203.162.163.44]


DNS Records

Answer records
zingphim.net A 123.30.210.91 3600s
zingphim.net NS  ns1.matbao.com 3600s
zingphim.net NS  ns2.matbao.com 3600s
zingphim.net SOA
server: ns1.matbao.com
email: [email protected]
serial: 2013022008
refresh: 7200
retry: 1800
expire: 1209600
minimum ttl: 3600
3600s
zingphim.net MX
preference: 10
exchange: mail.zingphim.net
3600s
zingphim.net TXT v=spf1 mx ~all 3600s

Authority records

Additional records
mail.zingphim.net A 112.78.2.247 3600s

IP 123.30.210.91 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 97 Errors
  • 104 Warnings
Ratio Text/Html
  • 0.6587709055942855
Message Error
  • Error Line 12, Column 35: end tag for "meta" omitted, but OMITTAG NO was specified
    	<meta name="abstract" content="">  	

    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 12, Column 2: start tag was here
    	<meta name="abstract" content="">  	
  • Error Line 14, Column 41: end tag for "meta" omitted, but OMITTAG NO was specified
    	<meta name="classification" content="">

    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 14, Column 2: start tag was here
    	<meta name="classification" content="">
  • Error Line 15, Column 347: end tag for "meta" omitted, but OMITTAG NO was specified
    …w.yahoo.com, www.alltheweb.com, www.msn.com, www.netscape.com, www.nomade.com">

    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 15, Column 2: start tag was here
    	<meta name="Search Engines" content="www.altaVista.com, www.aol.com, www.infos…
  • Error Line 20, Column 36: end tag for "meta" omitted, but OMITTAG NO was specified
    	<meta name="rating" content="All">	

    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 20, Column 2: start tag was here
    	<meta name="rating" content="All">	
  • Error Line 21, Column 147: end tag for "link" omitted, but OMITTAG NO was specified
    …him*phim HD, Phim tam ly, Xem phim online" href="http://zingphim.net/rss.php">	

    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 21, Column 2: start tag was here
    	<link rel="alternate" type="application/rss+xml" title="Phim, Xem Phim*phim HD…
  • Error Line 24, Column 50: end tag for element "base" which is not open
            <base href="http://zingphim.net/"/></base>

    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 30, Column 77: end tag for "link" omitted, but OMITTAG NO was specified
    <link href="skin/thienduongphim/style.css" type="text/css" rel="stylesheet">

    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 30, Column 1: start tag was here
    <link href="skin/thienduongphim/style.css" type="text/css" rel="stylesheet">
  • Error Line 35, Column 54: required attribute "type" not specified
    <script src="http://adbroker.zing.vn/res1/crystal.js"></script>

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

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

  • Error Line 38, Column 54: required attribute "type" not specified
    <script src="http://adbroker.zing.vn/res1/crystal.js"></script>

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

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

  • Error Line 47, Column 87: required attribute "action" not specified
    …="search_form" name="search" onsubmit="do_search();return false" method="post">

    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 48, Column 76: there is no attribute "placeholder"
    …" name="keyword" class="keyword" id="keyword" placeholder="Từ Khóa Cần Tìm...">

    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 48, Column 97: end tag for "input" omitted, but OMITTAG NO was specified
    …" name="keyword" class="keyword" id="keyword" placeholder="Từ Khóa Cần Tìm...">

    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 48, Column 1: start tag was here
    <input type="text" name="keyword" class="keyword" id="keyword" placeholder="Từ …
  • Error Line 49, Column 70: end tag for "input" omitted, but OMITTAG NO was specified
    <input type="hidden" name="search_type" id="search_type" value="all"> 

    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 49, Column 1: start tag was here
    <input type="hidden" name="search_type" id="search_type" value="all"> 
  • Error Line 119, Column 7: invalid comment declaration: found name start character outside comment but inside comment declaration
    <!----ads-990x100---------------------------->
  • Info Line 119, Column 1: comment declaration started here
    <!----ads-990x100---------------------------->
  • Error Line 121, Column 137: end tag for "img" omitted, but OMITTAG NO was specified
    …ads-990-100.jpg" alt="high optical" border="0px" height="100px;" width="990px">

    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 121, Column 1: start tag was here
    <img src="http://zingphim.net/skin/thienduongphim/images/ads-990-100.jpg" alt="…
  • Error Line 262, Column 212: end tag for "param" omitted, but OMITTAG NO was specified
    …pplication/x-shockwave-flash"><param value="transparent" name="wmode"></object>

    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 262, Column 164: start tag was here
    … type="application/x-shockwave-flash"><param value="transparent" name="wmode">…
  • Error Line 267, Column 37: there is no attribute "data-target"
    						<div class="tabs" data-target="#phim-bo-hay">

    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 268, Column 42: there is no attribute "data-name"
    							<div class="tab active" data-name="phim-bo-moi">

    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 387, Column 24: there is no attribute "data-name"
    							<span data-name="toan-bo" class="btn active">Toàn bộ</span>

    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 37: there is no attribute "data-name"
    						<h3 class="type"><a data-name="phim-le" class="btn" href="danh-sach/phim-…

    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 562, Column 16: there is no attribute "data-liked"
    <li data-liked="31" data-views="390">

    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 562, Column 32: there is no attribute "data-views"
    <li data-liked="31" data-views="390">

    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 830, Column 142: end tag for "img" omitted, but OMITTAG NO was specified
    …ong-vu-cap-7-civil-servant-level-7-2013.jpg" alt="Điệp Viên Công Vụ Cấp 7"></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 830, Column 1: start tag was here
    <img src="http://phim14.info/data/images/film/thumb/diep-vien-cong-vu-cap-7-civ…
  • Error Line 837, Column 149: end tag for "img" omitted, but OMITTAG NO was specified
    …459_53706964.huongngoclan.jpg?rand=0.521550418041026" alt="Huơng Ngọc Lan"></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 837, Column 1: start tag was here
    <img src="http://nv4.upanh.com/b6.s35.d4/0ab3f97e113fa63cc9843fe834b99459_53706…
  • Error Line 844, Column 165: end tag for "img" omitted, but OMITTAG NO was specified
    …00/Poster-Tieu-ngao-giang-ho-2012.jpg" alt="Tân Tiếu Ngạo Giang Hồ - 2012"></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 844, Column 1: start tag was here
    <img src="http://2.bp.blogspot.com/-rlVlLjfIlmI/T-ckWndvT3I/AAAAAAAAFRk/SGUVD7I…
  • Error Line 851, Column 129: end tag for "img" omitted, but OMITTAG NO was specified
    …l/2013/02/14/12/40/1360820417155754_574_574.jpg" alt="Gió Mùa Đông Năm Ấy"></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 851, Column 1: start tag was here
    <img src="http://d.f11.photo.zdn.vn/upload/original/2013/02/14/12/40/1360820417…
  • Error Line 858, Column 170: end tag for "img" omitted, but OMITTAG NO was specified
    …ien-tai-quang-cao-lee-tae-baek.jpg" alt="Thiên Tài Quảng Cáo Lee Tae Baek"></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 858, Column 1: start tag was here
    <img src="http://2.bp.blogspot.com/-4spiLVYzGx8/URzxegJagQI/AAAAAAAAMys/JrdzPyM…
  • Error Line 865, Column 144: end tag for "img" omitted, but OMITTAG NO was specified
    …-da-todaytv-vu-dieu-hoang-da-marimar-2007.jpg" alt="Vũ Điệu Hoang Dã 2013"></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 865, Column 1: start tag was here
    <img src="http://phim14.info/data/images/film/thumb/vu-dieu-hoang-da-todaytv-vu…
  • Error Line 872, Column 106: end tag for "img" omitted, but OMITTAG NO was specified
    …geshack.us/img823/4421/thitranbansheeposter201.jpg" alt="Thị Trấn Banshee"></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 872, Column 1: start tag was here
    <img src="http://img823.imageshack.us/img823/4421/thitranbansheeposter201.jpg" …
  • Error Line 879, Column 148: end tag for "img" omitted, but OMITTAG NO was specified
    …bw/k3YpxlrHw5w/s1600/xemphimso-ntphanlehue.jpg" alt="Nữ Tướng Phàn Lê Huê"></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 879, Column 1: start tag was here
    <img src="http://2.bp.blogspot.com/-WyAc2_kIdLA/USXsYlV1QNI/AAAAAAAADbw/k3Ypxlr…
  • Error Line 886, Column 246: end tag for "img" omitted, but OMITTAG NO was specified
    …inh-thu-mat-trai-cua-tinh-yeu.jpg" alt="Lửa Hận Tình Thù - Todaytv - 2013"></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 886, Column 1: start tag was here
    <img src="http://afamily1.vcmedia.vn/k:thumb_w/600/D7prXinbUB7s5ppWxBGqtwKrIZ1z…
  • Error Line 893, Column 81: end tag for "img" omitted, but OMITTAG NO was specified
    …mg src="http://imageshack.us/a/img252/3416/huongbuoi.jpg" alt="Huơng Bưởi"></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 893, Column 1: start tag was here
    <img src="http://imageshack.us/a/img252/3416/huongbuoi.jpg" alt="Huơng Bưởi"></…
  • Error Line 900, Column 127: end tag for "img" omitted, but OMITTAG NO was specified
    …5/KBS-Drama-Special-Their-Perfect-Day_8882_poster.jpg" alt="Ngày Hoàn Hảo"></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 900, Column 1: start tag was here
    <img src="http://static.dramastyle.com/images/1/5/KBS-Drama-Special-Their-Perfe…
  • Error Line 907, Column 175: end tag for "img" omitted, but OMITTAG NO was specified
    …c-Song-3-The-Walking-Dead-Season-3-Poster_PhimSV.Com.jpg" alt="Xác Sống 3"></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 907, Column 1: start tag was here
    <img src="http://1.bp.blogspot.com/-Yd68RH3d38k/UHzlcdFpLEI/AAAAAAAALF0/25kNaPZ…
  • Error Line 914, Column 153: end tag for "img" omitted, but OMITTAG NO was specified
    …53641705.nanglienthanh.jpg?rand=0.40124824998549236" alt="Nàng Liên Thanh"></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 914, Column 1: start tag was here
    <img src="http://nv5.upanh.com/b4.s32.d1/ff1641a30460aefe09e33120327e6ece_53641…
  • Error Line 921, Column 156: end tag for "img" omitted, but OMITTAG NO was specified
    …cZY6vU/s430/xemphimon_nhung-doa-ngoc-lan.jpg" alt="Những Đóa Hoa Ngọc Lan"></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 921, Column 1: start tag was here
    <img src="http://2.bp.blogspot.com/-Svc9ChiE48o/US3C-sQSTrI/AAAAAAAAMZU/NlfCLcZ…
  • Error Line 928, Column 181: end tag for "img" omitted, but OMITTAG NO was specified
    …ster-phim-Cong-thoi-gian-Continuum-Season-1-2012.jpg" alt="Cổng Thời Gian"></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 928, Column 1: start tag was here
    <img src="http://2.bp.blogspot.com/-V5_Jviydfpg/UDaJVkXe55I/AAAAAAAAIts/ouxh6fq…
  • Error Line 935, Column 141: end tag for "img" omitted, but OMITTAG NO was specified
    …AAAAAACAQ/4YCQuJwn6ds/s1600/tro-dua-cua-so-phan.jpg" alt="Trò Đùa Số Phận"></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 935, Column 1: start tag was here
    <img src="http://3.bp.blogspot.com/-0J5614i7SLk/UOevTvKcXAI/AAAAAAAACAQ/4YCQuJw…
  • Error Line 942, Column 148: end tag for "img" omitted, but OMITTAG NO was specified
    …73d03a59edd96a_52545995.phimcohangxomracroi.jpg" alt="Cô Hàng Xóm Rắc Rối"></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 942, Column 1: start tag was here
    <img src="http://heyphim.com/images/film/xemphimso-4507e1643f1fce3fdc73d03a59ed…
  • Error Line 949, Column 139: end tag for "img" omitted, but OMITTAG NO was specified
    …AAAAAAAAC0g/TzcmiyLLSBc/s1600/Nikita-season-3.jpeg" alt="Sát Thủ Nikita 3"></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 949, Column 1: start tag was here
    <img src="http://4.bp.blogspot.com/-ux-yIqZgDzQ/UIPwEpibDGI/AAAAAAAAC0g/TzcmiyL…
  • Error Line 956, Column 93: end tag for "img" omitted, but OMITTAG NO was specified
    …://phimf.com/images/film/Boys-Over-Flowers-poster.jpg" alt="Vườn Sao Băng"></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 956, Column 1: start tag was here
    <img src="http://phimf.com/images/film/Boys-Over-Flowers-poster.jpg" alt="Vườn …
  • Error Line 963, Column 123: end tag for "img" omitted, but OMITTAG NO was specified
    …_editor/image/vietnam/chiecguongchiadoi02.jpg" alt="Chiếc Giường Chia Đôi"></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 963, Column 1: start tag was here
    <img src="http://www.todaytv.vn/upload/store_editor/image/vietnam/chiecguongchi…
  • Error Line 988, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 988, Column 1: start tag was here
    <br>
  • Error Line 989, Column 18: invalid comment declaration: found name start character outside comment but inside comment declaration
    <!--ads 300x200--lâm----------------->
  • Info Line 989, Column 1: comment declaration started here
    <!--ads 300x200--lâm----------------->
  • Error Line 990, Column 159: end tag for "img" omitted, but OMITTAG NO was specified
    …lt="ads" src="http://zingphim.net/skin/thienduongphim/ads/300x200-lam.jpg"></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 75: start tag was here
    …x.php" target="_blank" rel="nofollow"><img alt="ads" src="http://zingphim.net/…
  • Warning Line 992, Column 16: multiple comments in comment declaration
    <!--End lâm--------------------------------->
  • Warning Line 992, Column 20: multiple comments in comment declaration
    <!--End lâm--------------------------------->
  • Warning Line 992, Column 24: multiple comments in comment declaration
    <!--End lâm--------------------------------->
  • Warning Line 992, Column 28: multiple comments in comment declaration
    <!--End lâm--------------------------------->
  • Warning Line 992, Column 32: multiple comments in comment declaration
    <!--End lâm--------------------------------->
  • Warning Line 992, Column 36: multiple comments in comment declaration
    <!--End lâm--------------------------------->
  • Warning Line 992, Column 40: multiple comments in comment declaration
    <!--End lâm--------------------------------->
  • Warning Line 993, Column 3: multiple comments in comment declaration
    <!--ads 300x200
  • Error Line 993, Column 5: invalid comment declaration: found name start character outside comment but inside comment declaration
    <!--ads 300x200
  • Info Line 992, Column 1: comment declaration started here
    <!--End lâm--------------------------------->
  • Error Line 995, Column 137: end tag for "img" omitted, but OMITTAG NO was specified
    …ads-300x200.jpg" alt="high optical" border="0px" height="203px;" width="300px">

    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 995, Column 1: start tag was here
    <img src="http://zingphim.net/skin/thienduongphim/images/ads-300x200.jpg" alt="…
  • Warning Line 1018, Column 20: multiple comments in comment declaration
    <!--End vatgia ------------->
  • Warning Line 1018, Column 24: multiple comments in comment declaration
    <!--End vatgia ------------->
  • Warning Line 1019, Column 3: multiple comments in comment declaration
    <!-- ads end 20h 07/01/2013 -->
  • Warning Line 1019, Column 5: S separator in comment declaration
    <!-- ads end 20h 07/01/2013 -->

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Error Line 1019, Column 6: invalid comment declaration: found name start character outside comment but inside comment declaration
    <!-- ads end 20h 07/01/2013 -->
  • Info Line 1018, Column 1: comment declaration started here
    <!--End vatgia ------------->
  • Error Line 1023, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>--------------------------------------------------<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 1023, Column 1: start tag was here
    <br>--------------------------------------------------<br>
  • Error Line 1023, Column 59: end tag for "br" omitted, but OMITTAG NO was specified
    <br>--------------------------------------------------<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 1023, Column 55: start tag was here
    <br>--------------------------------------------------<br>
  • Warning Line 1091, Column 122: character "&" is the first character of a delimiter but occurred as data
    … title="Sấm Chớp Và Tốc Độ 2 -  Flash & Dash 2 ...">Sấm Chớp Và Tốc Độ 2</a></…

    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 1155, Column 228: reference not terminated by REFC delimiter
    …tml" title="Wallace and Gromit in &#39A Matter of Loaf and Death&#39 -  A Matt…

    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 1155, Column 258: reference not terminated by REFC delimiter
    … in &#39A Matter of Loaf and Death&#39 -  A Matter of Loaf and Death ...">Wall…

    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 1155, Column 320: reference not terminated by REFC delimiter
    … Death ...">Wallace and Gromit in &#39A Matter of Loaf and Death&#39</a></div>…

    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 1155, Column 350: reference not terminated by REFC delimiter
    … in &#39A Matter of Loaf and Death&#39</a></div><div class="views">Lượt Xem 87…

    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 1205, Column 71: cannot generate system identifier for general entity "callback"
    …er.zing.vn/lview?loc=_adb_22_10002985&callback=crystal2.addStaticSlot"></scrip…

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

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

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

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

  • Error Line 1205, Column 71: general entity "callback" not defined and no default entity
    …er.zing.vn/lview?loc=_adb_22_10002985&callback=crystal2.addStaticSlot"></scrip…

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

  • Warning Line 1205, Column 79: reference not terminated by REFC delimiter
    …r.zing.vn/lview?loc=_adb_22_10002985&callback=crystal2.addStaticSlot"></script>

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

  • Warning Line 1205, Column 79: reference to external entity in attribute value
    …r.zing.vn/lview?loc=_adb_22_10002985&callback=crystal2.addStaticSlot"></script>

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

  • Error Line 1205, Column 79: reference to entity "callback" for which no system identifier could be generated
    …r.zing.vn/lview?loc=_adb_22_10002985&callback=crystal2.addStaticSlot"></script>

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

  • Info Line 1205, Column 70: entity was defined here
    …ker.zing.vn/lview?loc=_adb_22_10002985&callback=crystal2.addStaticSlot"></scri…
  • Error Line 1205, Column 103: required attribute "type" not specified
    …r.zing.vn/lview?loc=_adb_22_10002985&callback=crystal2.addStaticSlot"></script>

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

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

  • Warning Line 1209, Column 79: reference not terminated by REFC delimiter
    …r.zing.vn/lview?loc=_adb_22_10002986&callback=crystal2.addStaticSlot"></script>

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

  • Warning Line 1209, Column 79: reference to external entity in attribute value
    …r.zing.vn/lview?loc=_adb_22_10002986&callback=crystal2.addStaticSlot"></script>

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

  • Error Line 1209, Column 79: reference to entity "callback" for which no system identifier could be generated
    …r.zing.vn/lview?loc=_adb_22_10002986&callback=crystal2.addStaticSlot"></script>

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

  • Info Line 1205, Column 70: entity was defined here
    …ker.zing.vn/lview?loc=_adb_22_10002985&callback=crystal2.addStaticSlot"></scri…
  • Error Line 1209, Column 103: required attribute "type" not specified
    …r.zing.vn/lview?loc=_adb_22_10002986&callback=crystal2.addStaticSlot"></script>

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

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

  • Error Line 1220, Column 254: document type does not allow element "a" here
    …L = '<a href="javascript:hide_float()">x</a>'; } else { content.style.display …

    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 1220, Column 355: document type does not allow element "a" here
    …ide.innerHTML = '<a href="javascript:hide_float()">GAME Hot Lắm Nè!!!</a>'; } }

    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 1222, Column 7: required attribute "type" not specified
    <style>

    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 1222, Column 7: document type does not allow element "style" here
    <style>

    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 1231, Column 21: there is no attribute "marginWidth"
    <iframe marginWidth="0" marginHeight="0" frameBorder="0" width="300" height="25…

    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 1231, Column 38: there is no attribute "marginHeight"
    <iframe marginWidth="0" marginHeight="0" frameBorder="0" width="300" height="25…

    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 1231, Column 54: there is no attribute "frameBorder"
    …idth="0" marginHeight="0" frameBorder="0" width="300" height="250" bottommargi…

    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 1231, Column 96: there is no attribute "bottommargin"
    …width="300" height="250" bottommargin="0" rightmargin="0" leftmargin="0" topma…

    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 1231, Column 112: there is no attribute "rightmargin"
    …ht="250" bottommargin="0" rightmargin="0" leftmargin="0" topmargin="0" nosize …

    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 1231, Column 127: there is no attribute "leftmargin"
    …margin="0" rightmargin="0" leftmargin="0" topmargin="0" nosize scrolling="no" …

    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 1231, Column 141: there is no attribute "topmargin"
    …htmargin="0" leftmargin="0" topmargin="0" nosize scrolling="no" src="http://im…

    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 1231, Column 152: "nosize" is not a member of a group specified for any attribute
    …" leftmargin="0" topmargin="0" nosize scrolling="no" src="http://img.goodadver…
  • Error Line 1260, Column 3: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p>

    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 1262, Column 3: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p>

    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 1267, Column 7: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    </p><p><a href="sitemap.xml" title="Sitemap" class="style2">Sitemap</a>, <a hre…

    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 1267, Column 137: end tag for "p" omitted, but OMITTAG NO was specified
    …">Sitemap</a>, <a href="rss/" class="style2" title="Rss Feed">RSS</a></p></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 1260, Column 1: start tag was here
    <p>
  • Error Line 1267, Column 137: end tag for "p" omitted, but OMITTAG NO was specified
    …">Sitemap</a>, <a href="rss/" class="style2" title="Rss Feed">RSS</a></p></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 1252, Column 1: start tag was here
    <p>
  • Error Line 1267, Column 137: end tag for "center" omitted, but OMITTAG NO was specified
    …">Sitemap</a>, <a href="rss/" class="style2" title="Rss Feed">RSS</a></p></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 1251, Column 1: start tag was here
    <center>
  • Error Line 1268, Column 9: end tag for element "center" which is not open
    </center>

    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 1270, Column 90: end tag for "br" omitted, but OMITTAG NO was specified
    …Contact: Mr.Điệp - 0978.76.86.16  <br>Email: zingphim.net@gmail.com - Yh: zing…

    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 1270, Column 86: start tag was here
    …an> Contact: Mr.Điệp - 0978.76.86.16  <br>Email: zingphim.net@gmail.com - Yh: …
  • Error Line 1273, Column 21: required attribute "type" not specified
    <script id="_wauk2m">var _wau = _wau || []; _wau.push(["small", "b82mzinr6jjx",…

    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 1298, Column 7: invalid comment declaration: found name character outside comment but inside comment declaration
    <!-----code popup----------------------->
  • Info Line 1298, Column 1: comment declaration started here
    <!-----code popup----------------------->
  • Error Line 1300, Column 7: invalid comment declaration: found name character outside comment but inside comment declaration
    <!-----End code popup----------------------->
  • Info Line 1300, Column 1: comment declaration started here
    <!-----End code popup----------------------->

Visitor Analysis

Daily Visitor
  • 350 visits