*Forums* Welcome To Findadeath! Follow us to be notified of updates and other fun stuff! Exciting Announcement! On Halloween 2013 - the E! Channel will show a 1 hour special about the ...

findadeath.com
  • Domain Name
    findadeath.com
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #63685
  • Page Size
    16.5 KB
  • Ip Address
    174.122.113.123
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    5 GIF, 17 JPG, 0 PNG

Website Meta Analysis

  • Title
    Findadeath - Celebrity Deaths
  • Meta Keyword
    keyword=death,celeb,john,phillips,deadelvis,elvi,elvis,deaners,dean,dea,suicide,kill,end,judy,Dean,dean,find,a ,death,grave,DOA
  • Meta Description
      *Forums* Welcome To Findadeath! Follow us to be notified of updates and other fun stuff! Exciting Announcement! On Halloween 2013 - the E! Channel will show a 1 hour special about the Deaths in Hollywood hosted by myself and modern scream-queen ...

Technical Analysis

  • Webserver
    Apache/2.2.16 (Unix) mod_ssl/2.2.16 OpenSSL/0.9.8e-fips-rhel5 DAV/2 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
  • Ip Address
    174.122.113.123
  • Domain Age
    14 Years, 11 Months, 15 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Tue, 10 Sep 2013 03:12:34 GMT
  • server: Apache/2.2.16 (Unix) mod_ssl/2.2.16 OpenSSL/0.9.8e-fips-rhel5 DAV/2 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
  • last-modified: Sat, 07 Sep 2013 14:14:12 GMT
  • etag: "1b60019-41b5-4e5cbc4ef9500"
  • accept-ranges: bytes
  • content-length: 16821
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
www.findadeath.com
5419 Hollywood Boulevard
#404
Hollywood, California 90027
United States

Domain Name: FINDADEATH.COM
Created on: 12-Oct-98
Expires on: 11-Oct-12
Last Updated on: 25-Aug-11

Administrative Contact:
Michaels, Scott email
www.findadeath.com
5419 Hollywood Boulevard
#404
Hollywood, California 90027
United States
+1.3234663696

Technical Contact:
Michaels, Scott email
www.findadeath.com
5419 Hollywood Boulevard
#404
Hollywood, California 90027
United States
+1.3234663696

Domain servers in listed order:
NS1.THE-NEXTLEVEL.COM
NS2.THE-NEXTLEVEL.COM

DNS Analysis


DNS servers
ns1.the-nextlevel.com [174.122.113.122]
ns2.the-nextlevel.com [174.122.113.123]


DNS Records

Answer records
findadeath.com TXT v=spf1 +a +mx +ip4:174.122.113.122 ?all 300s
findadeath.com MX
preference: 0
exchange: findadeath.com
300s
findadeath.com SOA
server: ns1.the-nextlevel.com
email: nvlamakis@comcast.net
serial: 2012083002
refresh: 300
retry: 7200
expire: 3600000
minimum ttl: 3600
14440s
findadeath.com NS  ns1.the-nextlevel.com 86400s
findadeath.com NS  ns2.the-nextlevel.com 86400s
findadeath.com A 174.122.113.123 300s

Authority records

Additional records
findadeath.com A 174.122.113.123 300s
ns1.the-nextlevel.com A 174.122.113.122 300s

IP 174.122.113.123 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Houston
  • Continent Code
    77002
  • Latitude
    713
  • Longitude
    618
  • %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-THEPLANET-BLK-16
    network:Auth-Area:174.120.0.0/14
    network:Network-Name:TPIS-BLK-174-122-113-0
    network:IP-Network:174.122.113.120/29
    network:IP-Network-Block:174.122.113.120 - 174.122.113.127
    network:Organization;I:The Next Level
    network:Street-Address:N/A
    network:City:Chicago
    network:State:IL
    network:Postal-Code:60603
    network:Country-Code:USA
    network:Tech-Contact;I:abuse@theplanet.com
    network:Admin-Contact;I:abuse@theplanet.com
    network:Created:20100917
    network:Updated:20100917

    network:Class-Name:network
    network:ID:NETBLK-SOFTLAYER.174.120.0.0/14
    network:Auth-Area:174.120.0.0/14
    network:Network-Name:SOFTLAYER-174.120.0.0
    network:IP-Network:174.122.64.0/18
    network:IP-Network-Block:174.122.64.0-174.122.127.255
    network:Organization;I:SoftLayer
    network:Street-Address:4849 Alpha Road
    network:City:Dallas
    network:State:TX
    network:Postal-Code:75244
    network:Country-Code:US
    network:Tech-Contact;I:sysadmins@softlayer.com
    network:Abuse-Contact;I:abuse@softlayer.com
    network:Admin-Contact;I:IPADM258-ARIN
    network:Created:2013-01-09 09:58:35
    network:Updated:2013-01-09 09:58:35
    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
  • 61 Errors
  • 11 Warnings
Ratio Text/Html
  • 0.6044073218411232
Message Error
  • Error Line 1, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
    <html><head><title>Findadeath - Celebrity Deaths</title>

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

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

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

  • Warning Line 121, Column 108: NET-enabling start-tag requires SHORTTAG YES
    …om/pixel/p-90bzYojLh70Xc.gif" border="0" height="1" width="1" alt="Quantcast"/>

    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 187, Column 7: end tag for element "HEAD" which is not open
    </head><body background="Fad_pictures/translog5_1.jpg">

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

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

  • Error Line 187, Column 55: document type does not allow element "BODY" here
    </head><body background="Fad_pictures/translog5_1.jpg">

    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 191, Column 259: required attribute "ALT" not specified
    …mg border="0" src="/Fad_pictures/ddtouranim.gif" width="147" height="70"><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>.

  • Warning Line 191, Column 264: NET-enabling start-tag requires SHORTTAG YES
    …mg border="0" src="/Fad_pictures/ddtouranim.gif" width="147" height="70"><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 195, Column 51: required attribute "ALT" not specified
    <area href="/" shape="rect" coords="26, 1, 90, 18">

    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 197, Column 66: required attribute "ALT" not specified
    <area href="/directory.htm" shape="rect" coords="14, 23, 101, 44">

    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 199, Column 59: required attribute "ALT" not specified
    <area href="/new.htm" shape="rect" coords="24, 47, 95, 67">

    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 201, Column 80: required attribute "ALT" not specified
    <area href="/AboutUs.htm" shape="rect" coords="12, 71, 108, 91" target="_blank">

    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 203, Column 72: required attribute "ALT" not specified
    <area href="/fadstore/store.html" shape="rect" coords="29, 93, 86, 116">

    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 205, Column 63: required attribute "ALT" not specified
    <area href="/LINKS.htm" shape="rect" coords="27, 120, 83, 140">

    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 207, Column 70: required attribute "ALT" not specified
    <area href="/emailnotice.htm" shape="rect" coords="19, 143, 101, 163">

    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 209, Column 69: required attribute "ALT" not specified
    <area href="/mailinglist.htm" shape="rect" coords="1, 166, 113, 187">

    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 211, Column 72: required attribute "ALT" not specified
    <area href="/PressandQuotes.htm" shape="rect" coords="6, 191, 107, 211">

    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 213, Column 65: required attribute "ALT" not specified
    <area href="/search.htm" shape="rect" coords="19, 214, 100, 235">

    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 215, Column 82: required attribute "ALT" not specified
    …shape="rect" coords="3, 238, 104, 255"></map><img border="0" src="/Fad_picture…

    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 215, Column 181: required attribute "ALT" not specified
    …"/Fad_pictures/fadimgmap4.jpg" usemap="#FPMap0" width="115" height="256"><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>.

  • Warning Line 215, Column 186: NET-enabling start-tag requires SHORTTAG YES
    …"/Fad_pictures/fadimgmap4.jpg" usemap="#FPMap0" width="115" height="256"><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 221, Column 172: NET-enabling start-tag requires SHORTTAG YES
    …r="0" marginwidth="0" marginheight="0" width="160" height="147" /></iframe></p>

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

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

  • Error Line 229, Column 319: required attribute "ALT" not specified
    …s/fad-ba3.jpg" width="120" height="73"><br /><a href="http://www.celebritycoll…

    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 229, Column 324: NET-enabling start-tag requires SHORTTAG YES
    …-ba3.jpg" width="120" height="73"><br /><a href="http://www.celebritycollectab…

    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 229, Column 458: required attribute "ALT" not specified
    …ogo_type.jpg" width="150" height="113"></a></p></td><td bgcolor="#000000" alig…

    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 229, Column 583: required attribute "ALT" not specified
    …s/fadban5.jpg" width="576" height="57"><br /><strong><cite><font color="#FF000…

    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 229, Column 588: NET-enabling start-tag requires SHORTTAG YES
    …ban5.jpg" width="576" height="57"><br /><strong><cite><font color="#FF0000">We…

    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 229, Column 907: end tag for element "P" which is not open
    …display('div-gpt-ad-1330413499729-0'); });</script></div></p></td></tr><tr><td>

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

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

  • Error Line 245, Column 136: "ALLOWFULLSCREEN" is not a member of a group specified for any attribute
    …://www.youtube.com/embed/mXo9ajoibV4" frameborder="0" allowfullscreen></iframe>
  • Error Line 261, Column 117: "WEBKITALLOWFULLSCREEN" is not a member of a group specified for any attribute
    …frameborder="0" webkitAllowFullScreen mozallowfullscreen allowFullScreen></ifr…
  • Error Line 261, Column 136: "MOZALLOWFULLSCREEN" is not a member of a group specified for any attribute
    …eborder="0" webkitAllowFullScreen mozallowfullscreen allowFullScreen></iframe> 
  • Error Line 261, Column 151: "ALLOWFULLSCREEN" is not a member of a group specified for any attribute
    …eborder="0" webkitAllowFullScreen mozallowfullscreen allowFullScreen></iframe> 
  • Error Line 269, Column 176: required attribute "ALT" not specified
    …y_Coleman/gary-coleman-christmas.jpg" width="400" height="303"></a>&nbsp;&nbsp;

    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 271, Column 115: required attribute "ALT" not specified
    …scott.htm"><img border="0" src="debralee.jpg" width="412" height="302"></a></p>

    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 281, Column 130: required attribute "ALT" not specified
    …wain_Lee.htm"><img border="0" src="thumb.jpg" width="300" height="190"></a></p>

    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 299, Column 136: "ALLOWFULLSCREEN" is not a member of a group specified for any attribute
    …ww.youtube.com/embed/PcMSyuvCRNE" frameborder="0" allowfullscreen></iframe></p>
  • Error Line 307, Column 173: required attribute "ALT" not specified
    …ased/r/Zelda_Rubinstein/zelda_rubinstein.jpg" width="450" height="300"></a></p>

    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 323, Column 149: "WEBKITALLOWFULLSCREEN" is not a member of a group specified for any attribute
    …frameborder="0" webkitAllowFullScreen mozallowfullscreen allowFullScreen></ifr…
  • Error Line 323, Column 168: "MOZALLOWFULLSCREEN" is not a member of a group specified for any attribute
    …kitAllowFullScreen mozallowfullscreen allowFullScreen></iframe> <p align="cent…
  • Error Line 323, Column 183: "ALLOWFULLSCREEN" is not a member of a group specified for any attribute
    …wFullScreen mozallowfullscreen allowFullScreen></iframe> <p align="center"></p>
  • Error Line 485, Column 150: required attribute "ALT" not specified
    …pictures/facebookIcon.JPG" width="180" height="68"></a>&nbsp;&nbsp;&nbsp;&nbsp;

    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 489, Column 130: required attribute "ALT" not specified
    …border="0" src="Fad_pictures/twitter-icon.jpg" width="198" height="68"></a></p>

    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 621, Column 261: required attribute "ALT" not specified
    …r="0" src="HS%20-%20Animated%20Banner%205.gif" width="720" height="90"></a></p>

    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 705, Column 131: required attribute "ALT" not specified
    …e.htm"><img border="0" src="jeep%20plate%20thumb.JPG" width="295" height="197">

    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 765, Column 166: required attribute "ALT" not specified
    …r%20icon.JPG" width="255" height="230"></a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp…

    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 845, Column 122: cannot generate system identifier for general entity "hl"
    …"http://www.youtube.com/v/3IZurMszUhQ&hl=en"></param><param name="wmode" value…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 845, Column 122: general entity "hl" not defined and no default entity
    …"http://www.youtube.com/v/3IZurMszUhQ&hl=en"></param><param name="wmode" value…

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

  • Error Line 845, Column 124: reference to entity "hl" for which no system identifier could be generated
    …ttp://www.youtube.com/v/3IZurMszUhQ&hl=en"></param><param name="wmode" value="…

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

  • Info Line 845, Column 121: entity was defined here
    …="http://www.youtube.com/v/3IZurMszUhQ&hl=en"></param><param name="wmode" valu…
  • Error Line 845, Column 136: end tag for element "PARAM" which is not open
    …utube.com/v/3IZurMszUhQ&hl=en"></param><param name="wmode" value="transparent"…

    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 845, Column 184: end tag for element "PARAM" which is not open
    …m/v/3IZurMszUhQ&hl=en"></param><param name="wmode" value="transparent"></param>

    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 849, Column 14: there is no attribute "SRC"
      <embed src="http://www.youtube.com/v/3IZurMszUhQ&hl=en" type="application/x-s…

    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 849, Column 54: reference to entity "hl" for which no system identifier could be generated
    …ttp://www.youtube.com/v/3IZurMszUhQ&hl=en" type="application/x-shockwave-flash…

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

  • Info Line 845, Column 121: entity was defined here
    …="http://www.youtube.com/v/3IZurMszUhQ&hl=en"></param><param name="wmode" valu…
  • Error Line 849, Column 64: there is no attribute "TYPE"
    …youtube.com/v/3IZurMszUhQ&hl=en" type="application/x-shockwave-flash" wmode="t…

    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 849, Column 102: there is no attribute "WMODE"
    …"application/x-shockwave-flash" wmode="transparent" width="425" height="355"><…

    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 849, Column 122: there is no attribute "WIDTH"
    …shockwave-flash" wmode="transparent" width="425" height="355"></embed></object>

    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 849, Column 135: there is no attribute "HEIGHT"
    …shockwave-flash" wmode="transparent" width="425" height="355"></embed></object>

    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 849, Column 140: element "EMBED" undefined
    …shockwave-flash" wmode="transparent" width="425" height="355"></embed></object>

    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 917, Column 144: required attribute "ALT" not specified
    …="_blank"><img border="0" src="Spamarrest.gif" width="728" height="90"></a></p>

    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 1033, Column 67: required attribute "ALT" not specified
    …g border="0" src="fadstore/sticker.jpg" width="438" height="78"></font></a></p>

    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 1269, Column 72: required attribute "ALT" not specified
    …g%20-%201.gif" width="728" height="90"></a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp…

    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>.

Visitor Analysis

Daily Visitor
  • 2.917 visits