HOME BUSINESS TRAVEL TECHNOLOGY NEWS Hot News Anastacia cancels tour after cancer diagnosis DUBAI, United Arab Emirates (AP) — Managers for U.S. pop singer Anastacia say she has canceled a planned performance in ...

anchorfree.net
  • Domain Name
    anchorfree.net
  • Favicon
  • Google Page Rank
    1
  • Alexa Rank
    #7201
  • Page Size
    26.5 KB
  • Ip Address
    68.68.107.69
  • Heading
    H1: 6, H2: 12, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    2 GIF, 7 JPG, 2 PNG

Website Meta Analysis

  • Title
    Anchorfree
  • Meta Keyword
  • Meta Description
    HOME BUSINESS TRAVEL TECHNOLOGY NEWS Hot News Anastacia cancels tour after cancer diagnosis DUBAI, United Arab Emirates (AP) — Managers for U.S. pop singer Anastacia say she has canceled a planned performance in Dubai and an upcoming European ...

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    68.68.107.69
  • Domain Age
    8 Years, 0 Months, 2 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from anchorfree.net.

HTML Analysis

  • date: Thu, 28 Feb 2013 14:01:54 GMT
  • server: Apache
  • content-encoding: gzip
  • vary: Accept-Encoding
  • cache-control: max-age=600
  • expires: Thu, 28 Feb 2013 14:11:54 GMT
  • content-length: 7717
  • content-type: text/html; charset=UTF-8
  • connection: close
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for anchorfree.net

DNS Analysis


DNS servers
ns1.anchorfree.com [74.115.4.111]
ns2.anchorfree.com [107.1.93.200]


DNS Records

Answer records
anchorfree.net SOA
server: ns1.anchorfree.com
email: monitor@anchorfree.com
serial: 2012122101
refresh: 28800
retry: 7200
expire: 2419200
minimum ttl: 86400
86400s
anchorfree.net NS  ns1.anchorfree.com 86400s
anchorfree.net NS  ns2.anchorfree.com 86400s
anchorfree.net MX
preference: 10
exchange: web1.anchorfree.net
86400s
anchorfree.net TXT AnchorFree Inc. 86400s
anchorfree.net A 68.68.107.69 86400s

Authority records

Additional records
ns1.anchorfree.com A 74.115.4.111 3600s
ns2.anchorfree.com A 107.1.93.200 3600s
web1.anchorfree.net A 74.115.4.219 86400s

IP 68.68.107.69 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • No whois ip data for 68.68.107.69

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 108 Errors
  • 117 Warnings
Ratio Text/Html
  • 0.6453456221198157
Message Error
  • Error Line 22, Column 96: value of attribute "method" cannot be "GET"; must be one of "get", "post"
    …search.hotspotshield.com/land/results.php" method="GET" accept-charset="UTF-8">

    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 23, Column 51: there is no attribute "autocomplete"
    …lass="search_form_input" autocomplete="off" type="text" name="q" id="q" size="…

    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 23, Column 121: end tag for "input" omitted, but OMITTAG NO was specified
    …complete="off" type="text" name="q" id="q" size="51" maxlength="2048" value="">

    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 23, Column 5: start tag was here
    	 		<input class="search_form_input" autocomplete="off" type="text" name="q" id…
  • Error Line 24, Column 50: end tag for "input" omitted, but OMITTAG NO was specified
    	 		<input type="hidden" value="903" name="askt">

    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 24, Column 5: start tag was here
    	 		<input type="hidden" value="903" name="askt">
  • Error Line 25, Column 58: end tag for "input" omitted, but OMITTAG NO was specified
    	 		<input type="hidden" value="UNREGISTERED" name="tag">

    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 25, Column 5: start tag was here
    	 		<input type="hidden" value="UNREGISTERED" name="tag">
  • Error Line 26, Column 69: end tag for "input" omitted, but OMITTAG NO was specified
    	 		<input class="search_form_submit" type="submit" value="SEARCH" >

    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 26, Column 5: start tag was here
    	 		<input class="search_form_submit" type="submit" value="SEARCH" >
  • Warning Line 49, Column 96: cannot generate system identifier for general entity "tag"
    …arch.com/delivery/afrlg.php?zoneid=94&tag=UNREGISTERED&cnl=empty&afhss=UNDEFIN…

    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 49, Column 96: general entity "tag" not defined and no default entity
    …arch.com/delivery/afrlg.php?zoneid=94&tag=UNREGISTERED&cnl=empty&afhss=UNDEFIN…

    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 49, Column 99: reference not terminated by REFC delimiter
    …h.com/delivery/afrlg.php?zoneid=94&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&…

    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 49, Column 99: reference to external entity in attribute value
    …h.com/delivery/afrlg.php?zoneid=94&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&…

    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 49, Column 99: reference to entity "tag" for which no system identifier could be generated
    …h.com/delivery/afrlg.php?zoneid=94&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&…

    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 49, Column 95: entity was defined here
    …earch.com/delivery/afrlg.php?zoneid=94&tag=UNREGISTERED&cnl=empty&afhss=UNDEFI…
  • Warning Line 49, Column 113: cannot generate system identifier for general entity "cnl"
    …/afrlg.php?zoneid=94&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812…

    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 49, Column 113: general entity "cnl" not defined and no default entity
    …/afrlg.php?zoneid=94&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812…

    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 49, Column 116: reference not terminated by REFC delimiter
    …rlg.php?zoneid=94&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&ca…

    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 49, Column 116: reference to external entity in attribute value
    …rlg.php?zoneid=94&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&ca…

    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 49, Column 116: reference to entity "cnl" for which no system identifier could be generated
    …rlg.php?zoneid=94&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&ca…

    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 49, Column 112: entity was defined here
    …y/afrlg.php?zoneid=94&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=323223881…
  • Warning Line 49, Column 123: cannot generate system identifier for general entity "afhss"
    …?zoneid=94&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&a…

    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 49, Column 123: general entity "afhss" not defined and no default entity
    …?zoneid=94&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&a…

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

  • Warning Line 49, Column 128: reference not terminated by REFC delimiter
    …id=94&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=d…

    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 49, Column 128: reference to external entity in attribute value
    …id=94&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=d…

    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 49, Column 128: reference to entity "afhss" for which no system identifier could be generated
    …id=94&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=d…

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

  • Info Line 49, Column 122: entity was defined here
    …p?zoneid=94&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&…
  • Warning Line 49, Column 139: cannot generate system identifier for general entity "sip"
    …NREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_if…

    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 49, Column 139: general entity "sip" not defined and no default entity
    …NREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_if…

    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 49, Column 142: reference not terminated by REFC delimiter
    …GISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_ifram…

    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 49, Column 142: reference to external entity in attribute value
    …GISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_ifram…

    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 49, Column 142: reference to entity "sip" for which no system identifier could be generated
    …GISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_ifram…

    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 49, Column 138: entity was defined here
    …UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_i…
  • Warning Line 49, Column 154: cannot generate system identifier for general entity "cat"
    …=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=…

    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 49, Column 154: general entity "cat" not defined and no default entity
    …=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=…

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

  • Warning Line 49, Column 157: reference not terminated by REFC delimiter
    …pty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anc…

    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 49, Column 157: reference to external entity in attribute value
    …pty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anc…

    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 49, Column 157: reference to entity "cat" for which no system identifier could be generated
    …pty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anc…

    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 49, Column 153: entity was defined here
    …l=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc…
  • Warning Line 49, Column 162: cannot generate system identifier for general entity "affr"
    …fhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anchorfr…

    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 49, Column 162: general entity "affr" not defined and no default entity
    …fhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anchorfr…

    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 49, Column 166: reference not terminated by REFC delimiter
    …=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anchorfree.n…

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

  • Warning Line 49, Column 166: reference to external entity in attribute value
    …=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anchorfree.n…

    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 49, Column 166: reference to entity "affr" for which no system identifier could be generated
    …=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anchorfree.n…

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

  • Info Line 49, Column 161: entity was defined here
    …afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anchorf…
  • Warning Line 49, Column 190: cannot generate system identifier for general entity "loc"
    …2&cat=11K&affr=displayed_iframe_primo&loc=anchorfree.net&referer=empty' frameb…

    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 49, Column 190: general entity "loc" not defined and no default entity
    …2&cat=11K&affr=displayed_iframe_primo&loc=anchorfree.net&referer=empty' frameb…

    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 49, Column 193: reference not terminated by REFC delimiter
    …at=11K&affr=displayed_iframe_primo&loc=anchorfree.net&referer=empty' framebord…

    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 49, Column 193: reference to external entity in attribute value
    …at=11K&affr=displayed_iframe_primo&loc=anchorfree.net&referer=empty' framebord…

    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 49, Column 193: reference to entity "loc" for which no system identifier could be generated
    …at=11K&affr=displayed_iframe_primo&loc=anchorfree.net&referer=empty' framebord…

    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 49, Column 189: entity was defined here
    …12&cat=11K&affr=displayed_iframe_primo&loc=anchorfree.net&referer=empty' frame…
  • Warning Line 49, Column 209: cannot generate system identifier for general entity "referer"
    …layed_iframe_primo&loc=anchorfree.net&referer=empty' frameborder='0' scrolling…

    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 49, Column 209: general entity "referer" not defined and no default entity
    …layed_iframe_primo&loc=anchorfree.net&referer=empty' frameborder='0' scrolling…

    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 49, Column 216: reference not terminated by REFC delimiter
    …frame_primo&loc=anchorfree.net&referer=empty' frameborder='0' scrolling='no' w…

    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 49, Column 216: reference to external entity in attribute value
    …frame_primo&loc=anchorfree.net&referer=empty' frameborder='0' scrolling='no' w…

    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 49, Column 216: reference to entity "referer" for which no system identifier could be generated
    …frame_primo&loc=anchorfree.net&referer=empty' frameborder='0' scrolling='no' w…

    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 49, Column 208: entity was defined here
    …played_iframe_primo&loc=anchorfree.net&referer=empty' frameborder='0' scrollin…
  • Error Line 53, Column 68: value of attribute "frameborder" cannot be "no"; must be one of "1", "0"
    …ling="no" height="520" frameborder="no" allowtransparency="true" framespacing=…

    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 53, Column 88: there is no attribute "allowtransparency"
    …0" frameborder="no" allowtransparency="true" framespacing="0" scrolling="No"  …

    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 53, Column 108: there is no attribute "framespacing"
    …allowtransparency="true" framespacing="0" scrolling="No"  src="http://delivery…

    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 53, Column 122: duplicate specification of attribute "scrolling"
    …ncy="true" framespacing="0" scrolling="No"  src="http://delivery.anchorfree.us…

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

  • Error Line 53, Column 125: value of attribute "scrolling" cannot be "No"; must be one of "yes", "no", "auto"
    …="true" framespacing="0" scrolling="No"  src="http://delivery.anchorfree.us/pl…

    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 53, Column 193: reference not terminated by REFC delimiter
    …free.us/player-multi.php?zoneid=98&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&…

    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 53, Column 193: reference to external entity in attribute value
    …free.us/player-multi.php?zoneid=98&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&…

    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 53, Column 193: reference to entity "tag" for which no system identifier could be generated
    …free.us/player-multi.php?zoneid=98&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&…

    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 49, Column 95: entity was defined here
    …earch.com/delivery/afrlg.php?zoneid=94&tag=UNREGISTERED&cnl=empty&afhss=UNDEFI…
  • Warning Line 53, Column 210: reference not terminated by REFC delimiter
    …lti.php?zoneid=98&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&ca…

    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 53, Column 210: reference to external entity in attribute value
    …lti.php?zoneid=98&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&ca…

    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 53, Column 210: reference to entity "cnl" for which no system identifier could be generated
    …lti.php?zoneid=98&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&ca…

    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 49, Column 112: entity was defined here
    …y/afrlg.php?zoneid=94&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=323223881…
  • Warning Line 53, Column 222: reference not terminated by REFC delimiter
    …id=98&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=d…

    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 53, Column 222: reference to external entity in attribute value
    …id=98&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=d…

    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 53, Column 222: reference to entity "afhss" for which no system identifier could be generated
    …id=98&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=d…

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

  • Info Line 49, Column 122: entity was defined here
    …p?zoneid=94&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&…
  • Warning Line 53, Column 236: reference not terminated by REFC delimiter
    …GISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_ifram…

    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 53, Column 236: reference to external entity in attribute value
    …GISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_ifram…

    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 53, Column 236: reference to entity "sip" for which no system identifier could be generated
    …GISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_ifram…

    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 49, Column 138: entity was defined here
    …UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_i…
  • Warning Line 53, Column 251: reference not terminated by REFC delimiter
    …pty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anc…

    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 53, Column 251: reference to external entity in attribute value
    …pty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anc…

    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 53, Column 251: reference to entity "cat" for which no system identifier could be generated
    …pty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anc…

    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 49, Column 153: entity was defined here
    …l=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc…
  • Warning Line 53, Column 260: reference not terminated by REFC delimiter
    …=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anchorfree.n…

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

  • Warning Line 53, Column 260: reference to external entity in attribute value
    …=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anchorfree.n…

    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 53, Column 260: reference to entity "affr" for which no system identifier could be generated
    …=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anchorfree.n…

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

  • Info Line 49, Column 161: entity was defined here
    …afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anchorf…
  • Warning Line 53, Column 287: reference not terminated by REFC delimiter
    …at=11K&affr=displayed_iframe_primo&loc=anchorfree.net&referer=empty" name="a22…

    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 53, Column 287: reference to external entity in attribute value
    …at=11K&affr=displayed_iframe_primo&loc=anchorfree.net&referer=empty" name="a22…

    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 53, Column 287: reference to entity "loc" for which no system identifier could be generated
    …at=11K&affr=displayed_iframe_primo&loc=anchorfree.net&referer=empty" name="a22…

    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 49, Column 189: entity was defined here
    …12&cat=11K&affr=displayed_iframe_primo&loc=anchorfree.net&referer=empty' frame…
  • Warning Line 53, Column 310: reference not terminated by REFC delimiter
    …frame_primo&loc=anchorfree.net&referer=empty" name="a220c995" id="a220c995" cl…

    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 53, Column 310: reference to external entity in attribute value
    …frame_primo&loc=anchorfree.net&referer=empty" name="a220c995" id="a220c995" cl…

    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 53, Column 310: reference to entity "referer" for which no system identifier could be generated
    …frame_primo&loc=anchorfree.net&referer=empty" name="a220c995" id="a220c995" cl…

    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 49, Column 208: entity was defined here
    …played_iframe_primo&loc=anchorfree.net&referer=empty' frameborder='0' scrollin…
  • Error Line 54, Column 68: value of attribute "frameborder" cannot be "no"; must be one of "1", "0"
    …ling="no" height="250" frameborder="no" allowtransparency="true" framespacing=…

    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 54, Column 172: reference not terminated by REFC delimiter
    ….com/delivery/afrlg.php?zoneid=313&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&…

    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 54, Column 172: reference to external entity in attribute value
    ….com/delivery/afrlg.php?zoneid=313&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&…

    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 54, Column 172: reference to entity "tag" for which no system identifier could be generated
    ….com/delivery/afrlg.php?zoneid=313&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&…

    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 49, Column 95: entity was defined here
    …earch.com/delivery/afrlg.php?zoneid=94&tag=UNREGISTERED&cnl=empty&afhss=UNDEFI…
  • Warning Line 54, Column 189: reference not terminated by REFC delimiter
    …lg.php?zoneid=313&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&ca…

    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 54, Column 189: reference to external entity in attribute value
    …lg.php?zoneid=313&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&ca…

    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 54, Column 189: reference to entity "cnl" for which no system identifier could be generated
    …lg.php?zoneid=313&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&ca…

    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 49, Column 112: entity was defined here
    …y/afrlg.php?zoneid=94&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=323223881…
  • Warning Line 54, Column 201: reference not terminated by REFC delimiter
    …d=313&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=d…

    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 54, Column 201: reference to external entity in attribute value
    …d=313&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=d…

    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 54, Column 201: reference to entity "afhss" for which no system identifier could be generated
    …d=313&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=d…

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

  • Info Line 49, Column 122: entity was defined here
    …p?zoneid=94&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&…
  • Warning Line 54, Column 215: reference not terminated by REFC delimiter
    …GISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_ifram…

    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 54, Column 215: reference to external entity in attribute value
    …GISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_ifram…

    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 54, Column 215: reference to entity "sip" for which no system identifier could be generated
    …GISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_ifram…

    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 49, Column 138: entity was defined here
    …UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_i…
  • Warning Line 54, Column 230: reference not terminated by REFC delimiter
    …pty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anc…

    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 54, Column 230: reference to external entity in attribute value
    …pty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anc…

    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 54, Column 230: reference to entity "cat" for which no system identifier could be generated
    …pty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anc…

    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 49, Column 153: entity was defined here
    …l=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc…
  • Warning Line 54, Column 239: reference not terminated by REFC delimiter
    …=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anchorfree.n…

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

  • Warning Line 54, Column 239: reference to external entity in attribute value
    …=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anchorfree.n…

    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 54, Column 239: reference to entity "affr" for which no system identifier could be generated
    …=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anchorfree.n…

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

  • Info Line 49, Column 161: entity was defined here
    …afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anchorf…
  • Warning Line 54, Column 266: reference not terminated by REFC delimiter
    …at=11K&affr=displayed_iframe_primo&loc=anchorfree.net&referer=empty" name="a22…

    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 54, Column 266: reference to external entity in attribute value
    …at=11K&affr=displayed_iframe_primo&loc=anchorfree.net&referer=empty" name="a22…

    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 54, Column 266: reference to entity "loc" for which no system identifier could be generated
    …at=11K&affr=displayed_iframe_primo&loc=anchorfree.net&referer=empty" name="a22…

    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 49, Column 189: entity was defined here
    …12&cat=11K&affr=displayed_iframe_primo&loc=anchorfree.net&referer=empty' frame…
  • Warning Line 54, Column 289: reference not terminated by REFC delimiter
    …frame_primo&loc=anchorfree.net&referer=empty" name="a220c995" id="a220c995" cl…

    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 54, Column 289: reference to external entity in attribute value
    …frame_primo&loc=anchorfree.net&referer=empty" name="a220c995" id="a220c995" cl…

    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 54, Column 289: reference to entity "referer" for which no system identifier could be generated
    …frame_primo&loc=anchorfree.net&referer=empty" name="a220c995" id="a220c995" cl…

    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 49, Column 208: entity was defined here
    …played_iframe_primo&loc=anchorfree.net&referer=empty' frameborder='0' scrollin…
  • Error Line 54, Column 317: ID "a220c995" already defined
    …ree.net&referer=empty" name="a220c995" id="a220c995" class="left_adv"></iframe>

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

  • Info Line 53, Column 338: ID "a220c995" first defined here
    …ree.net&referer=empty" name="a220c995" id="a220c995" class="left_adv"></iframe>
  • Error Line 62, Column 2184: required attribute "alt" not specified
    …'><img src='images/morenews_btn.jpg' /></a></div></div>			</div><div class="rb…

    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 68, Column 120: required attribute "alt" not specified
    …Free" ><img src="images/facebook-logo.png" style="border:0px;margin:5px" /></a>

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

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

  • Error Line 69, Column 118: required attribute "alt" not specified
    …e" ><img src="images/twitter-logo.gif" style="border:0px;margin:5px 0px" /></a>

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

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

  • Error Line 70, Column 105: required attribute "alt" not specified
    …hield.com" ><img src="images/hss-logo.gif" style="border:0px;margin:5px" /></a>

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

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

  • Error Line 71, Column 356: there is no attribute "allowTransparency"
    …overflow:hidden; width:150px; height:60px;" allowTransparency="true"></iframe> 

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

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

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

  • Error Line 73, Column 209: required attribute "alt" not specified
    …9" src="http://www.anchorfree.com/assets/images/HSS_for_iphone.png"></a></div>	

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

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

  • Error Line 73, Column 213: end tag for "img" omitted, but OMITTAG NO was specified
    …9" src="http://www.anchorfree.com/assets/images/HSS_for_iphone.png"></a></div>	

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

  • Info Line 73, Column 105: start tag was here
    …hotspotshield.com/clientless/iphone/"><img height="34" border="0" width="159" …
  • Error Line 75, Column 80: there is no attribute "hspace"
    …height="600px" frameborder="0" hspace="0" vspace="0" marginheight="0" marginwi…

    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 75, Column 91: there is no attribute "vspace"
    …px" frameborder="0" hspace="0" vspace="0" marginheight="0" marginwidth="0" src…

    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 75, Column 188: reference not terminated by REFC delimiter
    ….com/delivery/afrlg.php?zoneid=124&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&…

    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 75, Column 188: reference to external entity in attribute value
    ….com/delivery/afrlg.php?zoneid=124&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&…

    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 75, Column 188: reference to entity "tag" for which no system identifier could be generated
    ….com/delivery/afrlg.php?zoneid=124&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&…

    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 49, Column 95: entity was defined here
    …earch.com/delivery/afrlg.php?zoneid=94&tag=UNREGISTERED&cnl=empty&afhss=UNDEFI…
  • Warning Line 75, Column 205: reference not terminated by REFC delimiter
    …lg.php?zoneid=124&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&ca…

    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 75, Column 205: reference to external entity in attribute value
    …lg.php?zoneid=124&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&ca…

    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 75, Column 205: reference to entity "cnl" for which no system identifier could be generated
    …lg.php?zoneid=124&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&ca…

    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 49, Column 112: entity was defined here
    …y/afrlg.php?zoneid=94&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=323223881…
  • Warning Line 75, Column 217: reference not terminated by REFC delimiter
    …d=124&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=d…

    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 75, Column 217: reference to external entity in attribute value
    …d=124&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=d…

    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 75, Column 217: reference to entity "afhss" for which no system identifier could be generated
    …d=124&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=d…

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

  • Info Line 49, Column 122: entity was defined here
    …p?zoneid=94&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&…
  • Warning Line 75, Column 231: reference not terminated by REFC delimiter
    …GISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_ifram…

    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 75, Column 231: reference to external entity in attribute value
    …GISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_ifram…

    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 75, Column 231: reference to entity "sip" for which no system identifier could be generated
    …GISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_ifram…

    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 49, Column 138: entity was defined here
    …UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_i…
  • Warning Line 75, Column 246: reference not terminated by REFC delimiter
    …pty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anc…

    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 75, Column 246: reference to external entity in attribute value
    …pty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anc…

    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 75, Column 246: reference to entity "cat" for which no system identifier could be generated
    …pty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anc…

    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 49, Column 153: entity was defined here
    …l=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc…
  • Warning Line 75, Column 255: reference not terminated by REFC delimiter
    …=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anchorfree.n…

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

  • Warning Line 75, Column 255: reference to external entity in attribute value
    …=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anchorfree.n…

    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 75, Column 255: reference to entity "affr" for which no system identifier could be generated
    …=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anchorfree.n…

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

  • Info Line 49, Column 161: entity was defined here
    …afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anchorf…
  • Warning Line 75, Column 282: reference not terminated by REFC delimiter
    …at=11K&affr=displayed_iframe_primo&loc=anchorfree.net&referer=empty" id="a54cd…

    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 75, Column 282: reference to external entity in attribute value
    …at=11K&affr=displayed_iframe_primo&loc=anchorfree.net&referer=empty" id="a54cd…

    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 75, Column 282: reference to entity "loc" for which no system identifier could be generated
    …at=11K&affr=displayed_iframe_primo&loc=anchorfree.net&referer=empty" id="a54cd…

    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 49, Column 189: entity was defined here
    …12&cat=11K&affr=displayed_iframe_primo&loc=anchorfree.net&referer=empty' frame…
  • Warning Line 75, Column 305: reference not terminated by REFC delimiter
    …frame_primo&loc=anchorfree.net&referer=empty" id="a54cd4c4" class="right_adv">…

    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 75, Column 305: reference to external entity in attribute value
    …frame_primo&loc=anchorfree.net&referer=empty" id="a54cd4c4" class="right_adv">…

    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 75, Column 305: reference to entity "referer" for which no system identifier could be generated
    …frame_primo&loc=anchorfree.net&referer=empty" id="a54cd4c4" class="right_adv">…

    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 49, Column 208: entity was defined here
    …played_iframe_primo&loc=anchorfree.net&referer=empty' frameborder='0' scrollin…
  • Error Line 87, Column 2052: required attribute "alt" not specified
    …'><img src='images/morenews_btn.jpg' /></a></div></div>   		</div><div class="…

    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 91, Column 183: character "&" is the first character of a delimiter but occurred as data
    …ions-users-and-groups.html'>Configuring Mountain Lion's Users & Groups</a></h2>

    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 102, Column 240: cannot generate system identifier for general entity "R"
    …itors in the tax software realm are H&R Block and Intuit, and while their apps…

    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 102, Column 240: general entity "R" not defined and no default entity
    …itors in the tax software realm are H&R Block and Intuit, and while their apps…

    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 102, Column 241: reference not terminated by REFC delimiter
    …tors in the tax software realm are H&R Block and Intuit, and while their apps …

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

  • Error Line 102, Column 241: reference to entity "R" for which no system identifier could be generated
    …tors in the tax software realm are H&R Block and Intuit, and while their apps …

    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 102, Column 239: entity was defined here
    …titors in the tax software realm are H&R Block and Intuit, and while their app…
  • Warning Line 102, Column 748: reference not terminated by REFC delimiter
    …-home-1040ez-for-ios.html'>Review: H&R Block At Home 1040EZ for iOS</a></li><l…

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

  • Error Line 102, Column 748: reference to entity "R" for which no system identifier could be generated
    …-home-1040ez-for-ios.html'>Review: H&R Block At Home 1040EZ for iOS</a></li><l…

    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 102, Column 239: entity was defined here
    …titors in the tax software realm are H&R Block and Intuit, and while their app…
  • Warning Line 102, Column 1075: reference not terminated by REFC delimiter
    …ree-edition-for-ipad.html'>Review: H&R Block At Home Free Edition for iPad</a>…

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

  • Error Line 102, Column 1075: reference to entity "R" for which no system identifier could be generated
    …ree-edition-for-ipad.html'>Review: H&R Block At Home Free Edition for iPad</a>…

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

  • Info Line 102, Column 239: entity was defined here
    …titors in the tax software realm are H&R Block and Intuit, and while their app…
  • Warning Line 102, Column 1251: reference not terminated by REFC delimiter
    …at-home-2012-for-mac.html'>Review: H&R Block At Home 2012 for Mac</a></li><li …

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

  • Error Line 102, Column 1251: reference to entity "R" for which no system identifier could be generated
    …at-home-2012-for-mac.html'>Review: H&R Block At Home 2012 for Mac</a></li><li …

    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 102, Column 239: entity was defined here
    …titors in the tax software realm are H&R Block and Intuit, and while their app…
  • Error Line 102, Column 1870: required attribute "alt" not specified
    …'><img src='images/morenews_btn.jpg' /></a></div></div>		</div><div class="rbb…

    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 105, Column 11: ID "content_bottom" already defined
     <div id="content_bottom" align="left">

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

  • Info Line 82, Column 11: ID "content_bottom" first defined here
     <div id="content_bottom" align="left">
  • Warning Line 108, Column 188: reference not terminated by REFC delimiter
    …h.com/delivery/afrlg.php?zoneid=95&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&…

    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 108, Column 188: reference to external entity in attribute value
    …h.com/delivery/afrlg.php?zoneid=95&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&…

    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 108, Column 188: reference to entity "tag" for which no system identifier could be generated
    …h.com/delivery/afrlg.php?zoneid=95&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&…

    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 49, Column 95: entity was defined here
    …earch.com/delivery/afrlg.php?zoneid=94&tag=UNREGISTERED&cnl=empty&afhss=UNDEFI…
  • Warning Line 108, Column 205: reference not terminated by REFC delimiter
    …rlg.php?zoneid=95&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&ca…

    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 108, Column 205: reference to external entity in attribute value
    …rlg.php?zoneid=95&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&ca…

    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 108, Column 205: reference to entity "cnl" for which no system identifier could be generated
    …rlg.php?zoneid=95&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&ca…

    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 49, Column 112: entity was defined here
    …y/afrlg.php?zoneid=94&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=323223881…
  • Warning Line 108, Column 217: reference not terminated by REFC delimiter
    …id=95&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=d…

    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 108, Column 217: reference to external entity in attribute value
    …id=95&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=d…

    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 108, Column 217: reference to entity "afhss" for which no system identifier could be generated
    …id=95&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=d…

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

  • Info Line 49, Column 122: entity was defined here
    …p?zoneid=94&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&…
  • Warning Line 108, Column 231: reference not terminated by REFC delimiter
    …GISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_ifram…

    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 108, Column 231: reference to external entity in attribute value
    …GISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_ifram…

    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 108, Column 231: reference to entity "sip" for which no system identifier could be generated
    …GISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_ifram…

    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 49, Column 138: entity was defined here
    …UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_i…
  • Warning Line 108, Column 246: reference not terminated by REFC delimiter
    …pty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anc…

    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 108, Column 246: reference to external entity in attribute value
    …pty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anc…

    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 108, Column 246: reference to entity "cat" for which no system identifier could be generated
    …pty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anc…

    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 49, Column 153: entity was defined here
    …l=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc…
  • Warning Line 108, Column 255: reference not terminated by REFC delimiter
    …=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anchorfree.n…

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

  • Warning Line 108, Column 255: reference to external entity in attribute value
    …=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anchorfree.n…

    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 108, Column 255: reference to entity "affr" for which no system identifier could be generated
    …=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anchorfree.n…

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

  • Info Line 49, Column 161: entity was defined here
    …afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anchorf…
  • Warning Line 108, Column 282: reference not terminated by REFC delimiter
    …at=11K&affr=displayed_iframe_primo&loc=anchorfree.net&referer=empty" id="AFt_a…

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

  • Warning Line 108, Column 282: reference to external entity in attribute value
    …at=11K&affr=displayed_iframe_primo&loc=anchorfree.net&referer=empty" id="AFt_a…

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

  • Error Line 108, Column 282: reference to entity "loc" for which no system identifier could be generated
    …at=11K&affr=displayed_iframe_primo&loc=anchorfree.net&referer=empty" id="AFt_a…

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

  • Info Line 49, Column 189: entity was defined here
    …12&cat=11K&affr=displayed_iframe_primo&loc=anchorfree.net&referer=empty' frame…
  • Warning Line 108, Column 305: reference not terminated by REFC delimiter
    …frame_primo&loc=anchorfree.net&referer=empty" id="AFt_adFrame2" class="middle_…

    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 108, Column 305: reference to external entity in attribute value
    …frame_primo&loc=anchorfree.net&referer=empty" id="AFt_adFrame2" class="middle_…

    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 108, Column 305: reference to entity "referer" for which no system identifier could be generated
    …frame_primo&loc=anchorfree.net&referer=empty" id="AFt_adFrame2" class="middle_…

    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 49, Column 208: entity was defined here
    …played_iframe_primo&loc=anchorfree.net&referer=empty' frameborder='0' scrollin…
  • Error Line 112, Column 11: ID "content_bottom" already defined
     <div id="content_bottom" align="left">

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

  • Info Line 82, Column 11: ID "content_bottom" first defined here
     <div id="content_bottom" align="left">
  • Error Line 117, Column 1967: required attribute "alt" not specified
    …'><img src='images/morenews_btn.jpg' /></a></div></div>   		</div><div class="…

    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 122, Column 361: cannot generate system identifier for general entity "P"
    …ry. Over the past two sessions, the S&P 500 has gained 1.9 percent, rising bac…

    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 122, Column 361: general entity "P" not defined and no default entity
    …ry. Over the past two sessions, the S&P 500 has gained 1.9 percent, rising bac…

    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 122, Column 362: reference not terminated by REFC delimiter
    …y. Over the past two sessions, the S&P 500 has gained 1.9 percent, rising back…

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

  • Error Line 122, Column 362: reference to entity "P" for which no system identifier could be generated
    …y. Over the past two sessions, the S&P 500 has gained 1.9 percent, rising back…

    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 122, Column 360: entity was defined here
    …ary. Over the past two sessions, the S&P 500 has gained 1.9 percent, rising ba…
  • Error Line 123, Column 2443: required attribute "alt" not specified
    …'><img src='images/morenews_btn.jpg' /></a></div></div>   		 </div><div class=…

    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 126, Column 10: ID "content_bottom" already defined
    <div id="content_bottom" align="left" >

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

  • Info Line 82, Column 11: ID "content_bottom" first defined here
     <div id="content_bottom" align="left">
  • Warning Line 129, Column 175: character "&" is the first character of a delimiter but occurred as data
    …hp?itemId=18956'>Enjoy Springtime in Venice at Il Palladio Hotel & SPA</a></h2>

    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 130, Column 496: character "&" is the first character of a delimiter but occurred as data
    …rown Costa Rica Honored by Conde Nast & Travel + Leisure</a></li><li style='di…

    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 130, Column 970: cannot generate system identifier for general entity "Only"
    …/custom/rsslink.php?itemId=18947'>One&Only Cape Town Wins Best Spa of the Year…

    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 130, Column 970: general entity "Only" not defined and no default entity
    …/custom/rsslink.php?itemId=18947'>One&Only Cape Town Wins Best Spa of the Year…

    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 130, Column 974: reference not terminated by REFC delimiter
    …tom/rsslink.php?itemId=18947'>One&Only Cape Town Wins Best Spa of the Year in …

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

  • Error Line 130, Column 974: reference to entity "Only" for which no system identifier could be generated
    …tom/rsslink.php?itemId=18947'>One&Only Cape Town Wins Best Spa of the Year in …

    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 130, Column 969: entity was defined here
    …m/custom/rsslink.php?itemId=18947'>One&Only Cape Town Wins Best Spa of the Yea…
  • Warning Line 130, Column 1346: character "&" is the first character of a delimiter but occurred as data
    …n the Engadine: Family Fun in the Sun & Snow</a></li><li style='display:none'>…

    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 130, Column 1973: required attribute "alt" not specified
    …'><img src='images/morenews_btn.jpg' /></a></div></div>   		 </div><div class=…

    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 132, Column 121: value of attribute "frameborder" cannot be "no"; must be one of "1", "0"
    …ling="no" height="250" frameborder="no" allowtransparency="true" framespacing=…

    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 132, Column 224: reference not terminated by REFC delimiter
    …h.com/delivery/afrlg.php?zoneid=96&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&…

    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 132, Column 224: reference to external entity in attribute value
    …h.com/delivery/afrlg.php?zoneid=96&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&…

    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 132, Column 224: reference to entity "tag" for which no system identifier could be generated
    …h.com/delivery/afrlg.php?zoneid=96&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&…

    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 49, Column 95: entity was defined here
    …earch.com/delivery/afrlg.php?zoneid=94&tag=UNREGISTERED&cnl=empty&afhss=UNDEFI…
  • Warning Line 132, Column 241: reference not terminated by REFC delimiter
    …rlg.php?zoneid=96&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&ca…

    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 132, Column 241: reference to external entity in attribute value
    …rlg.php?zoneid=96&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&ca…

    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 132, Column 241: reference to entity "cnl" for which no system identifier could be generated
    …rlg.php?zoneid=96&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&ca…

    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 49, Column 112: entity was defined here
    …y/afrlg.php?zoneid=94&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=323223881…
  • Warning Line 132, Column 253: reference not terminated by REFC delimiter
    …id=96&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=d…

    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 132, Column 253: reference to external entity in attribute value
    …id=96&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=d…

    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 132, Column 253: reference to entity "afhss" for which no system identifier could be generated
    …id=96&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=d…

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

  • Info Line 49, Column 122: entity was defined here
    …p?zoneid=94&tag=UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&…
  • Warning Line 132, Column 267: reference not terminated by REFC delimiter
    …GISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_ifram…

    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 132, Column 267: reference to external entity in attribute value
    …GISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_ifram…

    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 132, Column 267: reference to entity "sip" for which no system identifier could be generated
    …GISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_ifram…

    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 49, Column 138: entity was defined here
    …UNREGISTERED&cnl=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_i…
  • Warning Line 132, Column 282: reference not terminated by REFC delimiter
    …pty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anc…

    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 132, Column 282: reference to external entity in attribute value
    …pty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anc…

    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 132, Column 282: reference to entity "cat" for which no system identifier could be generated
    …pty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anc…

    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 49, Column 153: entity was defined here
    …l=empty&afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc…
  • Warning Line 132, Column 291: reference not terminated by REFC delimiter
    …=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anchorfree.n…

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

  • Warning Line 132, Column 291: reference to external entity in attribute value
    …=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anchorfree.n…

    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 132, Column 291: reference to entity "affr" for which no system identifier could be generated
    …=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anchorfree.n…

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

  • Info Line 49, Column 161: entity was defined here
    …afhss=UNDEFINED&sip=3232238812&cat=11K&affr=displayed_iframe_primo&loc=anchorf…
  • Warning Line 132, Column 318: reference not terminated by REFC delimiter
    …at=11K&affr=displayed_iframe_primo&loc=anchorfree.net&referer=empty" name="a22…

    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 132, Column 318: reference to external entity in attribute value
    …at=11K&affr=displayed_iframe_primo&loc=anchorfree.net&referer=empty" name="a22…

    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 132, Column 318: reference to entity "loc" for which no system identifier could be generated
    …at=11K&affr=displayed_iframe_primo&loc=anchorfree.net&referer=empty" name="a22…

    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 49, Column 189: entity was defined here
    …12&cat=11K&affr=displayed_iframe_primo&loc=anchorfree.net&referer=empty' frame…
  • Warning Line 132, Column 341: reference not terminated by REFC delimiter
    …frame_primo&loc=anchorfree.net&referer=empty" name="a220c995" id="a220c995" cl…

    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 132, Column 341: reference to external entity in attribute value
    …frame_primo&loc=anchorfree.net&referer=empty" name="a220c995" id="a220c995" cl…

    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 132, Column 341: reference to entity "referer" for which no system identifier could be generated
    …frame_primo&loc=anchorfree.net&referer=empty" name="a220c995" id="a220c995" cl…

    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 49, Column 208: entity was defined here
    …played_iframe_primo&loc=anchorfree.net&referer=empty' frameborder='0' scrollin…
  • Error Line 132, Column 369: ID "a220c995" already defined
    …et&referer=empty" name="a220c995" id="a220c995" class="left_adv"></iframe></di…

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

  • Info Line 53, Column 338: ID "a220c995" first defined here
    …ree.net&referer=empty" name="a220c995" id="a220c995" class="left_adv"></iframe>
  • Error Line 138, Column 14: ID "search_form" already defined
    	 	<form id="search_form" action="http://search.hotspotshield.com/land/results.…

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

  • Info Line 22, Column 14: ID "search_form" first defined here
    	 	<form id="search_form" action="http://search.hotspotshield.com/land/results.…
  • Error Line 138, Column 96: value of attribute "method" cannot be "GET"; must be one of "get", "post"
    …search.hotspotshield.com/land/results.php" method="GET" accept-charset="UTF-8">

    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 139, Column 82: ID "q" already defined
    …complete="off" type="text" name="q" id="q" size="51" maxlength="2048" value="">

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

  • Info Line 23, Column 82: ID "q" first defined here
    …complete="off" type="text" name="q" id="q" size="51" maxlength="2048" value="">
  • Error Line 139, Column 121: end tag for "input" omitted, but OMITTAG NO was specified
    …complete="off" type="text" name="q" id="q" size="51" maxlength="2048" value="">

    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 139, Column 5: start tag was here
    	 		<input class="search_form_input" autocomplete="off" type="text" name="q" id…
  • Error Line 140, Column 50: end tag for "input" omitted, but OMITTAG NO was specified
    	 		<input type="hidden" value="903" name="askt">

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

  • Info Line 140, Column 5: start tag was here
    	 		<input type="hidden" value="903" name="askt">
  • Error Line 141, Column 58: end tag for "input" omitted, but OMITTAG NO was specified
    	 		<input type="hidden" value="UNREGISTERED" name="tag">

    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 141, Column 5: start tag was here
    	 		<input type="hidden" value="UNREGISTERED" name="tag">
  • Error Line 142, Column 69: end tag for "input" omitted, but OMITTAG NO was specified
    	 		<input class="search_form_submit" type="submit" value="SEARCH" >

    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 142, Column 5: start tag was here
    	 		<input class="search_form_submit" type="submit" value="SEARCH" >
  • Error Line 161, Column 12: character ")" not allowed in attribute specification list
    		while(m<i){
  • Error Line 161, Column 12: document type does not allow element "i" here
    		while(m<i){

    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 171, Column 9: end tag for "i" omitted, but OMITTAG NO was specified
    </script>

    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 161, Column 10: start tag was here
    		while(m<i){
  • Error Line 172, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body>

    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 13, Column 1: start tag was here
    <div id="maincontent" align="center">

Visitor Analysis

Daily Visitor
  • 26.833 visits
Daily Visitor