Billige Flüge schnell & einfach bei billigfluege.de online buchen. ✈ Finden Sie den günstigsten Flug aus unserem Angebot & fliegen Sie billiger in den Urlaub. ...

billigfluege.de
  • Domain Name
    billigfluege.de
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #16102
  • Page Size
    73.4 KB
  • Ip Address
    217.114.208.49
  • Heading
    H1: 2, H2: 11, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 3 JPG, 0 PNG

Website Meta Analysis

  • Title
    Billig Fliegen - günstige Flüge und Billigflüge: Top reduzierte Flug Preise direkt vom Ticketgroßhändler - Billigfluege.de
  • Meta Keyword
    Billigflüge, Billigflug, Billig Fliegen, Billige Flüge, Billigflieger, billigfluege, Billigfluglinien, Billigairline, billigairlines, Billigflugtarife, billigflugtarife, billig flug, billige flüge, billig fliegen.de ,flüge, flug, nurflug, Flug, Fluege, sparfluege, Sparflüge, billig fliegen, billiger fliegen,billigflüge weltweit, direktflug, billig verreisen, preiswert fliegen,billigstflug, billigreisen, innerdeutsch fliegen, frankfurt hahn
  • Meta Description
    Billige Flüge schnell & einfach bei billigfluege.de online buchen. ✈ Finden Sie den günstigsten Flug aus unserem Angebot & fliegen Sie billiger in den Urlaub.

Technical Analysis

  • Webserver
    Apache/2
  • Ip Address
    217.114.208.49
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from billigfluege.de.

HTML Analysis

  • date: Tue, 10 Sep 2013 23:48:43 GMT
  • server: Apache/2
  • provided-host: flugslave17
  • p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
  • expires: Wed, 11 Sep 2013 01:49:40 +0200
  • cache-control: public, max-age=57
  • pragma:
  • x-age: Wed, 11 Sep 2013 01:47:40 +0200
  • etag: "0941db397de0eb687b8720ab6c4547ba"
  • x-app-cache: memcached
  • content-encoding: gzip
  • vary: Accept-Encoding
  • connection: close
  • content-type: text/html; charset=UTF-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
% Copyright (c) 2010 by DENIC
% Version: 2.0
%
% Restricted rights.
%
% Terms and Conditions of Use
%
% The data in this record is provided by DENIC for informational purposes only.
% DENIC does not guarantee its accuracy and cannot, under any circumstances,
% be held liable in case the stored information would prove to be wrong,
% incomplete or not accurate in any sense.
%
% All the domain data that is visible in the whois service is protected by law.
% It is not permitted to use it for any purpose other than technical or
% administrative requirements associated with the operation of the Internet.
% It is explicitly forbidden to extract, copy and/or use or re-utilise in any
% form and by any means (electronically or not) the whole or a quantitatively
% or qualitatively substantial part of the contents of the whois database
% without prior and explicit written permission by DENIC.
% It is prohibited, in particular, to use it for transmission of unsolicited
% and/or commercial and/or advertising by phone, fax, e-mail or for any similar
% purposes.
%
% By maintaining the connection you assure that you have a legitimate interest
% in the data and that you will only use it for the stated purposes. You are
% aware that DENIC maintains the right to initiate legal proceedings against
% you in the event of any breach of this assurance and to bar you from using
% its whois service.
%
% The DENIC whois service on port 43 never discloses any information concerning
% the domain holder/administrative contact. Information concerning the domain
% holder/administrative contact can be obtained through use of our web-based
% whois service available at the DENIC website:
% http://www.denic.de/en/background/whois-service/webwhois.html
%

Domain: billigfluege.de
Nserver: a.u-ns.net
Nserver: b.u-ns.net
Nserver: c.u-ns.net
Nserver: d.u-ns.net
Status: connect
Changed: 2012-02-29T17:00:30+01:00

[Tech-C]
Type: PERSON
Name: Anja Sykora
Organisation: RMK Billigfluege.de GmbH
Address: Werdauer Str. 3
PostalCode: 01069
City: Dresden
CountryCode: DE
Phone: +49-1805-95859980
Fax: +49-1805-95859981
Email: email
Changed: 2011-09-05T18:54:31+02:00

[Zone-C]
Type: PERSON
Name: Anja Sykora
Organisation: RMK Billigfluege.de GmbH
Address: Werdauer Str. 3
PostalCode: 01069
City: Dresden
CountryCode: DE
Phone: +49-1805-95859980
Fax: +49-1805-95859981
Email: email
Changed: 2011-09-05T18:54:31+02:00

IP 217.114.208.49 Analysis

  • Country Code
    DE
  • Country Code3
    DEU
  • Country Name
    Germany
  • City
    EU
  • Continent Code
    51° North
  • Latitude
    9.
  • Longitude
  • No whois ip data for 217.114.208.49

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 34 Errors
  • 12 Warnings
Ratio Text/Html
  • 0.5777210001729942
Message Error
  • Error Line 2, Column 7: there is no attribute "class"
    class="nojs" xmlns="http://www.w3.org/1999/xhtml" lang="de" xml:lang="de"><head

    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 12, Column 21: there is no attribute "value"
    name="google" value="notranslate" /><meta

    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 12, Column 36: required attribute "content" not specified
    name="google" value="notranslate" /><meta

    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 85, Column 29: there is no attribute "name"
    action="" method="get" name="newsletter_form" id="newsletter_form"><div

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

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

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

  • Warning Line 112, Column 64: cannot generate system identifier for general entity "answer"
    …rt.google.com/websearch/bin/answer.py?hl=de&answer=23852">hier</a>!</div></div>

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

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

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

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

  • Error Line 112, Column 64: general entity "answer" not defined and no default entity
    …rt.google.com/websearch/bin/answer.py?hl=de&answer=23852">hier</a>!</div></div>

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

  • Warning Line 112, Column 70: reference not terminated by REFC delimiter
    …rt.google.com/websearch/bin/answer.py?hl=de&answer=23852">hier</a>!</div></div>

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

  • Warning Line 112, Column 70: reference to external entity in attribute value
    …rt.google.com/websearch/bin/answer.py?hl=de&answer=23852">hier</a>!</div></div>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 112, Column 70: reference to entity "answer" for which no system identifier could be generated
    …rt.google.com/websearch/bin/answer.py?hl=de&answer=23852">hier</a>!</div></div>

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

  • Info Line 112, Column 63: entity was defined here
    …rt.google.com/websearch/bin/answer.py?hl=de&answer=23852">hier</a>!</div></div>
  • Error Line 163, Column 14: there is no attribute "autocomplete"
    autocomplete="off" name="sFlightInput[depCity]" id="depCity" class="airport_dep…

    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 173, Column 18: character "[" is not allowed in the value of attribute "for"
    for="sFlightInput[departureTimeRange]">zeitl. Flexibilität</label>

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 587, Column 18: character "[" is not allowed in the value of attribute "for"
    for="sFlightInput[returnTimeRange]">zeitl. Flexibilität</label>

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 648, Column 66: there is no attribute "language"
    …eb03076c018e7c925', '<script language="javascript1.1" src=http://adserver.adte…

    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 648, Column 86: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …'<script language="javascript1.1" src=http://adserver.adtech.de/addyn/3.0/781/…
  • Error Line 648, Column 92: NET-enabling start-tag not immediately followed by null end-tag
    …pt language="javascript1.1" src=http://adserver.adtech.de/addyn/3.0/781/352241…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 648, Column 92: required attribute "type" not specified
    …pt language="javascript1.1" src=http://adserver.adtech.de/addyn/3.0/781/352241…

    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 648, Column 92: document type does not allow element "script" here
    …pt language="javascript1.1" src=http://adserver.adtech.de/addyn/3.0/781/352241…

    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 648, Column 189: character "<" is the first character of a delimiter but occurred as data
    …00;target=_blank;grp=;misc=1359028054><\/script>', o || {});</script> <noscrip…

    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 650, Column 89: there is no attribute "target"
    …ver.adtech.de/adlink/3.0/781/3522413/0/16/ADTECH;loc=300;grp=" target="_blank">

    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 650, Column 97: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …ver.adtech.de/adlink/3.0/781/3522413/0/16/ADTECH;loc=300;grp=" target="_blank">

    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 652, Column 88: there is no attribute "border"
    …/3.0/781/3522413/0/16/ADTECH;loc=300;grp=" border="0" width="1" height="1"></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 652, Column 112: required attribute "alt" not specified
    …/3.0/781/3522413/0/16/ADTECH;loc=300;grp=" border="0" width="1" height="1"></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 652, Column 116: end tag for "img" omitted, but OMITTAG NO was specified
    …/3.0/781/3522413/0/16/ADTECH;loc=300;grp=" border="0" width="1" height="1"></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 651, Column 1: start tag was here
    <img
  • Error Line 666, Column 76: there is no attribute "data-destination"
    …" rel="nofollow" name="MIL" data-destination="MIL" title="Mailand ab 30 &euro;"

    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 852, Column 55: document type does not allow element "h3" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …info_tab" href="javascript:;" id="benefits"><h3>Ihre Vorteile</h3></a></li><li>

    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 854, Column 54: document type does not allow element "h3" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …_tab" href="javascript:;" id="flights"><h3>Sparen wie im Flug</h3></a></li><li>

    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 856, Column 55: document type does not allow element "h3" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …" href="javascript:;" id="airlines"><h3>Billigfluege.de News</h3></a></li><li >

    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 858, Column 54: document type does not allow element "h3" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …info_tab" href="javascript:;" id="lowcost"><h3>Hilfe und FAQ</h3></a></li><li >

    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 860, Column 60: document type does not allow element "h3" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ab" href="http://www.billigfluege.de/card"><h3>MasterCard GOLD</h3></a></li><li

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

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

  • Warning Line 865, Column 101: character "&" is the first character of a delimiter but occurred as data
    …rline-Deals!</strong></li><li>Schnell & sicher zum <strong>billigsten Flug!</s…

    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 887, Column 5: ID "Content" already defined
    id="Content" class="floatfix"><ul

    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 864, Column 5: ID "Content" first defined here
    id="Content" class="floatfix"><ul
  • Warning Line 916, Column 1098: character "&" is the first character of a delimiter but occurred as data
    … : function (form, status) {if(status && noemail == false) {registerNewsletter…

    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 916, Column 1099: character "&" is the first character of a delimiter but occurred as data
    …: function (form, status) {if(status && noemail == false) {registerNewsletter(…

    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 916, Column 2180: cannot generate system identifier for general entity "utm_medium"
    …ge.de',a: 'utm_source=billigfluege.de&utm_medium=referral&utm_campaign=sec_pop…

    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 916, Column 2180: general entity "utm_medium" not defined and no default entity
    …ge.de',a: 'utm_source=billigfluege.de&utm_medium=referral&utm_campaign=sec_pop…

    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 916, Column 2190: reference not terminated by REFC delimiter
    …'utm_source=billigfluege.de&utm_medium=referral&utm_campaign=sec_popunder'};va…

    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 916, Column 2190: reference to entity "utm_medium" for which no system identifier could be generated
    …'utm_source=billigfluege.de&utm_medium=referral&utm_campaign=sec_popunder'};va…

    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 916, Column 2179: entity was defined here
    …ege.de',a: 'utm_source=billigfluege.de&utm_medium=referral&utm_campaign=sec_po…
  • Warning Line 916, Column 2200: cannot generate system identifier for general entity "utm_campaign"
    …e=billigfluege.de&utm_medium=referral&utm_campaign=sec_popunder'};var aStorage…

    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 916, Column 2200: general entity "utm_campaign" not defined and no default entity
    …e=billigfluege.de&utm_medium=referral&utm_campaign=sec_popunder'};var aStorage…

    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 916, Column 2212: reference not terminated by REFC delimiter
    …ge.de&utm_medium=referral&utm_campaign=sec_popunder'};var aStorage = false;$('…

    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 916, Column 2212: reference to entity "utm_campaign" for which no system identifier could be generated
    …ge.de&utm_medium=referral&utm_campaign=sec_popunder'};var aStorage = false;$('…

    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 916, Column 2199: entity was defined here
    …ce=billigfluege.de&utm_medium=referral&utm_campaign=sec_popunder'};var aStorag…
  • Warning Line 916, Column 2658: character "&" is the first character of a delimiter but occurred as data
    …alue;}});var bShow = aPopunder.active && !$.constants.isOpera && !$.constants.…

    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 916, Column 2659: character "&" is the first character of a delimiter but occurred as data
    …lue;}});var bShow = aPopunder.active && !$.constants.isOpera && !$.constants.i…

    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 916, Column 2682: character "&" is the first character of a delimiter but occurred as data
    …punder.active && !$.constants.isOpera && !$.constants.isIpad;$('#directCompare…

    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 916, Column 2683: character "&" is the first character of a delimiter but occurred as data
    …under.active && !$.constants.isOpera && !$.constants.isIpad;$('#directCompare'…

    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 916, Column 3167: character ";" not allowed in attribute specification list
    …ink = '?',r, i;for (i=0;i<aForm.length;i++) {r = aForm[i].name.toString().matc…
  • Error Line 916, Column 3167: element "aForm.length" undefined
    …ink = '?',r, i;for (i=0;i<aForm.length;i++) {r = aForm[i].name.toString().matc…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 916, Column 3235: character "&" is the first character of a delimiter but occurred as data
    …ing().match(/\[\w+\]/g);if (r != null && $.inArray(r[0], aProps) != -1) {sLink…

    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 916, Column 3236: character "&" is the first character of a delimiter but occurred as data
    …ng().match(/\[\w+\]/g);if (r != null && $.inArray(r[0], aProps) != -1) {sLink …

    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 916, Column 3339: character "&" is the first character of a delimiter but occurred as data
    …encodeURIComponent(aForm[i].value) + '&';}}sLink += 'sFlightInput[departureTim…

    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 916, Column 3388: character "&" is the first character of a delimiter but occurred as data
    …+= 'sFlightInput[departureTimeRange]=0&';sLink += 'sFlightInput[returnTimeRang…

    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 916, Column 3432: character "&" is the first character of a delimiter but occurred as data
    …nk += 'sFlightInput[returnTimeRange]=0&';for (i in aPopunder.types) {if ($('#d…

    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 916, Column 4298: character "<" is the first character of a delimiter but occurred as data
    … = $.ajax({url: ((request.term.length < 10) ? "http://static.billigfluege.de/"…

    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 916, Column 5401: character "&" is the first character of a delimiter but occurred as data
    … $("#accDepRegion");if (e.which !== 9 && e.which !== 13 && e.which !== 27 && e…

    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 916, Column 5402: character "&" is the first character of a delimiter but occurred as data
    …$("#accDepRegion");if (e.which !== 9 && e.which !== 13 && e.which !== 27 && e.…

    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 916, Column 5419: character "&" is the first character of a delimiter but occurred as data
    …);if (e.which !== 9 && e.which !== 13 && e.which !== 27 && e.which !== 37 && e…

    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 916, Column 5420: character "&" is the first character of a delimiter but occurred as data
    …;if (e.which !== 9 && e.which !== 13 && e.which !== 27 && e.which !== 37 && e.…

    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 916, Column 5437: character "&" is the first character of a delimiter but occurred as data
    …9 && e.which !== 13 && e.which !== 27 && e.which !== 37 && e.which !== 38 && e…

    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 916, Column 5438: character "&" is the first character of a delimiter but occurred as data
    … && e.which !== 13 && e.which !== 27 && e.which !== 37 && e.which !== 38 && e.…

    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 916, Column 5455: character "&" is the first character of a delimiter but occurred as data
    …3 && e.which !== 27 && e.which !== 37 && e.which !== 38 && e.which !== 39 && e…

    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 916, Column 5456: character "&" is the first character of a delimiter but occurred as data
    … && e.which !== 27 && e.which !== 37 && e.which !== 38 && e.which !== 39 && e.…

    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 916, Column 5473: character "&" is the first character of a delimiter but occurred as data
    …7 && e.which !== 37 && e.which !== 38 && e.which !== 39 && e.which !== 40 && e…

    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 916, Column 5474: character "&" is the first character of a delimiter but occurred as data
    … && e.which !== 37 && e.which !== 38 && e.which !== 39 && e.which !== 40 && e.…

    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 916, Column 5491: character "&" is the first character of a delimiter but occurred as data
    …7 && e.which !== 38 && e.which !== 39 && e.which !== 40 && e.which !== 35 && e…

    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 916, Column 5492: character "&" is the first character of a delimiter but occurred as data
    … && e.which !== 38 && e.which !== 39 && e.which !== 40 && e.which !== 35 && e.…

    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 916, Column 5509: character "&" is the first character of a delimiter but occurred as data
    …8 && e.which !== 39 && e.which !== 40 && e.which !== 35 && e.which !== 36) {$h…

    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 916, Column 5510: character "&" is the first character of a delimiter but occurred as data
    … && e.which !== 39 && e.which !== 40 && e.which !== 35 && e.which !== 36) {$hi…

    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 916, Column 5527: character "&" is the first character of a delimiter but occurred as data
    …9 && e.which !== 40 && e.which !== 35 && e.which !== 36) {$hidden.val('');$reg…

    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 916, Column 5528: character "&" is the first character of a delimiter but occurred as data
    … && e.which !== 40 && e.which !== 35 && e.which !== 36) {$hidden.val('');$regi…

    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 916, Column 6236: character "<" is the first character of a delimiter but occurred as data
    … = $.ajax({url: ((request.term.length < 10) ? "http://static.billigfluege.de/"…

    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 916, Column 7341: character "&" is the first character of a delimiter but occurred as data
    … $("#accArrRegion");if (e.which !== 9 && e.which !== 13 && e.which !== 27 && e…

    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 916, Column 7342: character "&" is the first character of a delimiter but occurred as data
    …$("#accArrRegion");if (e.which !== 9 && e.which !== 13 && e.which !== 27 && e.…

    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 916, Column 7359: character "&" is the first character of a delimiter but occurred as data
    …);if (e.which !== 9 && e.which !== 13 && e.which !== 27 && e.which !== 37 && e…

    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 916, Column 7360: character "&" is the first character of a delimiter but occurred as data
    …;if (e.which !== 9 && e.which !== 13 && e.which !== 27 && e.which !== 37 && e.…

    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 916, Column 7377: character "&" is the first character of a delimiter but occurred as data
    …9 && e.which !== 13 && e.which !== 27 && e.which !== 37 && e.which !== 38 && e…

    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 916, Column 7378: character "&" is the first character of a delimiter but occurred as data
    … && e.which !== 13 && e.which !== 27 && e.which !== 37 && e.which !== 38 && e.…

    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 916, Column 7395: character "&" is the first character of a delimiter but occurred as data
    …3 && e.which !== 27 && e.which !== 37 && e.which !== 38 && e.which !== 39 && e…

    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 916, Column 7396: character "&" is the first character of a delimiter but occurred as data
    … && e.which !== 27 && e.which !== 37 && e.which !== 38 && e.which !== 39 && e.…

    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 916, Column 7413: character "&" is the first character of a delimiter but occurred as data
    …7 && e.which !== 37 && e.which !== 38 && e.which !== 39 && e.which !== 40 && e…

    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 916, Column 7414: character "&" is the first character of a delimiter but occurred as data
    … && e.which !== 37 && e.which !== 38 && e.which !== 39 && e.which !== 40 && e.…

    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 916, Column 7431: character "&" is the first character of a delimiter but occurred as data
    …7 && e.which !== 38 && e.which !== 39 && e.which !== 40 && e.which !== 35 && e…

    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 916, Column 7432: character "&" is the first character of a delimiter but occurred as data
    … && e.which !== 38 && e.which !== 39 && e.which !== 40 && e.which !== 35 && e.…

    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 916, Column 7449: character "&" is the first character of a delimiter but occurred as data
    …8 && e.which !== 39 && e.which !== 40 && e.which !== 35 && e.which !== 36) {$h…

    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 916, Column 7450: character "&" is the first character of a delimiter but occurred as data
    … && e.which !== 39 && e.which !== 40 && e.which !== 35 && e.which !== 36) {$hi…

    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 916, Column 7467: character "&" is the first character of a delimiter but occurred as data
    …9 && e.which !== 40 && e.which !== 35 && e.which !== 36) {$hidden.val('');$reg…

    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 916, Column 7468: character "&" is the first character of a delimiter but occurred as data
    … && e.which !== 40 && e.which !== 35 && e.which !== 36) {$hidden.val('');$regi…

    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 916, Column 8014: character "<" is the first character of a delimiter but occurred as data
    …Val').datepicker("getDate").getTime() < $(this).datepicker("getDate").getTime(…

    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 916, Column 10355: end tag for "aForm.length" omitted, but OMITTAG NO was specified
    …gisterNewsletter(true);});}); </script><script type="text/javascript">try{var …

    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 916, Column 3154: start tag was here
    …izeArray(),sLink = '?',r, i;for (i=0;i<aForm.length;i++) {r = aForm[i].name.to…
  • Warning Line 917, Column 104: cannot generate system identifier for general entity "ng_nuggn"
    …com/js/adition.sjs?ng_nuggsub=unister&ng_nuggn=2020431744&ng_nuggsid=138837183…

    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 917, Column 104: general entity "ng_nuggn" not defined and no default entity
    …com/js/adition.sjs?ng_nuggsub=unister&ng_nuggn=2020431744&ng_nuggsid=138837183…

    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 917, Column 112: reference not terminated by REFC delimiter
    …dition.sjs?ng_nuggsub=unister&ng_nuggn=2020431744&ng_nuggsid=1388371837&ng_nug…

    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 917, Column 112: reference to entity "ng_nuggn" for which no system identifier could be generated
    …dition.sjs?ng_nuggsub=unister&ng_nuggn=2020431744&ng_nuggsid=1388371837&ng_nug…

    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 917, Column 103: entity was defined here
    ….com/js/adition.sjs?ng_nuggsub=unister&ng_nuggn=2020431744&ng_nuggsid=13883718…
  • Warning Line 917, Column 124: cannot generate system identifier for general entity "ng_nuggsid"
    …g_nuggsub=unister&ng_nuggn=2020431744&ng_nuggsid=1388371837&ng_nuggtg=homepage…

    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 917, Column 124: general entity "ng_nuggsid" not defined and no default entity
    …g_nuggsub=unister&ng_nuggn=2020431744&ng_nuggsid=1388371837&ng_nuggtg=homepage…

    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 917, Column 134: reference not terminated by REFC delimiter
    …unister&ng_nuggn=2020431744&ng_nuggsid=1388371837&ng_nuggtg=homepage', 'http:/…

    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 917, Column 134: reference to entity "ng_nuggsid" for which no system identifier could be generated
    …unister&ng_nuggn=2020431744&ng_nuggsid=1388371837&ng_nuggtg=homepage', 'http:/…

    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 917, Column 123: entity was defined here
    …ng_nuggsub=unister&ng_nuggn=2020431744&ng_nuggsid=1388371837&ng_nuggtg=homepag…
  • Warning Line 917, Column 146: cannot generate system identifier for general entity "ng_nuggtg"
    …uggn=2020431744&ng_nuggsid=1388371837&ng_nuggtg=homepage', 'http://imagesrv.ad…

    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 917, Column 146: general entity "ng_nuggtg" not defined and no default entity
    …uggn=2020431744&ng_nuggsid=1388371837&ng_nuggtg=homepage', 'http://imagesrv.ad…

    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 917, Column 155: reference not terminated by REFC delimiter
    …431744&ng_nuggsid=1388371837&ng_nuggtg=homepage', 'http://imagesrv.adition.com…

    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 917, Column 155: reference to entity "ng_nuggtg" for which no system identifier could be generated
    …431744&ng_nuggsid=1388371837&ng_nuggtg=homepage', 'http://imagesrv.adition.com…

    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 917, Column 145: entity was defined here
    …nuggn=2020431744&ng_nuggsid=1388371837&ng_nuggtg=homepage', 'http://imagesrv.a…
  • Warning Line 924, Column 31: character "&" is the first character of a delimiter but occurred as data
                    (lp.s() === 0 && lp.n() === true) ? f() : lp.a(f);

    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 924, Column 32: character "&" is the first character of a delimiter but occurred as data
                    (lp.s() === 0 && lp.n() === true) ? f() : lp.a(f);

    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 932, Column 5: there is no attribute "src"
    src="http://fls.doubleclick.net/activityi;src=3178833;type=besuc621;cat=landi84…

    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 932, Column 102: there is no attribute "width"
    …c621;cat=landi846;ord=5927959?" width="1" height="1" frameborder="0" style="di…

    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 932, Column 113: there is no attribute "height"
    …ndi846;ord=5927959?" width="1" height="1" frameborder="0" style="display:none"…

    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 932, Column 129: there is no attribute "frameborder"
    …59?" width="1" height="1" frameborder="0" style="display:none"></iframe><scrip…

    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 932, Column 139: there is no attribute "style"
    …="1" height="1" frameborder="0" style="display:none"></iframe><script type="te…

    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 932, Column 153: element "iframe" undefined
    …" frameborder="0" style="display:none"></iframe><script type="text/javascript"…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 947, Column 149: cannot generate system identifier for general entity "guid"
    …rsion/973721582/?label=f2ZpCMrAuQIQ7p-n0AM&guid=ON&script=0"/></div></noscript>

    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 947, Column 149: general entity "guid" not defined and no default entity
    …rsion/973721582/?label=f2ZpCMrAuQIQ7p-n0AM&guid=ON&script=0"/></div></noscript>

    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 947, Column 153: reference not terminated by REFC delimiter
    …rsion/973721582/?label=f2ZpCMrAuQIQ7p-n0AM&guid=ON&script=0"/></div></noscript>

    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 947, Column 153: reference to external entity in attribute value
    …rsion/973721582/?label=f2ZpCMrAuQIQ7p-n0AM&guid=ON&script=0"/></div></noscript>

    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 947, Column 153: reference to entity "guid" for which no system identifier could be generated
    …rsion/973721582/?label=f2ZpCMrAuQIQ7p-n0AM&guid=ON&script=0"/></div></noscript>

    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 947, Column 148: entity was defined here
    …rsion/973721582/?label=f2ZpCMrAuQIQ7p-n0AM&guid=ON&script=0"/></div></noscript>
  • Warning Line 947, Column 157: cannot generate system identifier for general entity "script"
    …rsion/973721582/?label=f2ZpCMrAuQIQ7p-n0AM&guid=ON&script=0"/></div></noscript>

    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 947, Column 157: general entity "script" not defined and no default entity
    …rsion/973721582/?label=f2ZpCMrAuQIQ7p-n0AM&guid=ON&script=0"/></div></noscript>

    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 947, Column 163: reference not terminated by REFC delimiter
    …rsion/973721582/?label=f2ZpCMrAuQIQ7p-n0AM&guid=ON&script=0"/></div></noscript>

    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 947, Column 163: reference to external entity in attribute value
    …rsion/973721582/?label=f2ZpCMrAuQIQ7p-n0AM&guid=ON&script=0"/></div></noscript>

    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 947, Column 163: reference to entity "script" for which no system identifier could be generated
    …rsion/973721582/?label=f2ZpCMrAuQIQ7p-n0AM&guid=ON&script=0"/></div></noscript>

    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 947, Column 156: entity was defined here
    …rsion/973721582/?label=f2ZpCMrAuQIQ7p-n0AM&guid=ON&script=0"/></div></noscript>
  • Warning Line 173, Column 6: reference to non-existent ID "sFlightInput[departureTimeRange]"
    for="sFlightInput[departureTimeRange]">zeitl. Flexibilität</label>

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

  • Warning Line 587, Column 6: reference to non-existent ID "sFlightInput[returnTimeRange]"
    for="sFlightInput[returnTimeRange]">zeitl. Flexibilität</label>

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

Visitor Analysis

Daily Visitor
  • 18.667 visits