dpstream.net has Alexa Rank 1.890 and Google Page Rank is 3

dpstream.net
  • Domain Name
    dpstream.net
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #1890
  • Page Size
    810 B
  • Ip Address
    78.140.178.5
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
  • Meta Keyword
  • Meta Description

Technical Analysis

  • Webserver
    nginx
  • Ip Address
    78.140.178.5
  • Domain Age
    3 Years, 9 Months, 21 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from dpstream.net.

HTML Analysis

  • content-type: text/html; charset=UTF-8
  • cache-control: no-cache, no-store, must-revalidate, max-age=0
  • expires: Thu, 01 Jan 1970 00:00:00 GMT
  • connection: close
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain dpstream.net

Date Registered: 2009-8-28
Date Modified: 2012-8-14
Expiry Date: 2013-8-28

DNS1: ns-canada.topdns.com
DNS2: ns-uk.topdns.com
DNS3: ns-usa.topdns.com

Registrant
Fundacion Private Whois
Domain Administrator
Email: email
Attn: dpstream.net
Aptds. 0850-00056
Zona 15 Panama
Panama
Tel: +507.65995877

Administrative Contact
Fundacion Private Whois
Domain Administrator
Email: email
Attn: dpstream.net
Aptds. 0850-00056
Zona 15 Panama
Panama
Tel: +507.65995877

Technical Contact
Fundacion Private Whois
Domain Administrator
Email: email
Attn: dpstream.net
Aptds. 0850-00056
Zona 15 Panama
Panama
Tel: +507.65995877

DNS Analysis


DNS servers
ns-uk.topdns.com [31.192.106.198]
ns-usa.topdns.com [108.61.12.163]
ns-canada.topdns.com [109.201.142.225]

DNS Records

Answer records
dpstream.net SOA
server: ns-usa.topdns.com
email: hostmaster@topdns.com
serial: 2012112101
refresh: 172800
retry: 900
expire: 1209600
minimum ttl: 3600
7200s
dpstream.net NS  ns-usa.topdns.com 3600s
dpstream.net NS  ns-uk.topdns.com 3600s
dpstream.net NS  ns-canada.topdns.com 3600s
dpstream.net A 72.8.132.27 900s

Authority records

Additional records

IP 78.140.178.5 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 6 Errors
  • 3 Warnings
Ratio Text/Html
  • 0.5148148148148148
Message Error
  • Error Line 5, Column 14: there is no attribute "NAME"
    		<META NAME="keywords" content="streaming,film,films,serie,series,manga,mangas…

    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 5, Column 33: there is no attribute "content"
    		<META NAME="keywords" content="streaming,film,films,serie,series,manga,mangas…

    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 5, Column 120: element "META" undefined
    …,film,films,serie,series,manga,mangas,regarder,gratuit,dpstream,stream,video">	

    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 6, Column 39: there is no attribute "CONTENT"
    		<META NAME="Identifier-URL" CONTENT="http://www.dpstream.net/">

    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 6, Column 65: element "META" undefined
    		<META NAME="Identifier-URL" CONTENT="http://www.dpstream.net/">

    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 7, Column 167: element "META" undefined
    …g , film en streaming , films streaming , film divx , regarder film streaming">

    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 8, Column 60: element "META" undefined
    		<META NAME="SUBJECT" CONTENT="film en streaming gratuits">

    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 10, Column 82: end tag for "link" omitted, but OMITTAG NO was specified
    …ef="/fichiers/css/styleprod11.css?v2">		<link rel="shortcut icon" href="/fichi…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 10, Column 3: start tag was here
    		<link rel="stylesheet" type="text/css" href="/fichiers/css/styleprod11.css?v2…
  • Error Line 10, Column 146: end tag for "link" omitted, but OMITTAG NO was specified
    …prod11.css?v2">		<link rel="shortcut icon" href="/fichiers/images/favicon.ico">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 10, Column 84: start tag was here
    …="/fichiers/css/styleprod11.css?v2">		<link rel="shortcut icon" href="/fichier…
  • Error Line 21, Column 10: end tag for "META" omitted, but OMITTAG NO was specified
    			</head>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 8, Column 3: start tag was here
    		<META NAME="SUBJECT" CONTENT="film en streaming gratuits">
  • Error Line 21, Column 10: end tag for "META" omitted, but OMITTAG NO was specified
    			</head>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 7, Column 3: start tag was here
    		<META NAME="DESCRIPTION" CONTENT=" film streaming , streaming film , films en…
  • Error Line 21, Column 10: end tag for "META" omitted, but OMITTAG NO was specified
    			</head>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 6, Column 3: start tag was here
    		<META NAME="Identifier-URL" CONTENT="http://www.dpstream.net/">
  • Error Line 21, Column 10: end tag for "META" omitted, but OMITTAG NO was specified
    			</head>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 5, Column 3: start tag was here
    		<META NAME="keywords" content="streaming,film,films,serie,series,manga,mangas…
  • Error Line 21, Column 10: end tag for "head" which is not finished
    			</head>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 35, Column 96: there is no attribute "border"
    …582" height="72" frameborder="0" border="0" scrolling="no"></iframe>					</td>	

    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 46, Column 64: end tag for "input" omitted, but OMITTAG NO was specified
    								<input type="text" size="30" name="recherche" value="">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 46, Column 9: start tag was here
    								<input type="text" size="30" name="recherche" value="">
  • Error Line 47, Column 49: end tag for "input" omitted, but OMITTAG NO was specified
    								<input type="submit" value="Rechercher">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 47, Column 9: start tag was here
    								<input type="submit" value="Rechercher">
  • Error Line 58, Column 47: value of attribute "method" cannot be "POST"; must be one of "get", "post"
    								<form action="serie.html" method="POST">

    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 59, Column 67: end tag for "input" omitted, but OMITTAG NO was specified
    									<input type="text" size="30" name="recherchem"  value="">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 59, Column 10: start tag was here
    									<input type="text" size="30" name="recherchem"  value="">
  • Error Line 60, Column 50: end tag for "input" omitted, but OMITTAG NO was specified
    									<input type="submit" value="Rechercher">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 60, Column 10: start tag was here
    									<input type="submit" value="Rechercher">
  • Error Line 71, Column 47: value of attribute "method" cannot be "POST"; must be one of "get", "post"
    								<form action="manga.html" method="POST">

    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 72, Column 66: end tag for "input" omitted, but OMITTAG NO was specified
    									<input type="text" size="30" name="recherchem" value="">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 72, Column 10: start tag was here
    									<input type="text" size="30" name="recherchem" value="">
  • Error Line 73, Column 50: end tag for "input" omitted, but OMITTAG NO was specified
    									<input type="submit" value="Rechercher">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 73, Column 10: start tag was here
    									<input type="submit" value="Rechercher">
  • Error Line 82, Column 47: there is no attribute "bgcolor"
    …me name="okk" src="black.php" bgcolor="#121212" width="0" height="0" align="to…

    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 82, Column 96: duplicate specification of attribute "align"
    …idth="0" height="0" align="top" align="left" frameborder="0" border="0" scroll…

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 113, Column 9: document type does not allow element "title" here
    		<title>Films Series Mangas en streaming - DpStream</title>

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

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

  • Warning Line 126, Column 62: cannot generate system identifier for general entity "t"
    ….dpstream.net/forum/viewtopic.php?f=1&t=9962&sid=ace5be6ab026960b89e3e0c783ff7…

    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 126, Column 62: general entity "t" not defined and no default entity
    ….dpstream.net/forum/viewtopic.php?f=1&t=9962&sid=ace5be6ab026960b89e3e0c783ff7…

    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.

  • Warning Line 126, Column 63: reference not terminated by REFC delimiter
    …dpstream.net/forum/viewtopic.php?f=1&t=9962&sid=ace5be6ab026960b89e3e0c783ff75…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 126, Column 63: reference to external entity in attribute value
    …dpstream.net/forum/viewtopic.php?f=1&t=9962&sid=ace5be6ab026960b89e3e0c783ff75…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 126, Column 63: reference to entity "t" for which no system identifier could be generated
    …dpstream.net/forum/viewtopic.php?f=1&t=9962&sid=ace5be6ab026960b89e3e0c783ff75…

    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 126, Column 61: entity was defined here
    …r.dpstream.net/forum/viewtopic.php?f=1&t=9962&sid=ace5be6ab026960b89e3e0c783ff…
  • Warning Line 126, Column 69: cannot generate system identifier for general entity "sid"
    …am.net/forum/viewtopic.php?f=1&t=9962&sid=ace5be6ab026960b89e3e0c783ff7577" ta…

    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 126, Column 69: general entity "sid" not defined and no default entity
    …am.net/forum/viewtopic.php?f=1&t=9962&sid=ace5be6ab026960b89e3e0c783ff7577" ta…

    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.

  • Warning Line 126, Column 72: reference not terminated by REFC delimiter
    …net/forum/viewtopic.php?f=1&t=9962&sid=ace5be6ab026960b89e3e0c783ff7577" targe…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 126, Column 72: reference to external entity in attribute value
    …net/forum/viewtopic.php?f=1&t=9962&sid=ace5be6ab026960b89e3e0c783ff7577" targe…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 126, Column 72: reference to entity "sid" for which no system identifier could be generated
    …net/forum/viewtopic.php?f=1&t=9962&sid=ace5be6ab026960b89e3e0c783ff7577" targe…

    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 126, Column 68: entity was defined here
    …eam.net/forum/viewtopic.php?f=1&t=9962&sid=ace5be6ab026960b89e3e0c783ff7577" t…
  • Error Line 130, Column 14: end tag for "br" omitted, but OMITTAG NO was specified
    					</a><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 130, Column 10: start tag was here
    					</a><br>
  • Error Line 134, Column 10: end tag for "br" omitted, but OMITTAG NO was specified
    					<br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 134, Column 6: start tag was here
    					<br>
  • Warning Line 140, Column 91: reference not terminated by REFC delimiter
    …dpstream.net/forum/viewtopic.php?f=1&t=14172" style="color:red;">Liste des fil…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 140, Column 91: reference to external entity in attribute value
    …dpstream.net/forum/viewtopic.php?f=1&t=14172" style="color:red;">Liste des fil…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 140, Column 91: reference to entity "t" for which no system identifier could be generated
    …dpstream.net/forum/viewtopic.php?f=1&t=14172" style="color:red;">Liste des fil…

    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 126, Column 61: entity was defined here
    …r.dpstream.net/forum/viewtopic.php?f=1&t=9962&sid=ace5be6ab026960b89e3e0c783ff…
  • Error Line 156, Column 162: required attribute "alt" not specified
    …/icone_txt.gif" border="0" width="7" height="10" /> Pour les fans de Castle</a>

    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 163, Column 162: required attribute "alt" not specified
    …ne_txt.gif" border="0" width="7" height="10" /> Anime fans Insomniac Club !</a>

    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 170, Column 162: required attribute "alt" not specified
    …gif" border="0" width="7" height="10" /> Vos Pseudo. D'où viennent-ils ? :p</a>

    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 177, Column 162: required attribute "alt" not specified
    …one_txt.gif" border="0" width="7" height="10" /> [Jeu] Suite de mot logique</a>

    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 184, Column 162: required attribute "alt" not specified
    …/theme/icone_txt.gif" border="0" width="7" height="10" /> JEUX Des Citation</a>

    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 191, Column 162: required attribute "alt" not specified
    …txt.gif" border="0" width="7" height="10" /> [Jeu] alphabet des...chansons!</a>

    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 198, Column 162: required attribute "alt" not specified
    …t.gif" border="0" width="7" height="10" /> [JEU] Devinez-moi version SERIES</a>

    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 162: required attribute "alt" not specified
    ….gif" border="0" width="7" height="10" /> Vous cherchez un manga, venez ici</a>

    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 212, Column 162: required attribute "alt" not specified
    …e/icone_txt.gif" border="0" width="7" height="10" /> The Bloody Chocolates.</a>

    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 219, Column 162: required attribute "alt" not specified
    …txt.gif" border="0" width="7" height="10" /> Pour les fans de Spartacus!!!!</a>

    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 226, Column 162: required attribute "alt" not specified
    …/theme/icone_txt.gif" border="0" width="7" height="10" /> [Jeu] Shabadabada</a>

    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 233, Column 162: required attribute "alt" not specified
    …if" border="0" width="7" height="10" /> [Jeu]•Quizz • Pays • Capitale • Ville …

    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 245, Column 46: cannot generate system identifier for general entity "aff"
    …e="color:#FF9922;" href="?action=cent&aff=dernier"><b>Afficher les 100 dernier…

    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 245, Column 46: general entity "aff" not defined and no default entity
    …e="color:#FF9922;" href="?action=cent&aff=dernier"><b>Afficher les 100 dernier…

    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.

  • Warning Line 245, Column 49: reference not terminated by REFC delimiter
    …color:#FF9922;" href="?action=cent&aff=dernier"><b>Afficher les 100 derniers a…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 245, Column 49: reference to external entity in attribute value
    …color:#FF9922;" href="?action=cent&aff=dernier"><b>Afficher les 100 derniers a…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 245, Column 49: reference to entity "aff" for which no system identifier could be generated
    …color:#FF9922;" href="?action=cent&aff=dernier"><b>Afficher les 100 derniers 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 245, Column 45: entity was defined here
    …le="color:#FF9922;" href="?action=cent&aff=dernier"><b>Afficher les 100 dernie…
  • Error Line 259, Column 1837: required attribute "type" not specified
    …-4570-saison-1-episode-05 [FR].html">Last Man Standing - S1E05 [FR]</a><script>

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

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

  • Warning Line 267, Column 24: character "&" is the first character of a delimiter but occurred as data
    if((navigateur == 'ok')&&(scriptauto!=1)){ 

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 267, Column 25: character "&" is the first character of a delimiter but occurred as data
    if((navigateur == 'ok')&&(scriptauto!=1)){ 

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 291, Column 50: reference not terminated by REFC delimiter
    …color:#FF9922;" href="?action=cent&aff=tophebdo"><b>Afficher les 100 plus vus …

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 291, Column 50: reference to external entity in attribute value
    …color:#FF9922;" href="?action=cent&aff=tophebdo"><b>Afficher les 100 plus vus …

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 291, Column 50: reference to entity "aff" for which no system identifier could be generated
    …color:#FF9922;" href="?action=cent&aff=tophebdo"><b>Afficher les 100 plus vus …

    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 245, Column 45: entity was defined here
    …le="color:#FF9922;" href="?action=cent&aff=dernier"><b>Afficher les 100 dernie…
  • Error Line 291, Column 115: end tag for "br" omitted, but OMITTAG NO was specified
    …ction=cent&aff=tophebdo"><b>Afficher les 100 plus vus de la semaine</b></a><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 291, Column 111: start tag was here
    …ction=cent&aff=tophebdo"><b>Afficher les 100 plus vus de la semaine</b></a><br>
  • Warning Line 321, Column 50: reference not terminated by REFC delimiter
    …color:#FF9922;" href="?action=cent&aff=top"><b>Afficher les 100 plus vus</b></…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 321, Column 50: reference to external entity in attribute value
    …color:#FF9922;" href="?action=cent&aff=top"><b>Afficher les 100 plus vus</b></…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 321, Column 50: reference to entity "aff" for which no system identifier could be generated
    …color:#FF9922;" href="?action=cent&aff=top"><b>Afficher les 100 plus vus</b></…

    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 245, Column 45: entity was defined here
    …le="color:#FF9922;" href="?action=cent&aff=dernier"><b>Afficher les 100 dernie…
  • Error Line 326, Column 26: document type does not allow element "th" here; assuming missing "tr" start-tag
    			<th style="width:40%;">Films les plus vus</th>
  • Warning Line 352, Column 49: reference not terminated by REFC delimiter
    …color:#FF9922;" href="?action=cent&aff=topnotefilm"><b>Afficher les 100 films …

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 352, Column 49: reference to external entity in attribute value
    …color:#FF9922;" href="?action=cent&aff=topnotefilm"><b>Afficher les 100 films …

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 352, Column 49: reference to entity "aff" for which no system identifier could be generated
    …color:#FF9922;" href="?action=cent&aff=topnotefilm"><b>Afficher les 100 films …

    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 245, Column 45: entity was defined here
    …le="color:#FF9922;" href="?action=cent&aff=dernier"><b>Afficher les 100 dernie…
  • Error Line 370, Column 14: end tag for "br" omitted, but OMITTAG NO was specified
    									<br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 370, Column 10: start tag was here
    									<br>
  • Error Line 386, Column 14: end tag for "br" omitted, but OMITTAG NO was specified
    									<br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 386, Column 10: start tag was here
    									<br>
  • Error Line 402, Column 14: end tag for "br" omitted, but OMITTAG NO was specified
    									<br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 402, Column 10: start tag was here
    									<br>
  • Error Line 418, Column 14: end tag for "br" omitted, but OMITTAG NO was specified
    									<br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 418, Column 10: start tag was here
    									<br>
  • Error Line 434, Column 14: end tag for "br" omitted, but OMITTAG NO was specified
    									<br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 434, Column 10: start tag was here
    									<br>
  • Error Line 450, Column 14: end tag for "br" omitted, but OMITTAG NO was specified
    									<br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 450, Column 10: start tag was here
    									<br>
  • Error Line 466, Column 14: end tag for "br" omitted, but OMITTAG NO was specified
    									<br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 466, Column 10: start tag was here
    									<br>
  • Error Line 482, Column 14: end tag for "br" omitted, but OMITTAG NO was specified
    									<br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 482, Column 10: start tag was here
    									<br>
  • Error Line 498, Column 14: end tag for "br" omitted, but OMITTAG NO was specified
    									<br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 498, Column 10: start tag was here
    									<br>
  • Error Line 514, Column 14: end tag for "br" omitted, but OMITTAG NO was specified
    									<br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 514, Column 10: start tag was here
    									<br>
  • Error Line 530, Column 14: end tag for "br" omitted, but OMITTAG NO was specified
    									<br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 530, Column 10: start tag was here
    									<br>
  • Error Line 546, Column 14: end tag for "br" omitted, but OMITTAG NO was specified
    									<br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 546, Column 10: start tag was here
    									<br>
  • Error Line 562, Column 14: end tag for "br" omitted, but OMITTAG NO was specified
    									<br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 562, Column 10: start tag was here
    									<br>
  • Error Line 578, Column 14: end tag for "br" omitted, but OMITTAG NO was specified
    									<br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 578, Column 10: start tag was here
    									<br>
  • Error Line 594, Column 14: end tag for "br" omitted, but OMITTAG NO was specified
    									<br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 594, Column 10: start tag was here
    									<br>
  • Error Line 609, Column 11: required attribute "type" not specified
    			<script>

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

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

  • Error Line 621, Column 7: end tag for "center" omitted, but OMITTAG NO was specified
    	</div>		

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 112, Column 3: start tag was here
    		<center>  
  • Error Line 628, Column 26: end tag for "br" omitted, but OMITTAG NO was specified
    				<b>milou_29290<br></b>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 628, Column 19: start tag was here
    				<b>milou_29290<br></b>
  • Error Line 629, Column 36: end tag for "br" omitted, but OMITTAG NO was specified
    				Nombre de Membres : 1257985<br><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 629, Column 32: start tag was here
    				Nombre de Membres : 1257985<br><br>
  • Error Line 629, Column 40: end tag for "br" omitted, but OMITTAG NO was specified
    				Nombre de Membres : 1257985<br><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 629, Column 36: start tag was here
    				Nombre de Membres : 1257985<br><br>
  • Error Line 633, Column 23: end tag for "br" omitted, but OMITTAG NO was specified
    							Identifiant<br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 633, Column 19: start tag was here
    							Identifiant<br>
  • Error Line 634, Column 56: end tag for "input" omitted, but OMITTAG NO was specified
    							<input type="text" name="login" maxlength="250"><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 634, Column 8: start tag was here
    							<input type="text" name="login" maxlength="250"><br>
  • Error Line 634, Column 60: end tag for "br" omitted, but OMITTAG NO was specified
    							<input type="text" name="login" maxlength="250"><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 634, Column 56: start tag was here
    							<input type="text" name="login" maxlength="250"><br>
  • Error Line 635, Column 24: end tag for "br" omitted, but OMITTAG NO was specified
    							Mot de passe<br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 635, Column 20: start tag was here
    							Mot de passe<br>
  • Error Line 636, Column 65: end tag for "input" omitted, but OMITTAG NO was specified
    							<input type="password"name="mot_de_passe" maxlength="10"><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 636, Column 8: start tag was here
    							<input type="password"name="mot_de_passe" maxlength="10"><br>
  • Error Line 636, Column 69: end tag for "br" omitted, but OMITTAG NO was specified
    							<input type="password"name="mot_de_passe" maxlength="10"><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 636, Column 65: start tag was here
    							<input type="password"name="mot_de_passe" maxlength="10"><br>
  • Error Line 637, Column 50: end tag for "input" omitted, but OMITTAG NO was specified
    							<input type="submit" value="Se connecter"><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 637, Column 8: start tag was here
    							<input type="submit" value="Se connecter"><br>
  • Error Line 637, Column 54: end tag for "br" omitted, but OMITTAG NO was specified
    							<input type="submit" value="Se connecter"><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 637, Column 50: start tag was here
    							<input type="submit" value="Se connecter"><br>
  • Error Line 638, Column 58: end tag for "br" omitted, but OMITTAG NO was specified
    							<a href="registrer.html">==> S'enregistrer</a><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 638, Column 54: start tag was here
    							<a href="registrer.html">==> S'enregistrer</a><br>
  • Warning Line 639, Column 35: cannot generate system identifier for general entity "p"
    							<a href="/?action=password&p=getpass">==> Mot de passe oublié</a><br>

    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 639, Column 35: general entity "p" not defined and no default entity
    							<a href="/?action=password&p=getpass">==> Mot de passe oublié</a><br>

    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.

  • Warning Line 639, Column 36: reference not terminated by REFC delimiter
    							<a href="/?action=password&p=getpass">==> Mot de passe oublié</a><br>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 639, Column 36: reference to external entity in attribute value
    							<a href="/?action=password&p=getpass">==> Mot de passe oublié</a><br>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 639, Column 36: reference to entity "p" for which no system identifier could be generated
    							<a href="/?action=password&p=getpass">==> Mot de passe oublié</a><br>

    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 639, Column 34: entity was defined here
    							<a href="/?action=password&p=getpass">==> Mot de passe oublié</a><br>
  • Error Line 639, Column 77: end tag for "br" omitted, but OMITTAG NO was specified
    							<a href="/?action=password&p=getpass">==> Mot de passe oublié</a><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 639, Column 73: start tag was here
    							<a href="/?action=password&p=getpass">==> Mot de passe oublié</a><br>
  • Error Line 643, Column 15: end tag for "br" omitted, but OMITTAG NO was specified
    										<br>			

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 643, Column 11: start tag was here
    										<br>			
  • Warning Line 645, Column 51: cannot generate system identifier for general entity "action"
    …"http://www.subfactory.fr/series.html&action=g_calendar" target="_blank" >V2</…

    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 645, Column 51: general entity "action" not defined and no default entity
    …"http://www.subfactory.fr/series.html&action=g_calendar" target="_blank" >V2</…

    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.

  • Warning Line 645, Column 57: reference not terminated by REFC delimiter
    …p://www.subfactory.fr/series.html&action=g_calendar" target="_blank" >V2</a> | 

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 645, Column 57: reference to external entity in attribute value
    …p://www.subfactory.fr/series.html&action=g_calendar" target="_blank" >V2</a> | 

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 645, Column 57: reference to entity "action" for which no system identifier could be generated
    …p://www.subfactory.fr/series.html&action=g_calendar" target="_blank" >V2</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 645, Column 50: entity was defined here
    …="http://www.subfactory.fr/series.html&action=g_calendar" target="_blank" >V2<…
  • Error Line 646, Column 66: end tag for "br" omitted, but OMITTAG NO was specified
    				<a href="http://tvcountdown.com/" target="_blank" >V3</a><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 646, Column 62: start tag was here
    				<a href="http://tvcountdown.com/" target="_blank" >V3</a><br>
  • Warning Line 647, Column 63: reference not terminated by REFC delimiter
    …dpstream.net/forum/viewtopic.php?f=7&t=13983" target="_blank" >Débrideurs Mixt…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 647, Column 63: reference to external entity in attribute value
    …dpstream.net/forum/viewtopic.php?f=7&t=13983" target="_blank" >Débrideurs Mixt…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 647, Column 63: reference to entity "t" for which no system identifier could be generated
    …dpstream.net/forum/viewtopic.php?f=7&t=13983" target="_blank" >Débrideurs Mixt…

    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 126, Column 61: entity was defined here
    …r.dpstream.net/forum/viewtopic.php?f=1&t=9962&sid=ace5be6ab026960b89e3e0c783ff…
  • Error Line 647, Column 125: end tag for "br" omitted, but OMITTAG NO was specified
    …ewtopic.php?f=7&t=13983" target="_blank" >Débrideurs Mixture et PureVid</a><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 647, Column 121: start tag was here
    …ewtopic.php?f=7&t=13983" target="_blank" >Débrideurs Mixture et PureVid</a><br>
  • Warning Line 648, Column 63: reference not terminated by REFC delimiter
    …dpstream.net/forum/viewtopic.php?f=7&t=14054">Comment regarder une vidéo</a><b…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 648, Column 63: reference to external entity in attribute value
    …dpstream.net/forum/viewtopic.php?f=7&t=14054">Comment regarder une vidéo</a><b…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 648, Column 63: reference to entity "t" for which no system identifier could be generated
    …dpstream.net/forum/viewtopic.php?f=7&t=14054">Comment regarder une vidéo</a><b…

    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 126, Column 61: entity was defined here
    …r.dpstream.net/forum/viewtopic.php?f=1&t=9962&sid=ace5be6ab026960b89e3e0c783ff…
  • Error Line 648, Column 105: end tag for "br" omitted, but OMITTAG NO was specified
    …pstream.net/forum/viewtopic.php?f=7&t=14054">Comment regarder une vidéo</a><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 648, Column 101: start tag was here
    …pstream.net/forum/viewtopic.php?f=7&t=14054">Comment regarder une vidéo</a><br>
  • Error Line 651, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    				<br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 651, Column 5: start tag was here
    				<br>
  • Error Line 652, Column 100: end tag for "br" omitted, but OMITTAG NO was specified
    …cript">Page générée en <span style="color:#454545;">0.000</span> sec</div>	<br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 652, Column 96: start tag was here
    …cript">Page générée en <span style="color:#454545;">0.000</span> sec</div>	<br>
  • Error Line 668, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    				<br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 668, Column 5: start tag was here
    				<br>
  • Error Line 672, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    				<br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 672, Column 5: start tag was here
    				<br>
  • Error Line 676, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    				<br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 676, Column 5: start tag was here
    				<br>
  • Error Line 678, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    				<br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 678, Column 5: start tag was here
    				<br>
  • Error Line 703, Column 10: ID "pied" already defined
    <div id="pied">			

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 700, Column 11: ID "pied" first defined here
    	<div id="pied"></div></td></tr></table>
  • Error Line 716, Column 9: 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>.

  • Error Line 716, Column 9: document type does not allow element "style" here
    		<style>

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

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

  • Warning Line 748, Column 22: character "<" is the first character of a delimiter but occurred as data
    							ref.replace(/[<>"]/g, '').replace(/&/g, '%26');

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 748, Column 43: character "&" is the first character of a delimiter but occurred as data
    							ref.replace(/[<>"]/g, '').replace(/&/g, '%26');

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 775, Column 171: document type does not allow element "a" here
    …cute;taill&eacute;es." target="_blank"><img src="http://www.livecount.fr/widge…

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

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

  • Warning Line 775, Column 229: cannot generate system identifier for general entity "ref"
    …w.livecount.fr/widget.php?wid='+wid+'&ref='+ref+'&os='+OSName+'&res='+EcranLar…

    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 775, Column 229: general entity "ref" not defined and no default entity
    …w.livecount.fr/widget.php?wid='+wid+'&ref='+ref+'&os='+OSName+'&res='+EcranLar…

    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.

  • Warning Line 775, Column 232: reference not terminated by REFC delimiter
    …ivecount.fr/widget.php?wid='+wid+'&ref='+ref+'&os='+OSName+'&res='+EcranLarg+'…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 775, Column 232: reference to external entity in attribute value
    …ivecount.fr/widget.php?wid='+wid+'&ref='+ref+'&os='+OSName+'&res='+EcranLarg+'…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 775, Column 232: reference to entity "ref" for which no system identifier could be generated
    …ivecount.fr/widget.php?wid='+wid+'&ref='+ref+'&os='+OSName+'&res='+EcranLarg+'…

    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 775, Column 228: entity was defined here
    …ww.livecount.fr/widget.php?wid='+wid+'&ref='+ref+'&os='+OSName+'&res='+EcranLa…
  • Warning Line 775, Column 241: cannot generate system identifier for general entity "os"
    …fr/widget.php?wid='+wid+'&ref='+ref+'&os='+OSName+'&res='+EcranLarg+'x'+EcranH…

    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 775, Column 241: general entity "os" not defined and no default entity
    …fr/widget.php?wid='+wid+'&ref='+ref+'&os='+OSName+'&res='+EcranLarg+'x'+EcranH…

    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.

  • Warning Line 775, Column 243: reference not terminated by REFC delimiter
    …/widget.php?wid='+wid+'&ref='+ref+'&os='+OSName+'&res='+EcranLarg+'x'+EcranHau…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 775, Column 243: reference to external entity in attribute value
    …/widget.php?wid='+wid+'&ref='+ref+'&os='+OSName+'&res='+EcranLarg+'x'+EcranHau…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 775, Column 243: reference to entity "os" for which no system identifier could be generated
    …/widget.php?wid='+wid+'&ref='+ref+'&os='+OSName+'&res='+EcranLarg+'x'+EcranHau…

    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 775, Column 240: entity was defined here
    ….fr/widget.php?wid='+wid+'&ref='+ref+'&os='+OSName+'&res='+EcranLarg+'x'+Ecran…
  • Warning Line 775, Column 255: cannot generate system identifier for general entity "res"
    …wid='+wid+'&ref='+ref+'&os='+OSName+'&res='+EcranLarg+'x'+EcranHaut+'&nav='+na…

    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 775, Column 255: general entity "res" not defined and no default entity
    …wid='+wid+'&ref='+ref+'&os='+OSName+'&res='+EcranLarg+'x'+EcranHaut+'&nav='+na…

    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.

  • Warning Line 775, Column 258: reference not terminated by REFC delimiter
    …='+wid+'&ref='+ref+'&os='+OSName+'&res='+EcranLarg+'x'+EcranHaut+'&nav='+navig…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 775, Column 258: reference to external entity in attribute value
    …='+wid+'&ref='+ref+'&os='+OSName+'&res='+EcranLarg+'x'+EcranHaut+'&nav='+navig…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 775, Column 258: reference to entity "res" for which no system identifier could be generated
    …='+wid+'&ref='+ref+'&os='+OSName+'&res='+EcranLarg+'x'+EcranHaut+'&nav='+navig…

    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 775, Column 254: entity was defined here
    …?wid='+wid+'&ref='+ref+'&os='+OSName+'&res='+EcranLarg+'x'+EcranHaut+'&nav='+n…
  • Warning Line 775, Column 287: cannot generate system identifier for general entity "nav"
    …ame+'&res='+EcranLarg+'x'+EcranHaut+'&nav='+navigateur+'" border=0 alt="Compte…

    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 775, Column 287: general entity "nav" not defined and no default entity
    …ame+'&res='+EcranLarg+'x'+EcranHaut+'&nav='+navigateur+'" border=0 alt="Compte…

    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.

  • Warning Line 775, Column 290: reference not terminated by REFC delimiter
    …+'&res='+EcranLarg+'x'+EcranHaut+'&nav='+navigateur+'" border=0 alt="Compteur …

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 775, Column 290: reference to external entity in attribute value
    …+'&res='+EcranLarg+'x'+EcranHaut+'&nav='+navigateur+'" border=0 alt="Compteur …

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 775, Column 290: reference to entity "nav" for which no system identifier could be generated
    …+'&res='+EcranLarg+'x'+EcranHaut+'&nav='+navigateur+'" border=0 alt="Compteur …

    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 775, Column 286: entity was defined here
    …Name+'&res='+EcranLarg+'x'+EcranHaut+'&nav='+navigateur+'" border=0 alt="Compt…
  • Error Line 775, Column 314: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …anLarg+'x'+EcranHaut+'&nav='+navigateur+'" border=0 alt="Compteur live"></a>');
  • Error Line 775, Column 339: end tag for "img" omitted, but OMITTAG NO was specified
    …anLarg+'x'+EcranHaut+'&nav='+navigateur+'" border=0 alt="Compteur live"></a>');

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 775, Column 172: start tag was here
    …ute;taill&eacute;es." target="_blank"><img src="http://www.livecount.fr/widget…
  • Error Line 784, Column 9: end tag for "center" omitted, but OMITTAG NO was specified
    			</div>	

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 741, Column 5: start tag was here
    				<center>
  • Error Line 790, Column 6: end tag for "br" omitted, but OMITTAG NO was specified
    	<br>Notre site ne consiste qu'en un référencement de liens vidéos hébergées pa…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 790, Column 2: start tag was here
    	<br>Notre site ne consiste qu'en un référencement de liens vidéos hébergées pa…
  • Error Line 791, Column 68: end tag for "br" omitted, but OMITTAG NO was specified
    …us n'hébergeons aucune vidéo. Nous n'uploadons aucune vidéo.<br><br><br><br>			

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 791, Column 64: start tag was here
    …us n'hébergeons aucune vidéo. Nous n'uploadons aucune vidéo.<br><br><br><br>			
  • Error Line 791, Column 72: end tag for "br" omitted, but OMITTAG NO was specified
    …us n'hébergeons aucune vidéo. Nous n'uploadons aucune vidéo.<br><br><br><br>			

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 791, Column 68: start tag was here
    …us n'hébergeons aucune vidéo. Nous n'uploadons aucune vidéo.<br><br><br><br>			
  • Error Line 791, Column 76: end tag for "br" omitted, but OMITTAG NO was specified
    …us n'hébergeons aucune vidéo. Nous n'uploadons aucune vidéo.<br><br><br><br>			

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 791, Column 72: start tag was here
    …us n'hébergeons aucune vidéo. Nous n'uploadons aucune vidéo.<br><br><br><br>			
  • Error Line 791, Column 80: end tag for "br" omitted, but OMITTAG NO was specified
    …us n'hébergeons aucune vidéo. Nous n'uploadons aucune vidéo.<br><br><br><br>			

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 791, Column 76: start tag was here
    …us n'hébergeons aucune vidéo. Nous n'uploadons aucune vidéo.<br><br><br><br>			
  • Error Line 806, Column 53: document type does not allow element "script" here
    …ge="javascript" type="text/javascript">document.getElementById("temps_script")…

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

Visitor Analysis

Daily Visitor
  • 74.667 visits
Daily Visitor