Sex Oasis has free long tube videos of the hottest pornstars and amateurs. 1000s of videos & pics to watch. 100% free high quality sex movies. ...

sexoasis.com
  • Domain Name
    sexoasis.com
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #43942
  • Page Size
    165.4 KB
  • Ip Address
    216.18.190.104
  • Heading
    H1: 1, H2: 120, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 120 JPG, 1 PNG

Website Meta Analysis

  • Title
    Sex Oasis - Free Sex Videos, Good Porn, Sex Movies Tube & XXX Pics
  • Meta Keyword
    sex, free sex, free sex videos, sex videos, sex movies, sex movie, sex tube, porn sex, sex porno, sexy videos, sex pics
  • Meta Description
    Sex Oasis has free long tube videos of the hottest pornstars and amateurs. 1000s of videos & pics to watch. 100% free high quality sex movies.

Technical Analysis

  • Webserver
    nginx
  • Ip Address
    216.18.190.104
  • Domain Age
    11 Years, 2 Months, 23 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx
  • date: Wed, 07 Aug 2013 03:00:21 GMT
  • content-type: text/html
  • connection: close
  • x-powered-by: PHP/5.2.17
  • 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
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: SEXOASIS.COM
Registrar: MONIKER

Registrant [3804842]:
Moniker Privacy Services email
Moniker Privacy Services
1800 SW 1st Avenue
Suite 440
Portland
OR
97201
US


Administrative Contact [3804842]:
Moniker Privacy Services email
Moniker Privacy Services
1800 SW 1st Avenue
Suite 440
Portland
OR
97201
US
Phone: +1.5032070147
Fax: +1.9545859186


Billing Contact [3804842]:
Moniker Privacy Services email
Moniker Privacy Services
1800 SW 1st Avenue
Suite 440
Portland
OR
97201
US
Phone: +1.5032070147
Fax: +1.9545859186


Technical Contact [3804842]:
Moniker Privacy Services email
Moniker Privacy Services
1800 SW 1st Avenue
Suite 440
Portland
OR
97201
US
Phone: +1.5032070147
Fax: +1.9545859186


Domain servers in listed order:

NS0.REFLECTED.NET
NS1.REFLECTED.NET

Record created on: 2002-05-13 14:29:42.0
Database last updated on: 2012-03-08 20:18:36.963
Domain Expires on: 2015-05-13 14:29:42.0

DNS Analysis


DNS servers
ns0.reflected.net [66.254.126.2]
ns1.reflected.net [66.254.127.2]


DNS Records

Answer records
sexoasis.com A 216.18.190.104 3600s
sexoasis.com SOA
server: ns0.reflected.net
email: noc@reflected.net
serial: 2012061300
refresh: 10800
retry: 900
expire: 604800
minimum ttl: 86400
3600s
sexoasis.com NS  ns0.reflected.net 3600s
sexoasis.com NS  ns1.reflected.net 3600s

Authority records

Additional records
ns0.reflected.net A 66.254.126.2 3600s
ns1.reflected.net A 66.254.127.2 3600s

IP 216.18.190.104 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Waltham
  • Continent Code
    02451
  • Latitude
    781
  • Longitude
    506
  • %rwhois V-1.5:002080:00 rwhois.reflected.net (Reflected::RWhoisD 0.0.2)
    network:Class-Name:network
    network:Auth-Area:216.18.190.104/30
    network:ID:NET-216-18-190-104-2959
    network:Handle:NET-216-18-190-104-2959
    network:IP-Network:216.18.190.104/30
    network:IP-Network-Block:216.18.190.104 - 216.18.190.107
    network:Name:Titan Websites, Inc.
    network:Street-Address:2540 (OR 2450?) Westlake Ave N. #B
    network:City:Seattle
    network:State:WA
    network:Country-Code:US
    network:Tech-Email:lisajams@gmail.com
    network:Tech-Phone:206-235-4298
    network:Abuse-Email:lisajams@gmail.com
    network:Abuse-Phone:206-235-4298
    network:Created:20100401
    network:Updated:20100401

    %ok

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 49 Errors
  • 2 Warnings
Ratio Text/Html
  • 0.8036127645502645
Message Error
  • Warning Line 33, Column 64: character "&" is the first character of a delimiter but occurred as data
    …itle>Sex Oasis - Free Sex Videos, Good Porn, Sex Movies Tube & XXX Pics</title>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 36, Column 126: character "&" is the first character of a delimiter but occurred as data
    …rnstars and amateurs. 1000s of videos & pics to watch.  100% free high quality…

    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 96, Column 8: required attribute "type" not specified
    <script>

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

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

  • Error Line 268, Column 52: document type does not allow element "span" here; assuming missing "li" start-tag
    …yle="float: right; margin-right: 15px">Switch To: <a href="http://www.sexoasis…
  • Error Line 269, Column 9: end tag for "li" omitted, but OMITTAG NO was specified
    				</ul>

    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 6: start tag was here
    					<span style="float: right; margin-right: 15px">Switch To: <a href="http://…
  • Error Line 361, Column 466: value of attribute "id" invalid: "5" cannot start a name
    …able unbelievable wow threesome"  id="5XrW9rOw2Vl" title="unbelievable unbelie…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 379, Column 528: value of attribute "id" invalid: "3" cannot start a name
    …es a great body to body massage"  id="3sVgbqH71lN" title="Sexy blonde pornstar…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 433, Column 498: value of attribute "id" invalid: "3" cannot start a name
    … hard by her massage therapist."  id="3wIVMyQXVcQ" title="Elaina seduced and f…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 487, Column 524: value of attribute "id" invalid: "4" cannot start a name
    …st time anal sex with huge cock"  id="40jt4pjs8kn" title="Massive boobs hottie…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 541, Column 544: value of attribute "id" invalid: "8" cannot start a name
    …d by two horny guys by OnePondo"  id="8kEgefX5n2M" title="Tiny Japanese idol b…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 613, Column 472: value of attribute "id" invalid: "5" cannot start a name
    …casting tape showing nasty babe"  id="5JfQwfJmGcO" title="Uncensored casting t…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 685, Column 500: value of attribute "id" invalid: "0" cannot start a name
    …Riley Steele glamourise fucking"  id="0R3QtakPMZk" title="Big tits blonde porn…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 793, Column 462: value of attribute "id" invalid: "1" cannot start a name
    …t penis for this amazing blonde"  id="1EsgHmjFm2X" title="Perfect penis for th…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 847, Column 462: value of attribute "id" invalid: "5" cannot start a name
    …blonde glamour banged in prison"  id="5vStlv68Vqc" title="Busty blonde glamour…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 1063, Column 524: value of attribute "id" invalid: "0" cannot start a name
    …asian friend's cock by OnePondo"  id="0icMHlk4NRz" title="Dirty asian babe suc…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 1099, Column 462: value of attribute "id" invalid: "8" cannot start a name
    …g cock into her hairy anal cunt"  id="8pdjZooQfPs" title="Too big cock into he…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 1117, Column 466: value of attribute "id" invalid: "8" cannot start a name
    … Babe Molly Spreading Her Pussy"  id="8cVfZoKzy51" title="Pregnant Babe Molly …

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 1279, Column 454: value of attribute "id" invalid: "8" cannot start a name
    …eve Gives Himself a Finger Fuck"  id="8EGbIT1vM8o" title="Steve Gives Himself …

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 1351, Column 466: value of attribute "id" invalid: "6" cannot start a name
    …girlfriend with big ass homevid"  id="6grbSk55Z0q" title="Amazing girlfriend w…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 1368, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br>

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

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

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

  • Info Line 1368, Column 5: start tag was here
    <br><br>
  • Warning Line 1370, Column 96: cannot generate system identifier for general entity "block"
    …affic.com/www/delivery/spcjs.php?id=1&block=1&blockcampaign=1&target=_blank&wi…

    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 1370, Column 96: general entity "block" not defined and no default entity
    …affic.com/www/delivery/spcjs.php?id=1&block=1&blockcampaign=1&target=_blank&wi…

    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 1370, Column 101: reference not terminated by REFC delimiter
    ….com/www/delivery/spcjs.php?id=1&block=1&blockcampaign=1&target=_blank&withtex…

    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 1370, Column 101: reference to external entity in attribute value
    ….com/www/delivery/spcjs.php?id=1&block=1&blockcampaign=1&target=_blank&withtex…

    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 1370, Column 101: reference to entity "block" for which no system identifier could be generated
    ….com/www/delivery/spcjs.php?id=1&block=1&blockcampaign=1&target=_blank&withtex…

    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 1370, Column 95: entity was defined here
    …raffic.com/www/delivery/spcjs.php?id=1&block=1&blockcampaign=1&target=_blank&w…
  • Warning Line 1370, Column 104: cannot generate system identifier for general entity "blockcampaign"
    …m/www/delivery/spcjs.php?id=1&block=1&blockcampaign=1&target=_blank&withtext=1…

    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 1370, Column 104: general entity "blockcampaign" not defined and no default entity
    …m/www/delivery/spcjs.php?id=1&block=1&blockcampaign=1&target=_blank&withtext=1…

    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 1370, Column 117: reference not terminated by REFC delimiter
    …very/spcjs.php?id=1&block=1&blockcampaign=1&target=_blank&withtext=1'></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 1370, Column 117: reference to external entity in attribute value
    …very/spcjs.php?id=1&block=1&blockcampaign=1&target=_blank&withtext=1'></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 1370, Column 117: reference to entity "blockcampaign" for which no system identifier could be generated
    …very/spcjs.php?id=1&block=1&blockcampaign=1&target=_blank&withtext=1'></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 1370, Column 103: entity was defined here
    …om/www/delivery/spcjs.php?id=1&block=1&blockcampaign=1&target=_blank&withtext=…
  • Warning Line 1370, Column 120: cannot generate system identifier for general entity "target"
    …very/spcjs.php?id=1&block=1&blockcampaign=1&target=_blank&withtext=1'></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 1370, Column 120: general entity "target" not defined and no default entity
    …very/spcjs.php?id=1&block=1&blockcampaign=1&target=_blank&withtext=1'></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 1370, Column 126: reference not terminated by REFC delimiter
    …very/spcjs.php?id=1&block=1&blockcampaign=1&target=_blank&withtext=1'></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 1370, Column 126: reference to external entity in attribute value
    …very/spcjs.php?id=1&block=1&blockcampaign=1&target=_blank&withtext=1'></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 1370, Column 126: reference to entity "target" for which no system identifier could be generated
    …very/spcjs.php?id=1&block=1&blockcampaign=1&target=_blank&withtext=1'></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 1370, Column 119: entity was defined here
    …very/spcjs.php?id=1&block=1&blockcampaign=1&target=_blank&withtext=1'></script>
  • Warning Line 1370, Column 134: cannot generate system identifier for general entity "withtext"
    …very/spcjs.php?id=1&block=1&blockcampaign=1&target=_blank&withtext=1'></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 1370, Column 134: general entity "withtext" not defined and no default entity
    …very/spcjs.php?id=1&block=1&blockcampaign=1&target=_blank&withtext=1'></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 1370, Column 142: reference not terminated by REFC delimiter
    …very/spcjs.php?id=1&block=1&blockcampaign=1&target=_blank&withtext=1'></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 1370, Column 142: reference to external entity in attribute value
    …very/spcjs.php?id=1&block=1&blockcampaign=1&target=_blank&withtext=1'></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 1370, Column 142: reference to entity "withtext" for which no system identifier could be generated
    …very/spcjs.php?id=1&block=1&blockcampaign=1&target=_blank&withtext=1'></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 1370, Column 133: entity was defined here
    …very/spcjs.php?id=1&block=1&blockcampaign=1&target=_blank&withtext=1'></script>
  • Error Line 1375, Column 199: there is no attribute "allowtransparency"
    …='250' height='250' allowtransparency='true'><a href='http://ads.weownthetraff…

    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 1387, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

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

  • Info Line 1387, Column 1: start tag was here
    <br>
  • Error Line 1589, Column 440: value of attribute "id" invalid: "3" cannot start a name
    …alt="best couples in counciling"  id="3NJgZLg9vEc" title="best couples in coun…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 1823, Column 453: value of attribute "id" invalid: "0" cannot start a name
    …xi Diamond Fucks Her Babysitter"  id="0gXja94Iw7z" title="Lexi Diamond Fucks H…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 1877, Column 454: value of attribute "id" invalid: "2" cannot start a name
    …unning Amateur Teen Riding Cock"  id="2Fg3s9lgzbV" title="Stunning Amateur Tee…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 2003, Column 496: value of attribute "id" invalid: "5" cannot start a name
    … facialed on homemade porn tape"  id="55t6vNVJcP1" title="Naughty gf analyzed …

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 2201, Column 478: value of attribute "id" invalid: "5" cannot start a name
    … giving a hot and nasty blowjob"  id="5Jdj4bJSRy6" title="Amateur indian givin…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 2219, Column 496: value of attribute "id" invalid: "6" cannot start a name
    …cum facialed after anal try out"  id="6YHwQknss8p" title="Big boobs gf Rikki N…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 2255, Column 472: value of attribute "id" invalid: "0" cannot start a name
    …ls Hazing Pussy With Vegetables"  id="0kvXv6IJ07K" title="College Girls Hazing…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 2363, Column 440: value of attribute "id" invalid: "0" cannot start a name
    …alt="Sierra is up for group sex"  id="00JTuWkmGEF" title="Sierra is up for gro…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 2513, Column 7: end tag for "td" omitted, but OMITTAG NO was specified
      </tr>

    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 2502, Column 5: start tag was here
        <td>Friends: 
  • Error Line 2517, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

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

  • Info Line 2517, Column 1: start tag was here
    <br>
  • Error Line 2518, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

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

  • Info Line 2518, Column 1: start tag was here
    <br>
  • Warning Line 2523, Column 91: cannot generate system identifier for general entity "u"
    …sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" target…

    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 2523, Column 91: general entity "u" not defined and no default entity
    …sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" target…

    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 2523, Column 92: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" target=…

    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 2523, Column 92: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" target=…

    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 2523, Column 92: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" target=…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Warning Line 2525, Column 60: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" target=…

    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 2525, Column 60: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" target=…

    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 2525, Column 60: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" target=…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2526, Column 126: required attribute "alt" not specified
    …pornvideos.jpg" width="192" height="144" style="border: 1px solid #EDDABC"></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 2526, Column 130: end tag for "img" omitted, but OMITTAG NO was specified
    …pornvideos.jpg" width="192" height="144" style="border: 1px solid #EDDABC"></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 2526, Column 1: start tag was here
    <img src="http://www.sexoasis.com/tradethumbs/youngpornvideos.jpg" width="192" …
  • Warning Line 2530, Column 92: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=12&u=http://www.asianpornmovies.com" target=…

    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 2530, Column 92: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=12&u=http://www.asianpornmovies.com" target=…

    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 2530, Column 92: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=12&u=http://www.asianpornmovies.com" target=…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Warning Line 2532, Column 60: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=12&u=http://www.asianpornmovies.com" target=…

    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 2532, Column 60: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=12&u=http://www.asianpornmovies.com" target=…

    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 2532, Column 60: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=12&u=http://www.asianpornmovies.com" target=…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2533, Column 126: required attribute "alt" not specified
    …pornmovies.jpg" width="192" height="144" style="border: 1px solid #EDDABC"></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 2533, Column 130: end tag for "img" omitted, but OMITTAG NO was specified
    …pornmovies.jpg" width="192" height="144" style="border: 1px solid #EDDABC"></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 2533, Column 1: start tag was here
    <img src="http://www.sexoasis.com/tradethumbs/asianpornmovies.jpg" width="192" …
  • Warning Line 2537, Column 92: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=28&u=http://www.searchvids.com" target="_bla…

    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 2537, Column 92: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=28&u=http://www.searchvids.com" target="_bla…

    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 2537, Column 92: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=28&u=http://www.searchvids.com" target="_bla…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Warning Line 2539, Column 60: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=28&u=http://www.searchvids.com" target="_bla…

    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 2539, Column 60: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=28&u=http://www.searchvids.com" target="_bla…

    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 2539, Column 60: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=28&u=http://www.searchvids.com" target="_bla…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2540, Column 121: required attribute "alt" not specified
    …searchvids.jpg" width="192" height="144" style="border: 1px solid #EDDABC"></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 2540, Column 125: end tag for "img" omitted, but OMITTAG NO was specified
    …searchvids.jpg" width="192" height="144" style="border: 1px solid #EDDABC"></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 2540, Column 1: start tag was here
    <img src="http://www.sexoasis.com/tradethumbs/searchvids.jpg" width="192" heigh…
  • Warning Line 2544, Column 92: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=36&u=http://www.bravovids.com" target="_blan…

    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 2544, Column 92: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=36&u=http://www.bravovids.com" target="_blan…

    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 2544, Column 92: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=36&u=http://www.bravovids.com" target="_blan…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Warning Line 2546, Column 60: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.bravovids.com" target="_blan…

    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 2546, Column 60: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.bravovids.com" target="_blan…

    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 2546, Column 60: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.bravovids.com" target="_blan…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2547, Column 120: required attribute "alt" not specified
    …/bravovids.jpg" width="192" height="144" style="border: 1px solid #EDDABC"></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 2547, Column 124: end tag for "img" omitted, but OMITTAG NO was specified
    …/bravovids.jpg" width="192" height="144" style="border: 1px solid #EDDABC"></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 2547, Column 1: start tag was here
    <img src="http://www.sexoasis.com/tradethumbs/bravovids.jpg" width="192" height…
  • Warning Line 2551, Column 92: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=13&u=http://www.asspoint.com" target="_blank…

    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 2551, Column 92: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=13&u=http://www.asspoint.com" target="_blank…

    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 2551, Column 92: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=13&u=http://www.asspoint.com" target="_blank…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Warning Line 2553, Column 60: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=13&u=http://www.asspoint.com" target="_blank…

    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 2553, Column 60: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=13&u=http://www.asspoint.com" target="_blank…

    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 2553, Column 60: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=13&u=http://www.asspoint.com" target="_blank…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2554, Column 119: required attribute "alt" not specified
    …s/asspoint.jpg" width="192" height="144" style="border: 1px solid #EDDABC"></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 2554, Column 123: end tag for "img" omitted, but OMITTAG NO was specified
    …s/asspoint.jpg" width="192" height="144" style="border: 1px solid #EDDABC"></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 2554, Column 1: start tag was here
    <img src="http://www.sexoasis.com/tradethumbs/asspoint.jpg" width="192" height=…
  • Warning Line 2558, Column 92: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=21&u=http://www.fuckk.com" target="_blank">F…

    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 2558, Column 92: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=21&u=http://www.fuckk.com" target="_blank">F…

    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 2558, Column 92: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=21&u=http://www.fuckk.com" target="_blank">F…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Warning Line 2560, Column 60: reference not terminated by REFC delimiter
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.fuckk.com" target="_blank">

    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 2560, Column 60: reference to external entity in attribute value
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.fuckk.com" target="_blank">

    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 2560, Column 60: reference to entity "u" for which no system identifier could be generated
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.fuckk.com" target="_blank">

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2561, Column 116: required attribute "alt" not specified
    …umbs/fuckk.jpg" width="192" height="144" style="border: 1px solid #EDDABC"></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 2561, Column 120: end tag for "img" omitted, but OMITTAG NO was specified
    …umbs/fuckk.jpg" width="192" height="144" style="border: 1px solid #EDDABC"></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 2561, Column 1: start tag was here
    <img src="http://www.sexoasis.com/tradethumbs/fuckk.jpg" width="192" height="14…
  • Warning Line 2565, Column 92: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=17&u=http://www.pornstarclub.com" target="_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 2565, Column 92: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=17&u=http://www.pornstarclub.com" target="_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 2565, Column 92: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=17&u=http://www.pornstarclub.com" target="_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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Warning Line 2567, Column 60: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=17&u=http://www.pornstarclub.com" target="_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 2567, Column 60: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=17&u=http://www.pornstarclub.com" target="_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 2567, Column 60: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=17&u=http://www.pornstarclub.com" target="_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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2568, Column 123: required attribute "alt" not specified
    …rnstarclub.jpg" width="192" height="144" style="border: 1px solid #EDDABC"></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 2568, Column 127: end tag for "img" omitted, but OMITTAG NO was specified
    …rnstarclub.jpg" width="192" height="144" style="border: 1px solid #EDDABC"></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 2568, Column 1: start tag was here
    <img src="http://www.sexoasis.com/tradethumbs/pornstarclub.jpg" width="192" hei…
  • Warning Line 2572, Column 92: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=14&u=http://www.boneme.com" target="_blank">…

    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 2572, Column 92: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=14&u=http://www.boneme.com" target="_blank">…

    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 2572, Column 92: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=14&u=http://www.boneme.com" target="_blank">…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Warning Line 2574, Column 60: reference not terminated by REFC delimiter
    …sexoasis.com/cgi-bin/a2/out.cgi?id=14&u=http://www.boneme.com" target="_blank">

    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 2574, Column 60: reference to external entity in attribute value
    …sexoasis.com/cgi-bin/a2/out.cgi?id=14&u=http://www.boneme.com" target="_blank">

    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 2574, Column 60: reference to entity "u" for which no system identifier could be generated
    …sexoasis.com/cgi-bin/a2/out.cgi?id=14&u=http://www.boneme.com" target="_blank">

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2575, Column 117: required attribute "alt" not specified
    …mbs/boneme.jpg" width="192" height="144" style="border: 1px solid #EDDABC"></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 2575, Column 121: end tag for "img" omitted, but OMITTAG NO was specified
    …mbs/boneme.jpg" width="192" height="144" style="border: 1px solid #EDDABC"></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 2575, Column 1: start tag was here
    <img src="http://www.sexoasis.com/tradethumbs/boneme.jpg" width="192" height="1…
  • Warning Line 2579, Column 92: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=30&u=http://www.adult-series.com" target="_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 2579, Column 92: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=30&u=http://www.adult-series.com" target="_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 2579, Column 92: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=30&u=http://www.adult-series.com" target="_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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Warning Line 2581, Column 60: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=30&u=http://www.adult-series.com" target="_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 2581, Column 60: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=30&u=http://www.adult-series.com" target="_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 2581, Column 60: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=30&u=http://www.adult-series.com" target="_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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2582, Column 123: required attribute "alt" not specified
    …ult-series.jpg" width="192" height="144" style="border: 1px solid #EDDABC"></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 2582, Column 127: end tag for "img" omitted, but OMITTAG NO was specified
    …ult-series.jpg" width="192" height="144" style="border: 1px solid #EDDABC"></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 2582, Column 1: start tag was here
    <img src="http://www.sexoasis.com/tradethumbs/adult-series.jpg" width="192" hei…
  • Error Line 2589, Column 117: required attribute "alt" not specified
    …mbs/zuzazu.jpg" width="192" height="144" style="border: 1px solid #EDDABC"></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 2589, Column 121: end tag for "img" omitted, but OMITTAG NO was specified
    …mbs/zuzazu.jpg" width="192" height="144" style="border: 1px solid #EDDABC"></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 2589, Column 1: start tag was here
    <img src="http://www.sexoasis.com/tradethumbs/zuzazu.jpg" width="192" height="1…
  • Error Line 2593, Column 25: end tag for "br" omitted, but OMITTAG NO was specified
    <br style="clear: both">

    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 2593, Column 1: start tag was here
    <br style="clear: both">
  • Error Line 2596, Column 27: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table width="980" border=0 cellpadding=0 cellspacing=0 align=center>
  • Error Line 2596, Column 41: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table width="980" border=0 cellpadding=0 cellspacing=0 align=center>
  • Error Line 2596, Column 55: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table width="980" border=0 cellpadding=0 cellspacing=0 align=center>
  • Error Line 2596, Column 63: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table width="980" border=0 cellpadding=0 cellspacing=0 align=center>
  • Error Line 2598, Column 11: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <td width=20% align="left" valign=top>
  • Error Line 2598, Column 13: an attribute value must be a literal unless it contains only name characters
    <td width=20% align="left" valign=top>

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

  • Error Line 2598, Column 35: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <td width=20% align="left" valign=top>
  • Error Line 2599, Column 12: there is no attribute "href"
    01 <A href="http://www.sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.young…

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

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

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

  • Warning Line 2599, Column 63: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" target=…

    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 2599, Column 63: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" target=…

    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 2599, Column 63: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" target=…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2599, Column 103: there is no attribute "target"
    …=11&u=http://www.youngpornvideos.com" target="_blank">Young Porn Videos</a><br>

    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 2599, Column 111: element "A" undefined
    …=11&u=http://www.youngpornvideos.com" target="_blank">Young Porn Videos</a><br>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2599, Column 132: end tag for element "a" which is not open
    …=11&u=http://www.youngpornvideos.com" target="_blank">Young Porn Videos</a><br>

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

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

  • Error Line 2599, Column 137: end tag for "br" omitted, but OMITTAG NO was specified
    …=11&u=http://www.youngpornvideos.com" target="_blank">Young Porn Videos</a><br>

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

  • Info Line 2599, Column 133: start tag was here
    …=11&u=http://www.youngpornvideos.com" target="_blank">Young Porn Videos</a><br>
  • Warning Line 2600, Column 63: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=21&u=http://www.fuckk.com" target="_blank">F…

    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 2600, Column 63: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=21&u=http://www.fuckk.com" target="_blank">F…

    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 2600, Column 63: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=21&u=http://www.fuckk.com" target="_blank">F…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2600, Column 101: element "A" undefined
    …/cgi-bin/a2/out.cgi?id=21&u=http://www.fuckk.com" target="_blank">Fuckk</a><br>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2600, Column 110: end tag for element "a" which is not open
    …/cgi-bin/a2/out.cgi?id=21&u=http://www.fuckk.com" target="_blank">Fuckk</a><br>

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

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

  • Error Line 2600, Column 115: end tag for "br" omitted, but OMITTAG NO was specified
    …/cgi-bin/a2/out.cgi?id=21&u=http://www.fuckk.com" target="_blank">Fuckk</a><br>

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

  • Info Line 2600, Column 111: start tag was here
    …/cgi-bin/a2/out.cgi?id=21&u=http://www.fuckk.com" target="_blank">Fuckk</a><br>
  • Warning Line 2601, Column 63: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=67&u=http://www.jizzparade.com" target="_bla…

    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 2601, Column 63: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=67&u=http://www.jizzparade.com" target="_bla…

    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 2601, Column 63: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=67&u=http://www.jizzparade.com" target="_bla…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2601, Column 106: element "A" undefined
    …/out.cgi?id=67&u=http://www.jizzparade.com" target="_blank">Jizz Parade</a><br>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2601, Column 121: end tag for element "a" which is not open
    …/out.cgi?id=67&u=http://www.jizzparade.com" target="_blank">Jizz Parade</a><br>

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

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

  • Error Line 2601, Column 126: end tag for "br" omitted, but OMITTAG NO was specified
    …/out.cgi?id=67&u=http://www.jizzparade.com" target="_blank">Jizz Parade</a><br>

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

  • Info Line 2601, Column 122: start tag was here
    …/out.cgi?id=67&u=http://www.jizzparade.com" target="_blank">Jizz Parade</a><br>
  • Warning Line 2602, Column 63: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=26&u=http://www.viewgals.com" target="_blank…

    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 2602, Column 63: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=26&u=http://www.viewgals.com" target="_blank…

    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 2602, Column 63: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=26&u=http://www.viewgals.com" target="_blank…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2602, Column 104: element "A" undefined
    …n/a2/out.cgi?id=26&u=http://www.viewgals.com" target="_blank">View Gals</a><br>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2602, Column 117: end tag for element "a" which is not open
    …n/a2/out.cgi?id=26&u=http://www.viewgals.com" target="_blank">View Gals</a><br>

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

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

  • Error Line 2602, Column 122: end tag for "br" omitted, but OMITTAG NO was specified
    …n/a2/out.cgi?id=26&u=http://www.viewgals.com" target="_blank">View Gals</a><br>

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

  • Info Line 2602, Column 118: start tag was here
    …n/a2/out.cgi?id=26&u=http://www.viewgals.com" target="_blank">View Gals</a><br>
  • Warning Line 2603, Column 63: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=62&u=http://www.hqmovies.com" target="_blank…

    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 2603, Column 63: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=62&u=http://www.hqmovies.com" target="_blank…

    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 2603, Column 63: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=62&u=http://www.hqmovies.com" target="_blank…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2603, Column 104: element "A" undefined
    …n/a2/out.cgi?id=62&u=http://www.hqmovies.com" target="_blank">HQ Movies</a><br>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2603, Column 117: end tag for element "a" which is not open
    …n/a2/out.cgi?id=62&u=http://www.hqmovies.com" target="_blank">HQ Movies</a><br>

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

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

  • Error Line 2603, Column 122: end tag for "br" omitted, but OMITTAG NO was specified
    …n/a2/out.cgi?id=62&u=http://www.hqmovies.com" target="_blank">HQ Movies</a><br>

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

  • Info Line 2603, Column 118: start tag was here
    …n/a2/out.cgi?id=62&u=http://www.hqmovies.com" target="_blank">HQ Movies</a><br>
  • Warning Line 2604, Column 63: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=54&u=http://www.direct-porn.com" target="_bl…

    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 2604, Column 63: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=54&u=http://www.direct-porn.com" target="_bl…

    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 2604, Column 63: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=54&u=http://www.direct-porn.com" target="_bl…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2604, Column 107: element "A" undefined
    …out.cgi?id=54&u=http://www.direct-porn.com" target="_blank">Direct Porn</a><br>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2604, Column 122: end tag for element "a" which is not open
    …out.cgi?id=54&u=http://www.direct-porn.com" target="_blank">Direct Porn</a><br>

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

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

  • Error Line 2604, Column 127: end tag for "br" omitted, but OMITTAG NO was specified
    …out.cgi?id=54&u=http://www.direct-porn.com" target="_blank">Direct Porn</a><br>

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

  • Info Line 2604, Column 123: start tag was here
    …out.cgi?id=54&u=http://www.direct-porn.com" target="_blank">Direct Porn</a><br>
  • Warning Line 2605, Column 63: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=58&u=http://www.picshark.com" target="_blank…

    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 2605, Column 63: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=58&u=http://www.picshark.com" target="_blank…

    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 2605, Column 63: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=58&u=http://www.picshark.com" target="_blank…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2605, Column 104: element "A" undefined
    …n/a2/out.cgi?id=58&u=http://www.picshark.com" target="_blank">Pic Shark</a><br>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2605, Column 117: end tag for element "a" which is not open
    …n/a2/out.cgi?id=58&u=http://www.picshark.com" target="_blank">Pic Shark</a><br>

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

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

  • Error Line 2605, Column 122: end tag for "br" omitted, but OMITTAG NO was specified
    …n/a2/out.cgi?id=58&u=http://www.picshark.com" target="_blank">Pic Shark</a><br>

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

  • Info Line 2605, Column 118: start tag was here
    …n/a2/out.cgi?id=58&u=http://www.picshark.com" target="_blank">Pic Shark</a><br>
  • Error Line 2606, Column 5: end tag for "A" omitted, but OMITTAG NO was specified
    </td>

    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 2605, Column 4: start tag was here
    31 <A href="http://www.sexoasis.com/cgi-bin/a2/out.cgi?id=58&u=http://www.picsh…
  • Error Line 2606, Column 5: end tag for "A" omitted, but OMITTAG NO was specified
    </td>

    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 2604, Column 4: start tag was here
    26 <A href="http://www.sexoasis.com/cgi-bin/a2/out.cgi?id=54&u=http://www.direc…
  • Error Line 2606, Column 5: end tag for "A" omitted, but OMITTAG NO was specified
    </td>

    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 2603, Column 4: start tag was here
    21 <A href="http://www.sexoasis.com/cgi-bin/a2/out.cgi?id=62&u=http://www.hqmov…
  • Error Line 2606, Column 5: end tag for "A" omitted, but OMITTAG NO was specified
    </td>

    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 2602, Column 4: start tag was here
    16 <A href="http://www.sexoasis.com/cgi-bin/a2/out.cgi?id=26&u=http://www.viewg…
  • Error Line 2606, Column 5: end tag for "A" omitted, but OMITTAG NO was specified
    </td>

    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 2601, Column 4: start tag was here
    11 <A href="http://www.sexoasis.com/cgi-bin/a2/out.cgi?id=67&u=http://www.jizzp…
  • Error Line 2606, Column 5: end tag for "A" omitted, but OMITTAG NO was specified
    </td>

    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 2600, Column 4: start tag was here
    06 <A href="http://www.sexoasis.com/cgi-bin/a2/out.cgi?id=21&u=http://www.fuckk…
  • Error Line 2606, Column 5: end tag for "A" omitted, but OMITTAG NO was specified
    </td>

    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 2599, Column 4: start tag was here
    01 <A href="http://www.sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.young…
  • Error Line 2607, Column 11: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <td width=20% align="left" valign=top>
  • Error Line 2607, Column 13: an attribute value must be a literal unless it contains only name characters
    <td width=20% align="left" valign=top>

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

  • Error Line 2607, Column 35: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <td width=20% align="left" valign=top>
  • Warning Line 2608, Column 63: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=12&u=http://www.asianpornmovies.com" target=…

    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 2608, Column 63: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=12&u=http://www.asianpornmovies.com" target=…

    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 2608, Column 63: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=12&u=http://www.asianpornmovies.com" target=…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2608, Column 111: element "A" undefined
    …=12&u=http://www.asianpornmovies.com" target="_blank">Asian Porn Movies</a><br>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2608, Column 132: end tag for element "a" which is not open
    …=12&u=http://www.asianpornmovies.com" target="_blank">Asian Porn Movies</a><br>

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

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

  • Error Line 2608, Column 137: end tag for "br" omitted, but OMITTAG NO was specified
    …=12&u=http://www.asianpornmovies.com" target="_blank">Asian Porn Movies</a><br>

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

  • Info Line 2608, Column 133: start tag was here
    …=12&u=http://www.asianpornmovies.com" target="_blank">Asian Porn Movies</a><br>
  • Warning Line 2609, Column 63: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=17&u=http://www.pornstarclub.com" target="_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 2609, Column 63: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=17&u=http://www.pornstarclub.com" target="_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 2609, Column 63: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=17&u=http://www.pornstarclub.com" target="_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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2609, Column 108: element "A" undefined
    …cgi?id=17&u=http://www.pornstarclub.com" target="_blank">Porn Star Club</a><br>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2609, Column 126: end tag for element "a" which is not open
    …cgi?id=17&u=http://www.pornstarclub.com" target="_blank">Porn Star Club</a><br>

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

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

  • Error Line 2609, Column 131: end tag for "br" omitted, but OMITTAG NO was specified
    …cgi?id=17&u=http://www.pornstarclub.com" target="_blank">Porn Star Club</a><br>

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

  • Info Line 2609, Column 127: start tag was here
    …cgi?id=17&u=http://www.pornstarclub.com" target="_blank">Porn Star Club</a><br>
  • Warning Line 2610, Column 63: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=37&u=http://www.wildwildvids.com" target="_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 2610, Column 63: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=37&u=http://www.wildwildvids.com" target="_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 2610, Column 63: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=37&u=http://www.wildwildvids.com" target="_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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2610, Column 108: element "A" undefined
    …cgi?id=37&u=http://www.wildwildvids.com" target="_blank">Wild Wild Vids</a><br>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2610, Column 126: end tag for element "a" which is not open
    …cgi?id=37&u=http://www.wildwildvids.com" target="_blank">Wild Wild Vids</a><br>

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

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

  • Error Line 2610, Column 131: end tag for "br" omitted, but OMITTAG NO was specified
    …cgi?id=37&u=http://www.wildwildvids.com" target="_blank">Wild Wild Vids</a><br>

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

  • Info Line 2610, Column 127: start tag was here
    …cgi?id=37&u=http://www.wildwildvids.com" target="_blank">Wild Wild Vids</a><br>
  • Warning Line 2611, Column 63: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=32&u=http://www.dailymovies.tv" target="_bla…

    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 2611, Column 63: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=32&u=http://www.dailymovies.tv" target="_bla…

    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 2611, Column 63: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=32&u=http://www.dailymovies.tv" target="_bla…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2611, Column 106: element "A" undefined
    …out.cgi?id=32&u=http://www.dailymovies.tv" target="_blank">Daily Movies</a><br>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2611, Column 122: end tag for element "a" which is not open
    …out.cgi?id=32&u=http://www.dailymovies.tv" target="_blank">Daily Movies</a><br>

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

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

  • Error Line 2611, Column 127: end tag for "br" omitted, but OMITTAG NO was specified
    …out.cgi?id=32&u=http://www.dailymovies.tv" target="_blank">Daily Movies</a><br>

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

  • Info Line 2611, Column 123: start tag was here
    …out.cgi?id=32&u=http://www.dailymovies.tv" target="_blank">Daily Movies</a><br>
  • Warning Line 2612, Column 63: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=19&u=http://www.longestlist.com" target="_bl…

    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 2612, Column 63: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=19&u=http://www.longestlist.com" target="_bl…

    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 2612, Column 63: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=19&u=http://www.longestlist.com" target="_bl…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2612, Column 107: element "A" undefined
    …ut.cgi?id=19&u=http://www.longestlist.com" target="_blank">Longest List</a><br>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2612, Column 123: end tag for element "a" which is not open
    …ut.cgi?id=19&u=http://www.longestlist.com" target="_blank">Longest List</a><br>

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

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

  • Error Line 2612, Column 128: end tag for "br" omitted, but OMITTAG NO was specified
    …ut.cgi?id=19&u=http://www.longestlist.com" target="_blank">Longest List</a><br>

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

  • Info Line 2612, Column 124: start tag was here
    …ut.cgi?id=19&u=http://www.longestlist.com" target="_blank">Longest List</a><br>
  • Warning Line 2613, Column 63: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=48&u=http://www.czech-girls.com" target="_bl…

    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 2613, Column 63: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=48&u=http://www.czech-girls.com" target="_bl…

    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 2613, Column 63: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=48&u=http://www.czech-girls.com" target="_bl…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2613, Column 107: element "A" undefined
    …out.cgi?id=48&u=http://www.czech-girls.com" target="_blank">Czech Girls</a><br>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2613, Column 122: end tag for element "a" which is not open
    …out.cgi?id=48&u=http://www.czech-girls.com" target="_blank">Czech Girls</a><br>

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

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

  • Error Line 2613, Column 127: end tag for "br" omitted, but OMITTAG NO was specified
    …out.cgi?id=48&u=http://www.czech-girls.com" target="_blank">Czech Girls</a><br>

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

  • Info Line 2613, Column 123: start tag was here
    …out.cgi?id=48&u=http://www.czech-girls.com" target="_blank">Czech Girls</a><br>
  • Warning Line 2614, Column 63: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=60&u=http://www.blackmonsterweapons.net" tar…

    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 2614, Column 63: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=60&u=http://www.blackmonsterweapons.net" tar…

    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 2614, Column 63: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=60&u=http://www.blackmonsterweapons.net" tar…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2614, Column 115: element "A" undefined
    …=60&u=http://www.blackmonsterweapons.net" target="_blank">Black Monster</a><br>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2614, Column 132: end tag for element "a" which is not open
    …=60&u=http://www.blackmonsterweapons.net" target="_blank">Black Monster</a><br>

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

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

  • Error Line 2614, Column 137: end tag for "br" omitted, but OMITTAG NO was specified
    …=60&u=http://www.blackmonsterweapons.net" target="_blank">Black Monster</a><br>

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

  • Info Line 2614, Column 133: start tag was here
    …=60&u=http://www.blackmonsterweapons.net" target="_blank">Black Monster</a><br>
  • Error Line 2615, Column 5: end tag for "A" omitted, but OMITTAG NO was specified
    </td>

    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 2614, Column 4: start tag was here
    32 <A href="http://www.sexoasis.com/cgi-bin/a2/out.cgi?id=60&u=http://www.black…
  • Error Line 2615, Column 5: end tag for "A" omitted, but OMITTAG NO was specified
    </td>

    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 2613, Column 4: start tag was here
    27 <A href="http://www.sexoasis.com/cgi-bin/a2/out.cgi?id=48&u=http://www.czech…
  • Error Line 2615, Column 5: end tag for "A" omitted, but OMITTAG NO was specified
    </td>

    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 2612, Column 4: start tag was here
    22 <A href="http://www.sexoasis.com/cgi-bin/a2/out.cgi?id=19&u=http://www.longe…
  • Error Line 2615, Column 5: end tag for "A" omitted, but OMITTAG NO was specified
    </td>

    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 2611, Column 4: start tag was here
    17 <A href="http://www.sexoasis.com/cgi-bin/a2/out.cgi?id=32&u=http://www.daily…
  • Error Line 2615, Column 5: end tag for "A" omitted, but OMITTAG NO was specified
    </td>

    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 2610, Column 4: start tag was here
    12 <A href="http://www.sexoasis.com/cgi-bin/a2/out.cgi?id=37&u=http://www.wildw…
  • Error Line 2615, Column 5: end tag for "A" omitted, but OMITTAG NO was specified
    </td>

    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 2609, Column 4: start tag was here
    07 <A href="http://www.sexoasis.com/cgi-bin/a2/out.cgi?id=17&u=http://www.porns…
  • Error Line 2615, Column 5: end tag for "A" omitted, but OMITTAG NO was specified
    </td>

    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 2608, Column 4: start tag was here
    02 <A href="http://www.sexoasis.com/cgi-bin/a2/out.cgi?id=12&u=http://www.asian…
  • Error Line 2616, Column 11: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <td width=20% align="left" valign=top>
  • Error Line 2616, Column 13: an attribute value must be a literal unless it contains only name characters
    <td width=20% align="left" valign=top>

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

  • Error Line 2616, Column 35: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <td width=20% align="left" valign=top>
  • Warning Line 2617, Column 63: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=28&u=http://www.searchvids.com" target="_bla…

    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 2617, Column 63: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=28&u=http://www.searchvids.com" target="_bla…

    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 2617, Column 63: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=28&u=http://www.searchvids.com" target="_bla…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2617, Column 106: element "A" undefined
    …/out.cgi?id=28&u=http://www.searchvids.com" target="_blank">Search Vids</a><br>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2617, Column 121: end tag for element "a" which is not open
    …/out.cgi?id=28&u=http://www.searchvids.com" target="_blank">Search Vids</a><br>

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

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

  • Error Line 2617, Column 126: end tag for "br" omitted, but OMITTAG NO was specified
    …/out.cgi?id=28&u=http://www.searchvids.com" target="_blank">Search Vids</a><br>

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

  • Info Line 2617, Column 122: start tag was here
    …/out.cgi?id=28&u=http://www.searchvids.com" target="_blank">Search Vids</a><br>
  • Warning Line 2618, Column 63: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=14&u=http://www.boneme.com" target="_blank">…

    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 2618, Column 63: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=14&u=http://www.boneme.com" target="_blank">…

    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 2618, Column 63: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=14&u=http://www.boneme.com" target="_blank">…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2618, Column 102: element "A" undefined
    …i-bin/a2/out.cgi?id=14&u=http://www.boneme.com" target="_blank">Bone Me</a><br>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2618, Column 113: end tag for element "a" which is not open
    …i-bin/a2/out.cgi?id=14&u=http://www.boneme.com" target="_blank">Bone Me</a><br>

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

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

  • Error Line 2618, Column 118: end tag for "br" omitted, but OMITTAG NO was specified
    …i-bin/a2/out.cgi?id=14&u=http://www.boneme.com" target="_blank">Bone Me</a><br>

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

  • Info Line 2618, Column 114: start tag was here
    …i-bin/a2/out.cgi?id=14&u=http://www.boneme.com" target="_blank">Bone Me</a><br>
  • Warning Line 2619, Column 63: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=43&u=http://www.teenmpegs.com" target="_blan…

    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 2619, Column 63: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=43&u=http://www.teenmpegs.com" target="_blan…

    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 2619, Column 63: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=43&u=http://www.teenmpegs.com" target="_blan…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2619, Column 105: element "A" undefined
    …a2/out.cgi?id=43&u=http://www.teenmpegs.com" target="_blank">Teen Mpegs</a><br>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2619, Column 119: end tag for element "a" which is not open
    …a2/out.cgi?id=43&u=http://www.teenmpegs.com" target="_blank">Teen Mpegs</a><br>

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

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

  • Error Line 2619, Column 124: end tag for "br" omitted, but OMITTAG NO was specified
    …a2/out.cgi?id=43&u=http://www.teenmpegs.com" target="_blank">Teen Mpegs</a><br>

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

  • Info Line 2619, Column 120: start tag was here
    …a2/out.cgi?id=43&u=http://www.teenmpegs.com" target="_blank">Teen Mpegs</a><br>
  • Warning Line 2620, Column 63: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=59&u=http://www.dustyporn.com" target="_blan…

    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 2620, Column 63: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=59&u=http://www.dustyporn.com" target="_blan…

    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 2620, Column 63: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=59&u=http://www.dustyporn.com" target="_blan…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2620, Column 105: element "A" undefined
    …a2/out.cgi?id=59&u=http://www.dustyporn.com" target="_blank">Dusty Porn</a><br>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2620, Column 119: end tag for element "a" which is not open
    …a2/out.cgi?id=59&u=http://www.dustyporn.com" target="_blank">Dusty Porn</a><br>

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

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

  • Error Line 2620, Column 124: end tag for "br" omitted, but OMITTAG NO was specified
    …a2/out.cgi?id=59&u=http://www.dustyporn.com" target="_blank">Dusty Porn</a><br>

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

  • Info Line 2620, Column 120: start tag was here
    …a2/out.cgi?id=59&u=http://www.dustyporn.com" target="_blank">Dusty Porn</a><br>
  • Warning Line 2621, Column 63: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=35&u=http://www.xxxlf.com" target="_blank">X…

    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 2621, Column 63: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=35&u=http://www.xxxlf.com" target="_blank">X…

    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 2621, Column 63: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=35&u=http://www.xxxlf.com" target="_blank">X…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2621, Column 101: element "A" undefined
    …cgi-bin/a2/out.cgi?id=35&u=http://www.xxxlf.com" target="_blank">XXX LF</a><br>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2621, Column 111: end tag for element "a" which is not open
    …cgi-bin/a2/out.cgi?id=35&u=http://www.xxxlf.com" target="_blank">XXX LF</a><br>

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

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

  • Error Line 2621, Column 116: end tag for "br" omitted, but OMITTAG NO was specified
    …cgi-bin/a2/out.cgi?id=35&u=http://www.xxxlf.com" target="_blank">XXX LF</a><br>

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

  • Info Line 2621, Column 112: start tag was here
    …cgi-bin/a2/out.cgi?id=35&u=http://www.xxxlf.com" target="_blank">XXX LF</a><br>
  • Warning Line 2622, Column 63: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=52&u=http://www.cock.pro" target="_blank">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 2622, Column 63: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=52&u=http://www.cock.pro" target="_blank">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 2622, Column 63: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=52&u=http://www.cock.pro" target="_blank">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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2622, Column 100: element "A" undefined
    …gi-bin/a2/out.cgi?id=52&u=http://www.cock.pro" target="_blank">Cock Pro</a><br>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2622, Column 112: end tag for element "a" which is not open
    …gi-bin/a2/out.cgi?id=52&u=http://www.cock.pro" target="_blank">Cock Pro</a><br>

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

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

  • Error Line 2622, Column 117: end tag for "br" omitted, but OMITTAG NO was specified
    …gi-bin/a2/out.cgi?id=52&u=http://www.cock.pro" target="_blank">Cock Pro</a><br>

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

  • Info Line 2622, Column 113: start tag was here
    …gi-bin/a2/out.cgi?id=52&u=http://www.cock.pro" target="_blank">Cock Pro</a><br>
  • Warning Line 2623, Column 63: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=61&u=http://www.bigvids.com" target="_blank"…

    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 2623, Column 63: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=61&u=http://www.bigvids.com" target="_blank"…

    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 2623, Column 63: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=61&u=http://www.bigvids.com" target="_blank"…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2623, Column 103: element "A" undefined
    …bin/a2/out.cgi?id=61&u=http://www.bigvids.com" target="_blank">Big Vids</a><br>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2623, Column 115: end tag for element "a" which is not open
    …bin/a2/out.cgi?id=61&u=http://www.bigvids.com" target="_blank">Big Vids</a><br>

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

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

  • Error Line 2623, Column 120: end tag for "br" omitted, but OMITTAG NO was specified
    …bin/a2/out.cgi?id=61&u=http://www.bigvids.com" target="_blank">Big Vids</a><br>

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

  • Info Line 2623, Column 116: start tag was here
    …bin/a2/out.cgi?id=61&u=http://www.bigvids.com" target="_blank">Big Vids</a><br>
  • Error Line 2624, Column 5: end tag for "A" omitted, but OMITTAG NO was specified
    </td>

    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 2623, Column 4: start tag was here
    33 <A href="http://www.sexoasis.com/cgi-bin/a2/out.cgi?id=61&u=http://www.bigvi…
  • Error Line 2624, Column 5: end tag for "A" omitted, but OMITTAG NO was specified
    </td>

    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 2622, Column 4: start tag was here
    28 <A href="http://www.sexoasis.com/cgi-bin/a2/out.cgi?id=52&u=http://www.cock.…
  • Error Line 2624, Column 5: end tag for "A" omitted, but OMITTAG NO was specified
    </td>

    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 2621, Column 4: start tag was here
    23 <A href="http://www.sexoasis.com/cgi-bin/a2/out.cgi?id=35&u=http://www.xxxlf…
  • Error Line 2624, Column 5: end tag for "A" omitted, but OMITTAG NO was specified
    </td>

    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 2620, Column 4: start tag was here
    18 <A href="http://www.sexoasis.com/cgi-bin/a2/out.cgi?id=59&u=http://www.dusty…
  • Error Line 2624, Column 5: end tag for "A" omitted, but OMITTAG NO was specified
    </td>

    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 2619, Column 4: start tag was here
    13 <A href="http://www.sexoasis.com/cgi-bin/a2/out.cgi?id=43&u=http://www.teenm…
  • Error Line 2624, Column 5: end tag for "A" omitted, but OMITTAG NO was specified
    </td>

    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 2618, Column 4: start tag was here
    08 <A href="http://www.sexoasis.com/cgi-bin/a2/out.cgi?id=14&u=http://www.bonem…
  • Error Line 2624, Column 5: end tag for "A" omitted, but OMITTAG NO was specified
    </td>

    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 2617, Column 4: start tag was here
    03 <A href="http://www.sexoasis.com/cgi-bin/a2/out.cgi?id=28&u=http://www.searc…
  • Error Line 2625, Column 11: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <td width=20% align="left" valign=top>
  • Error Line 2625, Column 13: an attribute value must be a literal unless it contains only name characters
    <td width=20% align="left" valign=top>

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

  • Error Line 2625, Column 35: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <td width=20% align="left" valign=top>
  • Warning Line 2626, Column 63: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=36&u=http://www.bravovids.com" target="_blan…

    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 2626, Column 63: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=36&u=http://www.bravovids.com" target="_blan…

    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 2626, Column 63: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=36&u=http://www.bravovids.com" target="_blan…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2626, Column 105: element "A" undefined
    …a2/out.cgi?id=36&u=http://www.bravovids.com" target="_blank">Bravo Vids</a><br>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2626, Column 119: end tag for element "a" which is not open
    …a2/out.cgi?id=36&u=http://www.bravovids.com" target="_blank">Bravo Vids</a><br>

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

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

  • Error Line 2626, Column 124: end tag for "br" omitted, but OMITTAG NO was specified
    …a2/out.cgi?id=36&u=http://www.bravovids.com" target="_blank">Bravo Vids</a><br>

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

  • Info Line 2626, Column 120: start tag was here
    …a2/out.cgi?id=36&u=http://www.bravovids.com" target="_blank">Bravo Vids</a><br>
  • Warning Line 2627, Column 63: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=30&u=http://www.adult-series.com" target="_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 2627, Column 63: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=30&u=http://www.adult-series.com" target="_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 2627, Column 63: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=30&u=http://www.adult-series.com" target="_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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2627, Column 108: element "A" undefined
    …t.cgi?id=30&u=http://www.adult-series.com" target="_blank">Adult Series</a><br>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2627, Column 124: end tag for element "a" which is not open
    …t.cgi?id=30&u=http://www.adult-series.com" target="_blank">Adult Series</a><br>

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

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

  • Error Line 2627, Column 129: end tag for "br" omitted, but OMITTAG NO was specified
    …t.cgi?id=30&u=http://www.adult-series.com" target="_blank">Adult Series</a><br>

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

  • Info Line 2627, Column 125: start tag was here
    …t.cgi?id=30&u=http://www.adult-series.com" target="_blank">Adult Series</a><br>
  • Warning Line 2628, Column 63: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=18&u=http://www.juliamovies.com" target="_bl…

    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 2628, Column 63: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=18&u=http://www.juliamovies.com" target="_bl…

    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 2628, Column 63: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=18&u=http://www.juliamovies.com" target="_bl…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2628, Column 107: element "A" undefined
    …ut.cgi?id=18&u=http://www.juliamovies.com" target="_blank">Julie Movies</a><br>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2628, Column 123: end tag for element "a" which is not open
    …ut.cgi?id=18&u=http://www.juliamovies.com" target="_blank">Julie Movies</a><br>

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

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

  • Error Line 2628, Column 128: end tag for "br" omitted, but OMITTAG NO was specified
    …ut.cgi?id=18&u=http://www.juliamovies.com" target="_blank">Julie Movies</a><br>

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

  • Info Line 2628, Column 124: start tag was here
    …ut.cgi?id=18&u=http://www.juliamovies.com" target="_blank">Julie Movies</a><br>
  • Warning Line 2629, Column 63: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=55&u=http://www.hotbigmovies.com" target="_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 2629, Column 63: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=55&u=http://www.hotbigmovies.com" target="_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 2629, Column 63: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=55&u=http://www.hotbigmovies.com" target="_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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2629, Column 108: element "A" undefined
    …cgi?id=55&u=http://www.hotbigmovies.com" target="_blank">Hot Big Movies</a><br>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2629, Column 126: end tag for element "a" which is not open
    …cgi?id=55&u=http://www.hotbigmovies.com" target="_blank">Hot Big Movies</a><br>

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

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

  • Error Line 2629, Column 131: end tag for "br" omitted, but OMITTAG NO was specified
    …cgi?id=55&u=http://www.hotbigmovies.com" target="_blank">Hot Big Movies</a><br>

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

  • Info Line 2629, Column 127: start tag was here
    …cgi?id=55&u=http://www.hotbigmovies.com" target="_blank">Hot Big Movies</a><br>
  • Warning Line 2630, Column 63: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=42&u=http://www.smokinmovies.com" target="_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 2630, Column 63: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=42&u=http://www.smokinmovies.com" target="_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 2630, Column 63: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=42&u=http://www.smokinmovies.com" target="_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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2630, Column 108: element "A" undefined
    ….cgi?id=42&u=http://www.smokinmovies.com" target="_blank">Smokin Movies</a><br>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2630, Column 125: end tag for element "a" which is not open
    ….cgi?id=42&u=http://www.smokinmovies.com" target="_blank">Smokin Movies</a><br>

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

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

  • Error Line 2630, Column 130: end tag for "br" omitted, but OMITTAG NO was specified
    ….cgi?id=42&u=http://www.smokinmovies.com" target="_blank">Smokin Movies</a><br>

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

  • Info Line 2630, Column 126: start tag was here
    ….cgi?id=42&u=http://www.smokinmovies.com" target="_blank">Smokin Movies</a><br>
  • Warning Line 2631, Column 63: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=34&u=http://www.riaps.com" target="_blank">R…

    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 2631, Column 63: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=34&u=http://www.riaps.com" target="_blank">R…

    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 2631, Column 63: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=34&u=http://www.riaps.com" target="_blank">R…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2631, Column 101: element "A" undefined
    …/cgi-bin/a2/out.cgi?id=34&u=http://www.riaps.com" target="_blank">Riaps</a><br>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2631, Column 110: end tag for element "a" which is not open
    …/cgi-bin/a2/out.cgi?id=34&u=http://www.riaps.com" target="_blank">Riaps</a><br>

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

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

  • Error Line 2631, Column 115: end tag for "br" omitted, but OMITTAG NO was specified
    …/cgi-bin/a2/out.cgi?id=34&u=http://www.riaps.com" target="_blank">Riaps</a><br>

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

  • Info Line 2631, Column 111: start tag was here
    …/cgi-bin/a2/out.cgi?id=34&u=http://www.riaps.com" target="_blank">Riaps</a><br>
  • Warning Line 2632, Column 63: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=56&u=http://www.uniformslutzone.com" target=…

    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 2632, Column 63: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=56&u=http://www.uniformslutzone.com" target=…

    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 2632, Column 63: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=56&u=http://www.uniformslutzone.com" target=…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2632, Column 111: element "A" undefined
    …=56&u=http://www.uniformslutzone.com" target="_blank">Uniform Slut Zone</a><br>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2632, Column 132: end tag for element "a" which is not open
    …=56&u=http://www.uniformslutzone.com" target="_blank">Uniform Slut Zone</a><br>

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

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

  • Error Line 2632, Column 137: end tag for "br" omitted, but OMITTAG NO was specified
    …=56&u=http://www.uniformslutzone.com" target="_blank">Uniform Slut Zone</a><br>

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

  • Info Line 2632, Column 133: start tag was here
    …=56&u=http://www.uniformslutzone.com" target="_blank">Uniform Slut Zone</a><br>
  • Error Line 2633, Column 5: end tag for "A" omitted, but OMITTAG NO was specified
    </td>

    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 2632, Column 4: start tag was here
    34 <A href="http://www.sexoasis.com/cgi-bin/a2/out.cgi?id=56&u=http://www.unifo…
  • Error Line 2633, Column 5: end tag for "A" omitted, but OMITTAG NO was specified
    </td>

    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 2631, Column 4: start tag was here
    29 <A href="http://www.sexoasis.com/cgi-bin/a2/out.cgi?id=34&u=http://www.riaps…
  • Error Line 2633, Column 5: end tag for "A" omitted, but OMITTAG NO was specified
    </td>

    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 2630, Column 4: start tag was here
    24 <A href="http://www.sexoasis.com/cgi-bin/a2/out.cgi?id=42&u=http://www.smoki…
  • Error Line 2633, Column 5: end tag for "A" omitted, but OMITTAG NO was specified
    </td>

    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 2629, Column 4: start tag was here
    19 <A href="http://www.sexoasis.com/cgi-bin/a2/out.cgi?id=55&u=http://www.hotbi…
  • Error Line 2633, Column 5: end tag for "A" omitted, but OMITTAG NO was specified
    </td>

    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 2628, Column 4: start tag was here
    14 <A href="http://www.sexoasis.com/cgi-bin/a2/out.cgi?id=18&u=http://www.julia…
  • Error Line 2633, Column 5: end tag for "A" omitted, but OMITTAG NO was specified
    </td>

    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 2627, Column 4: start tag was here
    09 <A href="http://www.sexoasis.com/cgi-bin/a2/out.cgi?id=30&u=http://www.adult…
  • Error Line 2633, Column 5: end tag for "A" omitted, but OMITTAG NO was specified
    </td>

    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 2626, Column 4: start tag was here
    04 <A href="http://www.sexoasis.com/cgi-bin/a2/out.cgi?id=36&u=http://www.bravo…
  • Error Line 2634, Column 11: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <td width=20% align="left" valign=top>
  • Error Line 2634, Column 13: an attribute value must be a literal unless it contains only name characters
    <td width=20% align="left" valign=top>

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

  • Error Line 2634, Column 35: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <td width=20% align="left" valign=top>
  • Warning Line 2635, Column 63: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=13&u=http://www.asspoint.com" target="_blank…

    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 2635, Column 63: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=13&u=http://www.asspoint.com" target="_blank…

    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 2635, Column 63: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=13&u=http://www.asspoint.com" target="_blank…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2635, Column 104: element "A" undefined
    …n/a2/out.cgi?id=13&u=http://www.asspoint.com" target="_blank">Ass Point</a><br>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2635, Column 117: end tag for element "a" which is not open
    …n/a2/out.cgi?id=13&u=http://www.asspoint.com" target="_blank">Ass Point</a><br>

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

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

  • Error Line 2635, Column 122: end tag for "br" omitted, but OMITTAG NO was specified
    …n/a2/out.cgi?id=13&u=http://www.asspoint.com" target="_blank">Ass Point</a><br>

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

  • Info Line 2635, Column 118: start tag was here
    …n/a2/out.cgi?id=13&u=http://www.asspoint.com" target="_blank">Ass Point</a><br>
  • Warning Line 2636, Column 63: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=27&u=http://www.zuzazu.com" target="_blank">…

    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 2636, Column 63: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=27&u=http://www.zuzazu.com" target="_blank">…

    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 2636, Column 63: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=27&u=http://www.zuzazu.com" target="_blank">…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2636, Column 102: element "A" undefined
    …gi-bin/a2/out.cgi?id=27&u=http://www.zuzazu.com" target="_blank">ZuZaZu</a><br>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2636, Column 112: end tag for element "a" which is not open
    …gi-bin/a2/out.cgi?id=27&u=http://www.zuzazu.com" target="_blank">ZuZaZu</a><br>

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

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

  • Error Line 2636, Column 117: end tag for "br" omitted, but OMITTAG NO was specified
    …gi-bin/a2/out.cgi?id=27&u=http://www.zuzazu.com" target="_blank">ZuZaZu</a><br>

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

  • Info Line 2636, Column 113: start tag was here
    …gi-bin/a2/out.cgi?id=27&u=http://www.zuzazu.com" target="_blank">ZuZaZu</a><br>
  • Warning Line 2637, Column 63: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=38&u=http://www.nonstopmovies.com" target="_…

    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 2637, Column 63: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=38&u=http://www.nonstopmovies.com" target="_…

    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 2637, Column 63: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=38&u=http://www.nonstopmovies.com" target="_…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2637, Column 109: element "A" undefined
    …i?id=38&u=http://www.nonstopmovies.com" target="_blank">Non Stop Movies</a><br>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2637, Column 128: end tag for element "a" which is not open
    …i?id=38&u=http://www.nonstopmovies.com" target="_blank">Non Stop Movies</a><br>

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

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

  • Error Line 2637, Column 133: end tag for "br" omitted, but OMITTAG NO was specified
    …i?id=38&u=http://www.nonstopmovies.com" target="_blank">Non Stop Movies</a><br>

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

  • Info Line 2637, Column 129: start tag was here
    …i?id=38&u=http://www.nonstopmovies.com" target="_blank">Non Stop Movies</a><br>
  • Warning Line 2638, Column 63: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=20&u=http://www.eutopiamovies.com" target="_…

    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 2638, Column 63: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=20&u=http://www.eutopiamovies.com" target="_…

    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 2638, Column 63: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=20&u=http://www.eutopiamovies.com" target="_…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2638, Column 109: element "A" undefined
    …gi?id=20&u=http://www.eutopiamovies.com" target="_blank">Eutopia Movies</a><br>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2638, Column 127: end tag for element "a" which is not open
    …gi?id=20&u=http://www.eutopiamovies.com" target="_blank">Eutopia Movies</a><br>

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

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

  • Error Line 2638, Column 132: end tag for "br" omitted, but OMITTAG NO was specified
    …gi?id=20&u=http://www.eutopiamovies.com" target="_blank">Eutopia Movies</a><br>

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

  • Info Line 2638, Column 128: start tag was here
    …gi?id=20&u=http://www.eutopiamovies.com" target="_blank">Eutopia Movies</a><br>
  • Warning Line 2639, Column 63: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=57&u=http://www.rawthumbs.com" target="_blan…

    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 2639, Column 63: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=57&u=http://www.rawthumbs.com" target="_blan…

    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 2639, Column 63: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=57&u=http://www.rawthumbs.com" target="_blan…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2639, Column 105: element "A" undefined
    …a2/out.cgi?id=57&u=http://www.rawthumbs.com" target="_blank">Raw Thumbs</a><br>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2639, Column 119: end tag for element "a" which is not open
    …a2/out.cgi?id=57&u=http://www.rawthumbs.com" target="_blank">Raw Thumbs</a><br>

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

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

  • Error Line 2639, Column 124: end tag for "br" omitted, but OMITTAG NO was specified
    …a2/out.cgi?id=57&u=http://www.rawthumbs.com" target="_blank">Raw Thumbs</a><br>

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

  • Info Line 2639, Column 120: start tag was here
    …a2/out.cgi?id=57&u=http://www.rawthumbs.com" target="_blank">Raw Thumbs</a><br>
  • Warning Line 2640, Column 63: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=15&u=http://www.lesbianpornvideos.com" targe…

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

  • Warning Line 2640, Column 63: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=15&u=http://www.lesbianpornvideos.com" targe…

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

  • Error Line 2640, Column 63: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=15&u=http://www.lesbianpornvideos.com" targe…

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

  • Info Line 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2640, Column 113: element "A" undefined
    …u=http://www.lesbianpornvideos.com" target="_blank">Lesbian Porn Videos</a><br>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2640, Column 136: end tag for element "a" which is not open
    …u=http://www.lesbianpornvideos.com" target="_blank">Lesbian Porn Videos</a><br>

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

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

  • Error Line 2640, Column 141: end tag for "br" omitted, but OMITTAG NO was specified
    …u=http://www.lesbianpornvideos.com" target="_blank">Lesbian Porn Videos</a><br>

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

  • Info Line 2640, Column 137: start tag was here
    …u=http://www.lesbianpornvideos.com" target="_blank">Lesbian Porn Videos</a><br>
  • Warning Line 2641, Column 63: reference not terminated by REFC delimiter
    …exoasis.com/cgi-bin/a2/out.cgi?id=63&u=http://www.perversius.com" target="_bla…

    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 2641, Column 63: reference to external entity in attribute value
    …exoasis.com/cgi-bin/a2/out.cgi?id=63&u=http://www.perversius.com" target="_bla…

    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 2641, Column 63: reference to entity "u" for which no system identifier could be generated
    …exoasis.com/cgi-bin/a2/out.cgi?id=63&u=http://www.perversius.com" target="_bla…

    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 2523, Column 90: entity was defined here
    ….sexoasis.com/cgi-bin/a2/out.cgi?id=11&u=http://www.youngpornvideos.com" targe…
  • Error Line 2641, Column 106: element "A" undefined
    …2/out.cgi?id=63&u=http://www.perversius.com" target="_blank">Perversius</a><br>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 2641, Column 120: end tag for element "a" which is not open
    …2/out.cgi?id=63&u=http://www.perversius.com" target="_blank">Perversius</a><br>

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

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

  • Error Line 2641, Column 125: end tag for "br" omitted, but OMITTAG NO was specified
    …2/out.cgi?id=63&u=http://www.perversius.com" target="_blank">Perversius</a><br>

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

  • Info Line 2641, Column 121: start tag was here
    …2/out.cgi?id=63&u=http://www.perversius.com" target="_blank">Perversius</a><br>
  • Error Line 2642, Column 5: end tag for "A" omitted, but OMITTAG NO was specified
    </td>

    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 2641, Column 4: start tag was here
    35 <A href="http://www.sexoasis.com/cgi-bin/a2/out.cgi?id=63&u=http://www.perve…
  • Error Line 2642, Column 5: end tag for "A" omitted, but OMITTAG NO was specified
    </td>

    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 2640, Column 4: start tag was here
    30 <A href="http://www.sexoasis.com/cgi-bin/a2/out.cgi?id=15&u=http://www.lesbi…
  • Error Line 2642, Column 5: end tag for "A" omitted, but OMITTAG NO was specified
    </td>

    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 2639, Column 4: start tag was here
    25 <A href="http://www.sexoasis.com/cgi-bin/a2/out.cgi?id=57&u=http://www.rawth…
  • Error Line 2642, Column 5: end tag for "A" omitted, but OMITTAG NO was specified
    </td>

    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 2638, Column 4: start tag was here
    20 <A href="http://www.sexoasis.com/cgi-bin/a2/out.cgi?id=20&u=http://www.eutop…
  • Error Line 2642, Column 5: end tag for "A" omitted, but OMITTAG NO was specified
    </td>

    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 2637, Column 4: start tag was here
    15 <A href="http://www.sexoasis.com/cgi-bin/a2/out.cgi?id=38&u=http://www.nonst…
  • Error Line 2642, Column 5: end tag for "A" omitted, but OMITTAG NO was specified
    </td>

    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 2636, Column 4: start tag was here
    10 <A href="http://www.sexoasis.com/cgi-bin/a2/out.cgi?id=27&u=http://www.zuzaz…
  • Error Line 2642, Column 5: end tag for "A" omitted, but OMITTAG NO was specified
    </td>

    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 2635, Column 4: start tag was here
    05 <A href="http://www.sexoasis.com/cgi-bin/a2/out.cgi?id=13&u=http://www.asspo…
  • Error Line 2648, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

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

  • Info Line 2648, Column 1: start tag was here
    <br>
  • Error Line 2653, 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.

  • Error Line 2655, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

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

  • Info Line 2655, Column 1: start tag was here
    <br>
  • Error Line 2676, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br>

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

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

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

  • Info Line 2676, Column 5: start tag was here
    <br><br>
  • Error Line 2677, Column 153: end tag for "br" omitted, but OMITTAG NO was specified
    … site are not responsible for any action taken by its members on this site.<br>

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

  • Info Line 2677, Column 149: start tag was here
    … site are not responsible for any action taken by its members on this site.<br>
  • Error Line 2678, Column 123: end tag for "br" omitted, but OMITTAG NO was specified
    …ed, or posted is the sole responsibility of the person(s) who submitted it.<br>

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

  • Info Line 2678, Column 119: start tag was here
    …ed, or posted is the sole responsibility of the person(s) who submitted it.<br>

Visitor Analysis

Daily Visitor
  • 2.333 visits