zoo porn movies beastiality videos beastiality free animal sex galleries beastiality zoosex amateur pictures ...

zoodump.com
  • Domain Name
    zoodump.com
  • Favicon
  • Google Page Rank
    1
  • Alexa Rank
    #27565
  • Page Size
    50.2 KB
  • Ip Address
    46.246.122.11
  • Heading
    H1: 1, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 98 JPG, 0 PNG

Website Meta Analysis

  • Title
    animal porn dump - animal fuck movies, bestiality porn video, free horse sex pictures
  • Meta Keyword
    free,animal porn,horse porn,beastiality sex,dog porn,horse fuck,animal sex clips,beasiality porno tube video(movies),teens (mature) woman,sex,porn,fuck,porno,tube
  • Meta Description
    zoo porn movies beastiality videos beastiality free animal sex galleries beastiality zoosex amateur pictures

Technical Analysis

  • Webserver
    nginx/1.3.1
  • Ip Address
    46.246.122.11
  • Domain Age
    4 Years, 5 Months, 25 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx/1.3.1
  • date: Sun, 22 Sep 2013 23:29:21 GMT
  • content-type: text/html
  • connection: keep-alive
  • x-powered-by: PHP/5.2.17
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: ZOODUMP.COM

Registrant:
Hudolejev Andrei
Andrei ( email )
Kose 13-28
Narva
Ida-Virumaa,12415
EE
Tel. +372.5846501

Creation Date: 21-Apr-2009
Expiration Date: 21-Apr-2013

Domain servers in listed order:
ns1.zoodump.com
ns2.zoodump.com

Administrative Contact:
Hudolejev Andrei
Andrei ( email )
Kose 13-28
Narva
Ida-Virumaa,12415
EE
Tel. +372.5846501

Technical Contact:
Hudolejev Andrei
Andrei ( email )
Kose 13-28
Narva
Ida-Virumaa,12415
EE
Tel. +372.5846501

Billing Contact:
Hudolejev Andrei
Andrei ( email )
Kose 13-28
Narva
Ida-Virumaa,12415
EE
Tel. +372.5846501

Status:ACTIVE

DNS Analysis


DNS servers
ns1.zoodump.com [46.246.122.9]
ns2.zoodump.com [46.246.122.17]

DNS Records

Answer records
zoodump.com SOA
server: ns2.zoodump.com
email: admin@zoodump.com
serial: 1206623084
refresh: 10800
retry: 3600
expire: 432000
minimum ttl: 38400
1200s
zoodump.com NS  ns2.zoodump.com 1200s
zoodump.com NS  ns1.zoodump.com 1200s
zoodump.com A 46.246.122.11 1200s

Authority records

Additional records
ns2.zoodump.com A 46.246.122.17 1200s
ns1.zoodump.com A 46.246.122.9 1200s

IP 46.246.122.11 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 333 Errors
  • 7 Warnings
Ratio Text/Html
  • 0.7427782745616422
Message Error
  • Error Line 1, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
    <html>

    The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.

  • Warning Line 4, Column 73: NET-enabling start-tag requires SHORTTAG YES
    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />

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

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

  • Error Line 5, Column 52: document type does not allow element "META" here
    <meta http-equiv="Content-Language" content="en-us">

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

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

  • Warning Line 6, Column 67: NET-enabling start-tag requires SHORTTAG YES
    <link rel="shortcut icon" href="/favicon.ico" type="image/x-icon" />

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

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

  • Error Line 6, Column 67: document type does not allow element "LINK" here
    <link rel="shortcut icon" href="/favicon.ico" type="image/x-icon" />

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

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

  • Error Line 7, Column 145: document type does not allow element "META" here
    …os beastiality free animal sex galleries beastiality zoosex amateur pictures ">

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

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

  • Error Line 8, Column 195: document type does not allow element "META" here
    …iality porno tube video(movies),teens (mature) woman,sex,porn,fuck,porno,tube">

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

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

  • Error Line 9, Column 22: document type does not allow element "BASE" here
    <base target="_blank">

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

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

  • Error Line 10, Column 23: document type does not allow element "STYLE" here
    <style type="text/css">

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

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

  • Error Line 20, Column 7: end tag for element "HEAD" which is not open
    </head>

    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 21, Column 35: there is no attribute "TOPMARGIN"
    <body bgcolor="#000000" topmargin="0" bottommargin="0" leftmargin="0" rightmarg…

    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 21, Column 52: there is no attribute "BOTTOMMARGIN"
    …="#000000" topmargin="0" bottommargin="0" leftmargin="0" rightmargin="0" link=…

    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 21, Column 67: there is no attribute "LEFTMARGIN"
    …argin="0" bottommargin="0" leftmargin="0" rightmargin="0" link="#006699" vlink…

    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 21, Column 83: there is no attribute "RIGHTMARGIN"
    …margin="0" leftmargin="0" rightmargin="0" link="#006699" vlink="#006699" text=…

    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 21, Column 132: document type does not allow element "BODY" here
    …" leftmargin="0" rightmargin="0" link="#006699" vlink="#006699" text="#ffffff">

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

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

  • Warning Line 44, Column 68: cannot generate system identifier for general entity "u"
    … href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY2…

    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 44, Column 68: general entity "u" not defined and no default entity
    … href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY2…

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

  • Error Line 44, Column 69: reference to entity "u" for which no system identifier could be generated
    …href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Warning Line 44, Column 136: cannot generate system identifier for general entity "s"
    …b2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com/…

    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 44, Column 136: general entity "s" not defined and no default entity
    …b2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com/…

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

  • Error Line 44, Column 137: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 45, Column 69: reference to entity "u" for which no system identifier could be generated
    …href='/st/out.php?l=0.1.1.2907.16603&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 45, Column 137: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvei8xNjYwMy8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 45, Column 263: non SGML character number 146
    …ght='210' alt='Horse cumming into babe’s slit'><br>Horse cumming into babe’s s…

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

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

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

  • Error Line 45, Column 299: non SGML character number 146
    …be’s slit'><br>Horse cumming into babe’s slit</a><br><font class="style4">6 mi…

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

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

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

  • Error Line 46, Column 69: reference to entity "u" for which no system identifier could be generated
    …href='/st/out.php?l=0.1.2.2928.16620&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 46, Column 137: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvei8xNjYyMC8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 46, Column 261: non SGML character number 146
    …eight='210' alt='Hard cock tearing dog’s moist pussy'><br>Hard cock tearing do…

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

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

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

  • Error Line 46, Column 302: non SGML character number 146
    …moist pussy'><br>Hard cock tearing dog’s moist pussy</a><br><font class="style…

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

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

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

  • Error Line 49, Column 69: reference to entity "u" for which no system identifier could be generated
    …href='/st/out.php?l=0.1.3.2920.16607&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 49, Column 137: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvYWUvMTY2MDcv~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 49, Column 260: non SGML character number 146
    … height='210' alt='Pony drilling fella’s tight asshole'><br>Pony drilling fell…

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

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

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

  • Error Line 49, Column 301: non SGML character number 146
    …tight asshole'><br>Pony drilling fella’s tight asshole</a><br><font class="sty…

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

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

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

  • Error Line 50, Column 69: reference to entity "u" for which no system identifier could be generated
    …href='/st/out.php?l=0.1.4.2909.16601&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 50, Column 137: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvay8xNjYwMS8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 51, Column 69: reference to entity "u" for which no system identifier could be generated
    …href='/st/out.php?l=0.1.5.2237.16116&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 51, Column 137: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvYWYvMTYxMTYv~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 54, Column 69: reference to entity "u" for which no system identifier could be generated
    …href='/st/out.php?l=0.1.6.2913.16544&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 54, Column 137: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvby8xNjU0NC8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 54, Column 244: non SGML character number 146
    …'1' width='310' height='210' alt='Stud’s cum running out from slit'><br>Stud’s…

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

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

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

  • Error Line 54, Column 282: non SGML character number 146
    …’s cum running out from slit'><br>Stud’s cum running out from slit</a><br><fon…

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

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

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

  • Error Line 55, Column 69: reference to entity "u" for which no system identifier could be generated
    …href='/st/out.php?l=0.1.7.2919.16615&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 55, Column 137: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvZi8xNjYxNS8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 56, Column 69: reference to entity "u" for which no system identifier could be generated
    …href='/st/out.php?l=0.1.8.2926.16623&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 56, Column 137: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvaS8xNjYyMy8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 59, Column 71: reference to entity "u" for which no system identifier could be generated
    …ef='/st/out.php?l=0.1.9.2915.16591.t&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 59, Column 139: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvcy8xNjU5MS8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 60, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.10.2927.16618&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 60, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkveS8xNjYxOC8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 61, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.11.2908.16602&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 61, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvaC8xNjYwMi8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 64, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.12.3022.17027&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 64, Column 130: reference to entity "s" for which no system identifier could be generated
    …DovL3pvb2R1bXAuY29tL2Z0dDIvby5waHA=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 64, Column 257: non SGML character number 146
    …ght='210' alt='Chimpanzee licking girl’s slit clean'><br>Chimpanzee licking gi…

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

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

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

  • Error Line 64, Column 299: non SGML character number 146
    …lit clean'><br>Chimpanzee licking girl’s slit clean</a><br><font class="style4…

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

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

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

  • Error Line 65, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.13.2933.16605&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 65, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvaC8xNjYwNS8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 66, Column 72: reference to entity "u" for which no system identifier could be generated
    …f='/st/out.php?l=0.1.14.2557.12864.t&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 66, Column 140: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvei8xMjg2NC8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 69, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.15.2546.12187&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 69, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkveC8xNjU3OS8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 70, Column 68: reference to entity "u" for which no system identifier could be generated
    … href='/st/out.php?l=0.1.16.592.5103&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 70, Column 136: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvai81MTAzLw==~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 71, Column 69: reference to entity "u" for which no system identifier could be generated
    …href='/st/out.php?l=0.1.17.2225.9973&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 71, Column 137: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvdC85OTczLw==~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 71, Column 255: non SGML character number 146
    …10' height='210' alt='Male fucking dog’s asshole'><br>Male fucking dog’s assho…

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

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

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

  • Error Line 71, Column 287: non SGML character number 146
    …ng dog’s asshole'><br>Male fucking dog’s asshole</a><br><font class="style4">1…

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

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

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

  • Error Line 74, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.18.442.1611.t&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 74, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvYy8xNjExLw==~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 75, Column 71: reference to entity "u" for which no system identifier could be generated
    …ef='/st/out.php?l=0.1.19.2132.8895.t&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 75, Column 139: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvci84ODk1Lw==~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 76, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.20.2939.16631&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 76, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvdC8xNjYzMS8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 79, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.21.2894.16510&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 79, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvZy8xNjUxMC8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 79, Column 264: non SGML character number 146
    …ght='210' alt='Horny dog spearing slut’s cunt'><br>Horny dog spearing slut’s c…

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

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

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

  • Error Line 79, Column 300: non SGML character number 146
    …ut’s cunt'><br>Horny dog spearing slut’s cunt</a><br><font class="style4">4 mi…

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

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

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

  • Error Line 80, Column 69: reference to entity "u" for which no system identifier could be generated
    …href='/st/out.php?l=0.1.22.2217.7402&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 80, Column 137: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvby83NDAyLw==~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 80, Column 263: non SGML character number 146
    …ht='210' alt='Dick rubbing against dog’s slit'><br>Dick rubbing against dog’s …

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

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

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

  • Error Line 80, Column 300: non SGML character number 146
    …g’s slit'><br>Dick rubbing against dog’s slit</a><br><font class="style4">2 mi…

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

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

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

  • Error Line 81, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.23.2936.16624&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 81, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvby8xNjYyNC8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 84, Column 69: reference to entity "u" for which no system identifier could be generated
    …href='/st/out.php?l=0.1.24.2215.7663&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 84, Column 137: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvby83NjYzLw==~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 84, Column 259: non SGML character number 146
    …height='210' alt='Cock deep inside dog’s slit'><br>Cock deep inside dog’s slit…

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

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

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

  • Error Line 84, Column 292: non SGML character number 146
    …e dog’s slit'><br>Cock deep inside dog’s slit</a><br><font class="style4">1 mi…

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

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

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

  • Error Line 85, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.25.2192.16547&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 85, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvcC8xNjU0Ny8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 86, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.26.2921.16617&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 86, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvcS8xNjYxNy8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 89, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.27.2899.13732&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 89, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvYWIvMTM3MzIv~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 90, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.28.2258.12455&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 90, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkveS8xMjQ1NS8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 91, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.29.2929.16628&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 91, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvcS8xNjYyOC8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 91, Column 261: non SGML character number 146
    …height='210' alt='Horse filling blonde’s mouth with cum'><br>Horse filling blo…

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

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

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

  • Error Line 91, Column 304: non SGML character number 146
    …uth with cum'><br>Horse filling blonde’s mouth with cum</a><br><font class="st…

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

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

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

  • Warning Line 100, Column 32: cannot generate system identifier for general entity "perm"
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…

    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 100, Column 32: general entity "perm" not defined and no default entity
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…

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

  • Error Line 100, Column 36: reference to entity "perm" for which no system identifier could be generated
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 100, Column 106: required attribute "ALT" not specified
    …m/ftt2/toplists/img/zooxmania.com.jpg"><br>Animal Porn Movies</a><br>18138 Mov…

    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 104, Column 36: reference to entity "perm" for which no system identifier could be generated
    <a href="/ftt2/o.php?l=toplist&perm=456"><img src="http://zoodump.com/ftt2/topl…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 104, Column 105: required attribute "ALT" not specified
    …com/ftt2/toplists/img/k9beast.com.jpg"><br>K9beast</a><br>11183 Movies<br></fo…

    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 108, Column 36: reference to entity "perm" for which no system identifier could be generated
    <a href="/ftt2/o.php?l=toplist&perm=190"><img src="http://zoodump.com/ftt2/topl…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 108, Column 110: required attribute "ALT" not specified
    …tt2/toplists/img/animalporntv.com.jpg"><br>Animal Porn TV</a><br>11576 Movies<…

    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 112, Column 36: reference to entity "perm" for which no system identifier could be generated
    <a href="/ftt2/o.php?l=toplist&perm=42"><img src="http://zoodump.com/ftt2/topli…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 112, Column 109: required attribute "ALT" not specified
    …tt2/toplists/img/animalxclips.com.jpg"><br>Animal Sex Videos</a><br>13468 Movi…

    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 119, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.30.2233.12435&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 119, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkveS8xMjQzNS8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 119, Column 257: non SGML character number 146
    …10' height='210' alt='Exploring animal’s wet slit'><br>Exploring animal’s wet …

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

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

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

  • Error Line 119, Column 290: non SGML character number 146
    …nimal’s wet slit'><br>Exploring animal’s wet slit</a><br><font class="style4">…

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

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

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

  • Error Line 120, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.31.2181.11625&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 120, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvdy8xMTYyNS8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 120, Column 261: non SGML character number 146
    …height='210' alt='Babe jerking off dog’s cock'><br>Babe jerking off dog’s cock…

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

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

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

  • Error Line 120, Column 294: non SGML character number 146
    …f dog’s cock'><br>Babe jerking off dog’s cock</a><br><font class="style4">6 mi…

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

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

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

  • Error Line 121, Column 69: reference to entity "u" for which no system identifier could be generated
    …href='/st/out.php?l=0.1.32.2174.8947&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 121, Column 137: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvci84OTQ3Lw==~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 124, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.33.2990.16881&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 124, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2Z0dDIvby5waHA/bD1nYWxz~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 125, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.34.2946.16625&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 125, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvbC8xNjYyNS8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 125, Column 254: non SGML character number 146
    …='310' height='210' alt='Exploring dog’s asshole with a dick'><br>Exploring do…

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

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

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

  • Error Line 125, Column 295: non SGML character number 146
    …asshole with a dick'><br>Exploring dog’s asshole with a dick</a><br><font clas…

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

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

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

  • Error Line 126, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.35.293.2561.t&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 126, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvZS8yNTYxLw==~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 129, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.36.2937.16608&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 129, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvcS8xNjYwOC8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 130, Column 72: reference to entity "u" for which no system identifier could be generated
    …f='/st/out.php?l=0.1.37.2935.16627.t&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 130, Column 140: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvay8xNjYyNy8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 131, Column 68: reference to entity "u" for which no system identifier could be generated
    … href='/st/out.php?l=0.1.38.563.3416&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 131, Column 136: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvZy8zNDE2Lw==~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 134, Column 68: reference to entity "u" for which no system identifier could be generated
    … href='/st/out.php?l=0.1.39.218.2280&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 134, Column 136: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvZS8yMjgwLw==~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 135, Column 69: reference to entity "u" for which no system identifier could be generated
    …href='/st/out.php?l=0.1.40.2221.7225&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 135, Column 137: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvby83MjI1Lw==~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 136, Column 69: reference to entity "u" for which no system identifier could be generated
    …href='/st/out.php?l=0.1.41.171.575.t&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 136, Column 133: reference to entity "s" for which no system identifier could be generated
    …3pvb2R1bXAuY29tL2dhbGxlcnkvYS81NzUv~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 139, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.42.2911.16579&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 139, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvdy8xNjU3OS8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 140, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.43.2892.14211&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 140, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvYWIvMTQyMTEv~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 141, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.44.2246.13100&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 141, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvei8xMzEwMC8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 144, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.45.2940.16613&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 144, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvaC8xNjYxMy8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 145, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.46.2932.16626&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 145, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvcC8xNjYyNi8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 146, Column 69: reference to entity "u" for which no system identifier could be generated
    …href='/st/out.php?l=0.1.47.207.209.t&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 146, Column 133: reference to entity "s" for which no system identifier could be generated
    …3pvb2R1bXAuY29tL2dhbGxlcnkvYS8yMDkv~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 149, Column 69: reference to entity "u" for which no system identifier could be generated
    …href='/st/out.php?l=0.1.48.2185.7049&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 149, Column 137: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvbi83MDQ5Lw==~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 150, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.49.2917.16595&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 150, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkveS8xNjU5NS8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 150, Column 258: non SGML character number 146
    …0' height='210' alt='Male spearing dog’s anal hole'><br>Male spearing dog’s an…

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

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

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

  • Error Line 150, Column 293: non SGML character number 146
    …dog’s anal hole'><br>Male spearing dog’s anal hole</a><br><font class="style4"…

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

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

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

  • Error Line 151, Column 68: reference to entity "u" for which no system identifier could be generated
    … href='/st/out.php?l=0.1.50.546.9014&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 151, Column 136: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvci85MDE0Lw==~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 154, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.51.2931.16609&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 154, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvYWMvMTY2MDkv~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 155, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.52.2232.16402&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 155, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvYWcvMTY0MDIv~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 156, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.53.2897.16536&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 156, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvYWcvMTY1MzYv~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 159, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.54.2253.15068&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 159, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvYWQvMTUwNjgv~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 160, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.55.2925.16614&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 160, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvcC8xNjYxNC8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 161, Column 69: reference to entity "u" for which no system identifier could be generated
    …href='/st/out.php?l=0.1.56.2226.8943&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 161, Column 137: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvci84OTQzLw==~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 161, Column 256: non SGML character number 146
    …0' height='210' alt='Dog licking fella’s schlong'><br>Dog licking fella’s schl…

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

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

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

  • Error Line 161, Column 289: non SGML character number 146
    …fella’s schlong'><br>Dog licking fella’s schlong</a><br><font class="style4">1…

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

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

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

  • Error Line 164, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.57.2923.16621&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 164, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvYWMvMTY2MjEv~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 164, Column 253: non SGML character number 146
    …th='310' height='210' alt='Tearing dog’s ass with hard cock'><br>Tearing dog’s…

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

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

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

  • Error Line 164, Column 291: non SGML character number 146
    …’s ass with hard cock'><br>Tearing dog’s ass with hard cock</a><br><font class…

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

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

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

  • Error Line 165, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.58.2910.16554&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 165, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvZy8xNjU1NC8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 166, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.59.2944.16610&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 166, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvaS8xNjYxMC8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 166, Column 244: non SGML character number 146
    …='1' width='310' height='210' alt='Dog’s cock inside babe&#039;s moist slit'><…

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

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

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

  • Error Line 166, Column 290: non SGML character number 146
    …inside babe&#039;s moist slit'><br>Dog’s cock inside babe&#039;s moist slit</a…

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

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

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

  • Error Line 175, Column 36: reference to entity "perm" for which no system identifier could be generated
    <a href="/ftt2/o.php?l=toplist&perm=345"><img src="http://zoodump.com/ftt2/topl…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 175, Column 109: required attribute "ALT" not specified
    …ftt2/toplists/img/animalsex19.com.jpg"><br>Animal Sex 19</a><br>8115 Movies<br…

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

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

  • Error Line 179, Column 36: reference to entity "perm" for which no system identifier could be generated
    <a href="/ftt2/o.php?l=toplist&perm=227"><img src="http://zoodump.com/ftt2/topl…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 179, Column 103: required attribute "ALT" not specified
    …p.com/ftt2/toplists/img/zoosex.tv.jpg"><br>Zoo Sex Videos</a><br>6598 Movies<b…

    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 183, Column 36: reference to entity "perm" for which no system identifier could be generated
    <a href="/ftt2/o.php?l=toplist&perm=10"><img src="http://zoodump.com/ftt2/topli…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 183, Column 108: required attribute "ALT" not specified
    …ftt2/toplists/img/youngzoosex.com.jpg"><br>Young Zoo Sex</a><br>2878 Movies<br…

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

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

  • Error Line 187, Column 36: reference to entity "perm" for which no system identifier could be generated
    <a href="/ftt2/o.php?l=toplist&perm=179"><img src="http://zoodump.com/ftt2/topl…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 187, Column 112: required attribute "ALT" not specified
    …2/toplists/img/bizarresextube.net.jpg"><br>Bizarre Sex Tube</a><br>1760 Movies…

    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 194, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.60.2240.15790&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 194, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvYWYvMTU3OTAv~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 195, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.61.2924.16629&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 195, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvcy8xNjYyOS8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 195, Column 249: non SGML character number 146
    …width='310' height='210' alt='Huge dog’s dick makes her moan'><br>Huge dog’s d…

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

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

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

  • Error Line 195, Column 285: non SGML character number 146
    …og’s dick makes her moan'><br>Huge dog’s dick makes her moan</a><br><font clas…

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

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

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

  • Error Line 196, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.62.823.8288.t&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 196, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvcS84Mjg4Lw==~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 196, Column 258: non SGML character number 146
    …' height='210' alt='Mouth full of stud’s sperm'><br>Mouth full of stud’s sperm…

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

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

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

  • Error Line 196, Column 290: non SGML character number 146
    …f stud’s sperm'><br>Mouth full of stud’s sperm</a><br><font class="style4">8 m…

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

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

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

  • Error Line 199, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.63.2251.15047&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 199, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvYWQvMTUwNDcv~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 200, Column 69: reference to entity "u" for which no system identifier could be generated
    …href='/st/out.php?l=0.1.64.39.1849.t&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 200, Column 137: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvZC8xODQ5Lw==~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 201, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.65.2193.10776&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 201, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvdi8xMDc3Ni8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 204, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.66.2934.16622&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 204, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvYWEvMTY2MjIv~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 205, Column 65: reference to entity "u" for which no system identifier could be generated
    …><a href='/st/out.php?l=0.1.67.347.1&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 205, Column 129: reference to entity "s" for which no system identifier could be generated
    …3pvb2R1bXAuY29tL2dhbGxlcnkvYS8xLw==~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 206, Column 69: reference to entity "u" for which no system identifier could be generated
    …href='/st/out.php?l=0.1.68.2199.9470&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 206, Column 137: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvcy85NDcwLw==~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 209, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.69.2916.16577&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 209, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvbS8xNjU3Ny8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 210, Column 67: reference to entity "u" for which no system identifier could be generated
    …a href='/st/out.php?l=0.1.70.132.901&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 210, Column 131: reference to entity "s" for which no system identifier could be generated
    …3pvb2R1bXAuY29tL2dhbGxlcnkvYi85MDEv~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 211, Column 69: reference to entity "u" for which no system identifier could be generated
    …href='/st/out.php?l=0.1.71.440.489.t&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 211, Column 133: reference to entity "s" for which no system identifier could be generated
    …3pvb2R1bXAuY29tL2dhbGxlcnkvYS80ODkv~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 214, Column 69: reference to entity "u" for which no system identifier could be generated
    …href='/st/out.php?l=0.1.72.2135.7892&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 214, Column 137: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvcC83ODkyLw==~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 215, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.73.2243.13548&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 215, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvYWEvMTM1NDgv~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 215, Column 245: non SGML character number 146
    …='1' width='310' height='210' alt='She’s ready to fuck with a dog'><br>She’s r…

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

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

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

  • Error Line 215, Column 281: non SGML character number 146
    …he’s ready to fuck with a dog'><br>She’s ready to fuck with a dog</a><br><font…

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

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

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

  • Error Line 216, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.74.2244.13907&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 216, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvYWIvMTM5MDcv~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 216, Column 265: non SGML character number 146
    …ght='210' alt='Ready to experience dog’s dick'><br>Ready to experience dog’s d…

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

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

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

  • Error Line 216, Column 301: non SGML character number 146
    …og’s dick'><br>Ready to experience dog’s dick</a><br><font class="style4">7 mi…

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

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

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

  • Error Line 219, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.75.2396.12077&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 219, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkveC8xMjA3Ny8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 220, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.76.2945.16606&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 220, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvay8xNjYwNi8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 221, Column 72: reference to entity "u" for which no system identifier could be generated
    …f='/st/out.php?l=0.1.77.2904.14412.t&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 221, Column 140: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvYWMvMTQ0MTIv~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 224, Column 68: reference to entity "u" for which no system identifier could be generated
    … href='/st/out.php?l=0.1.78.444.1487&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 224, Column 136: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvYy8xNDg3Lw==~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 225, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.79.2219.10859&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 225, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvdi8xMDg1OS8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 226, Column 67: reference to entity "u" for which no system identifier could be generated
    …a href='/st/out.php?l=0.1.80.193.104&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 226, Column 131: reference to entity "s" for which no system identifier could be generated
    …3pvb2R1bXAuY29tL2dhbGxlcnkvYS8xMDQv~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 226, Column 236: non SGML character number 146
    …'1' width='310' height='210' alt='Stud’s dick inside warm cunt'><br>Stud’s dic…

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

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

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

  • Error Line 226, Column 270: non SGML character number 146
    …Stud’s dick inside warm cunt'><br>Stud’s dick inside warm cunt</a><br><font cl…

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

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

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

  • Error Line 229, Column 68: reference to entity "u" for which no system identifier could be generated
    … href='/st/out.php?l=0.1.81.501.9718&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 229, Column 136: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvdC85NzE4Lw==~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 230, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.82.2318.13267&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 230, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvYWEvMTMyNjcv~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 230, Column 246: non SGML character number 146
    …'1' width='310' height='210' alt='Stud’s dick inside moist cunt'><br>Stud’s di…

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

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

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

  • Error Line 230, Column 281: non SGML character number 146
    …tud’s dick inside moist cunt'><br>Stud’s dick inside moist cunt</a><br><font c…

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

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

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

  • Error Line 231, Column 71: reference to entity "u" for which no system identifier could be generated
    …ef='/st/out.php?l=0.1.83.2180.9578.t&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 231, Column 139: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvcy85NTc4Lw==~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 234, Column 67: reference to entity "u" for which no system identifier could be generated
    …a href='/st/out.php?l=0.1.84.83.15.t&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 234, Column 131: reference to entity "s" for which no system identifier could be generated
    …3pvb2R1bXAuY29tL2dhbGxlcnkvYS8xNS8=~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 234, Column 255: non SGML character number 146
    …ht='210' alt='Big dog penetrating babe’s slit'><br>Big dog penetrating babe’s …

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

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

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

  • Error Line 234, Column 292: non SGML character number 146
    …e’s slit'><br>Big dog penetrating babe’s slit</a><br><font class="style4">1 mi…

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

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

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

  • Error Line 235, Column 67: reference to entity "u" for which no system identifier could be generated
    …a href='/st/out.php?l=0.1.85.63.1377&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 235, Column 135: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvYy8xMzc3Lw==~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 236, Column 67: reference to entity "u" for which no system identifier could be generated
    …a href='/st/out.php?l=0.1.86.153.840&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 236, Column 131: reference to entity "s" for which no system identifier could be generated
    …3pvb2R1bXAuY29tL2dhbGxlcnkvYi84NDAv~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 239, Column 69: reference to entity "u" for which no system identifier could be generated
    …href='/st/out.php?l=0.1.87.2175.8737&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 239, Column 137: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvci84NzM3Lw==~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 240, Column 70: reference to entity "u" for which no system identifier could be generated
    …ref='/st/out.php?l=0.1.88.2241.14869&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 240, Column 138: reference to entity "s" for which no system identifier could be generated
    …2R1bXAuY29tL2dhbGxlcnkvYWQvMTQ4Njkv~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 241, Column 67: reference to entity "u" for which no system identifier could be generated
    …a href='/st/out.php?l=0.1.89.139.141&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY29…

    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 44, Column 67: entity was defined here
    …a href='/st/out.php?l=0.1.0.2222.16576&u=ftt2/o.php?url=~aHR0cDovL3pvb2R1bXAuY…
  • Error Line 241, Column 131: reference to entity "s" for which no system identifier could be generated
    …3pvb2R1bXAuY29tL2dhbGxlcnkvYS8xNDEv~&s=s2'><img src='http://img1.zoodump.com/s…

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

  • Info Line 44, Column 135: entity was defined here
    …vb2R1bXAuY29tL2dhbGxlcnkvdi8xNjU3Ni8=~&s=s2'><img src='http://img1.zoodump.com…
  • Error Line 241, Column 235: non SGML character number 146
    …='1' width='310' height='210' alt='Dog’s dick for her throat'><br>Dog’s dick f…

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

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

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

  • Error Line 241, Column 266: non SGML character number 146
    …lt='Dog’s dick for her throat'><br>Dog’s dick for her throat</a><br><font clas…

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

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

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

  • Error Line 249, Column 41: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=335">Animal Porn Clips</a><br>02 - <a h…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 249, Column 112: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=80">Animal Porn Movies</a><br>03 - <a h…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 249, Column 183: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=456">K9beast</a><br>04 - <a href="/ftt2…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 249, Column 244: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=190">Animal Porn TV</a><br>05 - <a href…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 249, Column 312: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=42">Animal Sex Videos</a><br>06 - <a hr…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 249, Column 382: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=345">Animal Sex 19</a><br>07 - <a href=…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 249, Column 449: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=227">Zoo Sex Videos</a><br>08 - <a href…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 249, Column 517: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=10">Young Zoo Sex</a><br>09 - <a href="…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 249, Column 583: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=179">Bizarre Sex Tube</a><br>10 - <a hr…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 249, Column 653: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=215">Beast hub</a><br>11 - <a href="/ft…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 249, Column 716: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=225">zoo porn</a><br>12 - <a href="/ftt…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 249, Column 778: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=198">Rare Zoo Video</a><br>13 - <a href…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 249, Column 846: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=84">G Zoo</a><br>14 - <a href="/ftt2/o.…

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

  • Info Line 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 249, Column 904: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=475">Sex animal</a><br>15 - <a href="/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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 249, Column 968: reference to entity "perm" for which no system identifier could be generated
    …>15 - <a href="/ftt2/o.php?l=toplist&perm=369">Extremal Tube</a><br></font></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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 253, Column 41: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=154">Mega Zoo Funs</a><br>17 - <a href=…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 253, Column 108: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=169">Animal Sex Clips</a><br>18 - <a hr…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 253, Column 178: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=72">NL ZOO Porn</a><br>19 - <a href="/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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 253, Column 242: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=165">Zoo Sex Videos</a><br>20 - <a href…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 253, Column 310: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=11">Extreme Sex 4 All</a><br>21 - <a hr…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 253, Column 380: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=341">Free Sex Tube</a><br>22 - <a href=…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 253, Column 447: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=184">Animal Sex TV</a><br>23 - <a href=…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 253, Column 514: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=205">Home Animal Pics</a><br>24 - <a hr…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 253, Column 584: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=5">Your Freak Tube</a><br>25 - <a href=…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 253, Column 651: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=219">Zoo Tube Here</a><br>26 - <a href=…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 253, Column 718: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=197">Bizarre ZOO TV</a><br>27 - <a href…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 253, Column 786: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=214">Free Bestiality Tube</a><br>28 - <…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 253, Column 860: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=213">Zoo Porn Tube</a><br>29 - <a href=…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 253, Column 927: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=254">Zoo Attack Porn</a><br>30 - <a hre…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 253, Column 996: reference to entity "perm" for which no system identifier could be generated
    …/a><br>30 - <a href="/ftt2/o.php?l=toplist&perm=55">Zoo Here</a><br></font></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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 257, Column 41: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=346">Free Animal Porn</a><br>32 - <a hr…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 257, Column 111: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=195">Zoo Sex Here</a><br>33 - <a href="…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 257, Column 177: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=243">Brutal Zoo Porn</a><br>34 - <a hre…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 257, Column 246: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=242">Cruel Zoo Porn</a><br>35 - <a href…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 257, Column 314: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=124">Pets Movies</a><br>36 - <a href="/…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 257, Column 379: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=115">Extreme Dog Sex</a><br>37 - <a hre…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 257, Column 448: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=250">HQ Farm Sex</a><br>38 - <a href="/…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 257, Column 513: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=138">Zoo Area</a><br>39 - <a href="/ftt…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 257, Column 575: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=122">Fuck Zoo</a><br>40 - <a href="/ftt…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 257, Column 637: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=316">Animal Zoo Tube</a><br>41 - <a hre…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 257, Column 706: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=251">Zoo Terror Porn</a><br>42 - <a hre…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 257, Column 775: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=439">X Rotten</a><br>43 - <a href="/ftt…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 257, Column 837: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=238">Zoo Pics And Movies</a><br>44 - <a…

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

  • Info Line 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 257, Column 910: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=83">Animal Romance</a><br>45 - <a href=…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 257, Column 977: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=349">Animal Porn Tube</a><br></font></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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 261, Column 41: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=287">Vip Animal Sex</a><br>47 - <a href…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 261, Column 109: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=353">Zoo Sex Galleries</a><br>48 - <a h…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 261, Column 180: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=224">Free Animal Sex</a><br>49 - <a hre…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 261, Column 249: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=212">Free Animal Tube</a><br>50 - <a hr…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 261, Column 319: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=6">Hot Bizarre Sex</a><br>51 - <a href=…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 261, Column 386: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=337">Free Animal Sex Movies</a><br>52 -…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 261, Column 462: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=249">Animal Porn</a><br>53 - <a href="/…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 261, Column 527: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=317">Free Animal Sex</a><br>54 - <a hre…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 261, Column 596: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=480">Dog Sex Tube</a><br>55 - <a href="…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 261, Column 662: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=8">Zoo Han</a><br>56 - <a href="/ftt2/o…

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

  • Info Line 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 261, Column 721: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=478">hardenimalsex</a><br>57 - <a href=…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 261, Column 788: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=246">Zoo Pic Post</a><br>58 - <a href="…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 261, Column 854: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=164">Hot Animal Porn</a><br>59 - <a hre…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 261, Column 923: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=362">Animal Sex Free</a><br>60 - <a hre…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 261, Column 992: reference to entity "perm" for which no system identifier could be generated
    … - <a href="/ftt2/o.php?l=toplist&perm=340">Free Animal Porn Clips</a><br></fo…

    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 100, Column 31: entity was defined here
    <a href="/ftt2/o.php?l=toplist&perm=80"><img src="http://zoodump.com/ftt2/topli…
  • Error Line 272, 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.

Visitor Analysis

Daily Visitor
  • 8.750 visits