Aktualny program telewizyjny polskich i zagranicznych stacji. Program TV oraz recenzje filmów i plotki z przemysłu rozrywkowego. Sprawdź - Telemagazyn.pl ...

telemagazyn.pl
  • Domain Name
    telemagazyn.pl
  • Favicon
  • Google Page Rank
    6
  • Alexa Rank
    #9388
  • Page Size
    98.6 KB
  • Ip Address
    195.8.99.6
  • Heading
    H1: 1, H2: 9, H3: 15, H4: 14, H5: 0, H6: 0
  • Images
    7 GIF, 12 JPG, 6 PNG

Website Meta Analysis

  • Title
    Program TV | Aktualny Program Telewizyjny: polskie i zagraniczne stacje
  • Meta Keyword
    program tv, program telewizyjny, recenzje filmów, plotki
  • Meta Description
    Aktualny program telewizyjny polskich i zagranicznych stacji. Program TV oraz recenzje filmów i plotki z przemysłu rozrywkowego. Sprawdź - Telemagazyn.pl

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    195.8.99.6
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from telemagazyn.pl.

HTML Analysis

  • date: Mon, 30 Sep 2013 00:38:00 GMT
  • server: Apache
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • vary: Accept-Encoding
  • content-encoding: gzip
  • connection: close
  • content-type: text/html; charset=iso-8859-2
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

DOMAIN NAME: telemagazyn.pl
registrant type: organization
nameservers: ns1.gratka.pl. [195.8.99.97]
ns2.gratka.pl. [213.192.69.59]
created: 2000.02.21 12:00:00
last modified: 2012.02.07 12:13:12
renewal date: 2013.02.20 13:00:00

no option

dnssec: Unsigned


REGISTRAR:
NetArt Spolka Akcyjna S.K.A.
ul. Cystersow 20A
31-553 Krakow
Polska/Poland
+48.801 33 22 33
+48.12 297 88 10
+48.12 297 88 08
email

WHOIS displays data with a delay not exceeding 15 minutes in relation to the .pl Registry system
Registrant data available at http://dns.pl/cgi-bin/en_whois.pl

DNS Analysis


DNS servers
ns2.gratka.pl [213.192.69.59]
ns1.gratka.pl [195.8.99.97]


DNS Records

Answer records
telemagazyn.pl SOA
server: ns1.gratka-technologie.pl
email: dns@gratka-technologie.pl
serial: 2012112900
refresh: 28800
retry: 7200
expire: 604800
minimum ttl: 1800
3600s
telemagazyn.pl NS  ns2.gratka-technologie.pl 3600s
telemagazyn.pl NS  ns1.gratka-technologie.pl 3600s
telemagazyn.pl MX
preference: 10
exchange: mail-02.gratka.pl
3600s
telemagazyn.pl TXT v=spf1 mx ptr ip4:195.8.99.0/24 ~all 3600s
telemagazyn.pl A 195.8.99.6 3600s
telemagazyn.pl 28 [16 bytes] 3600s

Authority records

Additional records
ns1.gratka-technologie.pl A 195.8.99.97 600s
ns2.gratka-technologie.pl A 213.192.69.59 600s
mail-02.gratka.pl A 195.8.99.56 600s

IP 195.8.99.6 Analysis

  • Country Code
    PL
  • Country Code3
    POL
  • Country Name
    Poland
  • City
    Gdansk
  • Continent Code
    EU
  • Latitude
    54.35
  • Longitude
    18.6667
  • No whois ip data for 195.8.99.6

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 32 Errors
  • 1 Warnings
Ratio Text/Html
  • 0.4709140450829824
Message Error
  • Warning Line 7, Column 77: NET-enabling start-tag requires SHORTTAG YES
    <link href="https://plus.google.com/111661564209643664698/" rel="publisher" />

    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 78: character data is not allowed here
    <link href="https://plus.google.com/111661564209643664698/" rel="publisher" />

    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.
  • Error Line 1077, Column 31: document type does not allow element "SCRIPT" here
    <script type="text/javascript">

    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 1236, Column 31: document type does not allow element "SCRIPT" here
    <script type="text/javascript">

    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 1312, Column 31: document type does not allow element "SCRIPT" here
    <script type="text/javascript">

    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 1423, Column 31: document type does not allow element "SCRIPT" here
    <script type="text/javascript">

    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 1876, Column 15: there is no attribute "SRC"
      <iframe src="http://telemagazyn.ipla.tv/nowosci/" width="965px" height="290px…

    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 1876, Column 59: there is no attribute "WIDTH"
    …//telemagazyn.ipla.tv/nowosci/" width="965px" height="290px" scrolling="no" fr…

    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 1876, Column 74: there is no attribute "HEIGHT"
    …pla.tv/nowosci/" width="965px" height="290px" scrolling="no" frameborder=0></i…

    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 1876, Column 92: there is no attribute "SCROLLING"
    …v/nowosci/" width="965px" height="290px" scrolling="no" frameborder=0></iframe>

    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 1876, Column 109: there is no attribute "FRAMEBORDER"
    …v/nowosci/" width="965px" height="290px" scrolling="no" frameborder=0></iframe>

    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 1876, Column 110: element "IFRAME" undefined
    …v/nowosci/" width="965px" height="290px" scrolling="no" frameborder=0></iframe>

    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 1987, Column 161: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …="Złote Maliny 2013 rozdane! "Zmierzch" dostał najwięcej"><img src="http://d.t…

    Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".

  • Error Line 1987, Column 289: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …="Złote Maliny 2013 rozdane! "Zmierzch" dostał najwięcej" height="100" width="…

    Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".

Visitor Analysis

Daily Visitor
  • 15.167 visits