phimhd.vn

Xem phim hd online miễn phí chất lượng cao tại phimhd.vn, liên tục cập nhật các phim hd chất lượng cao mới nhất nhanh nhất ...

Display Widget for this domain on your website. Click Here
This data was last updated from 15-09-2013 04:22:57  (update).

Overview Info

  • Domain Name
    phimhd.vn
  • Favicon
  • Alexa Rank
    #112406
  • Google Page Rank
    PR 3
  • Ip Address
    123.30.187.219
  • Page Size
    75.3 KB
  • Images
    1 GIF, 43 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 6 0 0 0

Website Meta Analysis



  • Title
    Phim HD, Xem phim HD online mien phi chat luong cao | phimHD.vn
  • Meta Keyword
    Phim HD, Xem Phim HD, Phim HD Nhanh, Phim Chất Lượng Cao, Phim HD Miễn Phí
  • Meta Description
    Xem phim hd online miễn phí chất lượng cao tại phimhd.vn, liên tục cập nhật các phim hd chất lượng cao mới nhất nhanh nhất

Technical Analysis



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

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

HTML Analysis

  • date: Sun, 15 Sep 2013 16:22:46 GMT
  • content-encoding: gzip
  • vary: Accept-Encoding
  • expires: Tue, 31 Dec 1980 00:00:01 GMT
  • cache-control: private
  • pragma: private
  • content-type: text/html; charset=UTF-8
  • connection: close
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for phimhd.vn

DNS Analysis


DNS servers
ns1.afraid.org
ns2.afraid.org [174.37.196.55]

DNS Records

Answer records
phimhd.vn A 123.30.187.219 3600s
phimhd.vn MX
preference: 10
exchange: mail.phimhd.vn
3600s
phimhd.vn TXT google-site-verification=M8nq8WcO6obaaU0kuOQoo9-opd764-rNXQ-vq9PI5eU 3600s
phimhd.vn SOA
server: ns1.afraid.org
email: dnsadmin@afraid.org
serial: 1211050005
refresh: 86400
retry: 7200
expire: 2419200
minimum ttl: 3600
3600s
phimhd.vn NS  ns2.afraid.org 3600s
phimhd.vn NS  ns3.afraid.org 3600s
phimhd.vn NS  ns4.afraid.org 3600s
phimhd.vn NS  ns1.afraid.org 3600s

Authority records

Additional records
mail.phimhd.vn A 72.8.150.2 3600s
ns1.afraid.org A 50.23.197.95 300s
ns1.afraid.org 28 [16 bytes] 300s
ns2.afraid.org A 174.37.196.55 300s
ns3.afraid.org A 72.20.15.62 300s
ns4.afraid.org A 174.128.246.102 300s

IP 123.30.187.219 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: 123.30.0.0 - 123.31.255.255
    netname: VDC-NET
    country: vn
    descr: VietNam Data Communication Company (VDC)
    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: 123.30.128.0/18
    descr: VietNam Post and Telecom Corporation (VNPT)
    descr: VNPT-AS-AP
    country: VN
    origin: AS7643
    remarks: mailto: noc@vnn.vn
    notify: hm-changed@vnnic.net.vn
    mnt-by: MAINT-VN-VNPT
    changed: hm-changed@vnnic.net.vn 20100121
    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


Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 24 Errors
  • 663 Warnings
Ratio Text/Html
  • 0.4455003954414034
Message Error
  • Error Line 11, Column 16: there is no attribute "property"
    <meta property="fb:admins" content="100002828542429"/>

    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 12, Column 54: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta property="fb:app_id" content="170796359666689">

    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 1: start tag was here
    <meta property="fb:app_id" content="170796359666689">
  • Error Line 93, Column 8: required attribute "type" not specified
    <script>(function(d, s, id) {

    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 97, Column 57: cannot generate system identifier for general entity "appId"
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=170796359666689";

    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 97, Column 57: general entity "appId" not defined and no default entity
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=170796359666689";

    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 97, Column 62: reference not terminated by REFC delimiter
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=170796359666689";

    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 97, Column 62: reference to entity "appId" for which no system identifier could be generated
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=170796359666689";

    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 97, Column 56: entity was defined here
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=170796359666689";
  • Error Line 139, Column 65: required attribute "action" not specified
            	<form 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 141, Column 34: there is no attribute "autocomplete"
                	<input autocomplete="off" id="search_t" type="text" value="Tìm kiế…

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

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

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

  • Warning Line 166, Column 23: cannot generate system identifier for general entity "t"
    						data: 'k='+kw+'&t='+$('#search_type').val(),

    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 166, Column 23: general entity "t" not defined and no default entity
    						data: 'k='+kw+'&t='+$('#search_type').val(),

    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 166, Column 24: reference not terminated by REFC delimiter
    						data: 'k='+kw+'&t='+$('#search_type').val(),

    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 166, Column 24: reference to entity "t" for which no system identifier could be generated
    						data: 'k='+kw+'&t='+$('#search_type').val(),

    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 166, Column 22: entity was defined here
    						data: 'k='+kw+'&t='+$('#search_type').val(),
  • Error Line 274, Column 13: required attribute "type" not specified
    					<script>

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

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

  • Warning Line 309, Column 23: character "&" is the first character of a delimiter but occurred as data
    							if (cats == '' && countries=='' && years !='') {

    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 309, Column 24: character "&" is the first character of a delimiter but occurred as data
    							if (cats == '' && countries=='' && years !='') {

    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 309, Column 40: character "&" is the first character of a delimiter but occurred as data
    							if (cats == '' && countries=='' && years !='') {

    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 309, Column 41: character "&" is the first character of a delimiter but occurred as data
    							if (cats == '' && countries=='' && years !='') {

    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 312, Column 27: character "&" is the first character of a delimiter but occurred as data
    							else if(cats == '' && countries!='' && years =='')

    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 312, Column 28: character "&" is the first character of a delimiter but occurred as data
    							else if(cats == '' && countries!='' && years =='')

    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 312, Column 44: character "&" is the first character of a delimiter but occurred as data
    							else if(cats == '' && countries!='' && years =='')

    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 312, Column 45: character "&" is the first character of a delimiter but occurred as data
    							else if(cats == '' && countries!='' && years =='')

    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 316, Column 27: character "&" is the first character of a delimiter but occurred as data
    							else if(cats != '' && countries=='' && years =='')

    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 316, Column 28: character "&" is the first character of a delimiter but occurred as data
    							else if(cats != '' && countries=='' && years =='')

    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 316, Column 44: character "&" is the first character of a delimiter but occurred as data
    							else if(cats != '' && countries=='' && years =='')

    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 316, Column 45: character "&" is the first character of a delimiter but occurred as data
    							else if(cats != '' && countries=='' && years =='')

    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 320, Column 27: character "&" is the first character of a delimiter but occurred as data
    							else if(cats == '' && countries !='' && years !='') 

    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 320, Column 28: character "&" is the first character of a delimiter but occurred as data
    							else if(cats == '' && countries !='' && years !='') 

    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 320, Column 45: character "&" is the first character of a delimiter but occurred as data
    							else if(cats == '' && countries !='' && years !='') 

    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 320, Column 46: character "&" is the first character of a delimiter but occurred as data
    							else if(cats == '' && countries !='' && years !='') 

    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 324, Column 27: character "&" is the first character of a delimiter but occurred as data
    							else if(cats != '' && countries =='' && years !='') 

    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 324, Column 28: character "&" is the first character of a delimiter but occurred as data
    							else if(cats != '' && countries =='' && years !='') 

    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 324, Column 45: character "&" is the first character of a delimiter but occurred as data
    							else if(cats != '' && countries =='' && years !='') 

    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 324, Column 46: character "&" is the first character of a delimiter but occurred as data
    							else if(cats != '' && countries =='' && years !='') 

    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 328, Column 27: character "&" is the first character of a delimiter but occurred as data
    							else if(cats != '' && countries !='' && years =='') 

    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 328, Column 28: character "&" is the first character of a delimiter but occurred as data
    							else if(cats != '' && countries !='' && years =='') 

    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 328, Column 45: character "&" is the first character of a delimiter but occurred as data
    							else if(cats != '' && countries !='' && years =='') 

    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 328, Column 46: character "&" is the first character of a delimiter but occurred as data
    							else if(cats != '' && countries !='' && years =='') 

    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 332, Column 27: character "&" is the first character of a delimiter but occurred as data
    							else if(cats != '' && countries !='' && years !='') 

    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 332, Column 28: character "&" is the first character of a delimiter but occurred as data
    							else if(cats != '' && countries !='' && years !='') 

    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 332, Column 45: character "&" is the first character of a delimiter but occurred as data
    							else if(cats != '' && countries !='' && years !='') 

    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 332, Column 46: character "&" is the first character of a delimiter but occurred as data
    							else if(cats != '' && countries !='' && years !='') 

    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 397, Column 59: there is no attribute "data-href"
    …-home"><div class="fb-like" data-href="http://www.facebook.com/phimHD.vn" data…

    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 397, Column 105: there is no attribute "data-send"
    …www.facebook.com/phimHD.vn" data-send="false" data-layout="button_count" data-…

    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 397, Column 125: there is no attribute "data-layout"
    …mHD.vn" data-send="false" data-layout="button_count" data-width="100" data-sho…

    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 397, Column 151: there is no attribute "data-width"
    …data-layout="button_count" data-width="100" data-show-faces="true"></div><p>&n…

    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 397, Column 173: there is no attribute "data-show-faces"
    …unt" data-width="100" data-show-faces="true"></div><p>&nbsp;Like để nhận 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 674, Column 26: required attribute "type" not specified
    <!-- container --><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 727, Column 292: end tag for "img" omitted, but OMITTAG NO was specified
    …" src="http://whos.amung.us/swidget/phimhdvn" alt="" border="0" height="0"></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 727, Column 202: start tag was here
    …http://whos.amung.us/stats/phimhdvn/"><img style="" src="http://whos.amung.us/…
  • Error Line 730, Column 178: required attribute "alt" not specified
    …"/img/XT-200x50.png" width="200px" height="50px" style="float: right;"></a></p>

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

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

  • Error Line 730, Column 182: end tag for "img" omitted, but OMITTAG NO was specified
    …"/img/XT-200x50.png" width="200px" height="50px" style="float: right;"></a></p>

    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 730, Column 99: start tag was here
    …/00000/1ba_PHIMHD_VN" target="_blank"><img src="/img/XT-200x50.png" width="200…
  • Warning Line 763, Column 23: character "<" is the first character of a delimiter but occurred as data
    							if(windowWidth < 1210){

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

    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 226, Column 3: start tag was here
    	 <div id="body" class="detail"><!-- header -->
  • Error Line 789, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body>

    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 100, Column 1: start tag was here
    <div id="Fancy-Free">

Visitor Analysis

Daily Visitor
  • 1.202 visits

In Page Analysis