Hot Searches: Grammy Awards 2013 Dr. Oz Flat Belly Plan Home Depot Hiring Weather Sign In Breaking News:  New England begins the big dig-out after epic snow February's Best Bargains From ...

compuserve.com
  • Domain Name
    compuserve.com
  • Favicon
  • Google Page Rank
    6
  • Alexa Rank
    #38337
  • Page Size
    21.9 KB
  • Ip Address
    64.12.128.199
  • Heading
    H1: 0, H2: 0, H3: 14, H4: 8, H5: 0, H6: 0
  • Images
    5 GIF, 7 JPG, 0 PNG

Website Meta Analysis

  • Title
    CompuServe.com - Home
  • Meta Keyword
  • Meta Description
        Hot Searches: Grammy Awards 2013 Dr. Oz Flat Belly Plan Home Depot Hiring Weather Sign In Breaking News:  New England begins the big dig-out after epic snow February's Best Bargains From chocolate goodies to luggage, find out this month's ...

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    64.12.128.199
  • Domain Age
    3 Years, 11 Months, 22 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Sun, 10 Feb 2013 05:19:16 GMT
  • server: Apache
  • content-type: text/html;charset=UTF-8
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

Domain Name.......... compuserve.com
Creation Date........ 1988-10-06
Registration Date.... 2009-10-03
Expiry Date.......... 2012-10-06
Organisation Name.... AOL Inc.
Organisation Address. 22000 AOL Way
Organisation Address.
Organisation Address.
Organisation Address. Dulles
Organisation Address. 20166
Organisation Address. VA
Organisation Address. UNITED STATES

Admin Name........... Domain Admin
Admin Address........ AOL Inc.
Admin Address........ 22000 AOL Way
Admin Address........
Admin Address. Dulles
Admin Address........ 20166
Admin Address........ VA
Admin Address........ UNITED STATES
Admin Email.......... email
Admin Phone.......... +1.7032654670
Admin Fax............

Tech Name............ Domain Admin
Tech Address......... AOL Inc.
Tech Address......... 22000 AOL Way
Tech Address.........
Tech Address......... Dulles
Tech Address......... 20166
Tech Address......... VA
Tech Address......... UNITED STATES
Tech Email........... email
Tech Phone........... +1.7032654670
Tech Fax.............
Name Server.......... DNS-02.NS.AOL.COM
Name Server.......... DNS-01.NS.AOL.COM
Name Server.......... DNS-07.NS.AOL.COM
Name Server.......... DNS-06.NS.AOL.COM


DNS Analysis


DNS servers
dns-02.ns.aol.com [205.188.157.232]
dns-01.ns.aol.com [64.12.51.132]
dns-06.ns.aol.com [207.200.73.80]
dns-07.ns.aol.com [64.236.1.107]


DNS Records

Answer records
compuserve.com SOA
server: dns-01.ns.aol.com
email: hostmaster@aol.net
serial: 357949231
refresh: 86400
retry: 180
expire: 2592000
minimum ttl: 300
3600s
compuserve.com NS  dns-07.ns.aol.com 3600s
compuserve.com NS  dns-06.ns.aol.com 3600s
compuserve.com NS  dns-02.ns.aol.com 3600s
compuserve.com NS  dns-01.ns.aol.com 3600s
compuserve.com A 64.12.128.199 3600s
compuserve.com A 205.188.96.199 3600s
compuserve.com MX
preference: 15
exchange: mailin-04.mx.aol.com
3600s
compuserve.com MX
preference: 15
exchange: mailin-01.mx.aol.com
3600s
compuserve.com MX
preference: 15
exchange: mailin-02.mx.aol.com
3600s
compuserve.com MX
preference: 15
exchange: mailin-03.mx.aol.com
3600s
compuserve.com TXT spf2.0/pra include:aol.com ?all 3600s
compuserve.com TXT v=spf1 include:aol.com ?all 3600s

Authority records

Additional records
dns-01.ns.aol.com A 64.12.51.132 3600s
dns-02.ns.aol.com A 205.188.157.232 3600s
dns-06.ns.aol.com A 207.200.73.80 3600s
dns-07.ns.aol.com A 64.236.1.107 3600s

IP 64.12.128.199 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 71 Errors
  • 33 Warnings
Ratio Text/Html
  • 0.6467279707169002
Message Error
  • Error Line 8, Column 13: there is no attribute "XMLNS"
    <html xmlns="http://www/w3.org/1999/xhtml" lang="em" xml:lang="en">

    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 8, Column 63: there is no attribute "XML:LANG"
    <html xmlns="http://www/w3.org/1999/xhtml" lang="em" xml:lang="en">

    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 12, Column 94: NET-enabling start-tag requires SHORTTAG YES
    …tylesheet" type="text/css" href="http://access.nscpcdn.com/home/i/style.css" />

    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 12, Column 95: character data is not allowed here
    …tylesheet" type="text/css" href="http://access.nscpcdn.com/home/i/style.css" />

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Warning Line 59, Column 108: NET-enabling start-tag requires SHORTTAG YES
    …s.nscpcdn.com/cppops/11/20110511_00001/i/CS_header.jpg" alt="CompuServe Logo"/>

    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 69, Column 26: there is no attribute "TARGET"
                <form target="_parent" action="/search/websearch" name="searchform"…

    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 70, Column 66: NET-enabling start-tag requires SHORTTAG YES
                  <input type="hidden" value="cscom" name="fromPage" />

    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 70, Column 66: document type does not allow element "INPUT" here; missing one of "P", "H1", "H2", "H3", "H4", "H5", "H6", "PRE", "DIV", "ADDRESS" start-tag
                  <input type="hidden" value="cscom" name="fromPage" />

    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 70, Column 67: character data is not allowed here
                  <input type="hidden" value="cscom" name="fromPage" />

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Warning Line 71, Column 96: NET-enabling start-tag requires SHORTTAG YES
    …ut id="hdrSrchText" type="text" title="Search the Web" name="query" value="" />

    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 71, Column 96: document type does not allow element "INPUT" here; missing one of "P", "H1", "H2", "H3", "H4", "H5", "H6", "PRE", "DIV", "ADDRESS" start-tag
    …ut id="hdrSrchText" type="text" title="Search the Web" name="query" value="" />

    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 72, Column 82: NET-enabling start-tag requires SHORTTAG YES
    …          <input id="hdrSrchBtn" type="submit" title="Search" value="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 72, Column 82: document type does not allow element "INPUT" here; missing one of "P", "H1", "H2", "H3", "H4", "H5", "H6", "PRE", "DIV", "ADDRESS" start-tag
    …          <input id="hdrSrchBtn" type="submit" title="Search" value="Search" />

    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 73, Column 19: end tag for "FORM" which is not finished
                </form>

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

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

  • Error Line 77, Column 19: start tag for "LI" omitted, but its declaration does not permit this
                <ul><b>Hot Searches:</b>
  • Error Line 160, Column 33: there is no attribute "TARGET"
            <a href="/news/" target="">New England begins the big dig-out after epi…

    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 164, Column 152: NET-enabling start-tag requires SHORTTAG YES
    …ccess.nscpcdn.com/cppops/19/20050919_00003/i/top_bestbuysfeb2.jpg" alt=""/></a>

    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 213, Column 10: document type does not allow element "H3" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
          <h3>News</h3>

    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 262, Column 10: document type does not allow element "H3" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
          <h3>From the Editor</h3>

    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 266, Column 201: NET-enabling start-tag requires SHORTTAG YES
    …1004_00003/i/mantle_lowerchildsiq.jpg" alt="WHAT Can Lower a Child's IQ?"/></a>

    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 304, Column 10: document type does not allow element "H3" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
          <h3>Talk About It</h3>

    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 309, Column 86: cannot generate system identifier for general entity "nav"
    …rve.com/n/pfx/forum.aspx?msg=235498.1&nav=messages&webtag=ws-newsforum">Trump'…

    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 309, Column 86: general entity "nav" not defined and no default entity
    …rve.com/n/pfx/forum.aspx?msg=235498.1&nav=messages&webtag=ws-newsforum">Trump'…

    This is usually a cascading error caused by 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 309, Column 89: reference to entity "nav" for which no system identifier could be generated
    ….com/n/pfx/forum.aspx?msg=235498.1&nav=messages&webtag=ws-newsforum">Trump'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.

  • Info Line 309, Column 85: entity was defined here
    …erve.com/n/pfx/forum.aspx?msg=235498.1&nav=messages&webtag=ws-newsforum">Trump…
  • Warning Line 309, Column 99: cannot generate system identifier for general entity "webtag"
    …/forum.aspx?msg=235498.1&nav=messages&webtag=ws-newsforum">Trump's $5 Million …

    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 309, Column 99: general entity "webtag" not defined and no default entity
    …/forum.aspx?msg=235498.1&nav=messages&webtag=ws-newsforum">Trump's $5 Million …

    This is usually a cascading error caused by 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 309, Column 105: reference to entity "webtag" for which no system identifier could be generated
    ….aspx?msg=235498.1&nav=messages&webtag=ws-newsforum">Trump's $5 Million Lawsui…

    This is usually a cascading error caused by 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 309, Column 98: entity was defined here
    …x/forum.aspx?msg=235498.1&nav=messages&webtag=ws-newsforum">Trump's $5 Million…
  • Error Line 315, Column 82: reference to entity "nav" for which no system identifier could be generated
    …puserve.com/n/pfx/forum.aspx?tsn=1&nav=messages&webtag=ws-gadgetsgear&tid=2955…

    This is usually a cascading error caused by 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 309, Column 85: entity was defined here
    …erve.com/n/pfx/forum.aspx?msg=235498.1&nav=messages&webtag=ws-newsforum">Trump…
  • Error Line 315, Column 98: reference to entity "webtag" for which no system identifier could be generated
    …x/forum.aspx?tsn=1&nav=messages&webtag=ws-gadgetsgear&tid=2955">What Happens t…

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

  • Info Line 309, Column 98: entity was defined here
    …x/forum.aspx?msg=235498.1&nav=messages&webtag=ws-newsforum">Trump's $5 Million…
  • Warning Line 315, Column 114: cannot generate system identifier for general entity "tid"
    …=1&nav=messages&webtag=ws-gadgetsgear&tid=2955">What Happens to My Digital Ass…

    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 315, Column 114: general entity "tid" not defined and no default entity
    …=1&nav=messages&webtag=ws-gadgetsgear&tid=2955">What Happens to My Digital Ass…

    This is usually a cascading error caused by 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 315, Column 117: reference to entity "tid" for which no system identifier could be generated
    …nav=messages&webtag=ws-gadgetsgear&tid=2955">What Happens to My Digital Assets…

    This is usually a cascading error caused by 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 315, Column 113: entity was defined here
    …n=1&nav=messages&webtag=ws-gadgetsgear&tid=2955">What Happens to My Digital As…
  • Error Line 318, Column 82: reference to entity "nav" for which no system identifier could be generated
    …puserve.com/n/pfx/forum.aspx?tsn=1&nav=messages&webtag=ws-cooks&tid=152829">Re…

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

  • Info Line 309, Column 85: entity was defined here
    …erve.com/n/pfx/forum.aspx?msg=235498.1&nav=messages&webtag=ws-newsforum">Trump…
  • Error Line 318, Column 98: reference to entity "webtag" for which no system identifier could be generated
    …x/forum.aspx?tsn=1&nav=messages&webtag=ws-cooks&tid=152829">Recipe of the Week…

    This is usually a cascading error caused by 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 309, Column 98: entity was defined here
    …x/forum.aspx?msg=235498.1&nav=messages&webtag=ws-newsforum">Trump's $5 Million…
  • Error Line 318, Column 111: reference to entity "tid" for which no system identifier could be generated
    …tsn=1&nav=messages&webtag=ws-cooks&tid=152829">Recipe of the Week: Chicken Mar…

    This is usually a cascading error caused by 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 315, Column 113: entity was defined here
    …n=1&nav=messages&webtag=ws-gadgetsgear&tid=2955">What Happens to My Digital As…
  • Error Line 321, Column 88: reference to entity "nav" for which no system identifier could be generated
    …e.com/n/pfx/forum.aspx?msg=22002.1&nav=messages&webtag=ws-womensforum">A Frien…

    This is usually a cascading error caused by 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 309, Column 85: entity was defined here
    …erve.com/n/pfx/forum.aspx?msg=235498.1&nav=messages&webtag=ws-newsforum">Trump…
  • Error Line 321, Column 104: reference to entity "webtag" for which no system identifier could be generated
    …m.aspx?msg=22002.1&nav=messages&webtag=ws-womensforum">A Friend Request From a…

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

  • Info Line 309, Column 98: entity was defined here
    …x/forum.aspx?msg=235498.1&nav=messages&webtag=ws-newsforum">Trump's $5 Million…
  • Error Line 324, Column 92: reference to entity "webtag" for which no system identifier could be generated
    …m/n/pfx/forum.aspx?nav=messages&webtag=ws-seniors&tid=2315">VOTE: Do You Have …

    This is usually a cascading error caused by 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 309, Column 98: entity was defined here
    …x/forum.aspx?msg=235498.1&nav=messages&webtag=ws-newsforum">Trump's $5 Million…
  • Error Line 324, Column 107: reference to entity "tid" for which no system identifier could be generated
    …spx?nav=messages&webtag=ws-seniors&tid=2315">VOTE: Do You Have a Living Will?<…

    This is usually a cascading error caused by 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 315, Column 113: entity was defined here
    …n=1&nav=messages&webtag=ws-gadgetsgear&tid=2955">What Happens to My Digital As…
  • Error Line 353, Column 10: document type does not allow element "H3" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
          <h3>Sports</h3>

    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 399, Column 10: document type does not allow element "H3" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
          <h3>Business</h3>

    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 487, Column 68: NET-enabling start-tag requires SHORTTAG YES
                <input class="tickers" type="text" name="TickerSymbols"/>

    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 487, Column 68: document type does not allow element "INPUT" here; missing one of "P", "H1", "H2", "H3", "H4", "H5", "H6", "PRE", "DIV", "ADDRESS" start-tag
                <input class="tickers" type="text" name="TickerSymbols"/>

    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 487, Column 69: character data is not allowed here
                <input class="tickers" type="text" name="TickerSymbols"/>

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Warning Line 488, Column 66: NET-enabling start-tag requires SHORTTAG YES
                <input class="button" type="submit" value="Get Quote"/>

    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 488, Column 66: document type does not allow element "INPUT" here; missing one of "P", "H1", "H2", "H3", "H4", "H5", "H6", "PRE", "DIV", "ADDRESS" start-tag
                <input class="button" type="submit" value="Get Quote"/>

    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 489, Column 17: end tag for "FORM" which is not finished
              </form>

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

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

  • Warning Line 525, Column 104: NET-enabling start-tag requires SHORTTAG YES
    …//access.nscpcdn.com/cppops/28/20050628_00001/i/banner_cscom2.jpg" alt=""/></a>

    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 560, Column 8: document type does not allow element "H3" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
        <h3>Weather</h3>

    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 566, Column 89: NET-enabling start-tag requires SHORTTAG YES
    …input class="box" type="text" name="f"/><input type="hidden" value="Y" name="p…

    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 566, Column 133: NET-enabling start-tag requires SHORTTAG YES
    …ut type="hidden" value="Y" name="pers"/><input class="button" type="submit" 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.

  • Warning Line 566, Column 181: NET-enabling start-tag requires SHORTTAG YES
    …en" value="Y" name="pers"/><input class="button" type="submit" value="Go"/></p>

    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 600, Column 53: document type does not allow element "A" here; missing one of "P", "H1", "H2", "H3", "H4", "H5", "H6", "PRE", "DIV", "ADDRESS" start-tag
    …ttp://ar.atwola.com/link/93171149/aol"><img src="http://ar.atwola.com/image/93…

    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 600, Column 170: NET-enabling start-tag requires SHORTTAG YES
    …49/aol" alt="Click Here to visit our advertiser" width="300" height="250"/></a>

    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 601, Column 13: end tag for "NOSCRIPT" which is not finished
      </noscript>

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

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

  • Warning Line 628, Column 75: cannot generate system identifier for general entity "storyterm"
    …idq=/ff/story/1001/20130207/a0923.htm&storyterm=grammys&maxstories=4"><img src…

    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 628, Column 75: general entity "storyterm" not defined and no default entity
    …idq=/ff/story/1001/20130207/a0923.htm&storyterm=grammys&maxstories=4"><img src…

    This is usually a cascading error caused by 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 628, Column 84: reference to entity "storyterm" for which no system identifier could be generated
    …tory/1001/20130207/a0923.htm&storyterm=grammys&maxstories=4"><img src="http://…

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

  • Info Line 628, Column 74: entity was defined here
    …?idq=/ff/story/1001/20130207/a0923.htm&storyterm=grammys&maxstories=4"><img sr…
  • Warning Line 628, Column 93: cannot generate system identifier for general entity "maxstories"
    …/20130207/a0923.htm&storyterm=grammys&maxstories=4"><img src="http://access.ns…

    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 628, Column 93: general entity "maxstories" not defined and no default entity
    …/20130207/a0923.htm&storyterm=grammys&maxstories=4"><img src="http://access.ns…

    This is usually a cascading error caused by 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 628, Column 103: reference to entity "maxstories" for which no system identifier could be generated
    …a0923.htm&storyterm=grammys&maxstories=4"><img src="http://access.nscpcdn.com/…

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

  • Info Line 628, Column 92: entity was defined here
    …1/20130207/a0923.htm&storyterm=grammys&maxstories=4"><img src="http://access.n…
  • Warning Line 628, Column 221: NET-enabling start-tag requires SHORTTAG YES
    …s/06/20051006_00005/i/jlo_grammy_95.jpg" alt="New Dress Code for Grammys"/></a>

    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 630, Column 90: reference to entity "storyterm" for which no system identifier could be generated
    …tory/1001/20130207/a0923.htm&storyterm=grammys&maxstories=4">New Dress Code fo…

    This is usually a cascading error caused by 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 628, Column 74: entity was defined here
    …?idq=/ff/story/1001/20130207/a0923.htm&storyterm=grammys&maxstories=4"><img sr…
  • Error Line 630, Column 109: reference to entity "maxstories" for which no system identifier could be generated
    …7/a0923.htm&storyterm=grammys&maxstories=4">New Dress Code for Grammys</a></h4>

    This is usually a cascading error caused by 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 628, Column 92: entity was defined here
    …1/20130207/a0923.htm&storyterm=grammys&maxstories=4"><img src="http://access.n…
  • Error Line 631, Column 89: reference to entity "storyterm" for which no system identifier could be generated
    …tory/1001/20130207/a0923.htm&storyterm=grammys&maxstories=4">CBS is getting ex…

    This is usually a cascading error caused by 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 628, Column 74: entity was defined here
    …?idq=/ff/story/1001/20130207/a0923.htm&storyterm=grammys&maxstories=4"><img sr…
  • Error Line 631, Column 108: reference to entity "maxstories" for which no system identifier could be generated
    …a0923.htm&storyterm=grammys&maxstories=4">CBS is getting explicit with what wi…

    This is usually a cascading error caused by 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 628, Column 92: entity was defined here
    …1/20130207/a0923.htm&storyterm=grammys&maxstories=4"><img src="http://access.n…
  • Warning Line 645, Column 86: cannot generate system identifier for general entity "phototerm"
    …?idq=/ff/story/1001/20130208/1827.htm&phototerm=grammys&maxphotos=4&storyterm=…

    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 645, Column 86: general entity "phototerm" not defined and no default entity
    …?idq=/ff/story/1001/20130208/1827.htm&phototerm=grammys&maxphotos=4&storyterm=…

    This is usually a cascading error caused by 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 645, Column 95: reference to entity "phototerm" for which no system identifier could be generated
    …story/1001/20130208/1827.htm&phototerm=grammys&maxphotos=4&storyterm=grammys&m…

    This is usually a cascading error caused by 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 645, Column 85: entity was defined here
    …p?idq=/ff/story/1001/20130208/1827.htm&phototerm=grammys&maxphotos=4&storyterm…
  • Warning Line 645, Column 104: cannot generate system identifier for general entity "maxphotos"
    …1/20130208/1827.htm&phototerm=grammys&maxphotos=4&storyterm=grammys&maxstories…

    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 645, Column 104: general entity "maxphotos" not defined and no default entity
    …1/20130208/1827.htm&phototerm=grammys&maxphotos=4&storyterm=grammys&maxstories…

    This is usually a cascading error caused by 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 645, Column 113: reference to entity "maxphotos" for which no system identifier could be generated
    …8/1827.htm&phototerm=grammys&maxphotos=4&storyterm=grammys&maxstories=4">One Y…

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

  • Info Line 645, Column 103: entity was defined here
    …01/20130208/1827.htm&phototerm=grammys&maxphotos=4&storyterm=grammys&maxstorie…
  • Error Line 645, Column 125: reference to entity "storyterm" for which no system identifier could be generated
    …hototerm=grammys&maxphotos=4&storyterm=grammys&maxstories=4">One Year Later, 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.

  • Info Line 628, Column 74: entity was defined here
    …?idq=/ff/story/1001/20130207/a0923.htm&storyterm=grammys&maxstories=4"><img sr…
  • Error Line 645, Column 144: reference to entity "maxstories" for which no system identifier could be generated
    …xphotos=4&storyterm=grammys&maxstories=4">One Year Later, Clive Remembers Whit…

    This is usually a cascading error caused by 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 628, Column 92: entity was defined here
    …1/20130207/a0923.htm&storyterm=grammys&maxstories=4"><img src="http://access.n…
  • Error Line 648, Column 97: reference to entity "phototerm" for which no system identifier could be generated
    …ory/0027/20130208/143210.htm&phototerm=%27ashton%20kutcher%27&maxphotos=4&stor…

    This is usually a cascading error caused by 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 645, Column 85: entity was defined here
    …p?idq=/ff/story/1001/20130208/1827.htm&phototerm=grammys&maxphotos=4&storyterm…
  • Error Line 648, Column 130: reference to entity "maxphotos" for which no system identifier could be generated
    …oterm=%27ashton%20kutcher%27&maxphotos=4&storyterm=%27ashton%20kutcher%27&maxs…

    This is usually a cascading error caused by 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 645, Column 103: entity was defined here
    …01/20130208/1827.htm&phototerm=grammys&maxphotos=4&storyterm=grammys&maxstorie…
  • Error Line 648, Column 142: reference to entity "storyterm" for which no system identifier could be generated
    …ton%20kutcher%27&maxphotos=4&storyterm=%27ashton%20kutcher%27&maxstories=4">Pr…

    This is usually a cascading error caused by 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 628, Column 74: entity was defined here
    …?idq=/ff/story/1001/20130207/a0923.htm&storyterm=grammys&maxstories=4"><img sr…
  • Error Line 648, Column 176: reference to entity "maxstories" for which no system identifier could be generated
    …term=%27ashton%20kutcher%27&maxstories=4">Pre-Teen Charged in Kutcher 'Swattin…

    This is usually a cascading error caused by 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 628, Column 92: entity was defined here
    …1/20130207/a0923.htm&storyterm=grammys&maxstories=4"><img src="http://access.n…
  • Error Line 651, Column 97: reference to entity "phototerm" for which no system identifier could be generated
    …ory/0027/20130208/143203.htm&phototerm=%27john%20mayer%27&maxphotos=4&storyter…

    This is usually a cascading error caused by 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 645, Column 85: entity was defined here
    …p?idq=/ff/story/1001/20130208/1827.htm&phototerm=grammys&maxphotos=4&storyterm…
  • Error Line 651, Column 126: reference to entity "maxphotos" for which no system identifier could be generated
    …phototerm=%27john%20mayer%27&maxphotos=4&storyterm=%27john%20mayer%27&maxstori…

    This is usually a cascading error caused by 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 645, Column 103: entity was defined here
    …01/20130208/1827.htm&phototerm=grammys&maxphotos=4&storyterm=grammys&maxstorie…
  • Error Line 651, Column 138: reference to entity "storyterm" for which no system identifier could be generated
    …7john%20mayer%27&maxphotos=4&storyterm=%27john%20mayer%27&maxstories=4">Mayer:…

    This is usually a cascading error caused by 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 628, Column 74: entity was defined here
    …?idq=/ff/story/1001/20130207/a0923.htm&storyterm=grammys&maxstories=4"><img sr…
  • Error Line 651, Column 168: reference to entity "maxstories" for which no system identifier could be generated
    …toryterm=%27john%20mayer%27&maxstories=4">Mayer: I'm Not the Jerk I Once Was</…

    This is usually a cascading error caused by 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 628, Column 92: entity was defined here
    …1/20130207/a0923.htm&storyterm=grammys&maxstories=4"><img src="http://access.n…
  • Error Line 654, Column 97: reference to entity "phototerm" for which no system identifier could be generated
    …ory/0027/20130208/143207.htm&phototerm=%27lindsay%20lohan%27&maxphotos=4&story…

    This is usually a cascading error caused by 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 645, Column 85: entity was defined here
    …p?idq=/ff/story/1001/20130208/1827.htm&phototerm=grammys&maxphotos=4&storyterm…
  • Error Line 654, Column 129: reference to entity "maxphotos" for which no system identifier could be generated
    …toterm=%27lindsay%20lohan%27&maxphotos=4&storyterm=%27lindsay%20lohan%27&maxst…

    This is usually a cascading error caused by 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 645, Column 103: entity was defined here
    …01/20130208/1827.htm&phototerm=grammys&maxphotos=4&storyterm=grammys&maxstorie…
  • Error Line 654, Column 141: reference to entity "storyterm" for which no system identifier could be generated
    …ndsay%20lohan%27&maxphotos=4&storyterm=%27lindsay%20lohan%27&maxstories=4">Lin…

    This is usually a cascading error caused by 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 628, Column 74: entity was defined here
    …?idq=/ff/story/1001/20130207/a0923.htm&storyterm=grammys&maxstories=4"><img sr…
  • Error Line 654, Column 174: reference to entity "maxstories" for which no system identifier could be generated
    …yterm=%27lindsay%20lohan%27&maxstories=4">Lindsay Served Foreclosure Notice</a…

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

  • Info Line 628, Column 92: entity was defined here
    …1/20130207/a0923.htm&storyterm=grammys&maxstories=4"><img src="http://access.n…
  • Error Line 691, Column 147: there is no attribute "ONERROR"
    …d40.jpg" alt="Channing Tatum" onError="showAltImage(this, 'celebEVERGREEN');"/…

    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 691, Column 186: NET-enabling start-tag requires SHORTTAG YES
    …jpg" alt="Channing Tatum" onError="showAltImage(this, 'celebEVERGREEN');"/></a>

    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 726, Column 183: NET-enabling start-tag requires SHORTTAG YES
    …0824_00001/i/high_married.jpg" alt="How Many Times Will You Get Married?"/></a>

    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 807, Column 98: NET-enabling start-tag requires SHORTTAG YES
    …://access.nscpcdn.com/cppops/11/20110511_00001/i/CS_wow.gif" alt="CompuServe"/>

    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 855, Column 111: NET-enabling start-tag requires SHORTTAG YES
    …pcdn.com/cppops/11/20110511_00001/i/CS_button_mail.gif" alt="CompuServe Mail"/>

    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 885, Column 163: NET-enabling start-tag requires SHORTTAG YES
    …nscpcdn.com/cppops/11/20110511_00001/i/but_whatsnew.gif" alt="What's New"/></a>

    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 1011, Column 89: cannot generate system identifier for general entity "v"
    …tion="http://www.yellowpages.com/sp/yellowpages/ypresults.jsp?From=COMPYP&v=13"

    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 1011, Column 89: general entity "v" not defined and no default entity
    …tion="http://www.yellowpages.com/sp/yellowpages/ypresults.jsp?From=COMPYP&v=13"

    This is usually a cascading error caused by 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 1011, Column 90: reference to entity "v" for which no system identifier could be generated
    …tion="http://www.yellowpages.com/sp/yellowpages/ypresults.jsp?From=COMPYP&v=13"

    This is usually a cascading error caused by 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 1011, Column 88: entity was defined here
    …tion="http://www.yellowpages.com/sp/yellowpages/ypresults.jsp?From=COMPYP&v=13"
  • Warning Line 1014, Column 89: NET-enabling start-tag requires SHORTTAG YES
    …put class="ypText" type="text" title="Yellow Pages Search" name="q" value="" />

    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 1014, Column 89: document type does not allow element "INPUT" here; missing one of "P", "H1", "H2", "H3", "H4", "H5", "H6", "PRE", "DIV", "ADDRESS" start-tag
    …put class="ypText" type="text" title="Yellow Pages Search" name="q" value="" />

    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 1014, Column 90: character data is not allowed here
    …put class="ypText" type="text" title="Yellow Pages Search" name="q" value="" />

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Warning Line 1015, Column 73: NET-enabling start-tag requires SHORTTAG YES
            <input class="ypSubmit" type="submit" title="Search" value="Go" />

    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 1015, Column 73: document type does not allow element "INPUT" here; missing one of "P", "H1", "H2", "H3", "H4", "H5", "H6", "PRE", "DIV", "ADDRESS" start-tag
            <input class="ypSubmit" type="submit" title="Search" value="Go" />

    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 1016, Column 13: end tag for "FORM" which is not finished
          </form>

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

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

  • Warning Line 1061, Column 111: NET-enabling start-tag requires SHORTTAG YES
    …://access.nscpcdn.com/home/i/np_logo.gif" alt="What's New" title="What's New"/>

    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 1063, Column 130: NET-enabling start-tag requires SHORTTAG YES
    …e" src="http://access.nscpcdn.com/home/i/np_close.gif" alt="Close Window"/></a>

    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.

Visitor Analysis

Daily Visitor
  • 5.950 visits
Daily Visitor