Member Sign In Not a Member? Join edHelper.com    What's New? Teacher Ideas Monthly Create Puzzles Runaway Math Puzzles   Foreign Languages Search: edHelper.com Newsletter Enter your e-mail address to receive the FREE ...

edhelper.com
  • Domain Name
    edhelper.com
  • Favicon
  • Google Page Rank
    6
  • Alexa Rank
    #33751
  • Page Size
    37.9 KB
  • Ip Address
    69.64.173.203
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    4 GIF, 11 JPG, 0 PNG

Website Meta Analysis

  • Title
    edHelper.com - Math, Reading Comprehension, Themes, Lesson Plans, and Printable Worksheets
  • Meta Keyword
    edHelper, edHelper.com, theme units, WebQuests, Teacher tools, homeschool, kindergarten, math, middle school math, algebra, animals, science, health, geography, united states, social study, classroom helpers, language arts, phonics, spelling, vocabulary, reading comprehension, writing, daily skills review, monthly theme, test prep
  • Meta Description
    Member Sign In Not a Member? Join edHelper.com    What's New? Teacher Ideas Monthly Create Puzzles Runaway Math Puzzles   Foreign Languages Search: edHelper.com Newsletter Enter your e-mail address to receive the FREE edHelper.com newsletter: ...

Technical Analysis

  • Webserver
    Apache/2.0.52 (Red Hat)
  • Ip Address
    69.64.173.203
  • Domain Age
    12 Years, 7 Months, 0 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Sun, 17 Feb 2013 20:07:23 GMT
  • server: Apache/2.0.52 (Red Hat)
  • last-modified: Fri, 15 Feb 2013 02:41:28 GMT
  • etag: "683c1-7b43-4d5ba4fe6c600"
  • accept-ranges: bytes
  • content-length: 31555
  • content-type: text/html
  • age: 18
  • x-google-cache-control: remote-cache-hit
  • via: HTTP/1.1 GWA (remote cache hit)
No data whois for edhelper.com

DNS Analysis


DNS servers
dns1.nettica.com [64.94.136.11]
dns2.nettica.com [64.237.45.34]
dns3.nettica.com [64.94.136.13]
dns4.nettica.com [69.41.170.223]
dns5.nettica.com [212.100.247.15]


DNS Records

Answer records
edhelper.com NS  dns4.nettica.com 86400s
edhelper.com NS  dns5.nettica.com 86400s
edhelper.com SOA
server: dns1.nettica.com
email: hostmaster@nettica.com
serial: 566
refresh: 21600
retry: 7200
expire: 604800
minimum ttl: 86400
86400s
edhelper.com TXT v=spf1 a mx ip4:64.41.127.87 ip4:69.64.173.204 ip4:216.139.215.244 ip4:69.64.173.206 ip4:64.26.61.162 ip4:69.64.173.199 include:aspmx.googlemail.com ~all 86400s
edhelper.com TXT v=spf1 a mx ip4:64.41.127.87 ip4:69.64.173.204 ip4:69.64.173.206 ip4:64.26.61.162 ip4:216.139.215.244 ip4:69.64.173.199 include:aspmx.googlemail.com ~all 86400s
edhelper.com A 69.64.173.203 1800s

Authority records

Additional records

IP 69.64.173.203 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Houston
  • Continent Code
    77008
  • Latitude
    713
  • Longitude
    618
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 69.64.173.203"
    #
    # Use "?" to get help.
    #

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

    NetRange: 69.64.160.0 - 69.64.191.255
    CIDR: 69.64.160.0/19
    OriginAS: AS14127
    NetName: ILAND-NET-1
    NetHandle: NET-69-64-160-0-1
    Parent: NET-69-0-0-0-0
    NetType: Direct Allocation
    Comment: http://www.iland.com/
    RegDate: 2003-07-31
    Updated: 2012-12-03
    Ref: http://whois.arin.net/rest/net/NET-69-64-160-0-1

    OrgName: Iland Internet Solutions Corporation
    OrgId: IISC-1
    Address: 1235 North Loop West
    Address: Suite 205
    City: Houston
    StateProv: TX
    PostalCode: 77008
    Country: US
    RegDate: 1999-05-21
    Updated: 2012-11-20
    Comment: http://iland.com
    Ref: http://whois.arin.net/rest/org/IISC-1

    OrgNOCHandle: NOC1517-ARIN
    OrgNOCName: NOC
    OrgNOCPhone: +1-713-868-2267
    OrgNOCEmail: noc@iland.com
    OrgNOCRef: http://whois.arin.net/rest/poc/NOC1517-ARIN

    OrgAbuseHandle: ILAND-ARIN
    OrgAbuseName: iland Abuse
    OrgAbusePhone: +1-713-868-2267
    OrgAbuseEmail: abuse@iland.com
    OrgAbuseRef: http://whois.arin.net/rest/poc/ILAND-ARIN

    OrgTechHandle: NOC1517-ARIN
    OrgTechName: NOC
    OrgTechPhone: +1-713-868-2267
    OrgTechEmail: noc@iland.com
    OrgTechRef: http://whois.arin.net/rest/poc/NOC1517-ARIN

    OrgTechHandle: JEG95-ARIN
    OrgTechName: Giardina, Justin E
    OrgTechPhone: +1-713-868-2268
    OrgTechEmail: jg@iland.com
    OrgTechRef: http://whois.arin.net/rest/poc/JEG95-ARIN

    RTechHandle: NOC1517-ARIN
    RTechName: NOC
    RTechPhone: +1-713-868-2267
    RTechEmail: noc@iland.com
    RTechRef: http://whois.arin.net/rest/poc/NOC1517-ARIN

    RAbuseHandle: ILAND-ARIN
    RAbuseName: iland Abuse
    RAbusePhone: +1-713-868-2267
    RAbuseEmail: abuse@iland.com
    RAbuseRef: http://whois.arin.net/rest/poc/ILAND-ARIN

    RNOCHandle: NOC1517-ARIN
    RNOCName: NOC
    RNOCPhone: +1-713-868-2267
    RNOCEmail: noc@iland.com
    RNOCRef: http://whois.arin.net/rest/poc/NOC1517-ARIN

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 82 Errors
  • 6 Warnings
Ratio Text/Html
  • 0.6624336716294884
Message Error
  • Error Line 1, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
    <html>

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

  • Warning Line 4, Column 79: NET-enabling start-tag requires SHORTTAG YES
    <meta name="verify-v1" content="YPW7Wm1B4ZqEJDaCB59fepWtvUXDHLOx+Ef9g+orle4=" />

    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 5, Column 365: document type does not allow element "META" here
    …reading comprehension, writing, daily skills review, monthly theme, test prep">

    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 6, 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 37, Column 23: "FPROLLOVERSTYLE" is not a member of a group specified for any attribute
    <style fprolloverstyle>A:hover {color: #FF0000}
  • Error Line 37, Column 23: required attribute "TYPE" not specified
    <style fprolloverstyle>A:hover {color: #FF0000}

    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 37, Column 23: document type does not allow element "STYLE" here
    <style fprolloverstyle>A:hover {color: #FF0000}

    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 67, Column 7: end tag for element "HEAD" which is not open
    </head>

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

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

  • Error Line 68, Column 17: there is no attribute "TOPMARGIN"
    <body topmargin="0" leftmargin="0" rightmargin="0" marginheight="0" marginwidth…

    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 68, Column 32: there is no attribute "LEFTMARGIN"
    <body topmargin="0" leftmargin="0" rightmargin="0" marginheight="0" marginwidth…

    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 68, Column 48: there is no attribute "RIGHTMARGIN"
    …margin="0" leftmargin="0" rightmargin="0" marginheight="0" marginwidth="0" bgc…

    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 68, Column 65: there is no attribute "MARGINHEIGHT"
    …rgin="0" rightmargin="0" marginheight="0" marginwidth="0" bgcolor="#FFFFFF" on…

    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 68, Column 81: there is no attribute "MARGINWIDTH"
    …rgin="0" marginheight="0" marginwidth="0" bgcolor="#FFFFFF" onload="JavaScript…

    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 68, Column 137: document type does not allow element "BODY" here
    …eight="0" marginwidth="0" bgcolor="#FFFFFF" onload="JavaScript:mainformload()">

    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 103, Column 15: there is no attribute "HEIGHT"
    <TABLE height=40 cellpadding=0 cellspacing=0 width=100%><TR valign=center align…

    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 103, Column 55: an attribute value must be a literal unless it contains only name characters
    …t=40 cellpadding=0 cellspacing=0 width=100%><TR valign=center align=center><TD>

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

  • Error Line 103, Column 68: value of attribute "VALIGN" cannot be "CENTER"; must be one of "TOP", "MIDDLE", "BOTTOM", "BASELINE"
    …t=40 cellpadding=0 cellspacing=0 width=100%><TR valign=center align=center><TD>

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

  • Error Line 112, Column 164: required attribute "ALT" not specified
    …c="http://www.edhelperclipart.com/clipart/edhelpersideasprevtheme.jpg"></a><BR>

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

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

  • Error Line 115, Column 138: required attribute "ALT" not specified
    … src="http://www.edhelperclipart.com/clipart/puzzleshtmindexlink1.jpg"></a><BR>

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

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

  • Error Line 123, Column 41: end tag for "SCRIPT" omitted, but its declaration does not permit this
    document.writeln("<CENTER>"+S1+"</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 119, Column 1: start tag was here
    <SCRIPT language="JavaScript" type="text/javascript">
  • Error Line 123, Column 41: end tag for "TABLE" omitted, but its declaration does not permit this
    document.writeln("<CENTER>"+S1+"</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 97, Column 1: start tag was here
    <table border="0" cellpadding="0" cellspacing="0" align="center" width="700">
  • Error Line 123, Column 41: end tag for "TABLE" omitted, but its declaration does not permit this
    document.writeln("<CENTER>"+S1+"</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 94, Column 1: start tag was here
    <table width="100%"><TR><TD>&nbsp;&nbsp;</TD><TD>
  • Error Line 125, Column 9: end tag for element "SCRIPT" which is not open
    </SCRIPT>

    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 127, Column 8: 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 140, Column 146: required attribute "ALT" not specified
    …p://www.edhelperclipart.com/clipart/runawaymathsmalllogo.gif" border=0></a><BR>

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

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

  • Error Line 141, Column 13: an attribute value must be a literal unless it contains only name characters
    <FONT color=#000099 face="Arial, Helvetica, sans-serif" size=3><b>

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

    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 144, Column 11: end tag for element "FONT" which is not open
    </b></FONT>

    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 170, Column 133: document type does not allow element "FORM" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME" start-tag
    ….cgi" METHOD="POST" onsubmit="javascript:urchinTracker('/search/index_html');">

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

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

  • Error Line 202, Column 144: document type does not allow element "FORM" here
    …D="POST" onsubmit="javascript:urchinTracker('/newsletter_signup/index_html');">

    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 203, Column 4: document type does not allow element "TR" here
    <TR><TD WIDTH = "180" ALIGN="left"><FONT SIZE="-1">Enter your e-mail address to…

    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 205, Column 18: end tag for "FORM" omitted, but its declaration does not permit this
    </TD></TR></TABLE>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 202, Column 1: start tag was here
    <FORM ACTION="http://www.edhelpernews.com/cgi-bin/news.cgi" METHOD="POST" onsub…
  • Error Line 205, Column 18: end tag for "TABLE" which is not finished
    </TD></TR></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 206, Column 7: end tag for element "FORM" which is not open
    </FORM></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 270, Column 13: end tag for element "TD" which is not open
    </TABLE></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 272, Column 27: document type does not allow element "TD" here
    <td width="5" valign="top">&nbsp;&nbsp;&nbsp;</td>

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

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

  • Error Line 275, Column 29: document type does not allow element "TD" here
    <td width="405" valign="top">

    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 277, Column 71: there is no attribute "VALIGN"
    …LLSPACING="0" CELLPADDING="0" BORDER="0" ALIGN="left" VALIGN="top" width="405">

    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 280, Column 55: an attribute value must be a literal unless it contains only name characters
    <TABLE height=40 cellpadding=0 cellspacing=0 width=100%><TR valign=center><TD>

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

  • Error Line 280, Column 68: value of attribute "VALIGN" cannot be "CENTER"; must be one of "TOP", "MIDDLE", "BOTTOM", "BASELINE"
    <TABLE height=40 cellpadding=0 cellspacing=0 width=100%><TR valign=center><TD>

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

  • Error Line 337, Column 11: value of attribute "ALIGN" cannot be "MIDDLE"; must be one of "LEFT", "CENTER", "RIGHT", "JUSTIFY", "CHAR"
    <TD align=middle><a href="http://www.edhelper.com/leveled_readers.htm" target=_…

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

  • Error Line 337, Column 173: required attribute "ALT" not specified
    …"http://www.edhelperclipart.com/clipart/leveled_animalbooks_prev.jpg"></a></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 340, Column 11: value of attribute "ALIGN" cannot be "MIDDLE"; must be one of "LEFT", "CENTER", "RIGHT", "JUSTIFY", "CHAR"
    <TD align=middle><a href="http://www.edhelper.com/leveled_readers.htm" target=_…

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

  • Error Line 340, Column 98: an attribute value must be a literal unless it contains only name characters
    …eaders.htm" target=_blank><FONT color=#000099 face="Arial, Helvetica, sans-ser…

    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 345, Column 66: an attribute value must be a literal unless it contains only name characters
    … width="100%" cellpadding=1 cellspacing=0 bgcolor=#cccc99 ><TR> <TD width=100%>

    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 345, Column 93: an attribute value must be a literal unless it contains only name characters
    … width="100%" cellpadding=1 cellspacing=0 bgcolor=#cccc99 ><TR> <TD width=100%>

    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 352, Column 13: an attribute value must be a literal unless it contains only name characters
    <TR bgcolor=#ffffff><TD WIDTH="200" ALIGN="left" VALIGN="TOP">

    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 483, 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>").

  • Error Line 485, Column 92: required attribute "ALT" not specified
    …p://www.edhelperclipart.com/clipart/edhelperkucustommakelinkprev.jpg" 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 518, 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>").

  • Error Line 526, 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>").

  • Error Line 534, Column 8: 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 538, Column 56: end tag for element "B" which is not open
    S="&nbsp;<font face=arial size=\"2\"><b>Daily Themes</b></font><br>"+S+"<br>";

    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 538, Column 63: end tag for "SCRIPT" omitted, but its declaration does not permit this
    S="&nbsp;<font face=arial size=\"2\"><b>Daily Themes</b></font><br>"+S+"<br>";
    • 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 534, Column 1: start tag was here
    <SCRIPT>
  • Error Line 541, Column 9: end tag for element "SCRIPT" which is not open
    </SCRIPT>

    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 543, Column 8: 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 547, Column 68: end tag for element "B" which is not open
    …="&nbsp;<font face=arial size=\"2\"><b>Spanish Daily Reading</b></font><br>"+S;

    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 547, Column 75: end tag for element "FONT" which is not open
    …="&nbsp;<font face=arial size=\"2\"><b>Spanish Daily Reading</b></font><br>"+S;

    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 556, Column 45: an attribute value must be a literal unless it contains only name characters
    <TABLE cellpadding=0 cellspacing=0 width=100%>

    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 558, Column 12: an attribute value must be a literal unless it contains only name characters
    <TD width=4%><BR></TD>

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

  • Error Line 559, Column 13: an attribute value must be a literal unless it contains only name characters
    <TD width=44%><a href="http://www.edhelper.com/fractions.htm">Fractions</a><BR>

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

  • Error Line 581, Column 12: an attribute value must be a literal unless it contains only name characters
    <TD width=4%><BR></TD>

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

  • Error Line 582, Column 13: an attribute value must be a literal unless it contains only name characters
    <TD width=44%><a href="http://www.edhelper.com/multiplication.htm">Multiplicati…

    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 603, Column 12: an attribute value must be a literal unless it contains only name characters
    <TD width=4%><BR></TD>

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

  • Error Line 617, Column 21: invalid comment declaration: found name character outside comment but inside comment declaration
    <!------------------->
  • Info Line 609, Column 1: comment declaration started here
    <!------------------->
  • Error Line 621, Column 7: end tag for element "FONT" which is not open
    </font></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 627, Column 27: document type does not allow element "TD" here
    <td width="5" valign="top">&nbsp;&nbsp;&nbsp;</td>

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

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

  • Error Line 629, Column 29: document type does not allow element "TD" here
    <td width="180" valign="top">

    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 667, Column 86: required attribute "ALT" not specified
    …c="http://www.edhelperclipart.com/clipart/weeklyreadingbooksmall.jpg" 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 678, Column 85: required attribute "ALT" not specified
    …rc="http://www.edhelperclipart.com/clipart/activitycenter3_prev1.jpg" 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 699, Column 41: end tag for element "CENTER" which is not open
    document.writeln("<CENTER>"+S1+"</CENTER>");

    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 709, Column 41: end tag for element "CENTER" which is not open
    document.writeln("<CENTER>"+S1+"</CENTER>");

    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 721, Column 87: required attribute "ALT" not specified
    …="http://www.edhelperclipart.com/clipart/critthinkinglinkhtmpage.jpg" 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 731, Column 98: required attribute "ALT" not specified
    …w.edhelperclipart.com/clipart/pdfbookbeagoodspbkpl1311272923prev.gif" 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 741, Column 88: required attribute "ALT" not specified
    …"http://www.edhelperclipart.com/clipart/studentgamesspellingprev.jpg" 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 759, Column 82: required attribute "ALT" not specified
    …g src="http://www.edhelperclipart.com/clipart/curvywordstheme150.jpg" 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 825, Column 41: end tag for element "CENTER" which is not open
    document.writeln("<CENTER>"+S1+"</CENTER>");

    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 838, Column 5: end tag for element "TR" which is not open
    </tr></table>

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

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

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

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

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

  • Error Line 841, Column 5: end tag for element "TD" which is not open
    </TD></TR></TABLE>

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

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

  • Error Line 841, Column 10: end tag for element "TR" which is not open
    </TD></TR></TABLE>

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

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

  • Error Line 841, Column 18: end tag for element "TABLE" which is not open
    </TD></TR></TABLE>

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

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

  • Error Line 867, Column 9: end tag for element "CENTER" which is not open
    </center>

    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.

Visitor Analysis

Daily Visitor
  • 7.233 visits
Daily Visitor