justice.cz

justice.cz has Alexa Rank 14.774 and Google Page Rank is 6

Display Widget for this domain on your website. Click Here
This data was last updated from 22-08-2013 06:06:33  (update).

Overview Info

  • Domain Name
    justice.cz
  • Favicon
  • Alexa Rank
    #14774
  • Google Page Rank
    PR 6
  • Ip Address
    194.213.41.145
  • Page Size
    26.2 KB
  • Images
    14 GIF, 2 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 3 6 2 0 0

Website Meta Analysis



  • Title
    Justice.cz - úvodní strana
  • Meta Keyword

Technical Analysis



  • Webserver
    Microsoft-IIS/6.0
  • Ip Address
    194.213.41.145
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from justice.cz.

HTML Analysis

  • date: Thu, 22 Aug 2013 18:06:09 GMT
  • server: Microsoft-IIS/6.0
  • microsoftofficewebserver: 5.0_Pub
  • x-powered-by: ASP.NET
  • x-aspnet-version: 2.0.50727
  • cache-control: private
  • content-type: text/html; charset=windows-1250
  • content-length: 27792
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
% (c) 2006-2012 CZ.NIC, z.s.p.o.
%
% Intended use of supplied data and information
%
% Data contained in the domain name register, as well as information
% supplied through public information services of CZ.NIC association,
% are appointed only for purposes connected with Internet network
% administration and operation, or for the purpose of legal or other
% similar proceedings, in process as regards a matter connected
% particularly with holding and using a concrete domain name.
%
% Full text available at:
% http://www.nic.cz/page/306/intended-use-of-supplied-data-and-information/
%
% See also a search service at http://www.nic.cz/whois/
%
%
% Whoisd Server Version: 3.6.0
% Timestamp: Tue Oct 02 06:37:42 2012

domain: justice.cz
registrant: SB:PV59-RIPE_XX
admin-c: PETRKOUCKY
nsset: NSS:MP106-RIPE_XX:2
registrar: REG-CT
status: paid and in zone
registered: 08.12.1996 01:00:00
changed: 26.11.2003 07:22:00
expire: 21.10.2014

contact: SB:PV59-RIPE_XX
org: Ministerstvo spravedlnosti
name: Ministerstvo spravedlnosti
address: Vysehradska 16
address: Praha 2
address: 128 00
address: CZ
e-mail: email
registrar: REG-CT
created: 10.08.2001 22:13:00
changed: 31.01.2006 12:15:00

contact: PETRKOUCKY
name: Petr Koucky
address: Vysehradska 16
address: Praha 2
address: 12800
address: CZ
e-mail: email
registrar: REG-CT
created: 03.11.2005 15:25:00

nsset: NSS:MP106-RIPE_XX:2
nserver: ns.justice.cz (194.213.41.2)
nserver: server1.gts.cz
tech-c: SB:MP106-RIPE_XX
tech-c: MP106-RIPE
registrar: REG-CT
created: 01.10.2007 02:00:00

contact: SB:MP106-RIPE_XX
org: Corpus s. r. o.
name: Corpus s. r. o.
address: Sluzeb 4
address: Praha 10
address: 108 52
address: CZ
e-mail: email
registrar: REG-ACTIVE24
created: 10.08.2001 22:13:00

contact: MP106-RIPE
name: Martin Pavlica
address: CZ
phone: +420 2771990
fax-no: +420 2771990
e-mail: email
registrar: REG-ACTIVE24
created: 10.08.2001 22:13:00


DNS Analysis


DNS servers
dns1.justice.cz [194.213.41.91]
dns2.justice.cz [194.213.41.92]
server1.gts.cz


DNS Records

Answer records
justice.cz SOA
server: dns1.justice.cz
email: root@justice.cz
serial: 2012122001
refresh: 7200
retry: 3600
expire: 1209600
minimum ttl: 10800
1800s
justice.cz A 194.213.41.145 1800s
justice.cz MX
preference: 10
exchange: mse2.justice.cz
1800s
justice.cz MX
preference: 50
exchange: mspool.gts.cz
1800s
justice.cz MX
preference: 10
exchange: ms.justice.cz
1800s
justice.cz MX
preference: 10
exchange: mse1.justice.cz
1800s
justice.cz NS  dns1.justice.cz 1800s
justice.cz NS  dns2.justice.cz 1800s
justice.cz NS  server1.gts.cz 1800s

Authority records

Additional records
ms.justice.cz A 194.213.41.35 1800s
mse1.justice.cz A 194.213.41.84 1800s
mse2.justice.cz A 194.213.41.88 1800s
mspool.gts.cz A 193.85.2.11 86400s
dns1.justice.cz A 194.213.41.91 1800s
dns2.justice.cz A 194.213.41.92 1800s
server1.gts.cz A 212.47.0.10 86400s

IP 194.213.41.145 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 1 Errors
  • 23 Warnings
Ratio Text/Html
  • 0.778658922521315
Message Error
  • Error Line 43, Column 26: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
            <script language=JavaScript>
  • Error Line 43, Column 36: required attribute "type" not specified
            <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 47, Column 26: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
            <script language=JavaScript>
  • Error Line 47, Column 36: required attribute "type" not specified
            <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 79, Column 167: required attribute "alt" not specified
    …tle="Justice.cz" src="../img/logo-justice.gif" style="border-width:0px;" /></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 122, Column 247: required attribute "alt" not specified
    …nformace o projektu" src="../img/ejustice.gif" style="border-width:0px;" /></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 129, Column 208: required attribute "alt" not specified
    …="ePodatelna" src="../img/logo-epodatelna.gif" style="border-width:0px;" /></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 130, Column 204: required attribute "alt" not specified
    …le="infoDeska" src="../img/logo-infodeska.gif" style="border-width:0px;" /></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 133, Column 200: required attribute "alt" not specified
    …itle="infoSoud" src="../img/logo-infosoud.gif" style="border-width:0px;" /></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 134, Column 212: required attribute "alt" not specified
    …infoJednání" src="../img/logo-infojednani.gif" style="border-width:0px;" /></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 137, Column 197: required attribute "alt" not specified
    …itle="infoData" src="../img/logo-infodata.gif" style="border-width:0px;" /></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 138, Column 244: required attribute "alt" not specified
    …="Judikatura" src="../img/logo-Judikatura.gif" style="border-width:0px;" /></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 293, Column 150: required attribute "alt" not specified
    …ál e-Justice" src="../img/e-Justice_banner_CS.jpg" style="border-width:0px;" />

    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 299, Column 68: cannot generate system identifier for general entity "o"
    …     <a class="banner" href="../MS/ms.aspx?j=33&o=23&k=5208&d=308460" 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 299, Column 68: general entity "o" not defined and no default entity
    …     <a class="banner" href="../MS/ms.aspx?j=33&o=23&k=5208&d=308460" 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 299, Column 69: reference not terminated by REFC delimiter
    …     <a class="banner" href="../MS/ms.aspx?j=33&o=23&k=5208&d=308460" 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 299, Column 69: reference to external entity in attribute value
    …     <a class="banner" href="../MS/ms.aspx?j=33&o=23&k=5208&d=308460" 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 299, Column 69: reference to entity "o" for which no system identifier could be generated
    …     <a class="banner" href="../MS/ms.aspx?j=33&o=23&k=5208&d=308460" 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 299, Column 67: entity was defined here
    …     <a class="banner" href="../MS/ms.aspx?j=33&o=23&k=5208&d=308460" title="">
  • Warning Line 299, Column 73: cannot generate system identifier for general entity "k"
    …     <a class="banner" href="../MS/ms.aspx?j=33&o=23&k=5208&d=308460" 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 299, Column 73: general entity "k" not defined and no default entity
    …     <a class="banner" href="../MS/ms.aspx?j=33&o=23&k=5208&d=308460" 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 299, Column 74: reference not terminated by REFC delimiter
    …     <a class="banner" href="../MS/ms.aspx?j=33&o=23&k=5208&d=308460" 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 299, Column 74: reference to external entity in attribute value
    …     <a class="banner" href="../MS/ms.aspx?j=33&o=23&k=5208&d=308460" 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 299, Column 74: reference to entity "k" for which no system identifier could be generated
    …     <a class="banner" href="../MS/ms.aspx?j=33&o=23&k=5208&d=308460" 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 299, Column 72: entity was defined here
    …     <a class="banner" href="../MS/ms.aspx?j=33&o=23&k=5208&d=308460" title="">
  • Warning Line 299, Column 80: cannot generate system identifier for general entity "d"
    …     <a class="banner" href="../MS/ms.aspx?j=33&o=23&k=5208&d=308460" 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 299, Column 80: general entity "d" not defined and no default entity
    …     <a class="banner" href="../MS/ms.aspx?j=33&o=23&k=5208&d=308460" 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 299, Column 81: reference not terminated by REFC delimiter
    …     <a class="banner" href="../MS/ms.aspx?j=33&o=23&k=5208&d=308460" 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 299, Column 81: reference to external entity in attribute value
    …     <a class="banner" href="../MS/ms.aspx?j=33&o=23&k=5208&d=308460" 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 299, Column 81: reference to entity "d" for which no system identifier could be generated
    …     <a class="banner" href="../MS/ms.aspx?j=33&o=23&k=5208&d=308460" 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 299, Column 79: entity was defined here
    …     <a class="banner" href="../MS/ms.aspx?j=33&o=23&k=5208&d=308460" title="">
  • Error Line 300, Column 150: required attribute "alt" not specified
    …atové schránky" src="../img/banner-dorucovani.gif" style="border-width:0px;" />

    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 304, Column 68: cannot generate system identifier for general entity "j"
    …     <a class="banner" href="../MS/ms.aspx?o=23&j=33&k=5266&d=310180" 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 304, Column 68: general entity "j" not defined and no default entity
    …     <a class="banner" href="../MS/ms.aspx?o=23&j=33&k=5266&d=310180" 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 304, Column 69: reference not terminated by REFC delimiter
    …     <a class="banner" href="../MS/ms.aspx?o=23&j=33&k=5266&d=310180" 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 304, Column 69: reference to external entity in attribute value
    …     <a class="banner" href="../MS/ms.aspx?o=23&j=33&k=5266&d=310180" 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 304, Column 69: reference to entity "j" for which no system identifier could be generated
    …     <a class="banner" href="../MS/ms.aspx?o=23&j=33&k=5266&d=310180" 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 304, Column 67: entity was defined here
    …     <a class="banner" href="../MS/ms.aspx?o=23&j=33&k=5266&d=310180" title="">
  • Warning Line 304, Column 74: reference not terminated by REFC delimiter
    …     <a class="banner" href="../MS/ms.aspx?o=23&j=33&k=5266&d=310180" 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 304, Column 74: reference to external entity in attribute value
    …     <a class="banner" href="../MS/ms.aspx?o=23&j=33&k=5266&d=310180" 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 304, Column 74: reference to entity "k" for which no system identifier could be generated
    …     <a class="banner" href="../MS/ms.aspx?o=23&j=33&k=5266&d=310180" 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 299, Column 72: entity was defined here
    …     <a class="banner" href="../MS/ms.aspx?j=33&o=23&k=5208&d=308460" title="">
  • Warning Line 304, Column 81: reference not terminated by REFC delimiter
    …     <a class="banner" href="../MS/ms.aspx?o=23&j=33&k=5266&d=310180" 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 304, Column 81: reference to external entity in attribute value
    …     <a class="banner" href="../MS/ms.aspx?o=23&j=33&k=5266&d=310180" 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 304, Column 81: reference to entity "d" for which no system identifier could be generated
    …     <a class="banner" href="../MS/ms.aspx?o=23&j=33&k=5266&d=310180" 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 299, Column 79: entity was defined here
    …     <a class="banner" href="../MS/ms.aspx?j=33&o=23&k=5208&d=308460" title="">
  • Error Line 305, Column 139: required attribute "alt" not specified
    …mácí vězení" src="../img/banner-domaci-vezeni.gif" style="border-width:0px;" />

    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 312, Column 82: end tag for "param" omitted, but OMITTAG NO was specified
    …                          <param name="SRC" value="../img/banner_468x60_Q.swf">

    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 312, Column 29: start tag was here
                                <param name="SRC" value="../img/banner_468x60_Q.swf…
  • Warning Line 332, Column 70: reference not terminated by REFC delimiter
    …lass="bannerGreenComp" href="../MS/ms.aspx?o=23&j=33&k=5067&d=306899" 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 332, Column 70: reference to external entity in attribute value
    …lass="bannerGreenComp" href="../MS/ms.aspx?o=23&j=33&k=5067&d=306899" 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 332, Column 70: reference to entity "j" for which no system identifier could be generated
    …lass="bannerGreenComp" href="../MS/ms.aspx?o=23&j=33&k=5067&d=306899" 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 304, Column 67: entity was defined here
    …     <a class="banner" href="../MS/ms.aspx?o=23&j=33&k=5266&d=310180" title="">
  • Warning Line 332, Column 75: reference not terminated by REFC delimiter
    …lass="bannerGreenComp" href="../MS/ms.aspx?o=23&j=33&k=5067&d=306899" 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 332, Column 75: reference to external entity in attribute value
    …lass="bannerGreenComp" href="../MS/ms.aspx?o=23&j=33&k=5067&d=306899" 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 332, Column 75: reference to entity "k" for which no system identifier could be generated
    …lass="bannerGreenComp" href="../MS/ms.aspx?o=23&j=33&k=5067&d=306899" 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 299, Column 72: entity was defined here
    …     <a class="banner" href="../MS/ms.aspx?j=33&o=23&k=5208&d=308460" title="">
  • Warning Line 332, Column 82: reference not terminated by REFC delimiter
    …lass="bannerGreenComp" href="../MS/ms.aspx?o=23&j=33&k=5067&d=306899" 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 332, Column 82: reference to external entity in attribute value
    …lass="bannerGreenComp" href="../MS/ms.aspx?o=23&j=33&k=5067&d=306899" 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 332, Column 82: reference to entity "d" for which no system identifier could be generated
    …lass="bannerGreenComp" href="../MS/ms.aspx?o=23&j=33&k=5067&d=306899" 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 299, Column 79: entity was defined here
    …     <a class="banner" href="../MS/ms.aspx?j=33&o=23&k=5208&d=308460" title="">
  • Error Line 333, Column 131: required attribute "alt" not specified
    …elená firma" src="../img/banner-zelena-firma.gif" style="border-width:0px;" />	

    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
  • 10.383 visits

In Page Analysis