Free khmer live TV and radio online. Watch or listen to khmer (cambodia) free tv, free radio, free movie, free music. ...

khiptv.com
  • Domain Name
    khiptv.com
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #80218
  • Page Size
    33.5 KB
  • Ip Address
    72.87.252.101
  • Heading
    H1: 0, H2: 3, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 4 JPG, 17 PNG

Website Meta Analysis

  • Title
    Khmer (Cambodia) Online TV (Television) and Radio
  • Meta Keyword
    TVK, Bayon, TV3, TV5 Cambodia, SEATV,apsara, Khmer TV9 , khmer, live tv, tv, online tv, cambodia, cambodian, television, khmer tv, cambodia tv, cambodian television, radio, khmer radio, cambodia radio, iptv
  • Meta Description
    Free khmer live TV and radio online. Watch or listen to khmer (cambodia) free tv, free radio, free movie, free music.

Technical Analysis

  • Webserver
    Microsoft-IIS/6.0
  • Ip Address
    72.87.252.101
  • Domain Age
    5 Years, 6 Months, 16 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Wed, 11 Sep 2013 12:19:14 GMT
  • server: Microsoft-IIS/6.0
  • x-powered-by: ASP.NET
  • x-aspnet-version: 4.0.30319
  • p3p: CP="ALL CAO PSA OUR"
  • cache-control: no-cache
  • pragma: no-cache
  • expires: -1
  • content-type: text/html; charset=utf-8
  • content-length: 37721
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for khiptv.com

DNS Analysis


DNS servers
yns1.yahoo.com [67.195.1.92]
yns2.yahoo.com [98.139.247.192]


DNS Records

Answer records
khiptv.com A 72.87.252.101 600s
khiptv.com TXT i=201&m=bizmail-mx2-p10 1200s
khiptv.com MX
preference: 20
exchange: mx1.biz.mail.yahoo.com
1200s
khiptv.com MX
preference: 30
exchange: mx5.biz.mail.yahoo.com
1200s
khiptv.com NS  yns1.yahoo.com 86400s
khiptv.com NS  yns2.yahoo.com 86400s
khiptv.com SOA
server: no-dyn-updates.san.yahoo.com
email: postmaster@san.yahoo.com
serial: 2012092801
refresh: 10800
retry: 3600
expire: 7084000
minimum ttl: 28800
1200s

Authority records
khiptv.com NS  yns2.yahoo.com 86400s
khiptv.com NS  yns1.yahoo.com 86400s

Additional records

IP 72.87.252.101 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Long Beach
  • Continent Code
    90807
  • Latitude
    562
  • Longitude
    803
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 72.87.252.101"
    #
    # Use "?" to get help.
    #

    #
    # The following results may also be obtained via:
    # http://whois.arin.net/rest/nets;q=72.87.252.101?showDetails=true&showARIN=false&ext=netref2
    #

    LOR, PHYNA FTTP (NET-72-87-252-96-1) 72.87.252.96 - 72.87.252.103
    Verizon Online LLC VIS-72-64 (NET-72-87-64-0-1) 72.87.64.0 - 72.92.127.255


    #
    # ARIN WHOIS data and services are subject to the Terms of Use
    # available at: https://www.arin.net/whois_tou.html
    #

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 49 Errors
  • 1 Warnings
Ratio Text/Html
  • 0.7945089572270526
Message Error
  • Error Line 17, Column 63: document type does not allow element "link" here
    <link href="style/menu.css" rel="stylesheet" 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 21, Column 85: required attribute "alt" not specified
    …  <tr><td><img id="master_header1_Image1" src="images/banner.png" border="0" />

    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 23, Column 12: document type does not allow element "tr" here; assuming missing "table" start-tag
            <tr><td>
  • Error Line 42, Column 14: end tag for "td" omitted, but OMITTAG NO was specified
            </div>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 21, Column 13: start tag was here
            <tr><td><img id="master_header1_Image1" src="images/banner.png" border=…
  • Error Line 42, Column 14: end tag for "tr" omitted, but OMITTAG NO was specified
            </div>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 21, Column 9: start tag was here
            <tr><td><img id="master_header1_Image1" src="images/banner.png" border=…
  • Error Line 42, Column 14: end tag for "table" omitted, but OMITTAG NO was specified
            </div>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 19, Column 5: start tag was here
        <table cellpadding="0" cellspacing="0">
  • Error Line 54, Column 64: document type does not allow element "link" here
    <link href="style/slide.css" rel="stylesheet" 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 60, Column 5184: document type does not allow element "ul" here; assuming missing "li" start-tag
    …hid=2010012401342310060'>59.  Vong Kanha Slek Meas FM 106.25 Mhz</a></li><ul />
  • Error Line 60, Column 5184: end tag for "ul" which is not finished
    …hid=2010012401342310060'>59.  Vong Kanha Slek Meas FM 106.25 Mhz</a></li><ul />

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 60, Column 5184: end tag for "ul" which is not finished
    …hid=2010012401342310060'>59.  Vong Kanha Slek Meas FM 106.25 Mhz</a></li><ul />

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 61, Column 10: end tag for "li" omitted, but OMITTAG NO was specified
        </div>                

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 60, Column 5179: start tag was here
    …hid=2010012401342310060'>59.  Vong Kanha Slek Meas FM 106.25 Mhz</a></li><ul />
  • Error Line 61, Column 10: end tag for "ul" omitted, but OMITTAG NO was specified
        </div>                

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 60, Column 9: start tag was here
            <ul class='side_menu'><li><a href='radio.aspx?chid=2010012401342310001'…
  • Error Line 142, Column 286: end tag for "img" omitted, but OMITTAG NO was specified
    …maxflags=12/viewers=0/labels=0/" alt="free counters" border="0"></a><br /><br/>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 142, Column 126: start tag was here
    …ounter.com/more/811o" target="_blank"><img src="http://s05.flagcounter.com/cou…
  • Error Line 148, 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>.

  • Error Line 157, Column 32: there is no attribute "data-href"
    <div class="fb-like" data-href="http://www.facebook.com/pages/Rothsron/25750991…

    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 157, Column 99: there is no attribute "data-send"
    …s/Rothsron/257509914300661" data-send="false" data-layout="box_count" data-wid…

    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 157, Column 119: there is no attribute "data-layout"
    …300661" data-send="false" data-layout="box_count" data-width="100" data-show-f…

    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 157, Column 142: there is no attribute "data-width"
    …e" data-layout="box_count" data-width="100" data-show-faces="false" data-font=…

    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 157, Column 164: there is no attribute "data-show-faces"
    …"box_count" data-width="100" data-show-faces="false" data-font="verdana"></div>

    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 157, Column 182: there is no attribute "data-font"
    …"box_count" data-width="100" data-show-faces="false" data-font="verdana"></div>

    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 160, Column 11: element "g:plusone" undefined
    <g:plusone></g:plusone>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 171, Column 94: there is no attribute "expr:data-url"
    …='twitter-share-button' expr:data-url='data:post.url' expr:data-text='data:pos…

    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 171, Column 125: there is no attribute "expr:data-text"
    …ta-url='data:post.url' expr:data-text='data:post.title' data-related='bloggerp…

    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 171, Column 156: there is no attribute "data-related"
    …a-text='data:post.title' data-related='bloggerplugins:Tutorials and Widgets fo…

    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 171, Column 218: there is no attribute "data-count"
    …s and Widgets for Blogger' data-count='vertical' data-via='bloggerplugins'  da…

    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 171, Column 238: there is no attribute "data-via"
    …r Blogger' data-count='vertical' data-via='bloggerplugins'  data-lang='en'></a>

    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 171, Column 266: there is no attribute "data-lang"
    …r Blogger' data-count='vertical' data-via='bloggerplugins'  data-lang='en'></a>

    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 172, Column 12: there is no attribute "cond"
    <b:if cond='data:post.isFirstPost'>

    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 172, Column 35: element "b:if" undefined
    <b:if cond='data:post.isFirstPost'>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 210, Column 63: document type does not allow element "link" here
    <link href="style/main.css" rel="stylesheet" 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 211, Column 66: document type does not allow element "link" here
    <link href="style/tv_menu.css" rel="stylesheet" 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 404, Column 68: document type does not allow element "link" here
        <link href="style/slide.css" rel="stylesheet" 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 406, Column 14: ID "Radio" already defined
        <div id="Radio">       	        

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 56, Column 10: ID "Radio" first defined here
    <div id="Radio">       	        
  • Error Line 411, Column 1101: document type does not allow element "ul" here; assuming missing "li" start-tag
    …04' target='_blank'>Beauty for sale</a></li><ul />                             
  • Error Line 411, Column 1101: end tag for "ul" which is not finished
    …04' target='_blank'>Beauty for sale</a></li><ul />                             

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 411, Column 1101: end tag for "ul" which is not finished
    …04' target='_blank'>Beauty for sale</a></li><ul />                             

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 412, Column 14: end tag for "li" omitted, but OMITTAG NO was specified
            </div>                

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 411, Column 1096: start tag was here
    …04' target='_blank'>Beauty for sale</a></li><ul />                             
  • Error Line 412, Column 14: end tag for "ul" omitted, but OMITTAG NO was specified
            </div>                

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 411, Column 13: start tag was here
                <ul class='side_menu'><li><a href='http://www.kirivong.com/News.php…
  • Error Line 424, Column 63: document type does not allow element "link" here
    <link href="style/main.css" rel="stylesheet" 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 428, Column 52: ID "link" already defined
          <a href="http://khiptv.com/support.aspx" id="link">Support</a>  | 

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 427, Column 14: ID "link" first defined here
        <div id="link">
  • Error Line 429, Column 50: ID "link" already defined
          <a href="http://khiptv.com/phone.aspx" id="link">Mobile Phone</a>  |  

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 427, Column 14: ID "link" first defined here
        <div id="link">
  • Error Line 430, Column 62: ID "link" already defined
    … <a href="http://khiptv.com/boxManual/manaul.aspx"  id="link">Box Manual</a> | 

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 427, Column 14: ID "link" first defined here
        <div id="link">
  • Error Line 431, Column 66: ID "link" already defined
    …   <a href="http://kirivong.com/News.php" target="_blank" id="link">News</a> | 

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 427, Column 14: ID "link" first defined here
        <div id="link">
  • Error Line 432, Column 62: ID "link" already defined
    … href="http://khiptv.com/cambodiaLinkTerm.aspx"  id="link">Terms of Uses</a> | 

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 427, Column 14: ID "link" first defined here
        <div id="link">
  • Error Line 433, Column 43: ID "link" already defined
          <a href="http://e-magic.info/"  id="link">Psychic</a> | 

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 427, Column 14: ID "link" first defined here
        <div id="link">
  • Error Line 434, Column 61: ID "link" already defined
    …ttp://kirivong.com/download/eBook.php"  id="link" target="_blank">E-book</a> | 

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 427, Column 14: ID "link" first defined here
        <div id="link">
  • Error Line 435, Column 58: ID "link" already defined
          <a href="http://khiptv.com/cambodiaLink.aspx"  id="link">Links</a> | 

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 427, Column 14: ID "link" first defined here
        <div id="link">
  • Error Line 436, Column 66: ID "link" already defined
    …   <a href="http://kirivong.com/game.php" target="_blank" id="link">Game</a> | 

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 427, Column 14: ID "link" first defined here
        <div id="link">
  • Error Line 437, Column 51: ID "link" already defined
          <a href="http://khiptv.com/about.aspx"  id="link">About Us</a> 

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 427, Column 14: ID "link" first defined here
        <div id="link">

Visitor Analysis

Daily Visitor
  • 1.983 visits