Lex.bg - Българският правен портал ...

lex.bg
  • Domain Name
    lex.bg
  • Favicon
  • Google Page Rank
    7
  • Alexa Rank
    #103928
  • Page Size
    63.7 KB
  • Ip Address
    94.156.102.51
  • Heading
    H1: 10, H2: 1, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 8 JPG, 25 PNG

Website Meta Analysis

  • Title
    Lex.bg - Българският правен портал
  • Meta Keyword
    право,закони,правен портал,юридически справочник,държавен вестник,нормативни актове,правни семинари,законодателство,работа за юристи, новини,форум
  • Meta Description
    Lex.bg - Българският правен портал

Technical Analysis

  • Webserver
    Apache/2.2.9
  • Ip Address
    94.156.102.51
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from lex.bg.

HTML Analysis

  • server: Apache/2.2.9
  • x-powered-by: PHP/5.2.6-1+lenny13
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-type: text/html
  • content-length: 14374
  • accept-ranges: bytes
  • date: Fri, 01 Mar 2013 11:42:19 GMT
  • age: 0
  • connection: close
  • x-cache: miss
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

DOMAIN NAME: lex.bg
requested on: 26/02/2001 00:00:00 EET
processed from: 26/02/2001 00:00:00 EET
activated on: 27/02/2001 00:00:00 EET
expires at: 27/02/2013 00:00:00 EET
registration status: Registered

REGISTRANT:
Lex.BG AD
bul. P. Evtimiy 36, vh. B, Sofiya
SOFIA, 1000
BULGARIA

ADMINISTRATIVE CONTACT:
Tatiana Stefanova
email
Leks.BG AD
36B Patriarh Evtimiy blvd., entr. B
SOFIA, 1000
BULGARIA
tel: +359 2 986 96 96
fax: +359 2 986 96 95
NIC handle: TS12548

TECHNICAL CONTACT(S):

Soyan Frantzov
email
Lex.BG PLC
36 P. Evtimii blvd., BG-1000 Sofia
SOFIA, 1000
BULGARIA
tel: +359 2 986 96 96
fax: +359 2 986 96 95
NIC handle: SF168593

NAME SERVER INFORMATION:
ns2.darikspace.com
ns1.darikspace.com

DNSSEC: Inactive

DNS Analysis


DNS servers
ns2.darikspace.com [93.123.36.86]
ns1.darikspace.com [93.123.36.85]

DNS Records

Answer records
lex.bg SOA
server: ns1.darikspace.com
email: root@lex.bg
serial: 2012033001
refresh: 7200
retry: 3600
expire: 1209600
minimum ttl: 900
28800s
lex.bg TXT v=spf1 mx ip4:94.156.102.79/32 ip4:93.123.36.82/32 ?all 28800s
lex.bg A 94.156.102.51 28800s
lex.bg MX
preference: 10
exchange: mail1.lex.bg
28800s
lex.bg NS  ns2.darikspace.com 28800s
lex.bg NS  ns1.darikspace.com 28800s

Authority records

Additional records
mail1.lex.bg A 94.156.102.79 28800s
ns1.darikspace.com A 93.123.36.85 28800s
ns2.darikspace.com A 93.123.36.86 28800s

IP 94.156.102.51 Analysis

  • Country Code
    BG
  • Country Code3
    BGR
  • Country Name
    Bulgaria
  • City
    EU
  • Continent Code
    43° North
  • Latitude
    25.
  • Longitude
  • No whois ip data for 94.156.102.51

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 65 Errors
  • 9 Warnings
Ratio Text/Html
  • 0.6047124429328676
Message Error
  • Error Line 11, Column 17: there is no attribute "property"
    	<meta property="fb:app_id" content="105231989568955" /> 

    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 23, Column 105: invalid comment declaration: found name character outside comment but inside comment declaration
    …bg/assets/css/search.css" rel="stylesheet" type="text/css" media="screen" /--->
  • Info Line 23, Column 2: comment declaration started here
    	<!--link href="http://lex.bg/assets/css/search.css" rel="stylesheet" type="tex…
  • Error Line 23, Column 106: character data is not allowed here
    …bg/assets/css/search.css" rel="stylesheet" type="text/css" media="screen" /--->

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 50, Column 104: end tag for "link" omitted, but OMITTAG NO was specified
    …webresearch.bg/survey/js/jquery.colorbox.css" rel="stylesheet" type="text/css">

    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 50, Column 2: start tag was here
    	<link href="http://www.webresearch.bg/survey/js/jquery.colorbox.css" rel="styl…
  • Error Line 51, Column 74: required attribute "type" not specified
    …ript src="http://www.webresearch.bg/survey/js/jquery.colorbox-min.js"></script>

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

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

  • Warning Line 142, Column 26: character "<" is the first character of a delimiter but occurred as data
              if (data.length<1)

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 197, Column 11: required attribute "type" not specified
    				<style>

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

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

  • Error Line 197, Column 11: document type does not allow element "style" here
    				<style>

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 235, Column 227: end tag for "input" omitted, but OMITTAG NO was specified
    …x 5px" /><br/><input type="hidden" name="redirect_login" id="f_redirect_login">

    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 235, Column 162: start tag was here
    …25px; padding:0px 5px 0px 5px" /><br/><input type="hidden" name="redirect_logi…
  • Error Line 315, Column 81: document type does not allow element "link" here
    …ink rel="stylesheet" type="text/css" href="/assets/css/jquery.multiselect.css">

    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 315, Column 82: end tag for "link" omitted, but OMITTAG NO was specified
    …ink rel="stylesheet" type="text/css" href="/assets/css/jquery.multiselect.css">

    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 315, Column 1: start tag was here
    <link rel="stylesheet" type="text/css" href="/assets/css/jquery.multiselect.css…
  • Error Line 316, Column 23: document type does not allow element "style" here
    <style type="text/css">

    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 553, Column 51: there is no attribute "autocomplete"
    …search1_txt" type="text" autocomplete="off" tabindex="1" name="searchBox" valu…

    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 646, Column 39: there is no attribute "rel"
    					<div class="tab-header-bold" rel="all"><span class="sprite sprite1"></span…

    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 660, Column 72: end tag for "input" omitted, but OMITTAG NO was specified
    …		<input type="radio" name="news_type" value="1" checked="checked"> <b>общи</b>

    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 660, Column 7: start tag was here
    						<input type="radio" name="news_type" value="1" checked="checked"> <b>общи…
  • Error Line 682, Column 73: end tag for "input" omitted, but OMITTAG NO was specified
    …        <input type="radio" name="news_type" value="2" > <b>регионални</b></li>

    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 682, Column 25: start tag was here
                            <input type="radio" name="news_type" value="2" > <b>рег…
  • Error Line 682, Column 95: end tag for element "li" which is not open
    …        <input type="radio" name="news_type" value="2" > <b>регионални</b></li>

    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 747, Column 72: end tag for "input" omitted, but OMITTAG NO was specified
    …				<td><input type="checkbox" name="sprav_filter[]" value="laws" > закони</td>

    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 747, Column 13: start tag was here
    								<td><input type="checkbox" name="sprav_filter[]" value="laws" > закони<…
  • Error Line 748, Column 72: end tag for "input" omitted, but OMITTAG NO was specified
    …			<td><input type="checkbox" name="sprav_filter[]" value="code" > кодекси</td>

    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 748, Column 13: start tag was here
    								<td><input type="checkbox" name="sprav_filter[]" value="code" > кодекси…
  • Error Line 749, Column 72: end tag for "input" omitted, but OMITTAG NO was specified
    …<td><input type="checkbox" name="sprav_filter[]" value="regs" > правилници</td>

    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 749, Column 13: start tag was here
    								<td><input type="checkbox" name="sprav_filter[]" value="regs" > правилн…
  • Error Line 752, Column 79: end tag for "input" omitted, but OMITTAG NO was specified
    …ut type="checkbox" name="sprav_filter[]" value="konstitucia" > конституция</td>

    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 752, Column 13: start tag was here
    								<td><input type="checkbox" name="sprav_filter[]" value="konstitucia" > …
  • Error Line 753, Column 96: end tag for "input" omitted, but OMITTAG NO was specified
    …   <td><input type="checkbox" name="sprav_filter[]" value="ords" > наредби</td>

    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 753, Column 37: start tag was here
                                    <td><input type="checkbox" name="sprav_filter[]…
  • Error Line 754, Column 94: end tag for "input" omitted, but OMITTAG NO was specified
    …          <td><input type="checkbox" name="sprav_filter[]" value="dv" > ДВ</td>

    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 754, Column 37: start tag was here
                                    <td><input type="checkbox" name="sprav_filter[]…
  • Error Line 882, Column 76: end tag for "input" omitted, but OMITTAG NO was specified
    …td><input type="checkbox" name="sprav_filter1[]" value="obrazci" > образци</td>

    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 882, Column 13: start tag was here
    								<td><input type="checkbox" name="sprav_filter1[]" value="obrazci" > обр…
  • Error Line 883, Column 87: end tag for "input" omitted, but OMITTAG NO was specified
    …="2"><input type="checkbox" name="sprav_filter1[]" value="blanki" > бланки</td>

    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 883, Column 25: start tag was here
    								<td colspan="2"><input type="checkbox" name="sprav_filter1[]" value="bl…
  • Error Line 998, Column 96: required attribute "alt" not specified
    … style="margin-right: 6px;" src="http://lex.bg/upload/news/51499_thumb2.jpg" />

    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 1129, Column 34: an attribute value specification must start with a literal or a name character
    						<a class="rlink bold" href=="http://lex.bg/bg/guide#nav3" title="Образци"…
  • Error Line 1187, Column 10: end tag for "div" omitted, but OMITTAG NO was specified
    					</li>

    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 1186, Column 61: start tag was here
    						<div class="lip date">София, ч.л., <em>01.03.2013</em><div>
  • Error Line 1187, Column 10: end tag for "div" omitted, but OMITTAG NO was specified
    					</li>

    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 1186, Column 7: start tag was here
    						<div class="lip date">София, ч.л., <em>01.03.2013</em><div>
  • Error Line 1193, Column 10: end tag for "div" omitted, but OMITTAG NO was specified
    					</li>

    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 1192, Column 60: start tag was here
    						<div class="lip date">София, чси, <em>28.02.2013</em><div>
  • Error Line 1193, Column 10: end tag for "div" omitted, but OMITTAG NO was specified
    					</li>

    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 1192, Column 7: start tag was here
    						<div class="lip date">София, чси, <em>28.02.2013</em><div>
  • Error Line 1199, Column 10: end tag for "div" omitted, but OMITTAG NO was specified
    					</li>

    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 1198, Column 60: start tag was here
    						<div class="lip date">Варна, ВОС, <em>25.02.2013</em><div>
  • Error Line 1199, Column 10: end tag for "div" omitted, but OMITTAG NO was specified
    					</li>

    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 1198, Column 7: start tag was here
    						<div class="lip date">Варна, ВОС, <em>25.02.2013</em><div>
  • Error Line 1452, Column 63: duplicate specification of attribute "class"
    …ght" href="http://lex.bg/forum" class="all">Посети форума <img src="http://lex…

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

  • Error Line 1464, Column 42: there is no attribute "data-href"
    …			<div class="fb-like-box" data-href="http://www.facebook.com/#!/pages/LEXBG-…

    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 1464, Column 251: there is no attribute "data-width"
    …%B0%D0%BB/252700991422690" data-width="300" data-show-faces="true" data-stream…

    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 1464, Column 273: there is no attribute "data-show-faces"
    …690" data-width="300" data-show-faces="true" data-stream="false" data-header="…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 1464, Column 292: there is no attribute "data-stream"
    …idth="300" data-show-faces="true" data-stream="false" data-header="true"></div>

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 1464, Column 312: there is no attribute "data-header"
    …idth="300" data-show-faces="true" data-stream="false" data-header="true"></div>

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 1468, Column 20: there is no attribute "href"
    						<g:plus href="https://plus.google.com/116192933107688046495" size="badge"…

    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 1468, Column 73: there is no attribute "size"
    …lus href="https://plus.google.com/116192933107688046495" size="badge"></g:plus>

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 1468, Column 80: element "g:plus" undefined
    …lus href="https://plus.google.com/116192933107688046495" size="badge"></g:plus>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1478, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 1478, Column 1: start tag was here
    <br>- Господин съдия, ако човек е бил осъждан осемнадесет пъти досега, то той н…
  • Error Line 1479, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 1479, Column 1: start tag was here
    <br>- А какъв е според вас?
  • Error Line 1480, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 1480, Column 1: start tag was here
    <br>- Колекционер на присъди.
  • Error Line 1481, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>						</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 1481, Column 1: start tag was here
    <br>						</p>
  • Error Line 1521, Column 17: end tag for "br" omitted, but OMITTAG NO was specified
    <br clear="all">

    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 1521, Column 1: start tag was here
    <br clear="all">
  • Warning Line 1539, Column 39: character "<" is the first character of a delimiter but occurred as data
    if ( $("#div_onfocus_right").height() < ($("#div_onfocus_left").height())) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 1545, Column 6: end tag for element "div" which is not open
    </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 1546, Column 6: end tag for element "div" which is not open
    </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 1602, Column 15: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    			<font size=1><script type="text/javascript" language="javascript"><!--
  • Error Line 1614, Column 32: document type does not allow element "noscript" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    			t(); //--></script><noscript><img width=1 height=1 border=0 alt=""

    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 1614, Column 44: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    			t(); //--></script><noscript><img width=1 height=1 border=0 alt=""
  • Error Line 1614, Column 53: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    			t(); //--></script><noscript><img width=1 height=1 border=0 alt=""
  • Error Line 1614, Column 62: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    			t(); //--></script><noscript><img width=1 height=1 border=0 alt=""
  • Warning Line 1615, Column 54: cannot generate system identifier for general entity "_z"
    …	src="http://counter.search.bg/cgi-bin/c?_id=lexbg&_z=0"></noscript></a></font>

    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 1615, Column 54: general entity "_z" not defined and no default entity
    …	src="http://counter.search.bg/cgi-bin/c?_id=lexbg&_z=0"></noscript></a></font>

    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 1615, Column 56: reference not terminated by REFC delimiter
    …	src="http://counter.search.bg/cgi-bin/c?_id=lexbg&_z=0"></noscript></a></font>

    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 1615, Column 56: reference to external entity in attribute value
    …	src="http://counter.search.bg/cgi-bin/c?_id=lexbg&_z=0"></noscript></a></font>

    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 1615, Column 56: reference to entity "_z" for which no system identifier could be generated
    …	src="http://counter.search.bg/cgi-bin/c?_id=lexbg&_z=0"></noscript></a></font>

    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 1615, Column 53: entity was defined here
    …	src="http://counter.search.bg/cgi-bin/c?_id=lexbg&_z=0"></noscript></a></font>
  • Error Line 1615, Column 70: end tag for "img" omitted, but OMITTAG NO was specified
    …	src="http://counter.search.bg/cgi-bin/c?_id=lexbg&_z=0"></noscript></a></font>

    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 1614, Column 33: start tag was here
    			t(); //--></script><noscript><img width=1 height=1 border=0 alt=""
  • Warning Line 1619, Column 4: character "<" is the first character of a delimiter but occurred as data
    			<!- NACHALO NA TYXO.BG BROYACH -->

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 1620, Column 95: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …o.bg/?590" title="Tyxo.bg counter" target="_blank"><script language=JavaScript>
  • Error Line 1620, Column 105: required attribute "type" not specified
    …o.bg/?590" title="Tyxo.bg counter" target="_blank"><script language=JavaScript>

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

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

  • Error Line 1626, Column 22: document type does not allow element "noscript" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    			</script><noscript><img src="http://cnt.tyxo.bg/590" width=80 height=15 bord…

    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 1626, Column 63: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …/script><noscript><img src="http://cnt.tyxo.bg/590" width=80 height=15 border=0
  • Error Line 1626, Column 73: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …/script><noscript><img src="http://cnt.tyxo.bg/590" width=80 height=15 border=0
  • Error Line 1626, Column 83: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …/script><noscript><img src="http://cnt.tyxo.bg/590" width=80 height=15 border=0
  • Warning Line 1628, Column 4: character "<" is the first character of a delimiter but occurred as data
    			<!- KRAI NA TYXO.BG BROYACH -->

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 1650, Column 8: required attribute "type" not specified
    <script>(function(d, s, id) {

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

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

  • Warning Line 1654, Column 57: cannot generate system identifier for general entity "appId"
      js.src = "//connect.facebook.net/bg_BG/all.js#xfbml=1&appId=105231989568955";

    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 1654, Column 57: general entity "appId" not defined and no default entity
      js.src = "//connect.facebook.net/bg_BG/all.js#xfbml=1&appId=105231989568955";

    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 1654, Column 62: reference not terminated by REFC delimiter
      js.src = "//connect.facebook.net/bg_BG/all.js#xfbml=1&appId=105231989568955";

    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 1654, Column 62: reference to entity "appId" for which no system identifier could be generated
      js.src = "//connect.facebook.net/bg_BG/all.js#xfbml=1&appId=105231989568955";

    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 1654, Column 56: entity was defined here
      js.src = "//connect.facebook.net/bg_BG/all.js#xfbml=1&appId=105231989568955";

Visitor Analysis

Daily Visitor
  • 1.983 visits
Daily Visitor