Xem Phim Online, phim, xem phim, phim tap, phim viet, phim bo, phim viet nam, phim han quoc, phim kiem hiep, phim vn ...

kenh30.com
  • Domain Name
    kenh30.com
  • Favicon
  • Google Page Rank
    1
  • Alexa Rank
    #65339
  • Page Size
    1.2 KB
  • Ip Address
    108.163.188.218
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
    Phim Online, Phim Le, Phim Bo, Xem Phim Online, Phim Hong Kong
  • Meta Keyword
    Xem Phim Online, phim, xem phim, phim tap, phim viet, phim bo, phim viet nam, phim han quoc, phim kiem hiep, phim vn
  • Meta Description
    Xem Phim Online, phim, xem phim, phim tap, phim viet, phim bo, phim viet nam, phim han quoc, phim kiem hiep, phim vn

Technical Analysis

  • Webserver
    LiteSpeed
  • Ip Address
    108.163.188.218
  • Domain Age
    9 Months, 9 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • content-encoding: gzip
  • vary: Accept-Encoding
  • date: Fri, 28 Jun 2013 13:05:04 GMT
  • server: LiteSpeed
  • accept-ranges: bytes
  • connection: close
  • etag: "4af-51c533ba-de62d1b7a897962c"
  • last-modified: Sat, 22 Jun 2013 05:18:50 GMT
  • content-type: text/html
  • content-length: 574
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
domain: kenh30.com
created: 22-Sep-2012
last-changed: 22-Sep-2012
registration-expiration: 22-Sep-2013

nserver: ns51.1and1.com 217.160.80.164
nserver: ns52.1and1.com 217.160.81.164

status: CLIENT-TRANSFER-PROHIBITED

registrant-firstname: Oneandone
registrant-lastname: Private Registration
registrant-organization: 1&1 Internet, Inc. - http://1and1.com/contact
registrant-street1: 701 Lee Road, Suite 300
registrant-street2: ATTN: kenh30.com
registrant-pcode: 19087
registrant-state: PA
registrant-city: Chesterbrook
registrant-ccode: US
registrant-phone: +1.8772064254
registrant-email: email

admin-c-firstname: Oneandone
admin-c-lastname: Private Registration
admin-c-organization: 1&1 Internet, Inc. - http://1and1.com/contact
admin-c-street1: 701 Lee Road, Suite 300
admin-c-street2: ATTN: kenh30.com
admin-c-pcode: 19087
admin-c-state: PA
admin-c-city: Chesterbrook
admin-c-ccode: US
admin-c-phone: +1.8772064254
admin-c-email: email

tech-c-firstname: Oneandone
tech-c-lastname: Private Registration
tech-c-organization: 1&1 Internet, Inc. - http://1and1.com/contact
tech-c-street1: 701 Lee Road, Suite 300
tech-c-street2: ATTN: kenh30.com
tech-c-pcode: 19087
tech-c-state: PA
tech-c-city: Chesterbrook
tech-c-ccode: US
tech-c-phone: +1.8772064254
tech-c-email: email

bill-c-firstname: Oneandone
bill-c-lastname: Private Registration
bill-c-organization: 1&1 Internet, Inc. - http://1and1.com/contact
bill-c-street1: 701 Lee Road, Suite 300
bill-c-street2: ATTN: kenh30.com
bill-c-pcode: 19087
bill-c-state: PA
bill-c-city: Chesterbrook
bill-c-ccode: US
bill-c-phone: +1.8772064254
bill-c-email: email

DNS Analysis


DNS servers
ns51.1and1.com [217.160.80.164]
ns52.1and1.com [217.160.81.164]


DNS Records

Answer records
kenh30.com MX
preference: 10
exchange: mx00.1and1.com
86400s
kenh30.com NS  ns52.1and1.com 86400s
kenh30.com A 108.163.188.218 86400s
kenh30.com MX
preference: 10
exchange: mx01.1and1.com
86400s
kenh30.com SOA
server: ns51.1and1.com
email: hostmaster@1and1.com
serial: 2012121801
refresh: 28800
retry: 7200
expire: 604800
minimum ttl: 86400
86400s
kenh30.com NS  ns51.1and1.com 86400s

Authority records

Additional records

IP 108.163.188.218 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 15 Errors
  • 9 Warnings
Ratio Text/Html
  • 0.7634854771784232
Message Error
  • Error Line 1, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
    <html>

    The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.

  • Warning Line 4, Column 72: 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 5, Column 48: 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.

  • Error Line 5, Column 48: document type does not allow element "META" here
        <meta name="robots" content="index,follow" />

    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 6, Column 154: NET-enabling start-tag requires SHORTTAG YES
    …, phim viet, phim bo, phim viet nam, phim han quoc, phim kiem hiep, phim vn" />

    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 6, Column 154: document type does not allow element "META" here
    …, phim viet, phim bo, phim viet nam, phim han quoc, phim kiem hiep, phim vn" />

    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 7, Column 35: NET-enabling start-tag requires SHORTTAG YES
        <meta name="title" 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 7, Column 35: document type does not allow element "META" here
        <meta name="title" 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 8, Column 50: NET-enabling start-tag requires SHORTTAG YES
        <meta name="author" content="xomgiaitri.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 8, Column 50: document type does not allow element "META" here
        <meta name="author" content="xomgiaitri.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 9, Column 157: NET-enabling start-tag requires SHORTTAG YES
    …, phim viet, phim bo, phim viet nam, phim han quoc, phim kiem hiep, phim vn" />

    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 157: document type does not allow element "META" here
    …, phim viet, phim bo, phim viet nam, phim han quoc, phim kiem hiep, phim vn" />

    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 10, Column 50: document type does not allow element "META" here
        <meta name="revisit-after" content=" 2 days ">

    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 11, Column 46: document type does not allow element "META" here
        <META HTTP-EQUIV="name" CONTENT="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).

  • Error Line 12, Column 53: document type does not allow element "META" here
        <META HTTP-EQUIV="Content-Language" CONTENT="Vi">

    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 13, Column 44: document type does not allow element "META" here
        <META NAME="Language" CONTENT="vietnam">

    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 14, Column 52: document type does not allow element "META" here
        <meta name="copyright" content="Copyright 2008">

    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 15, Column 93: NET-enabling start-tag requires SHORTTAG YES
    …gle-site-verification" content="-WqFfaNXqV9_XX0HPHHeg1O9guCOqDwu4u_TIDx41Sc" />

    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 93: document type does not allow element "META" here
    …gle-site-verification" content="-WqFfaNXqV9_XX0HPHHeg1O9guCOqDwu4u_TIDx41Sc" />

    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 19, Column 30: required attribute "TYPE" not specified
    <script language="JavaScript">

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

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

  • Error Line 34, 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 37, Column 6: document type does not allow element "BODY" here
    <body>

    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).

Visitor Analysis

Daily Visitor
  • 933 visits
Daily Visitor