Orange Slovensko je najväčším mobilným operátorom na Slovensku. Má 2,89 milióna aktívnych zákazníkov mobilnej siete, ktorej signálom pokrýva 99,6 % populácie a takmer 90 % územia SR. Okrem toho eviduje ďalších takmer 50 ...

orange.sk
  • Domain Name
    orange.sk
  • Favicon
  • Google Page Rank
    6
  • Alexa Rank
    #44002
  • Page Size
    123.9 KB
  • Ip Address
    213.151.200.57
  • Heading
    H1: 0, H2: 7, H3: 1, H4: 3, H5: 0, H6: 0
  • Images
    18 GIF, 7 JPG, 33 PNG

Website Meta Analysis

  • Title
    Orange Slovensko, a.s.
  • Meta Keyword
  • Meta Description
    Orange Slovensko je najväčším mobilným operátorom na Slovensku. Má 2,89 milióna aktívnych zákazníkov mobilnej siete, ktorej signálom pokrýva 99,6 % populácie a takmer 90 % územia SR. Okrem toho eviduje ďalších takmer 50 000 zákazníkov FiberNetu, FiberTV a FiberTelu vo svojej pevnej optickej sieti.

Technical Analysis

  • Webserver
    Oracle-Application-Server-10g/10.1.3.5.0 Oracle-HTTP-Server OracleAS-Web-Cache-10g/10.1.2.0.2 (N;ecid=72057766638670642,0)
  • Ip Address
    213.151.200.57
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from orange.sk.

HTML Analysis

  • expires: Thu, 27 Jun 2013 08:11:10 GMT
  • content-type: text/html; charset=ISO-8859-2
  • content-encoding: gzip
  • server: Oracle-Application-Server-10g/10.1.3.5.0 Oracle-HTTP-Server OracleAS-Web-Cache-10g/10.1.2.0.2 (N;ecid=72057766638670642,0)
  • date: Thu, 27 Jun 2013 08:11:00 GMT
  • x-cache: MISS from www.orange.sk
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
%
% whois.sk-nic.sk - whois server for TLD .sk
%


Domain-name orange.sk
Admin-id ORAN-0003
Admin-name Orange Slovensko, a.s.
Admin-legal-form akciova spolocnost
Admin-org.-ID 35697270
Admin-address Prievozska 6/A, Bratislava 821 09
Admin-telephone +421258512345
Admin-email email
Tech-id ORAN-0003
Tech-name Orange Slovensko, a.s.
Tech-org.-ID 35697270
Tech-address Prievozska 6/A, Bratislava 821 09
Tech-telephone +421258512345
Tech-email email
dns_name ns1.orange.sk
dns_IPv4 213.151.200.30
dns_name tdns1.orange.sk
dns_IPv4 213.151.208.161
dns_name ns2.orange.sk
dns_IPv4 213.151.200.31
dns_name tdns2.orange.sk
dns_IPv4 213.151.208.162
Last-update 2012-03-27
Valid-date 2013-04-21
Domain-status DOM_OK

DNS Analysis


DNS servers
tdns1.orange.sk [213.151.208.161]
tdns2.orange.sk [213.151.208.162]
ns1.orange.sk [213.151.200.30]
ns2.orange.sk [213.151.200.31]


DNS Records

Answer records
orange.sk SOA
server: ns.orange.sk
email: hostmaster@orange.sk
serial: 2013013001
refresh: 7200
retry: 7200
expire: 86400
minimum ttl: 900
86400s
orange.sk A 213.151.200.57 86400s
orange.sk TXT v=spf1 ip4:213.151.200.40 ip4:213.151.200.41 ip4:213.151.200.42 ip4:213.151.200.32 mx a:smtp01-outbound.orange.sk a:smtp02-outbound.orange.sk ~all 86400s
orange.sk MX
preference: 10
exchange: smtp01.orange.sk
86400s
orange.sk MX
preference: 20
exchange: smtp02.orange.sk
86400s
orange.sk NS  tdns1.orange.sk 86400s
orange.sk NS  ns1.orange.sk 86400s
orange.sk NS  tdns2.orange.sk 86400s
orange.sk NS  ns2.orange.sk 86400s

Authority records

Additional records
smtp01.orange.sk A 213.151.208.43 86400s
smtp02.orange.sk A 213.151.208.41 86400s
ns1.orange.sk A 213.151.200.30 86400s
ns2.orange.sk A 213.151.200.31 86400s
tdns1.orange.sk A 213.151.208.161 86400s
tdns2.orange.sk A 213.151.208.162 86400s

IP 213.151.200.57 Analysis

  • Country Code
    SK
  • Country Code3
    SVK
  • Country Name
    Slovakia
  • City
    EU
  • Continent Code
    48°66'67" North
  • Latitude
    19.5.
  • Longitude
  • No whois ip data for 213.151.200.57

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 29 Errors
  • 19 Warnings
Ratio Text/Html
  • 0.6122881522861037
Message Error
  • Error Line 20, Column 16: there is no attribute "property"
    <meta property="og:title" content="Snehuliaci pri aute"/>

    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 39, Column 93: required attribute "type" not specified
    …Script" src="//img.orange.sk/orange_sk/js/orange/ga_event_tracker.js"></script>

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

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

  • Error Line 40, Column 93: required attribute "type" not specified
    …Script" src="//img.orange.sk/orange_sk/js/orange/jquery-1.7.2.min.js"></script>

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

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

  • Error Line 41, Column 89: required attribute "type" not specified
    …JavaScript" src="//img.orange.sk/orange_sk/js/orange/hp-jq-script.js"></script>

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

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

  • Error Line 42, Column 86: required attribute "type" not specified
    …e="JavaScript" src="//img.orange.sk/orange_sk/js/orange/mega_menu.js"></script>

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

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

  • Error Line 59, 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).

  • Warning Line 269, Column 94: cannot generate system identifier for general entity "filterManufacturer1"
    …/eshop/telefony.html?filterPayType1=0&filterManufacturer1=Nokia" class="lev3Ti…

    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 269, Column 94: general entity "filterManufacturer1" not defined and no default entity
    …/eshop/telefony.html?filterPayType1=0&filterManufacturer1=Nokia" class="lev3Ti…

    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 269, Column 113: reference not terminated by REFC delimiter
    …ny.html?filterPayType1=0&filterManufacturer1=Nokia" class="lev3Title">Nokia</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 269, Column 113: reference to external entity in attribute value
    …ny.html?filterPayType1=0&filterManufacturer1=Nokia" class="lev3Title">Nokia</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 269, Column 113: reference to entity "filterManufacturer1" for which no system identifier could be generated
    …ny.html?filterPayType1=0&filterManufacturer1=Nokia" class="lev3Title">Nokia</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 269, Column 93: entity was defined here
    …k/eshop/telefony.html?filterPayType1=0&filterManufacturer1=Nokia" class="lev3T…
  • Warning Line 270, Column 113: reference not terminated by REFC delimiter
    …tml?filterPayType1=0&filterManufacturer1=Samsung" class="lev3Title">Samsung</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 270, Column 113: reference to external entity in attribute value
    …tml?filterPayType1=0&filterManufacturer1=Samsung" class="lev3Title">Samsung</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 270, Column 113: reference to entity "filterManufacturer1" for which no system identifier could be generated
    …tml?filterPayType1=0&filterManufacturer1=Samsung" class="lev3Title">Samsung</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 269, Column 93: entity was defined here
    …k/eshop/telefony.html?filterPayType1=0&filterManufacturer1=Nokia" class="lev3T…
  • Warning Line 271, Column 113: reference not terminated by REFC delimiter
    …l?filterPayType1=0&filterManufacturer1=Sony%20Ericsson&filterManufacturer2=Son…

    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 113: reference to external entity in attribute value
    …l?filterPayType1=0&filterManufacturer1=Sony%20Ericsson&filterManufacturer2=Son…

    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 113: reference to entity "filterManufacturer1" for which no system identifier could be generated
    …l?filterPayType1=0&filterManufacturer1=Sony%20Ericsson&filterManufacturer2=Son…

    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 269, Column 93: entity was defined here
    …k/eshop/telefony.html?filterPayType1=0&filterManufacturer1=Nokia" class="lev3T…
  • Warning Line 271, Column 130: cannot generate system identifier for general entity "filterManufacturer2"
    …0&filterManufacturer1=Sony%20Ericsson&filterManufacturer2=Sony" class="lev3Tit…

    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 271, Column 130: general entity "filterManufacturer2" not defined and no default entity
    …0&filterManufacturer1=Sony%20Ericsson&filterManufacturer2=Sony" class="lev3Tit…

    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 271, Column 149: reference not terminated by REFC delimiter
    …ufacturer1=Sony%20Ericsson&filterManufacturer2=Sony" class="lev3Title">Sony</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 149: reference to external entity in attribute value
    …ufacturer1=Sony%20Ericsson&filterManufacturer2=Sony" class="lev3Title">Sony</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 149: reference to entity "filterManufacturer2" for which no system identifier could be generated
    …ufacturer1=Sony%20Ericsson&filterManufacturer2=Sony" class="lev3Title">Sony</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 271, Column 129: entity was defined here
    …=0&filterManufacturer1=Sony%20Ericsson&filterManufacturer2=Sony" class="lev3Ti…
  • Warning Line 272, Column 113: reference not terminated by REFC delimiter
    …efony.html?filterPayType1=0&filterManufacturer1=HTC " class="lev3Title">HTC</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 272, Column 113: reference to external entity in attribute value
    …efony.html?filterPayType1=0&filterManufacturer1=HTC " class="lev3Title">HTC</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 272, Column 113: reference to entity "filterManufacturer1" for which no system identifier could be generated
    …efony.html?filterPayType1=0&filterManufacturer1=HTC " class="lev3Title">HTC</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 269, Column 93: entity was defined here
    …k/eshop/telefony.html?filterPayType1=0&filterManufacturer1=Nokia" class="lev3T…
  • Warning Line 273, Column 113: reference not terminated by REFC delimiter
    …y.html?filterPayType1=0&filterManufacturer1=Apple" class="lev3Title">iPhone</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 273, Column 113: reference to external entity in attribute value
    …y.html?filterPayType1=0&filterManufacturer1=Apple" class="lev3Title">iPhone</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 273, Column 113: reference to entity "filterManufacturer1" for which no system identifier could be generated
    …y.html?filterPayType1=0&filterManufacturer1=Apple" class="lev3Title">iPhone</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 269, Column 93: entity was defined here
    …k/eshop/telefony.html?filterPayType1=0&filterManufacturer1=Nokia" class="lev3T…
  • Error Line 650, Column 27: 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).

  • Warning Line 800, Column 211: cannot generate system identifier for general entity "phoneId"
    …p/zvyhodneny-program-wow.html?offer=2&phoneId=16894&option=2', '', 'Maximum za…

    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 800, Column 211: general entity "phoneId" not defined and no default entity
    …p/zvyhodneny-program-wow.html?offer=2&phoneId=16894&option=2', '', 'Maximum za…

    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 800, Column 218: reference not terminated by REFC delimiter
    …dneny-program-wow.html?offer=2&phoneId=16894&option=2', '', 'Maximum za 39,99 …

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

  • Error Line 800, Column 218: reference to entity "phoneId" for which no system identifier could be generated
    …dneny-program-wow.html?offer=2&phoneId=16894&option=2', '', 'Maximum za 39,99 …

    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 800, Column 210: entity was defined here
    …op/zvyhodneny-program-wow.html?offer=2&phoneId=16894&option=2', '', 'Maximum z…
  • Warning Line 800, Column 225: cannot generate system identifier for general entity "option"
    …rogram-wow.html?offer=2&phoneId=16894&option=2', '', 'Maximum za 39,99 &euro; …

    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 800, Column 225: general entity "option" not defined and no default entity
    …rogram-wow.html?offer=2&phoneId=16894&option=2', '', 'Maximum za 39,99 &euro; …

    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 800, Column 231: reference not terminated by REFC delimiter
    …-wow.html?offer=2&phoneId=16894&option=2', '', 'Maximum za 39,99 &euro; mesačn…

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

  • Error Line 800, Column 231: reference to entity "option" for which no system identifier could be generated
    …-wow.html?offer=2&phoneId=16894&option=2', '', 'Maximum za 39,99 &euro; mesačn…

    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 800, Column 224: entity was defined here
    …program-wow.html?offer=2&phoneId=16894&option=2', '', 'Maximum za 39,99 &euro;…
  • Warning Line 805, Column 242: reference not terminated by REFC delimiter
    …dneny-program-wow.html?offer=1&phoneId=17695&option=4', '', 'Nekonečno Extra z…

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

  • Error Line 805, Column 242: reference to entity "phoneId" for which no system identifier could be generated
    …dneny-program-wow.html?offer=1&phoneId=17695&option=4', '', 'Nekonečno Extra z…

    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 800, Column 210: entity was defined here
    …op/zvyhodneny-program-wow.html?offer=2&phoneId=16894&option=2', '', 'Maximum z…
  • Warning Line 805, Column 255: reference not terminated by REFC delimiter
    …-wow.html?offer=1&phoneId=17695&option=4', '', 'Nekonečno Extra za 29,99 &euro…

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

  • Error Line 805, Column 255: reference to entity "option" for which no system identifier could be generated
    …-wow.html?offer=1&phoneId=17695&option=4', '', 'Nekonečno Extra za 29,99 &euro…

    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 800, Column 224: entity was defined here
    …program-wow.html?offer=2&phoneId=16894&option=2', '', 'Maximum za 39,99 &euro;…
  • Warning Line 807, Column 224: reference not terminated by REFC delimiter
    …eshop/specialnaPonuka.html?a=a&phoneId=17695&offer=1&option=3', '', 'Nekonečno…

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

  • Error Line 807, Column 224: reference to entity "phoneId" for which no system identifier could be generated
    …eshop/specialnaPonuka.html?a=a&phoneId=17695&offer=1&option=3', '', 'Nekonečno…

    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 800, Column 210: entity was defined here
    …op/zvyhodneny-program-wow.html?offer=2&phoneId=16894&option=2', '', 'Maximum z…
  • Warning Line 807, Column 231: cannot generate system identifier for general entity "offer"
    …pecialnaPonuka.html?a=a&phoneId=17695&offer=1&option=3', '', 'Nekonečno a Noki…

    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 807, Column 231: general entity "offer" not defined and no default entity
    …pecialnaPonuka.html?a=a&phoneId=17695&offer=1&option=3', '', 'Nekonečno a Noki…

    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 807, Column 236: reference not terminated by REFC delimiter
    …lnaPonuka.html?a=a&phoneId=17695&offer=1&option=3', '', 'Nekonečno a Nokia Lum…

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

  • Error Line 807, Column 236: reference to entity "offer" for which no system identifier could be generated
    …lnaPonuka.html?a=a&phoneId=17695&offer=1&option=3', '', 'Nekonečno a Nokia Lum…

    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 807, Column 230: entity was defined here
    …specialnaPonuka.html?a=a&phoneId=17695&offer=1&option=3', '', 'Nekonečno a Nok…
  • Warning Line 807, Column 245: reference not terminated by REFC delimiter
    ….html?a=a&phoneId=17695&offer=1&option=3', '', 'Nekonečno a Nokia Lumia za 1 &…

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

  • Error Line 807, Column 245: reference to entity "option" for which no system identifier could be generated
    ….html?a=a&phoneId=17695&offer=1&option=3', '', 'Nekonečno a Nokia Lumia za 1 &…

    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 800, Column 224: entity was defined here
    …program-wow.html?offer=2&phoneId=16894&option=2', '', 'Maximum za 39,99 &euro;…
  • Warning Line 812, Column 224: reference not terminated by REFC delimiter
    …eshop/specialnaPonuka.html?a=a&phoneId=17695&offer=1&option=3', '', 'Nekonečno…

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

  • Error Line 812, Column 224: reference to entity "phoneId" for which no system identifier could be generated
    …eshop/specialnaPonuka.html?a=a&phoneId=17695&offer=1&option=3', '', 'Nekonečno…

    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 800, Column 210: entity was defined here
    …op/zvyhodneny-program-wow.html?offer=2&phoneId=16894&option=2', '', 'Maximum z…
  • Warning Line 812, Column 236: reference not terminated by REFC delimiter
    …lnaPonuka.html?a=a&phoneId=17695&offer=1&option=3', '', 'Nekonečno a Nokia Lum…

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

  • Error Line 812, Column 236: reference to entity "offer" for which no system identifier could be generated
    …lnaPonuka.html?a=a&phoneId=17695&offer=1&option=3', '', 'Nekonečno a Nokia Lum…

    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 807, Column 230: entity was defined here
    …specialnaPonuka.html?a=a&phoneId=17695&offer=1&option=3', '', 'Nekonečno a Nok…
  • Warning Line 812, Column 245: reference not terminated by REFC delimiter
    ….html?a=a&phoneId=17695&offer=1&option=3', '', 'Nekonečno a Nokia Lumia za 1 &…

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

  • Error Line 812, Column 245: reference to entity "option" for which no system identifier could be generated
    ….html?a=a&phoneId=17695&offer=1&option=3', '', 'Nekonečno a Nokia Lumia za 1 &…

    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 800, Column 224: entity was defined here
    …program-wow.html?offer=2&phoneId=16894&option=2', '', 'Maximum za 39,99 &euro;…
  • Warning Line 818, Column 206: cannot generate system identifier for general entity "benefitId"
    …k/eshop/directBuy.html?packageId=3750&benefitId=15162&phoneId=18399&checkout=1…

    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 818, Column 206: general entity "benefitId" not defined and no default entity
    …k/eshop/directBuy.html?packageId=3750&benefitId=15162&phoneId=18399&checkout=1…

    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 818, Column 215: reference not terminated by REFC delimiter
    …irectBuy.html?packageId=3750&benefitId=15162&phoneId=18399&checkout=1', '', 'M…

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

  • Error Line 818, Column 215: reference to entity "benefitId" for which no system identifier could be generated
    …irectBuy.html?packageId=3750&benefitId=15162&phoneId=18399&checkout=1', '', 'M…

    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 818, Column 205: entity was defined here
    …sk/eshop/directBuy.html?packageId=3750&benefitId=15162&phoneId=18399&checkout=…
  • Warning Line 818, Column 229: reference not terminated by REFC delimiter
    …packageId=3750&benefitId=15162&phoneId=18399&checkout=1', '', 'Maximum a Sony …

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

  • Error Line 818, Column 229: reference to entity "phoneId" for which no system identifier could be generated
    …packageId=3750&benefitId=15162&phoneId=18399&checkout=1', '', 'Maximum a Sony …

    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 800, Column 210: entity was defined here
    …op/zvyhodneny-program-wow.html?offer=2&phoneId=16894&option=2', '', 'Maximum z…
  • Warning Line 818, Column 236: cannot generate system identifier for general entity "checkout"
    …Id=3750&benefitId=15162&phoneId=18399&checkout=1', '', 'Maximum a Sony Xperia …

    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 818, Column 236: general entity "checkout" not defined and no default entity
    …Id=3750&benefitId=15162&phoneId=18399&checkout=1', '', 'Maximum a Sony Xperia …

    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 818, Column 244: reference not terminated by REFC delimiter
    …benefitId=15162&phoneId=18399&checkout=1', '', 'Maximum a Sony Xperia J za 20 …

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

  • Error Line 818, Column 244: reference to entity "checkout" for which no system identifier could be generated
    …benefitId=15162&phoneId=18399&checkout=1', '', 'Maximum a Sony Xperia J za 20 …

    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 818, Column 235: entity was defined here
    …eId=3750&benefitId=15162&phoneId=18399&checkout=1', '', 'Maximum a Sony Xperia…
  • Warning Line 822, Column 233: reference not terminated by REFC delimiter
    …eshop/specialnaPonuka.html?a=a&phoneId=17195&offer=1&option=2', '', 'Zvýhodnen…

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

  • Error Line 822, Column 233: reference to entity "phoneId" for which no system identifier could be generated
    …eshop/specialnaPonuka.html?a=a&phoneId=17195&offer=1&option=2', '', 'Zvýhodnen…

    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 800, Column 210: entity was defined here
    …op/zvyhodneny-program-wow.html?offer=2&phoneId=16894&option=2', '', 'Maximum z…
  • Warning Line 822, Column 245: reference not terminated by REFC delimiter
    …lnaPonuka.html?a=a&phoneId=17195&offer=1&option=2', '', 'Zvýhodnená WOW ponuka…

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

  • Error Line 822, Column 245: reference to entity "offer" for which no system identifier could be generated
    …lnaPonuka.html?a=a&phoneId=17195&offer=1&option=2', '', 'Zvýhodnená WOW ponuka…

    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 807, Column 230: entity was defined here
    …specialnaPonuka.html?a=a&phoneId=17695&offer=1&option=3', '', 'Nekonečno a Nok…
  • Warning Line 822, Column 254: reference not terminated by REFC delimiter
    ….html?a=a&phoneId=17195&offer=1&option=2', '', 'Zvýhodnená WOW ponuka', 's tel…

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

  • Error Line 822, Column 254: reference to entity "option" for which no system identifier could be generated
    ….html?a=a&phoneId=17195&offer=1&option=2', '', 'Zvýhodnená WOW ponuka', 's tel…

    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 800, Column 224: entity was defined here
    …program-wow.html?offer=2&phoneId=16894&option=2', '', 'Maximum za 39,99 &euro;…
  • Warning Line 823, Column 219: reference not terminated by REFC delimiter
    …shop/directBuy.html?checkout=1&phoneId=15897&benefitId=15162&packageId=3744', …

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

  • Error Line 823, Column 219: reference to entity "phoneId" for which no system identifier could be generated
    …shop/directBuy.html?checkout=1&phoneId=15897&benefitId=15162&packageId=3744', …

    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 800, Column 210: entity was defined here
    …op/zvyhodneny-program-wow.html?offer=2&phoneId=16894&option=2', '', 'Maximum z…
  • Warning Line 823, Column 235: reference not terminated by REFC delimiter
    …tml?checkout=1&phoneId=15897&benefitId=15162&packageId=3744', '', 'Zvýhodnená …

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

  • Error Line 823, Column 235: reference to entity "benefitId" for which no system identifier could be generated
    …tml?checkout=1&phoneId=15897&benefitId=15162&packageId=3744', '', 'Zvýhodnená …

    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 818, Column 205: entity was defined here
    …sk/eshop/directBuy.html?packageId=3750&benefitId=15162&phoneId=18399&checkout=…
  • Warning Line 823, Column 242: cannot generate system identifier for general entity "packageId"
    …ckout=1&phoneId=15897&benefitId=15162&packageId=3744', '', 'Zvýhodnená WOW pon…

    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 823, Column 242: general entity "packageId" not defined and no default entity
    …ckout=1&phoneId=15897&benefitId=15162&packageId=3744', '', 'Zvýhodnená WOW pon…

    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 823, Column 251: reference not terminated by REFC delimiter
    …honeId=15897&benefitId=15162&packageId=3744', '', 'Zvýhodnená WOW ponuka', 's …

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

  • Error Line 823, Column 251: reference to entity "packageId" for which no system identifier could be generated
    …honeId=15897&benefitId=15162&packageId=3744', '', 'Zvýhodnená WOW ponuka', 's …

    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 823, Column 241: entity was defined here
    …eckout=1&phoneId=15897&benefitId=15162&packageId=3744', '', 'Zvýhodnená WOW po…
  • Warning Line 830, Column 208: reference not terminated by REFC delimiter
    …eshop/specialnaPonuka.html?a=a&phoneId=10094&offer=1&option=3', '', 'Zvýhodnen…

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

  • Error Line 830, Column 208: reference to entity "phoneId" for which no system identifier could be generated
    …eshop/specialnaPonuka.html?a=a&phoneId=10094&offer=1&option=3', '', 'Zvýhodnen…

    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 800, Column 210: entity was defined here
    …op/zvyhodneny-program-wow.html?offer=2&phoneId=16894&option=2', '', 'Maximum z…
  • Warning Line 830, Column 220: reference not terminated by REFC delimiter
    …lnaPonuka.html?a=a&phoneId=10094&offer=1&option=3', '', 'Zvýhodnená WOW ponuka…

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

  • Error Line 830, Column 220: reference to entity "offer" for which no system identifier could be generated
    …lnaPonuka.html?a=a&phoneId=10094&offer=1&option=3', '', 'Zvýhodnená WOW ponuka…

    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 807, Column 230: entity was defined here
    …specialnaPonuka.html?a=a&phoneId=17695&offer=1&option=3', '', 'Nekonečno a Nok…
  • Warning Line 830, Column 229: reference not terminated by REFC delimiter
    ….html?a=a&phoneId=10094&offer=1&option=3', '', 'Zvýhodnená WOW ponuka', 's tel…

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

  • Error Line 830, Column 229: reference to entity "option" for which no system identifier could be generated
    ….html?a=a&phoneId=10094&offer=1&option=3', '', 'Zvýhodnená WOW ponuka', 's tel…

    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 800, Column 224: entity was defined here
    …program-wow.html?offer=2&phoneId=16894&option=2', '', 'Maximum za 39,99 &euro;…
  • Warning Line 854, Column 113: reference not terminated by REFC delimiter
    …dneny-program-wow.html?offer=1&phoneId=17695&option=4" title="Nekonečno Extra …

    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 854, Column 113: reference to external entity in attribute value
    …dneny-program-wow.html?offer=1&phoneId=17695&option=4" title="Nekonečno Extra …

    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 854, Column 113: reference to entity "phoneId" for which no system identifier could be generated
    …dneny-program-wow.html?offer=1&phoneId=17695&option=4" title="Nekonečno Extra …

    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 800, Column 210: entity was defined here
    …op/zvyhodneny-program-wow.html?offer=2&phoneId=16894&option=2', '', 'Maximum z…
  • Warning Line 854, Column 126: reference not terminated by REFC delimiter
    …-wow.html?offer=1&phoneId=17695&option=4" title="Nekonečno Extra za 29,99 &eur…

    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 854, Column 126: reference to external entity in attribute value
    …-wow.html?offer=1&phoneId=17695&option=4" title="Nekonečno Extra za 29,99 &eur…

    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 854, Column 126: reference to entity "option" for which no system identifier could be generated
    …-wow.html?offer=1&phoneId=17695&option=4" title="Nekonečno Extra za 29,99 &eur…

    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 800, Column 224: entity was defined here
    …program-wow.html?offer=2&phoneId=16894&option=2', '', 'Maximum za 39,99 &euro;…
  • Warning Line 854, Column 167: reference not terminated by REFC delimiter
    …ow.html?offer=1&phoneId=17695&option=4" title="Nekonečno Extra za 29,99 &euro">

    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 855, Column 88: reference not terminated by REFC delimiter
    …0" alt="Nekonečno Extra za 29,99 &euro" title="Nekonečno Extra za 29,99 &euro"…

    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 855, Column 127: reference not terminated by REFC delimiter
    … title="Nekonečno Extra za 29,99 &euro" src="http://img.orange.sk/orange_sk/im…

    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 864, Column 113: reference not terminated by REFC delimiter
    …dneny-program-wow.html?offer=2&phoneId=16894&option=2" title="Maximum za 39,99…

    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 864, Column 113: reference to external entity in attribute value
    …dneny-program-wow.html?offer=2&phoneId=16894&option=2" title="Maximum za 39,99…

    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 864, Column 113: reference to entity "phoneId" for which no system identifier could be generated
    …dneny-program-wow.html?offer=2&phoneId=16894&option=2" title="Maximum za 39,99…

    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 800, Column 210: entity was defined here
    …op/zvyhodneny-program-wow.html?offer=2&phoneId=16894&option=2', '', 'Maximum z…
  • Warning Line 864, Column 126: reference not terminated by REFC delimiter
    …ogram-wow.html?offer=2&phoneId=16894&option=2" title="Maximum za 39,99 &euro;">

    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 864, Column 126: reference to external entity in attribute value
    …ogram-wow.html?offer=2&phoneId=16894&option=2" title="Maximum za 39,99 &euro;">

    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 864, Column 126: reference to entity "option" for which no system identifier could be generated
    …ogram-wow.html?offer=2&phoneId=16894&option=2" title="Maximum za 39,99 &euro;">

    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 800, Column 224: entity was defined here
    …program-wow.html?offer=2&phoneId=16894&option=2', '', 'Maximum za 39,99 &euro;…
  • Warning Line 946, Column 141: reference not terminated by REFC delimiter
    ….sk/eshop/zvyhodneny-program-wow.html?offer=2&phoneId=16894&option=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 946, Column 141: reference to external entity in attribute value
    ….sk/eshop/zvyhodneny-program-wow.html?offer=2&phoneId=16894&option=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 946, Column 141: reference to entity "phoneId" for which no system identifier could be generated
    ….sk/eshop/zvyhodneny-program-wow.html?offer=2&phoneId=16894&option=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 800, Column 210: entity was defined here
    …op/zvyhodneny-program-wow.html?offer=2&phoneId=16894&option=2', '', 'Maximum z…
  • Warning Line 946, Column 154: reference not terminated by REFC delimiter
    ….sk/eshop/zvyhodneny-program-wow.html?offer=2&phoneId=16894&option=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 946, Column 154: reference to external entity in attribute value
    ….sk/eshop/zvyhodneny-program-wow.html?offer=2&phoneId=16894&option=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 946, Column 154: reference to entity "option" for which no system identifier could be generated
    ….sk/eshop/zvyhodneny-program-wow.html?offer=2&phoneId=16894&option=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 800, Column 224: entity was defined here
    …program-wow.html?offer=2&phoneId=16894&option=2', '', 'Maximum za 39,99 &euro;…
  • Warning Line 1017, Column 115: reference not terminated by REFC delimiter
    …shop/directBuy.html?checkout=1&phoneId=17699&benefitId=15162&packageId=3744" t…

    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 1017, Column 115: reference to external entity in attribute value
    …shop/directBuy.html?checkout=1&phoneId=17699&benefitId=15162&packageId=3744" t…

    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 1017, Column 115: reference to entity "phoneId" for which no system identifier could be generated
    …shop/directBuy.html?checkout=1&phoneId=17699&benefitId=15162&packageId=3744" t…

    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 800, Column 210: entity was defined here
    …op/zvyhodneny-program-wow.html?offer=2&phoneId=16894&option=2', '', 'Maximum z…
  • Warning Line 1017, Column 131: reference not terminated by REFC delimiter
    …tml?checkout=1&phoneId=17699&benefitId=15162&packageId=3744" title=""><img src…

    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 1017, Column 131: reference to external entity in attribute value
    …tml?checkout=1&phoneId=17699&benefitId=15162&packageId=3744" title=""><img src…

    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 1017, Column 131: reference to entity "benefitId" for which no system identifier could be generated
    …tml?checkout=1&phoneId=17699&benefitId=15162&packageId=3744" title=""><img src…

    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 818, Column 205: entity was defined here
    …sk/eshop/directBuy.html?packageId=3750&benefitId=15162&phoneId=18399&checkout=…
  • Warning Line 1017, Column 147: reference not terminated by REFC delimiter
    …honeId=17699&benefitId=15162&packageId=3744" title=""><img src="http://img.ora…

    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 1017, Column 147: reference to external entity in attribute value
    …honeId=17699&benefitId=15162&packageId=3744" title=""><img src="http://img.ora…

    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 1017, Column 147: reference to entity "packageId" for which no system identifier could be generated
    …honeId=17699&benefitId=15162&packageId=3744" title=""><img src="http://img.ora…

    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 823, Column 241: entity was defined here
    …eckout=1&phoneId=15897&benefitId=15162&packageId=3744', '', 'Zvýhodnená WOW po…
  • Warning Line 1044, Column 115: reference not terminated by REFC delimiter
    …shop/directBuy.html?checkout=1&phoneId=18293&benefitId=15162&packageId=3744" t…

    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 1044, Column 115: reference to external entity in attribute value
    …shop/directBuy.html?checkout=1&phoneId=18293&benefitId=15162&packageId=3744" t…

    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 1044, Column 115: reference to entity "phoneId" for which no system identifier could be generated
    …shop/directBuy.html?checkout=1&phoneId=18293&benefitId=15162&packageId=3744" t…

    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 800, Column 210: entity was defined here
    …op/zvyhodneny-program-wow.html?offer=2&phoneId=16894&option=2', '', 'Maximum z…
  • Warning Line 1044, Column 131: reference not terminated by REFC delimiter
    …tml?checkout=1&phoneId=18293&benefitId=15162&packageId=3744" title=""><img src…

    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 1044, Column 131: reference to external entity in attribute value
    …tml?checkout=1&phoneId=18293&benefitId=15162&packageId=3744" title=""><img src…

    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 1044, Column 131: reference to entity "benefitId" for which no system identifier could be generated
    …tml?checkout=1&phoneId=18293&benefitId=15162&packageId=3744" title=""><img src…

    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 818, Column 205: entity was defined here
    …sk/eshop/directBuy.html?packageId=3750&benefitId=15162&phoneId=18399&checkout=…
  • Warning Line 1044, Column 147: reference not terminated by REFC delimiter
    …honeId=18293&benefitId=15162&packageId=3744" title=""><img src="http://img.ora…

    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 1044, Column 147: reference to external entity in attribute value
    …honeId=18293&benefitId=15162&packageId=3744" title=""><img src="http://img.ora…

    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 1044, Column 147: reference to entity "packageId" for which no system identifier could be generated
    …honeId=18293&benefitId=15162&packageId=3744" title=""><img src="http://img.ora…

    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 823, Column 241: entity was defined here
    …eckout=1&phoneId=15897&benefitId=15162&packageId=3744', '', 'Zvýhodnená WOW po…
  • Error Line 1633, Column 33: 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).

  • Warning Line 1836, Column 95: cannot generate system identifier for general entity "survey_id"
    …80/cation/ipanel/start?user_id=RANDOM&survey_id=114&css=orange" 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 1836, Column 95: general entity "survey_id" not defined and no default entity
    …80/cation/ipanel/start?user_id=RANDOM&survey_id=114&css=orange" 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 1836, Column 104: reference not terminated by REFC delimiter
    …/ipanel/start?user_id=RANDOM&survey_id=114&css=orange" target="_blank"><span c…

    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 1836, Column 104: reference to external entity in attribute value
    …/ipanel/start?user_id=RANDOM&survey_id=114&css=orange" target="_blank"><span c…

    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 1836, Column 104: reference to entity "survey_id" for which no system identifier could be generated
    …/ipanel/start?user_id=RANDOM&survey_id=114&css=orange" target="_blank"><span c…

    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 1836, Column 94: entity was defined here
    …080/cation/ipanel/start?user_id=RANDOM&survey_id=114&css=orange" target="_blan…
  • Warning Line 1836, Column 109: cannot generate system identifier for general entity "css"
    …el/start?user_id=RANDOM&survey_id=114&css=orange" target="_blank"><span class=…

    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 1836, Column 109: general entity "css" not defined and no default entity
    …el/start?user_id=RANDOM&survey_id=114&css=orange" target="_blank"><span class=…

    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 1836, Column 112: reference not terminated by REFC delimiter
    …start?user_id=RANDOM&survey_id=114&css=orange" target="_blank"><span class="vi…

    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 1836, Column 112: reference to external entity in attribute value
    …start?user_id=RANDOM&survey_id=114&css=orange" target="_blank"><span class="vi…

    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 1836, Column 112: reference to entity "css" for which no system identifier could be generated
    …start?user_id=RANDOM&survey_id=114&css=orange" target="_blank"><span class="vi…

    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 1836, Column 108: entity was defined here
    …nel/start?user_id=RANDOM&survey_id=114&css=orange" target="_blank"><span class…
  • Warning Line 1875, Column 154: cannot generate system identifier for general entity "guid"
    …com/pagead/conversion/1025639625/?label=UZdPCMfM8QIQyYmI6QM&guid=ON&script=0"/>

    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 1875, Column 154: general entity "guid" not defined and no default entity
    …com/pagead/conversion/1025639625/?label=UZdPCMfM8QIQyYmI6QM&guid=ON&script=0"/>

    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 1875, Column 158: reference not terminated by REFC delimiter
    …com/pagead/conversion/1025639625/?label=UZdPCMfM8QIQyYmI6QM&guid=ON&script=0"/>

    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 1875, Column 158: reference to external entity in attribute value
    …com/pagead/conversion/1025639625/?label=UZdPCMfM8QIQyYmI6QM&guid=ON&script=0"/>

    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 1875, Column 158: reference to entity "guid" for which no system identifier could be generated
    …com/pagead/conversion/1025639625/?label=UZdPCMfM8QIQyYmI6QM&guid=ON&script=0"/>

    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 1875, Column 153: entity was defined here
    …com/pagead/conversion/1025639625/?label=UZdPCMfM8QIQyYmI6QM&guid=ON&script=0"/>
  • Warning Line 1875, Column 162: cannot generate system identifier for general entity "script"
    …com/pagead/conversion/1025639625/?label=UZdPCMfM8QIQyYmI6QM&guid=ON&script=0"/>

    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 1875, Column 162: general entity "script" not defined and no default entity
    …com/pagead/conversion/1025639625/?label=UZdPCMfM8QIQyYmI6QM&guid=ON&script=0"/>

    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 1875, Column 168: reference not terminated by REFC delimiter
    …com/pagead/conversion/1025639625/?label=UZdPCMfM8QIQyYmI6QM&guid=ON&script=0"/>

    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 1875, Column 168: reference to external entity in attribute value
    …com/pagead/conversion/1025639625/?label=UZdPCMfM8QIQyYmI6QM&guid=ON&script=0"/>

    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 1875, Column 168: reference to entity "script" for which no system identifier could be generated
    …com/pagead/conversion/1025639625/?label=UZdPCMfM8QIQyYmI6QM&guid=ON&script=0"/>

    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 1875, Column 161: entity was defined here
    …com/pagead/conversion/1025639625/?label=UZdPCMfM8QIQyYmI6QM&guid=ON&script=0"/>
  • Error Line 1972, Column 88: document type does not allow element "a" here
    …_phone_number_02').innerHTML = '[ <a href="tel:0905905905">0905 905 905</a> ]';

    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 1977, Column 88: document type does not allow element "a" here
    …_phone_number_02').innerHTML = '[ <a href="tel:0908908908">0908 908 908</a> ]';

    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 1982, Column 88: document type does not allow element "a" here
    …_phone_number_02').innerHTML = '[ <a href="tel:0908908908">0908 908 908</a> ]';

    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 1987, Column 88: document type does not allow element "a" here
    …_phone_number_02').innerHTML = '[ <a href="tel:0905905905">0905 905 905</a> ]';

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

Visitor Analysis

Daily Visitor
  • 2.800 visits
Daily Visitor