xem phim online nhanh, cập nhập hàng ngày với nhiều bộ phim cực kỳ hấp dẫn, phim hành động, phim tình cảm, phim hàn quốc, phim kinh dị, khoa học viễn tưởng, Phim47.Com ...

phim47.com
  • Domain Name
    phim47.com
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #29996
  • Page Size
    108.5 KB
  • Ip Address
    123.30.187.229
  • Heading
    H1: 1, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 73 JPG, 0 PNG

Website Meta Analysis

  • Title
    Xem Phim Online, xem phim moi nhat, xem phim han quoc
  • Meta Keyword
    phim, phim hay, xem phim, phim online, xem phim online, xem phim nhanh, phim online nhanh, phim hanh dong
  • Meta Description
    xem phim online nhanh, cập nhập hàng ngày với nhiều bộ phim cực kỳ hấp dẫn, phim hành động, phim tình cảm, phim hàn quốc, phim kinh dị, khoa học viễn tưởng, Phim47.Com

Technical Analysis

  • Webserver
  • Ip Address
    123.30.187.229
  • Domain Age
    3 Years, 10 Months, 16 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Thu, 12 Sep 2013 18:04:40 GMT
  • content-encoding: gzip
  • vary: Accept-Encoding,User-Agent
  • 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
Domain Name: PHIM47.COM

Registrant:
None
Nguyen Huu Minh ( email )
Dak Lak
Dak Lak
Dak Lak,84000
VN
Tel. +84.1692006668

Creation Date: 17-Nov-2009
Expiration Date: 17-Nov-2017

Domain servers in listed order:
ns1.sitelutions.com
ns2.sitelutions.com
ns3.sitelutions.com
ns4.sitelutions.com


Administrative Contact:
None
Nguyen Huu Minh ( email )
Dak Lak
Dak Lak
Dak Lak,84000
VN
Tel. +84.1692006668

Technical Contact:
None
Nguyen Huu Minh ( email )
Dak Lak
Dak Lak
Dak Lak,84000
VN
Tel. +84.1692006668

Billing Contact:
None
Nguyen Huu Minh ( email )
Dak Lak
Dak Lak
Dak Lak,84000
VN
Tel. +84.1692006668

Status:LOCKED

DNS Analysis


DNS servers
ns1.sitelutions.com [67.208.74.19]
ns2.sitelutions.com [69.26.176.28]
ns3.sitelutions.com [66.231.180.140]
ns4.sitelutions.com [67.208.84.25]

DNS Records

Answer records
phim47.com SOA
server: ns1.sitelutions.com
email: huuminh@us.gmail.com
serial: 344
refresh: 28000
retry: 7200
expire: 604800
minimum ttl: 1
3600s
phim47.com NS  ns1.sitelutions.com 172800s
phim47.com NS  ns2.sitelutions.com 172800s
phim47.com NS  ns3.sitelutions.com 172800s
phim47.com NS  ns4.sitelutions.com 172800s
phim47.com NS  ns5.sitelutions.com 172800s
phim47.com A 123.30.187.229 21600s
phim47.com MX
preference: 1
exchange: ASPMX.L.GOOGLE.com
21600s
phim47.com MX
preference: 5
exchange: ALT2.ASPMX.L.GOOGLE.com
21600s
phim47.com MX
preference: 5
exchange: ALT1.ASPMX.L.GOOGLE.com
21600s
phim47.com MX
preference: 10
exchange: ASPMX2.GOOGLEMAIL.com
21600s
phim47.com MX
preference: 10
exchange: ASPMX5.GOOGLEMAIL.com
21600s
phim47.com MX
preference: 10
exchange: ASPMX3.GOOGLEMAIL.com
21600s
phim47.com MX
preference: 10
exchange: ASPMX4.GOOGLEMAIL.com
21600s

Authority records

Additional records
ns1.sitelutions.com A 67.208.74.19 172800s
ns2.sitelutions.com A 69.26.176.28 172800s
ns3.sitelutions.com A 66.231.180.140 172800s
ns4.sitelutions.com A 67.208.84.25 172800s
ns5.sitelutions.com A 69.93.94.154 172800s

IP 123.30.187.229 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-4]
    % 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: 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:
    notify:
    mnt-by: MAINT-VN-VNPT
    changed: 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:
    remarks: send spam reports to
    remarks: and abuse reports to
    admin-c: THMH1-AP
    tech-c: THMH1-AP
    nic-hdl: VIG1-AP
    notify:
    mnt-by: MAINT-VN-VNPT
    changed: 20090325
    source: APNIC
    changed: 20111114


In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 71 Errors
  • 34 Warnings
Ratio Text/Html
  • 0.7358782749617359
Message Error
  • Error Line 2, Column 13: there is no attribute "XMLNS"
    <html xmlns="http://www.w3.org/1999/xhtml" lang="vi" xml:lang="vi">

    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 2, Column 63: there is no attribute "XML:LANG"
    <html xmlns="http://www.w3.org/1999/xhtml" lang="vi" xml:lang="vi">

    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.

  • Warning Line 4, Column 92: NET-enabling start-tag requires SHORTTAG YES
    …ogle-site-verification" content="4t4iQBjIJ1GiNk4iid_Dwja2xUYroj2cV3L6iPOpnks"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 4, Column 93: character data is not allowed here
    …ogle-site-verification" content="4t4iQBjIJ1GiNk4iid_Dwja2xUYroj2cV3L6iPOpnks"/>

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Warning Line 5, Column 66: NET-enabling start-tag requires SHORTTAG YES
    <meta http-equiv=Content-Type content="text/html; charset=utf-8" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 7, Column 45: NET-enabling start-tag requires SHORTTAG YES
    <meta name="robots" content="index, follow" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 8, Column 34: NET-enabling start-tag requires SHORTTAG YES
    <meta name="keywords" content="" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 8, Column 34: document type does not allow element "META" here
    <meta name="keywords" content="" />

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

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

  • Warning Line 9, Column 59: NET-enabling start-tag requires SHORTTAG YES
    <meta name="title" content="Xem Phim Online - Phim47.Com" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 9, Column 59: document type does not allow element "META" here
    <meta name="title" content="Xem Phim Online - Phim47.Com" />

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

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

  • Warning Line 10, Column 63: NET-enabling start-tag requires SHORTTAG YES
    <meta name="copyright" content="Phim47.Com - Xem Phim Online" /> 

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 10, Column 63: document type does not allow element "META" here
    <meta name="copyright" content="Phim47.Com - Xem Phim Online" /> 

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

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

  • Warning Line 11, Column 66: NET-enabling start-tag requires SHORTTAG YES
    <meta name="author" content="Nguyễn Hữu Minh - Call 01692006668" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 11, Column 66: document type does not allow element "META" here
    <meta name="author" content="Nguyễn Hữu Minh - Call 01692006668" />

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

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

  • Warning Line 12, Column 204: NET-enabling start-tag requires SHORTTAG YES
    … hành động, phim tình cảm, phim hàn quốc, phim kinh dị, khoa học viễn tưởng" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 12, Column 204: document type does not allow element "META" here
    … hành động, phim tình cảm, phim hàn quốc, phim kinh dị, khoa học viễn tưởng" />

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

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

  • Warning Line 13, Column 44: NET-enabling start-tag requires SHORTTAG YES
    <meta name="generator" content="PHP XHTML" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 13, Column 44: document type does not allow element "META" here
    <meta name="generator" content="PHP XHTML" />

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

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

  • Warning Line 14, Column 44: NET-enabling start-tag requires SHORTTAG YES
    <meta name="abstract" content="Movie Site" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 14, Column 44: document type does not allow element "META" here
    <meta name="abstract" content="Movie Site" />

    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 15, Column 16: there is no attribute "PROPERTY"
    <meta property="fb:app_id" content="397189350367259" />

    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.

  • Warning Line 15, Column 54: NET-enabling start-tag requires SHORTTAG YES
    <meta property="fb:app_id" content="397189350367259" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 15, Column 54: document type does not allow element "META" here
    <meta property="fb:app_id" content="397189350367259" />

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

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

  • Warning Line 17, Column 49: NET-enabling start-tag requires SHORTTAG YES
    <link rel="canonical" href="http://phim47.com/" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 17, Column 49: document type does not allow element "LINK" here
    <link rel="canonical" href="http://phim47.com/" />

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

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

  • Warning Line 18, Column 106: NET-enabling start-tag requires SHORTTAG YES
    …application/atom+xml" title="Phim47.Com - Atom" href="http://phim47.com/rss" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 18, Column 106: document type does not allow element "LINK" here
    …application/atom+xml" title="Phim47.Com - Atom" href="http://phim47.com/rss" />

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

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

  • Warning Line 19, Column 104: NET-enabling start-tag requires SHORTTAG YES
    …="application/rss+xml" title="Phim47.Com - RSS" href="http://phim47.com/rss" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 19, Column 104: document type does not allow element "LINK" here
    …="application/rss+xml" title="Phim47.Com - RSS" href="http://phim47.com/rss" />

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

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

  • Warning Line 20, Column 90: NET-enabling start-tag requires SHORTTAG YES
    …hortcut icon" href="http://phim47.com/images/favicon.gif" type="image/x-icon"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 20, Column 90: document type does not allow element "LINK" here
    …hortcut icon" href="http://phim47.com/images/favicon.gif" type="image/x-icon"/>

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

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

  • Warning Line 21, Column 91: NET-enabling start-tag requires SHORTTAG YES
    …ylesheet" href="http://phim47.com/skin/movie/style/style.css" type="text/css"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 21, Column 91: document type does not allow element "LINK" here
    …ylesheet" href="http://phim47.com/skin/movie/style/style.css" type="text/css"/>

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

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

  • Error Line 26, 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 31, Column 85: end tag for element "CENTER" which is not open
    …dingText = "<center><img src='http://phim47.com/images/loading.gif'></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 41, Column 7: end tag for element "HEAD" which is not open
    </head>

    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 42, Column 50: document type does not allow element "BODY" here
    …ck="popupud();" onmouseover="UnTip();"><script type="text/javascript" src="htt…

    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 47, Column 126: there is no attribute "PLACEHOLDER"
    …yword_search" type="text" placeholder="Nhập vào tên phim bạn muốn tìm"  tabind…

    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.

  • Warning Line 47, Column 175: NET-enabling start-tag requires SHORTTAG YES
    …pe="text" placeholder="Nhập vào tên phim bạn muốn tìm"  tabindex="1"   /></div>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 61, Column 63: cannot generate system identifier for general entity "link"
    …47.com/no-cache/member.php?type=login&link=http://phim47.com/" type="text/java…

    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 61, Column 63: general entity "link" not defined and no default entity
    …47.com/no-cache/member.php?type=login&link=http://phim47.com/" type="text/java…

    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.

  • Error Line 61, Column 67: reference to entity "link" for which no system identifier could be generated
    …om/no-cache/member.php?type=login&link=http://phim47.com/" type="text/javascri…

    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 61, Column 62: entity was defined here
    …m47.com/no-cache/member.php?type=login&link=http://phim47.com/" type="text/jav…
  • Error Line 67, Column 473: there is no attribute "ALT"
    …kZGDjZQN=')" onmouseout="UnTip()" alt="Nữ Đặc Vụ Xinh Đẹp" ><img class="showen…

    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 67, Column 5874: required attribute "TYPE" not specified
    …lass="clear"></div></div></div><script>$(document).ready(function() {var root …

    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 71, Column 755: duplicate specification of attribute "TITLE"
    …"><h1><a title="Nhanh Hay Chết" title="Nhanh Hay Chết (2011)" href="http://phi…

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

  • Error Line 71, Column 993: there is no attribute "ITEMPROP"
    …dong.html' title='Hành Động' itemprop="genre">Hành Động</a></span><span class=…

    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 71, Column 2014: duplicate specification of attribute "TITLE"
    …h1><a title="Người Tình Bí Mật" title="Người Tình Bí Mật (2011)" href="http://…

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

  • Error Line 71, Column 3363: duplicate specification of attribute "TITLE"
    …title"><h1><a title="Chỉ Có Em" title="Chỉ Có Em (2011)" href="http://phim47.c…

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

  • Error Line 71, Column 4725: duplicate specification of attribute "TITLE"
    …<a title="Một Tuần Với Kiều Nữ" title="Một Tuần Với Kiều Nữ (2011)" href="http…

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

  • Error Line 71, Column 6338: duplicate specification of attribute "TITLE"
    …<a title="Đại Gia Đình Mafia 4" title="Đại Gia Đình Mafia 4 (2011)" href="http…

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

  • Error Line 71, Column 7622: duplicate specification of attribute "TITLE"
    …"><h1><a title="Lối Thoát 2012" title="Lối Thoát 2012 (2012)" href="http://phi…

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

  • Error Line 71, Column 9005: duplicate specification of attribute "TITLE"
    …h1><a title="Thất Tình 33 Ngày" title="Thất Tình 33 Ngày (2011)" href="http://…

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

  • Error Line 71, Column 10500: duplicate specification of attribute "TITLE"
    …><a title="Câu Chuyện Tình Yêu" title="Câu Chuyện Tình Yêu (2011)" href="http:…

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

  • Error Line 71, Column 11835: duplicate specification of attribute "TITLE"
    …s="title"><h1><a title="Ẩn Sát" title="Ẩn Sát (2011)" href="http://phim47.com/…

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

  • Error Line 71, Column 13233: duplicate specification of attribute "TITLE"
    …itle"><h1><a title="Kẻ Đối Đầu" title="Kẻ Đối Đầu (2011)" href="http://phim47.…

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

  • Error Line 71, Column 14430: duplicate specification of attribute "TITLE"
    …"title"><h1><a title="Tình Bạn" title="Tình Bạn (2008)" href="http://phim47.co…

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

  • Error Line 71, Column 15742: duplicate specification of attribute "TITLE"
    …="title"><h1><a title="Điềm Gở" title="Điềm Gở (2012)" href="http://phim47.com…

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

  • Warning Line 71, Column 16053: NET-enabling start-tag requires SHORTTAG YES
    …dung <span><a target=_blank href=http://phim47.com title=phim>phim</a></span> …

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 71, Column 16084: end tag for element "A" which is not open
    …f=http://phim47.com title=phim>phim</a></span> hấp dẫn nói về Ethan Hawke - mộ…

    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 74, Column 772: duplicate specification of attribute "TITLE"
    …title="Người Bảo Vệ Kinh Thánh" title="Người Bảo Vệ Kinh Thánh (2003)" href="h…

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

  • Error Line 74, Column 2155: duplicate specification of attribute "TITLE"
    …e"><h1><a title="Ký Sinh Trùng" title="Ký Sinh Trùng (2012)" href="http://phim…

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

  • Warning Line 74, Column 2485: NET-enabling start-tag requires SHORTTAG YES
    …à bộ <span><a target=_blank href=http://phim47.com title=phim>phim</a></span> …

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 74, Column 2516: end tag for element "A" which is not open
    …f=http://phim47.com title=phim>phim</a></span> đầu tiên của Hàn Quốc về đề tài…

    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 74, Column 3404: duplicate specification of attribute "TITLE"
    …h1><a title="Biến Địa Lang Yến" title="Biến Địa Lang Yến (2011)" href="http://…

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

  • Error Line 75, Column 890: duplicate specification of attribute "TITLE"
    …- Hải Tặc Mủ Rơm - Đảo Hải Tặc" title="Vua Hải Tặc - Hải Tặc Mủ Rơm - Đảo Hải …

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

  • Error Line 75, Column 2272: duplicate specification of attribute "TITLE"
    …="Nàng Alice Phố Cheongdamdong" title="Nàng Alice Phố Cheongdamdong (2012)" hr…

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

  • Error Line 75, Column 2845: there is no attribute "ALICE"
    …amdong-Alice.html" title="Nàng" alice="" phố="" cheongdamdong="">Nàng Alice Ph…

    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 75, Column 2850: "PH" is not a member of a group specified for any attribute
    …g-Alice.html" title="Nàng" alice="" ph="" cheongdamdong="">Nàng Alice Phố Che…
  • Error Line 75, Column 2869: there is no attribute "CHEONGDAMDONG"
    …="Nàng" alice="" phố="" cheongdamdong="">Nàng Alice Phố Cheongdamdong</a></spa…

    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 78, Column 722: duplicate specification of attribute "TITLE"
    …le"><h1><a title="Mũi Tên Xanh" title="Mũi Tên Xanh (2012)" href="http://phim4…

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

  • Error Line 79, Column 773: duplicate specification of attribute "TITLE"
    …<h1><a title="Gia Đình Ojakgyo" title="Gia Đình Ojakgyo (2012)" href="http://p…

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

  • Error Line 79, Column 1456: character "đ" not allowed in attribute specification list
    …om/tim-kiem/gia%20dinh/0" title="gia" đình="">gia đình</a></span> với bốn ngườ…
  • Error Line 82, Column 736: duplicate specification of attribute "TITLE"
    …"><h1><a title="Tiệm Mì Mỹ Nam" title="Tiệm Mì Mỹ Nam (2011)" href="http://phi…

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

  • Error Line 82, Column 1855: duplicate specification of attribute "TITLE"
    …1><a title="Nơi Chốn Cuối Cùng" title="Nơi Chốn Cuối Cùng (2012)" href="http:/…

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

  • Error Line 82, Column 2294: "CH" is not a member of a group specified for any attribute
    …ort-Season-1-2012.html" title="Nơi" chn="" cuối="" cùng="">Nơi Chốn Cuối Cùng…
  • Error Line 82, Column 2302: "CU" is not a member of a group specified for any attribute
    …on-1-2012.html" title="Nơi" chốn="" cui="" cùng="">Nơi Chốn Cuối Cùng</a></sp…
  • Error Line 82, Column 2309: "C" is not a member of a group specified for any attribute
    …12.html" title="Nơi" chốn="" cuối="" cùng="">Nơi Chốn Cuối Cùng</a></span> - <…
  • Error Line 82, Column 2477: there is no attribute "RESORT"
    …ason-1-2012.html" title="Last" resort="">Last Resort</a></span> (2012): Một ch…

    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 85, Column 708: duplicate specification of attribute "TITLE"
    …le"><h1><a title="Jeon Woo Chi" title="Jeon Woo Chi (2012)" href="http://phim4…

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

  • Error Line 85, Column 1331: there is no attribute "WOO"
    …i/Jeon-Woo-Chi.html" title="Jeon" woo="" chi="">Jeon Woo Chi</a></span> là một…

    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 85, Column 1338: there is no attribute "CHI"
    …on-Woo-Chi.html" title="Jeon" woo="" chi="">Jeon Woo Chi</a></span> là một đạo 

    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 88, Column 715: duplicate specification of attribute "TITLE"
    …<h1><a title="Sát Thủ Nikita 3" title="Sát Thủ Nikita 3 (2012)" href="http://p…

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

  • Error Line 91, Column 699: duplicate specification of attribute "TITLE"
    …s="title"><h1><a title="Phi Hổ" title="Phi Hổ (2012)" href="http://phim47.com/…

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

  • Warning Line 91, Column 1099: NET-enabling start-tag requires SHORTTAG YES
    …ent"><span><a target=_blank href=http://phim47.com/xem-phim-Phi-Ho/Tiger-Cubs-…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 91, Column 1167: end tag for element "A" which is not open
    …iger-Cubs-2012.html title=Phim>Phim</a></span> dài 13 tập, do giám chế Lâm Chí…

    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 93, Column 793: duplicate specification of attribute "TITLE"
    …oàng Cung - Được Làm Hoàng Hậu" title="Hoàng Cung - Được Làm Hoàng Hậu (2009)"…

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

  • Error Line 93, Column 2162: duplicate specification of attribute "TITLE"
    …"title"><h1><a title="Nữ Quyền" title="Nữ Quyền (2011)" href="http://phim47.co…

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

  • Error Line 96, Column 697: duplicate specification of attribute "TITLE"
    …title"><h1><a title="Miss Rose" title="Miss Rose (2012)" href="http://phim47.c…

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

  • Error Line 99, Column 723: duplicate specification of attribute "TITLE"
    …itle"><h1><a title="Anh Nhớ Em" title="Anh Nhớ Em (2012)" href="http://phim47.…

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

  • Error Line 102, Column 787: duplicate specification of attribute "TITLE"
    … title="Chàng Quản Gia Của Tôi" title="Chàng Quản Gia Của Tôi (2009)" href="ht…

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

  • Error Line 105, Column 739: duplicate specification of attribute "TITLE"
    …h1><a title="Naruto Shippuuden" title="Naruto Shippuuden " href="http://phim47…

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

  • Error Line 123, Column 4: end tag for element "P" which is not open
    </p><div class='clear'></div><div class='clear_td'></div> 	

    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 126, Column 4: end tag for element "P" which is not open
    </p><div class='clear'></div><div class='clear_td'></div> 	

    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 129, Column 4: end tag for element "P" which is not open
    </p><div class='clear'></div><div class='clear_td'></div> 	

    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 132, Column 4: end tag for element "P" which is not open
    </p><div class='clear'></div><div class='clear_td'></div> 	

    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 135, Column 4: end tag for element "P" which is not open
    </p><div class='clear'></div><div class='clear_td'></div> 	

    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 138, Column 4: end tag for element "P" which is not open
    </p><div class='clear'></div><div class='clear_td'></div> 	

    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 141, Column 4: end tag for element "P" which is not open
    </p><div class='clear'></div><div class='clear_td'></div> 	

    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 144, Column 4: end tag for element "P" which is not open
    </p><div class='clear'></div><div class='clear_td'></div> 	

    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 147, Column 4: end tag for element "P" which is not open
    </p><div class='clear'></div><div class='clear_td'></div> 	

    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 150, Column 4: end tag for element "P" which is not open
    </p><div class='clear'></div></div>

    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 155, Column 4: end tag for element "P" which is not open
    </p><div class='clear'></div><div class='clear_td'></div> 	

    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 158, Column 4: end tag for element "P" which is not open
    </p><div class='clear'></div><div class='clear_td'></div> 	

    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 161, Column 4: end tag for element "P" which is not open
    </p><div class='clear'></div><div class='clear_td'></div> 	

    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 164, Column 4: end tag for element "P" which is not open
    </p><div class='clear'></div><div class='clear_td'></div> 	

    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 167, Column 4: end tag for element "P" which is not open
    </p><div class='clear'></div><div class='clear_td'></div> 	

    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 170, Column 4: end tag for element "P" which is not open
    </p><div class='clear'></div><div class='clear_td'></div> 	

    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 173, Column 4: end tag for element "P" which is not open
    </p><div class='clear'></div><div class='clear_td'></div> 	

    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 176, Column 4: end tag for element "P" which is not open
    </p><div class='clear'></div><div class='clear_td'></div> 	

    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 179, Column 4: end tag for element "P" which is not open
    </p><div class='clear'></div><div class='clear_td'></div> 	

    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 182, Column 4: end tag for element "P" which is not open
    </p><div class='clear'></div></div>

    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 199, Column 390: there is no attribute "ALLOWTRANSPARENCY"
    …0px; height:290px;" allowTransparency="true"></iframe></div><div class="ads4">…

    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 239, Column 81: document type does not allow element "STYLE" here
    …in:10px;"></div><style type="text/css">img {display:inline; }</style><script t…

    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 242, 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>.

Visitor Analysis

Daily Visitor
  • 6.067 visits