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.de
  • Domain Name
    autoscout24.de
  • Favicon
  • Google Page Rank
    6
  • Alexa Rank
    #1040
  • Page Size
    72 KB
  • Ip Address
    92.42.227.69
  • Heading
    H1: 1, H2: 2, H3: 5, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
    AutoScout24 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.de.

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: LWEBDEV013
  • x-powered-by: ASP.NET
  • date: Thu, 05 Sep 2013 06:02:36 GMT
  • content-length: 20673
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Domain Name: autoscout24.de
Name Servers: dnslbrz2.autoscout24.com
Name Servers: dnslbrz3.autoscout24.com
Domain Status: connect
Updated: 2011-09-08T17:20:32+02:00
Tech-C
Type: PERSON
Domain Name: DNS Admin
Organisation: AutoScout24 GmbH
Address: Dingolfinger Str. 1-15
PostalCode: 81673
City: Muenchen
CountryCode: DE
Phone: +49-89-444560
Fax: +49-89-444563000
Email: email
Updated: 2011-10-28T19:20:29+02:00
Zone-C
Type: PERSON
Domain Name: DNS Admin
Organisation: AutoScout24 GmbH
Address: Dingolfinger Str. 1-15
PostalCode: 81673
City: Muenchen
CountryCode: DE
Phone: +49-89-444560
Fax: +49-89-444563000
Email: email
Updated: 2011-10-28T19:20:29+02:00

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 45 Errors
  • 20 Warnings
Ratio Text/Html
  • 0.612316874660879
Message Error
  • Warning Line 21, Column 625: cannot generate system identifier for general entity "u"
    …eoptimizer.com/j.php?a='+account_id+'&u='+encodeURIComponent(d.URL)+'&r='+Math…

    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 "&" (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 æ 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 21, Column 625: general entity "u" not defined and no default entity
    …eoptimizer.com/j.php?a='+account_id+'&u='+encodeURIComponent(d.URL)+'&r='+Math…

    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 21, Column 626: reference not terminated by REFC delimiter
    …optimizer.com/j.php?a='+account_id+'&u='+encodeURIComponent(d.URL)+'&r='+Math.…

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

  • Error Line 21, Column 626: reference to entity "u" for which no system identifier could be generated
    …optimizer.com/j.php?a='+account_id+'&u='+encodeURIComponent(d.URL)+'&r='+Math.…

    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 21, Column 624: entity was defined here
    …teoptimizer.com/j.php?a='+account_id+'&u='+encodeURIComponent(d.URL)+'&r='+Mat…
  • Warning Line 21, Column 657: cannot generate system identifier for general entity "r"
    …_id+'&u='+encodeURIComponent(d.URL)+'&r='+Math.random());var a=d.createElement…

    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 "&" (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 æ 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 21, Column 657: general entity "r" not defined and no default entity
    …_id+'&u='+encodeURIComponent(d.URL)+'&r='+Math.random());var a=d.createElement…

    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 21, Column 658: reference not terminated by REFC delimiter
    …id+'&u='+encodeURIComponent(d.URL)+'&r='+Math.random());var a=d.createElement(…

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

  • Error Line 21, Column 658: reference to entity "r" for which no system identifier could be generated
    …id+'&u='+encodeURIComponent(d.URL)+'&r='+Math.random());var a=d.createElement(…

    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 21, Column 656: entity was defined here
    …t_id+'&u='+encodeURIComponent(d.URL)+'&r='+Math.random());var a=d.createElemen…
  • Error Line 134, Column 71: ID "search-customer" already defined
    …www.autoscout24.de/Customersearch.aspx" id="search-customer">Händler suchen</a>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 82, Column 71: ID "search-customer" first defined here
    …www.autoscout24.de/Customersearch.aspx" id="search-customer">Händler suchen</a>
  • Error Line 168, 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 175, 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 163, Column 1: start tag was here
    <div style="display:block" id="inpagemsg" class="msg-error">
  • Error Line 203, Column 8: required attribute "type" not specified
    <script>

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

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

  • Warning Line 204, Column 118: cannot generate system identifier for general entity "GarageTypeFilter"
    …sse?intcidosp=WP-GWP-SearchBox-Button&GarageTypeFilter=All&UseResultSizeRestri…

    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 204, Column 118: general entity "GarageTypeFilter" not defined and no default entity
    …sse?intcidosp=WP-GWP-SearchBox-Button&GarageTypeFilter=All&UseResultSizeRestri…

    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 204, Column 134: reference not terminated by REFC delimiter
    …-GWP-SearchBox-Button&GarageTypeFilter=All&UseResultSizeRestriction=True&IsNot…

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

  • Error Line 204, Column 134: reference to entity "GarageTypeFilter" for which no system identifier could be generated
    …-GWP-SearchBox-Button&GarageTypeFilter=All&UseResultSizeRestriction=True&IsNot…

    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 204, Column 117: entity was defined here
    …isse?intcidosp=WP-GWP-SearchBox-Button&GarageTypeFilter=All&UseResultSizeRestr…
  • Warning Line 204, Column 139: cannot generate system identifier for general entity "UseResultSizeRestriction"
    …SearchBox-Button&GarageTypeFilter=All&UseResultSizeRestriction=True&IsNotCover…

    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 204, Column 139: general entity "UseResultSizeRestriction" not defined and no default entity
    …SearchBox-Button&GarageTypeFilter=All&UseResultSizeRestriction=True&IsNotCover…

    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 204, Column 163: reference not terminated by REFC delimiter
    …ypeFilter=All&UseResultSizeRestriction=True&IsNotCoveredRegion=False&ZipCode="…

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

  • Error Line 204, Column 163: reference to entity "UseResultSizeRestriction" for which no system identifier could be generated
    …ypeFilter=All&UseResultSizeRestriction=True&IsNotCoveredRegion=False&ZipCode="…

    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 204, Column 138: entity was defined here
    …-SearchBox-Button&GarageTypeFilter=All&UseResultSizeRestriction=True&IsNotCove…
  • Warning Line 204, Column 169: cannot generate system identifier for general entity "IsNotCoveredRegion"
    …peFilter=All&UseResultSizeRestriction=True&IsNotCoveredRegion=False&ZipCode="; 

    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 204, Column 169: general entity "IsNotCoveredRegion" not defined and no default entity
    …peFilter=All&UseResultSizeRestriction=True&IsNotCoveredRegion=False&ZipCode="; 

    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 204, Column 187: reference not terminated by REFC delimiter
    …peFilter=All&UseResultSizeRestriction=True&IsNotCoveredRegion=False&ZipCode="; 

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

  • Error Line 204, Column 187: reference to entity "IsNotCoveredRegion" for which no system identifier could be generated
    …peFilter=All&UseResultSizeRestriction=True&IsNotCoveredRegion=False&ZipCode="; 

    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 204, Column 168: entity was defined here
    …peFilter=All&UseResultSizeRestriction=True&IsNotCoveredRegion=False&ZipCode="; 
  • Warning Line 204, Column 194: cannot generate system identifier for general entity "ZipCode"
    …peFilter=All&UseResultSizeRestriction=True&IsNotCoveredRegion=False&ZipCode="; 

    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 204, Column 194: general entity "ZipCode" not defined and no default entity
    …peFilter=All&UseResultSizeRestriction=True&IsNotCoveredRegion=False&ZipCode="; 

    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 204, Column 201: reference not terminated by REFC delimiter
    …peFilter=All&UseResultSizeRestriction=True&IsNotCoveredRegion=False&ZipCode="; 

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

  • Error Line 204, Column 201: reference to entity "ZipCode" for which no system identifier could be generated
    …peFilter=All&UseResultSizeRestriction=True&IsNotCoveredRegion=False&ZipCode="; 

    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 204, Column 193: entity was defined here
    …peFilter=All&UseResultSizeRestriction=True&IsNotCoveredRegion=False&ZipCode="; 
  • Warning Line 280, Column 37: character "&" is the first character of a delimiter but occurred as data
                       (e.keyCode == 65 && e.ctrlKey === true) ||

    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 280, Column 38: character "&" is the first character of a delimiter but occurred as data
                       (e.keyCode == 65 && e.ctrlKey === true) ||

    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 281, Column 37: character "&" is the first character of a delimiter but occurred as data
                       (e.keyCode >= 35 && e.keyCode <= 39)) {

    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 281, Column 38: character "&" is the first character of a delimiter but occurred as data
                       (e.keyCode >= 35 && e.keyCode <= 39)) {

    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 281, Column 50: character "<" is the first character of a delimiter but occurred as data
                       (e.keyCode >= 35 && e.keyCode <= 39)) {

    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 286, Column 50: character "<" is the first character of a delimiter but occurred as data
    …         if (e.shiftKey || (e.keyCode < 48 || e.keyCode > 57) && (e.keyCode < …

    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 286, Column 74: character "&" is the first character of a delimiter but occurred as data
    …|| (e.keyCode < 48 || e.keyCode > 57) && (e.keyCode < 96 || e.keyCode > 105)) …

    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 286, Column 75: character "&" is the first character of a delimiter but occurred as data
    …|| (e.keyCode < 48 || e.keyCode > 57) && (e.keyCode < 96 || e.keyCode > 105)) {

    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 286, Column 88: character "<" is the first character of a delimiter but occurred as data
    …|| (e.keyCode < 48 || e.keyCode > 57) && (e.keyCode < 96 || e.keyCode > 105)) {

    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 306, Column 51: end tag for "input" omitted, but OMITTAG NO was specified
    		<input type="button" value="Werkstätten finden">

    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 306, Column 3: start tag was here
    		<input type="button" value="Werkstätten finden">
  • Error Line 311, Column 80: end tag for "input" omitted, but OMITTAG NO was specified
    			<input maxlength="5" type="text" value="Postleitzahl" id="cms-plz" class="">

    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 311, Column 4: start tag was here
    			<input maxlength="5" type="text" value="Postleitzahl" id="cms-plz" class="">
  • Error Line 325, Column 36: end tag for element "Label" which is not open
                    <label>Marke</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 330, Column 18: 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 325, Column 17: start tag was here
                    <label>Marke</Label>
  • Error Line 332, 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 333, Column 79: duplicate specification of attribute "name"
    …         <select name="model1" id="model1" class="inputFullWidth" name="model">

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

  • Error Line 337, Column 18: 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 332, Column 17: start tag was here
                    <label class="label-disabled model">Modell</Label>
  • Error Line 339, Column 40: end tag for element "Label" which is not open
                    <label>Preis (€)</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 367, Column 18: 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 17: start tag was here
                    <label>Preis (€)</Label>
  • Error Line 369, Column 44: end tag for element "Label" which is not open
                    <label>Erstzulassung</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 414, Column 18: 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 369, Column 17: start tag was here
                    <label>Erstzulassung</Label>
  • Error Line 416, Column 45: end tag for element "Label" which is not open
                    <label>Kilometerstand</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 437, Column 18: 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 416, Column 17: start tag was here
                    <label>Kilometerstand</Label>
  • Error Line 439, Column 42: end tag for element "Label" which is not open
                    <label>Kraftstoff </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 445, Column 18: 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 439, Column 17: start tag was here
                    <label>Kraftstoff </Label>
  • Error Line 446, Column 86: duplicate specification of attribute "id"
    … id="blockZip" class="marginTopFontM quickSearchInputS floatLeft" id="zip-lbl">

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

  • Error Line 447, Column 43: end tag for element "Label" which is not open
                    <label>Ort oder PLZ</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 449, Column 96: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …div id="mapSuggestionBox" class="mapSuggestionBox" style="position: absolute;">

    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 451, Column 18: 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 447, Column 17: start tag was here
                    <label>Ort oder PLZ</Label>
  • Error Line 453, Column 38: end tag for element "Label" which is not open
                    <label>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 463, Column 18: 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 453, Column 17: start tag was here
                    <label>Umkreis</Label>
  • Error Line 476, Column 108: end tag for element "Span" which is not open
    …="equip_37" type="checkbox" name="equip" value="37" /><span>Mit Garantie</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 477, Column 24: end tag for "span" omitted, but OMITTAG NO was specified
                    </label>

    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 476, Column 84: start tag was here
    …="equip_37" type="checkbox" name="equip" value="37" /><span>Mit Garantie</Span>
  • Error Line 499, Column 131: there is no attribute "border"
    …;" width="990" height="317" scrolling="no" frameborder='0' border='0'></iframe>

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

  • Error Line 652, Column 203: document type does not allow element "script" here
    …tString + 'tile=5;sz=1x1;ord=' + ord + '?" type="text/javascript"><\/script>');

    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 652, Column 204: character "<" is the first character of a delimiter but occurred as data
    …tString + 'tile=5;sz=1x1;ord=' + ord + '?" type="text/javascript"><\/script>');

    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 656, Column 6: end tag for "script" 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 636, Column 1: start tag was here
    <script language="JavaScript" type="text/javascript">
  • Error Line 749, Column 64: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.de/modelle/audi/">Audi</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 749, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.de/modelle/audi/">Audi</li></a>
  • Error Line 749, Column 68: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.de/modelle/audi/">Audi</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 750, Column 62: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.de/modelle/bmw/">BMW</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 750, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.de/modelle/bmw/">BMW</li></a>
  • Error Line 750, Column 66: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.de/modelle/bmw/">BMW</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 64: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.de/modelle/ford/">Ford</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.de/modelle/ford/">Ford</li></a>
  • Error Line 751, Column 68: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.de/modelle/ford/">Ford</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 86: end tag for "a" omitted, but OMITTAG NO was specified
    …f="http://www.autoscout24.de/modelle/hyundai/" title="Hyundai">Hyundai</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.de/modelle/hyundai/" title="Hyundai">Hyund…
  • Error Line 752, Column 90: end tag for element "a" which is not open
    …f="http://www.autoscout24.de/modelle/hyundai/" title="Hyundai">Hyundai</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 77: end tag for "a" omitted, but OMITTAG NO was specified
    …li><a href="http://www.autoscout24.de/modelle/mercedes-benz/">Mercedes</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.de/modelle/mercedes-benz/">Mercedes</li></…
  • Error Line 753, Column 81: end tag for element "a" which is not open
    …li><a href="http://www.autoscout24.de/modelle/mercedes-benz/">Mercedes</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 68: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.de/modelle/nissan/">Nissan</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.de/modelle/nissan/">Nissan</li></a>
  • Error Line 754, Column 72: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.de/modelle/nissan/">Nissan</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 64: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.de/modelle/opel/">Opel</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.de/modelle/opel/">Opel</li></a>
  • Error Line 755, Column 68: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.de/modelle/opel/">Opel</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 756, Column 70: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.de/modelle/peugeot/">Peugeot</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 756, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.de/modelle/peugeot/">Peugeot</li></a>
  • Error Line 756, Column 74: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.de/modelle/peugeot/">Peugeot</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 757, Column 80: end tag for "a" omitted, but OMITTAG NO was specified
    …<a href="http://www.autoscout24.de/modelle/skoda/" title="Skoda">Skoda</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 757, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.de/modelle/skoda/" title="Skoda">Skoda</li…
  • Error Line 757, Column 84: end tag for element "a" which is not open
    …<a href="http://www.autoscout24.de/modelle/skoda/" title="Skoda">Skoda</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 758, Column 68: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.de/modelle/toyota/">Toyota</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 758, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.de/modelle/toyota/">Toyota</li></a>
  • Error Line 758, Column 72: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.de/modelle/toyota/">Toyota</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 759, Column 68: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.de/modelle/vw/">Volkswagen</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 759, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.de/modelle/vw/">Volkswagen</li></a>
  • Error Line 759, Column 72: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.de/modelle/vw/">Volkswagen</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 760, Column 65: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://katalog.motoscout24.de/">Motorradmarken</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 760, Column 6: start tag was here
    	<li><a href="http://katalog.motoscout24.de/">Motorradmarken</li></a>
  • Error Line 760, Column 69: end tag for element "a" which is not open
    	<li><a href="http://katalog.motoscout24.de/">Motorradmarken</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 767, Column 75: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.de/modelle/audi/audi-a3/">Audi A3</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 767, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.de/modelle/audi/audi-a3/">Audi A3</li></a>
  • Error Line 767, Column 79: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.de/modelle/audi/audi-a3/">Audi A3</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 768, Column 75: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.de/modelle/audi/audi-a4/">Audi A4</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 768, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.de/modelle/audi/audi-a4/">Audi A4</li></a>
  • Error Line 768, Column 79: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.de/modelle/audi/audi-a4/">Audi A4</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 75: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.de/modelle/audi/audi-a6/">Audi A6</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.de/modelle/audi/audi-a6/">Audi A6</li></a>
  • Error Line 769, Column 79: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.de/modelle/audi/audi-a6/">Audi A6</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 74: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.de/modelle/bmw/bmw-3er/">BMW 3er</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.de/modelle/bmw/bmw-3er/">BMW 3er</li></a>
  • Error Line 770, Column 78: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.de/modelle/bmw/bmw-3er/">BMW 3er</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 74: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.de/modelle/bmw/bmw-5er/">BMW 5er</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.de/modelle/bmw/bmw-5er/">BMW 5er</li></a>
  • Error Line 771, Column 78: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.de/modelle/bmw/bmw-5er/">BMW 5er</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 109: end tag for "a" omitted, but OMITTAG NO was specified
    …24.de/modelle/mercedes-benz/mercedes-benz-c-klasse/">Mercedes C-Klasse</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.de/modelle/mercedes-benz/mercedes-benz-c-k…
  • Error Line 772, Column 113: end tag for element "a" which is not open
    …24.de/modelle/mercedes-benz/mercedes-benz-c-klasse/">Mercedes C-Klasse</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 109: end tag for "a" omitted, but OMITTAG NO was specified
    …24.de/modelle/mercedes-benz/mercedes-benz-e-klasse/">Mercedes E-Klasse</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.de/modelle/mercedes-benz/mercedes-benz-e-k…
  • Error Line 773, Column 113: end tag for element "a" which is not open
    …24.de/modelle/mercedes-benz/mercedes-benz-e-klasse/">Mercedes E-Klasse</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 774, Column 81: end tag for "a" omitted, but OMITTAG NO was specified
    …a href="http://www.autoscout24.de/modelle/opel/opel-astra/">Opel Astra</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 774, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.de/modelle/opel/opel-astra/">Opel Astra</l…
  • Error Line 774, Column 85: end tag for element "a" which is not open
    …a href="http://www.autoscout24.de/modelle/opel/opel-astra/">Opel Astra</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 775, Column 73: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.de/modelle/vw/vw-golf/">VW Golf</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 775, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.de/modelle/vw/vw-golf/">VW Golf</li></a>
  • Error Line 775, Column 77: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.de/modelle/vw/vw-golf/">VW Golf</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 776, Column 77: end tag for "a" omitted, but OMITTAG NO was specified
    …li><a href="http://www.autoscout24.de/modelle/vw/vw-passat/">VW Passat</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 776, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.de/modelle/vw/vw-passat/">VW Passat</li></…
  • Error Line 776, Column 81: end tag for element "a" which is not open
    …li><a href="http://www.autoscout24.de/modelle/vw/vw-passat/">VW Passat</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 777, Column 73: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.de/modelle/vw/vw-polo/">VW Polo</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 777, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.de/modelle/vw/vw-polo/">VW Polo</li></a>
  • Error Line 777, Column 77: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.de/modelle/vw/vw-polo/">VW Polo</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 778, Column 70: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.de/modelle/">Weitere Modelle</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 778, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.de/modelle/">Weitere Modelle</li></a>
  • Error Line 778, Column 74: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.de/modelle/">Weitere Modelle</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 785, Column 82: end tag for "a" omitted, but OMITTAG NO was specified
    … href="http://ww2.autoscout24.de/mz_makes_audi.aspx">Audi Testberichte</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 785, Column 6: start tag was here
    	<li><a href="http://ww2.autoscout24.de/mz_makes_audi.aspx">Audi Testberichte</…
  • Error Line 785, Column 86: end tag for element "a" which is not open
    … href="http://ww2.autoscout24.de/mz_makes_audi.aspx">Audi Testberichte</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 786, Column 80: end tag for "a" omitted, but OMITTAG NO was specified
    …<a href="http://ww2.autoscout24.de/mz_makes_bmw.aspx">BMW Testberichte</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 786, Column 6: start tag was here
    	<li><a href="http://ww2.autoscout24.de/mz_makes_bmw.aspx">BMW Testberichte</li…
  • Error Line 786, Column 84: end tag for element "a" which is not open
    …<a href="http://ww2.autoscout24.de/mz_makes_bmw.aspx">BMW Testberichte</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 787, Column 90: end tag for "a" omitted, but OMITTAG NO was specified
    …ttp://ww2.autoscout24.de/mz_makes_mercedes.aspx">Mercedes Testberichte</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 787, Column 6: start tag was here
    	<li><a href="http://ww2.autoscout24.de/mz_makes_mercedes.aspx">Mercedes Testbe…
  • Error Line 787, Column 94: end tag for element "a" which is not open
    …ttp://ww2.autoscout24.de/mz_makes_mercedes.aspx">Mercedes Testberichte</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 788, Column 82: end tag for "a" omitted, but OMITTAG NO was specified
    … href="http://ww2.autoscout24.de/mz_makes_opel.aspx">Opel Testberichte</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 788, Column 6: start tag was here
    	<li><a href="http://ww2.autoscout24.de/mz_makes_opel.aspx">Opel Testberichte</…
  • Error Line 788, Column 86: end tag for element "a" which is not open
    … href="http://ww2.autoscout24.de/mz_makes_opel.aspx">Opel Testberichte</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 789, Column 78: end tag for "a" omitted, but OMITTAG NO was specified
    …i><a href="http://ww2.autoscout24.de/mz_makes_vw.aspx">VW Testberichte</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 789, Column 6: start tag was here
    	<li><a href="http://ww2.autoscout24.de/mz_makes_vw.aspx">VW Testberichte</li><…
  • Error Line 789, Column 82: end tag for element "a" which is not open
    …i><a href="http://ww2.autoscout24.de/mz_makes_vw.aspx">VW Testberichte</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 790, Column 108: end tag for "a" omitted, but OMITTAG NO was specified
    …t24.de/studie/bmw-4er-concept-coupe/aus-3-mach-4/7016/325636/">BMW 4er</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 790, Column 6: start tag was here
    	<li><a href="http://ww2.autoscout24.de/studie/bmw-4er-concept-coupe/aus-3-mach…
  • Error Line 790, Column 112: end tag for element "a" which is not open
    …t24.de/studie/bmw-4er-concept-coupe/aus-3-mach-4/7016/325636/">BMW 4er</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 791, Column 100: end tag for "a" omitted, but OMITTAG NO was specified
    …autoscout24.de/erstkontakt/vw-golf-7/das-auto/44275/315006/">VW Golf 7</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 791, Column 6: start tag was here
    	<li><a href="http://ww2.autoscout24.de/erstkontakt/vw-golf-7/das-auto/44275/31…
  • Error Line 791, Column 104: end tag for element "a" which is not open
    …autoscout24.de/erstkontakt/vw-golf-7/das-auto/44275/315006/">VW Golf 7</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 792, Column 115: end tag for "a" omitted, but OMITTAG NO was specified
    …erstkontakt/opel-adam/kunterbunte-kampfansage/44331/320933/">Opel Adam</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 792, Column 6: start tag was here
    	<li><a href="http://ww2.autoscout24.de/erstkontakt/opel-adam/kunterbunte-kampf…
  • Error Line 792, Column 119: end tag for element "a" which is not open
    …erstkontakt/opel-adam/kunterbunte-kampfansage/44331/320933/">Opel Adam</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 793, Column 115: end tag for "a" omitted, but OMITTAG NO was specified
    …test/mercedes-benz-a-klasse/geht-doch/44276/323436/">Mercedes A-Klasse</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 793, Column 6: start tag was here
    	<li><a href="http://ww2.autoscout24.de/test/mercedes-benz-a-klasse/geht-doch/4…
  • Error Line 793, Column 119: end tag for element "a" which is not open
    …test/mercedes-benz-a-klasse/geht-doch/44276/323436/">Mercedes A-Klasse</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 794, Column 116: end tag for "a" omitted, but OMITTAG NO was specified
    …rstkontakt/skoda-octavia-iii/cleverle/44439/331850/">Skoda Octavia III</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 794, Column 6: start tag was here
    	<li><a href="http://ww2.autoscout24.de/erstkontakt/skoda-octavia-iii/cleverle/…
  • Error Line 794, Column 120: end tag for element "a" which is not open
    …rstkontakt/skoda-octavia-iii/cleverle/44439/331850/">Skoda Octavia III</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 795, Column 124: end tag for "a" omitted, but OMITTAG NO was specified
    …etroit-2013/mit-pauken-und-trompeten/329041/330923/">Detroit Auto Show</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 795, Column 6: start tag was here
    	<li><a href="http://ww2.autoscout24.de/bericht/detroit-2013/mit-pauken-und-tro…
  • Error Line 795, Column 128: end tag for element "a" which is not open
    …etroit-2013/mit-pauken-und-trompeten/329041/330923/">Detroit Auto Show</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 796, Column 101: end tag for "a" omitted, but OMITTAG NO was specified
    …utoscout24.de/magazine/mz_newcars/mz_makes.aspx/">Weitere Testberichte</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 796, Column 6: start tag was here
    	<li><a href="http://ww2.autoscout24.de/magazine/mz_newcars/mz_makes.aspx/">Wei…
  • Error Line 796, Column 105: end tag for element "a" which is not open
    …utoscout24.de/magazine/mz_newcars/mz_makes.aspx/">Weitere Testberichte</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 803, Column 70: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://ww2.autoscout24.de/fraud">Sicherheitshinweis</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 803, Column 6: start tag was here
    	<li><a href="http://ww2.autoscout24.de/fraud">Sicherheitshinweis</li></a>
  • Error Line 803, Column 74: end tag for element "a" which is not open
    	<li><a href="http://ww2.autoscout24.de/fraud">Sicherheitshinweis</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 804, Column 74: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://werkstatt.autoscout24.de/inspektion/">Inspektion</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 804, Column 6: start tag was here
    	<li><a href="http://werkstatt.autoscout24.de/inspektion/">Inspektion</li></a>
  • Error Line 804, Column 78: end tag for element "a" which is not open
    	<li><a href="http://werkstatt.autoscout24.de/inspektion/">Inspektion</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 805, Column 78: end tag for "a" omitted, but OMITTAG NO was specified
    …i><a href="http://werkstatt.autoscout24.de/oelwechsel/">&Ouml;lwechsel</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 805, Column 6: start tag was here
    	<li><a href="http://werkstatt.autoscout24.de/oelwechsel/">&Ouml;lwechsel</li><…
  • Error Line 805, Column 82: end tag for element "a" which is not open
    …i><a href="http://werkstatt.autoscout24.de/oelwechsel/">&Ouml;lwechsel</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 806, Column 88: end tag for "a" omitted, but OMITTAG NO was specified
    …"http://werkstatt.autoscout24.de/zahnriemenwechsel/">Zahnriemenwechsel</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 806, Column 6: start tag was here
    	<li><a href="http://werkstatt.autoscout24.de/zahnriemenwechsel/">Zahnriemenwec…
  • Error Line 806, Column 92: end tag for element "a" which is not open
    …"http://werkstatt.autoscout24.de/zahnriemenwechsel/">Zahnriemenwechsel</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 807, Column 78: end tag for "a" omitted, but OMITTAG NO was specified
    …i><a href="http://www.autoscout24.de/nutzfahrzeuge/">Nutzfahrzeugtypen</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 807, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.de/nutzfahrzeuge/">Nutzfahrzeugtypen</li><…
  • Error Line 807, Column 82: end tag for element "a" which is not open
    …i><a href="http://www.autoscout24.de/nutzfahrzeuge/">Nutzfahrzeugtypen</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 808, Column 77: end tag for "a" omitted, but OMITTAG NO was specified
    …li><a href="http://www.autoscout24.de/modelle/motorrad/">Motorradtypen</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 808, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.de/modelle/motorrad/">Motorradtypen</li></…
  • Error Line 808, Column 81: end tag for element "a" which is not open
    …li><a href="http://www.autoscout24.de/modelle/motorrad/">Motorradtypen</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 809, Column 80: end tag for "a" omitted, but OMITTAG NO was specified
    …<a href="http://suche.truckscout24.de/anhaenger.php">PKW Anh&auml;nger</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 809, Column 6: start tag was here
    	<li><a href="http://suche.truckscout24.de/anhaenger.php">PKW Anh&auml;nger</li…
  • Error Line 809, Column 84: end tag for element "a" which is not open
    …<a href="http://suche.truckscout24.de/anhaenger.php">PKW Anh&auml;nger</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 810, Column 70: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://ww2.autoscout24.de/teilkasko.aspx">Teilkasko</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 810, Column 6: start tag was here
    	<li><a href="http://ww2.autoscout24.de/teilkasko.aspx">Teilkasko</li></a>
  • Error Line 810, Column 74: end tag for element "a" which is not open
    	<li><a href="http://ww2.autoscout24.de/teilkasko.aspx">Teilkasko</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 70: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://ww2.autoscout24.de/vollkasko.aspx">Vollkasko</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 811, Column 6: start tag was here
    	<li><a href="http://ww2.autoscout24.de/vollkasko.aspx">Vollkasko</li></a>
  • Error Line 811, Column 74: end tag for element "a" which is not open
    	<li><a href="http://ww2.autoscout24.de/vollkasko.aspx">Vollkasko</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 812, Column 68: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.de/caravaning/">Caravaning</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 812, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.de/caravaning/">Caravaning</li></a>
  • Error Line 812, Column 72: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.de/caravaning/">Caravaning</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 813, Column 74: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://suche.truckscout24.de/wohnmobile.php">Wohnmobile</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 813, Column 6: start tag was here
    	<li><a href="http://suche.truckscout24.de/wohnmobile.php">Wohnmobile</li></a>
  • Error Line 813, Column 78: end tag for element "a" which is not open
    	<li><a href="http://suche.truckscout24.de/wohnmobile.php">Wohnmobile</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 814, Column 68: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://themen.autoscout24.de/">Weitere Autothemen</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 814, Column 6: start tag was here
    	<li><a href="http://themen.autoscout24.de/">Weitere Autothemen</li></a>
  • Error Line 814, Column 72: end tag for element "a" which is not open
    	<li><a href="http://themen.autoscout24.de/">Weitere Autothemen</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 843, Column 59: there is no attribute "name"
    …lass="mediumRectangle marginTopBlockM" name="slot_110152" id="mediumRectangle">

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

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

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

  • Warning Line 884, Column 62: cannot generate system identifier for general entity "link"
    …autoscout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Ede…

    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 884, Column 62: general entity "link" not defined and no default entity
    …autoscout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Ede…

    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 884, Column 66: reference not terminated by REFC delimiter
    …scout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Ede%2Fm…

    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 884, Column 66: reference to external entity in attribute value
    …scout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Ede%2Fm…

    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 884, Column 66: reference to entity "link" for which no system identifier could be generated
    …scout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Ede%2Fm…

    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 884, Column 61: entity was defined here
    ….autoscout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Ed…
  • Warning Line 884, Column 142: cannot generate system identifier for general entity "name"
    …Fmagazine%2Fmz%5Fothers%2Fsw%5Fcardif&name=hp_tb_sw-repair-protect&site=1"  on…

    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 884, Column 142: general entity "name" not defined and no default entity
    …Fmagazine%2Fmz%5Fothers%2Fsw%5Fcardif&name=hp_tb_sw-repair-protect&site=1"  on…

    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 884, Column 146: reference not terminated by REFC delimiter
    …azine%2Fmz%5Fothers%2Fsw%5Fcardif&name=hp_tb_sw-repair-protect&site=1"  onclic…

    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 884, Column 146: reference to external entity in attribute value
    …azine%2Fmz%5Fothers%2Fsw%5Fcardif&name=hp_tb_sw-repair-protect&site=1"  onclic…

    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 884, Column 146: reference to entity "name" for which no system identifier could be generated
    …azine%2Fmz%5Fothers%2Fsw%5Fcardif&name=hp_tb_sw-repair-protect&site=1"  onclic…

    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 884, Column 141: entity was defined here
    …2Fmagazine%2Fmz%5Fothers%2Fsw%5Fcardif&name=hp_tb_sw-repair-protect&site=1"  o…
  • Warning Line 884, Column 171: cannot generate system identifier for general entity "site"
    …5Fcardif&name=hp_tb_sw-repair-protect&site=1"  onclick="var s=s_gi('autoscout2…

    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 884, Column 171: general entity "site" not defined and no default entity
    …5Fcardif&name=hp_tb_sw-repair-protect&site=1"  onclick="var s=s_gi('autoscout2…

    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 884, Column 175: reference not terminated by REFC delimiter
    …rdif&name=hp_tb_sw-repair-protect&site=1"  onclick="var s=s_gi('autoscout24de'…

    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 884, Column 175: reference to external entity in attribute value
    …rdif&name=hp_tb_sw-repair-protect&site=1"  onclick="var s=s_gi('autoscout24de'…

    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 884, Column 175: reference to entity "site" for which no system identifier could be generated
    …rdif&name=hp_tb_sw-repair-protect&site=1"  onclick="var s=s_gi('autoscout24de'…

    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 884, Column 170: entity was defined here
    …%5Fcardif&name=hp_tb_sw-repair-protect&site=1"  onclick="var s=s_gi('autoscout…
  • Error Line 884, Column 454: required attribute "alt" not specified
    …tp://cmspic.autoscout24.com/de-DE/110114/0/0.jpg?timestamp=20130219092851"></a>

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

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

  • Error Line 884, Column 458: end tag for "img" omitted, but OMITTAG NO was specified
    …tp://cmspic.autoscout24.com/de-DE/110114/0/0.jpg?timestamp=20130219092851"></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 884, Column 368: start tag was here
    …is,'o', 'Mag-HP-sw-repair-protect');"><img src="http://cmspic.autoscout24.com/…
  • Warning Line 891, Column 69: reference not terminated by REFC delimiter
    …scout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Ede%2Fm…

    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 891, Column 69: reference to external entity in attribute value
    …scout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Ede%2Fm…

    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 891, Column 69: reference to entity "link" for which no system identifier could be generated
    …scout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Ede%2Fm…

    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 884, Column 61: entity was defined here
    ….autoscout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Ed…
  • Warning Line 891, Column 149: reference not terminated by REFC delimiter
    …azine%2Fmz%5Fothers%2Fsw%5Fcardif&name=hp_tb_sw-repair-protect&site=1"  onclic…

    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 891, Column 149: reference to external entity in attribute value
    …azine%2Fmz%5Fothers%2Fsw%5Fcardif&name=hp_tb_sw-repair-protect&site=1"  onclic…

    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 891, Column 149: reference to entity "name" for which no system identifier could be generated
    …azine%2Fmz%5Fothers%2Fsw%5Fcardif&name=hp_tb_sw-repair-protect&site=1"  onclic…

    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 884, Column 141: entity was defined here
    …2Fmagazine%2Fmz%5Fothers%2Fsw%5Fcardif&name=hp_tb_sw-repair-protect&site=1"  o…
  • Warning Line 891, Column 178: reference not terminated by REFC delimiter
    …rdif&name=hp_tb_sw-repair-protect&site=1"  onclick="var s=s_gi('autoscout24de'…

    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 891, Column 178: reference to external entity in attribute value
    …rdif&name=hp_tb_sw-repair-protect&site=1"  onclick="var s=s_gi('autoscout24de'…

    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 891, Column 178: reference to entity "site" for which no system identifier could be generated
    …rdif&name=hp_tb_sw-repair-protect&site=1"  onclick="var s=s_gi('autoscout24de'…

    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 884, Column 170: entity was defined here
    …%5Fcardif&name=hp_tb_sw-repair-protect&site=1"  onclick="var s=s_gi('autoscout…
  • Error Line 891, Column 394: end tag for element "nobr" which is not open
    …-protect';s.tl(this,'o', 'Mag-HP-sw-repair-protect');">Weitere Infos</a></nobr>

    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.

  • Warning Line 898, Column 73: reference not terminated by REFC delimiter
    …scout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Ede%2Fm…

    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 898, Column 73: reference to external entity in attribute value
    …scout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Ede%2Fm…

    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 898, Column 73: reference to entity "link" for which no system identifier could be generated
    …scout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Ede%2Fm…

    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 884, Column 61: entity was defined here
    ….autoscout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Ed…
  • Warning Line 898, Column 150: reference not terminated by REFC delimiter
    …magazine%2Fmz%5Fothers%2Fsw%5Fdas&name=hp_tb_sw-das-rechtsberatung&site=1" id=…

    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 898, Column 150: reference to external entity in attribute value
    …magazine%2Fmz%5Fothers%2Fsw%5Fdas&name=hp_tb_sw-das-rechtsberatung&site=1" id=…

    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 898, Column 150: reference to entity "name" for which no system identifier could be generated
    …magazine%2Fmz%5Fothers%2Fsw%5Fdas&name=hp_tb_sw-das-rechtsberatung&site=1" id=…

    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 884, Column 141: entity was defined here
    …2Fmagazine%2Fmz%5Fothers%2Fsw%5Fcardif&name=hp_tb_sw-repair-protect&site=1"  o…
  • Warning Line 898, Column 183: reference not terminated by REFC delimiter
    …&name=hp_tb_sw-das-rechtsberatung&site=1" id="sw-das-rechtsberatung">D.A.S. Re…

    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 898, Column 183: reference to external entity in attribute value
    …&name=hp_tb_sw-das-rechtsberatung&site=1" id="sw-das-rechtsberatung">D.A.S. Re…

    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 898, Column 183: reference to entity "site" for which no system identifier could be generated
    …&name=hp_tb_sw-das-rechtsberatung&site=1" id="sw-das-rechtsberatung">D.A.S. Re…

    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 884, Column 170: entity was defined here
    …%5Fcardif&name=hp_tb_sw-repair-protect&site=1"  onclick="var s=s_gi('autoscout…
  • Warning Line 898, Column 313: reference not terminated by REFC delimiter
    …scout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Ede%2Fm…

    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 898, Column 313: reference to external entity in attribute value
    …scout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Ede%2Fm…

    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 898, Column 313: reference to entity "link" for which no system identifier could be generated
    …scout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Ede%2Fm…

    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 884, Column 61: entity was defined here
    ….autoscout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Ed…
  • Warning Line 898, Column 397: reference not terminated by REFC delimiter
    …e%2Fmz%5Fothers%2Fsw%5Fdirectline&name=hp_tb_sw-direct-line&site=1" id="sw-dir…

    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 898, Column 397: reference to external entity in attribute value
    …e%2Fmz%5Fothers%2Fsw%5Fdirectline&name=hp_tb_sw-direct-line&site=1" id="sw-dir…

    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 898, Column 397: reference to entity "name" for which no system identifier could be generated
    …e%2Fmz%5Fothers%2Fsw%5Fdirectline&name=hp_tb_sw-direct-line&site=1" id="sw-dir…

    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 884, Column 141: entity was defined here
    …2Fmagazine%2Fmz%5Fothers%2Fsw%5Fcardif&name=hp_tb_sw-repair-protect&site=1"  o…
  • Warning Line 898, Column 423: reference not terminated by REFC delimiter
    …ectline&name=hp_tb_sw-direct-line&site=1" id="sw-direct-line">Direct Line</opt…

    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 898, Column 423: reference to external entity in attribute value
    …ectline&name=hp_tb_sw-direct-line&site=1" id="sw-direct-line">Direct Line</opt…

    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 898, Column 423: reference to entity "site" for which no system identifier could be generated
    …ectline&name=hp_tb_sw-direct-line&site=1" id="sw-direct-line">Direct Line</opt…

    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 884, Column 170: entity was defined here
    …%5Fcardif&name=hp_tb_sw-repair-protect&site=1"  onclick="var s=s_gi('autoscout…
  • Warning Line 919, Column 66: reference not terminated by REFC delimiter
    …scout24.de/redir.asp?language=ger&link=http:%2F%2Fad%2Demea%2Edoubleclick%2Ene…

    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 919, Column 66: reference to external entity in attribute value
    …scout24.de/redir.asp?language=ger&link=http:%2F%2Fad%2Demea%2Edoubleclick%2Ene…

    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 919, Column 66: reference to entity "link" for which no system identifier could be generated
    …scout24.de/redir.asp?language=ger&link=http:%2F%2Fad%2Demea%2Edoubleclick%2Ene…

    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 884, Column 61: entity was defined here
    ….autoscout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Ed…
  • Warning Line 919, Column 139: reference not terminated by REFC delimiter
    …%2Enet%2Fclk;267285644;93116425;o&name=hp_tb_aw-dacia-service&site=1"  onclick…

    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 919, Column 139: reference to external entity in attribute value
    …%2Enet%2Fclk;267285644;93116425;o&name=hp_tb_aw-dacia-service&site=1"  onclick…

    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 919, Column 139: reference to entity "name" for which no system identifier could be generated
    …%2Enet%2Fclk;267285644;93116425;o&name=hp_tb_aw-dacia-service&site=1"  onclick…

    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 884, Column 141: entity was defined here
    …2Fmagazine%2Fmz%5Fothers%2Fsw%5Fcardif&name=hp_tb_sw-repair-protect&site=1"  o…
  • Warning Line 919, Column 167: reference not terminated by REFC delimiter
    …425;o&name=hp_tb_aw-dacia-service&site=1"  onclick="var s=s_gi('autoscout24de'…

    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 919, Column 167: reference to external entity in attribute value
    …425;o&name=hp_tb_aw-dacia-service&site=1"  onclick="var s=s_gi('autoscout24de'…

    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 919, Column 167: reference to entity "site" for which no system identifier could be generated
    …425;o&name=hp_tb_aw-dacia-service&site=1"  onclick="var s=s_gi('autoscout24de'…

    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 884, Column 170: entity was defined here
    …%5Fcardif&name=hp_tb_sw-repair-protect&site=1"  onclick="var s=s_gi('autoscout…
  • Error Line 919, Column 443: required attribute "alt" not specified
    …tp://cmspic.autoscout24.com/de-DE/110115/1/0.jpg?timestamp=20130212111601"></a>

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

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

  • Error Line 919, Column 447: end tag for "img" omitted, but OMITTAG NO was specified
    …tp://cmspic.autoscout24.com/de-DE/110115/1/0.jpg?timestamp=20130212111601"></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 919, Column 357: start tag was here
    …his,'o', 'Mag-HP-aw-dacia-service');"><img src="http://cmspic.autoscout24.com/…
  • Warning Line 926, Column 69: reference not terminated by REFC delimiter
    …scout24.de/redir.asp?language=ger&link=http:%2F%2Fad%2Demea%2Edoubleclick%2Ene…

    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 926, Column 69: reference to external entity in attribute value
    …scout24.de/redir.asp?language=ger&link=http:%2F%2Fad%2Demea%2Edoubleclick%2Ene…

    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 926, Column 69: reference to entity "link" for which no system identifier could be generated
    …scout24.de/redir.asp?language=ger&link=http:%2F%2Fad%2Demea%2Edoubleclick%2Ene…

    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 884, Column 61: entity was defined here
    ….autoscout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Ed…
  • Warning Line 926, Column 142: reference not terminated by REFC delimiter
    …%2Enet%2Fclk;267285644;93116425;o&name=hp_tb_aw-dacia-service&site=1"  onclick…

    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 926, Column 142: reference to external entity in attribute value
    …%2Enet%2Fclk;267285644;93116425;o&name=hp_tb_aw-dacia-service&site=1"  onclick…

    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 926, Column 142: reference to entity "name" for which no system identifier could be generated
    …%2Enet%2Fclk;267285644;93116425;o&name=hp_tb_aw-dacia-service&site=1"  onclick…

    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 884, Column 141: entity was defined here
    …2Fmagazine%2Fmz%5Fothers%2Fsw%5Fcardif&name=hp_tb_sw-repair-protect&site=1"  o…
  • Warning Line 926, Column 170: reference not terminated by REFC delimiter
    …425;o&name=hp_tb_aw-dacia-service&site=1"  onclick="var s=s_gi('autoscout24de'…

    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 926, Column 170: reference to external entity in attribute value
    …425;o&name=hp_tb_aw-dacia-service&site=1"  onclick="var s=s_gi('autoscout24de'…

    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 926, Column 170: reference to entity "site" for which no system identifier could be generated
    …425;o&name=hp_tb_aw-dacia-service&site=1"  onclick="var s=s_gi('autoscout24de'…

    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 884, Column 170: entity was defined here
    …%5Fcardif&name=hp_tb_sw-repair-protect&site=1"  onclick="var s=s_gi('autoscout…
  • Error Line 926, Column 383: end tag for element "nobr" which is not open
    …a-service';s.tl(this,'o', 'Mag-HP-aw-dacia-service');">Weitere Infos</a></nobr>

    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.

  • Warning Line 933, Column 73: reference not terminated by REFC delimiter
    …scout24.de/redir.asp?language=ger&link=http:%2F%2Fad%2Demea%2Edoubleclick%2Ene…

    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 933, Column 73: reference to external entity in attribute value
    …scout24.de/redir.asp?language=ger&link=http:%2F%2Fad%2Demea%2Edoubleclick%2Ene…

    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 933, Column 73: reference to entity "link" for which no system identifier could be generated
    …scout24.de/redir.asp?language=ger&link=http:%2F%2Fad%2Demea%2Edoubleclick%2Ene…

    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 884, Column 61: entity was defined here
    ….autoscout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Ed…
  • Warning Line 933, Column 152: reference not terminated by REFC delimiter
    …%2Fclk%3B267352465%3B93188465%3Bx&name=hp_tb_aw-renault&site=1" id="aw-renault…

    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 933, Column 152: reference to external entity in attribute value
    …%2Fclk%3B267352465%3B93188465%3Bx&name=hp_tb_aw-renault&site=1" id="aw-renault…

    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 933, Column 152: reference to entity "name" for which no system identifier could be generated
    …%2Fclk%3B267352465%3B93188465%3Bx&name=hp_tb_aw-renault&site=1" id="aw-renault…

    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 884, Column 141: entity was defined here
    …2Fmagazine%2Fmz%5Fothers%2Fsw%5Fcardif&name=hp_tb_sw-repair-protect&site=1"  o…
  • Warning Line 933, Column 174: reference not terminated by REFC delimiter
    …5%3B93188465%3Bx&name=hp_tb_aw-renault&site=1" id="aw-renault">Renault</option>

    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 933, Column 174: reference to external entity in attribute value
    …5%3B93188465%3Bx&name=hp_tb_aw-renault&site=1" id="aw-renault">Renault</option>

    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 933, Column 174: reference to entity "site" for which no system identifier could be generated
    …5%3B93188465%3Bx&name=hp_tb_aw-renault&site=1" id="aw-renault">Renault</option>

    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 884, Column 170: entity was defined here
    …%5Fcardif&name=hp_tb_sw-repair-protect&site=1"  onclick="var s=s_gi('autoscout…
  • Error Line 946, Column 11: element "NOSCRIPT" undefined
    	<NOSCRIPT>

    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 947, Column 11: there is no attribute "HREF"
    		<A HREF="http://ad-emea.doubleclick.net/ad/N5648.Autoscout24.omg/B7310124.4;s…

    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 947, Column 103: element "A" undefined
    …a.doubleclick.net/ad/N5648.Autoscout24.omg/B7310124.4;sz=1x1;ord=[timestamp]?">

    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 948, Column 12: there is no attribute "SRC"
    		<IMG SRC="http://ad-emea.doubleclick.net/ad/N5648.Autoscout24.omg/B7310124.4;…

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

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

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

  • Error Line 948, Column 112: there is no attribute "BORDER"
    …124.4;sz=1x1;ord=[timestamp]?" BORDER=0 WIDTH=1 HEIGHT=1 ALT="Advertisement"><…

    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 948, Column 112: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …124.4;sz=1x1;ord=[timestamp]?" BORDER=0 WIDTH=1 HEIGHT=1 ALT="Advertisement"><…
  • Error Line 948, Column 120: there is no attribute "WIDTH"
    …4.4;sz=1x1;ord=[timestamp]?" BORDER=0 WIDTH=1 HEIGHT=1 ALT="Advertisement"></A>

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

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

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

  • Error Line 948, Column 120: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …4.4;sz=1x1;ord=[timestamp]?" BORDER=0 WIDTH=1 HEIGHT=1 ALT="Advertisement"></A>
  • Error Line 948, Column 129: there is no attribute "HEIGHT"
    …4.4;sz=1x1;ord=[timestamp]?" BORDER=0 WIDTH=1 HEIGHT=1 ALT="Advertisement"></A>

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

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

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

  • Error Line 948, Column 129: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …4.4;sz=1x1;ord=[timestamp]?" BORDER=0 WIDTH=1 HEIGHT=1 ALT="Advertisement"></A>
  • Error Line 948, Column 135: there is no attribute "ALT"
    …4.4;sz=1x1;ord=[timestamp]?" BORDER=0 WIDTH=1 HEIGHT=1 ALT="Advertisement"></A>

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

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

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

  • Error Line 948, Column 150: element "IMG" undefined
    …4.4;sz=1x1;ord=[timestamp]?" BORDER=0 WIDTH=1 HEIGHT=1 ALT="Advertisement"></A>

    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 948, Column 154: end tag for "IMG" omitted, but OMITTAG NO was specified
    …4.4;sz=1x1;ord=[timestamp]?" BORDER=0 WIDTH=1 HEIGHT=1 ALT="Advertisement"></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 948, Column 3: start tag was here
    		<IMG SRC="http://ad-emea.doubleclick.net/ad/N5648.Autoscout24.omg/B7310124.4;…
  • Error Line 994, Column 1588: there is no attribute "alt"
    …ooter-Freemail");' name="ANZEIGE" alt="ANZEIGE" title="ANZEIGE" >Freemail@t-on…

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

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

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

  • Warning Line 1042, 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 1042, 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 1042, 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 1042, 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 1042, 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 1042, 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 1042, Column 190: entity was defined here
    …ndow.open('http://del.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponen…
  • Warning Line 1042, 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 1042, 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 1042, 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 1042, 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 1042, 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 1042, Column 195: entity was defined here
    …open('http://del.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponent(loc…
  • Warning Line 1042, 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 1042, 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 1042, 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 1042, 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 1042, 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 1042, Column 206: entity was defined here
    …//del.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponent(location.href+…
  • Warning Line 1042, 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 1042, 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 1042, 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 1042, 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 1042, 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 1042, Column 281: entity was defined here
    …ef+sb_prefix+'extcidm=sb-delicious')+'&title='+encodeURIComponent(document.tit…
  • Warning Line 1042, Column 926: 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 1042, Column 1080: 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 1042, Column 1080: 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 1042, Column 1081: 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 1042, Column 1081: 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 1042, Column 1081: 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 1042, Column 1079: entity was defined here
    …prefix+'extcidm=sb-bookmarks-yahoo')+'&t='+encodeURIComponent(document.title),…
  • Warning Line 1042, Column 1513: 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 1042, Column 1655: 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 1042, Column 1655: 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 1042, Column 1655: 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 1042, Column 281: entity was defined here
    …ef+sb_prefix+'extcidm=sb-delicious')+'&title='+encodeURIComponent(document.tit…
  • Warning Line 1042, Column 2099: 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.
  • Warning Line 1042, Column 2714: character "&" is the first character of a delimiter but occurred as data
    …(location.href.search(/\?/) != -1) ? '&' : '?';window.open('http://www.faceboo…

    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 1042, Column 2844: reference not terminated by REFC delimiter
    …f+sb_prefix+'extcidm=sb-facebook')+'&t='+encodeURIComponent(document.title),'f…

    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 1042, Column 2844: reference to external entity in attribute value
    …f+sb_prefix+'extcidm=sb-facebook')+'&t='+encodeURIComponent(document.title),'f…

    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 1042, Column 2844: reference to entity "t" for which no system identifier could be generated
    …f+sb_prefix+'extcidm=sb-facebook')+'&t='+encodeURIComponent(document.title),'f…

    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 1042, Column 1079: entity was defined here
    …prefix+'extcidm=sb-bookmarks-yahoo')+'&t='+encodeURIComponent(document.title),…
  • Error Line 1049, 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 1049, 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).

  • Warning Line 1101, Column 159: cannot generate system identifier for general entity "d"
    …n-SucheS.html?r=" + escape(document.referrer) + "&d=" + Date.parse(new Date());

    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 1101, Column 159: general entity "d" not defined and no default entity
    …n-SucheS.html?r=" + escape(document.referrer) + "&d=" + Date.parse(new Date());

    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 1101, Column 160: reference not terminated by REFC delimiter
    …n-SucheS.html?r=" + escape(document.referrer) + "&d=" + Date.parse(new Date());

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

  • Error Line 1101, Column 160: reference to entity "d" for which no system identifier could be generated
    …n-SucheS.html?r=" + escape(document.referrer) + "&d=" + Date.parse(new Date());

    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 1101, Column 158: entity was defined here
    …n-SucheS.html?r=" + escape(document.referrer) + "&d=" + Date.parse(new Date());
  • Error Line 1107, 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.

  • Warning Line 1137, Column 59: cannot generate system identifier for general entity "auto"
    var url = 'http://js.revsci.net/gateway/gw.js?csid=J11265&auto=t';

    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 1137, Column 59: general entity "auto" not defined and no default entity
    var url = 'http://js.revsci.net/gateway/gw.js?csid=J11265&auto=t';

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

  • Warning Line 1137, Column 63: reference not terminated by REFC delimiter
    var url = 'http://js.revsci.net/gateway/gw.js?csid=J11265&auto=t';

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

  • Error Line 1137, Column 63: reference to entity "auto" for which no system identifier could be generated
    var url = 'http://js.revsci.net/gateway/gw.js?csid=J11265&auto=t';

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

  • Info Line 1137, Column 58: entity was defined here
    var url = 'http://js.revsci.net/gateway/gw.js?csid=J11265&auto=t';

Visitor Analysis

Daily Visitor
  • 82.833 visits