Visionnez gratuitement en streaming nos vidéos de sexe d'une durée moyenne de 30mn ! Notre tube porno contient la plus grosse archive de films français. Vos notes et commentaires sont les bienvenue... ...

vporno.tv
  • Domain Name
    vporno.tv
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #15920
  • Page Size
    68.9 KB
  • Ip Address
    69.55.53.92
  • Heading
    H1: 0, H2: 38, H3: 48, H4: 0, H5: 114, H6: 0
  • Images
    0 GIF, 38 JPG, 7 PNG

Website Meta Analysis

  • Title
    Vporno.tv : Vidéo porno 100% gratuit sur le meilleur tube français
  • Meta Keyword
  • Meta Description
    Visionnez gratuitement en streaming nos vidéos de sexe d'une durée moyenne de 30mn ! Notre tube porno contient la plus grosse archive de films français. Vos notes et commentaires sont les bienvenue...

Technical Analysis

  • Webserver
    nginx
  • Ip Address
    69.55.53.92
  • Domain Age
    4 Years, 8 Months, 21 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from vporno.tv.

HTML Analysis

  • server: nginx
  • date: Fri, 13 Sep 2013 02:00:10 GMT
  • content-type: text/html
  • connection: keep-alive
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • content-encoding: gzip
  • vary: Accept-Encoding
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for vporno.tv

DNS Analysis


DNS servers
ns24.domaincontrol.com [208.109.255.12]
ns23.domaincontrol.com [216.69.185.12]


DNS Records

Answer records
vporno.tv A 69.55.53.92 3600s
vporno.tv MX
preference: 0
exchange: smtp.secureserver.net
3600s
vporno.tv MX
preference: 10
exchange: mailstore1.secureserver.net
3600s
vporno.tv NS  ns23.domaincontrol.com 3600s
vporno.tv NS  ns24.domaincontrol.com 3600s
vporno.tv SOA
server: ns23.domaincontrol.com
email: dns@jomax.net
serial: 2013020800
refresh: 28800
retry: 7200
expire: 604800
minimum ttl: 3600
3600s

Authority records

Additional records

IP 69.55.53.92 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Brooklyn
  • Continent Code
    11201
  • Latitude
    718
  • Longitude
    501
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 69.55.53.92"
    #
    # Use "?" to get help.
    #

    #
    # The following results may also be obtained via:
    # http://whois.arin.net/rest/nets;q=69.55.53.92?showDetails=true&showARIN=false&ext=netref2
    #

    NetRange: 69.55.48.0 - 69.55.63.255
    CIDR: 69.55.48.0/20
    OriginAS:
    NetName: SERVERSTACK1
    NetHandle: NET-69-55-48-0-1
    Parent: NET-69-0-0-0-0
    NetType: Direct Allocation
    RegDate: 2007-05-21
    Updated: 2012-09-11
    Ref: http://whois.arin.net/rest/net/NET-69-55-48-0-1

    OrgName: ServerStack, Inc.
    OrgId: RCN-12
    Address: 270 Lafayette St
    Address: Suite 1105
    City: New York
    StateProv: NY
    PostalCode: 10012
    Country: US
    RegDate: 2003-06-18
    Updated: 2013-01-11
    Ref: http://whois.arin.net/rest/org/RCN-12

    OrgAbuseHandle: MUR-ARIN
    OrgAbuseName: Uretsky, Moisey
    OrgAbusePhone: +1-866-976-8752
    OrgAbuseEmail: abuse@serverstack.com
    OrgAbuseRef: http://whois.arin.net/rest/poc/MUR-ARIN

    OrgTechHandle: MUR-ARIN
    OrgTechName: Uretsky, Moisey
    OrgTechPhone: +1-866-976-8752
    OrgTechEmail: abuse@serverstack.com
    OrgTechRef: http://whois.arin.net/rest/poc/MUR-ARIN

    #
    # ARIN WHOIS data and services are subject to the Terms of Use
    # available at: https://www.arin.net/whois_tou.html
    #

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 262 Errors
  • 85 Warnings
Ratio Text/Html
  • 0.7795757584345288
Message Error
  • Error Line 5, Column 61: there is no attribute "charset"
    <meta http-equiv="Content-Type" content="text/html" charset="utf-8" />

    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 9, Column 36: end tag for "base" omitted, but OMITTAG NO was specified
    <base href="http://www.vporno.tv/">

    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 9, Column 1: start tag was here
    <base href="http://www.vporno.tv/">
  • Warning Line 35, Column 86: cannot generate system identifier for general entity "idsite"
    …ication.exoclick.com/splash.php?cat=2&idsite=132932&idzone=301978&login=vporno…

    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 35, Column 86: general entity "idsite" not defined and no default entity
    …ication.exoclick.com/splash.php?cat=2&idsite=132932&idzone=301978&login=vporno…

    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 35, Column 92: reference not terminated by REFC delimiter
    …n.exoclick.com/splash.php?cat=2&idsite=132932&idzone=301978&login=vporno_flatf…

    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 35, Column 92: reference to external entity in attribute value
    …n.exoclick.com/splash.php?cat=2&idsite=132932&idzone=301978&login=vporno_flatf…

    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 35, Column 92: reference to entity "idsite" for which no system identifier could be generated
    …n.exoclick.com/splash.php?cat=2&idsite=132932&idzone=301978&login=vporno_flatf…

    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 35, Column 85: entity was defined here
    …dication.exoclick.com/splash.php?cat=2&idsite=132932&idzone=301978&login=vporn…
  • Warning Line 35, Column 100: cannot generate system identifier for general entity "idzone"
    …ck.com/splash.php?cat=2&idsite=132932&idzone=301978&login=vporno_flatfee&type=…

    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 35, Column 100: general entity "idzone" not defined and no default entity
    …ck.com/splash.php?cat=2&idsite=132932&idzone=301978&login=vporno_flatfee&type=…

    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 35, Column 106: reference not terminated by REFC delimiter
    …/splash.php?cat=2&idsite=132932&idzone=301978&login=vporno_flatfee&type=3"></s…

    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 35, Column 106: reference to external entity in attribute value
    …/splash.php?cat=2&idsite=132932&idzone=301978&login=vporno_flatfee&type=3"></s…

    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 35, Column 106: reference to entity "idzone" for which no system identifier could be generated
    …/splash.php?cat=2&idsite=132932&idzone=301978&login=vporno_flatfee&type=3"></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.

  • Info Line 35, Column 99: entity was defined here
    …ick.com/splash.php?cat=2&idsite=132932&idzone=301978&login=vporno_flatfee&type…
  • Warning Line 35, Column 114: cannot generate system identifier for general entity "login"
    …sh.php?cat=2&idsite=132932&idzone=301978&login=vporno_flatfee&type=3"></script>

    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 35, Column 114: general entity "login" not defined and no default entity
    …sh.php?cat=2&idsite=132932&idzone=301978&login=vporno_flatfee&type=3"></script>

    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 35, Column 119: reference not terminated by REFC delimiter
    …sh.php?cat=2&idsite=132932&idzone=301978&login=vporno_flatfee&type=3"></script>

    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 35, Column 119: reference to external entity in attribute value
    …sh.php?cat=2&idsite=132932&idzone=301978&login=vporno_flatfee&type=3"></script>

    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 35, Column 119: reference to entity "login" for which no system identifier could be generated
    …sh.php?cat=2&idsite=132932&idzone=301978&login=vporno_flatfee&type=3"></script>

    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 35, Column 113: entity was defined here
    …sh.php?cat=2&idsite=132932&idzone=301978&login=vporno_flatfee&type=3"></script>
  • Warning Line 35, Column 135: cannot generate system identifier for general entity "type"
    …sh.php?cat=2&idsite=132932&idzone=301978&login=vporno_flatfee&type=3"></script>

    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 35, Column 135: general entity "type" not defined and no default entity
    …sh.php?cat=2&idsite=132932&idzone=301978&login=vporno_flatfee&type=3"></script>

    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 35, Column 139: reference not terminated by REFC delimiter
    …sh.php?cat=2&idsite=132932&idzone=301978&login=vporno_flatfee&type=3"></script>

    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 35, Column 139: reference to external entity in attribute value
    …sh.php?cat=2&idsite=132932&idzone=301978&login=vporno_flatfee&type=3"></script>

    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 35, Column 139: reference to entity "type" for which no system identifier could be generated
    …sh.php?cat=2&idsite=132932&idzone=301978&login=vporno_flatfee&type=3"></script>

    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 35, Column 134: entity was defined here
    …sh.php?cat=2&idsite=132932&idzone=301978&login=vporno_flatfee&type=3"></script>
  • Error Line 36, Column 18: there is no attribute "Language"
    <script Language="JavaScript">

    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 36, Column 30: required attribute "type" not specified
    <script Language="JavaScript">

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

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

  • Error Line 63, Column 8: required attribute "type" not specified
    <script>(function(d, s, id) {

    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 84, Column 56: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
          <li id="nav_1"><a href="http://www.vporno.tv"><h3>ACCUEIL</h3></a></li>

    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 85, Column 67: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    … <li id="nav_2"><a href="http://www.vporno.tv/videos/"><h3>VIDEOS</h3></a></li>

    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 86, Column 68: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    … id="nav_3"><a href="http://www.vporno.tv/actrices/"><h3>ACTRICES</h3></a></li>

    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 87, Column 70: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …<a href="http://www.vporno.tv/communaute/"><h3>COMMUNAUT&Eacute; </h3></a></li>

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

  • Warning Line 88, Column 88: reference not terminated by REFC delimiter
    …n.exoclick.com/splash.php?cat=2&idsite=132932&idzone=301980&login=vporno_flatf…

    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 88, Column 88: reference to external entity in attribute value
    …n.exoclick.com/splash.php?cat=2&idsite=132932&idzone=301980&login=vporno_flatf…

    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 88, Column 88: reference to entity "idsite" for which no system identifier could be generated
    …n.exoclick.com/splash.php?cat=2&idsite=132932&idzone=301980&login=vporno_flatf…

    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 35, Column 85: entity was defined here
    …dication.exoclick.com/splash.php?cat=2&idsite=132932&idzone=301978&login=vporn…
  • Warning Line 88, Column 102: reference not terminated by REFC delimiter
    …/splash.php?cat=2&idsite=132932&idzone=301980&login=vporno_flatfee&type=9&retu…

    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 88, Column 102: reference to external entity in attribute value
    …/splash.php?cat=2&idsite=132932&idzone=301980&login=vporno_flatfee&type=9&retu…

    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 88, Column 102: reference to entity "idzone" for which no system identifier could be generated
    …/splash.php?cat=2&idsite=132932&idzone=301980&login=vporno_flatfee&type=9&retu…

    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 35, Column 99: entity was defined here
    …ick.com/splash.php?cat=2&idsite=132932&idzone=301978&login=vporno_flatfee&type…
  • Warning Line 88, Column 115: reference not terminated by REFC delimiter
    …at=2&idsite=132932&idzone=301980&login=vporno_flatfee&type=9&return_url=" targ…

    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 88, Column 115: reference to external entity in attribute value
    …at=2&idsite=132932&idzone=301980&login=vporno_flatfee&type=9&return_url=" targ…

    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 88, Column 115: reference to entity "login" for which no system identifier could be generated
    …at=2&idsite=132932&idzone=301980&login=vporno_flatfee&type=9&return_url=" targ…

    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 35, Column 113: entity was defined here
    …sh.php?cat=2&idsite=132932&idzone=301978&login=vporno_flatfee&type=3"></script>
  • Warning Line 88, Column 135: reference not terminated by REFC delimiter
    …dzone=301980&login=vporno_flatfee&type=9&return_url=" target="_blank" rel="nof…

    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 88, Column 135: reference to external entity in attribute value
    …dzone=301980&login=vporno_flatfee&type=9&return_url=" target="_blank" rel="nof…

    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 88, Column 135: reference to entity "type" for which no system identifier could be generated
    …dzone=301980&login=vporno_flatfee&type=9&return_url=" target="_blank" rel="nof…

    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 35, Column 134: entity was defined here
    …sh.php?cat=2&idsite=132932&idzone=301978&login=vporno_flatfee&type=3"></script>
  • Warning Line 88, Column 138: cannot generate system identifier for general entity "return_url"
    …ne=301980&login=vporno_flatfee&type=9&return_url=" target="_blank" rel="nofoll…

    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 88, Column 138: general entity "return_url" not defined and no default entity
    …ne=301980&login=vporno_flatfee&type=9&return_url=" target="_blank" rel="nofoll…

    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 88, Column 148: reference not terminated by REFC delimiter
    …login=vporno_flatfee&type=9&return_url=" target="_blank" rel="nofollow"><h3>WE…

    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 88, Column 148: reference to external entity in attribute value
    …login=vporno_flatfee&type=9&return_url=" target="_blank" rel="nofollow"><h3>WE…

    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 88, Column 148: reference to entity "return_url" for which no system identifier could be generated
    …login=vporno_flatfee&type=9&return_url=" target="_blank" rel="nofollow"><h3>WE…

    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 88, Column 137: entity was defined here
    …one=301980&login=vporno_flatfee&type=9&return_url=" target="_blank" rel="nofol…
  • Error Line 88, Column 185: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …e&type=9&return_url=" target="_blank" rel="nofollow"><h3>WEBCAMS </h3></a></li>

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

  • Warning Line 89, Column 88: reference not terminated by REFC delimiter
    …n.exoclick.com/splash.php?cat=2&idsite=132932&idzone=301982&login=vporno_flatf…

    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 89, Column 88: reference to external entity in attribute value
    …n.exoclick.com/splash.php?cat=2&idsite=132932&idzone=301982&login=vporno_flatf…

    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 89, Column 88: reference to entity "idsite" for which no system identifier could be generated
    …n.exoclick.com/splash.php?cat=2&idsite=132932&idzone=301982&login=vporno_flatf…

    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 35, Column 85: entity was defined here
    …dication.exoclick.com/splash.php?cat=2&idsite=132932&idzone=301978&login=vporn…
  • Warning Line 89, Column 102: reference not terminated by REFC delimiter
    …/splash.php?cat=2&idsite=132932&idzone=301982&login=vporno_flatfee&type=9&retu…

    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 89, Column 102: reference to external entity in attribute value
    …/splash.php?cat=2&idsite=132932&idzone=301982&login=vporno_flatfee&type=9&retu…

    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 89, Column 102: reference to entity "idzone" for which no system identifier could be generated
    …/splash.php?cat=2&idsite=132932&idzone=301982&login=vporno_flatfee&type=9&retu…

    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 35, Column 99: entity was defined here
    …ick.com/splash.php?cat=2&idsite=132932&idzone=301978&login=vporno_flatfee&type…
  • Warning Line 89, Column 115: reference not terminated by REFC delimiter
    …at=2&idsite=132932&idzone=301982&login=vporno_flatfee&type=9&return_url=" targ…

    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 89, Column 115: reference to external entity in attribute value
    …at=2&idsite=132932&idzone=301982&login=vporno_flatfee&type=9&return_url=" targ…

    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 89, Column 115: reference to entity "login" for which no system identifier could be generated
    …at=2&idsite=132932&idzone=301982&login=vporno_flatfee&type=9&return_url=" targ…

    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 35, Column 113: entity was defined here
    …sh.php?cat=2&idsite=132932&idzone=301978&login=vporno_flatfee&type=3"></script>
  • Warning Line 89, Column 135: reference not terminated by REFC delimiter
    …dzone=301982&login=vporno_flatfee&type=9&return_url=" target="_blank" rel="nof…

    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 89, Column 135: reference to external entity in attribute value
    …dzone=301982&login=vporno_flatfee&type=9&return_url=" target="_blank" rel="nof…

    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 89, Column 135: reference to entity "type" for which no system identifier could be generated
    …dzone=301982&login=vporno_flatfee&type=9&return_url=" target="_blank" rel="nof…

    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 35, Column 134: entity was defined here
    …sh.php?cat=2&idsite=132932&idzone=301978&login=vporno_flatfee&type=3"></script>
  • Warning Line 89, Column 148: reference not terminated by REFC delimiter
    …login=vporno_flatfee&type=9&return_url=" target="_blank" rel="nofollow"><h3>RE…

    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 89, Column 148: reference to external entity in attribute value
    …login=vporno_flatfee&type=9&return_url=" target="_blank" rel="nofollow"><h3>RE…

    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 89, Column 148: reference to entity "return_url" for which no system identifier could be generated
    …login=vporno_flatfee&type=9&return_url=" target="_blank" rel="nofollow"><h3>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 88, Column 137: entity was defined here
    …one=301980&login=vporno_flatfee&type=9&return_url=" target="_blank" rel="nofol…
  • Error Line 89, Column 185: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …type=9&return_url=" target="_blank" rel="nofollow"><h3>RENCONTRE </h3></a></li>

    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 100, Column 73: end tag for "input" omitted, but OMITTAG NO was specified
            <input name="search_term" id="search_term" type="text" 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 100, Column 9: start tag was here
            <input name="search_term" id="search_term" type="text" value="">
  • Error Line 101, Column 71: end tag for "input" omitted, but OMITTAG NO was specified
            <input id="btn_search" name="search" value="ok" type="submit">

    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 101, Column 9: start tag was here
            <input id="btn_search" name="search" value="ok" type="submit">
  • Warning Line 113, Column 94: reference not terminated by REFC delimiter
    …exoclick.com/ads.php?type=728x90&login=vporno_flatfee&cat=2&search=&ad_title_c…

    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 113, Column 94: reference to external entity in attribute value
    …exoclick.com/ads.php?type=728x90&login=vporno_flatfee&cat=2&search=&ad_title_c…

    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 113, Column 94: reference to entity "login" for which no system identifier could be generated
    …exoclick.com/ads.php?type=728x90&login=vporno_flatfee&cat=2&search=&ad_title_c…

    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 35, Column 113: entity was defined here
    …sh.php?cat=2&idsite=132932&idzone=301978&login=vporno_flatfee&type=3"></script>
  • Warning Line 113, Column 110: cannot generate system identifier for general entity "cat"
    ….php?type=728x90&login=vporno_flatfee&cat=2&search=&ad_title_color=0000cc&bgco…

    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 113, Column 110: general entity "cat" not defined and no default entity
    ….php?type=728x90&login=vporno_flatfee&cat=2&search=&ad_title_color=0000cc&bgco…

    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 113, Column 113: reference not terminated by REFC delimiter
    …p?type=728x90&login=vporno_flatfee&cat=2&search=&ad_title_color=0000cc&bgcolor…

    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 113, Column 113: reference to external entity in attribute value
    …p?type=728x90&login=vporno_flatfee&cat=2&search=&ad_title_color=0000cc&bgcolor…

    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 113, Column 113: reference to entity "cat" for which no system identifier could be generated
    …p?type=728x90&login=vporno_flatfee&cat=2&search=&ad_title_color=0000cc&bgcolor…

    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 113, Column 109: entity was defined here
    …s.php?type=728x90&login=vporno_flatfee&cat=2&search=&ad_title_color=0000cc&bgc…
  • Warning Line 113, Column 116: cannot generate system identifier for general entity "search"
    …ype=728x90&login=vporno_flatfee&cat=2&search=&ad_title_color=0000cc&bgcolor=FF…

    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 113, Column 116: general entity "search" not defined and no default entity
    …ype=728x90&login=vporno_flatfee&cat=2&search=&ad_title_color=0000cc&bgcolor=FF…

    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 113, Column 122: reference not terminated by REFC delimiter
    …8x90&login=vporno_flatfee&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&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 113, Column 122: reference to external entity in attribute value
    …8x90&login=vporno_flatfee&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&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 113, Column 122: reference to entity "search" for which no system identifier could be generated
    …8x90&login=vporno_flatfee&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&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 113, Column 115: entity was defined here
    …type=728x90&login=vporno_flatfee&cat=2&search=&ad_title_color=0000cc&bgcolor=F…
  • Warning Line 113, Column 124: cannot generate system identifier for general entity "ad_title_color"
    …90&login=vporno_flatfee&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&bor…

    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 113, Column 124: general entity "ad_title_color" not defined and no default entity
    …90&login=vporno_flatfee&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&bor…

    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 113, Column 138: reference not terminated by REFC delimiter
    …o_flatfee&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

    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 113, Column 138: reference to external entity in attribute value
    …o_flatfee&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

    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 113, Column 138: reference to entity "ad_title_color" for which no system identifier could be generated
    …o_flatfee&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

    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 113, Column 123: entity was defined here
    …x90&login=vporno_flatfee&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&bo…
  • Warning Line 113, Column 146: cannot generate system identifier for general entity "bgcolor"
    …e&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000…

    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 113, Column 146: general entity "bgcolor" not defined and no default entity
    …e&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000…

    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 113, Column 153: reference not terminated by REFC delimiter
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

    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 113, Column 153: reference to external entity in attribute value
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

    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 113, Column 153: reference to entity "bgcolor" for which no system identifier could be generated
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

    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 113, Column 145: entity was defined here
    …ee&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=00…
  • Warning Line 113, Column 161: cannot generate system identifier for general entity "border"
    …&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block…

    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 113, Column 161: general entity "border" not defined and no default entity
    …&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block…

    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 113, Column 167: reference not terminated by REFC delimiter
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

    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 113, Column 167: reference to external entity in attribute value
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

    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 113, Column 167: reference to entity "border" for which no system identifier could be generated
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

    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 113, Column 160: entity was defined here
    …=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&bloc…
  • Warning Line 113, Column 170: cannot generate system identifier for general entity "border_color"
    …_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords…

    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 113, Column 170: general entity "border_color" not defined and no default entity
    …_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords…

    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 113, Column 182: reference not terminated by REFC delimiter
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

    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 113, Column 182: reference to external entity in attribute value
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

    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 113, Column 182: reference to entity "border_color" for which no system identifier could be generated
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

    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 113, Column 169: entity was defined here
    …e_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keyword…
  • Warning Line 113, Column 190: cannot generate system identifier for general entity "font"
    …r=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=0000…

    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 113, Column 190: general entity "font" not defined and no default entity
    …r=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=0000…

    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 113, Column 194: reference not terminated by REFC delimiter
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&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 113, Column 194: reference to external entity in attribute value
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&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 113, Column 194: reference to entity "font" for which no system identifier could be generated
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&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 113, Column 189: entity was defined here
    …or=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000…
  • Warning Line 113, Column 196: cannot generate system identifier for general entity "block_keywords"
    …FF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&ad_…

    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 113, Column 196: general entity "block_keywords" not defined and no default entity
    …FF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&ad_…

    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 113, Column 210: reference not terminated by REFC delimiter
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

    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 113, Column 210: reference to external entity in attribute value
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

    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 113, Column 210: reference to entity "block_keywords" for which no system identifier could be generated
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

    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 113, Column 195: entity was defined here
    …FFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&ad…
  • Warning Line 113, Column 212: cannot generate system identifier for general entity "ad_text_color"
    …er_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=00800…

    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 113, Column 212: general entity "ad_text_color" not defined and no default entity
    …er_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=00800…

    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 113, Column 225: reference not terminated by REFC delimiter
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

    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 113, Column 225: reference to external entity in attribute value
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

    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 113, Column 225: reference to entity "ad_text_color" for which no system identifier could be generated
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

    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 113, Column 211: entity was defined here
    …der_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=0080…
  • Warning Line 113, Column 233: cannot generate system identifier for general entity "ad_durl_color"
    …&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_o…

    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 113, Column 233: general entity "ad_durl_color" not defined and no default entity
    …&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_o…

    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 113, Column 246: reference not terminated by REFC delimiter
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

    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 113, Column 246: reference to external entity in attribute value
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

    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 113, Column 246: reference to entity "ad_durl_color" for which no system identifier could be generated
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

    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 113, Column 232: entity was defined here
    …=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_…
  • Warning Line 113, Column 254: cannot generate system identifier for general entity "adult"
    …ext_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idz…

    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 113, Column 254: general entity "adult" not defined and no default entity
    …ext_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idz…

    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 113, Column 259: reference not terminated by REFC delimiter
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=3…

    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 113, Column 259: reference to external entity in attribute value
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=3…

    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 113, Column 259: reference to entity "adult" for which no system identifier could be generated
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=3…

    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 113, Column 253: entity was defined here
    …text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&id…
  • Warning Line 113, Column 265: reference not terminated by REFC delimiter
    …00000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=301962&…

    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 113, Column 267: cannot generate system identifier for general entity "text_only"
    …000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=301962&id…

    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 113, Column 267: general entity "text_only" not defined and no default entity
    …000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=301962&id…

    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 113, Column 276: reference not terminated by REFC delimiter
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=301962&idsite=1329…

    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 113, Column 276: reference to external entity in attribute value
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=301962&idsite=1329…

    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 113, Column 276: reference to entity "text_only" for which no system identifier could be generated
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=301962&idsite=1329…

    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 113, Column 266: entity was defined here
    …0000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=301962&i…
  • Warning Line 113, Column 279: cannot generate system identifier for general entity "show_thumb"
    …color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=301962&idsite=132932"…

    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 113, Column 279: general entity "show_thumb" not defined and no default entity
    …color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=301962&idsite=132932"…

    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 113, Column 289: reference not terminated by REFC delimiter
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=301962&idsite=132932"></script>

    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 113, Column 289: reference to external entity in attribute value
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=301962&idsite=132932"></script>

    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 113, Column 289: reference to entity "show_thumb" for which no system identifier could be generated
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=301962&idsite=132932"></script>

    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 113, Column 278: entity was defined here
    …_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=301962&idsite=132932…
  • Warning Line 113, Column 297: reference not terminated by REFC delimiter
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=301962&idsite=132932"></script>

    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 113, Column 297: reference to external entity in attribute value
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=301962&idsite=132932"></script>

    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 113, Column 297: reference to entity "idzone" for which no system identifier could be generated
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=301962&idsite=132932"></script>

    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 35, Column 99: entity was defined here
    …ick.com/splash.php?cat=2&idsite=132932&idzone=301978&login=vporno_flatfee&type…
  • Warning Line 113, Column 311: reference not terminated by REFC delimiter
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=301962&idsite=132932"></script>

    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 113, Column 311: reference to external entity in attribute value
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=301962&idsite=132932"></script>

    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 113, Column 311: reference to entity "idsite" for which no system identifier could be generated
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=301962&idsite=132932"></script>

    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 35, Column 85: entity was defined here
    …dication.exoclick.com/splash.php?cat=2&idsite=132932&idzone=301978&login=vporn…
  • Warning Line 122, Column 96: reference not terminated by REFC delimiter
    …xoclick.com/ads.php?type=300x250&login=vporno_flatfee&cat=2&search=&ad_title_c…

    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 122, Column 96: reference to external entity in attribute value
    …xoclick.com/ads.php?type=300x250&login=vporno_flatfee&cat=2&search=&ad_title_c…

    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 122, Column 96: reference to entity "login" for which no system identifier could be generated
    …xoclick.com/ads.php?type=300x250&login=vporno_flatfee&cat=2&search=&ad_title_c…

    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 35, Column 113: entity was defined here
    …sh.php?cat=2&idsite=132932&idzone=301978&login=vporno_flatfee&type=3"></script>
  • Warning Line 122, Column 115: reference not terminated by REFC delimiter
    …?type=300x250&login=vporno_flatfee&cat=2&search=&ad_title_color=0000cc&bgcolor…

    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 122, Column 115: reference to external entity in attribute value
    …?type=300x250&login=vporno_flatfee&cat=2&search=&ad_title_color=0000cc&bgcolor…

    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 122, Column 115: reference to entity "cat" for which no system identifier could be generated
    …?type=300x250&login=vporno_flatfee&cat=2&search=&ad_title_color=0000cc&bgcolor…

    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 113, Column 109: entity was defined here
    …s.php?type=728x90&login=vporno_flatfee&cat=2&search=&ad_title_color=0000cc&bgc…
  • Warning Line 122, Column 124: reference not terminated by REFC delimiter
    …x250&login=vporno_flatfee&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&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 122, Column 124: reference to external entity in attribute value
    …x250&login=vporno_flatfee&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&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 122, Column 124: reference to entity "search" for which no system identifier could be generated
    …x250&login=vporno_flatfee&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&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 113, Column 115: entity was defined here
    …type=728x90&login=vporno_flatfee&cat=2&search=&ad_title_color=0000cc&bgcolor=F…
  • Warning Line 122, Column 140: reference not terminated by REFC delimiter
    …o_flatfee&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

    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 122, Column 140: reference to external entity in attribute value
    …o_flatfee&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

    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 122, Column 140: reference to entity "ad_title_color" for which no system identifier could be generated
    …o_flatfee&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

    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 113, Column 123: entity was defined here
    …x90&login=vporno_flatfee&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&bo…
  • Warning Line 122, Column 155: reference not terminated by REFC delimiter
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

    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 122, Column 155: reference to external entity in attribute value
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

    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 122, Column 155: reference to entity "bgcolor" for which no system identifier could be generated
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

    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 113, Column 145: entity was defined here
    …ee&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=00…
  • Warning Line 122, Column 169: reference not terminated by REFC delimiter
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

    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 122, Column 169: reference to external entity in attribute value
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

    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 122, Column 169: reference to entity "border" for which no system identifier could be generated
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

    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 113, Column 160: entity was defined here
    …=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&bloc…
  • Warning Line 122, Column 184: reference not terminated by REFC delimiter
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

    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 122, Column 184: reference to external entity in attribute value
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

    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 122, Column 184: reference to entity "border_color" for which no system identifier could be generated
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

    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 113, Column 169: entity was defined here
    …e_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keyword…
  • Warning Line 122, Column 196: reference not terminated by REFC delimiter
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&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 122, Column 196: reference to external entity in attribute value
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&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 122, Column 196: reference to entity "font" for which no system identifier could be generated
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&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 113, Column 189: entity was defined here
    …or=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000…
  • Warning Line 122, Column 212: reference not terminated by REFC delimiter
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

    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 122, Column 212: reference to external entity in attribute value
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

    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 122, Column 212: reference to entity "block_keywords" for which no system identifier could be generated
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

    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 113, Column 195: entity was defined here
    …FFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&ad…
  • Warning Line 122, Column 227: reference not terminated by REFC delimiter
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

    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 122, Column 227: reference to external entity in attribute value
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

    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 122, Column 227: reference to entity "ad_text_color" for which no system identifier could be generated
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

    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 113, Column 211: entity was defined here
    …der_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=0080…
  • Warning Line 122, Column 248: reference not terminated by REFC delimiter
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

    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 122, Column 248: reference to external entity in attribute value
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

    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 122, Column 248: reference to entity "ad_durl_color" for which no system identifier could be generated
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

    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 113, Column 232: entity was defined here
    …=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_…
  • Warning Line 122, Column 261: reference not terminated by REFC delimiter
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=3…

    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 122, Column 261: reference to external entity in attribute value
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=3…

    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 122, Column 261: reference to entity "adult" for which no system identifier could be generated
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=3…

    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 113, Column 253: entity was defined here
    …text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&id…
  • Warning Line 122, Column 267: reference not terminated by REFC delimiter
    …00000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=301964&…

    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 122, Column 278: reference not terminated by REFC delimiter
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=301964&idsite=1329…

    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 122, Column 278: reference to external entity in attribute value
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=301964&idsite=1329…

    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 122, Column 278: reference to entity "text_only" for which no system identifier could be generated
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=301964&idsite=1329…

    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 113, Column 266: entity was defined here
    …0000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=301962&i…
  • Warning Line 122, Column 291: reference not terminated by REFC delimiter
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=301964&idsite=132932"></script>

    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 122, Column 291: reference to external entity in attribute value
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=301964&idsite=132932"></script>

    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 122, Column 291: reference to entity "show_thumb" for which no system identifier could be generated
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=301964&idsite=132932"></script>

    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 113, Column 278: entity was defined here
    …_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=301962&idsite=132932…
  • Warning Line 122, Column 299: reference not terminated by REFC delimiter
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=301964&idsite=132932"></script>

    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 122, Column 299: reference to external entity in attribute value
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=301964&idsite=132932"></script>

    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 122, Column 299: reference to entity "idzone" for which no system identifier could be generated
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=301964&idsite=132932"></script>

    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 35, Column 99: entity was defined here
    …ick.com/splash.php?cat=2&idsite=132932&idzone=301978&login=vporno_flatfee&type…
  • Warning Line 122, Column 313: reference not terminated by REFC delimiter
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=301964&idsite=132932"></script>

    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 122, Column 313: reference to external entity in attribute value
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=301964&idsite=132932"></script>

    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 122, Column 313: reference to entity "idsite" for which no system identifier could be generated
    …000&adult=0&sub=&text_only=0&show_thumb=&idzone=301964&idsite=132932"></script>

    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 35, Column 85: entity was defined here
    …dication.exoclick.com/splash.php?cat=2&idsite=132932&idzone=301978&login=vporn…
  • Error Line 131, Column 61: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …end"><span class="bullet">*</span> <h3>DERNIERES VIDEOS PORNOS REGARDEES</h3><…

    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 136, Column 24: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
                    <ul id=videosViewed>
  • Error Line 139, Column 277: required attribute "alt" not specified
    …over="changeThumb(this,'start')" title="Tina Cherrie videuse de Couilles"> </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 139, Column 278: end tag for "img" omitted, but OMITTAG NO was specified
    …over="changeThumb(this,'start')" title="Tina Cherrie videuse de Couilles"> </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 139, Column 96: start tag was here
    …-de-couilles/" class="display-block"> <img class="thumb" src="http://tvp.vmedi…
  • Error Line 156, Column 329: required attribute "alt" not specified
    …start')" title="Coquinette la vieille sans limite en trio avec sa copine"> </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 156, Column 330: end tag for "img" omitted, but OMITTAG NO was specified
    …start')" title="Coquinette la vieille sans limite en trio avec sa copine"> </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 156, Column 122: start tag was here
    …ec-sa-copine/" class="display-block"> <img class="thumb" src="http://tvp.vmedi…
  • Warning Line 173, Column 269: character "&" is the first character of a delimiter but occurred as data
    …eThumb(this,'start')" title="Video fist & insertion de légumes et fruits"> </a>

    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 173, Column 302: required attribute "alt" not specified
    …eThumb(this,'start')" title="Video fist & insertion de légumes et fruits"> </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 173, Column 303: end tag for "img" omitted, but OMITTAG NO was specified
    …eThumb(this,'start')" title="Video fist & insertion de légumes et fruits"> </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 173, Column 107: start tag was here
    …es-et-fruits/" class="display-block"> <img class="thumb" src="http://tvp.vmedi…
  • Error Line 174, Column 16: ID "flag" already defined
         <span id="flag">video fr</span>     <h3 class="titleVideos"> <a href="http…

    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 157, Column 16: ID "flag" first defined here
         <span id="flag">video fr</span>     <h3 class="titleVideos"> <a href="http…
  • Warning Line 174, Column 158: character "&" is the first character of a delimiter but occurred as data
    …on-de-legumes-et-fruits/"> Video fist & insertion de légumes et fruits</a> </h…

    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 201, Column 14: ID "title_box_end" already defined
    			<span id="title_box_end">

    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 131, Column 13: ID "title_box_end" first defined here
    		<span id="title_box_end"><span class="bullet">*</span> <h3>DERNIERES VIDEOS P…
  • Error Line 202, Column 85: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ries" onclick="categories.click('open');" class="float-right"> Categories</div>

    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 203, Column 40: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
       			<span class="bullet">*</span> <h3> Vidéo porno récemment ajoutées</h3>

    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 207, Column 113: required attribute "action" not specified
    …part margin-bottom10 no-border-top"  onsubmit="return submitCategories(this);">

    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 210, Column 68: end tag for "input" omitted, but OMITTAG NO was specified
    …kbox" name="category" value="amateur"> <a id="link_category_amateur" href="htt…

    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 210, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="amateur"> <a id="link…
  • Error Line 211, Column 70: end tag for "input" omitted, but OMITTAG NO was specified
    …ox" name="category" value="asiatique"> <a id="link_category_asiatique" href="h…

    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 211, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="asiatique"> <a id="li…
  • Error Line 212, Column 75: end tag for "input" omitted, but OMITTAG NO was specified
    …ame="category" value="baise-ma-femme"> <a id="link_category_baise-ma-femme" hr…

    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 212, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="baise-ma-femme"> <a i…
  • Error Line 213, Column 69: end tag for "input" omitted, but OMITTAG NO was specified
    …box" name="category" value="beurette"> <a id="link_category_beurette" href="ht…

    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 213, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="beurette"> <a id="lin…
  • Error Line 214, Column 66: end tag for "input" omitted, but OMITTAG NO was specified
    …eckbox" name="category" value="bimbo"> <a id="link_category_bimbo" href="http:…

    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 214, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="bimbo"> <a id="link_c…
  • Error Line 215, Column 69: end tag for "input" omitted, but OMITTAG NO was specified
    …box" name="category" value="bisexuel"> <a id="link_category_bisexuel" href="ht…

    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 215, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="bisexuel"> <a id="lin…
  • Error Line 216, Column 66: end tag for "input" omitted, but OMITTAG NO was specified
    …eckbox" name="category" value="black"> <a id="link_category_black" href="http:…

    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 216, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="black"> <a id="link_c…
  • Error Line 219, Column 68: end tag for "input" omitted, but OMITTAG NO was specified
    …kbox" name="category" value="bondage"> <a id="link_category_bondage" href="htt…

    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 219, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="bondage"> <a id="link…
  • Error Line 220, Column 68: end tag for "input" omitted, but OMITTAG NO was specified
    …kbox" name="category" value="casting"> <a id="link_category_casting" href="htt…

    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 220, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="casting"> <a id="link…
  • Error Line 221, Column 74: end tag for "input" omitted, but OMITTAG NO was specified
    …name="category" value="chatte-poilue"> <a id="link_category_chatte-poilue" hre…

    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 221, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="chatte-poilue"> <a id…
  • Error Line 222, Column 79: end tag for "input" omitted, but OMITTAG NO was specified
    …"category" value="double-penetration"> <a id="link_category_double-penetration…

    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 222, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="double-penetration"> …
  • Error Line 223, Column 77: end tag for "input" omitted, but OMITTAG NO was specified
    …e="category" value="douche-de-sperme"> <a id="link_category_douche-de-sperme" …

    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 223, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="douche-de-sperme"> <a…
  • Error Line 224, Column 80: end tag for "input" omitted, but OMITTAG NO was specified
    …category" value="ejaculation-buccale"> <a id="link_category_ejaculation-buccal…

    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 224, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="ejaculation-buccale">…
  • Error Line 225, Column 80: end tag for "input" omitted, but OMITTAG NO was specified
    …category" value="ejaculation-faciale"> <a id="link_category_ejaculation-facial…

    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 225, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="ejaculation-faciale">…
  • Error Line 228, Column 81: end tag for "input" omitted, but OMITTAG NO was specified
    …ategory" value="ejaculation-feminine"> <a id="link_category_ejaculation-femini…

    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 228, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="ejaculation-feminine"…
  • Error Line 229, Column 70: end tag for "input" omitted, but OMITTAG NO was specified
    …ox" name="category" value="etudiante"> <a id="link_category_etudiante" href="h…

    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 229, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="etudiante"> <a id="li…
  • Error Line 230, Column 71: end tag for "input" omitted, but OMITTAG NO was specified
    …x" name="category" value="exhibition"> <a id="link_category_exhibition" href="…

    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 230, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="exhibition"> <a id="l…
  • Error Line 231, Column 70: end tag for "input" omitted, but OMITTAG NO was specified
    …ox" name="category" value="exterieur"> <a id="link_category_exterieur" href="h…

    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 231, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="exterieur"> <a id="li…
  • Error Line 232, Column 71: end tag for "input" omitted, but OMITTAG NO was specified
    …x" name="category" value="femme-mure"> <a id="link_category_femme-mure" href="…

    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 232, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="femme-mure"> <a id="l…
  • Error Line 233, Column 68: end tag for "input" omitted, but OMITTAG NO was specified
    …kbox" name="category" value="fetiche"> <a id="link_category_fetiche" href="htt…

    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 233, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="fetiche"> <a id="link…
  • Error Line 234, Column 76: end tag for "input" omitted, but OMITTAG NO was specified
    …me="category" value="fille-enculeuse"> <a id="link_category_fille-enculeuse" h…

    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 234, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="fille-enculeuse"> <a …
  • Error Line 237, Column 65: end tag for "input" omitted, but OMITTAG NO was specified
    …heckbox" name="category" value="fist"> <a id="link_category_fist" href="http:/…

    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 237, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="fist"> <a id="link_ca…
  • Error Line 238, Column 70: end tag for "input" omitted, but OMITTAG NO was specified
    …ox" name="category" value="francaise"> <a id="link_category_francaise" href="h…

    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 238, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="francaise"> <a id="li…
  • Error Line 239, Column 70: end tag for "input" omitted, but OMITTAG NO was specified
    …ox" name="category" value="gang-bang"> <a id="link_category_gang-bang" href="h…

    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 239, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="gang-bang"> <a id="li…
  • Error Line 240, Column 66: end tag for "input" omitted, but OMITTAG NO was specified
    …eckbox" name="category" value="gonzo"> <a id="link_category_gonzo" href="http:…

    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 240, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="gonzo"> <a id="link_c…
  • Error Line 241, Column 75: end tag for "input" omitted, but OMITTAG NO was specified
    …ame="category" value="gorge-profonde"> <a id="link_category_gorge-profonde" hr…

    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 241, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="gorge-profonde"> <a i…
  • Error Line 242, Column 75: end tag for "input" omitted, but OMITTAG NO was specified
    …ame="category" value="grassouillette"> <a id="link_category_grassouillette" hr…

    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 242, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="grassouillette"> <a i…
  • Error Line 243, Column 71: end tag for "input" omitted, but OMITTAG NO was specified
    …x" name="category" value="gros-seins"> <a id="link_category_gros-seins" href="…

    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 243, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="gros-seins"> <a id="l…
  • Error Line 246, Column 67: end tag for "input" omitted, but OMITTAG NO was specified
    …ckbox" name="category" value="grosse"> <a id="link_category_grosse" href="http…

    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 246, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="grosse"> <a id="link_…
  • Error Line 247, Column 72: end tag for "input" omitted, but OMITTAG NO was specified
    …" name="category" value="grosse-bite"> <a id="link_category_grosse-bite" href=…

    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 247, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="grosse-bite"> <a id="…
  • Error Line 248, Column 71: end tag for "input" omitted, but OMITTAG NO was specified
    …x" name="category" value="infirmiere"> <a id="link_category_infirmiere" href="…

    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 248, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="infirmiere"> <a id="l…
  • Error Line 249, Column 66: end tag for "input" omitted, but OMITTAG NO was specified
    …eckbox" name="category" value="jeune"> <a id="link_category_jeune" href="http:…

    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 249, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="jeune"> <a id="link_c…
  • Error Line 250, Column 69: end tag for "input" omitted, but OMITTAG NO was specified
    …box" name="category" value="joli-cul"> <a id="link_category_joli-cul" href="ht…

    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 250, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="joli-cul"> <a id="lin…
  • Error Line 251, Column 72: end tag for "input" omitted, but OMITTAG NO was specified
    …" name="category" value="jolie-fille"> <a id="link_category_jolie-fille" href=…

    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 251, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="jolie-fille"> <a id="…
  • Error Line 252, Column 67: end tag for "input" omitted, but OMITTAG NO was specified
    …ckbox" name="category" value="latine"> <a id="link_category_latine" href="http…

    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 252, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="latine"> <a id="link_…
  • Error Line 255, Column 70: end tag for "input" omitted, but OMITTAG NO was specified
    …ox" name="category" value="lesbienne"> <a id="link_category_lesbienne" href="h…

    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 255, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="lesbienne"> <a id="li…
  • Error Line 256, Column 69: end tag for "input" omitted, but OMITTAG NO was specified
    …box" name="category" value="partouze"> <a id="link_category_partouze" href="ht…

    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 256, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="partouze"> <a id="lin…
  • Error Line 257, Column 72: end tag for "input" omitted, but OMITTAG NO was specified
    …" name="category" value="petit-seins"> <a id="link_category_petit-seins" href=…

    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 257, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="petit-seins"> <a id="…
  • Error Line 258, Column 70: end tag for "input" omitted, but OMITTAG NO was specified
    …ox" name="category" value="sado-maso"> <a id="link_category_sado-maso" href="h…

    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 258, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="sado-maso"> <a id="li…
  • Error Line 259, Column 71: end tag for "input" omitted, but OMITTAG NO was specified
    …x" name="category" value="secretaire"> <a id="link_category_secretaire" href="…

    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 259, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="secretaire"> <a id="l…
  • Error Line 260, Column 69: end tag for "input" omitted, but OMITTAG NO was specified
    …box" name="category" value="sex-toys"> <a id="link_category_sex-toys" href="ht…

    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 260, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="sex-toys"> <a id="lin…
  • Error Line 261, Column 68: end tag for "input" omitted, but OMITTAG NO was specified
    …kbox" name="category" value="sodomie"> <a id="link_category_sodomie" href="htt…

    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 261, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="sodomie"> <a id="link…
  • Error Line 264, Column 77: end tag for "input" omitted, but OMITTAG NO was specified
    …e="category" value="soiree-etudiante"> <a id="link_category_soiree-etudiante" …

    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 264, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="soiree-etudiante"> <a…
  • Error Line 265, Column 70: end tag for "input" omitted, but OMITTAG NO was specified
    …ox" name="category" value="star-du-x"> <a id="link_category_star-du-x" href="h…

    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 265, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="star-du-x"> <a id="li…
  • Error Line 266, Column 72: end tag for "input" omitted, but OMITTAG NO was specified
    …" name="category" value="transsexuel"> <a id="link_category_transsexuel" href=…

    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 266, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="transsexuel"> <a id="…
  • Error Line 267, Column 68: end tag for "input" omitted, but OMITTAG NO was specified
    …kbox" name="category" value="vieille"> <a id="link_category_vieille" href="htt…

    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 267, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="vieille"> <a id="link…
  • Error Line 268, Column 80: end tag for "input" omitted, but OMITTAG NO was specified
    …category" value="vieille-avec-jeunot"> <a id="link_category_vieille-avec-jeuno…

    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 268, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="vieille-avec-jeunot">…
  • Error Line 269, Column 80: end tag for "input" omitted, but OMITTAG NO was specified
    …category" value="vieux-avec-jeunette"> <a id="link_category_vieux-avec-jeunett…

    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 269, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="vieux-avec-jeunette">…
  • Error Line 270, Column 67: end tag for "input" omitted, but OMITTAG NO was specified
    …ckbox" name="category" value="voyeur"> <a id="link_category_voyeur" href="http…

    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 270, Column 13: start tag was here
    								<li><input type="checkbox" name="category" value="voyeur"> <a id="link_…
  • Warning Line 302, Column 269: character "&" is the first character of a delimiter but occurred as data
    …eThumb(this,'start')" title="Video fist & insertion de légumes et fruits"> </a>

    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 302, Column 302: required attribute "alt" not specified
    …eThumb(this,'start')" title="Video fist & insertion de légumes et fruits"> </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 302, Column 303: end tag for "img" omitted, but OMITTAG NO was specified
    …eThumb(this,'start')" title="Video fist & insertion de légumes et fruits"> </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 302, Column 107: start tag was here
    …es-et-fruits/" class="display-block"> <img class="thumb" src="http://tvp.vmedi…
  • Error Line 303, Column 16: ID "flag" already defined
         <span id="flag">video fr</span>     <h3 class="titleVideos"> <a href="http…

    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 157, Column 16: ID "flag" first defined here
         <span id="flag">video fr</span>     <h3 class="titleVideos"> <a href="http…
  • Warning Line 303, Column 158: character "&" is the first character of a delimiter but occurred as data
    …on-de-legumes-et-fruits/"> Video fist & insertion de légumes et fruits</a> </h…

    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 320, Column 259: required attribute "alt" not specified
    …)" onmouseover="changeThumb(this,'start')" title="2 Stars du X à la fois"> </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 320, Column 260: end tag for "img" omitted, but OMITTAG NO was specified
    …)" onmouseover="changeThumb(this,'start')" title="2 Stars du X à la fois"> </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 320, Column 87: start tag was here
    …-x-a-la-fois/" class="display-block"> <img class="thumb" src="http://tvp.vmedi…
  • Error Line 338, Column 273: required attribute "alt" not specified
    …ouseover="changeThumb(this,'start')" title="Porno années 90 avec Magella"> </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 338, Column 274: end tag for "img" omitted, but OMITTAG NO was specified
    …ouseover="changeThumb(this,'start')" title="Porno années 90 avec Magella"> </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 338, Column 94: start tag was here
    …avec-magella/" class="display-block"> <img class="thumb" src="http://tvp.vmedi…
  • Error Line 339, Column 16: ID "flag" already defined
         <span id="flag">video fr</span>     <h3 class="titleVideos"> <a href="http…

    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 157, Column 16: ID "flag" first defined here
         <span id="flag">video fr</span>     <h3 class="titleVideos"> <a href="http…
  • Error Line 356, Column 255: required attribute "alt" not specified
    …p')" onmouseover="changeThumb(this,'start')" title="Ejacule dans mon Cul"> </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 356, Column 256: end tag for "img" omitted, but OMITTAG NO was specified
    …p')" onmouseover="changeThumb(this,'start')" title="Ejacule dans mon Cul"> </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 356, Column 85: start tag was here
    …dans-mon-cul/" class="display-block"> <img class="thumb" src="http://tvp.vmedi…
  • Error Line 374, Column 258: required attribute "alt" not specified
    …p')" onmouseover="changeThumb(this,'start')" title="Encule moi mon chéri"> </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 374, Column 259: end tag for "img" omitted, but OMITTAG NO was specified
    …p')" onmouseover="changeThumb(this,'start')" title="Encule moi mon chéri"> </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 374, Column 86: start tag was here
    …oi-mon-cheri/" class="display-block"> <img class="thumb" src="http://tvp.vmedi…
  • Error Line 375, Column 16: ID "flag" already defined
         <span id="flag">video fr</span>     <h3 class="titleVideos"> <a href="http…

    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 157, Column 16: ID "flag" first defined here
         <span id="flag">video fr</span>     <h3 class="titleVideos"> <a href="http…
  • Error Line 392, Column 278: required attribute "alt" not specified
    …eover="changeThumb(this,'start')" title="Spécial je jouis dans ta chatte"> </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 392, Column 279: end tag for "img" omitted, but OMITTAG NO was specified
    …eover="changeThumb(this,'start')" title="Spécial je jouis dans ta chatte"> </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 392, Column 96: start tag was here
    …ns-ta-chatte/" class="display-block"> <img class="thumb" src="http://tvp.vmedi…
  • Error Line 410, Column 261: required attribute "alt" not specified
    …)" onmouseover="changeThumb(this,'start')" title="Secrétaire se déchaine"> </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 410, Column 262: end tag for "img" omitted, but OMITTAG NO was specified
    …)" onmouseover="changeThumb(this,'start')" title="Secrétaire se déchaine"> </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 410, Column 88: start tag was here
    …-se-dechaine/" class="display-block"> <img class="thumb" src="http://tvp.vmedi…
  • Error Line 411, Column 16: ID "flag" already defined
         <span id="flag">video fr</span>     <h3 class="titleVideos"> <a href="http…

    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 157, Column 16: ID "flag" first defined here
         <span id="flag">video fr</span>     <h3 class="titleVideos"> <a href="http…
  • Error Line 428, Column 281: required attribute "alt" not specified
    …ver="changeThumb(this,'start')" title="Double pénétration dans le jardin"> </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 428, Column 282: end tag for "img" omitted, but OMITTAG NO was specified
    …ver="changeThumb(this,'start')" title="Double pénétration dans le jardin"> </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 428, Column 98: start tag was here
    …ns-le-jardin/" class="display-block"> <img class="thumb" src="http://tvp.vmedi…
  • Error Line 446, Column 257: required attribute "alt" not specified
    …p')" onmouseover="changeThumb(this,'start')" title="Beurette bien chaude"> </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 446, Column 258: end tag for "img" omitted, but OMITTAG NO was specified
    …p')" onmouseover="changeThumb(this,'start')" title="Beurette bien chaude"> </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 446, Column 86: start tag was here
    …-bien-chaude/" class="display-block"> <img class="thumb" src="http://tvp.vmedi…
  • Error Line 447, Column 16: ID "flag" already defined
         <span id="flag">video fr</span>     <h3 class="titleVideos"> <a href="http…

    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 157, Column 16: ID "flag" first defined here
         <span id="flag">video fr</span>     <h3 class="titleVideos"> <a href="http…
  • Error Line 464, Column 263: required attribute "alt" not specified
    … onmouseover="changeThumb(this,'start')" title="18ans et grosse cochonne"> </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 464, Column 264: end tag for "img" omitted, but OMITTAG NO was specified
    … onmouseover="changeThumb(this,'start')" title="18ans et grosse cochonne"> </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 464, Column 89: start tag was here
    …sse-cochonne/" class="display-block"> <img class="thumb" src="http://tvp.vmedi…
  • Error Line 482, Column 272: required attribute "alt" not specified
    …mouseover="changeThumb(this,'start')" title="Video amateur d'une vieille"> </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 482, Column 273: end tag for "img" omitted, but OMITTAG NO was specified
    …mouseover="changeThumb(this,'start')" title="Video amateur d'une vieille"> </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 482, Column 93: start tag was here
    …-une-vieille/" class="display-block"> <img class="thumb" src="http://tvp.vmedi…
  • Error Line 483, Column 16: ID "flag" already defined
         <span id="flag">video fr</span>     <h3 class="titleVideos"> <a href="http…

    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 157, Column 16: ID "flag" first defined here
         <span id="flag">video fr</span>     <h3 class="titleVideos"> <a href="http…
  • Error Line 500, Column 269: required attribute "alt" not specified
    …ouseover="changeThumb(this,'start')" title="Maman aimle fromage blanc..."> </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 500, Column 270: end tag for "img" omitted, but OMITTAG NO was specified
    …ouseover="changeThumb(this,'start')" title="Maman aimle fromage blanc..."> </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 500, Column 90: start tag was here
    …romage-blanc/" class="display-block"> <img class="thumb" src="http://tvp.vmedi…
  • Error Line 518, Column 259: required attribute "alt" not specified
    …')" onmouseover="changeThumb(this,'start')" title="Lesbienne de grenoble"> </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 518, Column 260: end tag for "img" omitted, but OMITTAG NO was specified
    …')" onmouseover="changeThumb(this,'start')" title="Lesbienne de grenoble"> </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 518, Column 87: start tag was here
    …-de-grenoble/" class="display-block"> <img class="thumb" src="http://tvp.vmedi…
  • Error Line 519, Column 16: ID "flag" already defined
         <span id="flag">video fr</span>     <h3 class="titleVideos"> <a href="http…

    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 157, Column 16: ID "flag" first defined here
         <span id="flag">video fr</span>     <h3 class="titleVideos"> <a href="http…
  • Error Line 536, Column 262: required attribute "alt" not specified
    …" onmouseover="changeThumb(this,'start')" title="Jeune Bombe Brésilienne"> </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 536, Column 263: end tag for "img" omitted, but OMITTAG NO was specified
    …" onmouseover="changeThumb(this,'start')" title="Jeune Bombe Brésilienne"> </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 536, Column 88: start tag was here
    …-bresilienne/" class="display-block"> <img class="thumb" src="http://tvp.vmedi…
  • Error Line 554, Column 273: required attribute "alt" not specified
    …ouseover="changeThumb(this,'start')" title="2 matures de metz partouzent"> </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 554, Column 274: end tag for "img" omitted, but OMITTAG NO was specified
    …ouseover="changeThumb(this,'start')" title="2 matures de metz partouzent"> </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 554, Column 94: start tag was here
    …z-partouzent/" class="display-block"> <img class="thumb" src="http://tvp.vmedi…
  • Error Line 555, Column 16: ID "flag" already defined
         <span id="flag">video fr</span>     <h3 class="titleVideos"> <a href="http…

    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 157, Column 16: ID "flag" first defined here
         <span id="flag">video fr</span>     <h3 class="titleVideos"> <a href="http…
  • Error Line 572, Column 283: required attribute "alt" not specified
    …er="changeThumb(this,'start')" title="Grosse Vache Roulée dans la farine"> </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 572, Column 284: end tag for "img" omitted, but OMITTAG NO was specified
    …er="changeThumb(this,'start')" title="Grosse Vache Roulée dans la farine"> </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 572, Column 99: start tag was here
    …ns-la-farine/" class="display-block"> <img class="thumb" src="http://tvp.vmedi…
  • Error Line 590, Column 258: required attribute "alt" not specified
    …p')" onmouseover="changeThumb(this,'start')" title="Bouffeuses de queues"> </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 590, Column 259: end tag for "img" omitted, but OMITTAG NO was specified
    …p')" onmouseover="changeThumb(this,'start')" title="Bouffeuses de queues"> </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 590, Column 86: start tag was here
    …es-de-queues/" class="display-block"> <img class="thumb" src="http://tvp.vmedi…
  • Error Line 591, Column 16: ID "flag" already defined
         <span id="flag">video fr</span>     <h3 class="titleVideos"> <a href="http…

    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 157, Column 16: ID "flag" first defined here
         <span id="flag">video fr</span>     <h3 class="titleVideos"> <a href="http…
  • Error Line 608, Column 265: required attribute "alt" not specified
    …onmouseover="changeThumb(this,'start')" title="Tory Lane et Angela Stone"> </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 608, Column 266: end tag for "img" omitted, but OMITTAG NO was specified
    …onmouseover="changeThumb(this,'start')" title="Tory Lane et Angela Stone"> </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 608, Column 90: start tag was here
    …angela-stone/" class="display-block"> <img class="thumb" src="http://tvp.vmedi…
  • Error Line 626, Column 291: required attribute "alt" not specified
    …"changeThumb(this,'start')" title="Mature baisée par huissier de justice"> </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 626, Column 292: end tag for "img" omitted, but OMITTAG NO was specified
    …"changeThumb(this,'start')" title="Mature baisée par huissier de justice"> </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 626, Column 103: start tag was here
    …r-de-justice/" class="display-block"> <img class="thumb" src="http://tvp.vmedi…
  • Error Line 627, Column 16: ID "flag" already defined
         <span id="flag">video fr</span>     <h3 class="titleVideos"> <a href="http…

    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 157, Column 16: ID "flag" first defined here
         <span id="flag">video fr</span>     <h3 class="titleVideos"> <a href="http…
  • Error Line 644, Column 283: required attribute "alt" not specified
    …="changeThumb(this,'start')" title="Blondasse bourrée dans tout les sens"> </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 644, Column 284: end tag for "img" omitted, but OMITTAG NO was specified
    …="changeThumb(this,'start')" title="Blondasse bourrée dans tout les sens"> </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 644, Column 99: start tag was here
    …out-les-sens/" class="display-block"> <img class="thumb" src="http://tvp.vmedi…
  • Error Line 662, Column 266: required attribute "alt" not specified
    …onmouseover="changeThumb(this,'start')" title="Tu veux baiser ma femme ?"> </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 662, Column 267: end tag for "img" omitted, but OMITTAG NO was specified
    …onmouseover="changeThumb(this,'start')" title="Tu veux baiser ma femme ?"> </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 662, Column 90: start tag was here
    …er-ma-femme-/" class="display-block"> <img class="thumb" src="http://tvp.vmedi…
  • Error Line 663, Column 16: ID "flag" already defined
         <span id="flag">video fr</span>     <h3 class="titleVideos"> <a href="http…

    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 157, Column 16: ID "flag" first defined here
         <span id="flag">video fr</span>     <h3 class="titleVideos"> <a href="http…
  • Error Line 680, Column 272: required attribute "alt" not specified
    …useover="changeThumb(this,'start')" title="Keri Sable immaculée de sperm"> </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 680, Column 273: end tag for "img" omitted, but OMITTAG NO was specified
    …useover="changeThumb(this,'start')" title="Keri Sable immaculée de sperm"> </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 680, Column 93: start tag was here
    …lee-de-sperm/" class="display-block"> <img class="thumb" src="http://tvp.vmedi…
  • Error Line 698, Column 274: required attribute "alt" not specified
    …useover="changeThumb(this,'start')" title="Video amateur: Melanie 20 ans"> </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 698, Column 275: end tag for "img" omitted, but OMITTAG NO was specified
    …useover="changeThumb(this,'start')" title="Video amateur: Melanie 20 ans"> </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 698, Column 94: start tag was here
    …lanie-20-ans/" class="display-block"> <img class="thumb" src="http://tvp.vmedi…
  • Error Line 699, Column 16: ID "flag" already defined
         <span id="flag">video fr</span>     <h3 class="titleVideos"> <a href="http…

    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 157, Column 16: ID "flag" first defined here
         <span id="flag">video fr</span>     <h3 class="titleVideos"> <a href="http…
  • Error Line 716, Column 264: required attribute "alt" not specified
    … onmouseover="changeThumb(this,'start')" title="Belle Brésilienne baisée"> </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 716, Column 265: end tag for "img" omitted, but OMITTAG NO was specified
    … onmouseover="changeThumb(this,'start')" title="Belle Brésilienne baisée"> </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 716, Column 89: start tag was here
    …ienne-baisee/" class="display-block"> <img class="thumb" src="http://tvp.vmedi…
  • Error Line 734, Column 265: required attribute "alt" not specified
    …onmouseover="changeThumb(this,'start')" title="Casting X : sa 1ère video"> </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 734, Column 266: end tag for "img" omitted, but OMITTAG NO was specified
    …onmouseover="changeThumb(this,'start')" title="Casting X : sa 1ère video"> </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 734, Column 89: start tag was here
    …a-1ere-video/" class="display-block"> <img class="thumb" src="http://tvp.vmedi…
  • Error Line 735, Column 16: ID "flag" already defined
         <span id="flag">video fr</span>     <h3 class="titleVideos"> <a href="http…

    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 157, Column 16: ID "flag" first defined here
         <span id="flag">video fr</span>     <h3 class="titleVideos"> <a href="http…
  • Error Line 778, Column 6: end tag for element "div" which is not open
    </div>

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

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

  • Warning Line 806, Column 92: reference not terminated by REFC delimiter
    …n.exoclick.com/splash.php?cat=2&idsite=132932&idzone=301984&login=vporno_flatf…

    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 806, Column 92: reference to external entity in attribute value
    …n.exoclick.com/splash.php?cat=2&idsite=132932&idzone=301984&login=vporno_flatf…

    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 806, Column 92: reference to entity "idsite" for which no system identifier could be generated
    …n.exoclick.com/splash.php?cat=2&idsite=132932&idzone=301984&login=vporno_flatf…

    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 35, Column 85: entity was defined here
    …dication.exoclick.com/splash.php?cat=2&idsite=132932&idzone=301978&login=vporn…
  • Warning Line 806, Column 106: reference not terminated by REFC delimiter
    …/splash.php?cat=2&idsite=132932&idzone=301984&login=vporno_flatfee&type=4"></s…

    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 806, Column 106: reference to external entity in attribute value
    …/splash.php?cat=2&idsite=132932&idzone=301984&login=vporno_flatfee&type=4"></s…

    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 806, Column 106: reference to entity "idzone" for which no system identifier could be generated
    …/splash.php?cat=2&idsite=132932&idzone=301984&login=vporno_flatfee&type=4"></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.

  • Info Line 35, Column 99: entity was defined here
    …ick.com/splash.php?cat=2&idsite=132932&idzone=301978&login=vporno_flatfee&type…
  • Warning Line 806, Column 119: reference not terminated by REFC delimiter
    …h.php?cat=2&idsite=132932&idzone=301984&login=vporno_flatfee&type=4"></script> 

    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 806, Column 119: reference to external entity in attribute value
    …h.php?cat=2&idsite=132932&idzone=301984&login=vporno_flatfee&type=4"></script> 

    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 806, Column 119: reference to entity "login" for which no system identifier could be generated
    …h.php?cat=2&idsite=132932&idzone=301984&login=vporno_flatfee&type=4"></script> 

    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 35, Column 113: entity was defined here
    …sh.php?cat=2&idsite=132932&idzone=301978&login=vporno_flatfee&type=3"></script>
  • Warning Line 806, Column 139: reference not terminated by REFC delimiter
    …h.php?cat=2&idsite=132932&idzone=301984&login=vporno_flatfee&type=4"></script> 

    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 806, Column 139: reference to external entity in attribute value
    …h.php?cat=2&idsite=132932&idzone=301984&login=vporno_flatfee&type=4"></script> 

    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 806, Column 139: reference to entity "type" for which no system identifier could be generated
    …h.php?cat=2&idsite=132932&idzone=301984&login=vporno_flatfee&type=4"></script> 

    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 35, Column 134: entity was defined here
    …sh.php?cat=2&idsite=132932&idzone=301978&login=vporno_flatfee&type=3"></script>

Visitor Analysis

Daily Visitor
  • 12.600 visits