Celebrity Addresses ...

fanmail.biz
  • Domain Name
    fanmail.biz
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #73102
  • Page Size
    12.3 KB
  • Ip Address
    64.251.26.110
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    7 GIF, 1 JPG, 0 PNG

Website Meta Analysis

  • Title
    ★ FanMail.biz: The Celebrity Addresses Database
  • Meta Keyword
    contact information, fan mail addresses, celeb email addresses, celebrities email addresses, fan mail, official mail, celebrity email, free, new
  • Meta Description
    Celebrity Addresses

Technical Analysis

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

Hyper Text Transfer Protocol (HTTP) header show data header response from fanmail.biz.

HTML Analysis

  • date: Wed, 22 Oct 2014 03:50:25 GMT
  • server: Apache/2.2.3 (CentOS)
  • x-powered-by: PHP/5.1.6
  • connection: close
  • content-type: text/html; charset=iso-8859-1
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain ID: D6113925-BIZ
Registrar: GODADDY.COM, INC.
Sponsoring Registrar IANA ID: 146
Registrar URL (registration services): whois.godaddy.com
Domain Status: clientDeleteProhibited
Domain Status: clientRenewProhibited
Domain Status: clientTransferProhibited
Domain Status: clientUpdateProhibited
Registrant ID: CR18662151
Registrant Domain Name: Jean-Pierre Lolivier
Registrant Address1: 1-B Haleluya Maison
Registrant Address2: 1-25-6 Tomigaya
Registrant City: Shibuya-ku
Registrant State/Province: Tokyo
Registrant Postal Code: 151-0063
Registrant Country: Japan
Registrant Country Code: JP
Registrant Phone Number: +81.13257540
Registrant Email: email
Administrative Contact ID: CR18662153
Administrative Contact Domain Name: Jean-Pierre Lolivier
Administrative Contact Address1: 1-B Haleluya Maison
Administrative Contact Address2: 1-25-6 Tomigaya
Administrative Contact City: Shibuya-ku
Administrative Contact State/Province: Tokyo
Administrative Contact Postal Code: 151-0063
Administrative Contact Country: Japan
Administrative Contact Country Code: JP
Administrative Contact Phone Number: +81.13257540
Administrative Contact Email: email
Billing Contact ID: CR18662154
Billing Contact Domain Name: Jean-Pierre Lolivier
Billing Contact Address1: 1-B Haleluya Maison
Billing Contact Address2: 1-25-6 Tomigaya
Billing Contact City: Shibuya-ku
Billing Contact State/Province: Tokyo
Billing Contact Postal Code: 151-0063
Billing Contact Country: Japan
Billing Contact Country Code: JP
Billing Contact Phone Number: +81.13257540
Billing Contact Email: email
Technical Contact ID: CR18662152
Technical Contact Domain Name: Jean-Pierre Lolivier
Technical Contact Address1: 1-B Haleluya Maison
Technical Contact Address2: 1-25-6 Tomigaya
Technical Contact City: Shibuya-ku
Technical Contact State/Province: Tokyo
Technical Contact Postal Code: 151-0063
Technical Contact Country: Japan
Technical Contact Country Code: JP
Technical Contact Phone Number: +81.13257540
Technical Contact Email: email
Name Servers: NS1.FANMAIL.BIZ
Name Servers: NS2.FANMAIL.BIZ
Created by Registrar: GODADDY.COM, INC.
Last Updated by Registrar: GODADDY.COM, INC.
Created: Fri Jan 23 01:18:18 GMT 2004
Expires: Sun Jan 22 23:59:59 GMT 2012
Updated: Tue Jan 18 10:52:05 GMT 2011

DNS Analysis


DNS servers
ns2.fanmail.biz [71.6.218.27]
ns1.fanmail.biz [71.6.218.26]


DNS Records

Answer records
fanmail.biz MX
preference: 5
exchange: ASPMX.L.GOOGLE.COM
86400s
fanmail.biz MX
preference: 10
exchange: ALT2.ASPMX.L.GOOGLE.COM
86400s
fanmail.biz MX
preference: 20
exchange: ASPMX3.GOOGLEMAIL.COM
86400s
fanmail.biz MX
preference: 10
exchange: ALT1.ASPMX.L.GOOGLE.COM
86400s
fanmail.biz MX
preference: 20
exchange: ASPMX2.GOOGLEMAIL.COM
86400s
fanmail.biz MX
preference: 20
exchange: ASPMX4.GOOGLEMAIL.COM
86400s
fanmail.biz MX
preference: 20
exchange: ASPMX5.GOOGLEMAIL.COM
86400s
fanmail.biz A 71.6.218.26 86400s
fanmail.biz SOA
server: ns1.fanmail.biz
email: email@example.COM
serial: 1214022944
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 10800
86400s
fanmail.biz NS  ns1.fanmail.biz 86400s

Authority records

Additional records

IP 64.251.26.110 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 68 Errors
  • 29 Warnings
Ratio Text/Html
  • 0.7543748011454025
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 8, Column 79: NET-enabling start-tag requires SHORTTAG YES
    <meta name="verify-v1" content="eOQTqBLN7eYE8RywcLozULc5LaGwVxG3Yc4vPRpzNWU=" />

    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 8, Column 80: character data is not allowed here
    <meta name="verify-v1" content="eOQTqBLN7eYE8RywcLozULc5LaGwVxG3Yc4vPRpzNWU=" />

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

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

    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 12, Column 71: NET-enabling start-tag requires SHORTTAG YES
    <meta name="msvalidate.01" content="97E8F18ED92E45CA9E9EA1DF53D9054C" />

    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 15, Column 18: NET-enabling start-tag requires SHORTTAG YES
    href="style.css" />

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

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

  • Error Line 16, 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 17, Column 6: document type does not allow element "BODY" here
    <body>

    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 18, Column 20: there is no attribute "COLOR"
    <hr size="1" color="#C0C0C0" align="left" width="800">

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

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

  • Info Line 22, Column 1: start tag was here
    <center> 
  • Error Line 45, Column 74: there is no attribute "BACKGROUND"
    …ellspacing="0" width="800" background="http://www.fanmail.biz/images/backgroun…

    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 45, Column 129: there is no attribute "HEIGHT"
    …h="800" background="http://www.fanmail.biz/images/background1.gif" height="89">

    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 48, Column 91: required attribute "ALT" not specified
    …http://www.fanmail.biz/actor/a/1.html" shape="rect" coords="212, 99, 268, 109">

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

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

  • Error Line 49, Column 52: value of attribute "SHAPE" cannot be "POLYGON"; must be one of "RECT", "CIRCLE", "POLY", "DEFAULT"
    …ttp://www.fanmail.biz/" shape="polygon" coords="102, 116, 273, 34, 275, 5, 3, …

    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 49, Column 103: required attribute "ALT" not specified
    …, 116, 273, 34, 275, 5, 3, 7, 30, 122"></map><img border="0" src="http://www.f…

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

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

  • Error Line 49, Column 217: required attribute "ALT" not specified
    …nmail.biz/images/fan_mail2.gif" usemap="#FPMap1" width="277" height="130"></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 51, Column 67: required attribute "ALT" not specified
    <center><img border="0" src="http://www.fanmail.biz/images/m1.gif"><br><br>

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

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

  • Error Line 53, Column 79: required attribute "ALT" not specified
    <area href="http://www.fanmail.biz/a/1.html" shape="rect" coords="0, 0, 8, 12">

    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 54, Column 81: required attribute "ALT" not specified
    …rea href="http://www.fanmail.biz/b/1.html" shape="rect" coords="18, 0, 26, 11">

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

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

  • Error Line 55, Column 81: required attribute "ALT" not specified
    …rea href="http://www.fanmail.biz/c/1.html" shape="rect" coords="34, 2, 43, 10">

    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 56, Column 81: required attribute "ALT" not specified
    …rea href="http://www.fanmail.biz/d/1.html" shape="rect" coords="51, 2, 62, 11">

    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 57, Column 80: required attribute "ALT" not specified
    <area href="http://www.fanmail.biz/e/1.html" shape="rect" coords="69, 2, 78, 9">

    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 58, Column 80: required attribute "ALT" not specified
    <area href="http://www.fanmail.biz/f/1.html" shape="rect" coords="85, 2, 92, 8">

    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 59, Column 82: required attribute "ALT" not specified
    …ea href="http://www.fanmail.biz/g/1.html" shape="rect" coords="103, 2, 112, 9">

    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 60, Column 82: required attribute "ALT" not specified
    …ea href="http://www.fanmail.biz/h/1.html" shape="rect" coords="119, 2, 130, 9">

    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 61, Column 82: required attribute "ALT" not specified
    …ea href="http://www.fanmail.biz/i/1.html" shape="rect" coords="137, 3, 144, 8">

    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 62, Column 82: required attribute "ALT" not specified
    …ea href="http://www.fanmail.biz/j/1.html" shape="rect" coords="152, 2, 161, 9">

    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 63, Column 82: required attribute "ALT" not specified
    …ea href="http://www.fanmail.biz/k/1.html" shape="rect" coords="168, 2, 176, 9">

    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 64, Column 82: required attribute "ALT" not specified
    …ea href="http://www.fanmail.biz/l/1.html" shape="rect" coords="184, 2, 193, 8">

    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 65, Column 82: required attribute "ALT" not specified
    …ea href="http://www.fanmail.biz/m/1.html" shape="rect" coords="202, 3, 212, 9">

    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 66, Column 83: required attribute "ALT" not specified
    …a href="http://www.fanmail.biz/n/1.html" shape="rect" coords="221, 2, 232, 10">

    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 67, Column 83: required attribute "ALT" not specified
    …a href="http://www.fanmail.biz/o/1.html" shape="rect" coords="240, 3, 249, 10">

    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 68, Column 82: required attribute "ALT" not specified
    …ea href="http://www.fanmail.biz/p/1.html" shape="rect" coords="257, 3, 264, 9">

    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 69, Column 83: required attribute "ALT" not specified
    …a href="http://www.fanmail.biz/q/1.html" shape="rect" coords="274, 3, 284, 11">

    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 70, Column 82: required attribute "ALT" not specified
    …ea href="http://www.fanmail.biz/r/1.html" shape="rect" coords="292, 2, 303, 8">

    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 71, Column 83: required attribute "ALT" not specified
    …a href="http://www.fanmail.biz/s/1.html" shape="rect" coords="310, 3, 320, 10">

    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 72, Column 82: required attribute "ALT" not specified
    …ea href="http://www.fanmail.biz/t/1.html" shape="rect" coords="327, 1, 336, 9">

    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 73, Column 83: required attribute "ALT" not specified
    …a href="http://www.fanmail.biz/u/1.html" shape="rect" coords="344, 3, 353, 11">

    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 74, Column 83: required attribute "ALT" not specified
    …a href="http://www.fanmail.biz/v/1.html" shape="rect" coords="361, 3, 371, 10">

    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 75, Column 83: required attribute "ALT" not specified
    …a href="http://www.fanmail.biz/w/1.html" shape="rect" coords="380, 2, 392, 11">

    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 76, Column 82: required attribute "ALT" not specified
    …ea href="http://www.fanmail.biz/x/1.html" shape="rect" coords="402, 1, 410, 9">

    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 77, Column 83: required attribute "ALT" not specified
    …a href="http://www.fanmail.biz/y/1.html" shape="rect" coords="418, 4, 426, 10">

    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 78, Column 83: required attribute "ALT" not specified
    … shape="rect" coords="433, 2, 444, 12"></map><img border="0" src="http://www.f…

    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 78, Column 192: required attribute "ALT" not specified
    …p://www.fanmail.biz/images/alpha.gif" width="461" height="13" usemap="#FPMap0">

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

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

  • Info Line 51, Column 1: start tag was here
    <center><img border="0" src="http://www.fanmail.biz/images/m1.gif"><br><br>
  • Error Line 84, Column 88: required attribute "ALT" not specified
    …f="http://www.fanmail.biz/actress/a/1.html" shape="rect" coords="0, 2, 65, 11">

    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 85, Column 90: required attribute "ALT" not specified
    …"http://www.fanmail.biz/singer/a/1.html" shape="rect" coords="221, 2, 268, 11">

    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 86, Column 91: required attribute "ALT" not specified
    …http://www.fanmail.biz/director/a/1.html" shape="rect" coords="82, 3, 140, 11">

    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 87, Column 89: required attribute "ALT" not specified
    …="http://www.fanmail.biz/model/a/1.html" shape="rect" coords="159, 2, 203, 11">

    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 88, Column 95: required attribute "ALT" not specified
    …://www.fanmail.biz/music_group/a/1.html" shape="rect" coords="288, 3, 373, 11">

    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 89, Column 82: required attribute "ALT" not specified
    …" shape="rect" coords="391, 2, 429, 9"></map><left><img border="0" src="http:/…

    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 89, Column 94: element "LEFT" undefined
    …t" coords="391, 2, 429, 9"></map><left><img border="0" src="http://www.fanmail…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 89, Column 207: required attribute "ALT" not specified
    …nmail.biz/images/m3.gif" usemap="#FPMap2" width="434" height="12" align="left">

    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 96, Column 75: there is no attribute "BORDERCOLOR"
    …llspacing="0" width="796" bordercolor="#FFFFFF" bordercolorlight="#CCCCCC" bor…

    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 96, Column 102: there is no attribute "BORDERCOLORLIGHT"
    …96" bordercolor="#FFFFFF" bordercolorlight="#CCCCCC" bordercolordark="#FFFFFF">

    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 96, Column 128: there is no attribute "BORDERCOLORDARK"
    …96" bordercolor="#FFFFFF" bordercolorlight="#CCCCCC" bordercolordark="#FFFFFF">

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

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

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

  • Warning Line 111, Column 110: NET-enabling start-tag requires SHORTTAG YES
    …e; left:30px; font-size:10pt;"><form action="http://www.fanmail.biz/search/" />

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

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

  • Error Line 112, Column 80: required attribute "ALT" not specified
    …images/new.gif" width="28" height="11"><br /><br /><input name="q" type="text"…

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

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

  • Warning Line 112, Column 85: NET-enabling start-tag requires SHORTTAG YES
    …s/new.gif" width="28" height="11"><br /><br /><input name="q" type="text" size…

    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 112, Column 91: NET-enabling start-tag requires SHORTTAG YES
    …gif" width="28" height="11"><br /><br /><input name="q" type="text" size="34" …

    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 112, Column 131: NET-enabling start-tag requires SHORTTAG YES
    …<input name="q" type="text" size="34" /><input type="submit" name="sa" value="…

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

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

  • Warning Line 112, Column 179: NET-enabling start-tag requires SHORTTAG YES
    …ype="submit" name="sa" value="Search" /></form></div><br /><br /><p style="mar…

    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 112, Column 198: NET-enabling start-tag requires SHORTTAG YES
    …sa" value="Search" /></form></div><br /><br /><p style="margin-left: 20"><br /…

    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 112, Column 204: NET-enabling start-tag requires SHORTTAG YES
    …lue="Search" /></form></div><br /><br /><p style="margin-left: 20"><br /><br /…

    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 112, Column 237: NET-enabling start-tag requires SHORTTAG YES
    …><br /><p style="margin-left: 20"><br /><br /><br />Last 10 feedbacks received…

    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 112, Column 243: NET-enabling start-tag requires SHORTTAG YES
    …><p style="margin-left: 20"><br /><br /><br />Last 10 feedbacks received (upda…

    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 112, Column 249: NET-enabling start-tag requires SHORTTAG YES
    …yle="margin-left: 20"><br /><br /><br />Last 10 feedbacks received (updated ev…

    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 112, Column 309: NET-enabling start-tag requires SHORTTAG YES
    …><br /><br />Last 10 feedbacks received (updated every 15 minutes):<br /><br />

    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 112, Column 315: NET-enabling start-tag requires SHORTTAG YES
    …><br /><br />Last 10 feedbacks received (updated every 15 minutes):<br /><br />

    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 113, Column 124: NET-enabling start-tag requires SHORTTAG YES
    …ic.php?t=286399" target="_blank">John Travolta Success</a> 2/24/13 8:14pm<br />

    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 116, Column 134: NET-enabling start-tag requires SHORTTAG YES
    …86389" target="_blank">Jerry Lawler In Person Success.</a> 2/24/13 6:21pm<br />

    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 119, Column 122: NET-enabling start-tag requires SHORTTAG YES
    …opic.php?t=286383" target="_blank">Betty White Success</a> 2/24/13 4:34pm<br />

    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 122, Column 121: NET-enabling start-tag requires SHORTTAG YES
    …topic.php?t=286382" target="_blank">Andre Reed Success</a> 2/24/13 4:11pm<br />

    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 125, Column 122: NET-enabling start-tag requires SHORTTAG YES
    …opic.php?t=286381" target="_blank">John Smiley Success</a> 2/24/13 4:09pm<br />

    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 128, Column 123: NET-enabling start-tag requires SHORTTAG YES
    …pic.php?t=286380" target="_blank">Kevin Tapani Success</a> 2/24/13 4:07pm<br />

    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 131, Column 123: NET-enabling start-tag requires SHORTTAG YES
    …pic.php?t=286379" target="_blank">Lonnie Smith Success</a> 2/24/13 4:05pm<br />

    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 134, Column 168: NET-enabling start-tag requires SHORTTAG YES
    …Player Paul &quot;biznasty&quot; Bissonnette Success!</a> 2/24/13 12:42pm<br />

    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 137, Column 124: NET-enabling start-tag requires SHORTTAG YES
    …ic.php?t=286367" target="_blank">Joan Rivers Success!</a> 2/24/13 12:29pm<br />

    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 140, Column 131: NET-enabling start-tag requires SHORTTAG YES
    …t=286359" target="_blank">Willow Shields Succes (thg)</a> 2/24/13 11:37am<br />

    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 142, Column 5: NET-enabling start-tag requires SHORTTAG YES
    <br /><br /><br />

    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 142, Column 11: NET-enabling start-tag requires SHORTTAG YES
    <br /><br /><br />

    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 142, Column 17: NET-enabling start-tag requires SHORTTAG YES
    <br /><br /><br />

    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 144, Column 8: document type does not allow element "CENTER" here; missing one of "TH", "TD" 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 145, Column 16: document type does not allow element "TD" here
    <td width="282">

    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 147, Column 250: end tag for "CENTER" omitted, but its declaration does not permit this
    …r-color: #C0C0C0" alt="Brad Pitt" hspace="15" vspace="0" align="left"></a></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 146, Column 1: start tag was here
    <center><a href="http://www.fanmail.biz/
  • Error Line 148, Column 5: end tag for "CENTER" omitted, but its declaration does not permit this
    </tr>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 144, Column 1: start tag was here
    <center>
  • Error Line 159, Column 41: required attribute "TYPE" not specified
    <center><script language="JavaScript1.2">

    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 179, Column 372: required attribute "ALT" not specified
    …http://www.fanmail.biz/images/new.gif"> &nbsp;|&nbsp; <a href="javascript:addb…

    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 179, Column 789: required attribute "ALT" not specified
    … align="middle" width="13" height="12"><br><br><br><a href="http://www.fanmail…

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

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

  • Info Line 179, Column 1: start tag was here
    <center><p style="font-size: 8pt"><a href="/">Home</a> &nbsp;|&nbsp; <a href="h…

Visitor Analysis

Daily Visitor
  • 1.400 visits