Watch the latest movies for free! No registration, no cash! Everything is completly free! ...

filmikz.ch
  • Domain Name
    filmikz.ch
  • Favicon
  • Google Page Rank
    1
  • Alexa Rank
    #46894
  • Page Size
    18.5 KB
  • Ip Address
    78.138.97.19
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 1, H5: 0, H6: 0
  • Images
    11 GIF, 15 JPG, 1 PNG

Website Meta Analysis

  • Title
    FilmIkz - Watch the lastest movies | Online movies | Free Movies | Watch movies
  • Meta Keyword
    filmikz,online movies,free movies, watch online movies, watch movies, watch films,online films,film streaming
  • Meta Description
    Watch the latest movies for free! No registration, no cash! Everything is completly free!

Technical Analysis

  • Webserver
    lighttpd/1.4.32
  • Ip Address
    78.138.97.19
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from filmikz.ch.

HTML Analysis

  • x-powered-by: PHP/5.3.3
  • content-type: text/html
  • date: Wed, 11 Sep 2013 10:53:26 GMT
  • server: lighttpd/1.4.32
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
whois: This information is subject to an Acceptable Use Policy.
See http://www.nic.ch/terms/aup.html


Domain name:
filmikz.ch

Holder of domain name:
Ioana Gheorghe
Calea Serban Voda, Nr. 232
RO-040207 Bucuresti
Romania
Contractual Language: German

Technical contact:
Ioana Gheorghe
Calea Serban Voda, Nr. 232
RO-040207 Bucuresti
Romania

DNSSEC:N

Name servers:
ns1.domaindiscount24.net
ns2.domaindiscount24.net
ns3.domaindiscount24.net

DNS Analysis


DNS servers
ns1.domaindiscount24.net [109.234.109.55]
ns3.domaindiscount24.net [193.46.215.55]
ns2.domaindiscount24.net [213.128.138.234]


DNS Records

Answer records
filmikz.ch SOA
server: ns1.domaindiscount24.net
email: tech@key-systems.net
serial: 2012050100
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 180
28800s
filmikz.ch A 91.121.13.38 28800s

Authority records

Additional records

IP 78.138.97.19 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 62 Errors
  • 12 Warnings
Ratio Text/Html
  • 0.6846617973959988
Message Error
  • Error Line 90, Column 111: required attribute "ALT" not specified
    …<img src="/images/filmikz_02.gif" width="813" height="138" border="0"></a></td>

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

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

  • Error Line 94, Column 83: required attribute "ALT" not specified
    …mage1" src="/images/asdadsa_01.gif" width="90" height="73" border="0"></a></td>

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

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

  • Error Line 95, Column 278: required attribute "ALT" not specified
    …gif" width="69" height="73" border="0"></a><a onMouseOver="document.image3.src…

    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 95, Column 509: required attribute "ALT" not specified
    …gif" width="73" height="73" border="0"></a><a onMouseOver="document.image4.src…

    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 95, Column 741: required attribute "ALT" not specified
    …gif" width="71" height="73" border="0"></a><a onMouseOver="document.image5.src…

    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 95, Column 973: required attribute "ALT" not specified
    …gif" width="87" height="73" border="0"></a><a onMouseOver="document.image6.src…

    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 95, Column 1204: required attribute "ALT" not specified
    …gif" width="87" height="73" border="0"></a><a onMouseOver="document.image7.src…

    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 95, Column 1435: required attribute "ALT" not specified
    …gif" width="70" height="73" border="0"></a><a onMouseOver="document.image8.src…

    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 95, Column 1667: required attribute "ALT" not specified
    …if" width="105" height="73" border="0"></a><a onMouseOver="document.image9.src…

    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 95, Column 1900: required attribute "ALT" not specified
    …if" width="107" height="73" border="0"></a><a onMouseOver="document.image10.sr…

    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 95, Column 2134: required attribute "ALT" not specified
    …ge10"  src="/images/asdadsa_10.gif" width="54" height="73" border="0"></a></td>

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

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

  • Error Line 99, Column 27: there is no attribute "HEIGHT"
    <table width="813" height="100%" border="0" align="center" cellpadding="0" cell…

    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 101, Column 89: required attribute "ALT" not specified
    …19" rowspan="2" valign="top" bgcolor="#FFFFFF"><img src="/images/tra.PNG"></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 105, Column 9: an attribute value must be a literal unless it contains only name characters
    <a href=/index.php style="color:black"><b>Last added</b></a> |

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

  • Error Line 106, Column 9: an attribute value must be a literal unless it contains only name characters
    <a href=/index.php?most=1 style="color:black"><b>Most wanted</b></a> |

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

  • Error Line 107, Column 9: an attribute value must be a literal unless it contains only name characters
    <a href=/index.php?genre=14 style="color:red"><b>XXX Movies</b></a> |

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

  • Error Line 108, Column 9: an attribute value must be a literal unless it contains only name characters
    <a href=/index.php?genre=15 style="color:black"><b>Tv Shows</b></a>

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

  • Error Line 113, Column 203: required attribute "ALT" not specified
    …pg' width='90' border='0' height='138'></a></td><td align='center' valign='top…

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

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

  • Error Line 113, Column 417: required attribute "ALT" not specified
    …pg' width='90' border='0' height='138'></a></td><td align='center' valign='top…

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

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

  • Error Line 113, Column 650: required attribute "ALT" not specified
    …pg' width='90' border='0' height='138'></a></td><td align='center' valign='top…

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

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

  • Error Line 113, Column 858: required attribute "ALT" not specified
    …pg' width='90' border='0' height='138'></a></td><td align='center' valign='top…

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

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

  • Error Line 113, Column 1073: required attribute "ALT" not specified
    …eb3a393f0fa05460.jpg' width='90' border='0' height='138'></a></td></tr></table>

    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 129, Column 250: NET-enabling start-tag requires SHORTTAG YES
    …c1acba291af95507654ae.jpg" width="87" height="126" border="0" /></a></div></td>

    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 129, Column 250: required attribute "ALT" not specified
    …c1acba291af95507654ae.jpg" width="87" height="126" border="0" /></a></div></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>.

  • Warning Line 159, Column 235: NET-enabling start-tag requires SHORTTAG YES
    …ba8be353f9a0066b9d90c.jpg" width="87" height="126" border="0" /></a></div></td>

    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 159, Column 235: required attribute "ALT" not specified
    …ba8be353f9a0066b9d90c.jpg" width="87" height="126" border="0" /></a></div></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 162, Column 217: non SGML character number 133
    …ungle that hides an unexplored lost world populated with hungry dinosaurs… </p>

    You have used an illegal character in your text. HTML uses the standard UNICODE Consortium character repertoire, and it leaves undefined (among others) 65 character codes (0 to 31 inclusive and 127 to 159 inclusive) that are sometimes used for typographical quote marks and similar in proprietary character sets. The validator has found one of these undefined characters in your document. The character may appear on your browser as a curly quote, or a trademark symbol, or some other fancy glyph; on a different computer, however, it will likely appear as a completely different character, or nothing at all.

    Your best bet is to replace the character with the nearest equivalent ASCII character, or to use an appropriate character entity. For more information on Character Encoding on the web, see Alan Flavell's excellent HTML Character Set Issues reference.

    This error can also be triggered by formatting characters embedded in documents by some word processors. If you use a word processor to edit your HTML documents, be sure to use the "Save as ASCII" or similar command to save the document without formatting information.

  • Warning Line 189, Column 222: NET-enabling start-tag requires SHORTTAG YES
    …sters/110941360240532.jpg" width="87" height="126" border="0" /></a></div></td>

    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 189, Column 222: required attribute "ALT" not specified
    …sters/110941360240532.jpg" width="87" height="126" border="0" /></a></div></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>.

  • Warning Line 219, Column 209: NET-enabling start-tag requires SHORTTAG YES
    …osters/63751360237810.jpg" width="87" height="126" border="0" /></a></div></td>

    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 219, Column 209: required attribute "ALT" not specified
    …osters/63751360237810.jpg" width="87" height="126" border="0" /></a></div></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>.

  • Warning Line 249, Column 229: NET-enabling start-tag requires SHORTTAG YES
    …a2adaec21686827529fd0.jpg" width="87" height="126" border="0" /></a></div></td>

    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 249, Column 229: required attribute "ALT" not specified
    …a2adaec21686827529fd0.jpg" width="87" height="126" border="0" /></a></div></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>.

  • Warning Line 279, Column 221: NET-enabling start-tag requires SHORTTAG YES
    …sters/104281360233619.jpg" width="87" height="126" border="0" /></a></div></td>

    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 279, Column 221: required attribute "ALT" not specified
    …sters/104281360233619.jpg" width="87" height="126" border="0" /></a></div></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>.

  • Warning Line 309, Column 231: NET-enabling start-tag requires SHORTTAG YES
    …09e88146ac231b099f219.jpg" width="87" height="126" border="0" /></a></div></td>

    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 309, Column 231: required attribute "ALT" not specified
    …09e88146ac231b099f219.jpg" width="87" height="126" border="0" /></a></div></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>.

  • Warning Line 339, Column 233: NET-enabling start-tag requires SHORTTAG YES
    …e4aab51310e90ca7e4a73.jpg" width="87" height="126" border="0" /></a></div></td>

    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 339, Column 233: required attribute "ALT" not specified
    …e4aab51310e90ca7e4a73.jpg" width="87" height="126" border="0" /></a></div></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>.

  • Warning Line 369, Column 237: NET-enabling start-tag requires SHORTTAG YES
    …104f73da1e3337328b7b5.jpg" width="87" height="126" border="0" /></a></div></td>

    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 369, Column 237: required attribute "ALT" not specified
    …104f73da1e3337328b7b5.jpg" width="87" height="126" border="0" /></a></div></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>.

  • Warning Line 399, Column 246: NET-enabling start-tag requires SHORTTAG YES
    …68809d5b4411bc50736ea.jpg" width="87" height="126" border="0" /></a></div></td>

    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 399, Column 246: required attribute "ALT" not specified
    …68809d5b4411bc50736ea.jpg" width="87" height="126" border="0" /></a></div></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>.

  • Warning Line 431, Column 51: cannot generate system identifier for general entity "genre"
    …='color:red;' href='index.php?search=&genre=&pg=0'> First </a></td><td>1</td><…

    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 431, Column 51: general entity "genre" not defined and no default entity
    …='color:red;' href='index.php?search=&genre=&pg=0'> First </a></td><td>1</td><…

    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 431, Column 56: reference to entity "genre" for which no system identifier could be generated
    …or:red;' href='index.php?search=&genre=&pg=0'> First </a></td><td>1</td><td><a…

    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 431, Column 50: entity was defined here
    …e='color:red;' href='index.php?search=&genre=&pg=0'> First </a></td><td>1</td>…
  • Warning Line 431, Column 58: cannot generate system identifier for general entity "pg"
    …:red;' href='index.php?search=&genre=&pg=0'> First </a></td><td>1</td><td><a s…

    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 431, Column 58: general entity "pg" not defined and no default entity
    …:red;' href='index.php?search=&genre=&pg=0'> First </a></td><td>1</td><td><a s…

    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 431, Column 60: reference to entity "pg" for which no system identifier could be generated
    …ed;' href='index.php?search=&genre=&pg=0'> First </a></td><td>1</td><td><a sty…

    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 431, Column 57: entity was defined here
    …r:red;' href='index.php?search=&genre=&pg=0'> First </a></td><td>1</td><td><a …
  • Error Line 431, Column 145: reference to entity "genre" for which no system identifier could be generated
    …or:red;' href='index.php?search=&genre=&pg=10'> 2 </a></td><td><a style='color…

    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 431, Column 50: entity was defined here
    …e='color:red;' href='index.php?search=&genre=&pg=0'> First </a></td><td>1</td>…
  • Error Line 431, Column 149: reference to entity "pg" for which no system identifier could be generated
    …ed;' href='index.php?search=&genre=&pg=10'> 2 </a></td><td><a style='color:red…

    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 431, Column 57: entity was defined here
    …r:red;' href='index.php?search=&genre=&pg=0'> First </a></td><td>1</td><td><a …
  • Error Line 431, Column 221: reference to entity "genre" for which no system identifier could be generated
    …or:red;' href='index.php?search=&genre=&pg=20'> 3 </a></td><td><a style='color…

    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 431, Column 50: entity was defined here
    …e='color:red;' href='index.php?search=&genre=&pg=0'> First </a></td><td>1</td>…
  • Error Line 431, Column 225: reference to entity "pg" for which no system identifier could be generated
    …ed;' href='index.php?search=&genre=&pg=20'> 3 </a></td><td><a style='color:red…

    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 431, Column 57: entity was defined here
    …r:red;' href='index.php?search=&genre=&pg=0'> First </a></td><td>1</td><td><a …
  • Error Line 431, Column 297: reference to entity "genre" for which no system identifier could be generated
    …or:red;' href='index.php?search=&genre=&pg=30'> 4 </a></td><td><a style='color…

    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 431, Column 50: entity was defined here
    …e='color:red;' href='index.php?search=&genre=&pg=0'> First </a></td><td>1</td>…
  • Error Line 431, Column 301: reference to entity "pg" for which no system identifier could be generated
    …ed;' href='index.php?search=&genre=&pg=30'> 4 </a></td><td><a style='color:red…

    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 431, Column 57: entity was defined here
    …r:red;' href='index.php?search=&genre=&pg=0'> First </a></td><td>1</td><td><a …
  • Error Line 431, Column 373: reference to entity "genre" for which no system identifier could be generated
    …or:red;' href='index.php?search=&genre=&pg=40'> 5 </a></td><td><a style='color…

    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 431, Column 50: entity was defined here
    …e='color:red;' href='index.php?search=&genre=&pg=0'> First </a></td><td>1</td>…
  • Error Line 431, Column 377: reference to entity "pg" for which no system identifier could be generated
    …ed;' href='index.php?search=&genre=&pg=40'> 5 </a></td><td><a style='color:red…

    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 431, Column 57: entity was defined here
    …r:red;' href='index.php?search=&genre=&pg=0'> First </a></td><td>1</td><td><a …
  • Error Line 431, Column 449: reference to entity "genre" for which no system identifier could be generated
    …or:red;' href='index.php?search=&genre=&pg=50'> 6 </a></td><td><a style='color…

    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 431, Column 50: entity was defined here
    …e='color:red;' href='index.php?search=&genre=&pg=0'> First </a></td><td>1</td>…
  • Error Line 431, Column 453: reference to entity "pg" for which no system identifier could be generated
    …ed;' href='index.php?search=&genre=&pg=50'> 6 </a></td><td><a style='color:red…

    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 431, Column 57: entity was defined here
    …r:red;' href='index.php?search=&genre=&pg=0'> First </a></td><td>1</td><td><a …
  • Error Line 431, Column 525: reference to entity "genre" for which no system identifier could be generated
    …or:red;' href='index.php?search=&genre=&pg=60'> 7 </a></td><td><a style='color…

    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 431, Column 50: entity was defined here
    …e='color:red;' href='index.php?search=&genre=&pg=0'> First </a></td><td>1</td>…
  • Error Line 431, Column 529: reference to entity "pg" for which no system identifier could be generated
    …ed;' href='index.php?search=&genre=&pg=60'> 7 </a></td><td><a style='color:red…

    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 431, Column 57: entity was defined here
    …r:red;' href='index.php?search=&genre=&pg=0'> First </a></td><td>1</td><td><a …
  • Error Line 431, Column 601: reference to entity "genre" for which no system identifier could be generated
    …or:red;' href='index.php?search=&genre=&pg=70'> 8 </a></td><td><a style='color…

    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 431, Column 50: entity was defined here
    …e='color:red;' href='index.php?search=&genre=&pg=0'> First </a></td><td>1</td>…
  • Error Line 431, Column 605: reference to entity "pg" for which no system identifier could be generated
    …ed;' href='index.php?search=&genre=&pg=70'> 8 </a></td><td><a style='color:red…

    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 431, Column 57: entity was defined here
    …r:red;' href='index.php?search=&genre=&pg=0'> First </a></td><td>1</td><td><a …
  • Error Line 431, Column 677: reference to entity "genre" for which no system identifier could be generated
    …or:red;' href='index.php?search=&genre=&pg=80'> 9 </a></td><td><a style='color…

    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 431, Column 50: entity was defined here
    …e='color:red;' href='index.php?search=&genre=&pg=0'> First </a></td><td>1</td>…
  • Error Line 431, Column 681: reference to entity "pg" for which no system identifier could be generated
    …ed;' href='index.php?search=&genre=&pg=80'> 9 </a></td><td><a style='color:red…

    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 431, Column 57: entity was defined here
    …r:red;' href='index.php?search=&genre=&pg=0'> First </a></td><td>1</td><td><a …
  • Error Line 431, Column 753: reference to entity "genre" for which no system identifier could be generated
    …or:red;' href='index.php?search=&genre=&pg=90'> 10 </a></td><td><a style='colo…

    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 431, Column 50: entity was defined here
    …e='color:red;' href='index.php?search=&genre=&pg=0'> First </a></td><td>1</td>…
  • Error Line 431, Column 757: reference to entity "pg" for which no system identifier could be generated
    …ed;' href='index.php?search=&genre=&pg=90'> 10 </a></td><td><a style='color:re…

    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 431, Column 57: entity was defined here
    …r:red;' href='index.php?search=&genre=&pg=0'> First </a></td><td>1</td><td><a …
  • Error Line 431, Column 830: reference to entity "genre" for which no system identifier could be generated
    …or:red;' href='index.php?search=&genre=&pg=10'>&rsaquo;&rsaquo;</a></td><td><a…

    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 431, Column 50: entity was defined here
    …e='color:red;' href='index.php?search=&genre=&pg=0'> First </a></td><td>1</td>…
  • Error Line 431, Column 834: reference to entity "pg" for which no system identifier could be generated
    …ed;' href='index.php?search=&genre=&pg=10'>&rsaquo;&rsaquo;</a></td><td><a sty…

    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 431, Column 57: entity was defined here
    …r:red;' href='index.php?search=&genre=&pg=0'> First </a></td><td>1</td><td><a …
  • Error Line 431, Column 919: reference to entity "genre" for which no system identifier could be generated
    …le='color:red;' href='index.php?search=&genre=&pg=14206'> Last </a></td>  </tr>

    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 431, Column 50: entity was defined here
    …e='color:red;' href='index.php?search=&genre=&pg=0'> First </a></td><td>1</td>…
  • Error Line 431, Column 923: reference to entity "pg" for which no system identifier could be generated
    …le='color:red;' href='index.php?search=&genre=&pg=14206'> Last </a></td>  </tr>

    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 431, Column 57: entity was defined here
    …r:red;' href='index.php?search=&genre=&pg=0'> First </a></td><td>1</td><td><a …
  • Error Line 434, Column 49: there is no attribute "BACKGROUND"
    …td width="255" height="30" background="/images/grad.png" valign="top"><form ac…

    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 440, Column 22: there is no attribute "BORDER"
                  BORDER="0">

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

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

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

  • Error Line 445, Column 8: document type does not allow element "CENTER" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <center><b><a href=/movies.php>Movies List</a><br></b></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 445, Column 20: an attribute value must be a literal unless it contains only name characters
    <center><b><a href=/movies.php>Movies List</a><br></b></center>

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

Visitor Analysis

Daily Visitor
  • 9.450 visits