elmaz.com

Влез в най-посещавания сайт за запознанства за мъже и жени над 18 години. Разгледай галерия от жени и мъже от всички градове, търсещи любов и чат запознанства. Zapoznanstva, zapoznanstvo v Bulgaria. ...

Display Widget for this domain on your website. Click Here
This data was last updated from 03-02-2013 04:20:10  (update).

Overview Info

  • Domain Name
    elmaz.com
  • Favicon
  • Alexa Rank
    #30448
  • Google Page Rank
    PR 5
  • Ip Address
    79.124.65.17
  • Page Size
    49.6 KB
  • Images
    13 GIF, 9 JPG, 18 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 0 0 0 0 0

Website Meta Analysis



  • Title
    Запознанства - Elmaz.com. Zapoznanstva.
  • Meta Keyword
    запознанства, elmaz, елмаз,приятели, zapoznanstva, любов, обяви за запознанства, романтика, срещи, връзки, лични обяви, партньор, запознанство, zapoznanstwa, romantika, priatel, priateli, жени, мъже, търсене
  • Meta Description
    Влез в най-посещавания сайт за запознанства за мъже и жени над 18 години. Разгледай галерия от жени и мъже от всички градове, търсещи любов и чат запознанства. Zapoznanstva, zapoznanstvo v Bulgaria.

Technical Analysis



  • Webserver
    lighttpd/1.4.28
  • Ip Address
    79.124.65.17
  • Domain Age
    12 Years, 9 Months, 15 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from elmaz.com.

HTML Analysis

  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • content-encoding: gzip
  • vary: Accept-Encoding
  • content-type: text/html
  • server: lighttpd/1.4.28
  • content-length: 9784
  • accept-ranges: bytes
  • date: Sun, 03 Feb 2013 04:20:11 GMT
  • age: 0
  • connection: close
  • x-cache: MISS from web2
  • via: 1.7 proxy
  • x-google-cache-control: remote-fetch
Registrant:
Domain Discreet Privacy Service
ATTN: elmaz.com
12808 Gran Bay Pkwy, West
Jacksonville, FL 32258
US
Phone: 1-902-7492701
Email: email




Domain Name: elmaz.com
Created on..............: 2000-04-26
Expires on..............: 2013-04-26

Administrative Contact:
Domain Discreet Privacy Service
ATTN: elmaz.com
12808 Gran Bay Pkwy, West
Jacksonville, FL 32258
US
Phone: 1-902-7492701
Email: email


Technical Contact:
Domain Discreet Privacy Service
ATTN: elmaz.com
12808 Gran Bay Pkwy, West
Jacksonville, FL 32258
US
Phone: 1-902-7492701
Email: email


DNS Servers:
ns1.netguardbg.com
ns.elmaz.com

DNS Analysis


DNS servers
ns1.netguardbg.com [195.238.84.4]
ns.elmaz.com [79.124.65.2]

DNS Records

Answer records
elmaz.com SOA
server: ns.elmaz.com
email: root@elmaz.com
serial: 2012090401
refresh: 28800
retry: 7200
expire: 604800
minimum ttl: 86400
7200s
elmaz.com NS  ns.elmaz.com 7200s
elmaz.com NS  ns1.netguardbg.com 7200s
elmaz.com MX
preference: 10
exchange: mail.elmaz.com
7200s
elmaz.com A 79.124.65.17 7200s
elmaz.com TXT v=spf1 a a:mail.elmaz.com ip4:79.124.65.0/24 -all 7200s

Authority records

Additional records
ns.elmaz.com A 79.124.65.2 7200s
mail.elmaz.com A 79.124.65.2 7200s

IP 79.124.65.17 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

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

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

  • Error Line 72, Column 252: there is no attribute "align"
    … src="http://img.elmaz.com/style/img/separator.png" align="absmiddle" /></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 72, Column 265: required attribute "alt" not specified
    … src="http://img.elmaz.com/style/img/separator.png" align="absmiddle" /></span>

    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 73, Column 242: required attribute "alt" not specified
    … src="http://img.elmaz.com/style/img/separator.png" align="absmiddle" /></span>

    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 74, Column 254: required attribute "alt" not specified
    … src="http://img.elmaz.com/style/img/separator.png" align="absmiddle" /></span>

    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 222, Column 15: 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 222, Column 15: 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 241, Column 112: end tag for "img" omitted, but OMITTAG NO was specified
    …="http://img.elmaz.com/style/img/arrow_bullet.gif" class="bullet" alt="bullet">

    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 241, Column 25: start tag was here
                            <img src="http://img.elmaz.com/style/img/arrow_bullet.g…
  • Warning Line 244, Column 96: cannot generate system identifier for general entity "city"
    …w.elmaz.com/index.php?page=citysearch&city=1" title="Запознаства в София">Софи…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 244, Column 96: general entity "city" not defined and no default entity
    …w.elmaz.com/index.php?page=citysearch&city=1" title="Запознаства в София">Софи…

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

  • Warning Line 244, Column 100: reference not terminated by REFC delimiter
    …maz.com/index.php?page=citysearch&city=1" title="Запознаства в София">София</a…

    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 244, Column 100: reference to external entity in attribute value
    …maz.com/index.php?page=citysearch&city=1" title="Запознаства в София">София</a…

    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 244, Column 100: reference to entity "city" for which no system identifier could be generated
    …maz.com/index.php?page=citysearch&city=1" title="Запознаства в София">София</a…

    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 244, Column 95: entity was defined here
    …ww.elmaz.com/index.php?page=citysearch&city=1" title="Запознаства в София">Соф…
  • Error Line 250, Column 112: end tag for "img" omitted, but OMITTAG NO was specified
    …="http://img.elmaz.com/style/img/arrow_bullet.gif" class="bullet" alt="bullet">

    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 250, Column 25: start tag was here
                            <img src="http://img.elmaz.com/style/img/arrow_bullet.g…
  • Warning Line 253, Column 100: reference not terminated by REFC delimiter
    …maz.com/index.php?page=citysearch&city=3" title="Запознаства в Пловдив">Пловди…

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

  • Warning Line 253, Column 100: reference to external entity in attribute value
    …maz.com/index.php?page=citysearch&city=3" title="Запознаства в Пловдив">Пловди…

    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 253, Column 100: reference to entity "city" for which no system identifier could be generated
    …maz.com/index.php?page=citysearch&city=3" title="Запознаства в Пловдив">Пловди…

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

  • Info Line 244, Column 95: entity was defined here
    …ww.elmaz.com/index.php?page=citysearch&city=1" title="Запознаства в София">Соф…
  • Error Line 259, Column 112: end tag for "img" omitted, but OMITTAG NO was specified
    …="http://img.elmaz.com/style/img/arrow_bullet.gif" class="bullet" alt="bullet">

    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 259, Column 25: start tag was here
                            <img src="http://img.elmaz.com/style/img/arrow_bullet.g…
  • Warning Line 262, Column 100: reference not terminated by REFC delimiter
    …maz.com/index.php?page=citysearch&city=2" title="Запознаства във Варна">Варна<…

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

  • Warning Line 262, Column 100: reference to external entity in attribute value
    …maz.com/index.php?page=citysearch&city=2" title="Запознаства във Варна">Варна<…

    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 262, Column 100: reference to entity "city" for which no system identifier could be generated
    …maz.com/index.php?page=citysearch&city=2" title="Запознаства във Варна">Варна<…

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

  • Info Line 244, Column 95: entity was defined here
    …ww.elmaz.com/index.php?page=citysearch&city=1" title="Запознаства в София">Соф…
  • Error Line 268, Column 112: end tag for "img" omitted, but OMITTAG NO was specified
    …="http://img.elmaz.com/style/img/arrow_bullet.gif" class="bullet" alt="bullet">

    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 268, Column 25: start tag was here
                            <img src="http://img.elmaz.com/style/img/arrow_bullet.g…
  • Warning Line 271, Column 100: reference not terminated by REFC delimiter
    …lmaz.com/index.php?page=citysearch&city=99" title="Запознаства в Русе">Русе</a>

    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 271, Column 100: reference to external entity in attribute value
    …lmaz.com/index.php?page=citysearch&city=99" title="Запознаства в Русе">Русе</a>

    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 271, Column 100: reference to entity "city" for which no system identifier could be generated
    …lmaz.com/index.php?page=citysearch&city=99" title="Запознаства в Русе">Русе</a>

    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 244, Column 95: entity was defined here
    …ww.elmaz.com/index.php?page=citysearch&city=1" title="Запознаства в София">Соф…
  • Error Line 294, Column 67: there is no attribute "target"
    …p://www.amam.bg/?ad=004;00;03" target="_blank" rel="nofollow" title="кликни &a…

    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.

  • Warning Line 355, Column 73: cannot generate system identifier for general entity "source"
    …s.elmaz.com/adclick.php?bannerid=5643&source=&dest=http://ekvator.bg" target="…

    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 355, Column 73: general entity "source" not defined and no default entity
    …s.elmaz.com/adclick.php?bannerid=5643&source=&dest=http://ekvator.bg" target="…

    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 355, Column 79: reference not terminated by REFC delimiter
    …z.com/adclick.php?bannerid=5643&source=&dest=http://ekvator.bg" target="_blank…

    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 355, Column 79: reference to external entity in attribute value
    …z.com/adclick.php?bannerid=5643&source=&dest=http://ekvator.bg" target="_blank…

    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 355, Column 79: reference to entity "source" for which no system identifier could be generated
    …z.com/adclick.php?bannerid=5643&source=&dest=http://ekvator.bg" target="_blank…

    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 355, Column 72: entity was defined here
    …ds.elmaz.com/adclick.php?bannerid=5643&source=&dest=http://ekvator.bg" target=…
  • Warning Line 355, Column 81: cannot generate system identifier for general entity "dest"
    …com/adclick.php?bannerid=5643&source=&dest=http://ekvator.bg" target="_blank" …

    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 355, Column 81: general entity "dest" not defined and no default entity
    …com/adclick.php?bannerid=5643&source=&dest=http://ekvator.bg" target="_blank" …

    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 355, Column 85: reference not terminated by REFC delimiter
    …adclick.php?bannerid=5643&source=&dest=http://ekvator.bg" target="_blank" rel=…

    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 355, Column 85: reference to external entity in attribute value
    …adclick.php?bannerid=5643&source=&dest=http://ekvator.bg" target="_blank" rel=…

    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 355, Column 85: reference to entity "dest" for which no system identifier could be generated
    …adclick.php?bannerid=5643&source=&dest=http://ekvator.bg" target="_blank" rel=…

    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 355, Column 80: entity was defined here
    ….com/adclick.php?bannerid=5643&source=&dest=http://ekvator.bg" target="_blank"…
  • Warning Line 358, Column 84: reference not terminated by REFC delimiter
    …z.com/adclick.php?bannerid=5643&source=&dest=http://ekvator.bg" class="bold pu…

    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 358, Column 84: reference to external entity in attribute value
    …z.com/adclick.php?bannerid=5643&source=&dest=http://ekvator.bg" class="bold pu…

    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 358, Column 84: reference to entity "source" for which no system identifier could be generated
    …z.com/adclick.php?bannerid=5643&source=&dest=http://ekvator.bg" class="bold pu…

    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 355, Column 72: entity was defined here
    …ds.elmaz.com/adclick.php?bannerid=5643&source=&dest=http://ekvator.bg" target=…
  • Warning Line 358, Column 90: reference not terminated by REFC delimiter
    …adclick.php?bannerid=5643&source=&dest=http://ekvator.bg" class="bold purple2"…

    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 358, Column 90: reference to external entity in attribute value
    …adclick.php?bannerid=5643&source=&dest=http://ekvator.bg" class="bold purple2"…

    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 358, Column 90: reference to entity "dest" for which no system identifier could be generated
    …adclick.php?bannerid=5643&source=&dest=http://ekvator.bg" class="bold purple2"…

    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 355, Column 80: entity was defined here
    ….com/adclick.php?bannerid=5643&source=&dest=http://ekvator.bg" target="_blank"…
  • Warning Line 359, Column 99: reference not terminated by REFC delimiter
    …z.com/adclick.php?bannerid=5643&source=&dest=http://ekvator.bg" class="black" …

    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 359, Column 99: reference to external entity in attribute value
    …z.com/adclick.php?bannerid=5643&source=&dest=http://ekvator.bg" class="black" …

    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 359, Column 99: reference to entity "source" for which no system identifier could be generated
    …z.com/adclick.php?bannerid=5643&source=&dest=http://ekvator.bg" class="black" …

    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 355, Column 72: entity was defined here
    …ds.elmaz.com/adclick.php?bannerid=5643&source=&dest=http://ekvator.bg" target=…
  • Warning Line 359, Column 105: reference not terminated by REFC delimiter
    …adclick.php?bannerid=5643&source=&dest=http://ekvator.bg" class="black" target…

    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 359, Column 105: reference to external entity in attribute value
    …adclick.php?bannerid=5643&source=&dest=http://ekvator.bg" class="black" target…

    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 359, Column 105: reference to entity "dest" for which no system identifier could be generated
    …adclick.php?bannerid=5643&source=&dest=http://ekvator.bg" class="black" target…

    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 355, Column 80: entity was defined here
    ….com/adclick.php?bannerid=5643&source=&dest=http://ekvator.bg" target="_blank"…
  • Error Line 377, Column 79: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
                                    <input type="hidden" name="txtName" value="" />

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 378, Column 85: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …                          <input type="hidden" name="chbContact[]" value="0" />

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

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 380, Column 85: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …                          <input type="hidden" name="selFromWeight" value="" />

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 381, Column 83: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …                            <input type="hidden" name="selToWeight" value="" />

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 382, Column 79: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
                                    <input type="hidden" name="selEyes" value="" />

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 383, Column 85: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …                          <input type="hidden" name="selFromHeight" value="" />

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 384, Column 83: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …                            <input type="hidden" name="selToHeight" value="" />

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 385, Column 81: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …                              <input type="hidden" name="selFigure" value="" />

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 386, Column 80: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
                                    <input type="hidden" name="selDrink" value="" />

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 387, Column 80: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
                                    <input type="hidden" name="selSmoke" value="" />

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 388, Column 88: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …                       <input type="hidden" name="selRegistrations" value="" />

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 389, Column 84: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …                           <input type="hidden" name="selPerPage" value="10" />

    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 405, Column 206: character "&" is the first character of a delimiter but occurred as data
    …v');" onkeyup="if (event.keyCode != 9 && event.keyCode != 16) showhideCity(thi…

    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.
  • Warning Line 405, Column 207: character "&" is the first character of a delimiter but occurred as data
    …');" onkeyup="if (event.keyCode != 9 && event.keyCode != 16) showhideCity(this…

    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.
  • Warning Line 410, Column 199: character "&" is the first character of a delimiter but occurred as data
    …y');" onkeyup="if (event.keyCode != 9 && event.keyCode != 16) showhideArea(thi…

    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.
  • Warning Line 410, Column 200: character "&" is the first character of a delimiter but occurred as data
    …');" onkeyup="if (event.keyCode != 9 && event.keyCode != 16) showhideArea(this…

    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 524, Column 147: required attribute "alt" not specified
    …><img src="http://img.elmaz.com/style/img/btnLeft.gif" align="absmiddle" /></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>.

  • Error Line 525, Column 148: required attribute "alt" not specified
    …<img src="http://img.elmaz.com/style/img/btnRight.gif" align="absmiddle" /></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>.

  • Error Line 595, Column 145: required attribute "alt" not specified
    …><img src="http://img.elmaz.com/style/img/btnLeft.gif" align="absmiddle" /></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>.

  • Error Line 596, Column 146: required attribute "alt" not specified
    …<img src="http://img.elmaz.com/style/img/btnRight.gif" align="absmiddle" /></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>.

  • Error Line 617, Column 170: required attribute "alt" not specified
    …><img src="http://img.elmaz.com/style/img/advArrow.png" /> Advertisements</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 630, Column 91: required attribute "alt" not specified
    …tyle/img/num1.gif" align="absmiddle" /><a href="http://www.elmaz.com/index.php…

    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 632, Column 91: required attribute "alt" not specified
    …tyle/img/num2.gif" align="absmiddle" /><a href="http://www.elmaz.com/index.php…

    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 634, Column 91: required attribute "alt" not specified
    …        <img src="http://img.elmaz.com/style/img/num3.gif" align="absmiddle" />

    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 721, Column 110: required attribute "alt" not specified
    …/" target="_blank"><img src="http://img.elmaz.com/style/img/TelePoint.gif"></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>.

  • Error Line 721, Column 114: end tag for "img" omitted, but OMITTAG NO was specified
    …/" target="_blank"><img src="http://img.elmaz.com/style/img/TelePoint.gif"></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 721, Column 55: start tag was here
    …p://telepoint.bg/bg/" target="_blank"><img src="http://img.elmaz.com/style/img…
  • Error Line 749, Column 18: there is no attribute "language"
    <script language="javascript" type="text/javascript">

    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.

Visitor Analysis

Daily Visitor
  • 3.967 visits
Daily Visitor

In Page Analysis