FootballLOCKS.com provides weekly NFL football picks & predictions made using Backwards Odds NFL Handicapping of Las Vegas pro football lines & point spreads. Pool plays ATS and straight up. NFL expert picks each ...

footballlocks.com
  • Domain Name
    footballlocks.com
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #56876
  • Page Size
    61.3 KB
  • Ip Address
    65.18.174.166
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    16 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
    FootballLOCKS.com: NFL picks, weekly pro football lines, odds & point spreads. Expert NFL betting predictions.
  • Meta Keyword
    NFL picks, weekly nfl football picks, online sports betting, handicapping, odds, nfl predictions, week, game, handicappers, online gambling, sports, lines, odds, point spreads, wagering, pick, prediction, Las Vegas, line, handicapper, prediction, pro football, betting, spread, power rankings, fantasy, tips,
  • Meta Description
    FootballLOCKS.com provides weekly NFL football picks & predictions made using Backwards Odds NFL Handicapping of Las Vegas pro football lines & point spreads. Pool plays ATS and straight up. NFL expert picks each week. Betting lines, odds, the weekly point spread, power rankings, predictions, previews, handicapping strategy, standings projections, schedules and fantasy tips. Sports betting picks in pro football games and other online gambling information.

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    65.18.174.166
  • Domain Age
    12 Years, 7 Months, 12 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Sun, 17 Feb 2013 15:31:07 GMT
  • server: Apache
  • accept-ranges: bytes
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-length: 10493
  • content-type: text/html
  • age: 15
  • x-google-cache-control: remote-cache-hit
  • via: HTTP/1.1 GWA (remote cache hit)
Registrant:
Domain Discreet Privacy Service
ATTN: footballlocks.com
12808 Gran Bay Pkwy, West
Jacksonville, FL 32258
US
Phone: 1-902-7492701
Email: email




Domain Name: footballlocks.com
Created on..............: 2000-07-13
Expires on..............: 2020-07-13

Administrative Contact:
Domain Discreet Privacy Service
ATTN: footballlocks.com
12808 Gran Bay Pkwy, West
Jacksonville, FL 32258
US
Phone: 1-902-7492701
Email: email


Technical Contact:
Domain Discreet Privacy Service
ATTN: footballlocks.com
12808 Gran Bay Pkwy, West
Jacksonville, FL 32258
US
Phone: 1-902-7492701
Email: email


DNS Servers:
ns2.host4u.net
ns.host4u.net

DNS Analysis


DNS servers
ns.host4u.net [209.150.128.30]
ns2.host4u.net [209.150.128.15]


DNS Records

Answer records
footballlocks.com SOA
server: ns.host4u.net
email: hostmaster@host4u.net
serial: 8101511
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 28800
28800s
footballlocks.com NS  ns2.host4u.net 28800s
footballlocks.com NS  ns.host4u.net 28800s
footballlocks.com A 65.18.174.166 28800s
footballlocks.com MX
preference: 10
exchange: mail.footballlocks.com
28800s

Authority records

Additional records
ns.host4u.net A 209.150.128.30 600s
ns2.host4u.net A 209.150.128.15 600s
mail.footballlocks.com A 65.18.174.166 28800s

IP 65.18.174.166 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 174 Errors
  • 23 Warnings
Ratio Text/Html
  • 0.5559469539991712
Message Error
  • Error Line 11, Column 25: document type does not allow element "STYLE" here
      <style type="text/css">

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

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

  • Error Line 37, Column 10: required attribute "TYPE" not specified
      <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 49, Column 28: document type does not allow element "BODY" here
    <body onLoad="set_login();">

    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 53, Column 24: there is no attribute "COLSPAN"
    <tr><td><TABLE COLSPAN="3" width="1003" border="0" cellpadding="0" cellspacing=…

    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 61, Column 110: NET-enabling start-tag requires SHORTTAG YES
    …locks.com/openx/www/delivery/avw.php?zoneid=35&amp;n=a3f6b33' /></a></noscript>

    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 69, Column 110: NET-enabling start-tag requires SHORTTAG YES
    …locks.com/openx/www/delivery/avw.php?zoneid=15&amp;n=f29ad82' /></a></noscript>

    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 77, Column 110: NET-enabling start-tag requires SHORTTAG YES
    …locks.com/openx/www/delivery/avw.php?zoneid=85&amp;n=d612d10' /></a></noscript>

    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 80, Column 23: end tag for element "TD" which is not open
    </TR></TABLE></tr></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 82, Column 36: there is no attribute "HEIGHT"
    <tr><td><table width="1003" height="229" border="0" align="left" cellpadding="0…

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

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

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

  • Error Line 106, Column 9: an attribute specification must start with a name or name token
    <bgcolor="#0A8DC1" width="64" height="33"></td>

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

  • Error Line 106, Column 9: element "BGCOLOR" undefined
    <bgcolor="#0A8DC1" width="64" height="33"></td>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 116, Column 111: NET-enabling start-tag requires SHORTTAG YES
    …//www.footballlocks.com/openx/www/delivery/avw.php?zoneid=102&amp;n=2a91a84' />

    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 154, Column 107: name start character invalid: only S separators and TAGC allowed here
    …making NFL picks most pro football handicappers & sports</font color="#DD0616">
  • Error Line 157, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <P>		

    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 164, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <P>

    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 171, Column 157: name start character invalid: only S separators and TAGC allowed here
    …>View subscription options for NFL weekly picks.</B></font color="#000099"></A>
  • Error Line 172, Column 6: end tag for "SPAN" omitted, but its declaration does not permit this
    </div></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 152, Column 4: start tag was here
    			<span style="font-family: Arial; font-size: 11px">
  • Error Line 174, Column 68: end tag for element "SPAN" which is not open
    …"><div align="right"></div></td></SPAN></tr></table></td></tr></table></div></…

    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 187, Column 29: document type does not allow element "NOSCRIPT" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    // ]]> --></script><noscript><a target='_blank' href='http://www.footballlocks.…

    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 188, Column 110: NET-enabling start-tag requires SHORTTAG YES
    …locks.com/openx/www/delivery/avw.php?zoneid=89&amp;n=f9e1cf9' /></a></noscript>

    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 190, Column 136: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …e_week.shtml">Football<I>LOCKS</I>.com's<br>Free NFL Pick of<br>the Week</a><p>

    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 192, Column 6: end tag for "SPAN" omitted, but its declaration does not permit this
    </div></td></tr></table></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 183, Column 1: start tag was here
    <span style="font-family: Arial; font-size: 13px">
  • Error Line 231, Column 73: required attribute "ALT" not specified
    …s2/sample1a.gif" width="8" height="23"></td><td align="center" class="sample_1…

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

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

  • Error Line 234, Column 89: required attribute "ALT" not specified
    …><td align="center"><img src="images2/sample1b.gif" width="8" height="23"></td>

    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 238, Column 73: required attribute "ALT" not specified
    …s2/sample1a.gif" width="8" height="23"></td><td align="center" class="sample_1…

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

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

  • Error Line 241, Column 89: required attribute "ALT" not specified
    …><td align="center"><img src="images2/sample1b.gif" width="8" height="23"></td>

    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 244, Column 73: required attribute "ALT" not specified
    …s2/sample1a.gif" width="8" height="23"></td><td align="center" class="sample_1…

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

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

  • Error Line 247, Column 89: required attribute "ALT" not specified
    …><td align="center"><img src="images2/sample1b.gif" width="8" height="23"></td>

    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 250, Column 73: required attribute "ALT" not specified
    …s2/sample1a.gif" width="8" height="23"></td><td align="center" class="sample_1…

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

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

  • Error Line 253, Column 89: required attribute "ALT" not specified
    …><td align="center"><img src="images2/sample1b.gif" width="8" height="23"></td>

    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 256, Column 73: required attribute "ALT" not specified
    …s2/sample1a.gif" width="8" height="23"></td><td align="center" class="sample_1…

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

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

  • Error Line 259, Column 89: required attribute "ALT" not specified
    …><td align="center"><img src="images2/sample1b.gif" width="8" height="23"></td>

    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 262, Column 73: required attribute "ALT" not specified
    …s2/sample1a.gif" width="8" height="23"></td><td align="center" class="sample_1…

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

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

  • Error Line 265, Column 89: required attribute "ALT" not specified
    …><td align="center"><img src="images2/sample1b.gif" width="8" height="23"></td>

    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 287, Column 7: required attribute "TYPE" not specified
    <style>

    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 287, Column 7: document type does not allow element "STYLE" here
    <style>

    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 312, Column 4: "IF" is not a reserved name
    <![if !IE]> <td valign="top" width="2" height="33" bgcolor="#659DE8"></td>  <![…
  • Error Line 312, Column 7: character data is not allowed here
    <![if !IE]> <td valign="top" width="2" height="33" bgcolor="#659DE8"></td>  <![…

    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.
  • Error Line 312, Column 80: "ENDIF" is not a reserved name
    …IE]> <td valign="top" width="2" height="33" bgcolor="#659DE8"></td>  <![endif]>
  • Error Line 312, Column 85: character data is not allowed here
    …IE]> <td valign="top" width="2" height="33" bgcolor="#659DE8"></td>  <![endif]>

    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.
  • Error Line 319, Column 4: "IF" is not a reserved name
    <![if !IE]><i>Subscribe</i><![endif]>
  • Error Line 319, Column 31: "ENDIF" is not a reserved name
    <![if !IE]><i>Subscribe</i><![endif]>
  • Error Line 324, Column 4: "IF" is not a reserved name
    <![if !IE]> <td valign="top" width="2" height="33" bgcolor="#659DE8"></td>  <![…
  • Error Line 324, Column 7: character data is not allowed here
    <![if !IE]> <td valign="top" width="2" height="33" bgcolor="#659DE8"></td>  <![…

    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.
  • Error Line 324, Column 80: "ENDIF" is not a reserved name
    …IE]> <td valign="top" width="2" height="33" bgcolor="#659DE8"></td>  <![endif]>
  • Error Line 324, Column 85: character data is not allowed here
    …IE]> <td valign="top" width="2" height="33" bgcolor="#659DE8"></td>  <![endif]>

    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.
  • Error Line 331, Column 4: "IF" is not a reserved name
    <![if !IE]> <td valign="top" width="2" height="33" bgcolor="#659DE8"></td>  <![…
  • Error Line 331, Column 7: character data is not allowed here
    <![if !IE]> <td valign="top" width="2" height="33" bgcolor="#659DE8"></td>  <![…

    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.
  • Error Line 331, Column 80: "ENDIF" is not a reserved name
    …IE]> <td valign="top" width="2" height="33" bgcolor="#659DE8"></td>  <![endif]>
  • Error Line 331, Column 85: character data is not allowed here
    …IE]> <td valign="top" width="2" height="33" bgcolor="#659DE8"></td>  <![endif]>

    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.
  • Error Line 339, Column 4: "IF" is not a reserved name
    <![if !IE]> <td valign="top" width="2" height="33" bgcolor="#659DE8"></td>  <![…
  • Error Line 339, Column 7: character data is not allowed here
    <![if !IE]> <td valign="top" width="2" height="33" bgcolor="#659DE8"></td>  <![…

    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.
  • Error Line 339, Column 80: "ENDIF" is not a reserved name
    …IE]> <td valign="top" width="2" height="33" bgcolor="#659DE8"></td>  <![endif]>
  • Error Line 339, Column 85: character data is not allowed here
    …IE]> <td valign="top" width="2" height="33" bgcolor="#659DE8"></td>  <![endif]>

    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.
  • Error Line 345, Column 4: "IF" is not a reserved name
    <![if !IE]> <td valign="top" width="2" height="33" bgcolor="#659DE8"></td>  <![…
  • Error Line 345, Column 7: character data is not allowed here
    <![if !IE]> <td valign="top" width="2" height="33" bgcolor="#659DE8"></td>  <![…

    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.
  • Error Line 345, Column 80: "ENDIF" is not a reserved name
    …IE]> <td valign="top" width="2" height="33" bgcolor="#659DE8"></td>  <![endif]>
  • Error Line 345, Column 85: character data is not allowed here
    …IE]> <td valign="top" width="2" height="33" bgcolor="#659DE8"></td>  <![endif]>

    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.
  • Error Line 352, Column 4: "IF" is not a reserved name
    <![if !IE]> <td valign="top" width="2" height="33" bgcolor="#659DE8"></td>  <![…
  • Error Line 352, Column 7: character data is not allowed here
    <![if !IE]> <td valign="top" width="2" height="33" bgcolor="#659DE8"></td>  <![…

    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.
  • Error Line 352, Column 80: "ENDIF" is not a reserved name
    …IE]> <td valign="top" width="2" height="33" bgcolor="#659DE8"></td>  <![endif]>
  • Error Line 352, Column 85: character data is not allowed here
    …IE]> <td valign="top" width="2" height="33" bgcolor="#659DE8"></td>  <![endif]>

    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.
  • Error Line 360, Column 4: "IF" is not a reserved name
    <![if !IE]> <td valign="top" width="2" height="33" bgcolor="#659DE8"></td>  <![…
  • Error Line 360, Column 7: character data is not allowed here
    <![if !IE]> <td valign="top" width="2" height="33" bgcolor="#659DE8"></td>  <![…

    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.
  • Error Line 360, Column 80: "ENDIF" is not a reserved name
    …IE]> <td valign="top" width="2" height="33" bgcolor="#659DE8"></td>  <![endif]>
  • Error Line 360, Column 85: character data is not allowed here
    …IE]> <td valign="top" width="2" height="33" bgcolor="#659DE8"></td>  <![endif]>

    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.
  • Error Line 366, Column 4: "IF" is not a reserved name
    <![if !IE]> <td valign="top" width="2" height="33" bgcolor="#659DE8"></td>  <![…
  • Error Line 366, Column 7: character data is not allowed here
    <![if !IE]> <td valign="top" width="2" height="33" bgcolor="#659DE8"></td>  <![…

    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.
  • Error Line 366, Column 80: "ENDIF" is not a reserved name
    …IE]> <td valign="top" width="2" height="33" bgcolor="#659DE8"></td>  <![endif]>
  • Error Line 366, Column 85: character data is not allowed here
    …IE]> <td valign="top" width="2" height="33" bgcolor="#659DE8"></td>  <![endif]>

    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.
  • Error Line 376, Column 4: "IF" is not a reserved name
    <![if !IE]> <td valign="top" width="2" height="33" bgcolor="#659DE8"></td>  <![…
  • Error Line 376, Column 7: character data is not allowed here
    <![if !IE]> <td valign="top" width="2" height="33" bgcolor="#659DE8"></td>  <![…

    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.
  • Error Line 376, Column 80: "ENDIF" is not a reserved name
    …IE]> <td valign="top" width="2" height="33" bgcolor="#659DE8"></td>  <![endif]>
  • Error Line 376, Column 85: character data is not allowed here
    …IE]> <td valign="top" width="2" height="33" bgcolor="#659DE8"></td>  <![endif]>

    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.
  • Error Line 384, Column 23: document type does not allow element "STYLE" here
    <style type="text/css">

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

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

  • Error Line 412, Column 8: name start character invalid: only S separators and TAGC allowed here
    </span style='font-family:comic sans ms; font-size:9.0pt'>
  • Error Line 413, Column 8: name start character invalid: only S separators and TAGC allowed here
    </font color="#DD0616">
  • Error Line 417, Column 4: document type does not allow element "LI" here
    <li><font color="#000099">Super Bowl Pick</font color="#000099"></li>

    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 417, Column 49: name start character invalid: only S separators and TAGC allowed here
    <li><font color="#000099">Super Bowl Pick</font color="#000099"></li>
  • Error Line 418, Column 4: document type does not allow element "LI" here
    <li><font color="#000099">Super Bowl Over/Under</font color="#000099"></li>

    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 418, Column 55: name start character invalid: only S separators and TAGC allowed here
    <li><font color="#000099">Super Bowl Over/Under</font color="#000099"></li>
  • Error Line 419, Column 4: document type does not allow element "LI" here
    <li><font color="#000099">Super Bowl Props</font color="#000099"></li>

    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 419, Column 50: name start character invalid: only S separators and TAGC allowed here
    <li><font color="#000099">Super Bowl Props</font color="#000099"></li>
  • Error Line 421, Column 8: name start character invalid: only S separators and TAGC allowed here
    </font color="#000099">
  • Error Line 423, Column 7: end tag for element "FONT" which is not open
    </font></a></span></div>

    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 438, Column 4: end tag for element "B" which is not open
    </B>

    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 439, Column 7: end tag for "SPAN" omitted, but its declaration does not permit this
    </font></span></a><br></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 433, Column 23: start tag was here
    <font color="#DD0616"><span style='font-family:comic sans ms; font-size:9.0pt'>
  • Error Line 439, Column 14: end tag for element "SPAN" which is not open
    </font></span></a><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.

  • Warning Line 442, Column 89: NET-enabling start-tag requires SHORTTAG YES
    …know-grad1.gif" width="82" height="26" border="0" align="top" /></a></td> </tr>

    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 442, Column 89: required attribute "ALT" not specified
    …know-grad1.gif" width="82" height="26" border="0" align="top" /></a></td> </tr>

    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 456, Column 4: end tag for "SPAN" omitted, but its declaration does not permit this
    </a></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 452, Column 23: start tag was here
    <font color="#000099"><span style='font-family:comic sans ms; font-size:9.0pt'>
  • Error Line 456, Column 4: end tag for "FONT" omitted, but its declaration does not permit this
    </a></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 452, Column 1: start tag was here
    <font color="#000099"><span style='font-family:comic sans ms; font-size:9.0pt'>
  • Error Line 456, Column 9: end tag for "SPAN" omitted, but its declaration does not permit this
    </a></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 449, Column 51: start tag was here
                                    <div align="left"><span class="style5">
  • Error Line 456, Column 9: end tag for "DIV" omitted, but its declaration does not permit this
    </a></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 449, Column 33: start tag was here
                                    <div align="left"><span class="style5">
  • Error Line 456, Column 9: end tag for "DIV" omitted, but its declaration does not permit this
    </a></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 448, Column 31: start tag was here
                                  <div align="justify" class="style8"> 
  • Error Line 456, Column 9: end tag for "DIV" omitted, but its declaration does not permit this
    </a></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 447, Column 64: start tag was here
                                <td colspan="2"> <div align="left"><div>
  • Error Line 456, Column 9: end tag for "DIV" omitted, but its declaration does not permit this
    </a></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 447, Column 46: start tag was here
                                <td colspan="2"> <div align="left"><div>
  • Error Line 468, Column 14: there is no attribute "COLS"
     <TABLE COLS="8" width="168" border="0" cellpadding="0" cellspacing="0">

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

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

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

  • Error Line 498, Column 23: document type does not allow element "STYLE" here
    <style type="text/css">

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

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

  • Error Line 529, Column 122: end tag for "TABLE" which is not finished
    …"0" cellspacing="0"><tr><td width="10"><table width="8px" height="3px"></table>

    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 531, Column 40: end tag for "TABLE" which is not finished
    …table width="3px" height="3px"></table></td><td width="948" align="left" valig…

    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 543, Column 52: end tag for "A" omitted, but its declaration does not permit this
    <font color="#ffcc00">Member NFL Picks</font></span></a></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 541, Column 1: start tag was here
    <a style="text-decoration:none" rel="nofollow" href="https://footballlocks.com/…
  • Error Line 543, Column 56: end tag for element "A" which is not open
    <font color="#ffcc00">Member NFL Picks</font></span></a></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.

  • Warning Line 551, Column 66: reference to non-SGML character
    …ter" valign="middle"><span class="bullet">&#149; </span></td></tr></table></td>

    You've included a character reference to a character that is not defined in the document type you've chosen. This is most commonly caused by numerical references to characters from vendor proprietary character repertoires. Often the culprit will be fancy or typographical quote marks from either the Windows or Macintosh character repertoires.

    The solution is to reference UNICODE characters instead. A list of common characters from the Windows character repertoire and their UNICODE equivalents can be found in the document "On the use of some MS Windows characters in HTML" maintained by Jukka Korpela <jkorpela@cs.tut.fi>.

  • Error Line 556, Column 75: there is no attribute "WEIGHT"
    …t color="#0000FF" size="1" face="Arial, Helvetica, sans-serif" weight="normal">

    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 563, Column 66: reference to non-SGML character
    …ter" valign="middle"><span class="bullet">&#149; </span></td></tr></table></td>

    You've included a character reference to a character that is not defined in the document type you've chosen. This is most commonly caused by numerical references to characters from vendor proprietary character repertoires. Often the culprit will be fancy or typographical quote marks from either the Windows or Macintosh character repertoires.

    The solution is to reference UNICODE characters instead. A list of common characters from the Windows character repertoire and their UNICODE equivalents can be found in the document "On the use of some MS Windows characters in HTML" maintained by Jukka Korpela <jkorpela@cs.tut.fi>.

  • Warning Line 575, Column 66: reference to non-SGML character
    …ter" valign="middle"><span class="bullet">&#149; </span></td></tr></table></td>

    You've included a character reference to a character that is not defined in the document type you've chosen. This is most commonly caused by numerical references to characters from vendor proprietary character repertoires. Often the culprit will be fancy or typographical quote marks from either the Windows or Macintosh character repertoires.

    The solution is to reference UNICODE characters instead. A list of common characters from the Windows character repertoire and their UNICODE equivalents can be found in the document "On the use of some MS Windows characters in HTML" maintained by Jukka Korpela <jkorpela@cs.tut.fi>.

  • Error Line 605, Column 40: end tag for "FONT" omitted, but its declaration does not permit this
    <font color="#ffcc00">Free NFL Picks</a></font></span></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 605, Column 1: start tag was here
    <font color="#ffcc00">Free NFL Picks</a></font></span></td></tr>
  • Error Line 605, Column 47: end tag for element "FONT" which is not open
    <font color="#ffcc00">Free NFL Picks</a></font></span></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.

  • Warning Line 613, Column 66: reference to non-SGML character
    …ter" valign="middle"><span class="bullet">&#149; </span></td></tr></table></td>

    You've included a character reference to a character that is not defined in the document type you've chosen. This is most commonly caused by numerical references to characters from vendor proprietary character repertoires. Often the culprit will be fancy or typographical quote marks from either the Windows or Macintosh character repertoires.

    The solution is to reference UNICODE characters instead. A list of common characters from the Windows character repertoire and their UNICODE equivalents can be found in the document "On the use of some MS Windows characters in HTML" maintained by Jukka Korpela <jkorpela@cs.tut.fi>.

  • Error Line 617, Column 68: end tag for "A" omitted, but its declaration does not permit this
    …<font color="#0000FF">Free NFL Pick of the Week</font></u></font></a></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 615, Column 112: start tag was here
    …" face="Arial, Helvetica, sans-serif"><a href="http://www.footballlocks.com/fr…
  • Error Line 617, Column 72: end tag for element "A" which is not open
    …<font color="#0000FF">Free NFL Pick of the Week</font></u></font></a></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.

  • Warning Line 621, Column 62: reference to non-SGML character
    …gn="middle"><span class="bullet">&#149; </span></td></tr></table></td><td heig…

    You've included a character reference to a character that is not defined in the document type you've chosen. This is most commonly caused by numerical references to characters from vendor proprietary character repertoires. Often the culprit will be fancy or typographical quote marks from either the Windows or Macintosh character repertoires.

    The solution is to reference UNICODE characters instead. A list of common characters from the Windows character repertoire and their UNICODE equivalents can be found in the document "On the use of some MS Windows characters in HTML" maintained by Jukka Korpela <jkorpela@cs.tut.fi>.

  • Error Line 625, Column 71: end tag for "A" omitted, but its declaration does not permit this
    …nt color="#0000FF">Free Monday Night Total Pick</font></u></font></a></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 623, Column 68: start tag was here
    …" face="Arial, Helvetica, sans-serif"><a href="http://www.footballlocks.com/fr…
  • Error Line 625, Column 75: end tag for element "A" which is not open
    …nt color="#0000FF">Free Monday Night Total Pick</font></u></font></a></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 824, Column 78: document type does not allow element "TABLE" here
     <table width="98%" border="0" align="center" cellpadding="0" cellspacing="0">

    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 826, Column 75: there is no attribute "BORDERCOLOR"
    …e width="160" border="0" cellpadding="1" cellspacing="0" bordercolor="#000000">

    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 826, Column 84: document type does not allow element "TABLE" here
    …e width="160" border="0" cellpadding="1" cellspacing="0" bordercolor="#000000">

    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 827, Column 18: document type does not allow element "DIV" here
    <div align="left">

    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 849, Column 7: name start character invalid: only S separators and TAGC allowed here
    </div align="left"></table></td></tr><tr><td>&nbsp;</td><td align="left" valign…
  • Error Line 849, Column 8: character data is not allowed here
    </div align="left"></table></td></tr><tr><td>&nbsp;</td><td align="left" valign…

    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.
  • Error Line 849, Column 27: end tag for "TABLE" which is not finished
    </div align="left"></table></td></tr><tr><td>&nbsp;</td><td align="left" valign…

    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 849, Column 32: "TABLE" not finished but containing element ended
    </div align="left"></table></td></tr><tr><td>&nbsp;</td><td align="left" valign…
  • Error Line 849, Column 32: end tag for "TABLE" omitted, but its declaration does not permit this
    </div align="left"></table></td></tr><tr><td>&nbsp;</td><td align="left" valign…
    • 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 824, Column 2: start tag was here
     <table width="98%" border="0" align="center" cellpadding="0" cellspacing="0">
  • Error Line 849, Column 32: end tag for "TABLE" omitted, but its declaration does not permit this
    </div align="left"></table></td></tr><tr><td>&nbsp;</td><td align="left" valign…
    • 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 533, Column 1: start tag was here
    <table width="160" border="0" cellpadding="1" cellspacing="0" class="tableT3">
  • Error Line 889, Column 15: invalid comment declaration: found name start character outside comment but inside comment declaration
    To find out-- check back later or--
  • Info Line 887, Column 1: comment declaration started here
    <!--<BR>Which team will be the next selection?
  • Error Line 896, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <P>

    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 901, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <P>

    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 940, Column 110: NET-enabling start-tag requires SHORTTAG YES
    …locks.com/openx/www/delivery/avw.php?zoneid=47&amp;n=13be9cc' /></a></noscript>

    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 955, Column 110: NET-enabling start-tag requires SHORTTAG YES
    …locks.com/openx/www/delivery/avw.php?zoneid=49&amp;n=6d535f8' /></a></noscript>

    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 978, Column 110: NET-enabling start-tag requires SHORTTAG YES
    …locks.com/openx/www/delivery/avw.php?zoneid=48&amp;n=425cf75' /></a></noscript>

    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 997, Column 19: an attribute value must be a literal unless it contains only name characters
    <FONT FACE=Verdana, Arial, Helvetica, Sans size=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 997, Column 26: "ARIAL" is not a member of a group specified for any attribute
    <FONT FACE=Verdana, Arial, Helvetica, Sans size=2>
  • Error Line 997, Column 37: "HELVETICA" is not a member of a group specified for any attribute
    <FONT FACE=Verdana, Arial, Helvetica, Sans size=2>
  • Error Line 997, Column 44: "SANS" is not a member of a group specified for any attribute
    <FONT FACE=Verdana, Arial, Helvetica, Sans size=2>
  • Error Line 1016, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <P><B>Membership</B><BR>

    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 1019, Column 15: NET-enabling start-tag requires SHORTTAG YES
    <A HREF=https://footballlocks.com/cgi-bin/order.cgi?pick_id=0>here.</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 1019, Column 71: end tag for element "A" which is not open
    <A HREF=https://footballlocks.com/cgi-bin/order.cgi?pick_id=0>here.</A> 

    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 1021, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <P>

    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 1027, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <P>

    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 1035, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <P>

    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 1038, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <P>

    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 1049, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <P><B>Review 2012 Regular Season Win Total Future Lines</B><BR>

    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 1059, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <P><B>2014 Super Bowl Odds</B><BR>

    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 1070, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <P><B>NFL Standing Projections</B><BR>

    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 1087, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <P><B>Free NFL Predictions for the 2012 - 2013 Season</B><BR>

    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 1098, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <P><B>NFL Schedules</B><BR>

    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 1132, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <P><B>Ordering and Accessing Football<I>LOCKS</I>.com's Pro Football Picks</B><…

    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 1133, Column 4: end tag for element "B" which is not open
    </B>

    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 1143, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <P>

    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 1152, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <P><B>Sample Free Football Picks</B><BR>

    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 1164, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <P>

    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 1180, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <P>

    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 1186, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <P>

    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 1196, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <P>Get the Super Bowl NFL Sunday pick by clicking the following

    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 1201, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <P>

    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 1210, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <P>

    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 1224, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <P>

    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 1230, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <P>

    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 1242, Column 29: document type does not allow element "NOSCRIPT" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    // ]]> --></script><noscript>

    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 1244, Column 110: NET-enabling start-tag requires SHORTTAG YES
    …ww.footballlocks.com/openx/www/delivery/avw.php?zoneid=61&amp;n=63ce103' /></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 1255, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <P>

    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 1268, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <P>

    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 1278, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <P>

    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 1284, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <P> 

    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 1299, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <P><BR>

    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 1301, Column 8: document type does not allow element "CENTER" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <center>

    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 1306, Column 170: NET-enabling start-tag requires SHORTTAG YES
    …src="images2/satisfaction.gif" width="80" height="80" border="0" align="top" />

    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 1306, Column 170: required attribute "ALT" not specified
    …src="images2/satisfaction.gif" width="80" height="80" border="0" align="top" />

    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 1308, Column 58: document type does not allow element "A" here
    …otballlocks.com/cgi-bin/sub_order.cgi"><img src="images2/JoinNow.gif" width="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 1308, Column 124: required attribute "ALT" not specified
    …b_order.cgi"><img src="images2/JoinNow.gif" width="114" height="24" border="0">

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

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

  • Error Line 1311, Column 9: end tag for "A" omitted, but its declaration does not permit this
    </center>
    • 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 1306, Column 1: start tag was here
    <a style="text-decoration:none" href="https://footballlocks.com/cgi-bin/sub_ord…
  • Error Line 1316, Column 5: end tag for "FONT" omitted, but its declaration does not permit this
    </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 997, Column 1: start tag was here
    <FONT FACE=Verdana, Arial, Helvetica, Sans size=2>
  • Error Line 1331, Column 16: document type does not allow element "DIV" here
    <div align=left>

    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 1339, Column 8: end tag for "TABLE" which is not finished
    </table>

    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 1348, Column 35: document type does not allow element "TD" here
    <td align="center" valign="middle"><span style="font-size:14.0pt;font-family:Ge…

    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 1348, Column 97: end tag for element "P" which is not open
    …14.0pt;font-family:Georgia"></span></p><p class=MsoNormal style='line-height:1…

    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 1349, Column 56: element "O:P" undefined
    …-size:10.0pt;font-family:Verdana'><o:p></o:p></span></p></td></tr></table></td…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1349, Column 83: end tag for "CENTER" omitted, but its declaration does not permit this
    …rdana'><o:p></o:p></span></p></td></tr></table></td></tr></table></td></tr></t…
    • 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 873, Column 1: start tag was here
    <CENTER>
  • Warning Line 1360, Column 111: NET-enabling start-tag requires SHORTTAG YES
    …//www.footballlocks.com/openx/www/delivery/avw.php?zoneid=122&amp;n=1eeb36c' />

    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 1370, Column 110: NET-enabling start-tag requires SHORTTAG YES
    …ww.footballlocks.com/openx/www/delivery/avw.php?zoneid=33&amp;n=67bb3f5' /></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 1378, Column 110: NET-enabling start-tag requires SHORTTAG YES
    …locks.com/openx/www/delivery/avw.php?zoneid=87&amp;n=a0a006d' /></a></noscript>

    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 1402, Column 88: "TD" is not a member of a group specified for any attribute
    …padding="0" cellspacing="0"><tr><td width ="915" td height="30" align="center">
  • Error Line 1403, Column 35: "TD" is not a member of a group specified for any attribute
    </td></tr><tr><td width ="915" td height="30" align="center" class="normalblack…
  • Warning Line 1409, Column 111: NET-enabling start-tag requires SHORTTAG YES
    …ocks.com/openx/www/delivery/avw.php?zoneid=112&amp;n=7fb0b74' /></a></noscript>

    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 1412, Column 67: name start character invalid: only S separators and TAGC allowed here
    …ons@Football<em>LOCKS</em>.com </font color></FONT FACE="Verdana, Arial, Helve…
  • Error Line 1412, Column 80: name start character invalid: only S separators and TAGC allowed here
    …em>LOCKS</em>.com </font color></FONT FACE="Verdana, Arial, Helvetica, Sans" s…
  • Error Line 1412, Column 129: end tag for element "P" which is not open
    …na, Arial, Helvetica, Sans" size=2></p><p align="center"><P>&nbsp;</p></td></t…

    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 1413, Column 25: "TD" is not a member of a group specified for any attribute
    <tr><td width ="915" td height="30" align="center"><FONT FACE="Verdana, Arial, …
  • Error Line 1415, Column 109: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …erms and conditions</a> of site use.<p></FONT FACE="Verdana, Arial, Helvetica,…

    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 1415, Column 117: name start character invalid: only S separators and TAGC allowed here
    … conditions</a> of site use.<p></FONT FACE="Verdana, Arial, Helvetica, Sans" s…
  • Error Line 1415, Column 197: "TD" is not a member of a group specified for any attribute
    …e=2></td></tr><tr><td width ="915" td height="30" align="center" class="white"…
  • Error Line 1420, Column 35: "TD" is not a member of a group specified for any attribute
    </td></tr><tr><td width ="915" td height="30" align="center" class="normalblack…
  • Error Line 1420, Column 193: name start character invalid: only S separators and TAGC allowed here
    …- 2013 Football<I>LOCKS</I>.com</FONT FACE="Verdana, Arial, Helvetica, Sans" s…
  • Error Line 1437, Column 7: end tag for "TABLE" omitted, but its declaration does not permit this
    </body>
    • 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 51, Column 1: start tag was here
    <table border="0" width="100%" align="center" cellpadding="0" cellspacing="0">

Visitor Analysis

Daily Visitor
  • 82 visits
Daily Visitor