airnewzealand.co.nz

Air New Zealand's official site offering Flights, Airfares, Holidays & Travel Packages in New Zealand, to Australia and Worldwide. ...

Display Widget for this domain on your website. Click Here
This data was last updated from 17-09-2013 08:38:01  (update).

Overview Info

  • Domain Name
    airnewzealand.co.nz
  • Favicon
  • Alexa Rank
    #37510
  • Google Page Rank
    PR 6
  • Ip Address
    162.112.18.131
  • Page Size
    371.8 KB
  • Images
    2 GIF, 5 JPG, 20 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 2 0 1 0 0

Website Meta Analysis



  • Title
    Cheap Flights, Airfares & Holidays - Air New Zealand Official Site - New Zealand Site
  • Meta Keyword
  • Meta Description
    Air New Zealand's official site offering Flights, Airfares, Holidays & Travel Packages in New Zealand, to Australia and Worldwide.

Technical Analysis



  • Webserver
  • Ip Address
    162.112.18.131
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from airnewzealand.co.nz.

HTML Analysis

  • cache-control: max-age=600
  • expires: Tue, 17 Sep 2013 20:47:44 GMT
  • content-type: text/html; charset=UTF-8
  • vary: Accept-Encoding
  • content-encoding: gzip
  • accept-ranges: bytes
  • connection: Keep-Alive
  • date: Tue, 17 Sep 2013 20:37:57 GMT
  • age: 13
  • content-length: 60633
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
% New Zealand Domain Name Registry Limited
% Users confirm on submission their agreement to all published Terms
%
version: 5.00
query_datetime: 2012-08-17T00:00:38+12:00
domain_name: airnewzealand.co.nz
query_status: 200 Active
domain_dateregistered: 1996-09-11T00:00:00+12:00
domain_datebilleduntil: 2013-09-30T00:00:00+13:00
domain_datelastmodified: 2012-07-27T21:42:36+12:00
domain_delegaterequested: yes
domain_signed: no
%
registrar_name: Melbourne IT Limited
registrar_address1: Level 2
registrar_address2: 120 King Street
registrar_city: Melbourne
registrar_province: Victoria
registrar_postalcode: 3000
registrar_country: AU (AUSTRALIA)
registrar_phone: +61 3 8624 2300
registrar_fax: +61 3 8624 2499
registrar_email: email
%
registrant_contact_name: Air New Zealand Limited
registrant_contact_address1: 185 Fanshawe Street
registrant_contact_city: AUCKLAND
registrant_contact_country: NZ (NEW ZEALAND)
registrant_contact_phone: +64 9 93362545
registrant_contact_email: email
%
admin_contact_name: Domain Administrator
admin_contact_address1: 185 Fanshawe Street
admin_contact_city: AUCKLAND
admin_contact_country: NZ (NEW ZEALAND)
admin_contact_phone: +64 9 93362545
admin_contact_email: email
%
technical_contact_name: Account Manager
technical_contact_address1: Level 2, 120 King St
technical_contact_address2: Auckland
technical_contact_city: Melbourne
technical_contact_country: NZ (NEW ZEALAND)
technical_contact_phone: +61 3 86242465
technical_contact_fax: +61 3 96283606
technical_contact_email: email
%
ns_name_01: ns1.airnz.co.nz
ns_name_02: ns2.airnz.co.nz
ns_name_03: terminator.xtra.co.nz
%
% Users are advised that the following activities are strictly forbidden.
%
% Using multiple WHOIS queries, or using the output of multiple WHOIS
% queries in conjunction with any other facility or service, to enable
% or effect a download of part or all of the .nz Register.
%
% Using any information contained in the WHOIS query output to attempt a
% targeted contact campaign with any person, or any organisation, using any
% medium.
%
% A breach of these conditions will be treated as a breach of the .nz Policies
% and Procedures. Sanctions in line with those specified in the policies and
% procedures at www.dnc.org.nz may result from any breach.
%
% Copyright InternetNZ

DNS Analysis


DNS servers
ns1.airnz.co.nz [162.112.18.70]
ns2.airnz.co.nz [162.112.18.71]
terminator.xtra.co.nz [202.27.184.5]


DNS Records

Answer records
airnewzealand.co.nz SOA
server: ns1.airnz.co.nz
email: hostmaster@airnz.co.nz
serial: 2012111601
refresh: 10800
retry: 3600
expire: 1209600
minimum ttl: 10800
86400s
airnewzealand.co.nz NS  terminator.xtra.co.nz 86400s
airnewzealand.co.nz NS  ns2.airnz.co.nz 86400s
airnewzealand.co.nz NS  ns1.airnz.co.nz 86400s
airnewzealand.co.nz A 162.112.18.131 86400s
airnewzealand.co.nz MX
preference: 10
exchange: mx1.airnz.co.nz
86400s
airnewzealand.co.nz MX
preference: 20
exchange: mx2.airnz.co.nz
86400s

Authority records

Additional records

IP 162.112.18.131 Analysis

  • Country Code
    NZ
  • Country Code3
    NZL
  • Country Name
    New Zealand
  • City
    Auckland
  • Continent Code
    OC
  • Latitude
    36.8667
  • Longitude
    174.7667
  • % [whois.apnic.net node-3]
    % Whois data copyright terms http://www.apnic.net/db/dbcopyright.html

    inetnum: 162.112.0.0 - 162.112.255.255
    netname: AIRNZ
    descr: Air New Zealand
    descr: imported inetnum object for ANZL
    country: NZ
    admin-c: GM168-AP
    tech-c: GM168-AP
    status: ALLOCATED PORTABLE
    remarks: ----------
    remarks: imported from ARIN object for ANZL
    remarks: ----------
    notify: gavin.mcdowell@airnz.co.nz
    mnt-by: APNIC-HM
    mnt-lower: MNT-ERX-AIRNZLT-NON-NZ
    mnt-routes: MNT-ERX-AIRNZLT-NON-NZ
    changed: hostmaster@arin.net 20030303
    changed: hm-changed@apnic.net 20040926
    changed: hm-changed@apnic.net 20041221
    source: APNIC

    person: Gavin McDowell
    nic-hdl: GM168-AP
    e-mail: hostmaster@airnz.co.nz
    address: Downtown House - L8
    address: 21 Queen Street
    address: Private Bag 92007
    address: Auckland 1020
    address: NEW ZEALAND
    phone: +64-9-336-3228
    fax-no: +64-9-336-2856
    country: NZ
    changed: hostmaster@airnz.co.nz 20041221
    mnt-by: MNT-ERX-AIRNZLT-NON-NZ
    changed: hm-changed@apnic.net 20041221
    source: APNIC


Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 122 Errors
  • 70 Warnings
Ratio Text/Html
  • 0.1673556975058309
Message Error
  • Warning Line 8, Column 48: character "&" is the first character of a delimiter but occurred as data
    …eap Flights, Discount Airfares, Deals & Vacations - Air New Zealand  - Officia…

    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 90, Column 10: document type does not allow element "noscript" here; assuming missing "object" start-tag
    <noscript>
  • Error Line 91, Column 23: document type does not allow element "style" here
    <style type="text/css">

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

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

  • Warning Line 114, Column 25: character "&" is the first character of a delimiter but occurred as data
    if(jq('#origin').length && !jq('#origin').val()) {

    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 114, Column 26: character "&" is the first character of a delimiter but occurred as data
    if(jq('#origin').length && !jq('#origin').val()) {

    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 120, Column 10: character "&" is the first character of a delimiter but occurred as data
    if (data && data.length == 3) {

    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 120, Column 11: character "&" is the first character of a delimiter but occurred as data
    if (data && data.length == 3) {

    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 131, Column 7: end tag for "object" omitted, but OMITTAG NO was specified
    </head>

    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 90, Column 1: start tag was here
    <noscript>
  • Error Line 143, Column 10: there is no attribute "role"
    <ul role="navigation" id="top-nav" aria-label="Site Navigation">

    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 143, Column 47: there is no attribute "aria-label"
    <ul role="navigation" id="top-nav" aria-label="Site Navigation">

    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 144, Column 19: there is no attribute "aria-haspopup"
    <li aria-haspopup="true" role="menuitem" id="header-menu-24141" class="level1 l…

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

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

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

  • Error Line 144, Column 31: there is no attribute "role"
    <li aria-haspopup="true" role="menuitem" id="header-menu-24141" class="level1 l…

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

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

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

  • Error Line 145, Column 35: there is no attribute "data-original-url"
    <a href="/home" data-original-url="home" title="Flights" aria-label="Flights">F…

    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 145, Column 69: there is no attribute "aria-label"
    …url="home" title="Flights" aria-label="Flights">Flights<span class="level1-arr…

    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 146, Column 11: there is no attribute "role"
    <div role="dialog" class="submenu-block 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 201, Column 39: there is no attribute "role"
    <input class="flight-tools-sbmt" role="button" type="image" title="Continue" al…

    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 328, Column 9: there is no attribute "role"
    <a role="display" href="/airfare-deals-new-zealand" rev="" target="_self" class…

    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 343, Column 131: cannot generate system identifier for general entity "type"
    …nsform=FISD&amp;cursite=www.airnz.com&type=d&range=a&airportcode=LAX" rev="" 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 343, Column 131: general entity "type" not defined and no default entity
    …nsform=FISD&amp;cursite=www.airnz.com&type=d&range=a&airportcode=LAX" rev="" 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 343, Column 135: reference not terminated by REFC delimiter
    …rm=FISD&amp;cursite=www.airnz.com&type=d&range=a&airportcode=LAX" rev="" targe…

    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 343, Column 135: reference to external entity in attribute value
    …rm=FISD&amp;cursite=www.airnz.com&type=d&range=a&airportcode=LAX" rev="" targe…

    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 343, Column 135: reference to entity "type" for which no system identifier could be generated
    …rm=FISD&amp;cursite=www.airnz.com&type=d&range=a&airportcode=LAX" rev="" targe…

    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 343, Column 130: entity was defined here
    …ansform=FISD&amp;cursite=www.airnz.com&type=d&range=a&airportcode=LAX" rev="" …
  • Warning Line 343, Column 138: cannot generate system identifier for general entity "range"
    …FISD&amp;cursite=www.airnz.com&type=d&range=a&airportcode=LAX" rev="" target="…

    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 343, Column 138: general entity "range" not defined and no default entity
    …FISD&amp;cursite=www.airnz.com&type=d&range=a&airportcode=LAX" rev="" target="…

    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 343, Column 143: reference not terminated by REFC delimiter
    …amp;cursite=www.airnz.com&type=d&range=a&airportcode=LAX" rev="" target="_self…

    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 343, Column 143: reference to external entity in attribute value
    …amp;cursite=www.airnz.com&type=d&range=a&airportcode=LAX" rev="" target="_self…

    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 343, Column 143: reference to entity "range" for which no system identifier could be generated
    …amp;cursite=www.airnz.com&type=d&range=a&airportcode=LAX" rev="" target="_self…

    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 343, Column 137: entity was defined here
    …=FISD&amp;cursite=www.airnz.com&type=d&range=a&airportcode=LAX" rev="" target=…
  • Warning Line 343, Column 146: cannot generate system identifier for general entity "airportcode"
    …;cursite=www.airnz.com&type=d&range=a&airportcode=LAX" rev="" target="_self" c…

    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 343, Column 146: general entity "airportcode" not defined and no default entity
    …;cursite=www.airnz.com&type=d&range=a&airportcode=LAX" rev="" target="_self" c…

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

  • Warning Line 343, Column 157: reference not terminated by REFC delimiter
    …w.airnz.com&type=d&range=a&airportcode=LAX" rev="" target="_self" class="" tit…

    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 343, Column 157: reference to external entity in attribute value
    …w.airnz.com&type=d&range=a&airportcode=LAX" rev="" target="_self" class="" tit…

    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 343, Column 157: reference to entity "airportcode" for which no system identifier could be generated
    …w.airnz.com&type=d&range=a&airportcode=LAX" rev="" target="_self" class="" tit…

    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 343, Column 145: entity was defined here
    …p;cursite=www.airnz.com&type=d&range=a&airportcode=LAX" rev="" target="_self" …
  • Error Line 427, Column 186: syntax of attribute value does not conform to declared value
    …Z2h0PTcwMCxsZWZ0PTAsdG9wPSc=" target="" class="popup " title="">Golden Oldies …

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 544, Column 5: end tag for "ul" which is not finished
    </ul>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 571, Column 71: there is no attribute "autocomplete"
    …pnavSearch" method="get" autocomplete="off" action="javascript:searchHandler('…

    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 577, Column 33: there is no attribute "aria-label"
    <input role="button" aria-label="Search" type="image" name="searchGo" id="searc…

    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 1009, Column 35: document type does not allow element "style" here
    <style type="text/css" media="all">

    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 1086, Column 192: document type does not allow element "img" here
    …terefreshSS/"+droparrowimage+"' alt='' title='' width='100%' height='100%' />";

    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 1102, Column 124: there is no attribute "autocomplete"
    …return noenter(event)" value="" name="origin" autocomplete="off" tabindex="1"/>

    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 1122, Column 98: character "[" is not allowed in the value of attribute "id"
    …name="searchLegs[0].tripStartDate" id="searchLegs[0].tripStartDate" value="" />

    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 1123, Column 95: character "[" is not allowed in the value of attribute "id"
    …me="searchLegs[0].tripStartMonth" id="searchLegs[0].tripStartMonth" value="" />

    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 1130, Column 98: character "[" is not allowed in the value of attribute "id"
    …name="searchLegs[1].tripStartDate" id="searchLegs[1].tripStartDate" value="" />

    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 1131, Column 95: character "[" is not allowed in the value of attribute "id"
    …me="searchLegs[1].tripStartMonth" id="searchLegs[1].tripStartMonth" value="" />

    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 1208, Column 45: syntax of attribute value does not conform to declared value
    	    		<option value="smartsaver" selected="">Lowest available</option>

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 1208, Column 45: value of attribute "selected" cannot be ""; must be one of "selected"
    	    		<option value="smartsaver" selected="">Lowest available</option>

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Warning Line 1265, Column 25: character "&" is the first character of a delimiter but occurred as data
    if(recentSearchesCookie && recentSearchesCookie.length > 0){

    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 1265, Column 26: character "&" is the first character of a delimiter but occurred as data
    if(recentSearchesCookie && recentSearchesCookie.length > 0){

    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 1277, Column 13: character "<" is the first character of a delimiter but occurred as data
    if(dateDiff < 1){

    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 1288, Column 45: document type does not allow element "li" here
    listItem += "<li title='" + titleString + "'>";

    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 1313, Column 18: character "<" is the first character of a delimiter but occurred as data
    for(var n = 0; n < searchesInt.length; n++){

    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 1319, Column 23: character "<" is the first character of a delimiter but occurred as data
    if(searchesInt.length < 1){

    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 1337, Column 5: end tag for "ul" which is not finished
    </ul>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 1344, Column 27: duplicate specification of attribute "class"
    <div class="item-0" class="carousel-item">

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

  • Warning Line 1585, Column 104: reference not terminated by REFC delimiter
    …rm=FISD&amp;cursite=www.airnz.com&type=d&range=a&airportcode=LAX" rev="" targe…

    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 1585, Column 104: reference to external entity in attribute value
    …rm=FISD&amp;cursite=www.airnz.com&type=d&range=a&airportcode=LAX" rev="" targe…

    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 1585, Column 104: reference to entity "type" for which no system identifier could be generated
    …rm=FISD&amp;cursite=www.airnz.com&type=d&range=a&airportcode=LAX" rev="" targe…

    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 343, Column 130: entity was defined here
    …ansform=FISD&amp;cursite=www.airnz.com&type=d&range=a&airportcode=LAX" rev="" …
  • Warning Line 1585, Column 112: reference not terminated by REFC delimiter
    …amp;cursite=www.airnz.com&type=d&range=a&airportcode=LAX" rev="" target="_self…

    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 1585, Column 112: reference to external entity in attribute value
    …amp;cursite=www.airnz.com&type=d&range=a&airportcode=LAX" rev="" target="_self…

    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 1585, Column 112: reference to entity "range" for which no system identifier could be generated
    …amp;cursite=www.airnz.com&type=d&range=a&airportcode=LAX" rev="" target="_self…

    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 343, Column 137: entity was defined here
    …=FISD&amp;cursite=www.airnz.com&type=d&range=a&airportcode=LAX" rev="" target=…
  • Warning Line 1585, Column 126: reference not terminated by REFC delimiter
    …w.airnz.com&type=d&range=a&airportcode=LAX" rev="" target="_self" class="" tit…

    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 1585, Column 126: reference to external entity in attribute value
    …w.airnz.com&type=d&range=a&airportcode=LAX" rev="" target="_self" class="" tit…

    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 1585, Column 126: reference to entity "airportcode" for which no system identifier could be generated
    …w.airnz.com&type=d&range=a&airportcode=LAX" rev="" target="_self" class="" tit…

    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 343, Column 145: entity was defined here
    …p;cursite=www.airnz.com&type=d&range=a&airportcode=LAX" rev="" target="_self" …
  • Error Line 1616, Column 34: there is no attribute "aira-label"
    <ul role="navigation" aira-label="Footer Navigation" class="level1">

    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 1942, Column 76: character "&" is the first character of a delimiter but occurred as data
    …/legal-terms" class="floatbox" rev="width:1000">Legal Terms & Privacy</a></li> 

    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 1953, Column 47: cannot generate system identifier for general entity "q"
    …="http://relview.g.mm7.net/g/ue/?e=97&q=2.97.3Jn.2XX.......Y2lkPTExNg%5f%5fBTK…

    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 1953, Column 47: general entity "q" not defined and no default entity
    …="http://relview.g.mm7.net/g/ue/?e=97&q=2.97.3Jn.2XX.......Y2lkPTExNg%5f%5fBTK…

    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 1953, Column 48: reference not terminated by REFC delimiter
    …"http://relview.g.mm7.net/g/ue/?e=97&q=2.97.3Jn.2XX.......Y2lkPTExNg%5f%5fBTKE…

    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 1953, Column 48: reference to external entity in attribute value
    …"http://relview.g.mm7.net/g/ue/?e=97&q=2.97.3Jn.2XX.......Y2lkPTExNg%5f%5fBTKE…

    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 1953, Column 48: reference to entity "q" for which no system identifier could be generated
    …"http://relview.g.mm7.net/g/ue/?e=97&q=2.97.3Jn.2XX.......Y2lkPTExNg%5f%5fBTKE…

    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 1953, Column 46: entity was defined here
    …c="http://relview.g.mm7.net/g/ue/?e=97&q=2.97.3Jn.2XX.......Y2lkPTExNg%5f%5fBT…
  • Warning Line 1953, Column 93: cannot generate system identifier for general entity "ps"
    …Jn.2XX.......Y2lkPTExNg%5f%5fBTKEELW0&ps=HomePage" width="1px" height="1px" bo…

    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 1953, Column 93: general entity "ps" not defined and no default entity
    …Jn.2XX.......Y2lkPTExNg%5f%5fBTKEELW0&ps=HomePage" width="1px" height="1px" bo…

    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 1953, Column 95: reference not terminated by REFC delimiter
    ….2XX.......Y2lkPTExNg%5f%5fBTKEELW0&ps=HomePage" width="1px" height="1px" bord…

    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 1953, Column 95: reference to external entity in attribute value
    ….2XX.......Y2lkPTExNg%5f%5fBTKEELW0&ps=HomePage" width="1px" height="1px" bord…

    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 1953, Column 95: reference to entity "ps" for which no system identifier could be generated
    ….2XX.......Y2lkPTExNg%5f%5fBTKEELW0&ps=HomePage" width="1px" height="1px" bord…

    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 1953, Column 92: entity was defined here
    …3Jn.2XX.......Y2lkPTExNg%5f%5fBTKEELW0&ps=HomePage" width="1px" height="1px" b…
  • Error Line 1954, Column 10: there is no attribute "SRC"
    <IMG SRC="http://bp.specificclick.net?pixid=99002968" width="0" height="0" bord…

    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 1954, Column 61: there is no attribute "width"
    …="http://bp.specificclick.net?pixid=99002968" width="0" height="0" border="0"/>

    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 1954, Column 72: there is no attribute "height"
    …="http://bp.specificclick.net?pixid=99002968" width="0" height="0" border="0"/>

    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 1954, Column 83: there is no attribute "border"
    …="http://bp.specificclick.net?pixid=99002968" width="0" height="0" border="0"/>

    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 1954, Column 87: element "IMG" undefined
    …="http://bp.specificclick.net?pixid=99002968" width="0" height="0" border="0"/>

    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 1956, Column 121: cannot generate system identifier for general entity "bapid"
    …t="1" src="http://bstats.adbrite.com/click/bstats.gif?kid=34918276&bapid=32" />

    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 1956, Column 121: general entity "bapid" not defined and no default entity
    …t="1" src="http://bstats.adbrite.com/click/bstats.gif?kid=34918276&bapid=32" />

    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 1956, Column 126: reference not terminated by REFC delimiter
    …t="1" src="http://bstats.adbrite.com/click/bstats.gif?kid=34918276&bapid=32" />

    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 1956, Column 126: reference to external entity in attribute value
    …t="1" src="http://bstats.adbrite.com/click/bstats.gif?kid=34918276&bapid=32" />

    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 1956, Column 126: reference to entity "bapid" for which no system identifier could be generated
    …t="1" src="http://bstats.adbrite.com/click/bstats.gif?kid=34918276&bapid=32" />

    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 1956, Column 120: entity was defined here
    …t="1" src="http://bstats.adbrite.com/click/bstats.gif?kid=34918276&bapid=32" />
  • Error Line 1956, Column 132: required attribute "alt" not specified
    …t="1" src="http://bstats.adbrite.com/click/bstats.gif?kid=34918276&bapid=32" />

    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 1958, Column 10: there is no attribute "SRC"
    <img SRC="http://pbid.pro-market.net/engine?site=anzhome;size=1x1;mimetype=img"…

    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 1958, Column 113: required attribute "src" not specified
    …et/engine?site=anzhome;size=1x1;mimetype=img" width="0" height="0" border="0"/>

    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 1958, Column 113: required attribute "alt" not specified
    …et/engine?site=anzhome;size=1x1;mimetype=img" width="0" height="0" border="0"/>

    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 1960, Column 54: cannot generate system identifier for general entity "t"
    …mg src="http://ads.bluelithium.com/pixel?id=907358&t=2" width="1" height="1" />

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

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

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

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

  • Error Line 1960, Column 54: general entity "t" not defined and no default entity
    …mg src="http://ads.bluelithium.com/pixel?id=907358&t=2" width="1" height="1" />

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

  • Warning Line 1960, Column 55: reference not terminated by REFC delimiter
    …mg src="http://ads.bluelithium.com/pixel?id=907358&t=2" width="1" height="1" />

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

  • Warning Line 1960, Column 55: reference to external entity in attribute value
    …mg src="http://ads.bluelithium.com/pixel?id=907358&t=2" width="1" height="1" />

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

  • Error Line 1960, Column 55: reference to entity "t" for which no system identifier could be generated
    …mg src="http://ads.bluelithium.com/pixel?id=907358&t=2" width="1" height="1" />

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

  • Info Line 1960, Column 53: entity was defined here
    …mg src="http://ads.bluelithium.com/pixel?id=907358&t=2" width="1" height="1" />
  • Error Line 1960, Column 81: required attribute "alt" not specified
    …mg src="http://ads.bluelithium.com/pixel?id=907358&t=2" width="1" height="1" />

    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 1962, Column 118: required attribute "alt" not specified
    …g.com/Live/Pixel.aspx?PlacementId=49716" border="0" width="1px" height="1px" />

    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 1963, Column 93: required attribute "alt" not specified
    …://idcs.interclick.com/Segment.aspx?sid=7787eb29-6340-4161-8dd7-0d67c15e19bf"/>

    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 1964, Column 139: required attribute "alt" not specified
    …6873;cat1=20769;cat2=20770;rand=[CACHEBUSTER]" width="1" height="1" border="0">

    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 1964, Column 140: end tag for "img" omitted, but OMITTAG NO was specified
    …6873;cat1=20769;cat2=20770;rand=[CACHEBUSTER]" width="1" height="1" border="0">

    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 1964, Column 1: start tag was here
    <img src="http://media.fastclick.net/w/tre?ad_id=24038;evt=16873;cat1=20769;cat…
  • Warning Line 1965, Column 133: cannot generate system identifier for general entity "C"
    …252Fairnewzealand.com%252Faga%26DM_EOM%3D1&C=I11244&L=0" height="1" width="1"/>

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

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

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

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

  • Error Line 1965, Column 133: general entity "C" not defined and no default entity
    …252Fairnewzealand.com%252Faga%26DM_EOM%3D1&C=I11244&L=0" height="1" width="1"/>

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

  • Warning Line 1965, Column 134: reference not terminated by REFC delimiter
    …252Fairnewzealand.com%252Faga%26DM_EOM%3D1&C=I11244&L=0" height="1" width="1"/>

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

  • Warning Line 1965, Column 134: reference to external entity in attribute value
    …252Fairnewzealand.com%252Faga%26DM_EOM%3D1&C=I11244&L=0" height="1" width="1"/>

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

  • Error Line 1965, Column 134: reference to entity "C" for which no system identifier could be generated
    …252Fairnewzealand.com%252Faga%26DM_EOM%3D1&C=I11244&L=0" height="1" width="1"/>

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

  • Info Line 1965, Column 132: entity was defined here
    …252Fairnewzealand.com%252Faga%26DM_EOM%3D1&C=I11244&L=0" height="1" width="1"/>
  • Warning Line 1965, Column 142: cannot generate system identifier for general entity "L"
    …252Fairnewzealand.com%252Faga%26DM_EOM%3D1&C=I11244&L=0" height="1" width="1"/>

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

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

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

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

  • Error Line 1965, Column 142: general entity "L" not defined and no default entity
    …252Fairnewzealand.com%252Faga%26DM_EOM%3D1&C=I11244&L=0" height="1" width="1"/>

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

  • Warning Line 1965, Column 143: reference not terminated by REFC delimiter
    …252Fairnewzealand.com%252Faga%26DM_EOM%3D1&C=I11244&L=0" height="1" width="1"/>

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

  • Warning Line 1965, Column 143: reference to external entity in attribute value
    …252Fairnewzealand.com%252Faga%26DM_EOM%3D1&C=I11244&L=0" height="1" width="1"/>

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

  • Error Line 1965, Column 143: reference to entity "L" for which no system identifier could be generated
    …252Fairnewzealand.com%252Faga%26DM_EOM%3D1&C=I11244&L=0" height="1" width="1"/>

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

  • Info Line 1965, Column 141: entity was defined here
    …252Fairnewzealand.com%252Faga%26DM_EOM%3D1&C=I11244&L=0" height="1" width="1"/>
  • Error Line 1965, Column 168: required attribute "alt" not specified
    …252Fairnewzealand.com%252Faga%26DM_EOM%3D1&C=I11244&L=0" height="1" width="1"/>

    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 1966, Column 120: required attribute "alt" not specified
    …g.com/Live/Pixel.aspx?PlacementId=17075" border="0" width="1px" height="1px" />

    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 1967, Column 118: required attribute "alt" not specified
    …g.com/Live/Pixel.aspx?PlacementId=17075" border="0" width="1px" height="1px" />

    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 1968, Column 87: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …arket.net/engine?site=anzhome;size=1x1;mimetype=img" width=0 height=0 border=0>
  • Error Line 1968, Column 96: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …arket.net/engine?site=anzhome;size=1x1;mimetype=img" width=0 height=0 border=0>
  • Error Line 1968, Column 105: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …arket.net/engine?site=anzhome;size=1x1;mimetype=img" width=0 height=0 border=0>
  • Error Line 1968, Column 106: required attribute "alt" not specified
    …arket.net/engine?site=anzhome;size=1x1;mimetype=img" width=0 height=0 border=0>

    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 1968, Column 107: end tag for "img" omitted, but OMITTAG NO was specified
    …arket.net/engine?site=anzhome;size=1x1;mimetype=img" width=0 height=0 border=0>

    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 1968, Column 1: start tag was here
    <img src="http://pbid.pro-market.net/engine?site=anzhome;size=1x1;mimetype=img"…
  • Warning Line 1971, Column 77: cannot generate system identifier for general entity "p"
    …avascript" src="http://tag.yieldoptimizer.com/ps/ps?t=s&p=1234&pg=hp"></script>

    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 1971, Column 77: general entity "p" not defined and no default entity
    …avascript" src="http://tag.yieldoptimizer.com/ps/ps?t=s&p=1234&pg=hp"></script>

    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 1971, Column 78: reference not terminated by REFC delimiter
    …avascript" src="http://tag.yieldoptimizer.com/ps/ps?t=s&p=1234&pg=hp"></script>

    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 1971, Column 78: reference to external entity in attribute value
    …avascript" src="http://tag.yieldoptimizer.com/ps/ps?t=s&p=1234&pg=hp"></script>

    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 1971, Column 78: reference to entity "p" for which no system identifier could be generated
    …avascript" src="http://tag.yieldoptimizer.com/ps/ps?t=s&p=1234&pg=hp"></script>

    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 1971, Column 76: entity was defined here
    …avascript" src="http://tag.yieldoptimizer.com/ps/ps?t=s&p=1234&pg=hp"></script>
  • Warning Line 1971, Column 84: cannot generate system identifier for general entity "pg"
    …avascript" src="http://tag.yieldoptimizer.com/ps/ps?t=s&p=1234&pg=hp"></script>

    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 1971, Column 84: general entity "pg" not defined and no default entity
    …avascript" src="http://tag.yieldoptimizer.com/ps/ps?t=s&p=1234&pg=hp"></script>

    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 1971, Column 86: reference not terminated by REFC delimiter
    …avascript" src="http://tag.yieldoptimizer.com/ps/ps?t=s&p=1234&pg=hp"></script>

    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 1971, Column 86: reference to external entity in attribute value
    …avascript" src="http://tag.yieldoptimizer.com/ps/ps?t=s&p=1234&pg=hp"></script>

    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 1971, Column 86: reference to entity "pg" for which no system identifier could be generated
    …avascript" src="http://tag.yieldoptimizer.com/ps/ps?t=s&p=1234&pg=hp"></script>

    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 1971, Column 83: entity was defined here
    …avascript" src="http://tag.yieldoptimizer.com/ps/ps?t=s&p=1234&pg=hp"></script>
  • Warning Line 2000, Column 139: cannot generate system identifier for general entity "cid"
    …BHmCip7C5OrYioOZAZxV1s6vxNl8Fn3WBB_xdvKRV4iJ5zDYlNjRrxEpfZgQjhXFEVOnmq9Q&cid=">

    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 2000, Column 139: general entity "cid" not defined and no default entity
    …BHmCip7C5OrYioOZAZxV1s6vxNl8Fn3WBB_xdvKRV4iJ5zDYlNjRrxEpfZgQjhXFEVOnmq9Q&cid=">

    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 2000, Column 142: reference not terminated by REFC delimiter
    …BHmCip7C5OrYioOZAZxV1s6vxNl8Fn3WBB_xdvKRV4iJ5zDYlNjRrxEpfZgQjhXFEVOnmq9Q&cid=">

    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 2000, Column 142: reference to external entity in attribute value
    …BHmCip7C5OrYioOZAZxV1s6vxNl8Fn3WBB_xdvKRV4iJ5zDYlNjRrxEpfZgQjhXFEVOnmq9Q&cid=">

    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 2000, Column 142: reference to entity "cid" for which no system identifier could be generated
    …BHmCip7C5OrYioOZAZxV1s6vxNl8Fn3WBB_xdvKRV4iJ5zDYlNjRrxEpfZgQjhXFEVOnmq9Q&cid=">

    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 2000, Column 138: entity was defined here
    …BHmCip7C5OrYioOZAZxV1s6vxNl8Fn3WBB_xdvKRV4iJ5zDYlNjRrxEpfZgQjhXFEVOnmq9Q&cid=">
  • Error Line 2000, Column 144: required attribute "alt" not specified
    …BHmCip7C5OrYioOZAZxV1s6vxNl8Fn3WBB_xdvKRV4iJ5zDYlNjRrxEpfZgQjhXFEVOnmq9Q&cid=">

    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 2000, Column 145: end tag for "img" omitted, but OMITTAG NO was specified
    …BHmCip7C5OrYioOZAZxV1s6vxNl8Fn3WBB_xdvKRV4iJ5zDYlNjRrxEpfZgQjhXFEVOnmq9Q&cid=">

    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 2000, Column 1: start tag was here
    <img border="0" src="http://r.turn.com/r/beacon?b2=nj-rP9KX2CGSmoBHmCip7C5OrYio…
  • Warning Line 2004, Column 56: reference not terminated by REFC delimiter
    …g src="http://ads.bluelithium.com/pixel?id=1648629&t=2" width="1" height="1" />

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

  • Warning Line 2004, Column 56: reference to external entity in attribute value
    …g src="http://ads.bluelithium.com/pixel?id=1648629&t=2" width="1" height="1" />

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

  • Error Line 2004, Column 56: reference to entity "t" for which no system identifier could be generated
    …g src="http://ads.bluelithium.com/pixel?id=1648629&t=2" width="1" height="1" />

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

  • Info Line 1960, Column 53: entity was defined here
    …mg src="http://ads.bluelithium.com/pixel?id=907358&t=2" width="1" height="1" />
  • Error Line 2004, Column 82: required attribute "alt" not specified
    …g src="http://ads.bluelithium.com/pixel?id=1648629&t=2" width="1" height="1" />

    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 2016, Column 142: reference not terminated by REFC delimiter
    …yhrdpfbpNmd34hTqb5Sv73nL81cj9n3WBB_xdvKRV4iJ5zDYlN0FILomEqUie6b3XEjIK_gQ&cid=">

    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 2016, Column 142: reference to external entity in attribute value
    …yhrdpfbpNmd34hTqb5Sv73nL81cj9n3WBB_xdvKRV4iJ5zDYlN0FILomEqUie6b3XEjIK_gQ&cid=">

    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 2016, Column 142: reference to entity "cid" for which no system identifier could be generated
    …yhrdpfbpNmd34hTqb5Sv73nL81cj9n3WBB_xdvKRV4iJ5zDYlN0FILomEqUie6b3XEjIK_gQ&cid=">

    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 2000, Column 138: entity was defined here
    …BHmCip7C5OrYioOZAZxV1s6vxNl8Fn3WBB_xdvKRV4iJ5zDYlNjRrxEpfZgQjhXFEVOnmq9Q&cid=">
  • Error Line 2016, Column 144: required attribute "alt" not specified
    …yhrdpfbpNmd34hTqb5Sv73nL81cj9n3WBB_xdvKRV4iJ5zDYlN0FILomEqUie6b3XEjIK_gQ&cid=">

    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 2016, Column 145: end tag for "img" omitted, but OMITTAG NO was specified
    …yhrdpfbpNmd34hTqb5Sv73nL81cj9n3WBB_xdvKRV4iJ5zDYlN0FILomEqUie6b3XEjIK_gQ&cid=">

    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 2016, Column 1: start tag was here
    <img border="0" src="http://r.turn.com/r/beacon?b2=fBT8N8K4ijucY_yhrdpfbpNmd34h…
  • Warning Line 2038, Column 119: cannot generate system identifier for general entity "_pid"
    …t="1" src="https://stats.adbrite.com/stats/stats.gif?_uid=247948&_pid=14718" />

    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 2038, Column 119: general entity "_pid" not defined and no default entity
    …t="1" src="https://stats.adbrite.com/stats/stats.gif?_uid=247948&_pid=14718" />

    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 2038, Column 123: reference not terminated by REFC delimiter
    …t="1" src="https://stats.adbrite.com/stats/stats.gif?_uid=247948&_pid=14718" />

    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 2038, Column 123: reference to external entity in attribute value
    …t="1" src="https://stats.adbrite.com/stats/stats.gif?_uid=247948&_pid=14718" />

    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 2038, Column 123: reference to entity "_pid" for which no system identifier could be generated
    …t="1" src="https://stats.adbrite.com/stats/stats.gif?_uid=247948&_pid=14718" />

    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 2038, Column 118: entity was defined here
    …t="1" src="https://stats.adbrite.com/stats/stats.gif?_uid=247948&_pid=14718" />
  • Error Line 2038, Column 132: required attribute "alt" not specified
    …t="1" src="https://stats.adbrite.com/stats/stats.gif?_uid=247948&_pid=14718" />

    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 2040, Column 8: required attribute "type" not specified
    <script>document.write('<s'+'cript language="JavaScript" src="http://view.atdmt…

    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 2040, Column 27: an attribute specification must start with a name or name token
    <script>document.write('<s'+'cript language="JavaScript" src="http://view.atdmt…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 2040, Column 27: document type does not allow element "s" here
    <script>document.write('<s'+'cript language="JavaScript" src="http://view.atdmt…

    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 2040, Column 138: delimiter "'" invalid: only S separators and TAGC allowed here
    …AirNewZealandLandingPageUAT2012_1"></s'+'cript>')</script><noscript><iframe sr…
  • Error Line 2040, Column 303: value of attribute "scrolling" cannot be "No"; must be one of "yes", "no", "auto"
    …ight="1" frameborder="0" scrolling="No" marginheight="0" marginwidth="0" topma…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 2040, Column 348: there is no attribute "topmargin"
    …ginheight="0" marginwidth="0" topmargin="0" leftmargin="0"></iframe></noscript>

    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 2040, Column 363: there is no attribute "leftmargin"
    …ginheight="0" marginwidth="0" topmargin="0" leftmargin="0"></iframe></noscript>

    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 2095, Column 78: reference not terminated by REFC delimiter
    …avascript" src="http://tag.yieldoptimizer.com/ps/ps?t=s&p=1234&pg=hp"></script>

    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 2095, Column 78: reference to external entity in attribute value
    …avascript" src="http://tag.yieldoptimizer.com/ps/ps?t=s&p=1234&pg=hp"></script>

    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 2095, Column 78: reference to entity "p" for which no system identifier could be generated
    …avascript" src="http://tag.yieldoptimizer.com/ps/ps?t=s&p=1234&pg=hp"></script>

    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 1971, Column 76: entity was defined here
    …avascript" src="http://tag.yieldoptimizer.com/ps/ps?t=s&p=1234&pg=hp"></script>
  • Warning Line 2095, Column 86: reference not terminated by REFC delimiter
    …avascript" src="http://tag.yieldoptimizer.com/ps/ps?t=s&p=1234&pg=hp"></script>

    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 2095, Column 86: reference to external entity in attribute value
    …avascript" src="http://tag.yieldoptimizer.com/ps/ps?t=s&p=1234&pg=hp"></script>

    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 2095, Column 86: reference to entity "pg" for which no system identifier could be generated
    …avascript" src="http://tag.yieldoptimizer.com/ps/ps?t=s&p=1234&pg=hp"></script>

    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 1971, Column 83: entity was defined here
    …avascript" src="http://tag.yieldoptimizer.com/ps/ps?t=s&p=1234&pg=hp"></script>
  • Warning Line 284, Column 29: reference to non-existent ID "ft-email-address"
    <label class="infield" for="ft-email-address"> <span>Email address</span>

    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 1532, Column 29: reference to non-existent ID "ft-email-address"
    <label class="infield" for="ft-email-address"> <span>Email address</span>

    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 196, Column 29: reference to non-existent ID "ft-family-name"
    <label class="infield" for="ft-family-name"> <span>Family name</span>

    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 223, Column 29: reference to non-existent ID "ft-family-name"
    <label class="infield" for="ft-family-name"> <span>Family name</span>

    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 251, Column 29: reference to non-existent ID "ft-family-name"
    <label class="infield" for="ft-family-name"> <span>Family name</span>

    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 279, Column 29: reference to non-existent ID "ft-family-name"
    <label class="infield" for="ft-family-name"> <span>Family name</span>

    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 312, Column 29: reference to non-existent ID "ft-family-name"
    <label class="infield" for="ft-family-name"> <span>Family name</span>

    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 1444, Column 29: reference to non-existent ID "ft-family-name"
    <label class="infield" for="ft-family-name"> <span>Family name</span>

    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 1471, Column 29: reference to non-existent ID "ft-family-name"
    <label class="infield" for="ft-family-name"> <span>Family name</span>

    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 1499, Column 29: reference to non-existent ID "ft-family-name"
    <label class="infield" for="ft-family-name"> <span>Family name</span>

    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 1527, Column 29: reference to non-existent ID "ft-family-name"
    <label class="infield" for="ft-family-name"> <span>Family name</span>

    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 1560, Column 29: reference to non-existent ID "ft-family-name"
    <label class="infield" for="ft-family-name"> <span>Family name</span>

    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 191, Column 29: reference to non-existent ID "ft-booking-reference"
    <label class="infield" for="ft-booking-reference"> <span>Booking reference</spa…

    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 218, Column 29: reference to non-existent ID "ft-booking-reference"
    <label class="infield" for="ft-booking-reference"> <span>Booking reference</spa…

    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 246, Column 29: reference to non-existent ID "ft-booking-reference"
    <label class="infield" for="ft-booking-reference"> <span>Booking reference</spa…

    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 274, Column 29: reference to non-existent ID "ft-booking-reference"
    <label class="infield" for="ft-booking-reference"> <span>Booking reference</spa…

    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 307, Column 29: reference to non-existent ID "ft-booking-reference"
    <label class="infield" for="ft-booking-reference"> <span>Booking reference</spa…

    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 1439, Column 29: reference to non-existent ID "ft-booking-reference"
    <label class="infield" for="ft-booking-reference"> <span>Booking reference</spa…

    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 1466, Column 29: reference to non-existent ID "ft-booking-reference"
    <label class="infield" for="ft-booking-reference"> <span>Booking reference</spa…

    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 1494, Column 29: reference to non-existent ID "ft-booking-reference"
    <label class="infield" for="ft-booking-reference"> <span>Booking reference</spa…

    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 1522, Column 29: reference to non-existent ID "ft-booking-reference"
    <label class="infield" for="ft-booking-reference"> <span>Booking reference</spa…

    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 1555, Column 29: reference to non-existent ID "ft-booking-reference"
    <label class="infield" for="ft-booking-reference"> <span>Booking reference</spa…

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