Coin values are updated with live prices. Coinflation measures the current metal or melt value of U.S. circulating coinage, pre-1965 silver coins, and gold coins. ...

coinflation.com
  • Domain Name
    coinflation.com
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #52074
  • Page Size
    63.4 KB
  • Ip Address
    184.168.65.197
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    27 GIF, 22 JPG, 0 PNG

Website Meta Analysis

  • Title
    Current Melt Value Of Coins - How Much Is Your Coin Worth?
  • Meta Keyword
    coin values, silver, gold
  • Meta Description
    Coin values are updated with live prices. Coinflation measures the current metal or melt value of U.S. circulating coinage, pre-1965 silver coins, and gold coins.

Technical Analysis

  • Webserver
    Apache/2.2.3 (CentOS)
  • Ip Address
    184.168.65.197
  • Domain Age
    8 Years, 11 Months, 9 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from coinflation.com.

HTML Analysis

  • date: Fri, 28 Jun 2013 10:24:04 GMT
  • server: Apache/2.2.3 (CentOS)
  • accept-ranges: bytes
  • connection: close
  • content-type: text/html; charset=UTF-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: COINFLATION.COM
Created on: 06-Jul-04
Expires on: 06-Jul-20
Last Updated on: 06-Nov-11

Registrant:
Collectors Universe Inc.
1921 E. Alton Ave
Santa Ana, CA 92705
United States

Administrative Contact:
Saada, Ibrahim email
Collectors Universe Inc.
1921 E. Alton Ave
Santa Ana, CA 92705
United States
+1.9495671243

Technical Contact:
Saada, Ibrahim email
Collectors Universe Inc.
1921 E. Alton Ave
Santa Ana, CA 92705
United States
+1.9495671243

Domain servers in listed order:
NS1.COINFLATION.COM
NS2.COINFLATION.COM

DNS Analysis


DNS servers
ns2.coinflation.com [184.168.65.197]
ns1.coinflation.com [184.168.65.197]


DNS Records

Answer records
coinflation.com SOA
server: ns1.coinflation.com
email: hostmaster@coinflation.com
serial: 2011021901
refresh: 3600
retry: 3600
expire: 1209600
minimum ttl: 3600
3600s
coinflation.com A 184.168.65.197 3600s
coinflation.com NS  ns1.coinflation.com 3600s
coinflation.com NS  ns2.coinflation.com 3600s
coinflation.com MX
preference: 10
exchange: mail.coinflation.com
3600s

Authority records

Additional records
ns1.coinflation.com A 184.168.65.197 3600s
ns2.coinflation.com A 184.168.65.197 3600s
mail.coinflation.com A 184.168.65.197 3600s

IP 184.168.65.197 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Scottsdale
  • Continent Code
    85260
  • Latitude
    480
  • Longitude
    753
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 184.168.65.197"
    #
    # Use "?" to get help.
    #

    #
    # The following results may also be obtained via:
    # http://whois.arin.net/rest/nets;q=184.168.65.197?showDetails=true&showARIN=false&ext=netref2
    #

    NetRange: 184.168.0.0 - 184.168.255.255
    CIDR: 184.168.0.0/16
    OriginAS: AS26496
    NetName: GO-DADDY-COM-LLC
    NetHandle: NET-184-168-0-0-1
    Parent: NET-184-0-0-0-0
    NetType: Direct Allocation
    Comment: Please send abuse complaints to abuse@godaddy.com
    RegDate: 2010-09-21
    Updated: 2012-02-24
    Ref: http://whois.arin.net/rest/net/NET-184-168-0-0-1

    OrgName: GoDaddy.com, LLC
    OrgId: GODAD
    Address: 14455 N Hayden Road
    Address: Suite 226
    City: Scottsdale
    StateProv: AZ
    PostalCode: 85260
    Country: US
    RegDate: 2007-06-01
    Updated: 2012-03-15
    Comment: Please send abuse complaints to abuse@godaddy.com
    Ref: http://whois.arin.net/rest/org/GODAD

    OrgAbuseHandle: ABUSE51-ARIN
    OrgAbuseName: Abuse Department
    OrgAbusePhone: +1-480-624-2505
    OrgAbuseEmail: abuse@godaddy.com
    OrgAbuseRef: http://whois.arin.net/rest/poc/ABUSE51-ARIN

    OrgTechHandle: NOC124-ARIN
    OrgTechName: Network Operations Center
    OrgTechPhone: +1-480-505-8809
    OrgTechEmail: noc@godaddy.com
    OrgTechRef: http://whois.arin.net/rest/poc/NOC124-ARIN

    OrgNOCHandle: NOC124-ARIN
    OrgNOCName: Network Operations Center
    OrgNOCPhone: +1-480-505-8809
    OrgNOCEmail: noc@godaddy.com
    OrgNOCRef: http://whois.arin.net/rest/poc/NOC124-ARIN

    #
    # ARIN WHOIS data and services are subject to the Terms of Use
    # available at: https://www.arin.net/whois_tou.html
    #

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 421 Errors
  • 61 Warnings
Ratio Text/Html
  • 0.6848154310716708
Message Error
  • Error Line 1, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
    <html><head><title>Current Melt Value Of Coins - How Much Is Your Coin Worth?</…

    The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.

  • Warning Line 1, Column 409: NET-enabling start-tag requires SHORTTAG YES
    …e-1965 silver coins, and gold coins." /><meta name="google-site-verification" …

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 1, Column 503: NET-enabling start-tag requires SHORTTAG YES
    …f7DdpRhUcTUbr7zjKNw1TiVdJVgH917PN3-g" /><meta name="keywords" content="coin va…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1, Column 503: document type does not allow element "META" here
    …f7DdpRhUcTUbr7zjKNw1TiVdJVgH917PN3-g" /><meta name="keywords" content="coin va…

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

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

  • Warning Line 1, Column 563: NET-enabling start-tag requires SHORTTAG YES
    …" content="coin values, silver, gold" /><meta http-equiv="pragma" content="no-…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1, Column 563: document type does not allow element "META" here
    …" content="coin values, silver, gold" /><meta http-equiv="pragma" content="no-…

    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 1, Column 609: document type does not allow element "META" here
    …http-equiv="pragma" content="no-cache"><meta http-equiv="expires" content="-1"…

    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 1, Column 649: document type does not allow element "META" here
    …meta http-equiv="expires" content="-1"><link rel="shortcut icon" href="penny2.…

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

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

  • Warning Line 1, Column 714: NET-enabling start-tag requires SHORTTAG YES
    …href="penny2.ico" type="image/x-icon" /><link rel="canonical" href="http://www…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1, Column 714: document type does not allow element "LINK" here
    …href="penny2.ico" type="image/x-icon" /><link rel="canonical" href="http://www…

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

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

  • Warning Line 1, Column 773: NET-enabling start-tag requires SHORTTAG YES
    …l" href="http://www.coinflation.com/" /><script language="JavaScript" src="too…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1, Column 773: document type does not allow element "LINK" here
    …l" href="http://www.coinflation.com/" /><script language="JavaScript" src="too…

    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 1, Column 821: required attribute "TYPE" not specified
    …language="JavaScript" src="tooltip.js"></script><script language="JavaScript" …

    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 1, Column 872: required attribute "TYPE" not specified
    …" src="tooltip.js"></script><script language="JavaScript" src="dm.js"></script>

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

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

  • Error Line 23, Column 7: end tag for element "HEAD" which is not open
    </head>

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

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

  • Error Line 24, Column 24: document type does not allow element "BODY" here
    <body bgcolor="#ffffff"><div align="center">

    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 34, Column 87: document type does not allow element "FORM" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME" start-tag
    …tion="http://www.coinflation.com/search_results_test.html" id="cse-search-box">

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

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

  • Warning Line 36, Column 78: NET-enabling start-tag requires SHORTTAG YES
        <input type="hidden" name="cx" value="018385259782779351206:li8l7wnm3bo" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 37, Column 54: NET-enabling start-tag requires SHORTTAG YES
        <input type="hidden" name="cof" value="FORID:11" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 38, Column 50: NET-enabling start-tag requires SHORTTAG YES
        <input type="hidden" name="ie" value="UTF-8" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 39, Column 43: NET-enabling start-tag requires SHORTTAG YES
        <input type="text" name="q" size="31" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 40, Column 56: NET-enabling start-tag requires SHORTTAG YES
        <input type="submit" name="sa" value="Coin Search" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 45, Column 5: end tag for "FONT" omitted, but its declaration does not permit this
    </td></tr>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 32, Column 58: start tag was here
    </td><td align="right" valign="middle" bgcolor="#eeeeee"><font size="1"><br>
  • Error Line 47, Column 1292: required attribute "ALT" not specified
    …es</b> <img src="http://www.coinflation.com/menuarrow.gif" border=0></a></font>

    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 55, Column 17: an attribute value must be a literal unless it contains only name characters
    <tr><td width=75% valign=top align=left><br><div id="tooltip" name="tooltip" st…

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

  • Error Line 55, Column 68: there is no attribute "NAME"
    …gn=top align=left><br><div id="tooltip" name="tooltip" style="width:200"></div>

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

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

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

  • Error Line 57, Column 60: there is no attribute "MARGIN"
    …g="0" cellspacing="0" width="100%" margin="0"><tr><td valign="top" width="225">

    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 57, Column 63: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …g="0" cellspacing="0" width="100%" margin="0"><tr><td valign="top" width="225">

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

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

  • Error Line 64, Column 35: required attribute "ALT" not specified
    <img src="wt.gif" height=5 width=1><br><p class="main2">

    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 72, Column 87: cannot generate system identifier for general entity "pub"
    …over/1/711-53200-19255-0/1?icep_ff3=2&pub=5574895479&toolid=10001&campid=53368…

    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 72, Column 87: general entity "pub" not defined and no default entity
    …over/1/711-53200-19255-0/1?icep_ff3=2&pub=5574895479&toolid=10001&campid=53368…

    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.

  • Error Line 72, Column 90: reference to entity "pub" for which no system identifier could be generated
    …r/1/711-53200-19255-0/1?icep_ff3=2&pub=5574895479&toolid=10001&campid=53368864…

    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 72, Column 86: entity was defined here
    …rover/1/711-53200-19255-0/1?icep_ff3=2&pub=5574895479&toolid=10001&campid=5336…
  • Warning Line 72, Column 102: cannot generate system identifier for general entity "toolid"
    …0-19255-0/1?icep_ff3=2&pub=5574895479&toolid=10001&campid=5336886491&customid=…

    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 72, Column 102: general entity "toolid" not defined and no default entity
    …0-19255-0/1?icep_ff3=2&pub=5574895479&toolid=10001&campid=5336886491&customid=…

    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.

  • Error Line 72, Column 108: reference to entity "toolid" for which no system identifier could be generated
    …5-0/1?icep_ff3=2&pub=5574895479&toolid=10001&campid=5336886491&customid=&icep_…

    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 72, Column 101: entity was defined here
    …00-19255-0/1?icep_ff3=2&pub=5574895479&toolid=10001&campid=5336886491&customid…
  • Warning Line 72, Column 115: cannot generate system identifier for general entity "campid"
    …cep_ff3=2&pub=5574895479&toolid=10001&campid=5336886491&customid=&icep_item=35…

    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 72, Column 115: general entity "campid" not defined and no default entity
    …cep_ff3=2&pub=5574895479&toolid=10001&campid=5336886491&customid=&icep_item=35…

    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.

  • Error Line 72, Column 121: reference to entity "campid" for which no system identifier could be generated
    …3=2&pub=5574895479&toolid=10001&campid=5336886491&customid=&icep_item=35071448…

    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 72, Column 114: entity was defined here
    …icep_ff3=2&pub=5574895479&toolid=10001&campid=5336886491&customid=&icep_item=3…
  • Warning Line 72, Column 133: cannot generate system identifier for general entity "customid"
    …895479&toolid=10001&campid=5336886491&customid=&icep_item=350714482135&ipn=psm…

    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 72, Column 133: general entity "customid" not defined and no default entity
    …895479&toolid=10001&campid=5336886491&customid=&icep_item=350714482135&ipn=psm…

    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.

  • Error Line 72, Column 141: reference to entity "customid" for which no system identifier could be generated
    …oolid=10001&campid=5336886491&customid=&icep_item=350714482135&ipn=psmain&icep…

    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 72, Column 132: entity was defined here
    …4895479&toolid=10001&campid=5336886491&customid=&icep_item=350714482135&ipn=ps…
  • Warning Line 72, Column 143: cannot generate system identifier for general entity "icep_item"
    …lid=10001&campid=5336886491&customid=&icep_item=350714482135&ipn=psmain&icep_v…

    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 72, Column 143: general entity "icep_item" not defined and no default entity
    …lid=10001&campid=5336886491&customid=&icep_item=350714482135&ipn=psmain&icep_v…

    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.

  • Error Line 72, Column 152: reference to entity "icep_item" for which no system identifier could be generated
    …&campid=5336886491&customid=&icep_item=350714482135&ipn=psmain&icep_vectorid=2…

    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 72, Column 142: entity was defined here
    …olid=10001&campid=5336886491&customid=&icep_item=350714482135&ipn=psmain&icep_…
  • Warning Line 72, Column 166: cannot generate system identifier for general entity "ipn"
    …6491&customid=&icep_item=350714482135&ipn=psmain&icep_vectorid=229466&kwid=902…

    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 72, Column 166: general entity "ipn" not defined and no default entity
    …6491&customid=&icep_item=350714482135&ipn=psmain&icep_vectorid=229466&kwid=902…

    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.

  • Error Line 72, Column 169: reference to entity "ipn" for which no system identifier could be generated
    …1&customid=&icep_item=350714482135&ipn=psmain&icep_vectorid=229466&kwid=902099…

    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 72, Column 165: entity was defined here
    …86491&customid=&icep_item=350714482135&ipn=psmain&icep_vectorid=229466&kwid=90…
  • Warning Line 72, Column 177: cannot generate system identifier for general entity "icep_vectorid"
    …id=&icep_item=350714482135&ipn=psmain&icep_vectorid=229466&kwid=902099&mtid=82…

    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 72, Column 177: general entity "icep_vectorid" not defined and no default entity
    …id=&icep_item=350714482135&ipn=psmain&icep_vectorid=229466&kwid=902099&mtid=82…

    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.

  • Error Line 72, Column 190: reference to entity "icep_vectorid" for which no system identifier could be generated
    …=350714482135&ipn=psmain&icep_vectorid=229466&kwid=902099&mtid=824&kw=lg" clas…

    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 72, Column 176: entity was defined here
    …mid=&icep_item=350714482135&ipn=psmain&icep_vectorid=229466&kwid=902099&mtid=8…
  • Warning Line 72, Column 198: cannot generate system identifier for general entity "kwid"
    …82135&ipn=psmain&icep_vectorid=229466&kwid=902099&mtid=824&kw=lg" class="atest…

    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 72, Column 198: general entity "kwid" not defined and no default entity
    …82135&ipn=psmain&icep_vectorid=229466&kwid=902099&mtid=824&kw=lg" class="atest…

    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.

  • Error Line 72, Column 202: reference to entity "kwid" for which no system identifier could be generated
    …5&ipn=psmain&icep_vectorid=229466&kwid=902099&mtid=824&kw=lg" class="atest" on…

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

  • Info Line 72, Column 197: entity was defined here
    …482135&ipn=psmain&icep_vectorid=229466&kwid=902099&mtid=824&kw=lg" class="ates…
  • Warning Line 72, Column 210: cannot generate system identifier for general entity "mtid"
    …main&icep_vectorid=229466&kwid=902099&mtid=824&kw=lg" class="atest" onmouseout…

    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 72, Column 210: general entity "mtid" not defined and no default entity
    …main&icep_vectorid=229466&kwid=902099&mtid=824&kw=lg" class="atest" onmouseout…

    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.

  • Error Line 72, Column 214: reference to entity "mtid" for which no system identifier could be generated
    …&icep_vectorid=229466&kwid=902099&mtid=824&kw=lg" class="atest" onmouseout="ja…

    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 72, Column 209: entity was defined here
    …smain&icep_vectorid=229466&kwid=902099&mtid=824&kw=lg" class="atest" onmouseou…
  • Warning Line 72, Column 219: cannot generate system identifier for general entity "kw"
    …_vectorid=229466&kwid=902099&mtid=824&kw=lg" class="atest" onmouseout="javaScr…

    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 72, Column 219: general entity "kw" not defined and no default entity
    …_vectorid=229466&kwid=902099&mtid=824&kw=lg" class="atest" onmouseout="javaScr…

    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.

  • Error Line 72, Column 221: reference to entity "kw" for which no system identifier could be generated
    …ectorid=229466&kwid=902099&mtid=824&kw=lg" class="atest" onmouseout="javaScrip…

    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 72, Column 218: entity was defined here
    …p_vectorid=229466&kwid=902099&mtid=824&kw=lg" class="atest" onmouseout="javaSc…
  • Error Line 78, Column 41: there is no attribute "COLOR"
    <hr noshade width="100%" size="1" color="#999999">

    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 82, Column 90: cannot generate system identifier for general entity "sn"
    …ntent/en/mineweb-gold-news?oid=177582&sn=Detail" onmouseout="javaScript:toolti…

    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 82, Column 90: general entity "sn" not defined and no default entity
    …ntent/en/mineweb-gold-news?oid=177582&sn=Detail" onmouseout="javaScript:toolti…

    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.

  • Error Line 82, Column 92: reference to entity "sn" for which no system identifier could be generated
    …ent/en/mineweb-gold-news?oid=177582&sn=Detail" onmouseout="javaScript:tooltipO…

    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 82, Column 89: entity was defined here
    …ontent/en/mineweb-gold-news?oid=177582&sn=Detail" onmouseout="javaScript:toolt…
  • Warning Line 84, Column 74: cannot generate system identifier for general entity "ArticleId"
    …r.com/ta/numis/Article.jsp?ad=article&ArticleId=26492" onmouseout="javaScript:…

    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 84, Column 74: general entity "ArticleId" not defined and no default entity
    …r.com/ta/numis/Article.jsp?ad=article&ArticleId=26492" onmouseout="javaScript:…

    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.

  • Error Line 84, Column 83: reference to entity "ArticleId" for which no system identifier could be generated
    …numis/Article.jsp?ad=article&ArticleId=26492" onmouseout="javaScript:tooltipOf…

    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 84, Column 73: entity was defined here
    …er.com/ta/numis/Article.jsp?ad=article&ArticleId=26492" onmouseout="javaScript…
  • Error Line 93, Column 634: end tag for "FONT" omitted, but its declaration does not permit this
    …c="img/new_img.gif" width="18" height="7" alt="New"></td><td></td></tr></table>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 93, Column 82: start tag was here
    … align=left><tr><td align=left nowrap><font face="Arial" size=1><a href="http:…
  • Error Line 94, Column 4: end tag for element "P" which is not open
    </p>

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

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

  • Error Line 96, Column 43: document type does not allow element "A" here
    <a name="basemetal"><a name="unitedstates"><br><br>

    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 98, Column 50: document type does not allow element "HR" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <hr noshade width="100%" size="1" color="#999999">

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

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

  • Error Line 102, Column 63: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <table width="100%" border="0" cellpadding="0" cellspacing="0"><tr>

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

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

  • Error Line 103, Column 216: end tag for "FONT" omitted, but its declaration does not permit this
    … alt="up" width="10" height="14"> <font color="green"><b>0.0016</b></font></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 103, Column 30: start tag was here
    <td width="33%" valign="top"><font size="2" face="Arial, Helvetica"><b>Copper</…
  • Error Line 104, Column 216: end tag for "FONT" omitted, but its declaration does not permit this
    … alt="down" width="10" height="14"> <font color="red"><b>0.0021</b></font></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 104, Column 30: start tag was here
    <td width="33%" valign="top"><font size="2" face="Arial, Helvetica"><b>Zinc</b>…
  • Error Line 105, Column 216: end tag for "FONT" omitted, but its declaration does not permit this
    … alt="up" width="10" height="14"> <font color="green"><b>0.0711</b></font></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 105, Column 30: start tag was here
    <td width="33%" valign="top"><font size="2" face="Arial, Helvetica"><b>Nickel</…
  • Error Line 107, Column 54: an attribute value must be a literal unless it contains only name characters
    <table border=0 cellpadding=0 cellspacing=0 width=100%><tr><td>

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

  • Error Line 107, Column 55: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <table border=0 cellpadding=0 cellspacing=0 width=100%><tr><td>

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

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

  • Error Line 108, Column 54: an attribute value must be a literal unless it contains only name characters
    <table border=0 cellpadding=1 cellspacing=0 width=100% bgcolor=#ffffff><tr><td>

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

  • Error Line 108, Column 64: an attribute value must be a literal unless it contains only name characters
    <table border=0 cellpadding=1 cellspacing=0 width=100% bgcolor=#ffffff><tr><td>

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

  • Error Line 109, Column 54: an attribute value must be a literal unless it contains only name characters
    <table border=0 cellpadding=0 cellspacing=1 width=100% bgcolor=#cccccc><tr><td>

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

  • Error Line 109, Column 64: an attribute value must be a literal unless it contains only name characters
    <table border=0 cellpadding=0 cellspacing=1 width=100% bgcolor=#cccccc><tr><td>

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

  • Error Line 110, Column 17: an attribute value must be a literal unless it contains only name characters
    <table width=100% bgcolor="#ffffff" border=0 cellpadding=4 cellspacing=0><tr bg…

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

  • Error Line 110, Column 86: an attribute value must be a literal unless it contains only name characters
    …llpadding=4 cellspacing=0><tr bgcolor=#cccccc><td bgcolor=#cccccc border=0 ali…

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

  • Error Line 110, Column 106: an attribute value must be a literal unless it contains only name characters
    …ing=0><tr bgcolor=#cccccc><td bgcolor=#cccccc border=0 align=left colspan=2><f…

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

  • Error Line 110, Column 121: there is no attribute "BORDER"
    …or=#cccccc><td bgcolor=#cccccc border=0 align=left colspan=2><font face="Arial…

    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 111, Column 13: an attribute value must be a literal unless it contains only name characters
    <td bgcolor=#cccccc border=0><font face="Arial, Helvetica" size=2><b>Face Value…

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

  • Error Line 111, Column 88: end tag for "FONT" omitted, but its declaration does not permit this
    …or=#cccccc border=0><font face="Arial, Helvetica" size=2><b>Face Value</b></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 111, Column 30: start tag was here
    <td bgcolor=#cccccc border=0><font face="Arial, Helvetica" size=2><b>Face Value…
  • Error Line 112, Column 64: end tag for "FONT" omitted, but its declaration does not permit this
    <td><font face="Arial, Helvetica" size=2><b>Metal Value</b></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 112, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><b>Metal Value</b></td>
  • Error Line 113, Column 74: end tag for "FONT" omitted, but its declaration does not permit this
    <td><font face="Arial, Helvetica" size=2><b>Metal % of Face Value</b></td></tr>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 113, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><b>Metal % of Face Value</b></td></tr>
  • Error Line 114, Column 121: document type does not allow element "A" here
    …ue.html" title="1909-1982 Copper Cent"><img src="http://www.coinflation.com/pe…

    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 114, Column 408: document type does not allow element "A" here
    …le="1909-1982 Copper Cent Specification">1909-1982 Cent (95% copper)</a> *</td>

    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 114, Column 446: end tag for "FONT" omitted, but its declaration does not permit this
    …le="1909-1982 Copper Cent Specification">1909-1982 Cent (95% copper)</a> *</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 114, Column 245: start tag was here
    …er Cent" border=0></a></td><td nowrap><font face="Arial, Helvetica" size=2><a …
  • Error Line 115, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.01</td>

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

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

  • Error Line 115, Column 98: end tag for "DIV" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.01</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 115, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 115, Column 98: end tag for "FONT" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.01</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 115, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 116, Column 190: document type does not allow element "A" here
    …e" title="1909-1982 Copper Cent Melt Value Calculation">$0.0246081</a></b></td>

    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 116, Column 213: end tag for "FONT" omitted, but its declaration does not permit this
    …e" title="1909-1982 Copper Cent Melt Value Calculation">$0.0246081</a></b></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 116, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><b><a href="http://www.coinflation.com…
  • Error Line 117, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …, Helvetica" size=2><div style='font-size:12px; font-family:arial'>246.08%</td>

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

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

  • Error Line 117, Column 100: end tag for "DIV" omitted, but its declaration does not permit this
    …, Helvetica" size=2><div style='font-size:12px; font-family:arial'>246.08%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 117, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 117, Column 100: end tag for "FONT" omitted, but its declaration does not permit this
    …, Helvetica" size=2><div style='font-size:12px; font-family:arial'>246.08%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 117, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 119, Column 125: document type does not allow element "A" here
    …l" title="1946-2013 Nickel Melt Value"><img src="http://www.coinflation.com/ni…

    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 119, Column 231: end tag for "A" omitted, but its declaration does not permit this
    …9 alt="Jefferson Nickel" border=0></td><td><font face="Arial, Helvetica" size=…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 119, Column 9: start tag was here
    <tr><td><a href="http://www.coinflation.com/coins/1946-2007-Jefferson-Nickel-Va…
  • Error Line 119, Column 392: document type does not allow element "A" here
    …title="1946-2013 Nickel Specification">1946-2013 Nickel</a></td><td><font face…

    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 119, Column 417: end tag for "FONT" omitted, but its declaration does not permit this
    …pecification">1946-2013 Nickel</a></td><td><font face="Arial, Helvetica" size=…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 119, Column 236: start tag was here
    …="Jefferson Nickel" border=0></td><td><font face="Arial, Helvetica" size=2><a …
  • Error Line 119, Column 505: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.05</td>

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

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

  • Error Line 119, Column 515: end tag for "DIV" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.05</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 119, Column 459: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 119, Column 515: end tag for "FONT" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.05</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 119, Column 422: start tag was here
    …ication">1946-2013 Nickel</a></td><td><font face="Arial, Helvetica" size=2><di…
  • Error Line 120, Column 183: document type does not allow element "A" here
    …tvalue" title="1946-2013 Nickel Melt Value Calculation">$0.0537600</a></b></td>

    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 120, Column 206: end tag for "FONT" omitted, but its declaration does not permit this
    …tvalue" title="1946-2013 Nickel Melt Value Calculation">$0.0537600</a></b></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 120, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><b><a href="http://www.coinflation.com…
  • Error Line 121, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …, Helvetica" size=2><div style='font-size:12px; font-family:arial'>107.52%</td>

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

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

  • Error Line 121, Column 100: end tag for "DIV" omitted, but its declaration does not permit this
    …, Helvetica" size=2><div style='font-size:12px; font-family:arial'>107.52%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 121, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 121, Column 100: end tag for "FONT" omitted, but its declaration does not permit this
    …, Helvetica" size=2><div style='font-size:12px; font-family:arial'>107.52%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 121, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 123, Column 119: document type does not allow element "A" here
    …alue.html" title="1982-2013 Zinc Cent"><img src="http://www.coinflation.com/pe…

    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 123, Column 225: end tag for "A" omitted, but its declaration does not permit this
    … alt="Lincoln Zinc Cent" border=0></td><td><font face="Arial, Helvetica" size=…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 123, Column 9: start tag was here
    <tr><td><a href="http://www.coinflation.com/coins/1982-2007-Lincoln-Cent-Penny-…
  • Error Line 123, Column 391: document type does not allow element "A" here
    …itle="1982-2013 Zinc Cent Specification">1982-2013 Cent (97.5% zinc)</a> *</td>

    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 123, Column 429: end tag for "FONT" omitted, but its declaration does not permit this
    …itle="1982-2013 Zinc Cent Specification">1982-2013 Cent (97.5% zinc)</a> *</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 123, Column 230: start tag was here
    …"Lincoln Zinc Cent" border=0></td><td><font face="Arial, Helvetica" size=2><a …
  • Error Line 124, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.01</td>

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

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

  • Error Line 124, Column 98: end tag for "DIV" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.01</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 124, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 124, Column 98: end tag for "FONT" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.01</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 124, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 125, Column 188: document type does not allow element "A" here
    …lue" title="1982-2013 Zinc Cent Melt Value Calculation">$0.0058099</a></b></td>

    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 125, Column 211: end tag for "FONT" omitted, but its declaration does not permit this
    …lue" title="1982-2013 Zinc Cent Melt Value Calculation">$0.0058099</a></b></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 125, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><b><a href="http://www.coinflation.com…
  • Error Line 126, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …l, Helvetica" size=2><div style='font-size:12px; font-family:arial'>58.09%</td>

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

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

  • Error Line 126, Column 99: end tag for "DIV" omitted, but its declaration does not permit this
    …l, Helvetica" size=2><div style='font-size:12px; font-family:arial'>58.09%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 126, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 126, Column 99: end tag for "FONT" omitted, but its declaration does not permit this
    …l, Helvetica" size=2><div style='font-size:12px; font-family:arial'>58.09%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 126, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 128, Column 110: document type does not allow element "A" here
    …ime-Value.html" title="1965-2013 Dime"><img src="http://www.coinflation.com/di…

    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 128, Column 211: end tag for "A" omitted, but its declaration does not permit this
    …=39 alt="Roosevelt Dime" border=0></td><td><font face="Arial, Helvetica" size=…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 128, Column 9: start tag was here
    <tr><td><a href="http://www.coinflation.com/coins/1965-2007-Roosevelt-Dime-Valu…
  • Error Line 128, Column 368: document type does not allow element "A" here
    …t-Dime-Value.html" title="1965-2013 Dime Specification">1965-2013 Dime</a></td>

    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 128, Column 391: end tag for "FONT" omitted, but its declaration does not permit this
    …t-Dime-Value.html" title="1965-2013 Dime Specification">1965-2013 Dime</a></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 128, Column 216: start tag was here
    …lt="Roosevelt Dime" border=0></td><td><font face="Arial, Helvetica" size=2><a …
  • Error Line 129, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.10</td>

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

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

  • Error Line 129, Column 98: end tag for "DIV" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.10</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 129, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 129, Column 98: end tag for "FONT" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.10</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 129, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 130, Column 179: document type does not allow element "A" here
    …eltvalue" title="1965-2013 Dime Melt Value Calculation">$0.0205470</b></a></td>

    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 130, Column 193: end tag for "A" omitted, but its declaration does not permit this
    …eltvalue" title="1965-2013 Dime Melt Value Calculation">$0.0205470</b></a></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 130, Column 45: start tag was here
    …ont face="Arial, Helvetica" size=2><b><a href="http://www.coinflation.com/coin…
  • Error Line 130, Column 197: end tag for "FONT" omitted, but its declaration does not permit this
    …eltvalue" title="1965-2013 Dime Melt Value Calculation">$0.0205470</b></a></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 130, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><b><a href="http://www.coinflation.com…
  • Error Line 130, Column 197: end tag for "TABLE" omitted, but its declaration does not permit this
    …eltvalue" title="1965-2013 Dime Melt Value Calculation">$0.0205470</b></a></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 110, Column 1: start tag was here
    <table width=100% bgcolor="#ffffff" border=0 cellpadding=4 cellspacing=0><tr bg…
  • Error Line 130, Column 197: end tag for "TABLE" omitted, but its declaration does not permit this
    …eltvalue" title="1965-2013 Dime Melt Value Calculation">$0.0205470</b></a></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 109, Column 1: start tag was here
    <table border=0 cellpadding=0 cellspacing=1 width=100% bgcolor=#cccccc><tr><td>
  • Error Line 130, Column 197: end tag for "TABLE" omitted, but its declaration does not permit this
    …eltvalue" title="1965-2013 Dime Melt Value Calculation">$0.0205470</b></a></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 108, Column 1: start tag was here
    <table border=0 cellpadding=1 cellspacing=0 width=100% bgcolor=#ffffff><tr><td>
  • Error Line 130, Column 197: end tag for "TABLE" omitted, but its declaration does not permit this
    …eltvalue" title="1965-2013 Dime Melt Value Calculation">$0.0205470</b></a></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 107, Column 1: start tag was here
    <table border=0 cellpadding=0 cellspacing=0 width=100%><tr><td>
  • Error Line 130, Column 197: end tag for "FONT" omitted, but its declaration does not permit this
    …eltvalue" title="1965-2013 Dime Melt Value Calculation">$0.0205470</b></a></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 99, Column 1: start tag was here
    <font face="Arial, Helvetica" size=2 color="#000000">
  • Error Line 130, Column 202: end tag for "FONT" omitted, but its declaration does not permit this
    …eltvalue" title="1965-2013 Dime Melt Value Calculation">$0.0205470</b></a></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 56, Column 1: start tag was here
    <font face="Arial, Helvetica" size=2 color="#000000">
  • Error Line 131, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …l, Helvetica" size=2><div style='font-size:12px; font-family:arial'>20.54%</td>

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

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

  • Error Line 131, Column 99: end tag for "DIV" omitted, but its declaration does not permit this
    …l, Helvetica" size=2><div style='font-size:12px; font-family:arial'>20.54%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 131, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 131, Column 99: end tag for "FONT" omitted, but its declaration does not permit this
    …l, Helvetica" size=2><div style='font-size:12px; font-family:arial'>20.54%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 131, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 133, Column 226: end tag for "A" omitted, but its declaration does not permit this
    …alt="Washington Quarter" border=0></td><td><font face="Arial, Helvetica" size=…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 133, Column 9: start tag was here
    <tr><td><a href="http://www.coinflation.com/coins/1965-2007-Washington-Quarter-…
  • Error Line 133, Column 416: end tag for "FONT" omitted, but its declaration does not permit this
    …-Value.html" title="1965-2013 Quarter Specification">1965-2013 Quarter</a></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 133, Column 231: start tag was here
    …Washington Quarter" border=0></td><td><font face="Arial, Helvetica" size=2><a …
  • Error Line 134, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.25</td>

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

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

  • Error Line 134, Column 98: end tag for "DIV" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.25</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 134, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 134, Column 98: end tag for "FONT" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.25</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 134, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 135, Column 209: end tag for "FONT" omitted, but its declaration does not permit this
    …value" title="1965-2013 Quarter Melt Value Calculation">$0.0513700</a></b></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 135, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><b><a href="http://www.coinflation.com…
  • Error Line 136, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …l, Helvetica" size=2><div style='font-size:12px; font-family:arial'>20.54%</td>

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

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

  • Error Line 136, Column 99: end tag for "DIV" omitted, but its declaration does not permit this
    …l, Helvetica" size=2><div style='font-size:12px; font-family:arial'>20.54%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 136, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 136, Column 99: end tag for "FONT" omitted, but its declaration does not permit this
    …l, Helvetica" size=2><div style='font-size:12px; font-family:arial'>20.54%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 136, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 138, Column 231: end tag for "A" omitted, but its declaration does not permit this
    …lt="Kennedy Half Dollar" border=0></td><td><font face="Arial, Helvetica" size=…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 138, Column 9: start tag was here
    <tr><td><a href="http://www.coinflation.com/coins/1971-2007-Kennedy-Half-Dollar…
  • Error Line 138, Column 430: end tag for "FONT" omitted, but its declaration does not permit this
    …tml" title="1971-2013 Half Dollar Specification">1971-2013 Half Dollar</a></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 138, Column 236: start tag was here
    …ennedy Half Dollar" border=0></td><td><font face="Arial, Helvetica" size=2><a …
  • Error Line 139, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.50</td>

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

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

  • Error Line 139, Column 98: end tag for "DIV" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.50</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 139, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 139, Column 98: end tag for "FONT" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.50</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 139, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 140, Column 214: end tag for "FONT" omitted, but its declaration does not permit this
    …e" title="1971-2013 Half Dollar Melt Value Calculation">$0.1027413</a></b></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 140, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><b><a href="http://www.coinflation.com…
  • Error Line 141, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …l, Helvetica" size=2><div style='font-size:12px; font-family:arial'>20.54%</td>

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

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

  • Error Line 141, Column 99: end tag for "DIV" omitted, but its declaration does not permit this
    …l, Helvetica" size=2><div style='font-size:12px; font-family:arial'>20.54%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 141, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 141, Column 99: end tag for "FONT" omitted, but its declaration does not permit this
    …l, Helvetica" size=2><div style='font-size:12px; font-family:arial'>20.54%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 141, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 143, Column 449: end tag for "FONT" omitted, but its declaration does not permit this
    …1971-1978 Eisenhower Dollar Specification">1971-1978 Eisenhower Dollar</a></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 143, Column 241: start tag was here
    …lt="Ike Dollar" border=0></a></td><td><font face="Arial, Helvetica" size=2><a …
  • Error Line 144, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$1.00</td>

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

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

  • Error Line 144, Column 98: end tag for "DIV" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$1.00</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 144, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 144, Column 98: end tag for "FONT" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$1.00</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 144, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 145, Column 222: end tag for "FONT" omitted, but its declaration does not permit this
    …le="1971-1978 Eisenhower Dollar Melt Value Calculation">$0.2054839</a></b></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 145, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><b><a href="http://www.coinflation.com…
  • Error Line 146, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …l, Helvetica" size=2><div style='font-size:12px; font-family:arial'>20.54%</td>

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

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

  • Error Line 146, Column 99: end tag for "DIV" omitted, but its declaration does not permit this
    …l, Helvetica" size=2><div style='font-size:12px; font-family:arial'>20.54%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 146, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 146, Column 99: end tag for "FONT" omitted, but its declaration does not permit this
    …l, Helvetica" size=2><div style='font-size:12px; font-family:arial'>20.54%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 146, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 148, Column 257: end tag for "A" omitted, but its declaration does not permit this
    …Susan B. Anthony Dollar" border=0></td><td><font face="Arial, Helvetica" size=…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 148, Column 9: start tag was here
    <tr><td><a href="http://www.coinflation.com/coins/1979-1981-1999-Susan-B-Anthon…
  • Error Line 148, Column 487: end tag for "FONT" omitted, but its declaration does not permit this
    …1999 Susan B. Anthony Dollar Specification">1979-1981, 1999 SBA Dollar</a></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 148, Column 262: start tag was here
    … B. Anthony Dollar" border=0></td><td><font face="Arial, Helvetica" size=2><a …
  • Error Line 149, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$1.00</td>

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

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

  • Error Line 149, Column 98: end tag for "DIV" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$1.00</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 149, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 149, Column 98: end tag for "FONT" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$1.00</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 149, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 150, Column 240: end tag for "FONT" omitted, but its declaration does not permit this
    …1, 1999 Susan B. Anthony Dollar Melt Value Calculation">$0.0733862</a></b></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 150, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><b><a href="http://www.coinflation.com…
  • Error Line 151, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>7.33%</td>

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

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

  • Error Line 151, Column 98: end tag for "DIV" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>7.33%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 151, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 151, Column 98: end tag for "FONT" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>7.33%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 151, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 153, Column 240: end tag for "A" omitted, but its declaration does not permit this
    …1 alt="Sacajawea Dollar" border=0></td><td><font face="Arial, Helvetica" size=…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 153, Column 9: start tag was here
    <tr><td><a href="http://www.coinflation.com/coins/2000-2007-Sacagawea-Golden-Do…
  • Error Line 153, Column 460: end tag for "FONT" omitted, but its declaration does not permit this
    …2013 Sacagawea Golden Dollar Specification">2000-2013 Sacagawea Dollar</a></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 153, Column 245: start tag was here
    …="Sacajawea Dollar" border=0></td><td><font face="Arial, Helvetica" size=2><a …
  • Error Line 154, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$1.00</td>

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

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

  • Error Line 154, Column 98: end tag for "DIV" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$1.00</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 154, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 154, Column 98: end tag for "FONT" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$1.00</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 154, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 155, Column 230: end tag for "FONT" omitted, but its declaration does not permit this
    …00-2013 Sacagawea Golden Dollar Melt Value Calculation">$0.0635823</a></b></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 155, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><b><a href="http://www.coinflation.com…
  • Error Line 156, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>6.35%</td>

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

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

  • Error Line 156, Column 98: end tag for "DIV" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>6.35%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 156, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 156, Column 98: end tag for "FONT" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>6.35%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 156, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 158, Column 260: end tag for "A" omitted, but its declaration does not permit this
    …lt="Presidential Dollar" border=0></td><td><font face="Arial, Helvetica" size=…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 158, Column 9: start tag was here
    <tr><td><a href="http://www.coinflation.com/coins/2007-Presidential-Golden-Doll…
  • Error Line 158, Column 484: end tag for "FONT" omitted, but its declaration does not permit this
    …residential Golden Dollar Specification">2007-2013 Presidential Dollar</a></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 158, Column 265: start tag was here
    …residential Dollar" border=0></td><td><font face="Arial, Helvetica" size=2><a …
  • Error Line 159, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$1.00</td>

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

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

  • Error Line 159, Column 98: end tag for "DIV" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$1.00</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 159, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 159, Column 98: end tag for "FONT" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$1.00</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 159, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 160, Column 231: end tag for "FONT" omitted, but its declaration does not permit this
    …2013 Presidential Golden Dollar Melt Value Calculation">$0.0635823</a></b></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 160, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><b><a href="http://www.coinflation.com…
  • Error Line 161, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>6.35%</td>

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

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

  • Error Line 161, Column 98: end tag for "DIV" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>6.35%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 161, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 161, Column 98: end tag for "FONT" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>6.35%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 161, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 165, Column 44: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …e border=0 cellpadding=0 cellspacing=3><tr><td valign=middle><font style='font…

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

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

  • Error Line 165, Column 158: end tag for "FONT" omitted, but its declaration does not permit this
    …font:10px/12px arial, verdana'>Base metal coins not included above: &nbsp;</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 165, Column 67: start tag was here
    …0 cellspacing=3><tr><td valign=middle><font style='font:10px/12px arial, verda…
  • Error Line 170, Column 5: end tag for "FONT" omitted, but its declaration does not permit this
    </td></tr></table>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 163, Column 19: start tag was here
    <tr><td colspan=5><font face="Arial, Helvetica" size=1><br>* The U.S. Mint issu…
  • Error Line 171, Column 5: end tag for element "TD" which is not open
    </td></tr></table></td></tr></table></td></tr></table>

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

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

  • Error Line 171, Column 10: end tag for element "TR" which is not open
    </td></tr></table></td></tr></table></td></tr></table>

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

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

  • Error Line 171, Column 18: end tag for element "TABLE" which is not open
    </td></tr></table></td></tr></table></td></tr></table>

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

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

  • Error Line 171, Column 23: end tag for element "TD" which is not open
    </td></tr></table></td></tr></table></td></tr></table>

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

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

  • Error Line 171, Column 28: end tag for element "TR" which is not open
    </td></tr></table></td></tr></table></td></tr></table>

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

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

  • Error Line 171, Column 36: end tag for element "TABLE" which is not open
    </td></tr></table></td></tr></table></td></tr></table>

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

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

  • Error Line 171, Column 41: end tag for element "TD" which is not open
    </td></tr></table></td></tr></table></td></tr></table>

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

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

  • Error Line 171, Column 46: end tag for element "TR" which is not open
    </td></tr></table></td></tr></table></td></tr></table>

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

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

  • Error Line 171, Column 54: end tag for element "TABLE" which is not open
    </td></tr></table></td></tr></table></td></tr></table>

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

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

  • Error Line 180, Column 17: an attribute value must be a literal unless it contains only name characters
    <table width=100%><tr><td align=left>

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

  • Error Line 183, Column 22: an attribute value must be a literal unless it contains only name characters
    <hr noshade width=100% size=1 color="#999999">

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

  • Error Line 188, Column 9: end tag for "FONT" omitted, but its declaration does not permit this
    <br></td></tr></table>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 187, Column 107: start tag was here
    …om/up.gif" alt="up" width="10" height="14"> <font color="green"><b>0.04</b><br>
  • Error Line 188, Column 9: end tag for "FONT" omitted, but its declaration does not permit this
    <br></td></tr></table>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 184, Column 1: start tag was here
    <font face="Arial, Helvetica" size=2 color="#000000">
  • Error Line 190, Column 54: an attribute value must be a literal unless it contains only name characters
    <table border=0 cellpadding=0 cellspacing=0 width=100%><tr><td>

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

  • Error Line 191, Column 54: an attribute value must be a literal unless it contains only name characters
    <table border=0 cellpadding=1 cellspacing=0 width=100% bgcolor=#ffffff><tr><td>

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

  • Error Line 191, Column 64: an attribute value must be a literal unless it contains only name characters
    <table border=0 cellpadding=1 cellspacing=0 width=100% bgcolor=#ffffff><tr><td>

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

  • Error Line 192, Column 54: an attribute value must be a literal unless it contains only name characters
    <table border=0 cellpadding=0 cellspacing=1 width=100% bgcolor=#cccccc><tr><td>

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

  • Error Line 192, Column 64: an attribute value must be a literal unless it contains only name characters
    <table border=0 cellpadding=0 cellspacing=1 width=100% bgcolor=#cccccc><tr><td>

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

  • Error Line 193, Column 17: an attribute value must be a literal unless it contains only name characters
    <table width=100% bgcolor="#ffffff" border=0 cellpadding=4 cellspacing=0><tr bg…

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

  • Error Line 193, Column 86: an attribute value must be a literal unless it contains only name characters
    …llpadding=4 cellspacing=0><tr bgcolor=#cccccc><td bgcolor=#cccccc border=0  al…

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

  • Error Line 193, Column 106: an attribute value must be a literal unless it contains only name characters
    …ing=0><tr bgcolor=#cccccc><td bgcolor=#cccccc border=0  align=left colspan=2><…

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

  • Error Line 194, Column 13: an attribute value must be a literal unless it contains only name characters
    <td bgcolor=#cccccc border=0><font face="Arial, Helvetica" size=2><b>Face Value…

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

  • Error Line 194, Column 88: end tag for "FONT" omitted, but its declaration does not permit this
    …or=#cccccc border=0><font face="Arial, Helvetica" size=2><b>Face Value</b></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 194, Column 30: start tag was here
    <td bgcolor=#cccccc border=0><font face="Arial, Helvetica" size=2><b>Face Value…
  • Error Line 195, Column 65: end tag for "FONT" omitted, but its declaration does not permit this
    <td><font face="Arial, Helvetica" size=2><b>Silver Value</b></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 195, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><b>Silver Value</b></td>
  • Error Line 196, Column 75: end tag for "FONT" omitted, but its declaration does not permit this
    <td><font face="Arial, Helvetica" size=2><b>Silver % of Face Value</b></td></tr>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 196, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><b>Silver % of Face Value</b></td></tr>
  • Error Line 197, Column 239: end tag for "A" omitted, but its declaration does not permit this
    …Silver War Nickel Value" border=0></td><td><font face="Arial, Helvetica" size=…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 197, Column 9: start tag was here
    <tr><td><a href="http://www.coinflation.com/coins/1942-1945-Silver-War-Nickel-V…
  • Error Line 197, Column 440: end tag for "FONT" omitted, but its declaration does not permit this
    …ification">1942-1945 Nickel</a> **</td><td><font face="Arial, Helvetica" size=…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 197, Column 244: start tag was here
    …r War Nickel Value" border=0></td><td><font face="Arial, Helvetica" size=2><a …
  • Error Line 197, Column 528: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.05</td>

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

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

  • Error Line 197, Column 538: end tag for "DIV" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.05</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 197, Column 482: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 197, Column 538: end tag for "FONT" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.05</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 197, Column 445: start tag was here
    …tion">1942-1945 Nickel</a> **</td><td><font face="Arial, Helvetica" size=2><di…
  • Error Line 198, Column 215: end tag for "FONT" omitted, but its declaration does not permit this
    …title="1942-1945 Silver War Nickel Melt Value Calculation">$1.7323</a></b></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 198, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><b><a href="http://www.coinflation.com…
  • Error Line 199, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    … Helvetica" size=2><div style='font-size:12px; font-family:arial'>3464.72%</td>

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

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

  • Error Line 199, Column 101: end tag for "DIV" omitted, but its declaration does not permit this
    … Helvetica" size=2><div style='font-size:12px; font-family:arial'>3464.72%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 199, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 199, Column 101: end tag for "FONT" omitted, but its declaration does not permit this
    … Helvetica" size=2><div style='font-size:12px; font-family:arial'>3464.72%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 199, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 201, Column 468: end tag for "FONT" omitted, but its declaration does not permit this
    …e="1916-1945 Silver Mercury Dime Specification">1916-1945 Mercury Dime</a></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 201, Column 265: start tag was here
    …ver Dime Value" border=0></a></td><td><font face="Arial, Helvetica" size=2><a …
  • Error Line 202, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.10</td>

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

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

  • Error Line 202, Column 98: end tag for "DIV" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.10</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 202, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 202, Column 98: end tag for "FONT" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.10</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 202, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 203, Column 219: end tag for "FONT" omitted, but its declaration does not permit this
    …tle="1916-1945 Silver Mercury Dime Melt Value Calculation">$2.2273</a></b></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 203, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><b><a href="http://www.coinflation.com…
  • Error Line 204, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    … Helvetica" size=2><div style='font-size:12px; font-family:arial'>2227.32%</td>

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

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

  • Error Line 204, Column 101: end tag for "DIV" omitted, but its declaration does not permit this
    … Helvetica" size=2><div style='font-size:12px; font-family:arial'>2227.32%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 204, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 204, Column 101: end tag for "FONT" omitted, but its declaration does not permit this
    … Helvetica" size=2><div style='font-size:12px; font-family:arial'>2227.32%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 204, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 206, Column 451: end tag for "FONT" omitted, but its declaration does not permit this
    …" title="1946-1964 Silver Dime Specification">1946-1964 Roosevelt Dime</a></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 206, Column 252: start tag was here
    …elt Dime Value" border=0></a></td><td><font face="Arial, Helvetica" size=2><a …
  • Error Line 207, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.10</td>

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

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

  • Error Line 207, Column 98: end tag for "DIV" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.10</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 207, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 207, Column 98: end tag for "FONT" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.10</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 207, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 208, Column 213: end tag for "FONT" omitted, but its declaration does not permit this
    …alue" title="1946-1964 Silver Dime Melt Value Calculation">$2.2273</a></b></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 208, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><b><a href="http://www.coinflation.com…
  • Error Line 209, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    … Helvetica" size=2><div style='font-size:12px; font-family:arial'>2227.32%</td>

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

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

  • Error Line 209, Column 101: end tag for "DIV" omitted, but its declaration does not permit this
    … Helvetica" size=2><div style='font-size:12px; font-family:arial'>2227.32%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 209, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 209, Column 101: end tag for "FONT" omitted, but its declaration does not permit this
    … Helvetica" size=2><div style='font-size:12px; font-family:arial'>2227.32%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 209, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 211, Column 489: end tag for "FONT" omitted, but its declaration does not permit this
    …-1930 Silver Quarter Specification">1916-1930 Standing Liberty Quarter</a></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 211, Column 267: start tag was here
    … Quarter Value" border=0></a></td><td><font face="Arial, Helvetica" size=2><a …
  • Error Line 212, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.25</td>

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

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

  • Error Line 212, Column 98: end tag for "DIV" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.25</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 212, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 212, Column 98: end tag for "FONT" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.25</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 212, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 213, Column 226: end tag for "FONT" omitted, but its declaration does not permit this
    …e" title="1916-1930 Silver Quarter Melt Value Calculation">$5.5683</a></b></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 213, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><b><a href="http://www.coinflation.com…
  • Error Line 214, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    … Helvetica" size=2><div style='font-size:12px; font-family:arial'>2227.32%</td>

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

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

  • Error Line 214, Column 101: end tag for "DIV" omitted, but its declaration does not permit this
    … Helvetica" size=2><div style='font-size:12px; font-family:arial'>2227.32%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 214, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 214, Column 101: end tag for "FONT" omitted, but its declaration does not permit this
    … Helvetica" size=2><div style='font-size:12px; font-family:arial'>2227.32%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 214, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 216, Column 466: end tag for "FONT" omitted, but its declaration does not permit this
    …="1932-1964 Silver Quarter Specification">1932-1964 Washington Quarter</a></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 216, Column 256: start tag was here
    … Quarter Value" border=0></a></td><td><font face="Arial, Helvetica" size=2><a …
  • Error Line 217, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.25</td>

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

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

  • Error Line 217, Column 98: end tag for "DIV" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.25</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 217, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 217, Column 98: end tag for "FONT" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.25</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 217, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 218, Column 220: end tag for "FONT" omitted, but its declaration does not permit this
    …e" title="1932-1964 Silver Quarter Melt Value Calculation">$5.5683</a></b></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 218, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><b><a href="http://www.coinflation.com…
  • Error Line 219, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    … Helvetica" size=2><div style='font-size:12px; font-family:arial'>2227.32%</td>

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

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

  • Error Line 219, Column 101: end tag for "DIV" omitted, but its declaration does not permit this
    … Helvetica" size=2><div style='font-size:12px; font-family:arial'>2227.32%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 219, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 219, Column 101: end tag for "FONT" omitted, but its declaration does not permit this
    … Helvetica" size=2><div style='font-size:12px; font-family:arial'>2227.32%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 219, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 221, Column 549: end tag for "FONT" omitted, but its declaration does not permit this
    …ilver Walking Liberty Half Dollar Specification">1916-1947 Half Dollar</a></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 221, Column 317: start tag was here
    …f Dollar Value" border=0></a></td><td><font face="Arial, Helvetica" size=2><a …
  • Error Line 222, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.50</td>

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

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

  • Error Line 222, Column 98: end tag for "DIV" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.50</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 222, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 222, Column 98: end tag for "FONT" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.50</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 222, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 223, Column 250: end tag for "FONT" omitted, but its declaration does not permit this
    …ilver Walking Liberty Half Dollar Melt Value Calculation">$11.1366</a></b></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 223, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><b><a href="http://www.coinflation.com…
  • Error Line 224, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    … Helvetica" size=2><div style='font-size:12px; font-family:arial'>2227.32%</td>

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

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

  • Error Line 224, Column 101: end tag for "DIV" omitted, but its declaration does not permit this
    … Helvetica" size=2><div style='font-size:12px; font-family:arial'>2227.32%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 224, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 224, Column 101: end tag for "FONT" omitted, but its declaration does not permit this
    … Helvetica" size=2><div style='font-size:12px; font-family:arial'>2227.32%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 224, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 226, Column 505: end tag for "FONT" omitted, but its declaration does not permit this
    …ver Franklin Half Dollar Specification">1948-1963 Franklin Half Dollar</a></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 226, Column 278: start tag was here
    …in Half Dollar" border=0></a></td><td><font face="Arial, Helvetica" size=2><a …
  • Error Line 227, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.50</td>

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

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

  • Error Line 227, Column 98: end tag for "DIV" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.50</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 227, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 227, Column 98: end tag for "FONT" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.50</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 227, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 228, Column 236: end tag for "FONT" omitted, but its declaration does not permit this
    …-1963 Silver Franklin Half Dollar Melt Value Calculation">$11.1366</a></b></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 228, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><b><a href="http://www.coinflation.com…
  • Error Line 229, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    … Helvetica" size=2><div style='font-size:12px; font-family:arial'>2227.32%</td>

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

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

  • Error Line 229, Column 101: end tag for "DIV" omitted, but its declaration does not permit this
    … Helvetica" size=2><div style='font-size:12px; font-family:arial'>2227.32%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 229, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 229, Column 101: end tag for "FONT" omitted, but its declaration does not permit this
    … Helvetica" size=2><div style='font-size:12px; font-family:arial'>2227.32%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 229, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 231, Column 464: end tag for "FONT" omitted, but its declaration does not permit this
    …964 Silver Kennedy Half Dollar Specification">1964 Kennedy Half Dollar</a></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 231, Column 255: start tag was here
    …er half dollar" border=0></a></td><td><font face="Arial, Helvetica" size=2><a …
  • Error Line 232, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.50</td>

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

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

  • Error Line 232, Column 98: end tag for "DIV" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.50</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 232, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 232, Column 98: end tag for "FONT" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.50</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 232, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 233, Column 224: end tag for "FONT" omitted, but its declaration does not permit this
    …="1964 Silver Kennedy Half Dollar Melt Value Calculation">$11.1366</a></b></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 233, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><b><a href="http://www.coinflation.com…
  • Error Line 234, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    … Helvetica" size=2><div style='font-size:12px; font-family:arial'>2227.32%</td>

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

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

  • Error Line 234, Column 101: end tag for "DIV" omitted, but its declaration does not permit this
    … Helvetica" size=2><div style='font-size:12px; font-family:arial'>2227.32%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 234, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 234, Column 101: end tag for "FONT" omitted, but its declaration does not permit this
    … Helvetica" size=2><div style='font-size:12px; font-family:arial'>2227.32%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 234, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 236, Column 498: end tag for "FONT" omitted, but its declaration does not permit this
    … Kennedy Half Dollar Specification">1965-1970 Half Dollar (40% silver)</a></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 236, Column 269: start tag was here
    …er half dollar" border=0></a></td><td><font face="Arial, Helvetica" size=2><a …
  • Error Line 237, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.50</td>

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

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

  • Error Line 237, Column 98: end tag for "DIV" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.50</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 237, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 237, Column 98: end tag for "FONT" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$0.50</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 237, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 238, Column 233: end tag for "FONT" omitted, but its declaration does not permit this
    …65-1970 Silver Kennedy Half Dollar Melt Value Calculation">$4.5536</a></b></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 238, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><b><a href="http://www.coinflation.com…
  • Error Line 239, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …, Helvetica" size=2><div style='font-size:12px; font-family:arial'>910.72%</td>

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

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

  • Error Line 239, Column 100: end tag for "DIV" omitted, but its declaration does not permit this
    …, Helvetica" size=2><div style='font-size:12px; font-family:arial'>910.72%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 239, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 239, Column 100: end tag for "FONT" omitted, but its declaration does not permit this
    …, Helvetica" size=2><div style='font-size:12px; font-family:arial'>910.72%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 239, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 241, Column 468: end tag for "FONT" omitted, but its declaration does not permit this
    …"1878-1921 Silver Morgan Dollar Specification">1878-1921 Morgan Dollar</a></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 241, Column 262: start tag was here
    … Silver Dollar" border=0></a></td><td><font face="Arial, Helvetica" size=2><a …
  • Error Line 242, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$1.00</td>

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

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

  • Error Line 242, Column 98: end tag for "DIV" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$1.00</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 242, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 242, Column 98: end tag for "FONT" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$1.00</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 242, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 243, Column 222: end tag for "FONT" omitted, but its declaration does not permit this
    …e="1878-1921 Silver Morgan Dollar Melt Value Calculation">$23.8145</a></b></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 243, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><b><a href="http://www.coinflation.com…
  • Error Line 244, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    … Helvetica" size=2><div style='font-size:12px; font-family:arial'>2381.45%</td>

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

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

  • Error Line 244, Column 101: end tag for "DIV" omitted, but its declaration does not permit this
    … Helvetica" size=2><div style='font-size:12px; font-family:arial'>2381.45%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 244, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 244, Column 101: end tag for "FONT" omitted, but its declaration does not permit this
    … Helvetica" size=2><div style='font-size:12px; font-family:arial'>2381.45%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 244, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 246, Column 449: end tag for "FONT" omitted, but its declaration does not permit this
    …e="1921-1935 Silver Peace Dollar Specification">1921-1935 Peace Dollar</a></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 246, Column 246: start tag was here
    … Silver Dollar" border=0></a></td><td><font face="Arial, Helvetica" size=2><a …
  • Error Line 247, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$1.00</td>

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

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

  • Error Line 247, Column 98: end tag for "DIV" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$1.00</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 247, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 247, Column 98: end tag for "FONT" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$1.00</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 247, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 248, Column 220: end tag for "FONT" omitted, but its declaration does not permit this
    …le="1921-1935 Silver Peace Dollar Melt Value Calculation">$23.8145</a></b></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 248, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><b><a href="http://www.coinflation.com…
  • Error Line 249, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    … Helvetica" size=2><div style='font-size:12px; font-family:arial'>2381.45%</td>

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

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

  • Error Line 249, Column 101: end tag for "DIV" omitted, but its declaration does not permit this
    … Helvetica" size=2><div style='font-size:12px; font-family:arial'>2381.45%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 249, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 249, Column 101: end tag for "FONT" omitted, but its declaration does not permit this
    … Helvetica" size=2><div style='font-size:12px; font-family:arial'>2381.45%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 249, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 251, Column 497: end tag for "FONT" omitted, but its declaration does not permit this
    …Ike Dollar Specification">1971-1976 Eisenhower Dollar (40% silver)</a> ***</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 251, Column 260: start tag was here
    …ver Ike dollar" border=0></a></td><td><font face="Arial, Helvetica" size=2><a …
  • Error Line 252, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$1.00</td>

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

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

  • Error Line 252, Column 98: end tag for "DIV" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$1.00</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 252, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 252, Column 98: end tag for "FONT" omitted, but its declaration does not permit this
    …al, Helvetica" size=2><div style='font-size:12px; font-family:arial'>$1.00</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 252, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 253, Column 231: end tag for "FONT" omitted, but its declaration does not permit this
    …title="1971-1976 Silver Ike Dollar Melt Value Calculation">$9.7368</a></b></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 253, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><b><a href="http://www.coinflation.com…
  • Error Line 254, Column 88: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …, Helvetica" size=2><div style='font-size:12px; font-family:arial'>973.68%</td>

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

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

  • Error Line 254, Column 100: end tag for "DIV" omitted, but its declaration does not permit this
    …, Helvetica" size=2><div style='font-size:12px; font-family:arial'>973.68%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 254, Column 42: start tag was here
    …><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-family:…
  • Error Line 254, Column 100: end tag for "FONT" omitted, but its declaration does not permit this
    …, Helvetica" size=2><div style='font-size:12px; font-family:arial'>973.68%</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 254, Column 5: start tag was here
    <td><font face="Arial, Helvetica" size=2><div style='font-size:12px; font-famil…
  • Error Line 258, Column 44: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …e border=0 cellpadding=0 cellspacing=3><tr><td valign=middle><font style='font…

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

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

  • Error Line 258, Column 154: end tag for "FONT" omitted, but its declaration does not permit this
    …le='font:10px/12px arial, verdana'>Silver coins not included above: &nbsp;</td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 258, Column 67: start tag was here
    …0 cellspacing=3><tr><td valign=middle><font style='font:10px/12px arial, verda…
  • Error Line 263, Column 5: end tag for "FONT" omitted, but its declaration does not permit this
    </td></tr></table></td></tr></table></td></tr></table></td></tr></table>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 256, Column 19: start tag was here
    <tr><td colspan=5><font face="Arial, Helvetica" size=1><br>** The U.S. Mint iss…
  • Error Line 264, Column 9: end tag for element "TD" which is not open
    <br></td>

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

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

  • Error Line 265, Column 24: an attribute value must be a literal unless it contains only name characters
    <td valign=top width=25% align=right><br>

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

  • Error Line 265, Column 37: document type does not allow element "TD" here
    <td valign=top width=25% align=right><br>

    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 278, Column 54: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <table border=0 cellpadding=0 cellspacing=0 width=160><tr><td>

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

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

  • Error Line 279, Column 54: an attribute value must be a literal unless it contains only name characters
    <table border=0 cellpadding=1 cellspacing=0 width=100% bgcolor=#cccccc><tr><td>

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

  • Error Line 279, Column 64: an attribute value must be a literal unless it contains only name characters
    <table border=0 cellpadding=1 cellspacing=0 width=100% bgcolor=#cccccc><tr><td>

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

  • Error Line 280, Column 54: an attribute value must be a literal unless it contains only name characters
    … cellpadding=0 cellspacing=0 width=100% bgcolor=#ffffff><tr><td><table border=…

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

  • Error Line 280, Column 64: an attribute value must be a literal unless it contains only name characters
    …ng=0 cellspacing=0 width=100% bgcolor=#ffffff><tr><td><table border=0 cellspac…

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

  • Error Line 280, Column 133: an attribute value must be a literal unless it contains only name characters
    … cellspacing=0 cellpadding=2 width=100%><tr><td bgcolor="#cccccc" align=center…

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

  • Error Line 292, Column 5: end tag for "FONT" omitted, but its declaration does not permit this
    </td></tr>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 283, Column 1: start tag was here
    <font face="Arial, Helvetica" size=-2 color="#000000">
  • Error Line 295, Column 19: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <div align="right"><div id="sbad2">

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

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

  • Error Line 298, Column 31: end tag for "FONT" omitted, but its declaration does not permit this
    To Coinflation.com</b><br></td></tr></table>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 296, Column 39: start tag was here
    <table width=160><tr><td align=center><font face="Arial, Verdana, Helvetica" si…
  • Warning Line 299, Column 83: cannot generate system identifier for general entity "ai"
    …pi.ebay.com/ws/eBayISAPI.dll?EKServer&ai=maLpjp%7F%7C%7Dva&bdrcolor=cccccc&cid…

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

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

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

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

  • Error Line 299, Column 83: general entity "ai" not defined and no default entity
    …pi.ebay.com/ws/eBayISAPI.dll?EKServer&ai=maLpjp%7F%7C%7Dva&bdrcolor=cccccc&cid…

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

  • Error Line 299, Column 85: reference to entity "ai" for which no system identifier could be generated
    ….ebay.com/ws/eBayISAPI.dll?EKServer&ai=maLpjp%7F%7C%7Dva&bdrcolor=cccccc&cid=0…

    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 299, Column 82: entity was defined here
    …api.ebay.com/ws/eBayISAPI.dll?EKServer&ai=maLpjp%7F%7C%7Dva&bdrcolor=cccccc&ci…
  • Warning Line 299, Column 104: cannot generate system identifier for general entity "bdrcolor"
    …API.dll?EKServer&ai=maLpjp%7F%7C%7Dva&bdrcolor=cccccc&cid=0&eksize=10&encode=U…

    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 299, Column 104: general entity "bdrcolor" not defined and no default entity
    …API.dll?EKServer&ai=maLpjp%7F%7C%7Dva&bdrcolor=cccccc&cid=0&eksize=10&encode=U…

    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.

  • Error Line 299, Column 112: reference to entity "bdrcolor" for which no system identifier could be generated
    …EKServer&ai=maLpjp%7F%7C%7Dva&bdrcolor=cccccc&cid=0&eksize=10&encode=UTF-8&end…

    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 299, Column 103: entity was defined here
    …SAPI.dll?EKServer&ai=maLpjp%7F%7C%7Dva&bdrcolor=cccccc&cid=0&eksize=10&encode=…
  • Warning Line 299, Column 120: cannot generate system identifier for general entity "cid"
    …&ai=maLpjp%7F%7C%7Dva&bdrcolor=cccccc&cid=0&eksize=10&encode=UTF-8&endcolor=FF…

    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 299, Column 120: general entity "cid" not defined and no default entity
    …&ai=maLpjp%7F%7C%7Dva&bdrcolor=cccccc&cid=0&eksize=10&encode=UTF-8&endcolor=FF…

    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.

  • Error Line 299, Column 123: reference to entity "cid" for which no system identifier could be generated
    …=maLpjp%7F%7C%7Dva&bdrcolor=cccccc&cid=0&eksize=10&encode=UTF-8&endcolor=FF000…

    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 299, Column 119: entity was defined here
    …r&ai=maLpjp%7F%7C%7Dva&bdrcolor=cccccc&cid=0&eksize=10&encode=UTF-8&endcolor=F…
  • Warning Line 299, Column 126: cannot generate system identifier for general entity "eksize"
    …Lpjp%7F%7C%7Dva&bdrcolor=cccccc&cid=0&eksize=10&encode=UTF-8&endcolor=FF0000&e…

    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 299, Column 126: general entity "eksize" not defined and no default entity
    …Lpjp%7F%7C%7Dva&bdrcolor=cccccc&cid=0&eksize=10&encode=UTF-8&endcolor=FF0000&e…

    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.

  • Error Line 299, Column 132: reference to entity "eksize" for which no system identifier could be generated
    …F%7C%7Dva&bdrcolor=cccccc&cid=0&eksize=10&encode=UTF-8&endcolor=FF0000&endtime…

    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 299, Column 125: entity was defined here
    …aLpjp%7F%7C%7Dva&bdrcolor=cccccc&cid=0&eksize=10&encode=UTF-8&endcolor=FF0000&…
  • Warning Line 299, Column 136: cannot generate system identifier for general entity "encode"
    …%7Dva&bdrcolor=cccccc&cid=0&eksize=10&encode=UTF-8&endcolor=FF0000&endtime=y&f…

    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 299, Column 136: general entity "encode" not defined and no default entity
    …%7Dva&bdrcolor=cccccc&cid=0&eksize=10&encode=UTF-8&endcolor=FF0000&endtime=y&f…

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

  • Error Line 299, Column 142: reference to entity "encode" for which no system identifier could be generated
    …bdrcolor=cccccc&cid=0&eksize=10&encode=UTF-8&endcolor=FF0000&endtime=y&fbgcolo…

    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 299, Column 135: entity was defined here
    …C%7Dva&bdrcolor=cccccc&cid=0&eksize=10&encode=UTF-8&endcolor=FF0000&endtime=y&…
  • Warning Line 299, Column 149: cannot generate system identifier for general entity "endcolor"
    …r=cccccc&cid=0&eksize=10&encode=UTF-8&endcolor=FF0000&endtime=y&fbgcolor=eeeee…

    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 299, Column 149: general entity "endcolor" not defined and no default entity
    …r=cccccc&cid=0&eksize=10&encode=UTF-8&endcolor=FF0000&endtime=y&fbgcolor=eeeee…

    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.

  • Error Line 299, Column 157: reference to entity "endcolor" for which no system identifier could be generated
    …&cid=0&eksize=10&encode=UTF-8&endcolor=FF0000&endtime=y&fbgcolor=eeeeee&fntcol…

    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 299, Column 148: entity was defined here
    …or=cccccc&cid=0&eksize=10&encode=UTF-8&endcolor=FF0000&endtime=y&fbgcolor=eeee…
  • Warning Line 299, Column 165: cannot generate system identifier for general entity "endtime"
    …ksize=10&encode=UTF-8&endcolor=FF0000&endtime=y&fbgcolor=eeeeee&fntcolor=00000…

    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 299, Column 165: general entity "endtime" not defined and no default entity
    …ksize=10&encode=UTF-8&endcolor=FF0000&endtime=y&fbgcolor=eeeeee&fntcolor=00000…

    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.

  • Error Line 299, Column 172: reference to entity "endtime" for which no system identifier could be generated
    …0&encode=UTF-8&endcolor=FF0000&endtime=y&fbgcolor=eeeeee&fntcolor=000000&fs=0&…

    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 299, Column 164: entity was defined here
    …eksize=10&encode=UTF-8&endcolor=FF0000&endtime=y&fbgcolor=eeeeee&fntcolor=0000…
  • Warning Line 299, Column 175: cannot generate system identifier for general entity "fbgcolor"
    …ncode=UTF-8&endcolor=FF0000&endtime=y&fbgcolor=eeeeee&fntcolor=000000&fs=0&hdr…

    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 299, Column 175: general entity "fbgcolor" not defined and no default entity
    …ncode=UTF-8&endcolor=FF0000&endtime=y&fbgcolor=eeeeee&fntcolor=000000&fs=0&hdr…

    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.

  • Error Line 299, Column 183: reference to entity "fbgcolor" for which no system identifier could be generated
    …F-8&endcolor=FF0000&endtime=y&fbgcolor=eeeeee&fntcolor=000000&fs=0&hdrcolor=cc…

    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 299, Column 174: entity was defined here
    …encode=UTF-8&endcolor=FF0000&endtime=y&fbgcolor=eeeeee&fntcolor=000000&fs=0&hd…
  • Warning Line 299, Column 191: cannot generate system identifier for general entity "fntcolor"
    …olor=FF0000&endtime=y&fbgcolor=eeeeee&fntcolor=000000&fs=0&hdrcolor=cccccc&hdr…

    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 299, Column 191: general entity "fntcolor" not defined and no default entity
    …olor=FF0000&endtime=y&fbgcolor=eeeeee&fntcolor=000000&fs=0&hdrcolor=cccccc&hdr…

    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.

  • Error Line 299, Column 199: reference to entity "fntcolor" for which no system identifier could be generated
    …000&endtime=y&fbgcolor=eeeeee&fntcolor=000000&fs=0&hdrcolor=cccccc&hdrimage=1&…

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

  • Info Line 299, Column 190: entity was defined here
    …color=FF0000&endtime=y&fbgcolor=eeeeee&fntcolor=000000&fs=0&hdrcolor=cccccc&hd…
  • Warning Line 299, Column 207: cannot generate system identifier for general entity "fs"
    …ime=y&fbgcolor=eeeeee&fntcolor=000000&fs=0&hdrcolor=cccccc&hdrimage=1&hdrsrch=…

    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 299, Column 207: general entity "fs" not defined and no default entity
    …ime=y&fbgcolor=eeeeee&fntcolor=000000&fs=0&hdrcolor=cccccc&hdrimage=1&hdrsrch=…

    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.

  • Error Line 299, Column 209: reference to entity "fs" for which no system identifier could be generated
    …e=y&fbgcolor=eeeeee&fntcolor=000000&fs=0&hdrcolor=cccccc&hdrimage=1&hdrsrch=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 299, Column 206: entity was defined here
    …time=y&fbgcolor=eeeeee&fntcolor=000000&fs=0&hdrcolor=cccccc&hdrimage=1&hdrsrch…
  • Warning Line 299, Column 212: cannot generate system identifier for general entity "hdrcolor"
    …&fbgcolor=eeeeee&fntcolor=000000&fs=0&hdrcolor=cccccc&hdrimage=1&hdrsrch=n&img…

    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 299, Column 212: general entity "hdrcolor" not defined and no default entity
    …&fbgcolor=eeeeee&fntcolor=000000&fs=0&hdrcolor=cccccc&hdrimage=1&hdrsrch=n&img…

    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.

  • Error Line 299, Column 220: reference to entity "hdrcolor" for which no system identifier could be generated
    …r=eeeeee&fntcolor=000000&fs=0&hdrcolor=cccccc&hdrimage=1&hdrsrch=n&img=y&lnkco…

    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 299, Column 211: entity was defined here
    …y&fbgcolor=eeeeee&fntcolor=000000&fs=0&hdrcolor=cccccc&hdrimage=1&hdrsrch=n&im…
  • Warning Line 299, Column 228: cannot generate system identifier for general entity "hdrimage"
    …&fntcolor=000000&fs=0&hdrcolor=cccccc&hdrimage=1&hdrsrch=n&img=y&lnkcolor=0000…

    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 299, Column 228: general entity "hdrimage" not defined and no default entity
    …&fntcolor=000000&fs=0&hdrcolor=cccccc&hdrimage=1&hdrsrch=n&img=y&lnkcolor=0000…

    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.

  • Error Line 299, Column 236: reference to entity "hdrimage" for which no system identifier could be generated
    …r=000000&fs=0&hdrcolor=cccccc&hdrimage=1&hdrsrch=n&img=y&lnkcolor=0000FF&logo=…

    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 299, Column 227: entity was defined here
    …e&fntcolor=000000&fs=0&hdrcolor=cccccc&hdrimage=1&hdrsrch=n&img=y&lnkcolor=000…
  • Warning Line 299, Column 239: cannot generate system identifier for general entity "hdrsrch"
    …00000&fs=0&hdrcolor=cccccc&hdrimage=1&hdrsrch=n&img=y&lnkcolor=0000FF&logo=3&n…

    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 299, Column 239: general entity "hdrsrch" not defined and no default entity
    …00000&fs=0&hdrcolor=cccccc&hdrimage=1&hdrsrch=n&img=y&lnkcolor=0000FF&logo=3&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.

  • Error Line 299, Column 246: reference to entity "hdrsrch" for which no system identifier could be generated
    …s=0&hdrcolor=cccccc&hdrimage=1&hdrsrch=n&img=y&lnkcolor=0000FF&logo=3&num=25&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 299, Column 238: entity was defined here
    …000000&fs=0&hdrcolor=cccccc&hdrimage=1&hdrsrch=n&img=y&lnkcolor=0000FF&logo=3&…
  • Warning Line 299, Column 249: cannot generate system identifier for general entity "img"
    …&hdrcolor=cccccc&hdrimage=1&hdrsrch=n&img=y&lnkcolor=0000FF&logo=3&num=25&numb…

    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 299, Column 249: general entity "img" not defined and no default entity
    …&hdrcolor=cccccc&hdrimage=1&hdrsrch=n&img=y&lnkcolor=0000FF&logo=3&num=25&numb…

    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.

  • Error Line 299, Column 252: reference to entity "img" for which no system identifier could be generated
    …rcolor=cccccc&hdrimage=1&hdrsrch=n&img=y&lnkcolor=0000FF&logo=3&num=25&numbid=…

    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 299, Column 248: entity was defined here
    …0&hdrcolor=cccccc&hdrimage=1&hdrsrch=n&img=y&lnkcolor=0000FF&logo=3&num=25&num…
  • Warning Line 299, Column 255: cannot generate system identifier for general entity "lnkcolor"
    …lor=cccccc&hdrimage=1&hdrsrch=n&img=y&lnkcolor=0000FF&logo=3&num=25&numbid=n&p…

    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 299, Column 255: general entity "lnkcolor" not defined and no default entity
    …lor=cccccc&hdrimage=1&hdrsrch=n&img=y&lnkcolor=0000FF&logo=3&num=25&numbid=n&p…

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

  • Error Line 299, Column 263: reference to entity "lnkcolor" for which no system identifier could be generated
    …cc&hdrimage=1&hdrsrch=n&img=y&lnkcolor=0000FF&logo=3&num=25&numbid=n&paypal=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 299, Column 254: entity was defined here
    …olor=cccccc&hdrimage=1&hdrsrch=n&img=y&lnkcolor=0000FF&logo=3&num=25&numbid=n&…
  • Warning Line 299, Column 271: cannot generate system identifier for general entity "logo"
    …age=1&hdrsrch=n&img=y&lnkcolor=0000FF&logo=3&num=25&numbid=n&paypal=n&popup=y&…

    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 299, Column 271: general entity "logo" not defined and no default entity
    …age=1&hdrsrch=n&img=y&lnkcolor=0000FF&logo=3&num=25&numbid=n&paypal=n&popup=y&…

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

  • Error Line 299, Column 275: reference to entity "logo" for which no system identifier could be generated
    …1&hdrsrch=n&img=y&lnkcolor=0000FF&logo=3&num=25&numbid=n&paypal=n&popup=y&prvd…

    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 299, Column 270: entity was defined here
    …mage=1&hdrsrch=n&img=y&lnkcolor=0000FF&logo=3&num=25&numbid=n&paypal=n&popup=y…
  • Warning Line 299, Column 278: cannot generate system identifier for general entity "num"
    …drsrch=n&img=y&lnkcolor=0000FF&logo=3&num=25&numbid=n&paypal=n&popup=y&prvd=9&…

    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 299, Column 278: general entity "num" not defined and no default entity
    …drsrch=n&img=y&lnkcolor=0000FF&logo=3&num=25&numbid=n&paypal=n&popup=y&prvd=9&…

    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.

  • Error Line 299, Column 281: reference to entity "num" for which no system identifier could be generated
    …rch=n&img=y&lnkcolor=0000FF&logo=3&num=25&numbid=n&paypal=n&popup=y&prvd=9&que…

    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 299, Column 277: entity was defined here
    …hdrsrch=n&img=y&lnkcolor=0000FF&logo=3&num=25&numbid=n&paypal=n&popup=y&prvd=9…
  • Warning Line 299, Column 285: cannot generate system identifier for general entity "numbid"
    …n&img=y&lnkcolor=0000FF&logo=3&num=25&numbid=n&paypal=n&popup=y&prvd=9&query=c…

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

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

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

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

  • Error Line 299, Column 285: general entity "numbid" not defined and no default entity
    …n&img=y&lnkcolor=0000FF&logo=3&num=25&numbid=n&paypal=n&popup=y&prvd=9&query=c…

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

  • Error Line 299, Column 291: reference to entity "numbid" for which no system identifier could be generated
    …y&lnkcolor=0000FF&logo=3&num=25&numbid=n&paypal=n&popup=y&prvd=9&query=coinfla…

    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 299, Column 284: entity was defined here
    …=n&img=y&lnkcolor=0000FF&logo=3&num=25&numbid=n&paypal=n&popup=y&prvd=9&query=…
  • Warning Line 299, Column 294: cannot generate system identifier for general entity "paypal"
    …nkcolor=0000FF&logo=3&num=25&numbid=n&paypal=n&popup=y&prvd=9&query=coinflatio…

    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 299, Column 294: general entity "paypal" not defined and no default entity
    …nkcolor=0000FF&logo=3&num=25&numbid=n&paypal=n&popup=y&prvd=9&query=coinflatio…

    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.

  • Error Line 299, Column 300: reference to entity "paypal" for which no system identifier could be generated
    …r=0000FF&logo=3&num=25&numbid=n&paypal=n&popup=y&prvd=9&query=coinflation+-ant…

    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 299, Column 293: entity was defined here
    …lnkcolor=0000FF&logo=3&num=25&numbid=n&paypal=n&popup=y&prvd=9&query=coinflati…
  • Warning Line 299, Column 303: cannot generate system identifier for general entity "popup"
    …000FF&logo=3&num=25&numbid=n&paypal=n&popup=y&prvd=9&query=coinflation+-antiqu…

    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 299, Column 303: general entity "popup" not defined and no default entity
    …000FF&logo=3&num=25&numbid=n&paypal=n&popup=y&prvd=9&query=coinflation+-antiqu…

    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.

  • Error Line 299, Column 308: reference to entity "popup" for which no system identifier could be generated
    …&logo=3&num=25&numbid=n&paypal=n&popup=y&prvd=9&query=coinflation+-antique&r0=…

    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 299, Column 302: entity was defined here
    …0000FF&logo=3&num=25&numbid=n&paypal=n&popup=y&prvd=9&query=coinflation+-antiq…
  • Warning Line 299, Column 311: cannot generate system identifier for general entity "prvd"
    …go=3&num=25&numbid=n&paypal=n&popup=y&prvd=9&query=coinflation+-antique&r0=4&s…

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

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

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

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

  • Error Line 299, Column 311: general entity "prvd" not defined and no default entity
    …go=3&num=25&numbid=n&paypal=n&popup=y&prvd=9&query=coinflation+-antique&r0=4&s…

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

  • Error Line 299, Column 315: reference to entity "prvd" for which no system identifier could be generated
    …&num=25&numbid=n&paypal=n&popup=y&prvd=9&query=coinflation+-antique&r0=4&shipc…

    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 299, Column 310: entity was defined here
    …ogo=3&num=25&numbid=n&paypal=n&popup=y&prvd=9&query=coinflation+-antique&r0=4&…
  • Warning Line 299, Column 318: cannot generate system identifier for general entity "query"
    …m=25&numbid=n&paypal=n&popup=y&prvd=9&query=coinflation+-antique&r0=4&shipcost…

    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 299, Column 318: general entity "query" not defined and no default entity
    …m=25&numbid=n&paypal=n&popup=y&prvd=9&query=coinflation+-antique&r0=4&shipcost…

    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.

  • Error Line 299, Column 323: reference to entity "query" for which no system identifier could be generated
    …numbid=n&paypal=n&popup=y&prvd=9&query=coinflation+-antique&r0=4&shipcost=n&si…

    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 299, Column 317: entity was defined here
    …um=25&numbid=n&paypal=n&popup=y&prvd=9&query=coinflation+-antique&r0=4&shipcos…
  • Warning Line 299, Column 345: cannot generate system identifier for general entity "r0"
    …p=y&prvd=9&query=coinflation+-antique&r0=4&shipcost=n&sid=Linked+Auctions&site…

    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 299, Column 345: general entity "r0" not defined and no default entity
    …p=y&prvd=9&query=coinflation+-antique&r0=4&shipcost=n&sid=Linked+Auctions&site…

    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.

  • Error Line 299, Column 347: reference to entity "r0" for which no system identifier could be generated
    …y&prvd=9&query=coinflation+-antique&r0=4&shipcost=n&sid=Linked+Auctions&siteid…

    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 299, Column 344: entity was defined here
    …up=y&prvd=9&query=coinflation+-antique&r0=4&shipcost=n&sid=Linked+Auctions&sit…
  • Warning Line 299, Column 350: cannot generate system identifier for general entity "shipcost"
    …rvd=9&query=coinflation+-antique&r0=4&shipcost=n&sid=Linked+Auctions&siteid=0&…

    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 299, Column 350: general entity "shipcost" not defined and no default entity
    …rvd=9&query=coinflation+-antique&r0=4&shipcost=n&sid=Linked+Auctions&siteid=0&…

    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.

  • Error Line 299, Column 358: reference to entity "shipcost" for which no system identifier could be generated
    …ery=coinflation+-antique&r0=4&shipcost=n&sid=Linked+Auctions&siteid=0&sort=Met…

    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 299, Column 349: entity was defined here
    …prvd=9&query=coinflation+-antique&r0=4&shipcost=n&sid=Linked+Auctions&siteid=0…
  • Warning Line 299, Column 361: cannot generate system identifier for general entity "sid"
    …=coinflation+-antique&r0=4&shipcost=n&sid=Linked+Auctions&siteid=0&sort=MetaEn…

    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 299, Column 361: general entity "sid" not defined and no default entity
    …=coinflation+-antique&r0=4&shipcost=n&sid=Linked+Auctions&siteid=0&sort=MetaEn…

    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.

  • Error Line 299, Column 364: reference to entity "sid" for which no system identifier could be generated
    …inflation+-antique&r0=4&shipcost=n&sid=Linked+Auctions&siteid=0&sort=MetaEndSo…

    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 299, Column 360: entity was defined here
    …y=coinflation+-antique&r0=4&shipcost=n&sid=Linked+Auctions&siteid=0&sort=MetaE…
  • Warning Line 299, Column 381: cannot generate system identifier for general entity "siteid"
    …e&r0=4&shipcost=n&sid=Linked+Auctions&siteid=0&sort=MetaEndSort&sortby=endtime…

    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 299, Column 381: general entity "siteid" not defined and no default entity
    …e&r0=4&shipcost=n&sid=Linked+Auctions&siteid=0&sort=MetaEndSort&sortby=endtime…

    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.

  • Error Line 299, Column 387: reference to entity "siteid" for which no system identifier could be generated
    …&shipcost=n&sid=Linked+Auctions&siteid=0&sort=MetaEndSort&sortby=endtime&sortd…

    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 299, Column 380: entity was defined here
    …ue&r0=4&shipcost=n&sid=Linked+Auctions&siteid=0&sort=MetaEndSort&sortby=endtim…
  • Warning Line 299, Column 390: cannot generate system identifier for general entity "sort"
    …ipcost=n&sid=Linked+Auctions&siteid=0&sort=MetaEndSort&sortby=endtime&sortdir=…

    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 299, Column 390: general entity "sort" not defined and no default entity
    …ipcost=n&sid=Linked+Auctions&siteid=0&sort=MetaEndSort&sortby=endtime&sortdir=…

    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.

  • Error Line 299, Column 394: reference to entity "sort" for which no system identifier could be generated
    …st=n&sid=Linked+Auctions&siteid=0&sort=MetaEndSort&sortby=endtime&sortdir=asc&…

    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 299, Column 389: entity was defined here
    …hipcost=n&sid=Linked+Auctions&siteid=0&sort=MetaEndSort&sortby=endtime&sortdir…
  • Warning Line 299, Column 407: cannot generate system identifier for general entity "sortby"
    …ed+Auctions&siteid=0&sort=MetaEndSort&sortby=endtime&sortdir=asc&srchdesc=y&tb…

    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 299, Column 407: general entity "sortby" not defined and no default entity
    …ed+Auctions&siteid=0&sort=MetaEndSort&sortby=endtime&sortdir=asc&srchdesc=y&tb…

    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.

  • Error Line 299, Column 413: reference to entity "sortby" for which no system identifier could be generated
    …tions&siteid=0&sort=MetaEndSort&sortby=endtime&sortdir=asc&srchdesc=y&tbgcolor…

    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 299, Column 406: entity was defined here
    …ked+Auctions&siteid=0&sort=MetaEndSort&sortby=endtime&sortdir=asc&srchdesc=y&t…
  • Warning Line 299, Column 422: cannot generate system identifier for general entity "sortdir"
    …eid=0&sort=MetaEndSort&sortby=endtime&sortdir=asc&srchdesc=y&tbgcolor=FFFFFF&t…

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

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

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

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

  • Error Line 299, Column 422: general entity "sortdir" not defined and no default entity
    …eid=0&sort=MetaEndSort&sortby=endtime&sortdir=asc&srchdesc=y&tbgcolor=FFFFFF&t…

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

  • Error Line 299, Column 429: reference to entity "sortdir" for which no system identifier could be generated
    …ort=MetaEndSort&sortby=endtime&sortdir=asc&srchdesc=y&tbgcolor=FFFFFF&tlecolor…

    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 299, Column 421: entity was defined here
    …teid=0&sort=MetaEndSort&sortby=endtime&sortdir=asc&srchdesc=y&tbgcolor=FFFFFF&…
  • Warning Line 299, Column 434: cannot generate system identifier for general entity "srchdesc"
    …etaEndSort&sortby=endtime&sortdir=asc&srchdesc=y&tbgcolor=FFFFFF&tlecolor=cccc…

    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 299, Column 434: general entity "srchdesc" not defined and no default entity
    …etaEndSort&sortby=endtime&sortdir=asc&srchdesc=y&tbgcolor=FFFFFF&tlecolor=cccc…

    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.

  • Error Line 299, Column 442: reference to entity "srchdesc" for which no system identifier could be generated
    …rt&sortby=endtime&sortdir=asc&srchdesc=y&tbgcolor=FFFFFF&tlecolor=cccccc&tlefs…

    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 299, Column 433: entity was defined here
    …MetaEndSort&sortby=endtime&sortdir=asc&srchdesc=y&tbgcolor=FFFFFF&tlecolor=ccc…
  • Warning Line 299, Column 445: cannot generate system identifier for general entity "tbgcolor"
    …sortby=endtime&sortdir=asc&srchdesc=y&tbgcolor=FFFFFF&tlecolor=cccccc&tlefs=0&…

    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 299, Column 445: general entity "tbgcolor" not defined and no default entity
    …sortby=endtime&sortdir=asc&srchdesc=y&tbgcolor=FFFFFF&tlecolor=cccccc&tlefs=0&…

    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.

  • Error Line 299, Column 453: reference to entity "tbgcolor" for which no system identifier could be generated
    …ndtime&sortdir=asc&srchdesc=y&tbgcolor=FFFFFF&tlecolor=cccccc&tlefs=0&tlfcolor…

    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 299, Column 444: entity was defined here
    …&sortby=endtime&sortdir=asc&srchdesc=y&tbgcolor=FFFFFF&tlecolor=cccccc&tlefs=0…
  • Warning Line 299, Column 461: cannot generate system identifier for general entity "tlecolor"
    …ortdir=asc&srchdesc=y&tbgcolor=FFFFFF&tlecolor=cccccc&tlefs=0&tlfcolor=000000&…

    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 299, Column 461: general entity "tlecolor" not defined and no default entity
    …ortdir=asc&srchdesc=y&tbgcolor=FFFFFF&tlecolor=cccccc&tlefs=0&tlfcolor=000000&…

    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.

  • Error Line 299, Column 469: reference to entity "tlecolor" for which no system identifier could be generated
    …sc&srchdesc=y&tbgcolor=FFFFFF&tlecolor=cccccc&tlefs=0&tlfcolor=000000&toolid=1…

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

  • Info Line 299, Column 460: entity was defined here
    …sortdir=asc&srchdesc=y&tbgcolor=FFFFFF&tlecolor=cccccc&tlefs=0&tlfcolor=000000…
  • Warning Line 299, Column 477: cannot generate system identifier for general entity "tlefs"
    …esc=y&tbgcolor=FFFFFF&tlecolor=cccccc&tlefs=0&tlfcolor=000000&toolid=10004&tra…

    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 299, Column 477: general entity "tlefs" not defined and no default entity
    …esc=y&tbgcolor=FFFFFF&tlecolor=cccccc&tlefs=0&tlfcolor=000000&toolid=10004&tra…

    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.

  • Error Line 299, Column 482: reference to entity "tlefs" for which no system identifier could be generated
    …&tbgcolor=FFFFFF&tlecolor=cccccc&tlefs=0&tlfcolor=000000&toolid=10004&track=53…

    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 299, Column 476: entity was defined here
    …desc=y&tbgcolor=FFFFFF&tlecolor=cccccc&tlefs=0&tlfcolor=000000&toolid=10004&tr…
  • Warning Line 299, Column 485: cannot generate system identifier for general entity "tlfcolor"
    …gcolor=FFFFFF&tlecolor=cccccc&tlefs=0&tlfcolor=000000&toolid=10004&track=53368…

    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 299, Column 485: general entity "tlfcolor" not defined and no default entity
    …gcolor=FFFFFF&tlecolor=cccccc&tlefs=0&tlfcolor=000000&toolid=10004&track=53368…

    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.

  • Error Line 299, Column 493: reference to entity "tlfcolor" for which no system identifier could be generated
    …FFFFF&tlecolor=cccccc&tlefs=0&tlfcolor=000000&toolid=10004&track=5336886493&wa…

    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 299, Column 484: entity was defined here
    …bgcolor=FFFFFF&tlecolor=cccccc&tlefs=0&tlfcolor=000000&toolid=10004&track=5336…
  • Error Line 299, Column 507: reference to entity "toolid" for which no system identifier could be generated
    …=cccccc&tlefs=0&tlfcolor=000000&toolid=10004&track=5336886493&watchcat=253&wid…

    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 72, Column 101: entity was defined here
    …00-19255-0/1?icep_ff3=2&pub=5574895479&toolid=10001&campid=5336886491&customid…
  • Warning Line 299, Column 514: cannot generate system identifier for general entity "track"
    …&tlefs=0&tlfcolor=000000&toolid=10004&track=5336886493&watchcat=253&width=570"…

    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 299, Column 514: general entity "track" not defined and no default entity
    …&tlefs=0&tlfcolor=000000&toolid=10004&track=5336886493&watchcat=253&width=570"…

    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.

  • Error Line 299, Column 519: reference to entity "track" for which no system identifier could be generated
    …s=0&tlfcolor=000000&toolid=10004&track=5336886493&watchcat=253&width=570"></sc…

    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 299, Column 513: entity was defined here
    …c&tlefs=0&tlfcolor=000000&toolid=10004&track=5336886493&watchcat=253&width=570…
  • Warning Line 299, Column 531: cannot generate system identifier for general entity "watchcat"
    …tlfcolor=000000&toolid=10004&track=5336886493&watchcat=253&width=570"></script>

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

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

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

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

  • Error Line 299, Column 531: general entity "watchcat" not defined and no default entity
    …tlfcolor=000000&toolid=10004&track=5336886493&watchcat=253&width=570"></script>

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

  • Error Line 299, Column 539: reference to entity "watchcat" for which no system identifier could be generated
    …tlfcolor=000000&toolid=10004&track=5336886493&watchcat=253&width=570"></script>

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

  • Info Line 299, Column 530: entity was defined here
    …tlfcolor=000000&toolid=10004&track=5336886493&watchcat=253&width=570"></script>
  • Warning Line 299, Column 544: cannot generate system identifier for general entity "width"
    …tlfcolor=000000&toolid=10004&track=5336886493&watchcat=253&width=570"></script>

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

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

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

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

  • Error Line 299, Column 544: general entity "width" not defined and no default entity
    …tlfcolor=000000&toolid=10004&track=5336886493&watchcat=253&width=570"></script>

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

  • Error Line 299, Column 549: reference to entity "width" for which no system identifier could be generated
    …tlfcolor=000000&toolid=10004&track=5336886493&watchcat=253&width=570"></script>

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

  • Info Line 299, Column 543: entity was defined here
    …tlfcolor=000000&toolid=10004&track=5336886493&watchcat=253&width=570"></script>
  • Error Line 299, Column 554: required attribute "TYPE" not specified
    …tlfcolor=000000&toolid=10004&track=5336886493&watchcat=253&width=570"></script>

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

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

  • Error Line 301, Column 6: end tag for "FONT" omitted, but its declaration does not permit this
    </div><br><br><br><div align="right">
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 300, Column 5: start tag was here
    <br><font size=1><a href="http://www.coinflation.com/ebaylink.html" class="ates…
  • Warning Line 302, Column 73: cannot generate system identifier for general entity "tl"
    …er.com/Category/Category.aspx?catId=4&tl=true" title="Gold coins for sale at C…

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

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

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

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

  • Error Line 302, Column 73: general entity "tl" not defined and no default entity
    …er.com/Category/Category.aspx?catId=4&tl=true" title="Gold coins for sale at C…

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

  • Error Line 302, Column 75: reference to entity "tl" for which no system identifier could be generated
    ….com/Category/Category.aspx?catId=4&tl=true" title="Gold coins for sale at Col…

    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 302, Column 72: entity was defined here
    …ner.com/Category/Category.aspx?catId=4&tl=true" title="Gold coins for sale at …
  • Error Line 303, Column 132: required attribute "ALT" not specified
    …bar values and calculators"><img src="gold_gram_bars.jpg" border=0></a><br><br>

    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 304, Column 138: required attribute "ALT" not specified
    …r values and calculators"><img src="silver_gram_bars.jpg" border=0></a><br><br>

    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 307, Column 89: required attribute "TYPE" not specified
    …f-8" src='http://adn.ebay.com/files/js/min/ebay_activeContent-min.js'></script>

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

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

  • Error Line 309, Column 551: delimiter "'" invalid: only S separators and TAGC allowed here
    …ed=' + isFlashEnabled + '&pageTitle=' + _epn__pageTitle + '"></scr' + 'ipt>' );
  • Error Line 309, Column 551: end tag for element "SCR" which is not open
    …ed=' + isFlashEnabled + '&pageTitle=' + _epn__pageTitle + '"></scr' + 'ipt>' );

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

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

  • Error Line 312, Column 5: end tag for "DIV" omitted, but its declaration does not permit this
    </td></tr>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 295, Column 1: start tag was here
    <div align="right"><div id="sbad2">
  • Error Line 312, Column 5: end tag for "FONT" omitted, but its declaration does not permit this
    </td></tr>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 277, Column 5: start tag was here
    <br><font face="Arial, Helvetica" size=2 color="#000000">
  • Error Line 312, Column 10: end tag for element "TR" which is not open
    </td></tr>

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

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

  • Error Line 313, Column 4: document type does not allow element "TR" here
    <tr><td colspan=2 align=center><br><br>

    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 317, Column 13: there is no attribute "SIZE"
    <table size="100%"><tr><td width="640" align=left valign=top>

    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 318, Column 88: document type does not allow element "UL" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …00"><b>Also on Coinflation.com:</b><ul><li><a href="http://www.coinflation.com…

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

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

  • Error Line 322, Column 34: there is no attribute "DATA-SIZE"
    <div class="g-plusone" data-size="tall" data-annotation="inline" data-width="30…

    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 322, Column 57: there is no attribute "DATA-ANNOTATION"
    …one" data-size="tall" data-annotation="inline" data-width="300" data-href="htt…

    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 322, Column 77: there is no attribute "DATA-WIDTH"
    …" data-annotation="inline" data-width="300" data-href="http://www.coinflation.…

    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 322, Column 93: there is no attribute "DATA-HREF"
    …tation="inline" data-width="300" data-href="http://www.coinflation.com/"></div>

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

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

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

  • Error Line 322, Column 122: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …tation="inline" data-width="300" data-href="http://www.coinflation.com/"></div>

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

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

  • Error Line 333, Column 5: end tag for "FONT" omitted, but its declaration does not permit this
    </td><td width="320" align="right" valign="top">
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 320, Column 1: start tag was here
    <font face="Arial, Helvetica" size=2><b>Other Pages:</b><br><br><a href="http:/…
  • Error Line 348, Column 13: end tag for "FONT" omitted, but its declaration does not permit this
    <br><br></td></tr></table>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 347, Column 1: start tag was here
    <font face="Arial, Helvetica" size=1>
  • Error Line 348, Column 13: end tag for "DIV" omitted, but its declaration does not permit this
    <br><br></td></tr></table>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 315, Column 13: start tag was here
    <br><br><br><div align="center">
  • Error Line 348, Column 26: end tag for element "TABLE" which is not open
    <br><br></td></tr></table>

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

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

  • Error Line 357, Column 31: end tag for "DIV" omitted, but its declaration does not permit this
    } catch(err) {}</script></body></html>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 24, Column 25: start tag was here
    <body bgcolor="#ffffff"><div align="center">

Visitor Analysis

Daily Visitor
  • 4.083 visits
Daily Visitor