Самі оперативні новини України, новини світу від інформаційного агентства Уніан ...

unian.ua
  • Domain Name
    unian.ua
  • Favicon
  • Google Page Rank
    6
  • Alexa Rank
    #66320
  • Page Size
    72.3 KB
  • Ip Address
    217.20.163.85
  • Heading
    H1: 1, H2: 2, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    2 GIF, 21 JPG, 1 PNG

Website Meta Analysis

  • Title
    Новини УНІАН. Останні новини України та світу
  • Meta Keyword
    Новини, Уніан, інформаційне агентство, новини України, економіка, культура, прес-конференції, новини світу
  • Meta Description
    Самі оперативні новини України, новини світу від інформаційного агентства Уніан

Technical Analysis

  • Webserver
    lighttpd/1.4.25
  • Ip Address
    217.20.163.85
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from unian.ua.

HTML Analysis

  • x-powered-by: PHP/5.3.0
  • content-type: text/html; charset=windows-1251
  • date: Sun, 29 Sep 2013 04:59:59 GMT
  • server: lighttpd/1.4.25
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
% request from 149.47.7.177
% This is the Ukrainian Whois query server #F.
% The Whois is subject to Terms of use
% See https://hostmaster.ua/services/
%


% % .UA whois
% Domain Record:
% =============
domain: unian.ua
admin-c: UNAN1-UANIC
tech-c: WNET-UANIC
status: OK-UNTIL 20130223141721
dom-public: NO
license: 43469
nserver: ns2.wnet.ua
nserver: ns.wnet.ua
mnt-by: UARR189-UANIC (ua.wnet-mnt)
remark: UNIAN
created: 0-UANIC 20060223141721
changed: UARR189-UANIC 20120118131720
source: UANIC


% Administrative Contact:
% ======================
nic-handle: UNAN1-UANIC
organization: Ukrainskoe nezavisimoe agenstvo novostey
address: Ukraine, Kyiv, 01001
address: Khreshchatyk str. 4
fax-no: +380442780007
phone: +380442780007
e-mail: email
org-id: N/A
mnt-by: NONE
changed: UARR39-UANIC 20061205021331
source: UANIC

% Technical Contact:
% =================
nic-handle: WNET-UANIC
organization: WNET ISP
address: Ukraine, Kyiv
address: Esplanadnaya 20 apt 802
phone: +38044 2359246
e-mail: email
org-id: N/A
mnt-by: NONE
changed: WNET-UANIC 20110309161324
source: UANIC


% % .UA whois

% Last update of whois database: 18 Sep 2012 08:19:11 +0300 (EEST)

% Query time: 65 msec

DNS Analysis


DNS servers
ns.wnet.ua [217.20.160.161]
ns2.wnet.ua [217.20.160.162]


DNS Records

Answer records
unian.ua SOA
server: ns2.wnet.ua
email: hostmaster@wnet.ua
serial: 2012080202
refresh: 3600
retry: 900
expire: 3600000
minimum ttl: 3600
86400s
unian.ua NS  ns.wnet.ua 86400s
unian.ua NS  ns2.wnet.ua 86400s
unian.ua A 217.20.163.85 86400s
unian.ua MX
preference: 10
exchange: mail.unian.ua
86400s

Authority records

Additional records
ns.wnet.ua A 217.20.160.161 86400s
ns.wnet.ua 28 [16 bytes] 86400s
ns2.wnet.ua A 217.20.160.162 86400s
ns2.wnet.ua 28 [16 bytes] 86400s
mail.unian.ua A 195.137.240.8 86400s

IP 217.20.163.85 Analysis

  • Country Code
    UA
  • Country Code3
    UKR
  • Country Name
    Ukraine
  • City
    EU
  • Continent Code
    49° North
  • Latitude
    32.
  • Longitude
  • No whois ip data for 217.20.163.85

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 121 Errors
  • 23 Warnings
Ratio Text/Html
  • 0.558583621434745
Message Error
  • Warning Line 13, Column 61: NET-enabling start-tag requires SHORTTAG YES
    <meta name='yandex-verification' content='5cffe4e59b5fe325' />

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

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

    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 20, 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 21, 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 67, Column 32: element "NOINDEX" undefined
    	<td nowrap><div>&nbsp;<noindex><a  class=menu id="menu_2" href="http://photo.u…

    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 88, Column 37: there is no attribute "BACKGROUND"
    			<td  nowrap height=25 background="http://images.unian.net/img/bg2.gif"><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 88, Column 113: element "NOINDEX" undefined
    …<div style="padding-left:2px"><noindex><a  class=sub_menu id="menu_12" href="h…

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

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

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

  • Error Line 175, Column 65: end tag for element "DIV" which is not open
          $('#top_banner_video').html('<div id="alt_fullvideo"></div>');

    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 179, Column 68: end tag for element "DIV" which is not open
          $('#top_banner_video').html('<div id="Fullvideo_banner"></div>');

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

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

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

  • Warning Line 214, Column 121: NET-enabling start-tag requires SHORTTAG YES
    …2012_10/1349429127.jpg' title='На кінець року держборг зросте до 30,6% ВВП'  />

    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 214, Column 121: required attribute "ALT" not specified
    …2012_10/1349429127.jpg' title='На кінець року держборг зросте до 30,6% ВВП'  />

    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 223, Column 71: there is no attribute "ALIGN"
    …'top' width='33%'><a class='td' align='center' href='http://www.unian.ua/news/…

    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 240, Column 10: value of attribute "ID" invalid: "4" cannot start a name
    <div id="468x60_1"></div>

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 343, Column 12: required attribute "TYPE" not specified
    					<style>

    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 343, Column 12: document type does not allow element "STYLE" here
    					<style>

    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 413, Column 40: there is no attribute "DATA-HREF"
    …			<div class="fb-like-box" data-href="http://www.facebook.com/UNIAN.net" data…

    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 413, Column 87: there is no attribute "DATA-WIDTH"
    …ww.facebook.com/UNIAN.net" data-width="300" style="border:height:260px; width:…

    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 413, Column 181: there is no attribute "DATA-SHOW-FACES"
    …idden;margin:0px 3px" data-show-faces="true" data-stream="false" data-header="…

    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 413, Column 200: there is no attribute "DATA-STREAM"
    …n:0px 3px" data-show-faces="true" data-stream="false" data-header="true"></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 413, Column 220: there is no attribute "DATA-HEADER"
    …n:0px 3px" data-show-faces="true" data-stream="false" data-header="true"></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 420, Column 20: there is no attribute "WIDTH"
    					<g:plus width="300" href="https://plus.google.com/106975155676998607780" r…

    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 420, Column 31: there is no attribute "HREF"
    					<g:plus width="300" href="https://plus.google.com/106975155676998607780" r…

    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 420, Column 83: there is no attribute "REL"
    … href="https://plus.google.com/106975155676998607780" rel="publisher"></g:plus>

    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 420, Column 94: element "G:PLUS" undefined
    … href="https://plus.google.com/106975155676998607780" rel="publisher"></g:plus>

    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 468, Column 11: required attribute "TYPE" not specified
    				<STYLE>

    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 468, Column 11: document type does not allow element "STYLE" here
    				<STYLE>

    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 487, Column 9: required attribute "TYPE" not specified
    	<script>

    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 533, Column 14: element "NOINDEX" undefined
    					<noindex>

    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).
  • Warning Line 534, Column 423: NET-enabling start-tag requires SHORTTAG YES
    …tp://informers.sinoptik.ua/img/t.gif" /></a> <span id="siHeader"></span></div>…

    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 547, Column 41: end tag for element "IFRAME" which is not open
    + ' marginheight=0 scrolling=no></iframe>');

    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.

  • Warning Line 550, Column 60: cannot generate system identifier for general entity "sz"
    …river.ru/cgi-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" ta…

    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 550, Column 60: general entity "sz" not defined and no default entity
    …river.ru/cgi-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" ta…

    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 550, Column 62: reference to entity "sz" for which no system identifier could be generated
    …ver.ru/cgi-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" targ…

    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 550, Column 59: entity was defined here
    …driver.ru/cgi-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" t…
  • Warning Line 550, Column 68: cannot generate system identifier for general entity "bn"
    …/cgi-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" target=_bl…

    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 550, Column 68: general entity "bn" not defined and no default entity
    …/cgi-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" target=_bl…

    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 550, Column 70: reference to entity "bn" for which no system identifier could be generated
    …gi-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" target=_blan…

    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 550, Column 67: entity was defined here
    …u/cgi-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" target=_b…
  • Warning Line 550, Column 73: cannot generate system identifier for general entity "bt"
    …i-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" target=_blank>

    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 550, Column 73: general entity "bt" not defined and no default entity
    …i-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" target=_blank>

    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 550, Column 75: reference to entity "bt" for which no system identifier could be generated
    …i-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" target=_blank>

    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 550, Column 72: entity was defined here
    …i-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" target=_blank>
  • Warning Line 550, Column 78: cannot generate system identifier for general entity "pz"
    …i-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" target=_blank>

    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 550, Column 78: general entity "pz" not defined and no default entity
    …i-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" target=_blank>

    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 550, Column 80: reference to entity "pz" for which no system identifier could be generated
    …i-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" target=_blank>

    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 550, Column 77: entity was defined here
    …i-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" target=_blank>
  • Warning Line 550, Column 83: cannot generate system identifier for general entity "rnd"
    …i-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" target=_blank>

    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 550, Column 83: general entity "rnd" not defined and no default entity
    …i-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" target=_blank>

    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 550, Column 86: reference to entity "rnd" for which no system identifier could be generated
    …i-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" target=_blank>

    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 550, Column 82: entity was defined here
    …i-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" target=_blank>
  • Error Line 551, Column 61: reference to entity "sz" for which no system identifier could be generated
    …river.ru/cgi-bin/rle.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" alt=…

    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 550, Column 59: entity was defined here
    …driver.ru/cgi-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" t…
  • Error Line 551, Column 69: reference to entity "bn" for which no system identifier could be generated
    …/cgi-bin/rle.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" alt="-AdRive…

    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 550, Column 67: entity was defined here
    …u/cgi-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" target=_b…
  • Error Line 551, Column 74: reference to entity "bt" for which no system identifier could be generated
    …bin/rle.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" alt="-AdRiver-" b…

    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 550, Column 72: entity was defined here
    …i-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" target=_blank>
  • Error Line 551, Column 79: reference to entity "pz" for which no system identifier could be generated
    …le.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" alt="-AdRiver-" border…

    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 550, Column 77: entity was defined here
    …i-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" target=_blank>
  • Error Line 551, Column 85: reference to entity "rnd" for which no system identifier could be generated
    …?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" alt="-AdRiver-" border=0 wid…

    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 550, Column 82: entity was defined here
    …i-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" target=_blank>
  • Error Line 666, Column 29: document type does not allow element "H2" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    				<a href='/theme/792'><h2>Саміт Україна-ЄС</h2></a>

    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 682, Column 9: end tag for "UL" omitted, but its declaration does not permit this
    				</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 668, Column 5: start tag was here
    				<ul>
  • Error Line 682, Column 9: end tag for "DIV" omitted, but its declaration does not permit this
    				</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 667, Column 5: start tag was here
    				<div class='newsItem'>
  • Error Line 685, Column 29: document type does not allow element "H2" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    				<a href='/theme/711'><h2>Ув`язнення Тимошенко</h2></a>

    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 701, Column 9: end tag for "UL" omitted, but its declaration does not permit this
    				</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 687, Column 5: start tag was here
    				<ul>
  • Error Line 701, Column 9: end tag for "DIV" omitted, but its declaration does not permit this
    				</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 686, Column 5: start tag was here
    				<div class='newsItem'>
  • Error Line 704, Column 29: document type does not allow element "H2" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    				<a href='/theme/715'><h2>Вирок Луценку</h2></a>

    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 720, Column 9: end tag for "UL" omitted, but its declaration does not permit this
    				</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 706, Column 5: start tag was here
    				<ul>
  • Error Line 720, Column 9: end tag for "DIV" omitted, but its declaration does not permit this
    				</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 705, Column 5: start tag was here
    				<div class='newsItem'>
  • Error Line 728, Column 48: element "NOINDEX" undefined
    	<tr><td bgcolor="#ffffff" colspan="2"><noindex>

    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 816, Column 41: end tag for element "IFRAME" which is not open
    + ' marginheight=0 scrolling=no></iframe>');

    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 819, Column 62: reference to entity "sz" for which no system identifier could be generated
    …ver.ru/cgi-bin/click.cgi?sid=142102&sz=main&bn=3&bt=1&pz=3&rnd=1575298973" tar…

    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 550, Column 59: entity was defined here
    …driver.ru/cgi-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" t…
  • Error Line 819, Column 70: reference to entity "bn" for which no system identifier could be generated
    …gi-bin/click.cgi?sid=142102&sz=main&bn=3&bt=1&pz=3&rnd=1575298973" target=_bla…

    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 550, Column 67: entity was defined here
    …u/cgi-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" target=_b…
  • Error Line 819, Column 75: reference to entity "bt" for which no system identifier could be generated
    …-bin/click.cgi?sid=142102&sz=main&bn=3&bt=1&pz=3&rnd=1575298973" target=_blank>

    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 550, Column 72: entity was defined here
    …i-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" target=_blank>
  • Error Line 819, Column 80: reference to entity "pz" for which no system identifier could be generated
    …-bin/click.cgi?sid=142102&sz=main&bn=3&bt=1&pz=3&rnd=1575298973" target=_blank>

    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 550, Column 77: entity was defined here
    …i-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" target=_blank>
  • Error Line 819, Column 86: reference to entity "rnd" for which no system identifier could be generated
    …-bin/click.cgi?sid=142102&sz=main&bn=3&bt=1&pz=3&rnd=1575298973" target=_blank>

    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 550, Column 82: entity was defined here
    …i-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" target=_blank>
  • Error Line 820, Column 61: reference to entity "sz" for which no system identifier could be generated
    …river.ru/cgi-bin/rle.cgi?sid=142102&sz=main&bn=3&bt=1&pz=3&rnd=1575298973" alt…

    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 550, Column 59: entity was defined here
    …driver.ru/cgi-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" t…
  • Error Line 820, Column 69: reference to entity "bn" for which no system identifier could be generated
    …/cgi-bin/rle.cgi?sid=142102&sz=main&bn=3&bt=1&pz=3&rnd=1575298973" alt="-AdRiv…

    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 550, Column 67: entity was defined here
    …u/cgi-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" target=_b…
  • Error Line 820, Column 74: reference to entity "bt" for which no system identifier could be generated
    …bin/rle.cgi?sid=142102&sz=main&bn=3&bt=1&pz=3&rnd=1575298973" alt="-AdRiver-" …

    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 550, Column 72: entity was defined here
    …i-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" target=_blank>
  • Error Line 820, Column 79: reference to entity "pz" for which no system identifier could be generated
    …le.cgi?sid=142102&sz=main&bn=3&bt=1&pz=3&rnd=1575298973" alt="-AdRiver-" borde…

    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 550, Column 77: entity was defined here
    …i-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" target=_blank>
  • Error Line 820, Column 85: reference to entity "rnd" for which no system identifier could be generated
    …?sid=142102&sz=main&bn=3&bt=1&pz=3&rnd=1575298973" alt="-AdRiver-" border=0 wi…

    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 550, Column 82: entity was defined here
    …i-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" target=_blank>
  • Error Line 834, Column 41: end tag for element "IFRAME" which is not open
    + ' marginheight=0 scrolling=no></iframe>');

    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 837, Column 62: reference to entity "sz" for which no system identifier could be generated
    …ver.ru/cgi-bin/click.cgi?sid=142102&sz=main&bn=3&bt=1&pz=3&rnd=1575298973" tar…

    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 550, Column 59: entity was defined here
    …driver.ru/cgi-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" t…
  • Error Line 837, Column 70: reference to entity "bn" for which no system identifier could be generated
    …gi-bin/click.cgi?sid=142102&sz=main&bn=3&bt=1&pz=3&rnd=1575298973" target=_bla…

    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 550, Column 67: entity was defined here
    …u/cgi-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" target=_b…
  • Error Line 837, Column 75: reference to entity "bt" for which no system identifier could be generated
    …-bin/click.cgi?sid=142102&sz=main&bn=3&bt=1&pz=3&rnd=1575298973" target=_blank>

    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 550, Column 72: entity was defined here
    …i-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" target=_blank>
  • Error Line 837, Column 80: reference to entity "pz" for which no system identifier could be generated
    …-bin/click.cgi?sid=142102&sz=main&bn=3&bt=1&pz=3&rnd=1575298973" target=_blank>

    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 550, Column 77: entity was defined here
    …i-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" target=_blank>
  • Error Line 837, Column 86: reference to entity "rnd" for which no system identifier could be generated
    …-bin/click.cgi?sid=142102&sz=main&bn=3&bt=1&pz=3&rnd=1575298973" target=_blank>

    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 550, Column 82: entity was defined here
    …i-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" target=_blank>
  • Error Line 838, Column 61: reference to entity "sz" for which no system identifier could be generated
    …river.ru/cgi-bin/rle.cgi?sid=142102&sz=main&bn=3&bt=1&pz=3&rnd=1575298973" alt…

    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 550, Column 59: entity was defined here
    …driver.ru/cgi-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" t…
  • Error Line 838, Column 69: reference to entity "bn" for which no system identifier could be generated
    …/cgi-bin/rle.cgi?sid=142102&sz=main&bn=3&bt=1&pz=3&rnd=1575298973" alt="-AdRiv…

    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 550, Column 67: entity was defined here
    …u/cgi-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" target=_b…
  • Error Line 838, Column 74: reference to entity "bt" for which no system identifier could be generated
    …bin/rle.cgi?sid=142102&sz=main&bn=3&bt=1&pz=3&rnd=1575298973" alt="-AdRiver-" …

    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 550, Column 72: entity was defined here
    …i-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" target=_blank>
  • Error Line 838, Column 79: reference to entity "pz" for which no system identifier could be generated
    …le.cgi?sid=142102&sz=main&bn=3&bt=1&pz=3&rnd=1575298973" alt="-AdRiver-" borde…

    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 550, Column 77: entity was defined here
    …i-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" target=_blank>
  • Error Line 838, Column 85: reference to entity "rnd" for which no system identifier could be generated
    …?sid=142102&sz=main&bn=3&bt=1&pz=3&rnd=1575298973" alt="-AdRiver-" border=0 wi…

    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 550, Column 82: entity was defined here
    …i-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" target=_blank>
  • Error Line 854, Column 10: element "NOINDEX" undefined
     <noindex>

    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 912, Column 9: element "NOINDEX" undefined
    <noindex>

    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).
  • Warning Line 929, Column 49: NET-enabling start-tag requires SHORTTAG YES
    style="position:absolute; left:-9999px;" alt="" /></div></noscript>

    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 942, Column 117: delimiter "'" invalid: only S separators and TAGC allowed here
    …nguage="javascript" src="http://c.bigmir.net/?'+bs.join('&')+'"></sc'+'ript>');
  • Error Line 942, Column 117: end tag for element "SC" which is not open
    …nguage="javascript" src="http://c.bigmir.net/?'+bs.join('&')+'"></sc'+'ript>');

    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.

  • Warning Line 945, Column 50: cannot generate system identifier for general entity "s12815"
    …<img src="http://c.bigmir.net/?v12815&s12815&t6" width="0" height="0" alt="" t…

    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 945, Column 50: general entity "s12815" not defined and no default entity
    …<img src="http://c.bigmir.net/?v12815&s12815&t6" width="0" height="0" alt="" t…

    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 945, Column 56: reference to entity "s12815" for which no system identifier could be generated
    …rc="http://c.bigmir.net/?v12815&s12815&t6" width="0" height="0" alt="" title="…

    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 945, Column 49: entity was defined here
    …><img src="http://c.bigmir.net/?v12815&s12815&t6" width="0" height="0" alt="" …
  • Warning Line 945, Column 57: cannot generate system identifier for general entity "t6"
    …c="http://c.bigmir.net/?v12815&s12815&t6" width="0" height="0" alt="" title=""…

    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 945, Column 57: general entity "t6" not defined and no default entity
    …c="http://c.bigmir.net/?v12815&s12815&t6" width="0" height="0" alt="" title=""…

    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 945, Column 59: reference to entity "t6" for which no system identifier could be generated
    …"http://c.bigmir.net/?v12815&s12815&t6" width="0" height="0" alt="" title="" b…

    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 945, Column 56: entity was defined here
    …rc="http://c.bigmir.net/?v12815&s12815&t6" width="0" height="0" alt="" title="…
  • Warning Line 945, Column 109: NET-enabling start-tag requires SHORTTAG YES
    …v12815&s12815&t6" width="0" height="0" alt="" title="" border="0" /></noscript>

    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 951, Column 294: end tag for element "DIV" which is not open
    ….gif\') no-repeat bottom;">&nbsp;</div><div style="font:10px Tahoma;background…

    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 951, Column 586: end tag for "SCRIPT" omitted, but its declaration does not permit this
    …ir<span style="color:#ff0000;">)</span>net</a></div><div style="margin-top:3px…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 949, Column 2: start tag was here
    	<script type="text/javascript" language="javascript"><!--
  • Error Line 951, Column 593: end tag for element "A" which is not open
    … style="color:#ff0000;">)</span>net</a></div><div style="margin-top:3px;paddin…

    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 951, Column 599: end tag for element "DIV" which is not open
    …="color:#ff0000;">)</span>net</a></div><div style="margin-top:3px;padding: 0px…

    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.

  • Warning Line 951, Column 821: NET-enabling start-tag requires SHORTTAG YES
    …STAT.hits+'</div></div><br clear="all"/></div><div style="background:url(\'htt…

    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 951, Column 828: end tag for element "DIV" which is not open
    …ts+'</div></div><br clear="all"/></div><div style="background:url(\'http://i.b…

    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 951, Column 950: end tag for element "DIV" which is not open
    …gonal/b59_bottom.gif\') no-repeat top;">&nbsp;</div></div></td></tr></table>');

    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 951, Column 955: end tag for element "TD" which is not open
    …gonal/b59_bottom.gif\') no-repeat top;">&nbsp;</div></div></td></tr></table>');

    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 951, Column 960: end tag for element "TR" which is not open
    …gonal/b59_bottom.gif\') no-repeat top;">&nbsp;</div></div></td></tr></table>');

    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 951, Column 968: end tag for element "TABLE" which is not open
    …gonal/b59_bottom.gif\') no-repeat top;">&nbsp;</div></div></td></tr></table>');

    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 954, Column 10: end tag for element "SCRIPT" which is not open
    	</script>

    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.

  • Warning Line 955, Column 88: cannot generate system identifier for general entity "t0"
    …ipt" language="javascript" src="http://c.bigmir.net/?s12815&t0&l1&o1"></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 955, Column 88: general entity "t0" not defined and no default entity
    …ipt" language="javascript" src="http://c.bigmir.net/?s12815&t0&l1&o1"></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.

  • Error Line 955, Column 90: reference to entity "t0" for which no system identifier could be generated
    …ipt" language="javascript" src="http://c.bigmir.net/?s12815&t0&l1&o1"></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 955, Column 87: entity was defined here
    …ipt" language="javascript" src="http://c.bigmir.net/?s12815&t0&l1&o1"></script>
  • Warning Line 955, Column 91: cannot generate system identifier for general entity "l1"
    …ipt" language="javascript" src="http://c.bigmir.net/?s12815&t0&l1&o1"></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 955, Column 91: general entity "l1" not defined and no default entity
    …ipt" language="javascript" src="http://c.bigmir.net/?s12815&t0&l1&o1"></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.

  • Error Line 955, Column 93: reference to entity "l1" for which no system identifier could be generated
    …ipt" language="javascript" src="http://c.bigmir.net/?s12815&t0&l1&o1"></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 955, Column 90: entity was defined here
    …ipt" language="javascript" src="http://c.bigmir.net/?s12815&t0&l1&o1"></script>
  • Warning Line 955, Column 94: cannot generate system identifier for general entity "o1"
    …ipt" language="javascript" src="http://c.bigmir.net/?s12815&t0&l1&o1"></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 955, Column 94: general entity "o1" not defined and no default entity
    …ipt" language="javascript" src="http://c.bigmir.net/?s12815&t0&l1&o1"></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.

  • Error Line 955, Column 96: reference to entity "o1" for which no system identifier could be generated
    …ipt" language="javascript" src="http://c.bigmir.net/?s12815&t0&l1&o1"></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 955, Column 93: entity was defined here
    …ipt" language="javascript" src="http://c.bigmir.net/?s12815&t0&l1&o1"></script>
  • Error Line 957, Column 95: reference to entity "s12815" for which no system identifier could be generated
    …rc="http://c.bigmir.net/?v12815&s12815&t2&l1" width="88" height="31" alt="bigm…

    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 945, Column 49: entity was defined here
    …><img src="http://c.bigmir.net/?v12815&s12815&t6" width="0" height="0" alt="" …
  • Warning Line 957, Column 96: cannot generate system identifier for general entity "t2"
    …c="http://c.bigmir.net/?v12815&s12815&t2&l1" width="88" height="31" alt="bigmi…

    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 957, Column 96: general entity "t2" not defined and no default entity
    …c="http://c.bigmir.net/?v12815&s12815&t2&l1" width="88" height="31" alt="bigmi…

    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 957, Column 98: reference to entity "t2" for which no system identifier could be generated
    …"http://c.bigmir.net/?v12815&s12815&t2&l1" width="88" height="31" alt="bigmir)…

    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 957, Column 95: entity was defined here
    …rc="http://c.bigmir.net/?v12815&s12815&t2&l1" width="88" height="31" alt="bigm…
  • Error Line 957, Column 101: reference to entity "l1" for which no system identifier could be generated
    …tp://c.bigmir.net/?v12815&s12815&t2&l1" width="88" height="31" alt="bigmir)net…

    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 955, Column 90: entity was defined here
    …ipt" language="javascript" src="http://c.bigmir.net/?s12815&t0&l1&o1"></script>
  • Warning Line 957, Column 189: NET-enabling start-tag requires SHORTTAG YES
    …ight="31" alt="bigmir)net TOP 100" title="bigmir)net TOP 100" border="0" /></a>

    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 988, Column 461: end tag for element "IFRAME" which is not open
    …rolling="no" style="position:absolute; top:-1000px; left:-1000px;"></iframe>');

    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 992, Column 73: reference to entity "bn" for which no system identifier could be generated
    …r.net/partner/banner.php?sid=112026&bn=3&pz=1" width="1" height="1" frameborde…

    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 550, Column 67: entity was defined here
    …u/cgi-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" target=_b…
  • Error Line 992, Column 78: reference to entity "pz" for which no system identifier could be generated
    …/partner/banner.php?sid=112026&bn=3&pz=1" width="1" height="1" frameborder="0"…

    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 550, Column 77: entity was defined here
    …i-bin/click.cgi?sid=142102&sz=main&bn=1&bt=8&pz=3&rnd=247081022" target=_blank>
  • Error Line 992, Column 126: there is no attribute "VSPACE"
    …"1" height="1" frameborder="0" vspace="0" hspace="0" marginwidth="0" marginhei…

    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 992, Column 137: there is no attribute "HSPACE"
    …"1" frameborder="0" vspace="0" hspace="0" marginwidth="0" marginheight="0" scr…

    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 1001, Column 1: NET-enabling start-tag requires SHORTTAG YES
    />

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

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

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

  • Error Line 1025, Column 10: end tag for element "NOINDEX" which is not open
    </noindex></span>

    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 1025, Column 17: end tag for element "SPAN" which is not open
    </noindex></span>

    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 1048, 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
  • 2.450 visits