Главная Легендарные люди Помощь проекту! Войти Регистрация Вход RSS Записей RSS Комментариев WordPress.org Наши друзья Рубрики Видео (346) American Dad! (99) ARYstudio (28) Annoying Orange (9) South Park (15) Family Guy (152) Futurama ...

filiza.ru
  • Domain Name
    filiza.ru
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #184179
  • Page Size
    36.2 KB
  • Ip Address
    78.46.247.73
  • Heading
    H1: 5, H2: 10, H3: 4, H4: 0, H5: 0, H6: 0
  • Images
    10 GIF, 0 JPG, 1 PNG

Website Meta Analysis

  • Title
    FiliZa Studio – Гриффины, Американский папа, Шоу Кливленда
  • Meta Keyword
  • Meta Description
    Главная Легендарные люди Помощь проекту! Войти Регистрация Вход RSS Записей RSS Комментариев WordPress.org Наши друзья Рубрики Видео (346) American Dad! (99) ARYstudio (28) Annoying Orange (9) South Park (15) Family Guy (152) Futurama (4) NHK ...

Technical Analysis

  • Webserver
    Apache/2.2.22 (FreeBSD) PHP/5.2.17 with Suhosin-Patch mod_ssl/2.2.22 OpenSSL/0.9.8q DAV/2
  • Ip Address
    78.46.247.73
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Thu, 27 Jun 2013 08:32:21 GMT
  • server: Apache/2.2.22 (FreeBSD) PHP/5.2.17 with Suhosin-Patch mod_ssl/2.2.22 OpenSSL/0.9.8q DAV/2
  • x-powered-by: PHP/5.2.17
  • x-pingback: http://www.filiza.ru/xmlrpc.php
  • content-type: text/html; charset=UTF-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for filiza.ru

DNS Analysis


DNS servers
dns2.yandex.ru [93.158.134.213]
dns1.yandex.ru


DNS Records

Answer records
filiza.ru NS  dns2.yandex.ru 21600s
filiza.ru TXT v=spf1 a mx -all 21600s
filiza.ru A 78.46.247.73 21600s
filiza.ru MX
preference: 20
exchange: ALT1.ASPMX.L.GOOGLE.COM
21600s
filiza.ru MX
preference: 30
exchange: ASPMX4.GOOGLEMAIL.COM
21600s
filiza.ru NS  dns1.yandex.ru 21600s
filiza.ru MX
preference: 30
exchange: ASPMX3.GOOGLEMAIL.COM
21600s
filiza.ru MX
preference: 20
exchange: ALT2.ASPMX.L.GOOGLE.COM
21600s
filiza.ru MX
preference: 10
exchange: ASPMX.L.GOOGLE.COM
21600s
filiza.ru MX
preference: 30
exchange: ASPMX2.GOOGLEMAIL.COM
21600s
filiza.ru SOA
server: dns1.yandex.ru
email: freonx-mk@yandex.ru
serial: 2012053001
refresh: 14400
retry: 900
expire: 1209600
minimum ttl: 14400
21600s
filiza.ru MX
preference: 30
exchange: ASPMX5.GOOGLEMAIL.COM
21600s

Authority records

Additional records

IP 78.46.247.73 Analysis

  • Country Code
    DE
  • Country Code3
    DEU
  • Country Name
    Germany
  • City
    L�beck
  • Continent Code
    EU
  • Latitude
    53.8667
  • Longitude
    10.7.
  • No whois ip data for 78.46.247.73

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 64 Errors
  • 19 Warnings
Ratio Text/Html
  • 0.7121138605854763
Message Error
  • Error Line 10, Column 29: document type does not allow element "div" here; assuming missing "object" start-tag
    		<div id="vk_api_transport"></div>
  • Error Line 26, Column 121: document type does not allow element "link" here
    …rss+xml" title="FiliZa Studio &raquo; Фид" href="http://www.filiza.ru/feed/" />

    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 27, Column 143: document type does not allow element "link" here
    …tudio &raquo; Лента комментариев" href="http://www.filiza.ru/comments/feed/" />

    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 28, Column 160: document type does not allow element "link" here
    …t/plugins/wp-pagenavi/pagenavi-css.css?ver=2.70' type='text/css' media='all' />

    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 29, Column 16: there is no attribute "property"
    <meta property="vk:app_id" content="2620612" />

    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 29, Column 47: document type does not allow element "meta" here
    <meta property="vk:app_id" content="2620612" />

    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 33, Column 104: document type does not allow element "link" here
    …"application/rsd+xml" title="RSD" href="http://www.filiza.ru/xmlrpc.php?rsd" />

    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 34, Column 117: document type does not allow element "link" here
    …on/wlwmanifest+xml" href="http://www.filiza.ru/wp-includes/wlwmanifest.xml" /> 

    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 35, Column 102: document type does not allow element "link" here
    …n" href="http://www.filiza.ru/wp-content/themes/filizawordpress/favicon.ico" />

    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 37, Column 7: end tag for "object" omitted, but OMITTAG NO was specified
    </head>

    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 10, Column 3: start tag was here
    		<div id="vk_api_transport"></div>
  • Error Line 39, Column 31: document type does not allow element "script" here; assuming missing "body" start-tag
    <script type="text/javascript">
  • Warning Line 48, Column 50: cannot generate system identifier for general entity "jq"
    ….src="http://am10.ru/code.php?type=sb&jq="+am_jq+"&rand="+am_rand+"&u=18077&lo…

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

    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 48, Column 52: reference not terminated by REFC delimiter
    …rc="http://am10.ru/code.php?type=sb&jq="+am_jq+"&rand="+am_rand+"&u=18077&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 48, Column 52: 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=18077&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 48, Column 49: entity was defined here
    …b.src="http://am10.ru/code.php?type=sb&jq="+am_jq+"&rand="+am_rand+"&u=18077&l…
  • Warning Line 48, Column 63: cannot generate system identifier for general entity "rand"
    …am10.ru/code.php?type=sb&jq="+am_jq+"&rand="+am_rand+"&u=18077&loc="+am_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 48, Column 63: general entity "rand" not defined and no default entity
    …am10.ru/code.php?type=sb&jq="+am_jq+"&rand="+am_rand+"&u=18077&loc="+am_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 48, Column 67: reference not terminated by REFC delimiter
    ….ru/code.php?type=sb&jq="+am_jq+"&rand="+am_rand+"&u=18077&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 48, Column 67: reference to entity "rand" for which no system identifier could be generated
    ….ru/code.php?type=sb&jq="+am_jq+"&rand="+am_rand+"&u=18077&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 48, Column 62: entity was defined here
    …/am10.ru/code.php?type=sb&jq="+am_jq+"&rand="+am_rand+"&u=18077&loc="+am_loc+"…
  • Warning Line 48, Column 80: cannot generate system identifier for general entity "u"
    …type=sb&jq="+am_jq+"&rand="+am_rand+"&u=18077&loc="+am_loc+"&ref="+am_ref+"&ti…

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

  • Warning Line 48, Column 81: reference not terminated by REFC delimiter
    …ype=sb&jq="+am_jq+"&rand="+am_rand+"&u=18077&loc="+am_loc+"&ref="+am_ref+"&tit…

    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 48, Column 81: reference to entity "u" for which no system identifier could be generated
    …ype=sb&jq="+am_jq+"&rand="+am_rand+"&u=18077&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.

  • Info Line 48, Column 79: entity was defined here
    …?type=sb&jq="+am_jq+"&rand="+am_rand+"&u=18077&loc="+am_loc+"&ref="+am_ref+"&t…
  • Warning Line 48, Column 88: cannot generate system identifier for general entity "loc"
    …jq="+am_jq+"&rand="+am_rand+"&u=18077&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 48, Column 88: general entity "loc" not defined and no default entity
    …jq="+am_jq+"&rand="+am_rand+"&u=18077&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 48, Column 91: reference not terminated by REFC delimiter
    …"+am_jq+"&rand="+am_rand+"&u=18077&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 48, Column 91: reference to entity "loc" for which no system identifier could be generated
    …"+am_jq+"&rand="+am_rand+"&u=18077&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 48, Column 87: entity was defined here
    …&jq="+am_jq+"&rand="+am_rand+"&u=18077&loc="+am_loc+"&ref="+am_ref+"&title="+a…
  • Warning Line 48, Column 103: cannot generate system identifier for general entity "ref"
    …m_jq+"&rand="+am_rand+"&u=18077&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 48, Column 103: general entity "ref" not defined and no default entity
    …m_jq+"&rand="+am_rand+"&u=18077&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 48, Column 106: reference not terminated by REFC delimiter
    …m_jq+"&rand="+am_rand+"&u=18077&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 48, Column 106: reference to entity "ref" for which no system identifier could be generated
    …m_jq+"&rand="+am_rand+"&u=18077&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 48, Column 102: entity was defined here
    …m_jq+"&rand="+am_rand+"&u=18077&loc="+am_loc+"&ref="+am_ref+"&title="+am_title;
  • Warning Line 48, Column 118: cannot generate system identifier for general entity "title"
    …m_jq+"&rand="+am_rand+"&u=18077&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 48, Column 118: general entity "title" not defined and no default entity
    …m_jq+"&rand="+am_rand+"&u=18077&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 48, Column 123: reference not terminated by REFC delimiter
    …m_jq+"&rand="+am_rand+"&u=18077&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 48, Column 123: reference to entity "title" for which no system identifier could be generated
    …m_jq+"&rand="+am_rand+"&u=18077&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 48, Column 117: entity was defined here
    …m_jq+"&rand="+am_rand+"&u=18077&loc="+am_loc+"&ref="+am_ref+"&title="+am_title;
  • Error Line 53, Column 24: document type does not allow element "body" here
    <body class="home blog">

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

    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 90, Column 12: there is no attribute "src"
    <embed src="Hypno_Banner.swf" quality="high" type="application/x-shockwave-flas…

    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 90, Column 39: there is no attribute "quality"
    <embed src="Hypno_Banner.swf" quality="high" type="application/x-shockwave-flas…

    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 90, Column 51: there is no attribute "type"
    …Hypno_Banner.swf" quality="high" type="application/x-shockwave-flash" wmode="t…

    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 90, Column 89: there is no attribute "wmode"
    …"application/x-shockwave-flash" wmode="transparent" width="950" height="50" pl…

    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 90, Column 109: there is no attribute "width"
    …wave-flash" wmode="transparent" width="950" height="50" pluginspage="http://ww…

    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 90, Column 122: there is no attribute "height"
    …mode="transparent" width="950" height="50" pluginspage="http://www.macromedia.…

    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 90, Column 139: there is no attribute "pluginspage"
    …" width="950" height="50" pluginspage="http://www.macromedia.com/go/getflashpl…

    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 90, Column 203: there is no attribute "allowScriptAccess"
    …/go/getflashplayer" allowScriptAccess="always"></embed></div><div class="a-lay…

    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 90, Column 211: element "embed" undefined
    …lashplayer" allowScriptAccess="always"></embed></div><div class="a-layout-wrap…

    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 130, Column 77: cannot generate system identifier for general entity "f"
    …e='text/javascript' src='http://c.am11.ru/code/bn/js.php?u=18077&f=2'></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 130, Column 77: general entity "f" not defined and no default entity
    …e='text/javascript' src='http://c.am11.ru/code/bn/js.php?u=18077&f=2'></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 130, Column 78: reference not terminated by REFC delimiter
    …e='text/javascript' src='http://c.am11.ru/code/bn/js.php?u=18077&f=2'></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 130, Column 78: reference to external entity in attribute value
    …e='text/javascript' src='http://c.am11.ru/code/bn/js.php?u=18077&f=2'></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 130, Column 78: reference to entity "f" for which no system identifier could be generated
    …e='text/javascript' src='http://c.am11.ru/code/bn/js.php?u=18077&f=2'></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 130, Column 76: entity was defined here
    …e='text/javascript' src='http://c.am11.ru/code/bn/js.php?u=18077&f=2'></script>
  • Error Line 131, Column 12: end tag for element "br" which is not open
     </div></br>

    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 142, Column 168: there is no attribute "TARGET"
    …f="http://familyguyrussia.com" TARGET="_blank"><img src="http://familyguyrussi…

    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 142, Column 239: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …uyrussia.com/forums/banner.gif" width=88 height=31 border=0 title="Гриффины в …
  • Error Line 142, Column 249: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …om/forums/banner.gif" width=88 height=31 border=0 title="Гриффины в России - F…
  • Error Line 142, Column 259: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …banner.gif" width=88 height=31 border=0 title="Гриффины в России - Family Guy|…
  • Error Line 142, Column 306: required attribute "alt" not specified
    …Гриффины в России - Family Guy|Russia"><a href="http://gazetaslovo.com.ua/" TA…

    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 142, Column 307: end tag for "img" omitted, but OMITTAG NO was specified
    …риффины в России - Family Guy|Russia"><a href="http://gazetaslovo.com.ua/" TAR…

    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 142, Column 177: start tag was here
    …/familyguyrussia.com" TARGET="_blank"><img src="http://familyguyrussia.com/for…
  • Error Line 142, Column 359: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …//gazetaslovo.com.ua/" TARGET="_blank"><img src="http://filiza.ru/Slovo_banner…

    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 142, Column 411: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …p://filiza.ru/Slovo_banner.gif" width=88 height=31 border=0 title="Газета Слов…
  • Error Line 142, Column 421: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    ….ru/Slovo_banner.gif" width=88 height=31 border=0 title="Газета Слово"></a></a…
  • Error Line 142, Column 431: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …banner.gif" width=88 height=31 border=0 title="Газета Слово"></a></a><a title=…
  • Error Line 142, Column 453: required attribute "alt" not specified
    …eight=31 border=0 title="Газета Слово"></a></a><a title="Неофициальный сайт по…

    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 142, Column 457: end tag for "img" omitted, but OMITTAG NO was specified
    …t=31 border=0 title="Газета Слово"></a></a><a title="Неофициальный сайт поклон…

    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 142, Column 360: start tag was here
    …/gazetaslovo.com.ua/" TARGET="_blank"><img src="http://filiza.ru/Slovo_banner.…
  • Error Line 142, Column 600: syntax of attribute value does not conform to declared value
    …http://2x2.clan.su/knopka.gif" align="" border="0"></a><a href="http://www.fut…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 142, Column 600: value of attribute "align" cannot be ""; must be one of "top", "middle", "bottom", "left", "right"
    …http://2x2.clan.su/knopka.gif" align="" border="0"></a><a href="http://www.fut…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 142, Column 616: end tag for "img" omitted, but OMITTAG NO was specified
    …su/knopka.gif" align="" border="0"></a><a href="http://www.futuramer.ru" targe…

    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 142, Column 545: start tag was here
    …канала 2x2" href="http://2x2.clan.su"><img alt="" src="http://2x2.clan.su/knop…
  • Error Line 142, Column 806: end tag for "img" omitted, but OMITTAG NO was specified
    … width="88" height="31" border="0"></a><a title="GameShopper" href='http://www…

    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 142, Column 688: start tag was here
    … target="_blank" title="Futuramer.ru"><img src="http://www.futuramer.ru/images…
  • Error Line 142, Column 869: duplicate specification of attribute "title"
    …ref='http://www.gameshopper.ru' title='GameShopper'><img src='http://i2.fastpi…

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 142, Column 1400: end tag for "img" omitted, but OMITTAG NO was specified
    … border="0" height="31" width="88"></a></center></a><a href="http://www.2x2-fa…

    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 142, Column 1239: start tag was here
    …ref="http://south-park-online.com.ua"><img src="http://south-parkk.at.ua/knopk…
  • Error Line 142, Column 1409: end tag for element "center" which is not open
    …0" height="31" width="88"></a></center></a><a href="http://www.2x2-fan.ru/" mc…

    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 142, Column 1413: end tag for element "a" which is not open
    …eight="31" width="88"></a></center></a><a href="http://www.2x2-fan.ru/" mce_hr…

    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 142, Column 1456: there is no attribute "mce_href"
    …ref="http://www.2x2-fan.ru/" mce_href="http://www.2x2-fan.ru/" target="_blank"…

    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 142, Column 1601: there is no attribute "mce_src"
    …://www.2x2-fan.ru/banner.gif" mce_src="http://www.2x2-fan.ru/banner.gif" borde…

    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 142, Column 1669: required attribute "alt" not specified
    …gif" border="0" height="31" width="88"></a><a href="http://nice-media.ru/" tar…

    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 142, Column 1673: end tag for "img" omitted, but OMITTAG NO was specified
    … border="0" height="31" width="88"></a><a href="http://nice-media.ru/" target=…

    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 142, Column 1549: start tag was here
    ….Ru | Первый Фан Сайт Телеканала 2x2"><img src="http://www.2x2-fan.ru/banner.g…
  • Error Line 142, Column 2127: required attribute "alt" not specified
    …ng" border="0" height="31" width="264"><a href="http://fg-fan.ru" target="_bla…

    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 142, Column 2128: end tag for "img" omitted, but OMITTAG NO was specified
    …g" border="0" height="31" width="264"><a href="http://fg-fan.ru" target="_blan…

    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 142, Column 1978: start tag was here
    …альный фан-сайт телепередачи Галилео"><img src="http://filiza.ru/wp-content/th…
  • Error Line 142, Column 2170: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    … border="0" height="31" width="264"><a href="http://fg-fan.ru" target="_blank">

    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 143, Column 116: required attribute "alt" not specified
    …tom.gif" width="88" height="31" border="0" title="Все серии Гриффинов онлайн"/>

    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 144, Column 10: end tag for "a" omitted, but OMITTAG NO was specified
    </a></div>

    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 142, Column 1840: start tag was here
    …Media.ru - перевод и озвучание" /></a><a href="http://www.tv-galileo.ru/" mce_…
  • Error Line 271, Column 4: document type does not allow element "h1" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <h1> <a href="http://www.filiza.ru/2013/02/21/ad-8x11/#more-1941" class="more-l…

    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 272, Column 3: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p></span></p>

    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 272, Column 10: end tag for "p" omitted, but OMITTAG NO was specified
    <p></span></p>

    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 272, Column 1: start tag was here
    <p></span></p>
  • Error Line 295, Column 4: document type does not allow element "h1" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <h1> <a href="http://www.filiza.ru/2013/02/13/fg-11x12/#more-1938" class="more-…

    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 296, Column 3: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p></span></p>

    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 296, Column 10: end tag for "p" omitted, but OMITTAG NO was specified
    <p></span></p>

    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 296, Column 1: start tag was here
    <p></span></p>
  • Error Line 319, Column 4: document type does not allow element "h1" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <h1> <a href="http://www.filiza.ru/2013/02/01/ad-8x10/#more-1936" class="more-l…

    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 320, Column 3: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p></span></p>

    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 320, Column 10: end tag for "p" omitted, but OMITTAG NO was specified
    <p></span></p>

    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 320, Column 1: start tag was here
    <p></span></p>
  • Error Line 345, Column 4: document type does not allow element "h1" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <h1> <a href="http://www.filiza.ru/2013/01/31/ad-8x08/#more-1935" class="more-l…

    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 346, Column 3: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p></span></p>

    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 346, Column 10: end tag for "p" omitted, but OMITTAG NO was specified
    <p></span></p>

    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 346, Column 1: start tag was here
    <p></span></p>
  • Error Line 371, Column 4: document type does not allow element "h1" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <h1> <a href="http://www.filiza.ru/2013/01/30/ad-8x07/#more-1934" class="more-l…

    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 372, Column 3: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p></span></p>

    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 372, Column 10: end tag for "p" omitted, but OMITTAG NO was specified
    <p></span></p>

    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 372, Column 1: start tag was here
    <p></span></p>
  • Warning Line 441, Column 173: reference not terminated by REFC delimiter
    …cript' src='http://c.am11.ru/code/bn/js.php?u=18077&f=1'></script> </div></div>

    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 441, Column 173: reference to external entity in attribute value
    …cript' src='http://c.am11.ru/code/bn/js.php?u=18077&f=1'></script> </div></div>

    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 441, Column 173: reference to entity "f" for which no system identifier could be generated
    …cript' src='http://c.am11.ru/code/bn/js.php?u=18077&f=1'></script> </div></div>

    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 130, Column 76: entity was defined here
    …e='text/javascript' src='http://c.am11.ru/code/bn/js.php?u=18077&f=2'></script>
  • Warning Line 463, Column 174: reference not terminated by REFC delimiter
    …script" src="http://c.am11.ru/code/bn/js.php?u=18077&f=7"></script></div></div>

    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 463, Column 174: reference to external entity in attribute value
    …script" src="http://c.am11.ru/code/bn/js.php?u=18077&f=7"></script></div></div>

    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 463, Column 174: reference to entity "f" for which no system identifier could be generated
    …script" src="http://c.am11.ru/code/bn/js.php?u=18077&f=7"></script></div></div>

    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 130, Column 76: entity was defined here
    …e='text/javascript' src='http://c.am11.ru/code/bn/js.php?u=18077&f=2'></script>
  • Error Line 521, Column 7: end tag for "body" omitted, but OMITTAG NO was specified
    </html>

    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 39, Column 1: start tag was here
    <script type="text/javascript">

Visitor Analysis

Daily Visitor
  • 502 visits
Daily Visitor