Корпоративният уебсайт на GLOBUL, с актуална информация за мобилните и фиксирани телекомуникационни услуги на оператора. ...

globul.bg
  • Domain Name
    globul.bg
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #48380
  • Page Size
    60.5 KB
  • Ip Address
    85.118.192.33
  • Heading
    H1: 0, H2: 0, H3: 13, H4: 0, H5: 0, H6: 0
  • Images
    41 GIF, 13 JPG, 3 PNG

Website Meta Analysis

  • Title
    GLOBUL
  • Meta Keyword
    Български мобилен оператор, Мобилни телефонни услуги, Мобилен Телефон, Мобилен интернет, фиксиран телефон, домашен телефон, гласови услуги, Кариери, Стипендия, Квалификация, Стажантска програма, свободни работни места, Абонаментна програма, Предплатена програма, Бизнес програма, Данни, Роуминг, Видео разговор, Телекомуникации, Mултимедия, Полифонични мелодии, Реални звуци, Е-фактура, iPhone 4, BlackBerry, безплатни разговори, GSM, UMTS, Careers, Scholarship, Traineeship, Available positions, Video call, SMS, 3G, GPRS, WAP, MMS, HSDPA, EDGE, B Connect, Roaming, Business Program, SIM, MVPN, GLOBUL Connect Center, Fun call, Pre paid, Telecommunications
  • Meta Description
    Корпоративният уебсайт на GLOBUL, с актуална информация за мобилните и фиксирани телекомуникационни услуги на оператора.

Technical Analysis

  • Webserver
    Oracle Application Server/10g (10.1.2) Apache OracleAS-Web-Cache-10g/10.1.2.0.2
  • Ip Address
    85.118.192.33
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: Oracle Application Server/10g (10.1.2) Apache OracleAS-Web-Cache-10g/10.1.2.0.2
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • content-type: text/html
  • date: Sat, 09 Mar 2013 09:16:33 GMT
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
DOMAIN NAME: globul.bg
requested on: 24/04/2001 00:00:00 EEST
processed from: 24/04/2001 00:00:00 EEST
activated on: 27/04/2001 00:00:00 EEST
expires at: 27/04/2013 00:00:00 EEST
registration status: Registered

REGISTRANT:
Cosmo Bulgaria Mobile Ltd.
4 Mladost Distr., Business park Sofia, building 4, fl. 5, BG-1715 Sofia
SOFIA, 1715
BULGARIA

ADMINISTRATIVE CONTACT:
Kiril Todorov Todorov
email
Cosmo Bulgaria Mobile EAD
8 Akad. E. Pavlovski Str., 1 Mladost Distr., BG-1784 Sofia
SOFIA, 1784
BULGARIA
tel: +359 2 9428701
fax: +359 2 9428702
NIC handle: KT32-BGNIC

TECHNICAL CONTACT(S):

Tsvetomir Tsenkov
email
Cosmo Bulgaria Mobile EAD
8 Dimitar Mollov Str., 1 Mladost Distr.
SOFIA, 1784
BULGARIA
tel: +359 98 400 730
fax: +359 2 9428702
NIC handle: TT23834

Stanislav Georgiev
email
Cosmo Bulgaria Mobile EAD
8 Dimitar Mollov Str., 1 Mladost Distr.
SOFIA, 1784
BULGARIA
tel: +359 98 400 726
fax: +359 2 942 8702
NIC handle: SG23833

NAME SERVER INFORMATION:
ns2.globul.bg (85.118.192.3)
ns.globul.bg (85.118.192.2)

DNSSEC: Inactive

DNS Analysis


DNS servers
ns2.globul.bg
ns.globul.bg [85.118.192.2]

DNS Records

Answer records
globul.bg A 85.118.192.33 86400s
globul.bg NS  ns2.globul.bg 86400s
globul.bg NS  ns.globul.bg 86400s
globul.bg SOA
server: ns.globul.bg
email: hostmaster@ns.globul.bg
serial: 2006011353
refresh: 10800
retry: 900
expire: 604800
minimum ttl: 86400
86400s
globul.bg MX
preference: 10
exchange: mx1.globul.bg
86400s
globul.bg MX
preference: 15
exchange: mx2.globul.bg
86400s
globul.bg TXT v=spf1 mx a:mx1.globul.bg a:mx2.globul.bg a:edgesor01.globul.bg ~all 3600s

Authority records

Additional records
ns2.globul.bg A 85.118.192.3 86400s
ns.globul.bg A 85.118.192.2 86400s
mx1.globul.bg A 85.118.192.60 86400s
mx2.globul.bg A 85.118.192.62 86400s

IP 85.118.192.33 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 29 Errors
  • 14 Warnings
Ratio Text/Html
  • 0.6258983510715612
Message Error
  • Warning Line 32, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …rvey-software">Survey Software</a><br /><a target="_blank" href="http://www.qu…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 32, Column 222: NET-enabling start-tag requires SHORTTAG YES
    …erprise-feedback-management">Enterprise Feedback Management</a><br/></noscript>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 36, Column 18: NET-enabling start-tag requires SHORTTAG YES
    <SCRIPT type=text/javascript>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 153, 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 164, Column 110: document type does not allow element "LINK" here
    …text/css" href="/javascript/fancybox/jquery.fancybox-1.3.4.css" media="screen">

    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 180, Column 7: end tag for element "HEAD" which is not open
    </head>

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

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

  • Error Line 182, Column 6: document type does not allow element "BODY" here
    <body>

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

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

  • Error Line 194, Column 29: start tag for "LI" omitted, but its declaration does not permit this
    			<a href="#content-anchor">Премини към основното съдържание</a>
  • Warning Line 325, Column 63: NET-enabling start-tag requires SHORTTAG YES
    			<img src="../gimg/nm_btn_home.gif" border="0" alt="Начало" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 432, Column 77: NET-enabling start-tag requires SHORTTAG YES
    							  <img alt="" src="../images/asus_x55v9_top.jpg" style="float:none;" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 434, Column 179: NET-enabling start-tag requires SHORTTAG YES
    …11px;">15.6" екран с HD резолюция,<br />4&nbsp;GB памет, 500&nbsp;GB твърд дис…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 434, Column 273: NET-enabling start-tag requires SHORTTAG YES
    … 1&nbsp;GB собствена памет.</span><br /><div style="margin-top:5px;">Само за <…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 469, Column 139: NET-enabling start-tag requires SHORTTAG YES
    …le="float:right;width:51px;height:48px;margin-left:10px;margin-bottom:10px;" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 507, Column 284: NET-enabling start-tag requires SHORTTAG YES
    …and-surf.jpg" alt="QR код за достъп до Travel&amp;Surf приложението" /></a> 			

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 532, Column 8: required attribute "TYPE" not specified
    <script>

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

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

  • Warning Line 744, Column 143: NET-enabling start-tag requires SHORTTAG YES
    …се свържете със сътрудник от Отдел Обслужване на клиенти на GLOBUL:<br /><br />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 744, Column 149: NET-enabling start-tag requires SHORTTAG YES
    …се свържете със сътрудник от Отдел Обслужване на клиенти на GLOBUL:<br /><br />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 745, Column 73: NET-enabling start-tag requires SHORTTAG YES
    …     &bull; по <a href="contact.html">телефон и факс</a><br />                 

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

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

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

  • Info Line 723, Column 5: start tag was here
    				<div class="new_menu_sub_support new_menu_hidden_container">
  • Error Line 787, Column 22: there is no attribute "SRC"
              <embed src="../img/frontpages/priv.bg200903121533.swf" quality="high"…

    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 787, Column 74: there is no attribute "QUALITY"
    …ages/priv.bg200903121533.swf" quality="high" pluginspage="https://www.macromed…

    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 787, Column 93: there is no attribute "PLUGINSPAGE"
    …21533.swf" quality="high" pluginspage="https://www.macromedia.com/go/getflashp…

    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 787, Column 145: there is no attribute "TYPE"
    …acromedia.com/go/getflashplayer" type="application/x-shockwave-flash" width="4…

    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 787, Column 183: there is no attribute "WIDTH"
    …"application/x-shockwave-flash" width="479" height="240" wmode="transparent"><…

    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 787, Column 196: there is no attribute "HEIGHT"
    …x-shockwave-flash" width="479" height="240" wmode="transparent"></embed></obje…

    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 787, Column 208: there is no attribute "WMODE"
    …flash" width="479" height="240" wmode="transparent"></embed></object><script 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 787, Column 221: element "EMBED" undefined
    …"479" height="240" wmode="transparent"></embed></object><script type="text/jav…

    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 814, Column 7: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    				<P><A href="configurator.html?ref=home">Конфигуратор</A> <BR><A href="globu…

    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>").

  • Warning Line 848, Column 39: cannot generate system identifier for general entity "ref"
        <a href="postpaid.33.html?posm=26&ref=mhome02" target="_self"><img class="h…

    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 848, Column 39: general entity "ref" not defined and no default entity
        <a href="postpaid.33.html?posm=26&ref=mhome02" target="_self"><img class="h…

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

  • Error Line 848, Column 42: reference to entity "ref" for which no system identifier could be generated
    … <a href="postpaid.33.html?posm=26&ref=mhome02" target="_self"><img class="hom…

    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 848, Column 38: entity was defined here
        <a href="postpaid.33.html?posm=26&ref=mhome02" target="_self"><img class="h…
  • Error Line 851, Column 67: reference to entity "ref" for which no system identifier could be generated
    …             <h3><a href="postpaid.33.html?posm=26&ref=mhome02" target="_self">

    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 848, Column 38: entity was defined here
        <a href="postpaid.33.html?posm=26&ref=mhome02" target="_self"><img class="h…
  • Error Line 854, Column 58: reference to entity "ref" for which no system identifier could be generated
    … <a href="postpaid.33.html?posm=26&ref=mhome02" target="_self">Още повече мину…

    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 848, Column 38: entity was defined here
        <a href="postpaid.33.html?posm=26&ref=mhome02" target="_self"><img class="h…
  • Warning Line 862, Column 170: NET-enabling start-tag requires SHORTTAG YES
    …=rhome"><img src="../images/HTC_Desire_X-BG.jpg" alt="HTC Desire X" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 872, Column 45: reference to entity "ref" for which no system identifier could be generated
    … href="postpaid_goweb.html?id=4266&ref=mhome03" target="_self"><img class="hom…

    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 848, Column 38: entity was defined here
        <a href="postpaid.33.html?posm=26&ref=mhome02" target="_self"><img class="h…
  • Error Line 875, Column 70: reference to entity "ref" for which no system identifier could be generated
    …          <h3><a href="postpaid_goweb.html?id=4266&ref=mhome03" target="_self">

    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 848, Column 38: entity was defined here
        <a href="postpaid.33.html?posm=26&ref=mhome02" target="_self"><img class="h…
  • Error Line 878, Column 61: reference to entity "ref" for which no system identifier could be generated
    … href="postpaid_goweb.html?id=4266&ref=mhome03" target="_self">Сърфирай безгри…

    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 848, Column 38: entity was defined here
        <a href="postpaid.33.html?posm=26&ref=mhome02" target="_self"><img class="h…
  • Error Line 938, Column 90: end tag for element "STRONG" which is not open
    …f="promotion.html?id=5682&amp;ref=dhome3">b-connect happytime</a></strong></td>

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

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

  • Error Line 938, Column 95: end tag for "H3" omitted, but its declaration does not permit this
    …f="promotion.html?id=5682&amp;ref=dhome3">b-connect happytime</a></strong></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 937, Column 76: start tag was here
            <td colspan="2" height="38" align="left" class="prom-title noline"><h3>
  • Error Line 941, Column 164: required attribute "ALT" not specified
    …HT: 5px" src="../images/label_new.gif">До 2000 минути към група За приятели и …

    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 994, Column 537: required attribute "TYPE" not specified
    …eight=200')">GSM и UMTS радио интерфейси</a></em><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 1048, Column 9: there is no attribute "ALT"
    	<a alt="GLOBUL green" target="_blank" href="http://globulgreen.bg/themes/consu…

    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 1048, Column 168: required attribute "ALT" not specified
    …src="../images/GLOBUL_green_footer.gif" align="right" style="float: right"></a>

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

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

Visitor Analysis

Daily Visitor
  • 2.683 visits
Daily Visitor