apetube.com

Free porn tube categories, porn videos. ApeTube ...

Display Widget for this domain on your website. Click Here
This data was last updated from 08-07-2013 03:41:24  (update).

Overview Info

  • Domain Name
    apetube.com
  • Favicon
  • Alexa Rank
    #2656
  • Google Page Rank
    PR 2
  • Ip Address
    68.169.65.142
  • Page Size
    212 KB
  • Images
    2 GIF, 120 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 3 0 0 0 0

Website Meta Analysis

  • Title
    Free porn tube categories, porn videos. ApeTube
  • Meta Keyword
    free porn,porn tube, porn videos, free porn tube
  • Meta Description
    Free porn tube categories, porn videos. ApeTube

Technical Analysis

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

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

HTML Analysis

  • date: Mon, 08 Jul 2013 03:37:56 GMT
  • server: Apache
  • connection: close
  • content-type: text/html
  • content-length: 214711
  • age: 203
  • x-google-cache-control: remote-cache-hit
  • via: HTTP/1.1 GWA (remote cache hit)
Domain Name: APETUBE.COM
Registrar: MONIKER

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


Administrative Contact [3631244]:
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 [3631244]:
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 [3631244]:
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-04-29 07:22:19.0
Database last updated on: 2011-05-17 04:36:07.977
Domain Expires on: 2015-04-29 07:22:19.0

IP 68.169.65.142 Analysis

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

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 38 Errors
  • 27 Warnings
Ratio Text/Html
  • 0.8494860364011495
Message Error
  • Error Line 9, 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 21, 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 42, 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 42, 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 97, 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 97, 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 97, 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 97, 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 97, 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 97, Column 56: entity was defined here
    		var p,i,x;if(!d) d=document; if((p=n.indexOf("?"))>0&&parent.frames.length) {
  • Warning Line 99, 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 99, 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 99, 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 99, 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 99, 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 99, 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 99, 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 99, 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 99, 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 99, 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 99, 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 99, 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 99, 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 99, 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 100, 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 100, 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 100, 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 100, 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 100, 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 100, 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 100, 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 100, 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 100, 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 99, 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 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 100, 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 101, 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 101, 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 104, 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 100, 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 104, 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 99, 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];
  • Warning Line 138, 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 188, Column 46: character "&" not allowed in attribute specification list
    						for (var i=0; i<XmlHttpVersions.length && !HttpRequest; i++){
  • Error Line 188, 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 188, 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 223, 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 223, 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 223, 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 223, 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 228, 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 188, Column 22: start tag was here
    						for (var i=0; i<XmlHttpVersions.length && !HttpRequest; i++){
  • Error Line 246, Column 54: there is no attribute "src"
    …" href="/" title="Free Porn"><IMG src="http://assetfiles.com/apetube.com//imag…

    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 246, Column 111: there is no attribute "alt"
    …les.com/apetube.com//images/logo.gif" alt="Free Porn at ApeTube :: Home" /></a>

    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 246, Column 143: element "IMG" undefined
    …les.com/apetube.com//images/logo.gif" alt="Free Porn at ApeTube :: Home" /></a>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 254, 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 254, 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 254, Column 10: start tag was here
    									<input type="checkbox" id="checks1" onClick="Setting_Filter_SexChange(…
  • Error Line 259, 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 259, Column 10: start tag was here
    									<input type="checkbox" id="checks2" onClick="Setting_Filter_SexChange(…
  • Error Line 264, 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 264, Column 10: start tag was here
    									<input type="checkbox" id="checks3" onClick="Setting_Filter_SexChange(…
  • Error Line 267, 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 267, Column 33: start tag was here
    											<div id="filterSave"><input id="filterSaveButton" type="submit" valu…
  • Warning Line 278, Column 73: cannot generate system identifier for general entity "t"
    …om/traffic/textlink/?source=menu_link&t=8" target="_blank">Free Porn Tube</a> …

    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 278, Column 73: general entity "t" not defined and no default entity
    …om/traffic/textlink/?source=menu_link&t=8" target="_blank">Free Porn Tube</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.

  • Warning Line 278, Column 74: reference not terminated by REFC delimiter
    …m/traffic/textlink/?source=menu_link&t=8" target="_blank">Free Porn Tube</a> |…

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

  • Warning Line 278, Column 74: reference to external entity in attribute value
    …m/traffic/textlink/?source=menu_link&t=8" target="_blank">Free Porn Tube</a> |…

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

  • Error Line 278, Column 74: reference to entity "t" for which no system identifier could be generated
    …m/traffic/textlink/?source=menu_link&t=8" target="_blank">Free Porn Tube</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 278, Column 72: entity was defined here
    …com/traffic/textlink/?source=menu_link&t=8" target="_blank">Free Porn Tube</a>…
  • Error Line 1749, Column 22: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    	<div id="disclaimer">

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 1750, Column 116: 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 1750, Column 112: start tag was here
    …tricted To Adults" (RTA) website label to better enable parental filtering.<br>
  • Error Line 1751, 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 1751, Column 96: start tag was here
    …n from adult content and block access to this site by using these programs:<br>
  • Error Line 1752, 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 1752, Column 157: start tag was here
    ….com/">CyberPatrol</a> | <a href="http://www.solidoak.com/">CyberSitter</a><br>
  • Error Line 1753, 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 1753, Column 1: start tag was here
    <br>
  • Error Line 1763, 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 1763, Column 106: start tag was here
    …sternet.com/contact.html" target="_blank" title="Contact Us">Contact Us</a><br>
  • Error Line 1775, 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 1780, Column 56: there is no attribute "fb:like:layout"
    <a class="addthis_button_facebook_like" fb:like:layout="button_count"></a>

    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.

Visitor Analysis

Daily Visitor
  • 46.667 visits