serialu.net

Все сериалы бесплатно и без регистрации. Заходим и смотрим. ...

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

Overview Info

  • Domain Name
    serialu.net
  • Favicon
  • Alexa Rank
    #3759
  • Google Page Rank
    PR 6
  • Ip Address
    5.153.25.5
  • Page Size
    107.5 KB
  • Images
    2 GIF, 11 JPG, 3 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 8 0 0 0 0

Website Meta Analysis



  • Title
    Сериалы онлайн смотреть бесплатно. Русские и зарубежные. serialu.net
  • Meta Keyword
    �������,������,�����������,����������,�������,��������,�����,��������,�������,���������
  • Meta Description
    Все сериалы бесплатно и без регистрации. Заходим и смотрим.

Technical Analysis



  • Webserver
    nginx/1.2.7
  • Ip Address
    5.153.25.5
  • Domain Age
    3 Years, 1 Months, 8 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from serialu.net.

HTML Analysis

  • server: nginx/1.2.7
  • date: Tue, 17 Sep 2013 19:51:56 GMT
  • content-type: text/html; charset=UTF-8
  • connection: keep-alive
  • vary: Accept-Encoding
  • x-powered-by: PHP/5.3.26-1~dotdeb.0
  • x-pingback: http://serialu.net/xmlrpc.php
  • x-frame-options: sameorigin
  • x-xss-protection: 1; mode=block
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: SERIALU.NET

Registrant:
PrivacyProtect.org
Domain Admin ( email )
ID#10760, PO Box 16
Note - All Postal Mails Rejected, visit Privacyprotect.org
Nobby Beach
null,QLD 4218
AU
Tel. +45.36946676

Creation Date: 27-Jul-2010
Expiration Date: 27-Jul-2013

Domain servers in listed order:
ns1.reg.ru
ns2.reg.ru


Administrative Contact:
PrivacyProtect.org
Domain Admin ( email )
ID#10760, PO Box 16
Note - All Postal Mails Rejected, visit Privacyprotect.org
Nobby Beach
null,QLD 4218
AU
Tel. +45.36946676

Technical Contact:
PrivacyProtect.org
Domain Admin ( email )
ID#10760, PO Box 16
Note - All Postal Mails Rejected, visit Privacyprotect.org
Nobby Beach
null,QLD 4218
AU
Tel. +45.36946676

Billing Contact:
PrivacyProtect.org
Domain Admin ( email )
ID#10760, PO Box 16
Note - All Postal Mails Rejected, visit Privacyprotect.org
Nobby Beach
null,QLD 4218
AU
Tel. +45.36946676

Status:LOCKED

DNS Analysis


DNS servers
ns1.reg.ru [31.31.204.52]
ns2.reg.ru [88.212.207.122]

DNS Records

Answer records
serialu.net SOA
server: ns1.reg.ru
email: hostmaster@ns1.reg.ru
serial: 1343278174
refresh: 14400
retry: 3600
expire: 604800
minimum ttl: 21600
43200s
serialu.net NS  ns2.reg.ru 43200s
serialu.net A 93.190.40.154 43200s
serialu.net NS  ns1.reg.ru 43200s

Authority records

Additional records

IP 5.153.25.5 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 4 Errors
  • 4 Warnings
Ratio Text/Html
  • 0.5068463278786832
Message Error
  • Error Line 44, Column 30: there is no attribute "TARGET"
      <div class="h-m"><a TARGET="_blank" href="http://fepcom.net/filmy-onlajn/">Фи…

    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 56, Column 152: required attribute "alt" not specified
    …oisk_pic.jpg" style="position:absolute; margin-left:-47px; margin-top:-6px;" />

    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 58, Column 291: end tag for "input" omitted, but OMITTAG NO was specified
    …er-right:0; border-bottom:0; text-align: center; width: 142px; color:#c3c3c3;">

    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 58, Column 7: start tag was here
          <input type="text" name="s" value="Поиск" onfocus="if (value == 'Поиск') …
  • Error Line 59, Column 56: end tag for "input" omitted, but OMITTAG NO was specified
          <input type="submit" class="top_submit" value="">

    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 59, Column 7: start tag was here
          <input type="submit" class="top_submit" value="">
  • Error Line 60, Column 130: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ner.com/serialunet?format=xml" target=_blank title="Читать полный RSS сайта"><…
  • Error Line 60, Column 251: an attribute specification must start with a name or name token
    …http://serialu.net/img/feed-icon16x16.png" alt="Читать полный RSS сайта""/></a>

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

  • Error Line 60, Column 252: end tag for "img" omitted, but OMITTAG NO was specified
    …http://serialu.net/img/feed-icon16x16.png" alt="Читать полный RSS сайта""/></a>

    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 60, Column 169: start tag was here
    …blank title="Читать полный RSS сайта"><img src="http://serialu.net/img/feed-ic…
  • Error Line 67, Column 31: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
          <span class="h-motto"><p>Смотреть сериалы онлайн бесплатно</p></span> <!-…

    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 74, Column 137: end tag for "input" omitted, but OMITTAG NO was specified
    …solid #a9a9a9; padding: 3px; text-align: center; width: 169px; color:#c3c3c3;">

    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 74, Column 7: start tag was here
          <input type="text" name="email" style="border: 1px solid #a9a9a9; padding…
  • Error Line 75, Column 58: end tag for "input" omitted, but OMITTAG NO was specified
          <input type="hidden" name="uri" value="serialunet">

    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 75, Column 7: start tag was here
          <input type="hidden" name="uri" value="serialunet">
  • Error Line 76, Column 53: end tag for "input" omitted, but OMITTAG NO was specified
          <input type="hidden" value="ru_RU" name="loc">

    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 76, Column 7: start tag was here
          <input type="hidden" value="ru_RU" name="loc">
  • Error Line 77, Column 52: end tag for "input" omitted, but OMITTAG NO was specified
          <input type="submit" class="submit" value="">

    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 77, Column 7: start tag was here
          <input type="submit" class="submit" value="">
  • Warning Line 83, Column 62: cannot generate system identifier for general entity "url"
    …enta.yandex.ru/settings.xml?name=feed&url=http://feeds.feedburner.com/serialun…

    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 83, Column 62: general entity "url" not defined and no default entity
    …enta.yandex.ru/settings.xml?name=feed&url=http://feeds.feedburner.com/serialun…

    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 83, Column 65: reference not terminated by REFC delimiter
    …a.yandex.ru/settings.xml?name=feed&url=http://feeds.feedburner.com/serialunet"…

    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 83, Column 65: reference to external entity in attribute value
    …a.yandex.ru/settings.xml?name=feed&url=http://feeds.feedburner.com/serialunet"…

    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 83, Column 65: reference to entity "url" for which no system identifier could be generated
    …a.yandex.ru/settings.xml?name=feed&url=http://feeds.feedburner.com/serialunet"…

    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 83, Column 61: entity was defined here
    …lenta.yandex.ru/settings.xml?name=feed&url=http://feeds.feedburner.com/serialu…
  • Error Line 83, Column 113: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …eds.feedburner.com/serialunet" target=_blank title="Читать Сериалы RSS в Яндек…
  • Error Line 83, Column 260: an attribute specification must start with a name or name token
    …p://serialu.net/img/addfeed.gif" alt="Читать Сериалы RSS в Яндекс ленте""/></a>

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

  • Error Line 83, Column 261: end tag for "img" omitted, but OMITTAG NO was specified
    …p://serialu.net/img/addfeed.gif" alt="Читать Сериалы RSS в Яндекс ленте""/></a>

    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 83, Column 175: start tag was here
    …иалы RSS в Яндекс ленте" class="feed"><img src="http://serialu.net/img/addfeed…
  • Error Line 84, Column 100: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …eds.feedburner.com/serialunet" target=_blank title="Читать Сериалы RSS в Googl…
  • Error Line 84, Column 267: an attribute specification must start with a name or name token
    …"http://serialu.net/img/add.gif" alt="Читать Сериалы RSS в Google ленте""/></a>

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

  • Error Line 84, Column 268: end tag for "img" omitted, but OMITTAG NO was specified
    …"http://serialu.net/img/add.gif" alt="Читать Сериалы RSS в Google ленте""/></a>

    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 84, Column 162: start tag was here
    …иалы RSS в Google ленте" class="feed"><img style="margin-top:3px;" src="http:/…
  • Error Line 88, Column 74: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ner.com/serialunet?format=xml" target=_blank title="Читать полный RSS сайта" c…
  • Error Line 88, Column 232: an attribute specification must start with a name or name token
    …eed-icon16x16.png" alt="Читать полный RSS сайта""/>  RSS лента всех записей</a>

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

  • Error Line 88, Column 233: end tag for "img" omitted, but OMITTAG NO was specified
    …eed-icon16x16.png" alt="Читать полный RSS сайта""/>  RSS лента всех записей</a>

    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 88, Column 126: start tag was here
    …Читать полный RSS сайта" class="feed"><img style="margin-top:3px;" src="http:/…
  • Error Line 94, Column 45: element "noindex" undefined
    …						<div class="textwidget"><noindex><nofollow><script type='text/javascript…

    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 94, Column 55: element "nofollow" undefined
    … class="textwidget"><noindex><nofollow><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).
  • Warning Line 94, Column 132: cannot generate system identifier for general entity "f"
    …tp://c.am11.ru/code/bn/js.php?u=18256&f=3'></script></nofollow></noindex></div…

    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 94, Column 132: general entity "f" not defined and no default entity
    …tp://c.am11.ru/code/bn/js.php?u=18256&f=3'></script></nofollow></noindex></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.

  • Warning Line 94, Column 133: reference not terminated by REFC delimiter
    …tp://c.am11.ru/code/bn/js.php?u=18256&f=3'></script></nofollow></noindex></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 94, Column 133: reference to external entity in attribute value
    …tp://c.am11.ru/code/bn/js.php?u=18256&f=3'></script></nofollow></noindex></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 94, Column 133: reference to entity "f" for which no system identifier could be generated
    …tp://c.am11.ru/code/bn/js.php?u=18256&f=3'></script></nofollow></noindex></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 94, Column 131: entity was defined here
    …ttp://c.am11.ru/code/bn/js.php?u=18256&f=3'></script></nofollow></noindex></di…
  • Error Line 1320, Column 151: element "noindex" undefined
    …дуем</div><div class="c-content">			<div class="textwidget"><noindex><nofollow>

    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 1320, Column 161: element "nofollow" undefined
    …дуем</div><div class="c-content">			<div class="textwidget"><noindex><nofollow>

    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 1321, Column 94: there is no attribute "async"
    …src='http://static.recreativ.ru/js/jquery-1.6.2.min.js' async='async'></script>

    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 1323, Column 36: there is no attribute "SRC"
    <script type='text/javascript' SRC='http://recreativ.ru/rcode.1dfrSzR6Oi.js' de…

    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 1325, Column 160: element "noindex" undefined
    …t">			<div class="textwidget"><noindex><nofollow><div id="PC_Teaser_Block_6101…

    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 1325, Column 170: element "nofollow" undefined
    … class="textwidget"><noindex><nofollow><div id="PC_Teaser_Block_61013" class="…

    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 1326, Column 238: end tag for "br" omitted, but OMITTAG NO was specified
    …bshhaga/">Универ. Новая общага</a><br> <img SRC="http://img.serialu.net/wp-con…

    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 1326, Column 234: start tag was here
    …ya-obshhaga/">Универ. Новая общага</a><br> <img SRC="http://img.serialu.net/wp…
  • Error Line 1326, Column 248: there is no attribute "SRC"
    …Универ. Новая общага</a><br> <img SRC="http://img.serialu.net/wp-content/uploa…

    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 1326, Column 338: required attribute "src" not specified
    …alu.net/wp-content/uploads/2011/10/16805882.jpg" height="275" width="198" ><br>

    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 1326, Column 338: required attribute "alt" not specified
    …alu.net/wp-content/uploads/2011/10/16805882.jpg" height="275" width="198" ><br>

    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 1326, Column 339: end tag for "img" omitted, but OMITTAG NO was specified
    …alu.net/wp-content/uploads/2011/10/16805882.jpg" height="275" width="198" ><br>

    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 1326, Column 239: start tag was here
    …shhaga/">Универ. Новая общага</a><br> <img SRC="http://img.serialu.net/wp-cont…
  • Error Line 1326, Column 343: end tag for "br" omitted, but OMITTAG NO was specified
    …alu.net/wp-content/uploads/2011/10/16805882.jpg" height="275" width="198" ><br>

    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 1326, Column 339: start tag was here
    …alu.net/wp-content/uploads/2011/10/16805882.jpg" height="275" width="198" ><br>
  • Error Line 1328, Column 72: end tag for "br" omitted, but OMITTAG NO was specified
    …olepnyj-vek/">Великолепный век</a><br> <img SRC="http://img.serialu.net/img/61…

    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 1328, Column 68: start tag was here
    …elikolepnyj-vek/">Великолепный век</a><br> <img SRC="http://img.serialu.net/im…
  • Error Line 1328, Column 147: required attribute "src" not specified
    …<img SRC="http://img.serialu.net/img/610422.jpg" height="275" width="198" ><br>

    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 1328, Column 147: required attribute "alt" not specified
    …<img SRC="http://img.serialu.net/img/610422.jpg" height="275" width="198" ><br>

    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 1328, Column 148: end tag for "img" omitted, but OMITTAG NO was specified
    …<img SRC="http://img.serialu.net/img/610422.jpg" height="275" width="198" ><br>

    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 1328, Column 73: start tag was here
    …lepnyj-vek/">Великолепный век</a><br> <img SRC="http://img.serialu.net/img/610…
  • Error Line 1328, Column 152: end tag for "br" omitted, but OMITTAG NO was specified
    …<img SRC="http://img.serialu.net/img/610422.jpg" height="275" width="198" ><br>

    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 1328, Column 148: start tag was here
    …<img SRC="http://img.serialu.net/img/610422.jpg" height="275" width="198" ><br>
  • Error Line 1330, Column 82: end tag for "br" omitted, but OMITTAG NO was specified
    …a-4-sezon/">Дневники Вампира 4</a><br> <img SRC="http://img.serialu.net/wp-con…

    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 1330, Column 78: start tag was here
    …mpira-4-sezon/">Дневники Вампира 4</a><br> <img SRC="http://img.serialu.net/wp…
  • Error Line 1330, Column 192: required attribute "src" not specified
    …-content/uploads/2012/10/1327340096_vampiry.jpg" height="275" width="198" ><br>

    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 1330, Column 192: required attribute "alt" not specified
    …-content/uploads/2012/10/1327340096_vampiry.jpg" height="275" width="198" ><br>

    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 1330, Column 193: end tag for "img" omitted, but OMITTAG NO was specified
    …-content/uploads/2012/10/1327340096_vampiry.jpg" height="275" width="198" ><br>

    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 1330, Column 83: start tag was here
    …-4-sezon/">Дневники Вампира 4</a><br> <img SRC="http://img.serialu.net/wp-cont…
  • Error Line 1330, Column 197: end tag for "br" omitted, but OMITTAG NO was specified
    …-content/uploads/2012/10/1327340096_vampiry.jpg" height="275" width="198" ><br>

    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 1330, Column 193: start tag was here
    …-content/uploads/2012/10/1327340096_vampiry.jpg" height="275" width="198" ><br>
  • Error Line 1332, Column 91: end tag for "br" omitted, but OMITTAG NO was specified
    …n/">Сверхъестественное 8 сезон</a><br> <img SRC="http://img.serialu.net/wp-con…

    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 1332, Column 87: start tag was here
    …sezon/">Сверхъестественное 8 сезон</a><br> <img SRC="http://img.serialu.net/wp…
  • Error Line 1332, Column 192: required attribute "src" not specified
    …lu.net/wp-content/uploads/2012/10/134937700.jpg" height="275" width="198" ><br>

    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 1332, Column 192: required attribute "alt" not specified
    …lu.net/wp-content/uploads/2012/10/134937700.jpg" height="275" width="198" ><br>

    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 1332, Column 193: end tag for "img" omitted, but OMITTAG NO was specified
    …lu.net/wp-content/uploads/2012/10/134937700.jpg" height="275" width="198" ><br>

    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 1332, Column 92: start tag was here
    …/">Сверхъестественное 8 сезон</a><br> <img SRC="http://img.serialu.net/wp-cont…
  • Error Line 1332, Column 197: end tag for "br" omitted, but OMITTAG NO was specified
    …lu.net/wp-content/uploads/2012/10/134937700.jpg" height="275" width="198" ><br>

    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 1332, Column 193: start tag was here
    …lu.net/wp-content/uploads/2012/10/134937700.jpg" height="275" width="198" ><br>
  • Error Line 1334, Column 74: end tag for "br" omitted, but OMITTAG NO was specified
    …yu-5-sezon/">За гранью 5 сезон</a><br> <img SRC="http://img.serialu.net/wp-con…

    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 1334, Column 70: start tag was here
    …granyu-5-sezon/">За гранью 5 сезон</a><br> <img SRC="http://img.serialu.net/wp…
  • Error Line 1334, Column 182: required attribute "src" not specified
    …tent/uploads/2012/10/6398263_52b27ae0.jpg" height="275" width="198" ><br></div>

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

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

  • Error Line 1334, Column 182: required attribute "alt" not specified
    …tent/uploads/2012/10/6398263_52b27ae0.jpg" height="275" width="198" ><br></div>

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

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

  • Error Line 1334, Column 183: end tag for "img" omitted, but OMITTAG NO was specified
    …tent/uploads/2012/10/6398263_52b27ae0.jpg" height="275" width="198" ><br></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 1334, Column 75: start tag was here
    …u-5-sezon/">За гранью 5 сезон</a><br> <img SRC="http://img.serialu.net/wp-cont…
  • Error Line 1334, Column 192: end tag for "br" omitted, but OMITTAG NO was specified
    …tent/uploads/2012/10/6398263_52b27ae0.jpg" height="275" width="198" ><br></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 1334, Column 183: start tag was here
    …tent/uploads/2012/10/6398263_52b27ae0.jpg" height="275" width="198" ><br></div>
  • Error Line 1346, Column 35: end tag for "br" omitted, but OMITTAG NO was specified
          &copy; SERIALU.NET 2010 <br> Все права защищены. 

    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 1346, Column 31: start tag was here
          &copy; SERIALU.NET 2010 <br> Все права защищены. 
  • Error Line 1348, Column 35: element "noindex" undefined
        <div class="f-widget"><noindex><nofollow><!--LiveInternet counter--><script…

    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 1348, Column 45: element "nofollow" undefined
    …iv class="f-widget"><noindex><nofollow><!--LiveInternet counter--><script type…

    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 1362, Column 11: end tag for element "ul" which is not open
    						</ul>

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

    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 1371, Column 19: element "nofollow" undefined
    <noindex><nofollow>

    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 1376, Column 22: an attribute specification must start with a name or name token
     document.write('<scr'+'ipt type="text/javascript" '

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

  • Error Line 1376, Column 22: element "scr" undefined
     document.write('<scr'+'ipt type="text/javascript" '

    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 1377, Column 181: delimiter "'" invalid: only S separators and TAGC allowed here
    …GidDate.getDay()+MarketGidDate.getHours() + '" charset="utf-8" ></scr'+'ipt>');

Visitor Analysis

Daily Visitor
  • 28.000 visits

In Page Analysis