Największy w Polsce zbiór darmowej muzyki, teksty piosenek i teledyski. Mp3 do pobierania i darmowe teledyski do oglądania. ...

teledyski.info
  • Domain Name
    teledyski.info
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #53539
  • Page Size
    42 KB
  • Ip Address
    46.4.106.116
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    45 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
    Teledyski.info - Teledyski, Teksty Piosenek, Videoklipy
  • Meta Keyword
    Teledyski, videoklipy, teksty piosenek, darmowe mp3, muzyka
  • Meta Description
    Największy w Polsce zbiór darmowej muzyki, teksty piosenek i teledyski. Mp3 do pobierania i darmowe teledyski do oglądania.

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    46.4.106.116
  • Domain Age
    7 Years, 1 Months, 20 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from teledyski.info.

HTML Analysis

  • date: Tue, 19 Feb 2013 03:42:02 GMT
  • server: Apache
  • content-encoding: gzip
  • vary: Accept-Encoding
  • content-length: 6316
  • connection: close
  • content-type: text/html
  • age: 25
  • x-google-cache-control: remote-cache-hit
  • via: HTTP/1.1 GWA (remote cache hit)
Access to INFO WHOIS information is provided to assist persons in
determining the contents of a domain name registration record in the
Afilias registry database. The data in this record is provided by
Afilias Limited for informational purposes only, and Afilias does not
guarantee its accuracy. This service is intended only for query-based
access. You agree that you will use this data only for lawful purposes
and that, under no circumstances will you use this data to: (a) allow,
enable, or otherwise support the transmission by e-mail, telephone, or
facsimile of mass unsolicited, commercial advertising or solicitations
to entities other than the data recipient's own existing customers; or
(b) enable high volume, automated, electronic processes that send
queries or data to the systems of Registry Operator, a Registrar, or
Afilias except as reasonably necessary to register domain names or
modify existing registrations. All rights reserved. Afilias reserves
the right to modify these terms at any time. By submitting this query,
you agree to abide by this policy.

Domain ID:D11791065-LRMS
Domain Name:TELEDYSKI.INFO
Created On:06-Jan-2006 09:34:08 UTC
Last Updated On:31-Aug-2012 19:02:54 UTC
Expiration Date:06-Jan-2013 09:34:08 UTC
Sponsoring Registrar:Domain.com,LLC (R656-LRMS)
Status:CLIENT TRANSFER PROHIBITED
Status:CLIENT UPDATE PROHIBITED
Registrant ID:tu9IsZ5jLAi5vIQS
Registrant Name:Privacy Group
Registrant Organization:Domain Privacy Group
Registrant Street1:70 Blanchard Road
Registrant Street2:
Registrant Street3:
Registrant City:Burlington
Registrant State/Province:MA
Registrant Postal Code:01803
Registrant Country:US
Registrant Phone:+1.6027165339
Registrant Phone Ext.:
Registrant FAX:
Registrant FAX Ext.:
Registrant Email: email
Admin ID:tu9IsZ5jLAi5vIQS
Admin Name:Privacy Group
Admin Organization:Domain Privacy Group
Admin Street1:70 Blanchard Road
Admin Street2:
Admin Street3:
Admin City:Burlington
Admin State/Province:MA
Admin Postal Code:01803
Admin Country:US
Admin Phone:+1.6027165339
Admin Phone Ext.:
Admin FAX:
Admin FAX Ext.:
Admin Email: email
Billing ID:tu9IsZ5jLAi5vIQS
Billing Name:Privacy Group
Billing Organization:Domain Privacy Group
Billing Street1:70 Blanchard Road
Billing Street2:
Billing Street3:
Billing City:Burlington
Billing State/Province:MA
Billing Postal Code:01803
Billing Country:US
Billing Phone:+1.6027165339
Billing Phone Ext.:
Billing FAX:
Billing FAX Ext.:
Billing Email: email
Tech ID:tu9IsZ5jLAi5vIQS
Tech Name:Privacy Group
Tech Organization:Domain Privacy Group
Tech Street1:70 Blanchard Road
Tech Street2:
Tech Street3:
Tech City:Burlington
Tech State/Province:MA
Tech Postal Code:01803
Tech Country:US
Tech Phone:+1.6027165339
Tech Phone Ext.:
Tech FAX:
Tech FAX Ext.:
Tech Email: email
Name Server:NS1.AFRAID.ORG
Name Server:NS2.AFRAID.ORG
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:

DNS Analysis


DNS servers
ns1.afraid.org [50.23.197.94]
ns2.afraid.org [174.37.196.55]


DNS Records

Answer records
teledyski.info MX
preference: 10
exchange: mail.teledyski.info
3600s
teledyski.info A 46.4.106.116 3600s
teledyski.info TXT v=spf1 a mx ip4:46.4.106.116 ~all 3600s
teledyski.info SOA
server: ns1.afraid.org
email: dnsadmin@afraid.org
serial: 1302020001
refresh: 86400
retry: 7200
expire: 2419200
minimum ttl: 3600
3600s
teledyski.info NS  ns2.afraid.org 3600s
teledyski.info NS  ns1.afraid.org 3600s
teledyski.info NS  ns3.afraid.org 3600s
teledyski.info NS  ns4.afraid.org 3600s

Authority records

Additional records
mail.teledyski.info A 46.4.106.116 3600s
ns1.afraid.org A 50.23.197.95 300s
ns1.afraid.org 28 [16 bytes] 300s
ns2.afraid.org A 174.37.196.55 300s
ns3.afraid.org A 72.20.15.62 300s
ns4.afraid.org A 174.128.246.102 300s

IP 46.4.106.116 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 54 Errors
  • 14 Warnings
Ratio Text/Html
  • 0.8047054990575039
Message Error
  • Error Line 22, Column 110: end tag for "link" omitted, but OMITTAG NO was specified
    …="http://static-h2.teledyski.info/teledyski/teledyski.ico" type="image/x-icon">

    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 22, Column 1: start tag was here
    <link rel="shortcut icon" href="http://static-h2.teledyski.info/teledyski/teled…
  • Error Line 190, Column 87: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …bmit2" type="button" value="" onclick=location.href="http://teledyski.info/ind…
  • Error Line 190, Column 100: an attribute specification must start with a name or name token
    …button" value="" onclick=location.href="http://teledyski.info/index.html?file=…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 190, Column 101: end tag for "input" omitted, but OMITTAG NO was specified
    …utton" value="" onclick=location.href="http://teledyski.info/index.html?file=t…

    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 190, Column 9: start tag was here
            <input name="formb_submit2" id="formb_submit2" type="button" value="" o…
  • Error Line 201, Column 8: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <center>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 222, Column 44: there is no attribute "onMouseOver"
    …   <div class="mdel_info" onMouseOver="style.background='#EDEDED';" onMouseOut…

    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 222, Column 85: there is no attribute "onMouseOut"
    …useOver="style.background='#EDEDED';" onMouseOut="style.background='#f5f5f5';">

    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 223, Column 251: required attribute "alt" not specified
    …ki.info/cache/s.php?s=http://teledyski.info/obraz.php?id=9310" /></a></p></div>

    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 241, Column 251: required attribute "alt" not specified
    …ki.info/cache/s.php?s=http://teledyski.info/obraz.php?id=9316" /></a></p></div>

    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 259, Column 251: required attribute "alt" not specified
    …ki.info/cache/s.php?s=http://teledyski.info/obraz.php?id=9315" /></a></p></div>

    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 277, Column 251: required attribute "alt" not specified
    …ki.info/cache/s.php?s=http://teledyski.info/obraz.php?id=9314" /></a></p></div>

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

  • Warning Line 297, Column 80: cannot generate system identifier for general entity "t"
    …cript" src="http://teledyski.info/reklama_js2.php?id=2&t=1336624119a"></script>

    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 297, Column 80: general entity "t" not defined and no default entity
    …cript" src="http://teledyski.info/reklama_js2.php?id=2&t=1336624119a"></script>

    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.

  • Warning Line 297, Column 81: reference not terminated by REFC delimiter
    …cript" src="http://teledyski.info/reklama_js2.php?id=2&t=1336624119a"></script>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 297, Column 81: reference to external entity in attribute value
    …cript" src="http://teledyski.info/reklama_js2.php?id=2&t=1336624119a"></script>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 297, Column 81: reference to entity "t" for which no system identifier could be generated
    …cript" src="http://teledyski.info/reklama_js2.php?id=2&t=1336624119a"></script>

    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 297, Column 79: entity was defined here
    …cript" src="http://teledyski.info/reklama_js2.php?id=2&t=1336624119a"></script>
  • Error Line 305, Column 251: required attribute "alt" not specified
    …ki.info/cache/s.php?s=http://teledyski.info/obraz.php?id=9313" /></a></p></div>

    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 323, Column 251: required attribute "alt" not specified
    …ki.info/cache/s.php?s=http://teledyski.info/obraz.php?id=9312" /></a></p></div>

    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 341, Column 251: required attribute "alt" not specified
    …ki.info/cache/s.php?s=http://teledyski.info/obraz.php?id=9311" /></a></p></div>

    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 359, Column 251: required attribute "alt" not specified
    …ki.info/cache/s.php?s=http://teledyski.info/obraz.php?id=9318" /></a></p></div>

    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 377, Column 251: required attribute "alt" not specified
    …ki.info/cache/s.php?s=http://teledyski.info/obraz.php?id=9303" /></a></p></div>

    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 395, Column 251: required attribute "alt" not specified
    …ki.info/cache/s.php?s=http://teledyski.info/obraz.php?id=9309" /></a></p></div>

    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 413, Column 251: required attribute "alt" not specified
    …ki.info/cache/s.php?s=http://teledyski.info/obraz.php?id=9308" /></a></p></div>

    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 431, Column 251: required attribute "alt" not specified
    …ki.info/cache/s.php?s=http://teledyski.info/obraz.php?id=9307" /></a></p></div>

    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 449, Column 251: required attribute "alt" not specified
    …ki.info/cache/s.php?s=http://teledyski.info/obraz.php?id=9306" /></a></p></div>

    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 467, Column 251: required attribute "alt" not specified
    …ki.info/cache/s.php?s=http://teledyski.info/obraz.php?id=9305" /></a></p></div>

    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 485, Column 251: required attribute "alt" not specified
    …ki.info/cache/s.php?s=http://teledyski.info/obraz.php?id=9304" /></a></p></div>

    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 520, Column 253: required attribute "alt" not specified
    …eledyski.info/cache/s.php?s=http://teledyski.info/obraz.php?id=9310" /></a></p>

    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 535, Column 29: there is no attribute "FRAMEBORDER"
            <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=1…

    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 535, Column 29: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
            <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=1…
  • Error Line 535, Column 43: there is no attribute "MARGINWIDTH"
    …    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=160 …

    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 535, Column 43: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=160 …
  • Error Line 535, Column 58: there is no attribute "MARGINHEIGHT"
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=160 HEIGHT=600 SRC=…

    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 535, Column 58: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=160 HEIGHT=600 SRC=…
  • Error Line 535, Column 70: there is no attribute "SCROLLING"
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=160 HEIGHT=600 SRC="http://ad.y…

    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 535, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=160 HEIGHT=600 SRC="http://ad.y…
  • Error Line 535, Column 79: there is no attribute "WIDTH"
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=160 HEIGHT=600 SRC="http://ad.yieldmanag…

    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 535, Column 79: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=160 HEIGHT=600 SRC="http://ad.yieldmanag…
  • Error Line 535, Column 90: there is no attribute "HEIGHT"
    …EIGHT=0 SCROLLING=NO WIDTH=160 HEIGHT=600 SRC="http://ad.yieldmanager.com/st?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 535, Column 90: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …EIGHT=0 SCROLLING=NO WIDTH=160 HEIGHT=600 SRC="http://ad.yieldmanager.com/st?a…
  • Error Line 535, Column 98: there is no attribute "SRC"
    …SCROLLING=NO WIDTH=160 HEIGHT=600 SRC="http://ad.yieldmanager.com/st?ad_type=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.

  • Warning Line 535, Column 144: cannot generate system identifier for general entity "ad_size"
    …ad.yieldmanager.com/st?ad_type=iframe&ad_size=160x600&section=4068003&pub_url=…

    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 535, Column 144: general entity "ad_size" not defined and no default entity
    …ad.yieldmanager.com/st?ad_type=iframe&ad_size=160x600&section=4068003&pub_url=…

    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.

  • Warning Line 535, Column 151: reference not terminated by REFC delimiter
    …dmanager.com/st?ad_type=iframe&ad_size=160x600&section=4068003&pub_url=${PUB_U…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 535, Column 151: reference to external entity in attribute value
    …dmanager.com/st?ad_type=iframe&ad_size=160x600&section=4068003&pub_url=${PUB_U…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 535, Column 151: reference to entity "ad_size" for which no system identifier could be generated
    …dmanager.com/st?ad_type=iframe&ad_size=160x600&section=4068003&pub_url=${PUB_U…

    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 535, Column 143: entity was defined here
    …/ad.yieldmanager.com/st?ad_type=iframe&ad_size=160x600&section=4068003&pub_url…
  • Warning Line 535, Column 160: cannot generate system identifier for general entity "section"
    …com/st?ad_type=iframe&ad_size=160x600&section=4068003&pub_url=${PUB_URL}"></IF…

    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 535, Column 160: general entity "section" not defined and no default entity
    …com/st?ad_type=iframe&ad_size=160x600&section=4068003&pub_url=${PUB_URL}"></IF…

    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.

  • Warning Line 535, Column 167: reference not terminated by REFC delimiter
    …st?ad_type=iframe&ad_size=160x600&section=4068003&pub_url=${PUB_URL}"></IFRAME>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 535, Column 167: reference to external entity in attribute value
    …st?ad_type=iframe&ad_size=160x600&section=4068003&pub_url=${PUB_URL}"></IFRAME>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 535, Column 167: reference to entity "section" for which no system identifier could be generated
    …st?ad_type=iframe&ad_size=160x600&section=4068003&pub_url=${PUB_URL}"></IFRAME>

    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 535, Column 159: entity was defined here
    ….com/st?ad_type=iframe&ad_size=160x600&section=4068003&pub_url=${PUB_URL}"></I…
  • Warning Line 535, Column 176: cannot generate system identifier for general entity "pub_url"
    …st?ad_type=iframe&ad_size=160x600&section=4068003&pub_url=${PUB_URL}"></IFRAME>

    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 535, Column 176: general entity "pub_url" not defined and no default entity
    …st?ad_type=iframe&ad_size=160x600&section=4068003&pub_url=${PUB_URL}"></IFRAME>

    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.

  • Warning Line 535, Column 183: reference not terminated by REFC delimiter
    …st?ad_type=iframe&ad_size=160x600&section=4068003&pub_url=${PUB_URL}"></IFRAME>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 535, Column 183: reference to external entity in attribute value
    …st?ad_type=iframe&ad_size=160x600&section=4068003&pub_url=${PUB_URL}"></IFRAME>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 535, Column 183: reference to entity "pub_url" for which no system identifier could be generated
    …st?ad_type=iframe&ad_size=160x600&section=4068003&pub_url=${PUB_URL}"></IFRAME>

    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 535, Column 175: entity was defined here
    …st?ad_type=iframe&ad_size=160x600&section=4068003&pub_url=${PUB_URL}"></IFRAME>
  • Error Line 535, Column 195: element "IFRAME" undefined
    …st?ad_type=iframe&ad_size=160x600&section=4068003&pub_url=${PUB_URL}"></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 540, Column 253: required attribute "alt" not specified
    …eledyski.info/cache/s.php?s=http://teledyski.info/obraz.php?id=9316" /></a></p>

    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 556, Column 253: required attribute "alt" not specified
    …eledyski.info/cache/s.php?s=http://teledyski.info/obraz.php?id=9315" /></a></p>

    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 572, Column 253: required attribute "alt" not specified
    …eledyski.info/cache/s.php?s=http://teledyski.info/obraz.php?id=9314" /></a></p>

    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 588, Column 253: required attribute "alt" not specified
    …eledyski.info/cache/s.php?s=http://teledyski.info/obraz.php?id=9313" /></a></p>

    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 604, Column 253: required attribute "alt" not specified
    …eledyski.info/cache/s.php?s=http://teledyski.info/obraz.php?id=9312" /></a></p>

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

  • Warning Line 627, Column 81: reference not terminated by REFC delimiter
    …cript" src="http://teledyski.info/reklama_js2.php?id=1&t=1336624119a"></script>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 627, Column 81: reference to external entity in attribute value
    …cript" src="http://teledyski.info/reklama_js2.php?id=1&t=1336624119a"></script>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 627, Column 81: reference to entity "t" for which no system identifier could be generated
    …cript" src="http://teledyski.info/reklama_js2.php?id=1&t=1336624119a"></script>

    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 297, Column 79: entity was defined here
    …cript" src="http://teledyski.info/reklama_js2.php?id=2&t=1336624119a"></script>
  • Error Line 646, Column 394: there is no attribute "allowTransparency"
    … overflow:hidden; width:120px; height:21px;" allowTransparency="true"></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 685, Column 80: document type does not allow element "script" here
    …pe="text/javascript" src="http://stats.teledyski.info/vip.php?user=1"></script>

    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 686, Column 74: document type does not allow element "script" here
    …ipt type="text/javascript" src="http://twoja-strona.net/uptime/t.php"></script>

    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
  • 2.917 visits
Daily Visitor