Free math lessons and math homework help from basic math to algebra, geometry and beyond. Students, teachers, parents, and everyone can find solutions to their math problems instantly. ...

math.com
  • Domain Name
    math.com
  • Favicon
  • Google Page Rank
    6
  • Alexa Rank
    #22487
  • Page Size
    21.6 KB
  • Ip Address
    74.86.197.236
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    39 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
    Math.com - World of Math Online
  • Meta Keyword
    math, fractions, homework, pi, mathematician, fraction, algebra, geometry, number, numbers, equation, equations, math anxiety, homeschool math, math problems, math games, mental math, math puzzles, decimal, percent, mathematics, math magic, mathmagic, math homework, pre-algebra, converter, convert, prime number, ratio, probability, statistics, calculate, calculator, statistic, calculus, circle, trigonometry, tessellation, tesellation, tesselation, teselation, fractal, fractol, word problems, word problem, Pythagorean Theorem, multiply, divide, division, multiplication, quadratic, square, circle, triangle, trapezoid, polygon, solve, formula, area, perimeter, volume, unit, unit conversion, conversion, measure, measurement, change units, math resources, math history, mathematical, maths, maths problem, maths problems, converting, calculating
  • Meta Description
    Free math lessons and math homework help from basic math to algebra, geometry and beyond. Students, teachers, parents, and everyone can find solutions to their math problems instantly.

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    74.86.197.236
  • Domain Age
    14 Years, 4 Months, 9 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Sat, 02 Feb 2013 17:30:45 GMT
  • server: Apache
  • vary: Accept-Encoding
  • content-encoding: gzip
  • accept-ranges: none
  • content-length: 5377
  • content-type: text/html; charset=UTF-8
  • age: 23
  • x-google-cache-control: remote-cache-hit
  • via: HTTP/1.1 GWA (remote cache hit)
Registrant:
Leap of Faith Financial Services Inc.
34 Burnfield Avenue
Toronto, ON M6G 1Y5
CA

Domain name: MATH.COM

Administrative Contact:
Kirikos, George email
34 Burnfield Avenue
Toronto, ON M6G 1Y5
CA
416-588-0269 Fax: 416-588-5641

Technical Contact:
Kirikos, George email
34 Burnfield Avenue
Toronto, ON M6G 1Y5
CA
416-588-0269 Fax: 416-588-5641


Record last updated on 18-Nov-2011.
Record expires on 12-Nov-2021.
Record created on 10-Sep-1998.


Domain servers in listed order:
DNS1.EASYDNS.COM
DNS4.EASYDNS.INFO
DNS2.EASYDNS.NET
DNS3.EASYDNS.ORG

Domain status: clientTransferProhibited
clientUpdateProhibited
serverDeleteProhibited
serverTransferProhibited

DNS Analysis


DNS servers
dns3.easydns.org [64.68.195.10]
dns1.easydns.com [64.68.192.210]
dns2.easydns.net [72.52.2.1]
dns4.easydns.info [194.0.2.19]


DNS Records

Answer records
math.com A 74.86.197.236 10800s
math.com NS  dns1.easydns.com 10800s
math.com NS  dns2.easydns.net 10800s
math.com NS  dns3.easydns.org 10800s
math.com NS  dns4.easydns.info 10800s
math.com MX
preference: 5
exchange: sitemail.everyone.net
10800s
math.com SOA
server: dns0.easydns.com
email: zone@easydns.com
serial: 1355488884
refresh: 43200
retry: 10800
expire: 604800
minimum ttl: 10800
10800s

Authority records

Additional records

IP 74.86.197.236 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Dallas
  • Continent Code
    75207
  • Latitude
    214
  • Longitude
    623
  • %rwhois V-1.5:003fff:00 rwhois.softlayer.com (by Network Solutions, Inc. V-1.5.9.5)
    network:Class-Name:network
    network:ID:NETBLK-SOFTLAYER.74.86.192.0/19
    network:Auth-Area:74.86.192.0/19
    network:Network-Name:SOFTLAYER-74.86.192.0
    network:IP-Network:74.86.197.236/30
    network:IP-Network-Block:74.86.197.236-74.86.197.239
    network:Organization;I:Blend Interactive
    network:Street-Address:6400 W 56th St
    network:City:Sioux Falls
    network:State:SD
    network:Postal-Code:57104
    network:Country-Code:US
    network:Tech-Contact;I:sysadmins@softlayer.com
    network:Abuse-Contact;I:abuse@blendinteractive.com
    network:Admin-Contact;I:IPADM258-ARIN
    network:Created:2007-10-17 14:49:06
    network:Updated:2010-11-19 17:48:11
    network:Updated-By:ipadmin@softlayer.com

    %ok

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 53 Errors
  • 10 Warnings
Ratio Text/Html
  • 0.6042418772563176
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.

  • Error Line 84, Column 36: there is no attribute "LEFTMARGIN"
    <body bgcolor="#FFFFFF" leftmargin=0 topmargin=0 marginheight=0 marginwidth=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 84, Column 48: there is no attribute "TOPMARGIN"
    …olor="#FFFFFF" leftmargin=0 topmargin=0 marginheight=0 marginwidth=0" remonLoa…

    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 84, Column 63: there is no attribute "MARGINHEIGHT"
    …leftmargin=0 topmargin=0 marginheight=0 marginwidth=0" remonLoad="self.focus()…

    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 84, Column 77: there is no attribute "MARGINWIDTH"
    …eftmargin=0 topmargin=0 marginheight=0 marginwidth=0" remonLoad="self.focus()">

    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 84, Column 78: an attribute specification must start with a name or name token
    …eftmargin=0 topmargin=0 marginheight=0 marginwidth=0" remonLoad="self.focus()">

    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 88, Column 32: required attribute "TYPE" not specified
      <script language="JavaScript">

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

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

  • Error Line 200, Column 39: there is no attribute "HEIGHT"
    <table width="100%" border="0" height="26" cellspacing="0" 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 276, Column 30: there is no attribute "VALIGN"
    				<table border="0" valign="middle" cellspacing="0" 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 304, Column 72: required attribute "ALT" not specified
        <td><img src="images/nada.gif" align="bottom" border="0" height="6"></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 314, Column 38: invalid comment declaration: found name character outside comment but inside comment declaration
        <!--- START OF LEFT NAVIGATION --->
  • Info Line 314, Column 5: comment declaration started here
        <!--- START OF LEFT NAVIGATION --->
  • Error Line 314, Column 39: character data is not allowed here
        <!--- START OF LEFT NAVIGATION --->

    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 326, Column 129: required attribute "ALT" not specified
    …ht"><img src="/images/or_solid_top_rt_whitebk.gif" width="11" height="17"></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 359, Column 75: there is no attribute "BORDERCOLOR"
    …e width="140" border="1" cellspacing="0" cellpadding="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 359, Column 84: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …e width="140" border="1" cellspacing="0" cellpadding="0" bordercolor="#000000">

    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 365, Column 112: document type does not allow element "FORM" here
    …ction="http://math.mail.everyone.net/email/scripts/loginuser.pl" method="post">

    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 366, Column 32: document type does not allow element "TR" here
              <tr bgcolor="#6666CC"> 

    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 372, Column 32: document type does not allow element "TR" here
              <tr bgcolor="#6666CC"> 

    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 377, Column 32: document type does not allow element "TR" here
              <tr bgcolor="#DCDCDC"> 

    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 384, Column 14: 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 400, Column 105: required attribute "ALT" not specified
    …><img src="/images/nada.gif" width=5 height=18 hspace=0 vspace=0 border=0></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 404, Column 130: required attribute "ALT" not specified
    …t"><img src="/images/or_solid_top_rt_yellowbk.gif" width="11" height="17"></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 415, 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).

  • Warning Line 422, Column 89: NET-enabling start-tag requires SHORTTAG YES
    …put type="hidden" name="cx" value="partner-pub-2258608561945403:ykari17lksb" />

    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 423, Column 58: NET-enabling start-tag requires SHORTTAG YES
            <input type="hidden" name="cof" value="FORID:10" />

    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 424, Column 59: NET-enabling start-tag requires SHORTTAG YES
            <input type="hidden" name="ie" value="ISO-8859-1" />

    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 425, Column 47: NET-enabling start-tag requires SHORTTAG YES
            <input type="text" name="q" size="10" />

    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 426, Column 55: NET-enabling start-tag requires SHORTTAG YES
            <input type="submit" name="sa" value="Search" />

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

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

  • Warning Line 431, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …w.google.com/images/poweredby_transparent/poweredby_FFFFFF.gif" alt="Google" />

    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 446, Column 17: there is no attribute "SIZE"
    <g:plusone size="medium"></g:plusone>

    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 446, Column 25: element "G:PLUSONE" undefined
    <g:plusone size="medium"></g:plusone>

    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 448, Column 149: NET-enabling start-tag requires SHORTTAG YES
    …/images/math_jobs.gif" alt="Math Jobs" width="80" height="15" border="0" /></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 459, Column 51: invalid comment declaration: found name character outside comment but inside comment declaration
        <!-- END of Left navigation ------------------->
  • Info Line 459, Column 5: comment declaration started here
        <!-- END of Left navigation ------------------->
  • Error Line 459, Column 52: character data is not allowed here
        <!-- END of Left navigation ------------------->

    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 467, Column 31: invalid comment declaration: found name character outside comment but inside comment declaration
            <!-- [TOP TABLE]------->
  • Info Line 467, Column 9: comment declaration started here
            <!-- [TOP TABLE]------->
  • Error Line 467, Column 32: character data is not allowed here
            <!-- [TOP TABLE]------->

    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 513, Column 78: required attribute "ALT" not specified
    …colspan=2><img src="/images/hotsubject_title.gif" width="142" height="28"></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 517, Column 95: required attribute "ALT" not specified
    …gn="right" width="9"><img src="/images/nada.gif" width=5 height=6 border=0><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 518, Column 62: required attribute "ALT" not specified
    <img src="/images/arrow_red_sm.gif" width=5 height=7 border=0></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 523, Column 95: required attribute "ALT" not specified
    …gn="right" width="9"><img src="/images/nada.gif" width=5 height=6 border=0><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 524, Column 62: required attribute "ALT" not specified
    <img src="/images/arrow_red_sm.gif" width=5 height=7 border=0></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 529, Column 95: required attribute "ALT" not specified
    …gn="right" width="9"><img src="/images/nada.gif" width=5 height=6 border=0><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 530, Column 62: required attribute "ALT" not specified
    <img src="/images/arrow_red_sm.gif" width=5 height=7 border=0></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 535, Column 95: required attribute "ALT" not specified
    …gn="right" width="9"><img src="/images/nada.gif" width=5 height=6 border=0><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 536, Column 62: required attribute "ALT" not specified
    <img src="/images/arrow_red_sm.gif" width=5 height=7 border=0></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 541, Column 95: required attribute "ALT" not specified
    …gn="right" width="9"><img src="/images/nada.gif" width=5 height=6 border=0><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 542, Column 62: required attribute "ALT" not specified
    <img src="/images/arrow_red_sm.gif" width=5 height=7 border=0></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 547, Column 95: required attribute "ALT" not specified
    …gn="right" width="9"><img src="/images/nada.gif" width=5 height=6 border=0><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 548, Column 62: required attribute "ALT" not specified
    <img src="/images/arrow_red_sm.gif" width=5 height=7 border=0></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 553, Column 95: required attribute "ALT" not specified
    …gn="right" width="9"><img src="/images/nada.gif" width=5 height=6 border=0><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 554, Column 62: required attribute "ALT" not specified
    <img src="/images/arrow_red_sm.gif" width=5 height=7 border=0></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 579, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <p>Find <a href="http://jobs.math.com/" target="_new"><b>math jobs</b></a> at t…

    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 582, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <p>We hope your visit to math.com brings you a greater love of mathematics, bot…

    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 584, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <p> <b>Einstein, Albert (1879-1955)<br> </b>Do not worry about your difficultie…

    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 585, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <p><b>Dirac, Paul Adrien Maurice (1902-1984)<br> </b>Mathematics is

    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 588, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <p> <b>Egrafov, M.<br> </b>If you ask mathematicians what they do,

    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 599, Column 31: invalid comment declaration: found name character outside comment but inside comment declaration
            <!-- [TOP TABLE]------->
  • Info Line 599, Column 9: comment declaration started here
            <!-- [TOP TABLE]------->
  • Error Line 599, Column 32: character data is not allowed here
            <!-- [TOP TABLE]------->

    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 619, Column 23: invalid comment declaration: found name character outside comment but inside comment declaration
    		<!--- p>&nbsp;<br --->
  • Info Line 619, Column 3: comment declaration started here
    		<!--- p>&nbsp;<br --->
  • Error Line 629, Column 34: end tag for element "P" which is not open
            Policy</a>.</b></font></p>

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

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

Visitor Analysis

Daily Visitor
  • 10.850 visits
Daily Visitor