tubekitty.com

Free Porn Movies - Tube Kitty ...

Display Widget for this domain on your website. Click Here
Processing update domain...

Overview Info

  • Domain Name
    tubekitty.com
  • Favicon
  • Alexa Rank
    #3928
  • Google Page Rank
    PR 3
  • Ip Address
    68.169.110.227
  • Page Size
    232.3 KB
  • Images
    4 GIF, 120 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 3 0 0 0 0

Website Meta Analysis

  • Title
    Free Porn Movies - Tube Kitty
  • Meta Keyword
    free porn movies,tube porn,free porn,tube kitty,porn movies,porn tube
  • Meta Description
    Free Porn Movies - Tube Kitty

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    68.169.110.227
  • Domain Age
    5 Years, 3 Months, 8 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Mon, 29 Jul 2013 00:39:25 GMT
  • server: Apache
  • connection: close
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: TUBEKITTY.COM
Registrar: MONIKER

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


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


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


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


Domain servers in listed order:

NS2.ISPRIME.COM
NS.ISPRIME.COM

Record created on: 2008-02-28 06:58:38.0
Database last updated on: 2011-05-17 04:36:22.223
Domain Expires on: 2021-02-28 06:58:38.0

DNS Analysis


DNS servers
ns.isprime.com [76.9.7.3]
ns2.isprime.com [66.230.160.1]

DNS Records

Answer records
tubekitty.com SOA
server: ns.isprime.com
email: support@isprime.com
serial: 1228832190
refresh: 16384
retry: 2048
expire: 1048576
minimum ttl: 2560
2560s
tubekitty.com MX
preference: 10
exchange: dog.isprime.com
3600s
tubekitty.com NS  ns2.isprime.com 172800s
tubekitty.com NS  ns.isprime.com 172800s
tubekitty.com A 68.169.97.36 60s

Authority records

Additional records
dog.isprime.com A 64.111.210.229 3600s
ns2.isprime.com A 66.230.160.1 172800s
ns.isprime.com A 76.9.7.3 172800s

IP 68.169.110.227 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 86 Errors
  • 58 Warnings
Ratio Text/Html
  • 0.8580761792651139
Message Error
  • Error Line 10, Column 31: required attribute "type" not specified
    	<script language="JavaScript">

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

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

  • Error Line 22, Column 39: required attribute "type" not specified
    </script><script language="JavaScript">

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

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

  • Warning Line 43, Column 34: character "&" is the first character of a delimiter but occurred as data
                else if(window.opera && window.print){ // OP

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 43, Column 35: character "&" is the first character of a delimiter but occurred as data
                else if(window.opera && window.print){ // OP

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 98, Column 55: character "&" is the first character of a delimiter but occurred as data
    		var p,i,x;if(!d) d=document; if((p=n.indexOf("?"))>0&&parent.frames.length) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 98, Column 57: cannot generate system identifier for general entity "parent.frames.length"
    		var p,i,x;if(!d) d=document; if((p=n.indexOf("?"))>0&&parent.frames.length) {

    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 98, Column 57: general entity "parent.frames.length" not defined and no default entity
    		var p,i,x;if(!d) d=document; if((p=n.indexOf("?"))>0&&parent.frames.length) {

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

  • Warning Line 98, Column 77: reference not terminated by REFC delimiter
    		var p,i,x;if(!d) d=document; if((p=n.indexOf("?"))>0&&parent.frames.length) {

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

  • Error Line 98, Column 77: reference to entity "parent.frames.length" for which no system identifier could be generated
    		var p,i,x;if(!d) d=document; if((p=n.indexOf("?"))>0&&parent.frames.length) {

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

  • Info Line 98, Column 56: entity was defined here
    		var p,i,x;if(!d) d=document; if((p=n.indexOf("?"))>0&&parent.frames.length) {
  • Warning Line 100, Column 15: character "&" is the first character of a delimiter but occurred as data
    		if(!(x=d[n])&&d.all) x=d.all[n]; for (i=0;!x&&i<d.forms.length;i++) x=d.forms…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 100, Column 17: cannot generate system identifier for general entity "d.all"
    		if(!(x=d[n])&&d.all) x=d.all[n]; for (i=0;!x&&i<d.forms.length;i++) x=d.forms…

    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 17: general entity "d.all" not defined and no default entity
    		if(!(x=d[n])&&d.all) x=d.all[n]; for (i=0;!x&&i<d.forms.length;i++) x=d.forms…

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

  • Warning Line 100, Column 22: reference not terminated by REFC delimiter
    		if(!(x=d[n])&&d.all) x=d.all[n]; for (i=0;!x&&i<d.forms.length;i++) x=d.forms…

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

  • Error Line 100, Column 22: reference to entity "d.all" for which no system identifier could be generated
    		if(!(x=d[n])&&d.all) x=d.all[n]; for (i=0;!x&&i<d.forms.length;i++) x=d.forms…

    This is usually a cascading error caused by a an 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 16: entity was defined here
    		if(!(x=d[n])&&d.all) x=d.all[n]; for (i=0;!x&&i<d.forms.length;i++) x=d.forms…
  • Warning Line 100, Column 47: character "&" is the first character of a delimiter but occurred as data
    …x=d[n])&&d.all) x=d.all[n]; for (i=0;!x&&i<d.forms.length;i++) x=d.forms[i][n];

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 100, Column 49: cannot generate system identifier for general entity "i"
    …x=d[n])&&d.all) x=d.all[n]; for (i=0;!x&&i<d.forms.length;i++) x=d.forms[i][n];

    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 49: general entity "i" not defined and no default entity
    …x=d[n])&&d.all) x=d.all[n]; for (i=0;!x&&i<d.forms.length;i++) x=d.forms[i][n];

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

  • Warning Line 100, Column 50: reference not terminated by REFC delimiter
    …x=d[n])&&d.all) x=d.all[n]; for (i=0;!x&&i<d.forms.length;i++) x=d.forms[i][n];

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

  • Error Line 100, Column 50: reference to entity "i" for which no system identifier could be generated
    …x=d[n])&&d.all) x=d.all[n]; for (i=0;!x&&i<d.forms.length;i++) x=d.forms[i][n];

    This is usually a cascading error caused by a an 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 48: entity was defined here
    …x=d[n])&&d.all) x=d.all[n]; for (i=0;!x&&i<d.forms.length;i++) x=d.forms[i][n];
  • Error Line 100, Column 65: character ";" not allowed in attribute specification list
    …x=d[n])&&d.all) x=d.all[n]; for (i=0;!x&&i<d.forms.length;i++) x=d.forms[i][n];
  • Error Line 100, Column 65: element "d.forms.length" undefined
    …x=d[n])&&d.all) x=d.all[n]; for (i=0;!x&&i<d.forms.length;i++) x=d.forms[i][n];

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 101, Column 13: character "&" is the first character of a delimiter but occurred as data
    		for(i=0;!x&&d.layers&&i<d.layers.length;i++) x=MM_findObj(n,d.layers[i].docum…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 101, Column 15: cannot generate system identifier for general entity "d.layers"
    		for(i=0;!x&&d.layers&&i<d.layers.length;i++) x=MM_findObj(n,d.layers[i].docum…

    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 101, Column 15: general entity "d.layers" not defined and no default entity
    		for(i=0;!x&&d.layers&&i<d.layers.length;i++) x=MM_findObj(n,d.layers[i].docum…

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

  • Warning Line 101, Column 23: reference not terminated by REFC delimiter
    		for(i=0;!x&&d.layers&&i<d.layers.length;i++) x=MM_findObj(n,d.layers[i].docum…

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

  • Error Line 101, Column 23: reference to entity "d.layers" for which no system identifier could be generated
    		for(i=0;!x&&d.layers&&i<d.layers.length;i++) x=MM_findObj(n,d.layers[i].docum…

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

  • Info Line 101, Column 14: entity was defined here
    		for(i=0;!x&&d.layers&&i<d.layers.length;i++) x=MM_findObj(n,d.layers[i].docum…
  • Warning Line 101, Column 23: character "&" is the first character of a delimiter but occurred as data
    		for(i=0;!x&&d.layers&&i<d.layers.length;i++) x=MM_findObj(n,d.layers[i].docum…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 101, Column 26: reference not terminated by REFC delimiter
    		for(i=0;!x&&d.layers&&i<d.layers.length;i++) x=MM_findObj(n,d.layers[i].docum…

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

  • Error Line 101, Column 26: reference to entity "i" for which no system identifier could be generated
    		for(i=0;!x&&d.layers&&i<d.layers.length;i++) x=MM_findObj(n,d.layers[i].docum…

    This is usually a cascading error caused by a an 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 48: entity was defined here
    …x=d[n])&&d.all) x=d.all[n]; for (i=0;!x&&i<d.forms.length;i++) x=d.forms[i][n];
  • Error Line 101, Column 42: character ";" not allowed in attribute specification list
    …or(i=0;!x&&d.layers&&i<d.layers.length;i++) x=MM_findObj(n,d.layers[i].documen…
  • Error Line 101, Column 42: element "d.layers.length" undefined
    …or(i=0;!x&&d.layers&&i<d.layers.length;i++) x=MM_findObj(n,d.layers[i].documen…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 102, Column 9: character "&" is the first character of a delimiter but occurred as data
    		if(!x && document.getElementById) x=document.getElementById(n); return x;

    This message may appear in several cases:

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

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 105, Column 13: end tag for "d.layers.length" omitted, but OMITTAG NO was specified
        </script>

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

  • Info Line 101, Column 26: start tag was here
    		for(i=0;!x&&d.layers&&i<d.layers.length;i++) x=MM_findObj(n,d.layers[i].docum…
  • Error Line 105, Column 13: end tag for "d.forms.length" omitted, but OMITTAG NO was specified
        </script>

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

  • Info Line 100, Column 50: start tag was here
    …x=d[n])&&d.all) x=d.all[n]; for (i=0;!x&&i<d.forms.length;i++) x=d.forms[i][n];
  • Error Line 123, Column 81: document type does not allow element "link" here
    …'head').append("<link rel='stylesheet' href='"+ASSETS_URL+"css/style.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).

  • Warning Line 226, Column 27: character "<" is the first character of a delimiter but occurred as data
    										for(var i = 0;i < aItems.length;i++){

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 276, Column 46: character "&" not allowed in attribute specification list
    						for (var i=0; i<XmlHttpVersions.length && !HttpRequest; i++){
  • Error Line 276, Column 46: element "XmlHttpVersions.length" undefined
    						for (var i=0; i<XmlHttpVersions.length && !HttpRequest; i++){

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 276, Column 47: character "&" is the first character of a delimiter but occurred as data
    						for (var i=0; i<XmlHttpVersions.length && !HttpRequest; i++){

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 311, Column 45: character "&" is the first character of a delimiter but occurred as data
    …f(elemClicked.id != 'mySelectWrapper' && elemClicked.id != 'mySelectImg' && el…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 311, Column 46: character "&" is the first character of a delimiter but occurred as data
    …(elemClicked.id != 'mySelectWrapper' && elemClicked.id != 'mySelectImg' && ele…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 311, Column 80: character "&" is the first character of a delimiter but occurred as data
    …per' && elemClicked.id != 'mySelectImg' && elemClicked.id != 'mySelectResults')

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 311, Column 81: character "&" is the first character of a delimiter but occurred as data
    …per' && elemClicked.id != 'mySelectImg' && elemClicked.id != 'mySelectResults')

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 316, Column 12: end tag for "XmlHttpVersions.length" omitted, but OMITTAG NO was specified
    			</script>

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

  • Info Line 276, Column 22: start tag was here
    						for (var i=0; i<XmlHttpVersions.length && !HttpRequest; i++){
  • Error Line 334, Column 5: document type does not allow element "h1" here
    	<h1>Free porn movies</h1>

    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 337, Column 188: required attribute "alt" not specified
    …tfiles.com/tubekitty.com//images/logo.gif" width="500" height="80" /></a></div>

    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 347, Column 148: document type does not allow element "div" here
    …tById('mySelectResults'), '/site/indextables/xml/id/855/section_id/3/lid/1/')">

    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 348, Column 139: required attribute "alt" not specified
    …p://assetfiles.com/tubehun.com/images/ArrowDown.gif" width="16" height="16" /> 

    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 351, Column 49: document type does not allow element "div" here
    				<!-- End Dropdown -->	 <div id="filterSpace">

    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 356, Column 54: there is no attribute "onClick"
    … type="checkbox" id="checks1" onClick="Setting_Filter_SexChange(this)" value="…

    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 356, Column 133: end tag for "input" omitted, but OMITTAG NO was specified
    …etting_Filter_SexChange(this)" value="1" checked="checked" name="s_filter[]">  

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

  • Info Line 356, Column 10: start tag was here
    									<input type="checkbox" id="checks1" onClick="Setting_Filter_SexChange(…
  • Error Line 361, Column 133: end tag for "input" omitted, but OMITTAG NO was specified
    …etting_Filter_SexChange(this)" value="2" checked="checked" name="s_filter[]">  

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

  • Info Line 361, Column 10: start tag was here
    									<input type="checkbox" id="checks2" onClick="Setting_Filter_SexChange(…
  • Error Line 366, Column 133: end tag for "input" omitted, but OMITTAG NO was specified
    …etting_Filter_SexChange(this)" value="3" checked="checked" name="s_filter[]">  

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

  • Info Line 366, Column 10: start tag was here
    									<input type="checkbox" id="checks3" onClick="Setting_Filter_SexChange(…
  • Error Line 369, Column 92: end tag for "input" omitted, but OMITTAG NO was specified
    …iv id="filterSave"><input id="filterSaveButton" type="submit" value="Go"></div>

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

  • Info Line 369, Column 33: start tag was here
    											<div id="filterSave"><input id="filterSaveButton" type="submit" valu…
  • Warning Line 375, Column 34: cannot generate system identifier for general entity "lid"
    										<a href="/search/?rs=1&lid=1" target="_blank">New movies</a>&nbsp;

    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 375, Column 34: general entity "lid" not defined and no default entity
    										<a href="/search/?rs=1&lid=1" target="_blank">New movies</a>&nbsp;

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

  • Warning Line 375, Column 37: reference not terminated by REFC delimiter
    										<a href="/search/?rs=1&lid=1" target="_blank">New movies</a>&nbsp;

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

  • Warning Line 375, Column 37: reference to external entity in attribute value
    										<a href="/search/?rs=1&lid=1" target="_blank">New movies</a>&nbsp;

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

  • Error Line 375, Column 37: reference to entity "lid" for which no system identifier could be generated
    										<a href="/search/?rs=1&lid=1" target="_blank">New movies</a>&nbsp;

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

  • Info Line 375, Column 33: entity was defined here
    										<a href="/search/?rs=1&lid=1" target="_blank">New movies</a>&nbsp;
  • Warning Line 398, Column 44: reference not terminated by REFC delimiter
    …ref="/cgi-bin/atx/out.cgi?id=224&trade=http://www.cliti.com/" target="_blank">…

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

  • Warning Line 401, Column 43: reference not terminated by REFC delimiter
    …href="/cgi-bin/atx/out.cgi?id=66&trade=http://www.fuq.com/" target="_blank"><s…

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

  • Warning Line 404, Column 44: reference not terminated by REFC delimiter
    …ref="/cgi-bin/atx/out.cgi?id=109&trade=http://allrusamateurs.com/" target="_bl…

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

  • Warning Line 407, Column 43: reference not terminated by REFC delimiter
    …href="/cgi-bin/atx/out.cgi?id=12&trade=http://www.lolastube.com/" target="_bla…

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

  • Error Line 409, Column 4: document type does not allow element "tr" here
    <tr>

    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 410, Column 8: "tr" not finished but containing element ended
    </table>
  • Error Line 410, Column 8: end tag for "tr" omitted, but OMITTAG NO was specified
    </table>

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

  • Info Line 409, Column 1: start tag was here
    <tr>
  • Error Line 410, Column 8: end tag for "tr" omitted, but OMITTAG NO was specified
    </table>

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

  • Info Line 390, Column 2: start tag was here
     <tr>
  • Error Line 421, Column 61: there is no attribute "onClick"
    …=1&amp;qset=1&amp;qset_lid=1" onClick="_gaq.push(['_trackEvent', 'Setting_Lang…

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

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

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

  • Warning Line 1909, Column 43: reference not terminated by REFC delimiter
    …href="/cgi-bin/atx/out.cgi?id=66&trade=http://www.fuq.com/" target="_blank"><s…

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

  • Error Line 1909, Column 115: end tag for "br" omitted, but OMITTAG NO was specified
    …6&trade=http://www.fuq.com/" target="_blank"><strong>Fuck Tube</strong></a><br>

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

  • Info Line 1909, Column 111: start tag was here
    …6&trade=http://www.fuq.com/" target="_blank"><strong>Fuck Tube</strong></a><br>
  • Warning Line 1912, Column 44: reference not terminated by REFC delimiter
    …ref="/cgi-bin/atx/out.cgi?id=196&trade=http://www.nastyvideotube.com/" target=…

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

  • Error Line 1912, Column 134: end tag for "br" omitted, but OMITTAG NO was specified
    ….nastyvideotube.com/" target="_blank"><strong>Nasty Video Tube</strong></a><br>

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

  • Info Line 1912, Column 130: start tag was here
    ….nastyvideotube.com/" target="_blank"><strong>Nasty Video Tube</strong></a><br>
  • Warning Line 1915, Column 44: reference not terminated by REFC delimiter
    …ref="/cgi-bin/atx/out.cgi?id=224&trade=http://www.cliti.com/" target="_blank">…

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

  • Error Line 1915, Column 114: end tag for "br" omitted, but OMITTAG NO was specified
    …224&trade=http://www.cliti.com/" target="_blank"><strong>Cliti</strong></a><br>

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

  • Info Line 1915, Column 110: start tag was here
    …224&trade=http://www.cliti.com/" target="_blank"><strong>Cliti</strong></a><br>
  • Warning Line 1918, Column 43: reference not terminated by REFC delimiter
    …href="/cgi-bin/atx/out.cgi?id=57&trade=http://www.cunttt.com/" target="_blank"…

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

  • Error Line 1918, Column 115: end tag for "br" omitted, but OMITTAG NO was specified
    …7&trade=http://www.cunttt.com/" target="_blank"><strong>Cunttt</strong></a><br>

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

  • Info Line 1918, Column 111: start tag was here
    …7&trade=http://www.cunttt.com/" target="_blank"><strong>Cunttt</strong></a><br>
  • Error Line 1920, Column 4: document type does not allow element "tr" here
    <tr>

    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 1921, Column 5: end tag for "tr" which is not finished
    </tr>

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

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

  • Warning Line 1923, Column 44: reference not terminated by REFC delimiter
    …ref="/cgi-bin/atx/out.cgi?id=170&trade=http://www.yourdarkdesires.com/" target…

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

  • Error Line 1923, Column 113: end tag for "br" omitted, but OMITTAG NO was specified
    …=170&trade=http://www.yourdarkdesires.com/" target="_blank">Lola's Tube</a><br>

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

  • Info Line 1923, Column 109: start tag was here
    …=170&trade=http://www.yourdarkdesires.com/" target="_blank">Lola's Tube</a><br>
  • Warning Line 1926, Column 44: reference not terminated by REFC delimiter
    …ref="/cgi-bin/atx/out.cgi?id=217&trade=http://www.9taxi.com/" target="_blank">…

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

  • Error Line 1926, Column 109: end tag for "br" omitted, but OMITTAG NO was specified
    …i?id=217&trade=http://www.9taxi.com/" target="_blank">Your Dark Desires</a><br>

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

  • Info Line 1926, Column 105: start tag was here
    …i?id=217&trade=http://www.9taxi.com/" target="_blank">Your Dark Desires</a><br>
  • Warning Line 1929, Column 43: reference not terminated by REFC delimiter
    …href="/cgi-bin/atx/out.cgi?id=62&trade=http://www.bonusporntube.com/" target="…

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

  • Error Line 1929, Column 114: end tag for "br" omitted, but OMITTAG NO was specified
    …62&trade=http://www.bonusporntube.com/" target="_blank">Bonus Porn Tube</a><br>

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

  • Info Line 1929, Column 110: start tag was here
    …62&trade=http://www.bonusporntube.com/" target="_blank">Bonus Porn Tube</a><br>
  • Warning Line 1932, Column 44: reference not terminated by REFC delimiter
    …ref="/cgi-bin/atx/out.cgi?id=244&trade=http://lazypandatube.com/" target="_bla…

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

  • Error Line 1932, Column 111: end tag for "br" omitted, but OMITTAG NO was specified
    …id=244&trade=http://lazypandatube.com/" target="_blank">Lazy Panda Tube</a><br>

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

  • Info Line 1932, Column 107: start tag was here
    …id=244&trade=http://lazypandatube.com/" target="_blank">Lazy Panda Tube</a><br>
  • Error Line 1934, Column 4: document type does not allow element "tr" here
    <tr>

    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 1935, Column 5: end tag for "tr" which is not finished
    </tr>

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

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

  • Warning Line 1937, Column 44: reference not terminated by REFC delimiter
    …ref="/cgi-bin/atx/out.cgi?id=217&trade=http://www.9taxi.com/" target="_blank">…

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

  • Error Line 1937, Column 98: end tag for "br" omitted, but OMITTAG NO was specified
    …/atx/out.cgi?id=217&trade=http://www.9taxi.com/" target="_blank">9 Taxi</a><br>

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

  • Info Line 1937, Column 94: start tag was here
    …/atx/out.cgi?id=217&trade=http://www.9taxi.com/" target="_blank">9 Taxi</a><br>
  • Warning Line 1940, Column 44: reference not terminated by REFC delimiter
    …ref="/cgi-bin/atx/out.cgi?id=109&trade=http://allrusamateurs.com/" target="_bl…

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

  • Error Line 1940, Column 113: end tag for "br" omitted, but OMITTAG NO was specified
    …=109&trade=http://allrusamateurs.com/" target="_blank">All Rus Amateurs</a><br>

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

  • Info Line 1940, Column 109: start tag was here
    …=109&trade=http://allrusamateurs.com/" target="_blank">All Rus Amateurs</a><br>
  • Warning Line 1943, Column 44: reference not terminated by REFC delimiter
    …ref="/cgi-bin/atx/out.cgi?id=150&trade=http://www.monicastube.com/" target="_b…

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

  • Error Line 1943, Column 111: end tag for "br" omitted, but OMITTAG NO was specified
    …id=150&trade=http://www.monicastube.com/" target="_blank">Monica's Tube</a><br>

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

  • Info Line 1943, Column 107: start tag was here
    …id=150&trade=http://www.monicastube.com/" target="_blank">Monica's Tube</a><br>
  • Warning Line 1946, Column 43: reference not terminated by REFC delimiter
    …href="/cgi-bin/atx/out.cgi?id=50&trade=http://www.extremeforbiddentubes.com/" …

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

  • Error Line 1946, Column 130: end tag for "br" omitted, but OMITTAG NO was specified
    …www.extremeforbiddentubes.com/" target="_blank">Extreme Forbidden Tubes</a><br>

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

  • Info Line 1946, Column 126: start tag was here
    …www.extremeforbiddentubes.com/" target="_blank">Extreme Forbidden Tubes</a><br>
  • Error Line 1948, Column 4: document type does not allow element "tr" here
    <tr>

    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 1949, Column 5: end tag for "tr" which is not finished
    </tr>

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

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

  • Warning Line 1951, Column 43: reference not terminated by REFC delimiter
    …href="/cgi-bin/atx/out.cgi?id=35&trade=http://www.dirtyxxxtube.com/" target="_…

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

  • Error Line 1951, Column 112: end tag for "br" omitted, but OMITTAG NO was specified
    …d=35&trade=http://www.dirtyxxxtube.com/" target="_blank">Dirty XXX Tube</a><br>

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

  • Info Line 1951, Column 108: start tag was here
    …d=35&trade=http://www.dirtyxxxtube.com/" target="_blank">Dirty XXX Tube</a><br>
  • Warning Line 1954, Column 43: reference not terminated by REFC delimiter
    …href="/cgi-bin/atx/out.cgi?id=88&trade=http://www.pizzaporntube.com/" target="…

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

  • Error Line 1954, Column 114: end tag for "br" omitted, but OMITTAG NO was specified
    …88&trade=http://www.pizzaporntube.com/" target="_blank">Pizza Porn Tube</a><br>

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

  • Info Line 1954, Column 110: start tag was here
    …88&trade=http://www.pizzaporntube.com/" target="_blank">Pizza Porn Tube</a><br>
  • Warning Line 1957, Column 44: reference not terminated by REFC delimiter
    …ref="/cgi-bin/atx/out.cgi?id=233&trade=http://www.kowalskypage.com" target="_b…

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

  • Error Line 1957, Column 111: end tag for "br" omitted, but OMITTAG NO was specified
    …id=233&trade=http://www.kowalskypage.com" target="_blank">Kowalsky Page</a><br>

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

  • Info Line 1957, Column 107: start tag was here
    …id=233&trade=http://www.kowalskypage.com" target="_blank">Kowalsky Page</a><br>
  • Warning Line 1960, Column 43: reference not terminated by REFC delimiter
    …href="/cgi-bin/atx/out.cgi?id=41&trade=http://www.wetpussy.com/?wrn=n" target=…

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

  • Error Line 1960, Column 109: end tag for "br" omitted, but OMITTAG NO was specified
    …i?id=41&trade=http://www.wetpussy.com/?wrn=n" target="_blank">Wet Pussy</a><br>

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

  • Info Line 1960, Column 105: start tag was here
    …i?id=41&trade=http://www.wetpussy.com/?wrn=n" target="_blank">Wet Pussy</a><br>
  • Error Line 1963, Column 5: end tag for "table" omitted, but OMITTAG NO was specified
    </tr>

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

  • Info Line 1906, Column 3: start tag was here
    		<table width="980" cellpadding="0" cellspacing="0">
  • Error Line 1963, Column 5: end tag for "td" omitted, but OMITTAG NO was specified
    </tr>

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

  • Info Line 1904, Column 5: start tag was here
        <td>
  • Error Line 1964, Column 30: document type does not allow element "td" here; assuming missing "tr" start-tag
     <td width="20%" valign="top">
  • Warning Line 1965, Column 44: reference not terminated by REFC delimiter
    …ref="/cgi-bin/atx/out.cgi?id=136&trade=http://www.wowsextube.com/" target="_bl…

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

  • Error Line 1965, Column 109: end tag for "br" omitted, but OMITTAG NO was specified
    …i?id=136&trade=http://www.wowsextube.com/" target="_blank">Wow Sex Tube</a><br>

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

  • Info Line 1965, Column 105: start tag was here
    …i?id=136&trade=http://www.wowsextube.com/" target="_blank">Wow Sex Tube</a><br>
  • Warning Line 1968, Column 43: reference not terminated by REFC delimiter
    …href="/cgi-bin/atx/out.cgi?id=29&trade=http://www.homemadesextube.com/" target…

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

  • Error Line 1968, Column 118: end tag for "br" omitted, but OMITTAG NO was specified
    …rade=http://www.homemadesextube.com/" target="_blank">Homemade Sex Tube</a><br>

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

  • Info Line 1968, Column 114: start tag was here
    …rade=http://www.homemadesextube.com/" target="_blank">Homemade Sex Tube</a><br>
  • Warning Line 1971, Column 43: reference not terminated by REFC delimiter
    …href="/cgi-bin/atx/out.cgi?id=21&trade=http://www.goblinstube.com/" target="_b…

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

  • Error Line 1971, Column 109: end tag for "br" omitted, but OMITTAG NO was specified
    …i?id=21&trade=http://www.goblinstube.com/" target="_blank">Goblins Tube</a><br>

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

  • Info Line 1971, Column 105: start tag was here
    …i?id=21&trade=http://www.goblinstube.com/" target="_blank">Goblins Tube</a><br>
  • Warning Line 1974, Column 44: reference not terminated by REFC delimiter
    …ref="/cgi-bin/atx/out.cgi?id=347&trade=http://globaltubeporn.com/" target="_bl…

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

  • Error Line 1974, Column 114: end tag for "br" omitted, but OMITTAG NO was specified
    …347&trade=http://globaltubeporn.com/" target="_blank">Global Sex Movies</a><br>

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

  • Info Line 1974, Column 110: start tag was here
    …347&trade=http://globaltubeporn.com/" target="_blank">Global Sex Movies</a><br>
  • Error Line 1995, Column 6: end tag for element "td" which is not open
    	</td>

    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 1996, Column 7: end tag for element "tr" which is not open
      </tr>

    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 1997, Column 6: document type does not allow element "tr" here; assuming missing "table" start-tag
      <tr>
  • Warning Line 2011, Column 67: cannot generate system identifier for general entity "id"
    …http://rtalabel.org/?content=validate&id=&rating=RTA-5042-1996-1400-1577-RTA" …

    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 2011, Column 67: general entity "id" not defined and no default entity
    …http://rtalabel.org/?content=validate&id=&rating=RTA-5042-1996-1400-1577-RTA" …

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

  • Warning Line 2011, Column 69: reference not terminated by REFC delimiter
    …tp://rtalabel.org/?content=validate&id=&rating=RTA-5042-1996-1400-1577-RTA" ta…

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

  • Warning Line 2011, Column 69: reference to external entity in attribute value
    …tp://rtalabel.org/?content=validate&id=&rating=RTA-5042-1996-1400-1577-RTA" ta…

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

  • Error Line 2011, Column 69: reference to entity "id" for which no system identifier could be generated
    …tp://rtalabel.org/?content=validate&id=&rating=RTA-5042-1996-1400-1577-RTA" ta…

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

  • Info Line 2011, Column 66: entity was defined here
    …"http://rtalabel.org/?content=validate&id=&rating=RTA-5042-1996-1400-1577-RTA"…
  • Warning Line 2011, Column 71: cannot generate system identifier for general entity "rating"
    …://rtalabel.org/?content=validate&id=&rating=RTA-5042-1996-1400-1577-RTA" targ…

    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 2011, Column 71: general entity "rating" not defined and no default entity
    …://rtalabel.org/?content=validate&id=&rating=RTA-5042-1996-1400-1577-RTA" targ…

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

  • Warning Line 2011, Column 77: reference not terminated by REFC delimiter
    …label.org/?content=validate&id=&rating=RTA-5042-1996-1400-1577-RTA" target="_b…

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

  • Warning Line 2011, Column 77: reference to external entity in attribute value
    …label.org/?content=validate&id=&rating=RTA-5042-1996-1400-1577-RTA" target="_b…

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

  • Error Line 2011, Column 77: reference to entity "rating" for which no system identifier could be generated
    …label.org/?content=validate&id=&rating=RTA-5042-1996-1400-1577-RTA" target="_b…

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

  • Info Line 2011, Column 70: entity was defined here
    …p://rtalabel.org/?content=validate&id=&rating=RTA-5042-1996-1400-1577-RTA" tar…
  • Error Line 2014, Column 117: end tag for "br" omitted, but OMITTAG NO was specified
    …tricted To Adults" (RTA) website label to better enable parental filtering.<br>

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

  • Info Line 2014, Column 113: start tag was here
    …tricted To Adults" (RTA) website label to better enable parental filtering.<br>
  • Error Line 2015, Column 100: end tag for "br" omitted, but OMITTAG NO was specified
    …n from adult content and block access to this site by using these programs:<br>

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

  • Info Line 2015, Column 96: start tag was here
    …n from adult content and block access to this site by using these programs:<br>
  • Error Line 2016, Column 161: end tag for "br" omitted, but OMITTAG NO was specified
    ….com/">CyberPatrol</a> | <a href="http://www.solidoak.com/">CyberSitter</a><br>

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

  • Info Line 2016, Column 157: start tag was here
    ….com/">CyberPatrol</a> | <a href="http://www.solidoak.com/">CyberSitter</a><br>
  • Error Line 2017, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

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

  • Info Line 2017, Column 1: start tag was here
    <br>
  • Error Line 2027, Column 110: end tag for "br" omitted, but OMITTAG NO was specified
    …sternet.com/contact.html" target="_blank" title="Contact Us">Contact Us</a><br>

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

  • Info Line 2027, Column 106: start tag was here
    …sternet.com/contact.html" target="_blank" title="Contact Us">Contact Us</a><br>
  • Error Line 2035, Column 8: end tag for element "div" which is not open
    		</div>

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

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

  • Error Line 2036, Column 7: end tag for element "div" which is not open
    	</div>

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

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

  • Error Line 2037, Column 6: end tag for element "div" which is not open
    </div>

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

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

  • Error Line 2039, Column 6: document type does not allow element "br" here
    <br />

    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 2040, Column 24: document type does not allow element "div" here
    <div id="bookmarkSpace">> <a target="_self" href="javascript:bookmark('http://w…

    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 2040, Column 217: character "<" is the first character of a delimiter but occurred as data
    …itle="Add Tube Kitty .com to your favorites!">Add to your favorites</a> <</div>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 2042, Column 7: end tag for element "body" which is not open
    </body></html>

    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 2042, Column 14: end tag for element "html" which is not open
    </body></html>

    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
  • 25.667 visits