gooool.ru

Спортивные онлайн трансляции, видеоархив прошедших матчей и обзоров онлайн ...

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

Overview Info

  • Domain Name
    gooool.ru
  • Favicon
  • Alexa Rank
    #37870
  • Google Page Rank
    PR 4
  • Ip Address
    94.242.214.121
  • Page Size
    43.8 KB
  • Images
    0 GIF, 29 JPG, 23 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 0 0 0 0

Website Meta Analysis



  • Title
    Футбольные онлайн трансляции - смотреть футбол онлайн
  • Meta Keyword
    футбол онлайн, прямая трансляция, премьер лига, футбол онлайн трансляция, лига чемпионов, лига европы, чемпионат европы, чемпионат мира
  • Meta Description
    Спортивные онлайн трансляции, видеоархив прошедших матчей и обзоров онлайн

Technical Analysis



  • Webserver
    nginx/1.4.2
  • Ip Address
    94.242.214.121
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from gooool.ru.

HTML Analysis

  • server: nginx/1.4.2
  • date: Sat, 14 Sep 2013 20:56:25 GMT
  • content-type: text/html
  • connection: keep-alive
  • x-powered-by: PHP/5.3.3
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
% By submitting a query to RIPN's Whois Service
% you agree to abide by the following terms of use:
% http://www.ripn.net/about/servpol.html#3.2 (in Russian)
% http://www.ripn.net/about/en/servpol.html#3.2 (in English).

domain: GOOOOL.RU
nserver: ns1.ucoz.net.
nserver: ns2.ucoz.net.
state: REGISTERED, DELEGATED, VERIFIED
person: Private Person
registrar: REGGI-REG-RIPN
admin-contact: http://www.webdrive.ru/webmail/
created: 2009.12.07
paid-till: 2013.12.07
free-date: 2014.01.07
source: TCI

Last updated on 2012.10.10 10:01:42 MSK

DNS Analysis


DNS servers
ns1.ucoz.net [195.216.243.104]
ns2.ucoz.net [213.174.157.200]


DNS Records

Answer records
gooool.ru SOA
server: ns1.ucoz.net
email: alexey7604@rambler.ru
serial: 2013012801
refresh: 10800
retry: 1800
expire: 2592000
minimum ttl: 10800
14400s
gooool.ru MX
preference: 10
exchange: aspmx4.googlemail.com
14400s
gooool.ru MX
preference: 10
exchange: aspmx5.googlemail.com
14400s
gooool.ru MX
preference: 1
exchange: aspmx.l.google.com
14400s
gooool.ru MX
preference: 5
exchange: alt1.aspmx.l.google.com
14400s
gooool.ru MX
preference: 5
exchange: alt2.aspmx.l.google.com
14400s
gooool.ru MX
preference: 10
exchange: mx.yandex.ru
14400s
gooool.ru MX
preference: 10
exchange: aspmx2.googlemail.com
14400s
gooool.ru MX
preference: 10
exchange: aspmx3.googlemail.com
14400s
gooool.ru A 193.109.247.61 14400s
gooool.ru NS  ns1.ucoz.net 14400s
gooool.ru NS  ns2.ucoz.net 14400s

Authority records

Additional records
mx.yandex.ru A 195.216.243.30 14400s
ns1.ucoz.net A 195.216.243.104 14400s
ns2.ucoz.net A 213.174.157.200 14400s

IP 94.242.214.121 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 63 Errors
  • 19 Warnings
Ratio Text/Html
  • 0.6818728560609435
Message Error
  • Error Line 2, Column 1: Missing xmlns attribute for element html. The value should be: http://www.w3.org/1999/xhtml
    <html>

    Many Document Types based on XML need a mandatory xmlns attribute on the root element. For example, the root element for XHTML might look like:
    <html xmlns="http://www.w3.org/1999/xhtml">

  • Error Line 4, Column 68: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> 

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

  • Info Line 4, Column 1: start tag was here
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> 
  • Error Line 5, Column 179: end tag for "link" omitted, but OMITTAG NO was specified
    …идеоархив прошедших матчей и обзоров онлайн" href="http://gooool.ru/news/rss/">

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

  • Info Line 5, Column 1: start tag was here
    <link rel="alternate" type="application/rss+xml" title="GOOOOL.RU - спортивные …
  • Error Line 20, Column 24: there is no attribute "rel"
    <div id="utbr8214" rel="s61"></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 25, Column 28: there is no attribute "height"
    <tr><td colspan="2" height="50" style="background: transparent url(http://goooo…

    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 53, Column 34: ID "services" already defined
     <li class="top"><a href="/" id="services" class="top_link"><span class="down">…

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

  • Info Line 34, Column 34: ID "services" first defined here
     <li class="top"><a href="/" id="services" class="top_link"><span class="down">…
  • Error Line 60, Column 34: ID "services" already defined
     <li class="top"><a href="/" id="services" class="top_link"><span class="down">…

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

  • Info Line 34, Column 34: ID "services" first defined here
     <li class="top"><a href="/" id="services" class="top_link"><span class="down">…
  • Error Line 70, Column 34: ID "services" already defined
     <li class="top"><a href="/" id="services" class="top_link"><span class="down">…

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

  • Info Line 34, Column 34: ID "services" first defined here
     <li class="top"><a href="/" id="services" class="top_link"><span class="down">…
  • Error Line 89, Column 34: ID "services" already defined
     <li class="top"><a href="/" id="services" class="top_link"><span class="down">…

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

  • Info Line 34, Column 34: ID "services" first defined here
     <li class="top"><a href="/" id="services" class="top_link"><span class="down">…
  • Error Line 97, Column 34: ID "services" already defined
     <li class="top"><a href="/" id="services" class="top_link"><span class="down">…

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

  • Info Line 34, Column 34: ID "services" first defined here
     <li class="top"><a href="/" id="services" class="top_link"><span class="down">…
  • Error Line 108, Column 45: ID "privacy" already defined
    …lass="top"><a href="/index/0-331" id="privacy" class="top_link"><span>Поиск</s…

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

  • Info Line 107, Column 45: ID "privacy" first defined here
    …lass="top"><a href="/index/0-373" id="privacy" class="top_link"><span>FAQ</spa…
  • Error Line 115, Column 25: there is no attribute "width"
     <td valign="top" width="175" style="padding-right:1px;">

    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 128, Column 269: document type does not allow element "style" here
    …round-inline-policy: initial;"><!-- <bc> --><style type="text/css"></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 144, Column 16: there is no attribute "align"
    <td><div align="center"><b><span style="color:red">Суббота 16 февраля</span></b…

    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 146, Column 135: there is no attribute "bgcolor"
    …"19" /></td> <td align="left" bgcolor="#D0CEC9"><a href="http://gooool.ru/blog…

    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 151, Column 4: document type does not allow element "tr" here
    <tr> <td align="left" class="main_border222"><img src="/flags/de.gif" alt="" wi…

    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 151, Column 225: document type does not allow element "tr" here
    …href="http://gooool.ru/blog/2013-02-15-4576">Майнц - Шальке</a></td> </tr> <tr>

    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 156, Column 4: document type does not allow element "tr" here
    <tr> <td align="left" class="main_border222"><img src="/flags/en_cup.gif" alt="…

    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 156, Column 233: document type does not allow element "tr" here
    …="http://gooool.ru/blog/2013-02-15-4568">Арсенал - Блэкберн</a></td> </tr> <tr>

    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 161, Column 4: document type does not allow element "tr" here
    <tr> <td align="left" class="main_border222"><img src="/flags/es.gif" alt="" wi…

    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 161, Column 226: document type does not allow element "tr" here
    …ref="http://gooool.ru/blog/2013-02-15-4570">Хетафе - Сельта</a></td> </tr> <tr>

    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 166, Column 4: document type does not allow element "tr" here
    <tr> <td align="left" class="main_border222"><img src="/flags/es.gif" alt="" wi…

    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 166, Column 227: document type does not allow element "tr" here
    …ef="http://gooool.ru/blog/2013-02-15-4571">Малага - Атлетик</a></td> </tr> <tr>

    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 171, Column 4: document type does not allow element "tr" here
    <tr> <td align="left" class="main_border222"><img src="/flags/it.gif" alt="" wi…

    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 171, Column 226: document type does not allow element "tr" here
    …ref="http://gooool.ru/blog/2013-02-15-4574">Кьево - Палермо</a></td> </tr> <tr>

    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 176, Column 4: document type does not allow element "tr" here
    <tr> <td align="left" class="main_border222"><img src="/flags/de.gif" alt="" wi…

    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 176, Column 232: document type does not allow element "tr" here
    …ttp://gooool.ru/blog/2013-02-15-4577">Боруссия Д - Айнтрахт</a></td> </tr> <tr>

    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 181, Column 4: document type does not allow element "tr" here
    <tr> <td align="left" class="main_border222"><img src="/flags/en_cup.gif" alt="…

    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 181, Column 231: document type does not allow element "tr" here
    …ef="http://gooool.ru/blog/2013-02-15-4569">Олдхэм - Эвертон</a></td> </tr> <tr>

    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 186, Column 4: document type does not allow element "tr" here
    <tr> <td align="left" class="main_border222"><img src="/flags/es.gif" alt="" wi…

    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 186, Column 230: document type does not allow element "tr" here
    …"http://gooool.ru/blog/2013-02-15-4572">Гранада - Барселона</a></td> </tr> <tr>

    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 191, Column 4: document type does not allow element "tr" here
    <tr> <td align="left" class="main_border222"><img src="/flags/it.gif" alt="" wi…

    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 191, Column 225: document type does not allow element "tr" here
    …href="http://gooool.ru/blog/2013-02-15-4575">Рома - Ювентус</a></td> </tr> <tr>

    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 196, Column 4: document type does not allow element "tr" here
    <tr> <td align="left" class="main_border222"><img src="/flags/es.gif" alt="" wi…

    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 196, Column 229: document type does not allow element "tr" here
    …="http://gooool.ru/blog/2013-02-15-4573">Осасуна - Сарагоса</a></td> </tr> <tr>

    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 201, Column 8: end tag for "tr" omitted, but OMITTAG NO was specified
    </tbody>

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

  • Info Line 196, Column 226: start tag was here
    …="http://gooool.ru/blog/2013-02-15-4573">Осасуна - Сарагоса</a></td> </tr> <tr>
  • Error Line 201, Column 8: end tag for "tr" omitted, but OMITTAG NO was specified
    </tbody>

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

  • Info Line 191, Column 222: start tag was here
    …href="http://gooool.ru/blog/2013-02-15-4575">Рома - Ювентус</a></td> </tr> <tr>
  • Error Line 201, Column 8: end tag for "tr" omitted, but OMITTAG NO was specified
    </tbody>

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

  • Info Line 186, Column 227: start tag was here
    …"http://gooool.ru/blog/2013-02-15-4572">Гранада - Барселона</a></td> </tr> <tr>
  • Error Line 201, Column 8: end tag for "tr" omitted, but OMITTAG NO was specified
    </tbody>

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

  • Info Line 181, Column 228: start tag was here
    …ef="http://gooool.ru/blog/2013-02-15-4569">Олдхэм - Эвертон</a></td> </tr> <tr>
  • Error Line 201, Column 8: end tag for "tr" omitted, but OMITTAG NO was specified
    </tbody>

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

  • Info Line 176, Column 229: start tag was here
    …ttp://gooool.ru/blog/2013-02-15-4577">Боруссия Д - Айнтрахт</a></td> </tr> <tr>
  • Error Line 201, Column 8: end tag for "tr" omitted, but OMITTAG NO was specified
    </tbody>

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

  • Info Line 171, Column 223: start tag was here
    …ref="http://gooool.ru/blog/2013-02-15-4574">Кьево - Палермо</a></td> </tr> <tr>
  • Error Line 201, Column 8: end tag for "tr" omitted, but OMITTAG NO was specified
    </tbody>

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

  • Info Line 166, Column 224: start tag was here
    …ef="http://gooool.ru/blog/2013-02-15-4571">Малага - Атлетик</a></td> </tr> <tr>
  • Error Line 201, Column 8: end tag for "tr" omitted, but OMITTAG NO was specified
    </tbody>

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

  • Info Line 161, Column 223: start tag was here
    …ref="http://gooool.ru/blog/2013-02-15-4570">Хетафе - Сельта</a></td> </tr> <tr>
  • Error Line 201, Column 8: end tag for "tr" omitted, but OMITTAG NO was specified
    </tbody>

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

  • Info Line 156, Column 230: start tag was here
    …="http://gooool.ru/blog/2013-02-15-4568">Арсенал - Блэкберн</a></td> </tr> <tr>
  • Error Line 201, Column 8: end tag for "tr" omitted, but OMITTAG NO was specified
    </tbody>

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

  • Info Line 151, Column 222: start tag was here
    …href="http://gooool.ru/blog/2013-02-15-4576">Майнц - Шальке</a></td> </tr> <tr>
  • Error Line 201, Column 8: end tag for "tr" omitted, but OMITTAG NO was specified
    </tbody>

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

  • Info Line 146, Column 226: start tag was here
    …f="http://gooool.ru/blog/2013-02-15-4578">Эстафета. Мужчины</a></td> </tr> <tr>
  • Error Line 201, Column 8: end tag for "table" omitted, but OMITTAG NO was specified
    </tbody>

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

  • Info Line 141, Column 2: start tag was here
     <table border="0" cellpadding="0" cellspacing="0"
  • Error Line 201, Column 8: end tag for "td" omitted, but OMITTAG NO was specified
    </tbody>

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

  • Info Line 127, Column 2: start tag was here
     <td
  • Error Line 201, Column 8: end tag for "tr" omitted, but OMITTAG NO was specified
    </tbody>

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

  • Info Line 126, Column 2: start tag was here
     <tr>
  • Error Line 210, Column 7: 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 210, Column 7: 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 215, Column 8: 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 229, Column 5: end tag for "hr" omitted, but OMITTAG NO was specified
    <hr>

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

  • Info Line 229, Column 1: start tag was here
    <hr>
  • Error Line 238, Column 8: "tr" not finished but containing element ended
    </tbody>
  • Error Line 238, Column 8: end tag for "tr" omitted, but OMITTAG NO was specified
    </tbody>

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

  • Info Line 237, Column 219: start tag was here
    …"><a href="/index/0-44"><b>Прямые онлайн трансляции - 2</b></a></td> </tr> <tr>
  • Error Line 241, Column 9: end tag for element "tbody" which is not open
     </tbody>

    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 265, Column 168: document type does not allow element "div" here
    …('<div align="left" style="padding:5px;"><div class="myWinLoad"></div></div>');

    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 267, Column 64: document type does not allow element "div" here
    …div align="left" style="padding:10px;"><div class="myWinLoadSF" title="Невозмо…

    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 268, Column 39: document type does not allow element "div" here
    		_uWnd.alert('<div class="myWinError">Невозможно выполнить запрос, попробуйте …

    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 276, Column 28: there is no attribute "nowrap"
    <tr><td width="20%" nowrap="nowrap">E-mail:<a href="javascript://" rel="nofollo…

    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 276, Column 326: end tag for "img" omitted, but OMITTAG NO was specified
    …le="border:0;vertical-align:-4px;"></a></td><td><input class="loginField" type…

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

  • Info Line 276, Column 210: start tag was here
    …x/90-7'});return false;" class="noun"><img alt="" title="uID поддержка" src="h…
  • Error Line 280, Column 15: "nowrap" is not a member of a group specified for any attribute
    <tr><td nowrap><input id="remsitePage1" type="checkbox" name="rem" value="1" ch…
  • Error Line 284, Column 42: document type does not allow element "input" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "address", "fieldset" start-tag
    …put type="hidden" name="a" value="2" /><input type="hidden" name="ajax" value=…

    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 284, Column 87: document type does not allow element "input" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "address", "fieldset" start-tag
    … type="hidden" name="ajax" value="1" /><input type="hidden" name="rnd" value="…

    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 284, Column 133: document type does not allow element "input" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "address", "fieldset" start-tag
    …t type="hidden" name="rnd" value="274" /></form></div></div><!-- </bc> --></td>

    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 304, Column 255: element "noindex" undefined
    …olicy: initial;"><!-- <bc> --><noindex><div align="center"><div id="smi2adbloc…

    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 346, Column 254: element "center" undefined
    …policy: initial;"><!-- <bc> --><center><div class="tOnline" id="onl1">Сейчас н…

    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 352, Column 5: end tag for element "td" which is not open
    </td>

    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 354, Column 92: document type does not allow element "td" here
    …op" style="padding-left:1px;background:#FFFFFF;border-left:1px solid #DEDEDE;">

    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 357, Column 64: element "center" undefined
    …px solid #D7D7D7;padding:5px;"><center><script type="text/javascript" src="htt…

    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 358, Column 218: there is no attribute "border"
    …/s61.ucoz.net/img/ma/m/i3.gif" border="0" width="220" height="19" /></div></di…

    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 362, Column 9: element "center" undefined
     <center><img class="fotokol" width="400" border="1" align="center" vspace="5" …

    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 362, Column 60: there is no attribute "align"
    …fotokol" width="400" border="1" align="center" vspace="5" hspace="10" src="htt…

    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 362, Column 76: there is no attribute "vspace"
    …400" border="1" align="center" vspace="5" hspace="10" src="http://gooool.ru/im…

    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 362, Column 87: there is no attribute "hspace"
    …="1" align="center" vspace="5" hspace="10" src="http://gooool.ru/images1/00130…

    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 362, Column 132: required attribute "alt" not specified
    …ter" vspace="5" hspace="10" src="http://gooool.ru/images1/00130.png"></center> 

    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 362, Column 141: end tag for "img" omitted, but OMITTAG NO was specified
    …ter" vspace="5" hspace="10" src="http://gooool.ru/images1/00130.png"></center> 

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

  • Info Line 362, Column 10: start tag was here
     <center><img class="fotokol" width="400" border="1" align="center" vspace="5" …
  • Error Line 375, Column 9: element "center" undefined
     <center><img class="fotokol" width="400" border="1" align="center" vspace="5" …

    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 375, Column 132: required attribute "alt" not specified
    …ter" vspace="5" hspace="10" src="http://gooool.ru/images2/00044.jpg"></center> 

    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 375, Column 141: end tag for "img" omitted, but OMITTAG NO was specified
    …ter" vspace="5" hspace="10" src="http://gooool.ru/images2/00044.jpg"></center> 

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

  • Info Line 375, Column 10: start tag was here
     <center><img class="fotokol" width="400" border="1" align="center" vspace="5" …
  • Error Line 388, Column 9: element "center" undefined
     <center><img class="fotokol" width="400" border="1" align="center" vspace="5" …

    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 388, Column 132: required attribute "alt" not specified
    …ter" vspace="5" hspace="10" src="http://gooool.ru/images1/00129.png"></center> 

    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 388, Column 141: end tag for "img" omitted, but OMITTAG NO was specified
    …ter" vspace="5" hspace="10" src="http://gooool.ru/images1/00129.png"></center> 

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

  • Info Line 388, Column 10: start tag was here
     <center><img class="fotokol" width="400" border="1" align="center" vspace="5" …
  • Error Line 401, Column 9: element "center" undefined
     <center><img class="fotokol" width="400" border="1" align="center" vspace="5" …

    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 401, Column 135: required attribute "alt" not specified
    …" vspace="5" hspace="10" src="http://gooool.ru/images/post/news.jpg"></center> 

    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 401, Column 144: end tag for "img" omitted, but OMITTAG NO was specified
    …" vspace="5" hspace="10" src="http://gooool.ru/images/post/news.jpg"></center> 

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

  • Info Line 401, Column 10: start tag was here
     <center><img class="fotokol" width="400" border="1" align="center" vspace="5" …
  • Error Line 414, Column 9: element "center" undefined
     <center><img class="fotokol" width="400" border="1" align="center" vspace="5" …

    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 414, Column 148: required attribute "alt" not specified
    …hspace="10" src="http://gooool.ru/images/post/football_news_ukr.jpg"></center> 

    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 414, Column 157: end tag for "img" omitted, but OMITTAG NO was specified
    …hspace="10" src="http://gooool.ru/images/post/football_news_ukr.jpg"></center> 

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

  • Info Line 414, Column 10: start tag was here
     <center><img class="fotokol" width="400" border="1" align="center" vspace="5" …
  • Error Line 427, Column 9: element "center" undefined
     <center><img class="fotokol" width="400" border="1" align="center" vspace="5" …

    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 427, Column 132: required attribute "alt" not specified
    …ter" vspace="5" hspace="10" src="http://gooool.ru/images1/00176.jpg"></center> 

    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 427, Column 141: end tag for "img" omitted, but OMITTAG NO was specified
    …ter" vspace="5" hspace="10" src="http://gooool.ru/images1/00176.jpg"></center> 

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

  • Info Line 427, Column 10: start tag was here
     <center><img class="fotokol" width="400" border="1" align="center" vspace="5" …
  • Error Line 440, Column 9: element "center" undefined
     <center><img class="fotokol" width="400" border="1" align="center" vspace="5" …

    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 440, Column 132: required attribute "alt" not specified
    …ter" vspace="5" hspace="10" src="http://gooool.ru/images2/00082.jpg"></center> 

    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 440, Column 141: end tag for "img" omitted, but OMITTAG NO was specified
    …ter" vspace="5" hspace="10" src="http://gooool.ru/images2/00082.jpg"></center> 

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

  • Info Line 440, Column 10: start tag was here
     <center><img class="fotokol" width="400" border="1" align="center" vspace="5" …
  • Error Line 453, Column 9: element "center" undefined
     <center><img class="fotokol" width="400" border="1" align="center" vspace="5" …

    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 453, Column 139: required attribute "alt" not specified
    …pace="5" hspace="10" src="http://gooool.ru/images/post/obzor_el.jpg"></center> 

    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 453, Column 148: end tag for "img" omitted, but OMITTAG NO was specified
    …pace="5" hspace="10" src="http://gooool.ru/images/post/obzor_el.jpg"></center> 

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

  • Info Line 453, Column 10: start tag was here
     <center><img class="fotokol" width="400" border="1" align="center" vspace="5" …
  • Error Line 466, Column 9: element "center" undefined
     <center><img class="fotokol" width="400" border="1" align="center" vspace="5" …

    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 466, Column 137: required attribute "alt" not specified
    …vspace="5" hspace="10" src="http://gooool.ru/images/post/pro_el.jpg"></center> 

    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 466, Column 146: end tag for "img" omitted, but OMITTAG NO was specified
    …vspace="5" hspace="10" src="http://gooool.ru/images/post/pro_el.jpg"></center> 

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

  • Info Line 466, Column 10: start tag was here
     <center><img class="fotokol" width="400" border="1" align="center" vspace="5" …
  • Error Line 479, Column 9: element "center" undefined
     <center><img class="fotokol" width="400" border="1" align="center" vspace="5" …

    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 479, Column 132: required attribute "alt" not specified
    …ter" vspace="5" hspace="10" src="http://gooool.ru/images2/00081.jpg"></center> 

    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 479, Column 141: end tag for "img" omitted, but OMITTAG NO was specified
    …ter" vspace="5" hspace="10" src="http://gooool.ru/images2/00081.jpg"></center> 

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

  • Info Line 479, Column 10: start tag was here
     <center><img class="fotokol" width="400" border="1" align="center" vspace="5" …
  • Error Line 492, Column 9: element "center" undefined
     <center><img class="fotokol" width="400" border="1" align="center" vspace="5" …

    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 492, Column 132: required attribute "alt" not specified
    …ter" vspace="5" hspace="10" src="http://gooool.ru/images2/00080.png"></center> 

    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 492, Column 141: end tag for "img" omitted, but OMITTAG NO was specified
    …ter" vspace="5" hspace="10" src="http://gooool.ru/images2/00080.png"></center> 

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

  • Info Line 492, Column 10: start tag was here
     <center><img class="fotokol" width="400" border="1" align="center" vspace="5" …
  • Error Line 505, Column 9: element "center" undefined
     <center><img class="fotokol" width="400" border="1" align="center" vspace="5" …

    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 505, Column 132: required attribute "alt" not specified
    …ter" vspace="5" hspace="10" src="http://gooool.ru/images2/00079.jpg"></center> 

    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 505, Column 141: end tag for "img" omitted, but OMITTAG NO was specified
    …ter" vspace="5" hspace="10" src="http://gooool.ru/images2/00079.jpg"></center> 

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

  • Info Line 505, Column 10: start tag was here
     <center><img class="fotokol" width="400" border="1" align="center" vspace="5" …
  • Error Line 518, Column 9: element "center" undefined
     <center><img class="fotokol" width="400" border="1" align="center" vspace="5" …

    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 518, Column 132: required attribute "alt" not specified
    …ter" vspace="5" hspace="10" src="http://gooool.ru/images2/00078.png"></center> 

    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 518, Column 141: end tag for "img" omitted, but OMITTAG NO was specified
    …ter" vspace="5" hspace="10" src="http://gooool.ru/images2/00078.png"></center> 

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

  • Info Line 518, Column 10: start tag was here
     <center><img class="fotokol" width="400" border="1" align="center" vspace="5" …
  • Error Line 531, Column 9: element "center" undefined
     <center><img class="fotokol" width="400" border="1" align="center" vspace="5" …

    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 531, Column 132: required attribute "alt" not specified
    …ter" vspace="5" hspace="10" src="http://gooool.ru/images2/00077.jpg"></center> 

    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 531, Column 141: end tag for "img" omitted, but OMITTAG NO was specified
    …ter" vspace="5" hspace="10" src="http://gooool.ru/images2/00077.jpg"></center> 

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

  • Info Line 531, Column 10: start tag was here
     <center><img class="fotokol" width="400" border="1" align="center" vspace="5" …
  • Error Line 544, Column 9: element "center" undefined
     <center><img class="fotokol" width="400" border="1" align="center" vspace="5" …

    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 544, Column 139: required attribute "alt" not specified
    …pace="5" hspace="10" src="http://gooool.ru/images/post/obzor_el.jpg"></center> 

    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 544, Column 148: end tag for "img" omitted, but OMITTAG NO was specified
    …pace="5" hspace="10" src="http://gooool.ru/images/post/obzor_el.jpg"></center> 

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

  • Info Line 544, Column 10: start tag was here
     <center><img class="fotokol" width="400" border="1" align="center" vspace="5" …
  • Error Line 556, Column 5: end tag for element "tr" which is not open
    </tr>

    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 558, Column 4: document type does not allow element "tr" here; assuming missing "table" start-tag
    <tr><td colspan="2">
  • Error Line 559, Column 24: document type does not allow element "html" here
    <!--U1BFOOTER1Z--><html>

    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 559, Column 19: Missing xmlns attribute for element html. The value should be: http://www.w3.org/1999/xhtml
    <!--U1BFOOTER1Z--><html>

    Many Document Types based on XML need a mandatory xmlns attribute on the root element. For example, the root element for XHTML might look like:
    <html xmlns="http://www.w3.org/1999/xhtml">

  • Error Line 560, 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 562, Column 58: there is no attribute "height"
    …ellpadding="0" cellspacing="0" height="47" width="100%" style="background:url(…

    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 563, Column 422: there is no attribute "target"
    …13 <a href="http://gooool.ru/" target="_blank">gooool.ru</a> | <a href="http:/…

    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 565, Column 28: document type does not allow element "div" here
    <div id="smi2adblock_39372"><a href="http://smi2.ru/">Новости СМИ2</a></div>

    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 566, Column 54: document type does not allow element "script" here
    <script type="text/javascript" charset="windows-1251">

    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 579, Column 7: end tag for "html" which is not finished
    </html><!--/U1BFOOTER1Z-->

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

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

  • Error Line 584, Column 8: element "center" undefined
    <center>

    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 622, Column 49: document type does not allow element "a" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "pre", "address", "fieldset" start-tag
    <a href="http://top100.rambler.ru/navi/2279987/">

    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 626, Column 11: end tag for "noscript" which is not finished
    </noscript>

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

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

  • Error Line 659, 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).
  • Warning Line 670, Column 49: cannot generate system identifier for general entity "jq"
    ….src="http://am10.ru/code.php?type=sb&jq="+am_jq+"&rand="+am_rand+"&u=3276&loc…

    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 670, Column 49: general entity "jq" not defined and no default entity
    ….src="http://am10.ru/code.php?type=sb&jq="+am_jq+"&rand="+am_rand+"&u=3276&loc…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 670, Column 51: reference not terminated by REFC delimiter
    …rc="http://am10.ru/code.php?type=sb&jq="+am_jq+"&rand="+am_rand+"&u=3276&loc="…

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

  • Error Line 670, Column 51: reference to entity "jq" for which no system identifier could be generated
    …rc="http://am10.ru/code.php?type=sb&jq="+am_jq+"&rand="+am_rand+"&u=3276&loc="…

    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 670, Column 48: entity was defined here
    …b.src="http://am10.ru/code.php?type=sb&jq="+am_jq+"&rand="+am_rand+"&u=3276&lo…
  • Warning Line 670, Column 62: cannot generate system identifier for general entity "rand"
    …am10.ru/code.php?type=sb&jq="+am_jq+"&rand="+am_rand+"&u=3276&loc="+am_loc+"&r…

    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 670, Column 62: general entity "rand" not defined and no default entity
    …am10.ru/code.php?type=sb&jq="+am_jq+"&rand="+am_rand+"&u=3276&loc="+am_loc+"&r…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 670, Column 66: reference not terminated by REFC delimiter
    ….ru/code.php?type=sb&jq="+am_jq+"&rand="+am_rand+"&u=3276&loc="+am_loc+"&ref="…

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

  • Error Line 670, Column 66: reference to entity "rand" for which no system identifier could be generated
    ….ru/code.php?type=sb&jq="+am_jq+"&rand="+am_rand+"&u=3276&loc="+am_loc+"&ref="…

    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 670, Column 61: entity was defined here
    …/am10.ru/code.php?type=sb&jq="+am_jq+"&rand="+am_rand+"&u=3276&loc="+am_loc+"&…
  • Warning Line 670, Column 79: cannot generate system identifier for general entity "u"
    …type=sb&jq="+am_jq+"&rand="+am_rand+"&u=3276&loc="+am_loc+"&ref="+am_ref+"&tit…

    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 670, Column 79: general entity "u" not defined and no default entity
    …type=sb&jq="+am_jq+"&rand="+am_rand+"&u=3276&loc="+am_loc+"&ref="+am_ref+"&tit…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 670, Column 80: reference not terminated by REFC delimiter
    …ype=sb&jq="+am_jq+"&rand="+am_rand+"&u=3276&loc="+am_loc+"&ref="+am_ref+"&titl…

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

  • Error Line 670, Column 80: reference to entity "u" for which no system identifier could be generated
    …ype=sb&jq="+am_jq+"&rand="+am_rand+"&u=3276&loc="+am_loc+"&ref="+am_ref+"&titl…

    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 670, Column 78: entity was defined here
    …?type=sb&jq="+am_jq+"&rand="+am_rand+"&u=3276&loc="+am_loc+"&ref="+am_ref+"&ti…
  • Warning Line 670, Column 86: cannot generate system identifier for general entity "loc"
    …&jq="+am_jq+"&rand="+am_rand+"&u=3276&loc="+am_loc+"&ref="+am_ref+"&title="+am…

    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 670, Column 86: general entity "loc" not defined and no default entity
    …&jq="+am_jq+"&rand="+am_rand+"&u=3276&loc="+am_loc+"&ref="+am_ref+"&title="+am…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 670, Column 89: reference not terminated by REFC delimiter
    …="+am_jq+"&rand="+am_rand+"&u=3276&loc="+am_loc+"&ref="+am_ref+"&title="+am_ti…

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

  • Error Line 670, Column 89: reference to entity "loc" for which no system identifier could be generated
    …="+am_jq+"&rand="+am_rand+"&u=3276&loc="+am_loc+"&ref="+am_ref+"&title="+am_ti…

    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 670, Column 85: entity was defined here
    …b&jq="+am_jq+"&rand="+am_rand+"&u=3276&loc="+am_loc+"&ref="+am_ref+"&title="+a…
  • Warning Line 670, Column 101: cannot generate system identifier for general entity "ref"
    …am_jq+"&rand="+am_rand+"&u=3276&loc="+am_loc+"&ref="+am_ref+"&title="+am_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 670, Column 101: general entity "ref" not defined and no default entity
    …am_jq+"&rand="+am_rand+"&u=3276&loc="+am_loc+"&ref="+am_ref+"&title="+am_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.

  • Warning Line 670, Column 104: reference not terminated by REFC delimiter
    …am_jq+"&rand="+am_rand+"&u=3276&loc="+am_loc+"&ref="+am_ref+"&title="+am_title;

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

  • Error Line 670, Column 104: reference to entity "ref" for which no system identifier could be generated
    …am_jq+"&rand="+am_rand+"&u=3276&loc="+am_loc+"&ref="+am_ref+"&title="+am_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 670, Column 100: entity was defined here
    …am_jq+"&rand="+am_rand+"&u=3276&loc="+am_loc+"&ref="+am_ref+"&title="+am_title;
  • Warning Line 670, Column 116: cannot generate system identifier for general entity "title"
    …am_jq+"&rand="+am_rand+"&u=3276&loc="+am_loc+"&ref="+am_ref+"&title="+am_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 670, Column 116: general entity "title" not defined and no default entity
    …am_jq+"&rand="+am_rand+"&u=3276&loc="+am_loc+"&ref="+am_ref+"&title="+am_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.

  • Warning Line 670, Column 121: reference not terminated by REFC delimiter
    …am_jq+"&rand="+am_rand+"&u=3276&loc="+am_loc+"&ref="+am_ref+"&title="+am_title;

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

  • Error Line 670, Column 121: reference to entity "title" for which no system identifier could be generated
    …am_jq+"&rand="+am_rand+"&u=3276&loc="+am_loc+"&ref="+am_ref+"&title="+am_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 670, Column 115: entity was defined here
    …am_jq+"&rand="+am_rand+"&u=3276&loc="+am_loc+"&ref="+am_ref+"&title="+am_title;
  • Warning Line 676, Column 106: cannot generate system identifier for general entity "div"
    … src="http://www.directadvert.ru/show.cgi?adp=25293&div=DIV_DA_25293"></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 676, Column 106: general entity "div" not defined and no default entity
    … src="http://www.directadvert.ru/show.cgi?adp=25293&div=DIV_DA_25293"></script>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 676, Column 109: reference not terminated by REFC delimiter
    … src="http://www.directadvert.ru/show.cgi?adp=25293&div=DIV_DA_25293"></script>

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

  • Warning Line 676, Column 109: reference to external entity in attribute value
    … src="http://www.directadvert.ru/show.cgi?adp=25293&div=DIV_DA_25293"></script>

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

  • Error Line 676, Column 109: reference to entity "div" for which no system identifier could be generated
    … src="http://www.directadvert.ru/show.cgi?adp=25293&div=DIV_DA_25293"></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 676, Column 105: entity was defined here
    … src="http://www.directadvert.ru/show.cgi?adp=25293&div=DIV_DA_25293"></script>

Visitor Analysis

Daily Visitor
  • 0 visits

In Page Analysis