PORN2 is the ultimate free porn video website! Browse hundreds of categories, thousands of channels and tens of thousands of free porn videos! ...

porn2.com
  • Domain Name
    porn2.com
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #497571
  • Page Size
    33.1 KB
  • Ip Address
    69.10.35.192
  • Heading
    H1: 1, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    1 GIF, 28 JPG, 1 PNG

Website Meta Analysis

  • Title
    Porn 2 - Free Porn Videos
  • Meta Keyword
    porn, porn2, porn videos, free porn, free porn videos, pornstars, porn stars, free pornstars, free porn stars
  • Meta Description
    PORN2 is the ultimate free porn video website! Browse hundreds of categories, thousands of channels and tens of thousands of free porn videos!

Technical Analysis

  • Webserver
    Apache/1.3.39 (Unix) mod_gzip/1.3.26.1a mod_ssl/2.8.30 OpenSSL/0.9.7a PHP-CGI/0.1b
  • Ip Address
    69.10.35.192
  • Domain Age
    9 Years, 9 Months, 0 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Sun, 18 Aug 2013 05:30:36 GMT
  • server: Apache/1.3.39 (Unix) mod_gzip/1.3.26.1a mod_ssl/2.8.30 OpenSSL/0.9.7a PHP-CGI/0.1b
  • x-powered-by: PHP/4.4.4
  • content-type: text/html
  • content-encoding: gzip
  • content-length: 4923
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Domain Name: PORN2.COM
Registrar: MONIKER
Registrant:
Moniker Privacy Services email
Moniker Privacy Services
20 SW 27th Ave.
Suite 201
Pompano Beach
FL
33069
US

Administrative Contact 3704051:
Moniker Privacy Services email
Moniker Privacy Services
20 SW 27th Ave.
Suite 201
Pompano Beach
FL
33069
US
Phone: +1.9549848445
Fax: +1.9549699155

Billing Contact 3704051:
Moniker Privacy Services email
Moniker Privacy Services
20 SW 27th Ave.
Suite 201
Pompano Beach
FL
33069
US
Phone: +1.9549848445
Fax: +1.9549699155

Technical Contact 3704051:
Moniker Privacy Services email
Moniker Privacy Services
20 SW 27th Ave.
Suite 201
Pompano Beach
FL
33069
US
Phone: +1.9549848445
Fax: +1.9549699155

Name Servers:
NS-1546.AWSDNS-01.CO.UK
NS-829.AWSDNS-39.NET
NS-1268.AWSDNS-30.ORG
NS-395.AWSDNS-49.COM
Created: 2003-11-08 14:18:06.0
Database Updated: 2012-02-08 08:28:23.243
Expires: 2012-11-08 14:18:06.0

0

DNS Analysis


DNS servers
ns-395.awsdns-49.com [205.251.193.139]
ns-829.awsdns-39.net
ns-1546.awsdns-01.co.uk
ns-1268.awsdns-30.org [205.251.196.244]


DNS Records

Answer records
porn2.com A 69.10.35.192 300s
porn2.com NS  ns-1268.awsdns-30.org 172800s
porn2.com NS  ns-1546.awsdns-01.co.uk 172800s
porn2.com NS  ns-395.awsdns-49.com 172800s
porn2.com NS  ns-829.awsdns-39.net 172800s
porn2.com SOA
server: ns-1546.awsdns-01.co.uk
email: awsdns-hostmaster@amazon.com
serial: 1
refresh: 7200
retry: 900
expire: 1209600
minimum ttl: 86400
900s

Authority records

Additional records

IP 69.10.35.192 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Secaucus
  • Continent Code
    07094
  • Latitude
    201
  • Longitude
    501
  • %rwhois V-1.5:003fff:00 city.trouble-free.net (by Network Solutions, Inc. V-1.5.9.6)
    network:Class-Name:network
    network:ID:NETBLK-INTSRV.69.10.32.0/19
    network:Auth-Area:69.10.32.0/19
    network:Network-Name:INTSRV-69.10.35.192
    network:IP-Network:69.10.35.192/32
    network:Org-Name:Inxio Ltd
    network:Street-Address:PO Box 517
    network:City:Jersey
    network:State:Channel Islands
    network:Postal-Code:JE4 5UA
    network:Country-Code:GB
    network:Created:19691231
    network:Updated:20121213
    network:Updated-By:abuse@interserver.net

    network:Class-Name:network
    network:ID:NETBLK-INTSRV.69.10.32.0/19
    network:Auth-Area:69.10.32.0/19
    network:Network-Name:INTSRV-69.10.35.192
    network:IP-Network:69.10.35.192/29
    network:Org-Name:SiteNet Host
    network:Street-Address:1865 Palm Cove Blvd
    network:City:Delray Beach
    network:State:FL
    network:Postal-Code:33445
    network:Country-Code:US
    network:Created:20101101
    network:Updated:20121213
    network:Updated-By:abuse@interserver.net

    %ok

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 110 Errors
  • 7 Warnings
Ratio Text/Html
  • 0.8095013556524815
Message Error
  • Error Line 12, Column 15: document type does not allow element "HEAD" here
    </script><head>

    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 14, Column 179: NET-enabling start-tag requires SHORTTAG YES
    …ategories, thousands of channels and tens of thousands of free porn videos!" />

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

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

  • Error Line 14, Column 180: character data is not allowed here
    …ategories, thousands of channels and tens of thousands of free porn videos!" />

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Warning Line 15, Column 143: NET-enabling start-tag requires SHORTTAG YES
    …n, free porn videos, pornstars, porn stars, free pornstars, free porn stars" />

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

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

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

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

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

  • Warning Line 17, Column 82: NET-enabling start-tag requires SHORTTAG YES
    …k rel="stylesheet" href="http://www.porn2.com/css/porns.css" type="text/css" />

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

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

  • Warning Line 20, Column 66: NET-enabling start-tag requires SHORTTAG YES
    <link rel="shortcut icon" href="http://www.porn2.com/favicon.ico"/>

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

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

  • Warning Line 21, Column 79: NET-enabling start-tag requires SHORTTAG YES
    <meta name="verify-v1" content="SESIppLu7UaSS33oarf4sseij5g76bi7vnc5W3sXQe8=" />

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

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

  • Error Line 26, Column 14: there is no attribute "TARGET"
    <base target="_self">

    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 26, Column 21: required attribute "HREF" not specified
    <base target="_self">

    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 28, Column 6: document type does not allow element "BODY" here
    <body>

    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 32, Column 224: delimiter "'" invalid: only S separators and TAGC allowed here
    …ate().getTime()+'" language="JavaScript" type="text/javascript"></SCR'+'IPT>');
  • Error Line 32, Column 224: end tag for element "SCR" which is not open
    …ate().getTime()+'" language="JavaScript" type="text/javascript"></SCR'+'IPT>');

    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 44, Column 58: required attribute "ALT" not specified
    <img src="http://i.porn2.com/porn/spacer.gif" id="slogan">

    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 53, Column 93: cannot generate system identifier for general entity "timer"
    …els/static.index.php?affiliate_id=3158&timer=1277835324139">HD Channel</a></li>

    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 53, Column 93: general entity "timer" not defined and no default entity
    …els/static.index.php?affiliate_id=3158&timer=1277835324139">HD Channel</a></li>

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

  • Error Line 53, Column 98: reference to entity "timer" for which no system identifier could be generated
    …els/static.index.php?affiliate_id=3158&timer=1277835324139">HD Channel</a></li>

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

  • Info Line 53, Column 92: entity was defined here
    …els/static.index.php?affiliate_id=3158&timer=1277835324139">HD Channel</a></li…
  • Error Line 57, Column 138: document type does not allow element "INPUT" here; missing one of "P", "H1", "H2", "H3", "H4", "H5", "H6", "PRE", "DIV", "ADDRESS" start-tag
    …)" onblur="inp_txt_blur(this,def_val)"><input src="http://i.porn2.com/porn/src…

    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 57, Column 212: there is no attribute "ALIGN"
    …/srch_btn.png" id="pornsrchbtn" align="top" type="image" onsubmit="return porn…

    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 57, Column 240: there is no attribute "ONSUBMIT"
    …id="pornsrchbtn" align="top" type="image" onsubmit="return pornsearch(this.q)">

    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 57, Column 267: document type does not allow element "INPUT" here; missing one of "P", "H1", "H2", "H3", "H4", "H5", "H6", "PRE", "DIV", "ADDRESS" start-tag
    …id="pornsrchbtn" align="top" type="image" onsubmit="return pornsearch(this.q)">

    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 58, Column 40: document type does not allow element "INPUT" here; missing one of "P", "H1", "H2", "H3", "H4", "H5", "H6", "PRE", "DIV", "ADDRESS" start-tag
    <input name="b" type="hidden" value="1">

    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 59, Column 7: end tag for "FORM" which is not finished
    </form>

    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.

  • Error Line 78, Column 13: there is no attribute "SRC"
    <iframe src="http://textad.sexsearch.com/if/1/1101/0/ref=41475;keyword=porn2" w…

    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 78, Column 85: there is no attribute "WIDTH"
    …1101/0/ref=41475;keyword=porn2" width="166" height="1525" frameborder="0" scro…

    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 78, Column 98: there is no attribute "HEIGHT"
    …475;keyword=porn2" width="166" height="1525" frameborder="0" scrolling="no" ma…

    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 78, Column 117: there is no attribute "FRAMEBORDER"
    …width="166" height="1525" frameborder="0" scrolling="no" marginwidth="0" margi…

    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 78, Column 131: there is no attribute "SCROLLING"
    …ight="1525" frameborder="0" scrolling="no" marginwidth="0" marginheight="0"></…

    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 78, Column 148: there is no attribute "MARGINWIDTH"
    …1525" frameborder="0" scrolling="no" marginwidth="0" marginheight="0"></iframe>

    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 78, Column 165: there is no attribute "MARGINHEIGHT"
    …1525" frameborder="0" scrolling="no" marginwidth="0" marginheight="0"></iframe>

    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 78, Column 168: element "IFRAME" undefined
    …1525" frameborder="0" scrolling="no" marginwidth="0" marginheight="0"></iframe>

    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 81, Column 187: there is no attribute "TARGET"
    …hreesome" onmousedown="return porno(this,'100','164365-thumb')" target="_self">

    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 83, Column 156: there is no attribute "REL"
    … alt="Hardcore babe riding stiff cock in threesome" class="videothumb" rel="3">

    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 102, Column 10: ID "LENGTH" already defined
    <div id="length">00min 30sec</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 85, Column 10: ID "LENGTH" first defined here
    <div id="length">00min 59sec</div>
  • Error Line 103, Column 10: ID "DATE" already defined
    <div id="date">27 Mar 11</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 86, Column 10: ID "DATE" first defined here
    <div id="date">27 Mar 11</div>
  • Error Line 105, Column 10: ID "VIEWS" already defined
    <div id="views">797 views</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 88, Column 10: ID "VIEWS" first defined here
    <div id="views">159 views</div>
  • Error Line 119, Column 10: ID "LENGTH" already defined
    <div id="length">01min 00sec</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 85, Column 10: ID "LENGTH" first defined here
    <div id="length">00min 59sec</div>
  • Error Line 120, Column 10: ID "DATE" already defined
    <div id="date">27 Mar 11</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 86, Column 10: ID "DATE" first defined here
    <div id="date">27 Mar 11</div>
  • Error Line 122, Column 10: ID "VIEWS" already defined
    <div id="views">597 views</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 88, Column 10: ID "VIEWS" first defined here
    <div id="views">159 views</div>
  • Error Line 136, Column 10: ID "LENGTH" already defined
    <div id="length">01min 01sec</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 85, Column 10: ID "LENGTH" first defined here
    <div id="length">00min 59sec</div>
  • Error Line 137, Column 10: ID "DATE" already defined
    <div id="date">27 Mar 11</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 86, Column 10: ID "DATE" first defined here
    <div id="date">27 Mar 11</div>
  • Error Line 139, Column 10: ID "VIEWS" already defined
    <div id="views">272 views</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 88, Column 10: ID "VIEWS" first defined here
    <div id="views">159 views</div>
  • Error Line 153, Column 10: ID "LENGTH" already defined
    <div id="length">00min 30sec</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 85, Column 10: ID "LENGTH" first defined here
    <div id="length">00min 59sec</div>
  • Error Line 154, Column 10: ID "DATE" already defined
    <div id="date">27 Mar 11</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 86, Column 10: ID "DATE" first defined here
    <div id="date">27 Mar 11</div>
  • Error Line 156, Column 10: ID "VIEWS" already defined
    <div id="views">3472 views</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 88, Column 10: ID "VIEWS" first defined here
    <div id="views">159 views</div>
  • Error Line 170, Column 10: ID "LENGTH" already defined
    <div id="length">00min 38sec</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 85, Column 10: ID "LENGTH" first defined here
    <div id="length">00min 59sec</div>
  • Error Line 171, Column 10: ID "DATE" already defined
    <div id="date">27 Mar 11</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 86, Column 10: ID "DATE" first defined here
    <div id="date">27 Mar 11</div>
  • Error Line 173, Column 10: ID "VIEWS" already defined
    <div id="views">77 views</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 88, Column 10: ID "VIEWS" first defined here
    <div id="views">159 views</div>
  • Error Line 187, Column 10: ID "LENGTH" already defined
    <div id="length">01min 00sec</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 85, Column 10: ID "LENGTH" first defined here
    <div id="length">00min 59sec</div>
  • Error Line 188, Column 10: ID "DATE" already defined
    <div id="date">27 Mar 11</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 86, Column 10: ID "DATE" first defined here
    <div id="date">27 Mar 11</div>
  • Error Line 190, Column 10: ID "VIEWS" already defined
    <div id="views">214 views</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 88, Column 10: ID "VIEWS" first defined here
    <div id="views">159 views</div>
  • Error Line 204, Column 10: ID "LENGTH" already defined
    <div id="length">01min 20sec</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 85, Column 10: ID "LENGTH" first defined here
    <div id="length">00min 59sec</div>
  • Error Line 205, Column 10: ID "DATE" already defined
    <div id="date">27 Mar 11</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 86, Column 10: ID "DATE" first defined here
    <div id="date">27 Mar 11</div>
  • Error Line 207, Column 10: ID "VIEWS" already defined
    <div id="views">292 views</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 88, Column 10: ID "VIEWS" first defined here
    <div id="views">159 views</div>
  • Error Line 221, Column 10: ID "LENGTH" already defined
    <div id="length">01min 30sec</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 85, Column 10: ID "LENGTH" first defined here
    <div id="length">00min 59sec</div>
  • Error Line 222, Column 10: ID "DATE" already defined
    <div id="date">27 Mar 11</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 86, Column 10: ID "DATE" first defined here
    <div id="date">27 Mar 11</div>
  • Error Line 224, Column 10: ID "VIEWS" already defined
    <div id="views">1931 views</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 88, Column 10: ID "VIEWS" first defined here
    <div id="views">159 views</div>
  • Error Line 238, Column 10: ID "LENGTH" already defined
    <div id="length">00min 26sec</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 85, Column 10: ID "LENGTH" first defined here
    <div id="length">00min 59sec</div>
  • Error Line 239, Column 10: ID "DATE" already defined
    <div id="date">26 Mar 11</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 86, Column 10: ID "DATE" first defined here
    <div id="date">27 Mar 11</div>
  • Error Line 241, Column 10: ID "VIEWS" already defined
    <div id="views">789 views</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 88, Column 10: ID "VIEWS" first defined here
    <div id="views">159 views</div>
  • Error Line 255, Column 10: ID "LENGTH" already defined
    <div id="length">01min 00sec</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 85, Column 10: ID "LENGTH" first defined here
    <div id="length">00min 59sec</div>
  • Error Line 256, Column 10: ID "DATE" already defined
    <div id="date">26 Mar 11</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 86, Column 10: ID "DATE" first defined here
    <div id="date">27 Mar 11</div>
  • Error Line 258, Column 10: ID "VIEWS" already defined
    <div id="views">2160 views</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 88, Column 10: ID "VIEWS" first defined here
    <div id="views">159 views</div>
  • Error Line 272, Column 10: ID "LENGTH" already defined
    <div id="length">00min 59sec</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 85, Column 10: ID "LENGTH" first defined here
    <div id="length">00min 59sec</div>
  • Error Line 273, Column 10: ID "DATE" already defined
    <div id="date">26 Mar 11</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 86, Column 10: ID "DATE" first defined here
    <div id="date">27 Mar 11</div>
  • Error Line 275, Column 10: ID "VIEWS" already defined
    <div id="views">677 views</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 88, Column 10: ID "VIEWS" first defined here
    <div id="views">159 views</div>
  • Error Line 289, Column 10: ID "LENGTH" already defined
    <div id="length">00min 44sec</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 85, Column 10: ID "LENGTH" first defined here
    <div id="length">00min 59sec</div>
  • Error Line 290, Column 10: ID "DATE" already defined
    <div id="date">26 Mar 11</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 86, Column 10: ID "DATE" first defined here
    <div id="date">27 Mar 11</div>
  • Error Line 292, Column 10: ID "VIEWS" already defined
    <div id="views">236 views</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 88, Column 10: ID "VIEWS" first defined here
    <div id="views">159 views</div>
  • Error Line 306, Column 10: ID "LENGTH" already defined
    <div id="length">01min 28sec</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 85, Column 10: ID "LENGTH" first defined here
    <div id="length">00min 59sec</div>
  • Error Line 307, Column 10: ID "DATE" already defined
    <div id="date">26 Mar 11</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 86, Column 10: ID "DATE" first defined here
    <div id="date">27 Mar 11</div>
  • Error Line 309, Column 10: ID "VIEWS" already defined
    <div id="views">33 views</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 88, Column 10: ID "VIEWS" first defined here
    <div id="views">159 views</div>
  • Error Line 323, Column 10: ID "LENGTH" already defined
    <div id="length">00min 39sec</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 85, Column 10: ID "LENGTH" first defined here
    <div id="length">00min 59sec</div>
  • Error Line 324, Column 10: ID "DATE" already defined
    <div id="date">26 Mar 11</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 86, Column 10: ID "DATE" first defined here
    <div id="date">27 Mar 11</div>
  • Error Line 326, Column 10: ID "VIEWS" already defined
    <div id="views">453 views</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 88, Column 10: ID "VIEWS" first defined here
    <div id="views">159 views</div>
  • Error Line 340, Column 10: ID "LENGTH" already defined
    <div id="length">00min 59sec</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 85, Column 10: ID "LENGTH" first defined here
    <div id="length">00min 59sec</div>
  • Error Line 341, Column 10: ID "DATE" already defined
    <div id="date">26 Mar 11</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 86, Column 10: ID "DATE" first defined here
    <div id="date">27 Mar 11</div>
  • Error Line 343, Column 10: ID "VIEWS" already defined
    <div id="views">910 views</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 88, Column 10: ID "VIEWS" first defined here
    <div id="views">159 views</div>
  • Error Line 357, Column 10: ID "LENGTH" already defined
    <div id="length">00min 45sec</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 85, Column 10: ID "LENGTH" first defined here
    <div id="length">00min 59sec</div>
  • Error Line 358, Column 10: ID "DATE" already defined
    <div id="date">26 Mar 11</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 86, Column 10: ID "DATE" first defined here
    <div id="date">27 Mar 11</div>
  • Error Line 360, Column 10: ID "VIEWS" already defined
    <div id="views">1763 views</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 88, Column 10: ID "VIEWS" first defined here
    <div id="views">159 views</div>
  • Error Line 374, Column 10: ID "LENGTH" already defined
    <div id="length">00min 38sec</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 85, Column 10: ID "LENGTH" first defined here
    <div id="length">00min 59sec</div>
  • Error Line 375, Column 10: ID "DATE" already defined
    <div id="date">26 Mar 11</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 86, Column 10: ID "DATE" first defined here
    <div id="date">27 Mar 11</div>
  • Error Line 377, Column 10: ID "VIEWS" already defined
    <div id="views">New Video</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 88, Column 10: ID "VIEWS" first defined here
    <div id="views">159 views</div>
  • Error Line 391, Column 10: ID "LENGTH" already defined
    <div id="length">00min 44sec</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 85, Column 10: ID "LENGTH" first defined here
    <div id="length">00min 59sec</div>
  • Error Line 392, Column 10: ID "DATE" already defined
    <div id="date">26 Mar 11</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 86, Column 10: ID "DATE" first defined here
    <div id="date">27 Mar 11</div>
  • Error Line 394, Column 10: ID "VIEWS" already defined
    <div id="views">810 views</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 88, Column 10: ID "VIEWS" first defined here
    <div id="views">159 views</div>
  • Error Line 408, Column 10: ID "LENGTH" already defined
    <div id="length">00min 28sec</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 85, Column 10: ID "LENGTH" first defined here
    <div id="length">00min 59sec</div>
  • Error Line 409, Column 10: ID "DATE" already defined
    <div id="date">26 Mar 11</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 86, Column 10: ID "DATE" first defined here
    <div id="date">27 Mar 11</div>
  • Error Line 411, Column 10: ID "VIEWS" already defined
    <div id="views">344 views</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 88, Column 10: ID "VIEWS" first defined here
    <div id="views">159 views</div>
  • Error Line 425, Column 10: ID "LENGTH" already defined
    <div id="length">01min 00sec</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 85, Column 10: ID "LENGTH" first defined here
    <div id="length">00min 59sec</div>
  • Error Line 426, Column 10: ID "DATE" already defined
    <div id="date">26 Mar 11</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 86, Column 10: ID "DATE" first defined here
    <div id="date">27 Mar 11</div>
  • Error Line 428, Column 10: ID "VIEWS" already defined
    <div id="views">407 views</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 88, Column 10: ID "VIEWS" first defined here
    <div id="views">159 views</div>
  • Error Line 442, Column 10: ID "LENGTH" already defined
    <div id="length">00min 39sec</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 85, Column 10: ID "LENGTH" first defined here
    <div id="length">00min 59sec</div>
  • Error Line 443, Column 10: ID "DATE" already defined
    <div id="date">26 Mar 11</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 86, Column 10: ID "DATE" first defined here
    <div id="date">27 Mar 11</div>
  • Error Line 445, Column 10: ID "VIEWS" already defined
    <div id="views">831 views</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 88, Column 10: ID "VIEWS" first defined here
    <div id="views">159 views</div>
  • Error Line 459, Column 10: ID "LENGTH" already defined
    <div id="length">01min 00sec</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 85, Column 10: ID "LENGTH" first defined here
    <div id="length">00min 59sec</div>
  • Error Line 460, Column 10: ID "DATE" already defined
    <div id="date">25 Mar 11</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 86, Column 10: ID "DATE" first defined here
    <div id="date">27 Mar 11</div>
  • Error Line 462, Column 10: ID "VIEWS" already defined
    <div id="views">301 views</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 88, Column 10: ID "VIEWS" first defined here
    <div id="views">159 views</div>
  • Error Line 476, Column 10: ID "LENGTH" already defined
    <div id="length">01min 00sec</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 85, Column 10: ID "LENGTH" first defined here
    <div id="length">00min 59sec</div>
  • Error Line 477, Column 10: ID "DATE" already defined
    <div id="date">25 Mar 11</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 86, Column 10: ID "DATE" first defined here
    <div id="date">27 Mar 11</div>
  • Error Line 479, Column 10: ID "VIEWS" already defined
    <div id="views">779 views</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 88, Column 10: ID "VIEWS" first defined here
    <div id="views">159 views</div>
  • Error Line 493, Column 10: ID "LENGTH" already defined
    <div id="length">00min 57sec</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 85, Column 10: ID "LENGTH" first defined here
    <div id="length">00min 59sec</div>
  • Error Line 494, Column 10: ID "DATE" already defined
    <div id="date">25 Mar 11</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 86, Column 10: ID "DATE" first defined here
    <div id="date">27 Mar 11</div>
  • Error Line 496, Column 10: ID "VIEWS" already defined
    <div id="views">122 views</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 88, Column 10: ID "VIEWS" first defined here
    <div id="views">159 views</div>
  • Error Line 510, Column 10: ID "LENGTH" already defined
    <div id="length">00min 45sec</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 85, Column 10: ID "LENGTH" first defined here
    <div id="length">00min 59sec</div>
  • Error Line 511, Column 10: ID "DATE" already defined
    <div id="date">25 Mar 11</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 86, Column 10: ID "DATE" first defined here
    <div id="date">27 Mar 11</div>
  • Error Line 513, Column 10: ID "VIEWS" already defined
    <div id="views">2270 views</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 88, Column 10: ID "VIEWS" first defined here
    <div id="views">159 views</div>
  • Error Line 527, Column 10: ID "LENGTH" already defined
    <div id="length">01min 01sec</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 85, Column 10: ID "LENGTH" first defined here
    <div id="length">00min 59sec</div>
  • Error Line 528, Column 10: ID "DATE" already defined
    <div id="date">25 Mar 11</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 86, Column 10: ID "DATE" first defined here
    <div id="date">27 Mar 11</div>
  • Error Line 530, Column 10: ID "VIEWS" already defined
    <div id="views">213 views</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 88, Column 10: ID "VIEWS" first defined here
    <div id="views">159 views</div>
  • Error Line 544, Column 10: ID "LENGTH" already defined
    <div id="length">00min 39sec</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 85, Column 10: ID "LENGTH" first defined here
    <div id="length">00min 59sec</div>
  • Error Line 545, Column 10: ID "DATE" already defined
    <div id="date">25 Mar 11</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 86, Column 10: ID "DATE" first defined here
    <div id="date">27 Mar 11</div>
  • Error Line 547, Column 10: ID "VIEWS" already defined
    <div id="views">152 views</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 88, Column 10: ID "VIEWS" first defined here
    <div id="views">159 views</div>
  • Error Line 579, Column 6: end tag for element "DIV" which is not open
    </div> <!--CONTAINER END-->

    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 581, Column 7: "HEAD" not finished but containing element ended
    </html><!--
  • Error Line 581, Column 7: end tag for "HTML" which is not finished
    </html><!--

    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.

Visitor Analysis

Daily Visitor
  • 257 visits