AutoScout24: Europas großer Automarkt für Gebrauchtwagen und Neuwagen. Ihr Auto-Portal für Autokauf & Autoverkauf mit News und Informationen rund um das Auto. ...

autoscout24.at
  • Domain Name
    autoscout24.at
  • Favicon
  • Google Page Rank
    6
  • Alexa Rank
    #28775
  • Page Size
    60.3 KB
  • Ip Address
    92.42.227.69
  • Heading
    H1: 1, H2: 2, H3: 4, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
    AutoScout24 Autobörse: Europas Automarkt für Gebrauchtwagen und Neuwagen
  • Meta Keyword
    Gebrauchtwagen Autos Auto Automarkt Autokauf Autoverkauf
  • Meta Description
    AutoScout24: Europas großer Automarkt für Gebrauchtwagen und Neuwagen. Ihr Auto-Portal für Autokauf & Autoverkauf mit News und Informationen rund um das Auto.

Technical Analysis

  • Webserver
    Microsoft-IIS/7.5
  • Ip Address
    92.42.227.69
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from autoscout24.at.

HTML Analysis

  • cache-control: private
  • content-type: text/html; charset=utf-8
  • content-encoding: gzip
  • vary: Accept-Encoding
  • server: Microsoft-IIS/7.5
  • x-aspnetmvc-version: 3.0
  • x-aspnet-version: 4.0.30319
  • sid: LWEBATV001
  • x-powered-by: ASP.NET
  • date: Tue, 30 Jul 2013 15:41:56 GMT
  • content-length: 16489
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
% Copyright (c)2012 by NIC.AT (1)
%
% Restricted rights.
%
% Except for agreed Internet operational purposes, no part of this
% information may be reproduced, stored in a retrieval system, or
% transmitted, in any form or by any means, electronic, mechanical,
% recording, or otherwise, without prior permission of NIC.AT on behalf
% of itself and/or the copyright holders. Any use of this material to
% target advertising or similar activities is explicitly forbidden and
% can be prosecuted.
%
% It is furthermore strictly forbidden to use the Whois-Database in such
% a way that jeopardizes or could jeopardize the stability of the
% technical systems of NIC.AT under any circumstances. In particular,
% this includes any misuse of the Whois-Database and any use of the
% Whois-Database which disturbs its operation.
%
% Should the user violate these points, NIC.AT reserves the right to
% deactivate the Whois-Database entirely or partly for the user.
% Moreover, the user shall be held liable for any and all damage
% arising from a violation of these points.

domain: autoscout24.at
registrant: AG8210303-NICAT
admin-c: SIMA5413869-NICAT
tech-c: AG7952625-NICAT
nserver: dnslbrz2.autoscout24.com
nserver: dnslbrz3.autoscout24.com
changed: 20110908 17:20:29
source: AT-DOM

personname: Raimond Grempels
organization: AutoScout24 GmbH
street address: Dingolfinger Str. 1-15
postal code: 81673
city: Muenchen
country: Germany
phone: +4989444560
fax-no: +4989444563000
e-mail: email
nic-hdl: AG8210303-NICAT
changed: 20111103 11:59:07
source: AT-DOM

personname: Raimond Grempels
organization: Scout24 International Management AG
street address: Neuhofstrasse 4
postal code: 6341
city: Baar
country: Switzerland
phone: +41417687776
fax-no: +41417687885
e-mail: email
nic-hdl: SIMA5413869-NICAT
changed: 20110420 13:57:24
source: AT-DOM

personname: DNS Admin
organization: AutoScout24 GmbH
street address: Dingolfinger Str. 1-15
postal code: 81673
city: Muenchen
country: Germany
phone: +4989444560
fax-no: +4989444563000
e-mail: email
nic-hdl: AG7952625-NICAT
changed: 20111028 19:20:30
source: AT-DOM

DNS Analysis


DNS servers
dnslbrz2.autoscout24.com
dnslbrz3.autoscout24.com


DNS Records

Answer records
autoscout24.at SOA
server: dnslbrz3.autoscout24.com
email: hostmaster@autoscout24.de
serial: 2008020622
refresh: 86400
retry: 7200
expire: 604800
minimum ttl: 86400
86400s
autoscout24.at NS  dnslbrz3.autoscout24.com 86400s
autoscout24.at NS  dnslbrz2.autoscout24.com 86400s
autoscout24.at A 92.42.227.69 900s
autoscout24.at MX
preference: 100
exchange: mail3.autoscout24.com
900s
autoscout24.at MX
preference: 100
exchange: mail4.autoscout24.com
900s
autoscout24.at MX
preference: 10
exchange: mx1.autoscout24.com
900s
autoscout24.at MX
preference: 10
exchange: mx0.autoscout24.com
900s

Authority records

Additional records
dnslbrz3.autoscout24.com A 92.42.224.6 900s
dnslbrz2.autoscout24.com A 92.42.228.6 900s
mail3.autoscout24.com A 92.42.225.35 900s
mail4.autoscout24.com A 92.42.225.34 900s
mx1.autoscout24.com A 92.42.225.92 900s
mx0.autoscout24.com A 92.42.225.93 900s

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 113 Errors
  • 20 Warnings
Ratio Text/Html
  • 0.6438811047217947
Message Error
  • Error Line 145, Column 156: end tag for element "Div" which is not open
    …hrem Browser, um alle Funktionalitäten unserer Webseite nutzen zu können.</Div>

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

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

  • Error Line 152, Column 11: end tag for "div" omitted, but OMITTAG NO was specified
    </noscript>

    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 140, Column 1: start tag was here
    <div style="display:block" id="inpagemsg" class="msg-error">
  • Error Line 169, Column 96: there is no attribute "onMouseOver"
    …ass="used-car-ico-active" onMouseOver="setHoverLabelTxt(&#39;quickSearchTitle&…

    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 169, Column 181: there is no attribute "onMouseOut"
    …#39;Gebrauchtwagen&#39;);" onMouseOut="setHoverLabelTxt(&#39;quickSearchTitle&…

    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 196, Column 66: end tag for element "Label" which is not open
                    <label class="label-disabled model">Modell</Label>

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

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

  • Error Line 197, Column 21: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
                    <div>

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

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

  • Error Line 198, Column 60: duplicate specification of attribute "name"
                        <select name="model1" id="model1" name="model">

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

  • Error Line 203, Column 20: end tag for "label" omitted, but OMITTAG NO was specified
                  </div>

    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 196, Column 17: start tag was here
                    <label class="label-disabled model">Modell</Label>
  • Error Line 209, Column 44: end tag for element "Label" which is not open
                    <label>Preis (€) bis</Label>

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

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

  • Error Line 210, Column 43: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
                    <div class="marginbottom8">

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

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

  • Error Line 239, Column 49: end tag for element "Label" which is not open
                    <label>Kilometerstand bis</Label>

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

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

  • Error Line 240, Column 21: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
                    <div>

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

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

  • Error Line 263, Column 20: end tag for "label" omitted, but OMITTAG NO was specified
                  </div>

    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 239, Column 17: start tag was here
                    <label>Kilometerstand bis</Label>
  • Error Line 263, Column 20: end tag for "label" omitted, but OMITTAG NO was specified
                  </div>

    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 209, Column 17: start tag was here
                    <label>Preis (€) bis</Label>
  • Error Line 265, Column 48: end tag for element "Label" which is not open
                    <label>Erstzulassung von</Label>

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

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

  • Error Line 266, Column 43: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
                    <div class="marginbottom8">

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

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

  • Error Line 313, Column 35: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
                    <div class="label">

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

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

  • Error Line 319, Column 21: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
                    <div>

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

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

  • Error Line 324, Column 20: end tag for "label" omitted, but OMITTAG NO was specified
                  </div>

    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 265, Column 17: start tag was here
                    <label>Erstzulassung von</Label>
  • Error Line 339, Column 59: end tag for element "Label" which is not open
                        <label class="__radius">Umkreis</Label>

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

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

  • Error Line 340, Column 25: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
                        <div>

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

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

  • Error Line 351, Column 24: end tag for "label" omitted, but OMITTAG NO was specified
                      </div>

    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 339, Column 21: start tag was here
                        <label class="__radius">Umkreis</Label>
  • Error Line 373, Column 59: end tag for element "Span" which is not open
                  <span id="tcountLabel"><span>Fahrzeuge</Span></span>

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

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

  • Error Line 374, Column 18: end tag for "span" omitted, but OMITTAG NO was specified
                </div>

    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 373, Column 15: start tag was here
                  <span id="tcountLabel"><span>Fahrzeuge</Span></span>
  • Error Line 447, Column 264: there is no attribute "USEMAP"
    …oscout24.com/de-AT/110130/2/20130129105809_img_0.jpg" USEMAP='#map' ></a></div>

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

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

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

  • Error Line 447, Column 271: required attribute "alt" not specified
    …oscout24.com/de-AT/110130/2/20130129105809_img_0.jpg" USEMAP='#map' ></a></div>

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

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

  • Error Line 447, Column 275: end tag for "img" omitted, but OMITTAG NO was specified
    …oscout24.com/de-AT/110130/2/20130129105809_img_0.jpg" USEMAP='#map' ></a></div>

    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 447, Column 176: start tag was here
    …utoscout24.at/AIPrivateDecision.aspx'><img src="http://cmspic.autoscout24.com/…
  • Error Line 450, Column 52: end tag for "input" omitted, but OMITTAG NO was specified
    		<input type="button" value="Kostenlos verkaufen">

    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 450, Column 3: start tag was here
    		<input type="button" value="Kostenlos verkaufen">
  • Error Line 476, Column 36: required attribute "type" not specified
    	<div class="marginTopFontM"><style>

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

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

  • Error Line 476, Column 36: document type does not allow element "style" here
    	<div class="marginTopFontM"><style>

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

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

  • Warning Line 597, Column 112: cannot generate system identifier for general entity "intcidm"
    …24.at/info/magazine?toparticle=335234&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag…

    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 597, Column 112: general entity "intcidm" not defined and no default entity
    …24.at/info/magazine?toparticle=335234&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag…

    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 597, Column 119: reference not terminated by REFC delimiter
    …nfo/magazine?toparticle=335234&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-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 597, Column 119: reference to external entity in attribute value
    …nfo/magazine?toparticle=335234&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-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 597, Column 119: reference to entity "intcidm" for which no system identifier could be generated
    …nfo/magazine?toparticle=335234&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-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 597, Column 111: entity was defined here
    …t24.at/info/magazine?toparticle=335234&intcidm=HP-OCBox2-Mag-Teaser1&magcid=ma…
  • Warning Line 597, Column 142: cannot generate system identifier for general entity "magcid"
    …=335234&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-art" target="_parent"><i…

    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 597, Column 142: general entity "magcid" not defined and no default entity
    …=335234&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-art" target="_parent"><i…

    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 597, Column 148: reference not terminated by REFC delimiter
    …4&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-art" target="_parent"><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 597, Column 148: reference to external entity in attribute value
    …4&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-art" target="_parent"><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 597, Column 148: reference to entity "magcid" for which no system identifier could be generated
    …4&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-art" target="_parent"><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 597, Column 141: entity was defined here
    …e=335234&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-art" target="_parent"><…
  • Error Line 597, Column 262: required attribute "alt" not specified
    …://cmspic.autoscout24.com/de-AT/110118/5/20130129140749_img_0.jpg" /></a></div>

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

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

  • Warning Line 599, Column 94: reference not terminated by REFC delimiter
    …nfo/magazine?toparticle=335234&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-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 599, Column 94: reference to external entity in attribute value
    …nfo/magazine?toparticle=335234&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-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 599, Column 94: reference to entity "intcidm" for which no system identifier could be generated
    …nfo/magazine?toparticle=335234&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-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 597, Column 111: entity was defined here
    …t24.at/info/magazine?toparticle=335234&intcidm=HP-OCBox2-Mag-Teaser1&magcid=ma…
  • Warning Line 599, Column 123: reference not terminated by REFC delimiter
    …4&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-art" target="_parent">Honda 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.

  • Warning Line 599, Column 123: reference to external entity in attribute value
    …4&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-art" target="_parent">Honda 1.…

    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 599, Column 123: reference to entity "magcid" for which no system identifier could be generated
    …4&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-art" target="_parent">Honda 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 597, Column 141: entity was defined here
    …e=335234&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-art" target="_parent"><…
  • Warning Line 600, Column 185: reference not terminated by REFC delimiter
    …nfo/magazine?toparticle=335234&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-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 600, Column 185: reference to external entity in attribute value
    …nfo/magazine?toparticle=335234&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-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 600, Column 185: reference to entity "intcidm" for which no system identifier could be generated
    …nfo/magazine?toparticle=335234&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-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 597, Column 111: entity was defined here
    …t24.at/info/magazine?toparticle=335234&intcidm=HP-OCBox2-Mag-Teaser1&magcid=ma…
  • Warning Line 600, Column 214: reference not terminated by REFC delimiter
    …4&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-art" target="_parent">Mehr</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 600, Column 214: reference to external entity in attribute value
    …4&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-art" target="_parent">Mehr</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 600, Column 214: reference to entity "magcid" for which no system identifier could be generated
    …4&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-art" target="_parent">Mehr</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 597, Column 141: entity was defined here
    …e=335234&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-art" target="_parent"><…
  • Warning Line 604, Column 119: reference not terminated by REFC delimiter
    …nfo/magazine?toparticle=334704&intcidm=HP-OCBox2-Mag-Teaser2&magcid=mag-home-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 604, Column 119: reference to external entity in attribute value
    …nfo/magazine?toparticle=334704&intcidm=HP-OCBox2-Mag-Teaser2&magcid=mag-home-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 604, Column 119: reference to entity "intcidm" for which no system identifier could be generated
    …nfo/magazine?toparticle=334704&intcidm=HP-OCBox2-Mag-Teaser2&magcid=mag-home-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 597, Column 111: entity was defined here
    …t24.at/info/magazine?toparticle=335234&intcidm=HP-OCBox2-Mag-Teaser1&magcid=ma…
  • Warning Line 604, Column 148: reference not terminated by REFC delimiter
    …4&intcidm=HP-OCBox2-Mag-Teaser2&magcid=mag-home-art" target="_parent"><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 604, Column 148: reference to external entity in attribute value
    …4&intcidm=HP-OCBox2-Mag-Teaser2&magcid=mag-home-art" target="_parent"><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 604, Column 148: reference to entity "magcid" for which no system identifier could be generated
    …4&intcidm=HP-OCBox2-Mag-Teaser2&magcid=mag-home-art" target="_parent"><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 597, Column 141: entity was defined here
    …e=335234&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-art" target="_parent"><…
  • Error Line 604, Column 262: required attribute "alt" not specified
    …://cmspic.autoscout24.com/de-AT/110118/5/20130129140749_img_1.jpg" /></a></div>

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

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

  • Warning Line 606, Column 94: reference not terminated by REFC delimiter
    …nfo/magazine?toparticle=334704&intcidm=HP-OCBox2-Mag-Teaser2&magcid=mag-home-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 606, Column 94: reference to external entity in attribute value
    …nfo/magazine?toparticle=334704&intcidm=HP-OCBox2-Mag-Teaser2&magcid=mag-home-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 606, Column 94: reference to entity "intcidm" for which no system identifier could be generated
    …nfo/magazine?toparticle=334704&intcidm=HP-OCBox2-Mag-Teaser2&magcid=mag-home-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 597, Column 111: entity was defined here
    …t24.at/info/magazine?toparticle=335234&intcidm=HP-OCBox2-Mag-Teaser1&magcid=ma…
  • Warning Line 606, Column 123: reference not terminated by REFC delimiter
    …4&intcidm=HP-OCBox2-Mag-Teaser2&magcid=mag-home-art" target="_parent">60 Jahre…

    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 606, Column 123: reference to external entity in attribute value
    …4&intcidm=HP-OCBox2-Mag-Teaser2&magcid=mag-home-art" target="_parent">60 Jahre…

    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 606, Column 123: reference to entity "magcid" for which no system identifier could be generated
    …4&intcidm=HP-OCBox2-Mag-Teaser2&magcid=mag-home-art" target="_parent">60 Jahre…

    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 597, Column 141: entity was defined here
    …e=335234&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-art" target="_parent"><…
  • Warning Line 607, Column 200: reference not terminated by REFC delimiter
    …nfo/magazine?toparticle=334704&intcidm=HP-OCBox2-Mag-Teaser2&magcid=mag-home-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 607, Column 200: reference to external entity in attribute value
    …nfo/magazine?toparticle=334704&intcidm=HP-OCBox2-Mag-Teaser2&magcid=mag-home-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 607, Column 200: reference to entity "intcidm" for which no system identifier could be generated
    …nfo/magazine?toparticle=334704&intcidm=HP-OCBox2-Mag-Teaser2&magcid=mag-home-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 597, Column 111: entity was defined here
    …t24.at/info/magazine?toparticle=335234&intcidm=HP-OCBox2-Mag-Teaser1&magcid=ma…
  • Warning Line 607, Column 229: reference not terminated by REFC delimiter
    …4&intcidm=HP-OCBox2-Mag-Teaser2&magcid=mag-home-art" target="_parent">Mehr</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 607, Column 229: reference to external entity in attribute value
    …4&intcidm=HP-OCBox2-Mag-Teaser2&magcid=mag-home-art" target="_parent">Mehr</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 607, Column 229: reference to entity "magcid" for which no system identifier could be generated
    …4&intcidm=HP-OCBox2-Mag-Teaser2&magcid=mag-home-art" target="_parent">Mehr</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 597, Column 141: entity was defined here
    …e=335234&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-art" target="_parent"><…
  • Warning Line 693, Column 155: cannot generate system identifier for general entity "language"
    …24.com/adserver/index4.aspx?slot=1471&language=ger&siteid=20&elementid=slot-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 693, Column 155: general entity "language" not defined and no default entity
    …24.com/adserver/index4.aspx?slot=1471&language=ger&siteid=20&elementid=slot-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 693, Column 163: reference not terminated by REFC delimiter
    …dserver/index4.aspx?slot=1471&language=ger&siteid=20&elementid=slot-1"></scrip…

    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 693, Column 163: reference to external entity in attribute value
    …dserver/index4.aspx?slot=1471&language=ger&siteid=20&elementid=slot-1"></scrip…

    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 693, Column 163: reference to entity "language" for which no system identifier could be generated
    …dserver/index4.aspx?slot=1471&language=ger&siteid=20&elementid=slot-1"></scrip…

    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 693, Column 154: entity was defined here
    …t24.com/adserver/index4.aspx?slot=1471&language=ger&siteid=20&elementid=slot-1…
  • Warning Line 693, Column 168: cannot generate system identifier for general entity "siteid"
    …er/index4.aspx?slot=1471&language=ger&siteid=20&elementid=slot-1"></script></d…

    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 693, Column 168: general entity "siteid" not defined and no default entity
    …er/index4.aspx?slot=1471&language=ger&siteid=20&elementid=slot-1"></script></d…

    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 693, Column 174: reference not terminated by REFC delimiter
    …/index4.aspx?slot=1471&language=ger&siteid=20&elementid=slot-1"></script></div>

    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 693, Column 174: reference to external entity in attribute value
    …/index4.aspx?slot=1471&language=ger&siteid=20&elementid=slot-1"></script></div>

    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 693, Column 174: reference to entity "siteid" for which no system identifier could be generated
    …/index4.aspx?slot=1471&language=ger&siteid=20&elementid=slot-1"></script></div>

    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 693, Column 167: entity was defined here
    …ver/index4.aspx?slot=1471&language=ger&siteid=20&elementid=slot-1"></script></…
  • Warning Line 693, Column 178: cannot generate system identifier for general entity "elementid"
    …/index4.aspx?slot=1471&language=ger&siteid=20&elementid=slot-1"></script></div>

    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 693, Column 178: general entity "elementid" not defined and no default entity
    …/index4.aspx?slot=1471&language=ger&siteid=20&elementid=slot-1"></script></div>

    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 693, Column 187: reference not terminated by REFC delimiter
    …/index4.aspx?slot=1471&language=ger&siteid=20&elementid=slot-1"></script></div>

    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 693, Column 187: reference to external entity in attribute value
    …/index4.aspx?slot=1471&language=ger&siteid=20&elementid=slot-1"></script></div>

    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 693, Column 187: reference to entity "elementid" for which no system identifier could be generated
    …/index4.aspx?slot=1471&language=ger&siteid=20&elementid=slot-1"></script></div>

    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 693, Column 177: entity was defined here
    …/index4.aspx?slot=1471&language=ger&siteid=20&elementid=slot-1"></script></div>
  • Warning Line 694, Column 162: reference not terminated by REFC delimiter
    …adserver/index4.aspx?slot=210&language=ger&siteid=20&elementid=slot-2"></scrip…

    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 694, Column 162: reference to external entity in attribute value
    …adserver/index4.aspx?slot=210&language=ger&siteid=20&elementid=slot-2"></scrip…

    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 694, Column 162: reference to entity "language" for which no system identifier could be generated
    …adserver/index4.aspx?slot=210&language=ger&siteid=20&elementid=slot-2"></scrip…

    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 693, Column 154: entity was defined here
    …t24.com/adserver/index4.aspx?slot=1471&language=ger&siteid=20&elementid=slot-1…
  • Warning Line 694, Column 173: reference not terminated by REFC delimiter
    …r/index4.aspx?slot=210&language=ger&siteid=20&elementid=slot-2"></script></div>

    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 694, Column 173: reference to external entity in attribute value
    …r/index4.aspx?slot=210&language=ger&siteid=20&elementid=slot-2"></script></div>

    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 694, Column 173: reference to entity "siteid" for which no system identifier could be generated
    …r/index4.aspx?slot=210&language=ger&siteid=20&elementid=slot-2"></script></div>

    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 693, Column 167: entity was defined here
    …ver/index4.aspx?slot=1471&language=ger&siteid=20&elementid=slot-1"></script></…
  • Warning Line 694, Column 186: reference not terminated by REFC delimiter
    …r/index4.aspx?slot=210&language=ger&siteid=20&elementid=slot-2"></script></div>

    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 694, Column 186: reference to external entity in attribute value
    …r/index4.aspx?slot=210&language=ger&siteid=20&elementid=slot-2"></script></div>

    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 694, Column 186: reference to entity "elementid" for which no system identifier could be generated
    …r/index4.aspx?slot=210&language=ger&siteid=20&elementid=slot-2"></script></div>

    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 693, Column 177: entity was defined here
    …/index4.aspx?slot=1471&language=ger&siteid=20&elementid=slot-1"></script></div>
  • Warning Line 695, Column 162: reference not terminated by REFC delimiter
    …adserver/index4.aspx?slot=211&language=ger&siteid=20&elementid=slot-3"></scrip…

    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 695, Column 162: reference to external entity in attribute value
    …adserver/index4.aspx?slot=211&language=ger&siteid=20&elementid=slot-3"></scrip…

    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 695, Column 162: reference to entity "language" for which no system identifier could be generated
    …adserver/index4.aspx?slot=211&language=ger&siteid=20&elementid=slot-3"></scrip…

    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 693, Column 154: entity was defined here
    …t24.com/adserver/index4.aspx?slot=1471&language=ger&siteid=20&elementid=slot-1…
  • Warning Line 695, Column 173: reference not terminated by REFC delimiter
    …r/index4.aspx?slot=211&language=ger&siteid=20&elementid=slot-3"></script></div>

    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 695, Column 173: reference to external entity in attribute value
    …r/index4.aspx?slot=211&language=ger&siteid=20&elementid=slot-3"></script></div>

    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 695, Column 173: reference to entity "siteid" for which no system identifier could be generated
    …r/index4.aspx?slot=211&language=ger&siteid=20&elementid=slot-3"></script></div>

    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 693, Column 167: entity was defined here
    …ver/index4.aspx?slot=1471&language=ger&siteid=20&elementid=slot-1"></script></…
  • Warning Line 695, Column 186: reference not terminated by REFC delimiter
    …r/index4.aspx?slot=211&language=ger&siteid=20&elementid=slot-3"></script></div>

    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 695, Column 186: reference to external entity in attribute value
    …r/index4.aspx?slot=211&language=ger&siteid=20&elementid=slot-3"></script></div>

    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 695, Column 186: reference to entity "elementid" for which no system identifier could be generated
    …r/index4.aspx?slot=211&language=ger&siteid=20&elementid=slot-3"></script></div>

    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 693, Column 177: entity was defined here
    …/index4.aspx?slot=1471&language=ger&siteid=20&elementid=slot-1"></script></div>
  • Warning Line 696, Column 162: reference not terminated by REFC delimiter
    …adserver/index4.aspx?slot=212&language=ger&siteid=20&elementid=slot-4"></scrip…

    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 696, Column 162: reference to external entity in attribute value
    …adserver/index4.aspx?slot=212&language=ger&siteid=20&elementid=slot-4"></scrip…

    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 696, Column 162: reference to entity "language" for which no system identifier could be generated
    …adserver/index4.aspx?slot=212&language=ger&siteid=20&elementid=slot-4"></scrip…

    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 693, Column 154: entity was defined here
    …t24.com/adserver/index4.aspx?slot=1471&language=ger&siteid=20&elementid=slot-1…
  • Warning Line 696, Column 173: reference not terminated by REFC delimiter
    …r/index4.aspx?slot=212&language=ger&siteid=20&elementid=slot-4"></script></div>

    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 696, Column 173: reference to external entity in attribute value
    …r/index4.aspx?slot=212&language=ger&siteid=20&elementid=slot-4"></script></div>

    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 696, Column 173: reference to entity "siteid" for which no system identifier could be generated
    …r/index4.aspx?slot=212&language=ger&siteid=20&elementid=slot-4"></script></div>

    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 693, Column 167: entity was defined here
    …ver/index4.aspx?slot=1471&language=ger&siteid=20&elementid=slot-1"></script></…
  • Warning Line 696, Column 186: reference not terminated by REFC delimiter
    …r/index4.aspx?slot=212&language=ger&siteid=20&elementid=slot-4"></script></div>

    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 696, Column 186: reference to external entity in attribute value
    …r/index4.aspx?slot=212&language=ger&siteid=20&elementid=slot-4"></script></div>

    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 696, Column 186: reference to entity "elementid" for which no system identifier could be generated
    …r/index4.aspx?slot=212&language=ger&siteid=20&elementid=slot-4"></script></div>

    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 693, Column 177: entity was defined here
    …/index4.aspx?slot=1471&language=ger&siteid=20&elementid=slot-1"></script></div>
  • Error Line 715, Column 76: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.at/regional/steiermark/graz/">Graz</li></a>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 715, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.at/regional/steiermark/graz/">Graz</li></a>
  • Error Line 715, Column 80: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.at/regional/steiermark/graz/">Graz</li></a>

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

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

  • Error Line 716, Column 81: end tag for "a" omitted, but OMITTAG NO was specified
    …a href="http://www.autoscout24.at/regional/tirol/innsbruck/">Innsbruck</li></a>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 716, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.at/regional/tirol/innsbruck/">Innsbruck</l…
  • Error Line 716, Column 85: end tag for element "a" which is not open
    …a href="http://www.autoscout24.at/regional/tirol/innsbruck/">Innsbruck</li></a>

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

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

  • Error Line 717, Column 101: end tag for "a" omitted, but OMITTAG NO was specified
    …utoscout24.at/regional/kaernten/klagenfurt-am-woerthersee/">Klagenfurt</li></a>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 717, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.at/regional/kaernten/klagenfurt-am-woerthe…
  • Error Line 717, Column 105: end tag for element "a" which is not open
    …utoscout24.at/regional/kaernten/klagenfurt-am-woerthersee/">Klagenfurt</li></a>

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

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

  • Error Line 718, Column 98: end tag for "a" omitted, but OMITTAG NO was specified
    …w.autoscout24.at/regional/niederoesterreich/krems-an-der-donau/">Krems</li></a>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 718, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.at/regional/niederoesterreich/krems-an-der…
  • Error Line 718, Column 102: end tag for element "a" which is not open
    …w.autoscout24.at/regional/niederoesterreich/krems-an-der-donau/">Krems</li></a>

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

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

  • Error Line 719, Column 81: end tag for "a" omitted, but OMITTAG NO was specified
    …a href="http://www.autoscout24.at/regional/oberoesterreich/linz/">Linz</li></a>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 719, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.at/regional/oberoesterreich/linz/">Linz</l…
  • Error Line 719, Column 85: end tag for element "a" which is not open
    …a href="http://www.autoscout24.at/regional/oberoesterreich/linz/">Linz</li></a>

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

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

  • Error Line 733, Column 82: end tag for "a" omitted, but OMITTAG NO was specified
    … href="http://www.autoscout24.at/regional/salzburg/salzburg/">Salzburg</li></a>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 733, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.at/regional/salzburg/salzburg/">Salzburg</…
  • Error Line 733, Column 86: end tag for element "a" which is not open
    … href="http://www.autoscout24.at/regional/salzburg/salzburg/">Salzburg</li></a>

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

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

  • Error Line 734, Column 80: end tag for "a" omitted, but OMITTAG NO was specified
    …<a href="http://www.autoscout24.at/regional/kaernten/villach/">Villach</li></a>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 734, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.at/regional/kaernten/villach/">Villach</li…
  • Error Line 734, Column 84: end tag for element "a" which is not open
    …<a href="http://www.autoscout24.at/regional/kaernten/villach/">Villach</li></a>

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

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

  • Error Line 735, Column 81: end tag for "a" omitted, but OMITTAG NO was specified
    …a href="http://www.autoscout24.at/regional/oberoesterreich/wels/">Wels</li></a>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 735, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.at/regional/oberoesterreich/wels/">Wels</l…
  • Error Line 735, Column 85: end tag for element "a" which is not open
    …a href="http://www.autoscout24.at/regional/oberoesterreich/wels/">Wels</li></a>

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

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

  • Error Line 736, Column 70: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.at/regional/wien/wien/">Wien</li></a>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 736, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.at/regional/wien/wien/">Wien</li></a>
  • Error Line 736, Column 74: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.at/regional/wien/wien/">Wien</li></a>

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

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

  • Error Line 737, Column 105: end tag for "a" omitted, but OMITTAG NO was specified
    …cout24.at/regional/niederoesterreich/wiener-neustadt/">Wiener Neustadt</li></a>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 737, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.at/regional/niederoesterreich/wiener-neust…
  • Error Line 737, Column 109: end tag for element "a" which is not open
    …cout24.at/regional/niederoesterreich/wiener-neustadt/">Wiener Neustadt</li></a>

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

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

  • Error Line 751, Column 89: end tag for "a" omitted, but OMITTAG NO was specified
    …http://www.autoscout24.at/regional/steiermark/graz-autohaendler/">Graz</li></a>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 751, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.at/regional/steiermark/graz-autohaendler/"…
  • Error Line 751, Column 93: end tag for element "a" which is not open
    …http://www.autoscout24.at/regional/steiermark/graz-autohaendler/">Graz</li></a>

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

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

  • Error Line 752, Column 94: end tag for "a" omitted, but OMITTAG NO was specified
    …//www.autoscout24.at/regional/tirol/innsbruck-autohaendler/">Innsbruck</li></a>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 752, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.at/regional/tirol/innsbruck-autohaendler/"…
  • Error Line 752, Column 98: end tag for element "a" which is not open
    …//www.autoscout24.at/regional/tirol/innsbruck-autohaendler/">Innsbruck</li></a>

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

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

  • Error Line 753, Column 114: end tag for "a" omitted, but OMITTAG NO was specified
    …/regional/kaernten/klagenfurt-am-woerthersee-autohaendler/">Klagenfurt</li></a>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 753, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.at/regional/kaernten/klagenfurt-am-woerthe…
  • Error Line 753, Column 118: end tag for element "a" which is not open
    …/regional/kaernten/klagenfurt-am-woerthersee-autohaendler/">Klagenfurt</li></a>

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

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

  • Error Line 754, Column 111: end tag for "a" omitted, but OMITTAG NO was specified
    ….at/regional/niederoesterreich/krems-an-der-donau-autohaendler/">Krems</li></a>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 754, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.at/regional/niederoesterreich/krems-an-der…
  • Error Line 754, Column 115: end tag for element "a" which is not open
    ….at/regional/niederoesterreich/krems-an-der-donau-autohaendler/">Krems</li></a>

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

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

  • Error Line 755, Column 94: end tag for "a" omitted, but OMITTAG NO was specified
    …//www.autoscout24.at/regional/oberoesterreich/linz-autohaendler/">Linz</li></a>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 755, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.at/regional/oberoesterreich/linz-autohaend…
  • Error Line 755, Column 98: end tag for element "a" which is not open
    …//www.autoscout24.at/regional/oberoesterreich/linz-autohaendler/">Linz</li></a>

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

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

  • Error Line 769, Column 95: end tag for "a" omitted, but OMITTAG NO was specified
    …/www.autoscout24.at/regional/salzburg/salzburg-autohaendler/">Salzburg</li></a>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 769, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.at/regional/salzburg/salzburg-autohaendler…
  • Error Line 769, Column 99: end tag for element "a" which is not open
    …/www.autoscout24.at/regional/salzburg/salzburg-autohaendler/">Salzburg</li></a>

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

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

  • Error Line 770, Column 95: end tag for "a" omitted, but OMITTAG NO was specified
    …/www.autoscout24.at/regional/oberoesterreich/wels-autohaendler/">Steyr</li></a>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 770, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.at/regional/oberoesterreich/wels-autohaend…
  • Error Line 770, Column 99: end tag for element "a" which is not open
    …/www.autoscout24.at/regional/oberoesterreich/wels-autohaendler/">Steyr</li></a>

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

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

  • Error Line 771, Column 94: end tag for "a" omitted, but OMITTAG NO was specified
    …//www.autoscout24.at/regional/oberoesterreich/wels-autohaendler/">Wels</li></a>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 771, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.at/regional/oberoesterreich/wels-autohaend…
  • Error Line 771, Column 98: end tag for element "a" which is not open
    …//www.autoscout24.at/regional/oberoesterreich/wels-autohaendler/">Wels</li></a>

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

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

  • Error Line 772, Column 83: end tag for "a" omitted, but OMITTAG NO was specified
    …href="http://www.autoscout24.at/regional/wien/wien-autohaendler/">Wien</li></a>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 772, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.at/regional/wien/wien-autohaendler/">Wien<…
  • Error Line 772, Column 87: end tag for element "a" which is not open
    …href="http://www.autoscout24.at/regional/wien/wien-autohaendler/">Wien</li></a>

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

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

  • Error Line 773, Column 118: end tag for "a" omitted, but OMITTAG NO was specified
    …ional/niederoesterreich/wiener-neustadt-autohaendler/">Wiener Neustadt</li></a>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 773, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.at/regional/niederoesterreich/wiener-neust…
  • Error Line 773, Column 122: end tag for element "a" which is not open
    …ional/niederoesterreich/wiener-neustadt-autohaendler/">Wiener Neustadt</li></a>

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

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

  • Error Line 811, Column 23: there is no attribute "name"
                <div name="slot_110149" id="adTagHeader">

    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 855, Column 18: there is no attribute "LANGUAGE"
    <SCRIPT LANGUAGE="JavaScript" type="text/javascript">

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

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

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

  • Error Line 855, Column 36: there is no attribute "type"
    <SCRIPT LANGUAGE="JavaScript" type="text/javascript">

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

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

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

  • Error Line 855, Column 53: element "SCRIPT" undefined
    <SCRIPT LANGUAGE="JavaScript" type="text/javascript">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 986, Column 68: character "&" is the first character of a delimiter but occurred as data
    …gro&#223;e Autob&#246;rse f&#252;r Autokauf & Autoverkauf in 18 L&#228;ndern  	

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 991, Column 141: character "&" is the first character of a delimiter but occurred as data
    …(location.href.search(/\?/) != -1) ? '&' : '?';window.open('http://del.icio.us…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 991, Column 191: cannot generate system identifier for general entity "noui"
    …dow.open('http://del.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponent…

    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 991, Column 191: general entity "noui" not defined and no default entity
    …dow.open('http://del.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponent…

    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 991, Column 195: reference not terminated by REFC delimiter
    …open('http://del.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponent(loc…

    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 991, Column 195: reference to external entity in attribute value
    …open('http://del.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponent(loc…

    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 991, Column 195: reference to entity "noui" for which no system identifier could be generated
    …open('http://del.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponent(loc…

    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 991, Column 190: entity was defined here
    …ndow.open('http://del.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponen…
  • Warning Line 991, Column 196: cannot generate system identifier for general entity "jump"
    …pen('http://del.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponent(loca…

    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 991, Column 196: general entity "jump" not defined and no default entity
    …pen('http://del.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponent(loca…

    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 991, Column 200: reference not terminated by REFC delimiter
    …'http://del.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponent(location…

    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 991, Column 200: reference to external entity in attribute value
    …'http://del.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponent(location…

    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 991, Column 200: reference to entity "jump" for which no system identifier could be generated
    …'http://del.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponent(location…

    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 991, Column 195: entity was defined here
    …open('http://del.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponent(loc…
  • Warning Line 991, Column 207: cannot generate system identifier for general entity "url"
    …/del.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponent(location.href+s…

    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 991, Column 207: general entity "url" not defined and no default entity
    …/del.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponent(location.href+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.

  • Warning Line 991, Column 210: reference not terminated by REFC delimiter
    …l.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponent(location.href+sb_p…

    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 991, Column 210: reference to external entity in attribute value
    …l.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponent(location.href+sb_p…

    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 991, Column 210: reference to entity "url" for which no system identifier could be generated
    …l.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponent(location.href+sb_p…

    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 991, Column 206: entity was defined here
    …//del.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponent(location.href+…
  • Warning Line 991, Column 282: cannot generate system identifier for general entity "title"
    …f+sb_prefix+'extcidm=sb-delicious')+'&title='+encodeURIComponent(document.titl…

    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 991, Column 282: general entity "title" not defined and no default entity
    …f+sb_prefix+'extcidm=sb-delicious')+'&title='+encodeURIComponent(document.titl…

    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 991, Column 287: reference not terminated by REFC delimiter
    …prefix+'extcidm=sb-delicious')+'&title='+encodeURIComponent(document.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 991, Column 287: reference to external entity in attribute value
    …prefix+'extcidm=sb-delicious')+'&title='+encodeURIComponent(document.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 991, Column 287: reference to entity "title" for which no system identifier could be generated
    …prefix+'extcidm=sb-delicious')+'&title='+encodeURIComponent(document.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 991, Column 281: entity was defined here
    …ef+sb_prefix+'extcidm=sb-delicious')+'&title='+encodeURIComponent(document.tit…
  • Warning Line 991, Column 694: character "&" is the first character of a delimiter but occurred as data
    …(location.href.search(/\?/) != -1) ? '&' : '?';window.open('http://myweb2.sear…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 991, Column 848: cannot generate system identifier for general entity "t"
    …refix+'extcidm=sb-bookmarks-yahoo')+'&t='+encodeURIComponent(document.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 991, Column 848: general entity "t" not defined and no default entity
    …refix+'extcidm=sb-bookmarks-yahoo')+'&t='+encodeURIComponent(document.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 991, Column 849: reference not terminated by REFC delimiter
    …efix+'extcidm=sb-bookmarks-yahoo')+'&t='+encodeURIComponent(document.title),'y…

    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 991, Column 849: reference to external entity in attribute value
    …efix+'extcidm=sb-bookmarks-yahoo')+'&t='+encodeURIComponent(document.title),'y…

    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 991, Column 849: reference to entity "t" for which no system identifier could be generated
    …efix+'extcidm=sb-bookmarks-yahoo')+'&t='+encodeURIComponent(document.title),'y…

    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 991, Column 847: entity was defined here
    …prefix+'extcidm=sb-bookmarks-yahoo')+'&t='+encodeURIComponent(document.title),…
  • Warning Line 991, Column 1275: character "&" is the first character of a delimiter but occurred as data
    …(location.href.search(/\?/) != -1) ? '&' : '?';window.open('http://linkarena.c…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 991, Column 1417: reference not terminated by REFC delimiter
    …prefix+'extcidm=sb-linkarena')+'&title='+encodeURIComponent(document.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 991, Column 1417: reference to external entity in attribute value
    …prefix+'extcidm=sb-linkarena')+'&title='+encodeURIComponent(document.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 991, Column 1417: reference to entity "title" for which no system identifier could be generated
    …prefix+'extcidm=sb-linkarena')+'&title='+encodeURIComponent(document.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 991, Column 281: entity was defined here
    …ef+sb_prefix+'extcidm=sb-delicious')+'&title='+encodeURIComponent(document.tit…
  • Warning Line 991, Column 1855: character "&" is the first character of a delimiter but occurred as data
    …(location.href.search(/\?/) != -1) ? '&' : '?';window.open('http://www.mister-…

    This message may appear in several cases:

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

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

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

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

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

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

  • Error Line 1025, Column 150: document type does not allow element "div" here
    …/autoscout24.at'; document.write("<div><img src=\""+OEWA+"?r="+escape(document…

    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 1025, Column 160: an attribute value must be a literal unless it contains only name characters
    …24.at'; document.write("<div><img src=\""+OEWA+"?r="+escape(document.referrer)…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 1025, Column 216: "Date" is not a member of a group specified for any attribute
    …ape(document.referrer)+"&d="+(new Date()).getTime()+"\" width=\"1\" height=\"1…
  • Error Line 1025, Column 240: an attribute value must be a literal unless it contains only name characters
    …&d="+(new Date()).getTime()+"\" width=\"1\" height=\"1\" alt=\"oewapixel\" /><…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 1025, Column 253: an attribute value must be a literal unless it contains only name characters
    …e()).getTime()+"\" width=\"1\" height=\"1\" alt=\"oewapixel\" /></div>");</scr…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 1025, Column 263: an attribute value must be a literal unless it contains only name characters
    …me()+"\" width=\"1\" height=\"1\" alt=\"oewapixel\" /></div>");</script><noscr…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 1025, Column 474: there is no attribute "SRC"
    …pixel' /></div></noscript><SCRIPT SRC="http://ascout24.oewabox.at/survey.js" l…

    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 1025, Column 522: there is no attribute "language"
    …RIPT SRC="http://ascout24.oewabox.at/survey.js" language="Javascript"></SCRIPT>

    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 1025, Column 534: element "SCRIPT" undefined
    …RIPT SRC="http://ascout24.oewabox.at/survey.js" language="Javascript"></SCRIPT>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1062, Column 97: there is no attribute "RenderEvar24"
    …_bottomArea_bottomContentArea_omniturePixel" class="pixel" RenderEvar24="true">

    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 1076, Column 53: element "SCRIPT" undefined
    <SCRIPT LANGUAGE="JavaScript" type="text/javascript">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1087, Column 53: element "SCRIPT" undefined
    <SCRIPT LANGUAGE="JavaScript" type="text/javascript">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).

Visitor Analysis

Daily Visitor
  • 5.017 visits