cool-tv.net

Cool Tv Online - Televiziune Digitala prin Internet ! canale tv live pe calculator: filme, muzica, desene, sport, divertisment, entertainment ...

Display Widget for this domain on your website. Click Here
Processing update domain...

Overview Info

  • Domain Name
    cool-tv.net
  • Favicon
  • Alexa Rank
    #23814
  • Google Page Rank
    PR 4
  • Ip Address
    141.101.125.238
  • Page Size
    58.2 KB
  • Images
    5 GIF, 0 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    2 1 0 0 0 0

Website Meta Analysis



  • Title
    Cool Tv Online - Televiziune Digitala prin Internet ! Entertainment
  • Meta Keyword
    cool tv, tvonline, tv online, online tv, onlinetv, canale romanesti, Cool Tv, Entertainment, posturi, programe, canale
  • Meta Description
    Cool Tv Online - Televiziune Digitala prin Internet ! canale tv live pe calculator: filme, muzica, desene, sport, divertisment, entertainment

Technical Analysis



  • Webserver
    cloudflare-nginx
  • Ip Address
    141.101.125.238
  • Domain Age
    5 Years, 6 Months, 17 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from cool-tv.net.

HTML Analysis

  • server: cloudflare-nginx
  • date: Thu, 22 Aug 2013 23:16:40 GMT
  • content-type: text/html
  • connection: keep-alive
  • expires: Fri, 23 Aug 2013 01:18:01 GMT
  • cache-control: max-age=7200
  • last-modified: Sun, 04 Aug 2013 22:12:40 GMT
  • cf-ray: a2345a7f7b70388
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Domain Name: cool-tv.net
Registrant:
*
Dambu Marian ()

Fax:
*
Bucharest, * *
RO
Administrative Contact:
*
Dambu Marian ( email )
+40.721893764
Fax: +1.5555555555
*
Bucharest, * *
RO
Technical Contact:
*
Dambu Marian ( email )
+40.721893764
Fax: +1.5555555555
*
Bucharest, * *
RO
Domain Status: Active
Name Servers:
dns1.registrar-servers.com
dns2.registrar-servers.com
dns3.registrar-servers.com

Created: 03 Feb 2008 13:11:05
Expires: 03 Feb 2013 13:11:05

DNS Analysis


DNS servers
dns2.registrar-servers.com [208.64.122.242]
dns1.registrar-servers.com [38.101.213.194]
dns3.registrar-servers.com [173.224.125.12]
dns4.registrar-servers.com [173.236.55.99]
dns5.registrar-servers.com [188.138.2.23]


DNS Records

Answer records
cool-tv.net NS  dns1.registrar-servers.com 1800s
cool-tv.net NS  dns5.registrar-servers.com 1800s
cool-tv.net NS  dns4.registrar-servers.com 1800s
cool-tv.net NS  dns3.registrar-servers.com 1800s
cool-tv.net A 95.211.60.26 120s
cool-tv.net NS  dns2.registrar-servers.com 1800s
cool-tv.net SOA
server: dns1.registrar-servers.com
email: hostmaster@registrar-servers.com
serial: 2012092600
refresh: 3600
retry: 1801
expire: 604800
minimum ttl: 3601
3601s

Authority records

Additional records

IP 141.101.125.238 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

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

    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.

  • Error Line 84, 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 85, 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).

  • Error Line 89, Column 29: there is no attribute "HEIGHT"
      <table width="855" height="749" border="0" align="center" cellpadding="1" cel…

    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 91, Column 62: there is no attribute "BACKGROUND"
    …eight="592" align="center" background="chenar-mare-index.gif">        <div ali…

    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 428, Column 32: there is no attribute "DATA-HREF"
    <div class="fb-like" data-href="http://www.facebook.com/CoolTvNet.nr1" data-sen…

    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 428, Column 82: there is no attribute "DATA-SEND"
    …facebook.com/CoolTvNet.nr1" data-send="true" data-width="450" data-show-faces=…

    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 428, Column 100: there is no attribute "DATA-WIDTH"
    …vNet.nr1" data-send="true" data-width="450" 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 428, Column 122: there is no attribute "DATA-SHOW-FACES"
    …send="true" data-width="450" 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 428, Column 140: there is no attribute "DATA-FONT"
    …send="true" data-width="450" 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.

  • Warning Line 434, Column 27: NET-enabling start-tag requires SHORTTAG YES
     maxlength="255" value="" />

    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 435, Column 44: NET-enabling start-tag requires SHORTTAG YES
    <input type="submit" value="Google Search" />

    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 444, Column 105: cannot generate system identifier for general entity "msg"
    …le43"> ...</span> <a href="ymsgr:im?+&msg=%20%20%20www.cool-tv.net%20-%20Super…

    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 444, Column 105: general entity "msg" not defined and no default entity
    …le43"> ...</span> <a href="ymsgr:im?+&msg=%20%20%20www.cool-tv.net%20-%20Super…

    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 444, Column 108: reference to entity "msg" for which no system identifier could be generated
    …3"> ...</span> <a href="ymsgr:im?+&msg=%20%20%20www.cool-tv.net%20-%20Super%20…

    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 444, Column 104: entity was defined here
    …yle43"> ...</span> <a href="ymsgr:im?+&msg=%20%20%20www.cool-tv.net%20-%20Supe…
  • Warning Line 527, Column 51: cannot generate system identifier for general entity "iCategory"
    …p://www.deco-artis.ro/?p=productsList&iCategory=56" target="_blank"><img src="…

    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 527, Column 51: general entity "iCategory" not defined and no default entity
    …p://www.deco-artis.ro/?p=productsList&iCategory=56" target="_blank"><img src="…

    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 527, Column 60: reference to entity "iCategory" for which no system identifier could be generated
    …eco-artis.ro/?p=productsList&iCategory=56" target="_blank"><img src="reclame/a…

    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 527, Column 50: entity was defined here
    …tp://www.deco-artis.ro/?p=productsList&iCategory=56" target="_blank"><img src=…
  • Error Line 890, 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
  • 1.867 visits

In Page Analysis