slutroulette.com

A chatroulette sex platform where live girls put on free cam shows. Registration is free. ...

Display Widget for this domain on your website. Click Here
This data was last updated from 17-09-2013 08:44:06  (update).

Overview Info

  • Domain Name
    slutroulette.com
  • Favicon
  • Alexa Rank
    #8021
  • Google Page Rank
    PR 4
  • Ip Address
    76.74.193.178
  • Page Size
    22.3 KB
  • Images
    0 GIF, 1 JPG, 3 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 1 0 0 0 0

Website Meta Analysis

  • Title
    An Adult Chatroulette :: interact with free live webcam girls on Slutroulette.com
  • Meta Keyword
    Slutroulette, Webcam Sluts, Free Sluts, cam sluts
  • Meta Description
    A chatroulette sex platform where live girls put on free cam shows. Registration is free.

Technical Analysis

  • Webserver
    nginx
  • Ip Address
    76.74.193.178
  • Domain Age
    3 Years, 7 Months, 16 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx
  • date: Tue, 17 Sep 2013 20:44:00 GMT
  • content-type: text/html
  • x-powered-by: PHP/5.4.8
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: SLUTROULETTE.COM
Created on: 19-Feb-10
Expires on: 19-Feb-13
Last Updated on: 20-Mar-12

Registrant:
Domains By Proxy, LLC
DomainsByProxy.com
14747 N Northsight Blvd Suite 111, PMB 309
Scottsdale, Arizona 85260
United States

Administrative Contact:
Private, Registration email
Domains By Proxy, LLC
DomainsByProxy.com
14747 N Northsight Blvd Suite 111, PMB 309
Scottsdale, Arizona 85260
United States
(480) 624-2599 Fax -- (480) 624-2598

Technical Contact:
Private, Registration email
Domains By Proxy, LLC
DomainsByProxy.com
14747 N Northsight Blvd Suite 111, PMB 309
Scottsdale, Arizona 85260
United States
(480) 624-2599 Fax -- (480) 624-2598

Domain servers in listed order:
NS1.WEBDNSPROVIDER.COM
NS2.WEBDNSPROVIDER.COM
NS3.WEBDNSPROVIDER.COM

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 95 Errors
  • 47 Warnings
Ratio Text/Html
  • 0.382448442299254
Message Error
  • Error Line 72, Column 118: required attribute "alt" not specified
    …p://static.slutroulette.com/cr/static/freecamsexposed.com/212/images/logo.png'>

    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 72, Column 119: end tag for "img" omitted, but OMITTAG NO was specified
    …p://static.slutroulette.com/cr/static/freecamsexposed.com/212/images/logo.png'>

    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 72, Column 9: start tag was here
            <img  class="fancybox" src='http://static.slutroulette.com/cr/static/fr…
  • Error Line 76, Column 60: document type does not allow element "html" here
            <html xmlns:fb='https://www.facebook.com/2008/fbml'>

    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 76, Column 9: Missing xmlns attribute for element html. The value should be: http://www.w3.org/1999/xhtml
            <html xmlns:fb='https://www.facebook.com/2008/fbml'>

    Many Document Types based on XML need a mandatory xmlns attribute on the root element. For example, the root element for XHTML might look like:
    <html xmlns="http://www.w3.org/1999/xhtml">

  • Error Line 77, Column 16: required attribute "type" not specified
            <script>(function(d, s, id) {

    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 77, Column 16: document type does not allow element "script" here; assuming missing "head" start-tag
            <script>(function(d, s, id) {
  • Error Line 84, Column 23: there is no attribute "href"
            <fb:like href='http://www.slutroulette.com' style='float: right; width:…

    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 84, Column 59: there is no attribute "style"
    …f='http://www.slutroulette.com' style='float: right; width: 103px;' send='fals…

    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 84, Column 94: there is no attribute "send"
    …le='float: right; width: 103px;' send='false' layout='button_count' show_faces…

    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 84, Column 109: there is no attribute "layout"
    …t; width: 103px;' send='false' layout='button_count' show_faces='true' font='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 84, Column 135: there is no attribute "show_faces"
    …;' send='false' layout='button_count' show_faces='true' font='arial'></fb:like>

    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 84, Column 147: there is no attribute "font"
    …;' send='false' layout='button_count' show_faces='true' font='arial'></fb:like>

    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 84, Column 154: element "fb:like" undefined
    …;' send='false' layout='button_count' show_faces='true' font='arial'></fb:like>

    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 85, Column 49: document type does not allow element "div" here; assuming missing "object" start-tag
    …iv style='float: right; width: 132px;'><a href='http://twitter.com/share' clas…
  • Error Line 85, Column 123: there is no attribute "data-url"
    …class='twitter-share-button' data-url='http://www.slutroulette.com' data-count…

    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 85, Column 164: there is no attribute "data-count"
    …tp://www.slutroulette.com' data-count='horizontal'>Tweet</a><script type='text…

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

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

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

  • Error Line 86, Column 65: there is no attribute "size"
    … right; width: 90px;'><g:plusone size='medium' href='http://www.slutroulette.c…

    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 86, Column 79: there is no attribute "href"
    … 90px;'><g:plusone size='medium' href='http://www.slutroulette.com'></g:pluson…

    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 86, Column 108: element "g:plusone" undefined
    …><g:plusone size='medium' href='http://www.slutroulette.com'></g:plusone></div>

    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 87, Column 14: end tag for "object" omitted, but OMITTAG NO was specified
            </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 85, Column 9: start tag was here
            <div style='float: right; width: 132px;'><a href='http://twitter.com/sh…
  • Error Line 87, Column 14: "head" not finished but containing element ended
            </div>
  • Error Line 87, Column 14: end tag for "head" omitted, but OMITTAG NO was specified
            </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 77, Column 9: start tag was here
            <script>(function(d, s, id) {
  • Error Line 87, Column 14: "html" not finished but containing element ended
            </div>
  • Error Line 87, Column 14: end tag for "html" omitted, but OMITTAG NO was specified
            </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 76, Column 9: start tag was here
            <html xmlns:fb='https://www.facebook.com/2008/fbml'>
  • Error Line 91, Column 169: required attribute "alt" not specified
    …slutroulette.com/cr/static/freecamsexposed.com/212/images/flags/eng.png' /></a>

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

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

  • Error Line 92, Column 169: required attribute "alt" not specified
    …slutroulette.com/cr/static/freecamsexposed.com/212/images/flags/ita.png' /></a>

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

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

  • Error Line 93, Column 169: required attribute "alt" not specified
    …slutroulette.com/cr/static/freecamsexposed.com/212/images/flags/spa.png' /></a>

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

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

  • Error Line 94, Column 169: required attribute "alt" not specified
    …slutroulette.com/cr/static/freecamsexposed.com/212/images/flags/por.png' /></a>

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

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

  • Warning Line 101, Column 105: cannot generate system identifier for general entity "langchoice"
    …freefun.net/signup/?AFNO=1-1-.99.US.212.typein_Jan2013&langchoice=en">Girls</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 101, Column 105: general entity "langchoice" not defined and no default entity
    …freefun.net/signup/?AFNO=1-1-.99.US.212.typein_Jan2013&langchoice=en">Girls</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 101, Column 115: reference not terminated by REFC delimiter
    …freefun.net/signup/?AFNO=1-1-.99.US.212.typein_Jan2013&langchoice=en">Girls</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 101, Column 115: reference to external entity in attribute value
    …freefun.net/signup/?AFNO=1-1-.99.US.212.typein_Jan2013&langchoice=en">Girls</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 101, Column 115: reference to entity "langchoice" for which no system identifier could be generated
    …freefun.net/signup/?AFNO=1-1-.99.US.212.typein_Jan2013&langchoice=en">Girls</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 101, Column 104: entity was defined here
    …freefun.net/signup/?AFNO=1-1-.99.US.212.typein_Jan2013&langchoice=en">Girls</a>
  • Warning Line 102, Column 123: reference not terminated by REFC delimiter
    …straight-couples/?AFNO=1-1-.99.US.212.typein_Jan2013&langchoice=en">Couples</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 102, Column 123: reference to external entity in attribute value
    …straight-couples/?AFNO=1-1-.99.US.212.typein_Jan2013&langchoice=en">Couples</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 102, Column 123: reference to entity "langchoice" for which no system identifier could be generated
    …straight-couples/?AFNO=1-1-.99.US.212.typein_Jan2013&langchoice=en">Couples</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 101, Column 104: entity was defined here
    …freefun.net/signup/?AFNO=1-1-.99.US.212.typein_Jan2013&langchoice=en">Girls</a>
  • Warning Line 103, Column 103: reference not terminated by REFC delimiter
    …fun.net/webcam/guys/?AFNO=1-1-.99.US.212.typein_Jan2013&langchoice=en">Guys</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 103, Column 103: reference to external entity in attribute value
    …fun.net/webcam/guys/?AFNO=1-1-.99.US.212.typein_Jan2013&langchoice=en">Guys</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 103, Column 103: reference to entity "langchoice" for which no system identifier could be generated
    …fun.net/webcam/guys/?AFNO=1-1-.99.US.212.typein_Jan2013&langchoice=en">Guys</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 101, Column 104: entity was defined here
    …freefun.net/signup/?AFNO=1-1-.99.US.212.typein_Jan2013&langchoice=en">Girls</a>
  • Error Line 116, Column 19: there is no attribute "id"
            <video id="webcam_feed" autoplay class="fancybox"></video>

    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 116, Column 42: "autoplay" is not a member of a group specified for any attribute
            <video id="webcam_feed" autoplay class="fancybox"></video>
  • Error Line 116, Column 48: there is no attribute "class"
            <video id="webcam_feed" autoplay class="fancybox"></video>

    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 116, Column 58: element "video" undefined
            <video id="webcam_feed" autoplay class="fancybox"></video>

    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 131, Column 153: required attribute "rows" not specified
    …lue=='')this.value=this.defaultValue;">enter your text here...</textarea></spa…

    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 131, Column 153: required attribute "cols" not specified
    …lue=='')this.value=this.defaultValue;">enter your text here...</textarea></spa…

    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 140, Column 223: end tag for "img" omitted, but OMITTAG NO was specified
    …'http://static.slutroulette.com/cr/global/images/restrictedtoadults.jpg'></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 140, Column 97: start tag was here
    … 5px; width: 90px; text-align: left;'><img height='45' alt='Restricted To Adul…
  • Error Line 156, Column 104: required attribute "alt" not specified
    …atic.slutroulette.com/cr/static/freecamsexposed.com/212/images/login_logo.png'>

    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 156, Column 105: end tag for "img" omitted, but OMITTAG NO was specified
    …atic.slutroulette.com/cr/static/freecamsexposed.com/212/images/login_logo.png'>

    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 156, Column 7: start tag was here
          <img src='http://static.slutroulette.com/cr/static/freecamsexposed.com/21…
  • Error Line 158, Column 59: end tag for "br" omitted, but OMITTAG NO was specified
          <p>Enter your email and password to sign in.</p><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 158, Column 55: start tag was here
          <p>Enter your email and password to sign in.</p><br>
  • Error Line 161, Column 54: end tag for "input" omitted, but OMITTAG NO was specified
          <input type="hidden" name="trylogin" value="1">

    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 161, Column 7: start tag was here
          <input type="hidden" name="trylogin" value="1">
  • Error Line 162, Column 51: end tag for "input" omitted, but OMITTAG NO was specified
          <input type="hidden" name="tries" value="1">

    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 162, Column 7: start tag was here
          <input type="hidden" name="tries" value="1">
  • Error Line 163, Column 54: end tag for "input" omitted, but OMITTAG NO was specified
              <input type="hidden" name="g" value="Lw==">

    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 163, Column 11: start tag was here
              <input type="hidden" name="g" value="Lw==">
  • Error Line 165, Column 76: end tag for "input" omitted, but OMITTAG NO was specified
              <input class="text" type="text" id="sausr" name="sausr" value="">

    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 165, Column 11: start tag was here
              <input class="text" type="text" id="sausr" name="sausr" value="">
  • Error Line 167, Column 71: end tag for "input" omitted, but OMITTAG NO was specified
              <input class="text" type="password" id="sapwd" name="sapwd">

    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 167, Column 11: start tag was here
              <input class="text" type="password" id="sapwd" name="sapwd">
  • Error Line 186, Column 48: an attribute value must be a literal unless it contains only name characters
    …t = $.parseJSON('{"3500":"<span class=\\\"status\\\">Status: Connected to part…

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

  • Error Line 186, Column 62: document type does not allow element "span" here
    …N('{"3500":"<span class=\\\"status\\\">Status: Connected to partner<\/span>","…

    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 186, Column 91: character "<" is the first character of a delimiter but occurred as data
    …tatus\\\">Status: Connected to partner<\/span>","5000":"<span class=\\\"system…

    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 186, Column 121: an attribute value must be a literal unless it contains only name characters
    … partner<\/span>","5000":"<span class=\\\"system_msg\\\">System message:<\/spa…

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

  • Warning Line 186, Column 155: character "<" is the first character of a delimiter but occurred as data
    …ass=\\\"system_msg\\\">System message:<\/span> You must be at least 18 to join…

    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 186, Column 230: an attribute value must be a literal unless it contains only name characters
    …oin Slutroulette","9000":"<span class=\\\"system_msg\\\">System message:<\/spa…

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

  • Warning Line 186, Column 264: character "<" is the first character of a delimiter but occurred as data
    …ass=\\\"system_msg\\\">System message:<\/span> Please verify your age to start…

    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 186, Column 336: an attribute value must be a literal unless it contains only name characters
    … start chatting","12000":"<span class=\\\"system_msg\\\">System message:<\/spa…

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

  • Warning Line 186, Column 370: character "<" is the first character of a delimiter but occurred as data
    …ass=\\\"system_msg\\\">System message:<\/span> To stay connected and chat you …

    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 186, Column 468: an attribute value must be a literal unless it contains only name characters
    …ree fun account","18000":"<span class=\\\"warning\\\">To Chat you must create …

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

  • Warning Line 186, Column 590: character "<" is the first character of a delimiter but occurred as data
    …Account to Verify your age. Please click the Verify button below .<\/span>"}');

    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 227, Column 35: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
            $('#chat_room').append('<p>Your Message could not be sent! To enable th…

    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>").

  • Warning Line 256, Column 26: character "<" is the first character of a delimiter but occurred as data
            if (video_counter<=6){

    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 260, Column 97: cannot generate system identifier for general entity "mini"
    …net/exports/golive/iframe/?height=375&mini=1&width=500&flip=0&wmode=transparen…

    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 260, Column 97: general entity "mini" not defined and no default entity
    …net/exports/golive/iframe/?height=375&mini=1&width=500&flip=0&wmode=transparen…

    This is usually a cascading error caused by 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 260, Column 101: reference not terminated by REFC delimiter
    …exports/golive/iframe/?height=375&mini=1&width=500&flip=0&wmode=transparent&AF…

    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 260, Column 101: reference to entity "mini" for which no system identifier could be generated
    …exports/golive/iframe/?height=375&mini=1&width=500&flip=0&wmode=transparent&AF…

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

  • Info Line 260, Column 96: entity was defined here
    ….net/exports/golive/iframe/?height=375&mini=1&width=500&flip=0&wmode=transpare…
  • Warning Line 260, Column 104: cannot generate system identifier for general entity "width"
    …orts/golive/iframe/?height=375&mini=1&width=500&flip=0&wmode=transparent&AFNO=…

    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 260, Column 104: general entity "width" not defined and no default entity
    …orts/golive/iframe/?height=375&mini=1&width=500&flip=0&wmode=transparent&AFNO=…

    This is usually a cascading error caused by 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 260, Column 109: reference not terminated by REFC delimiter
    …golive/iframe/?height=375&mini=1&width=500&flip=0&wmode=transparent&AFNO=1-1-.…

    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 260, Column 109: reference to entity "width" for which no system identifier could be generated
    …golive/iframe/?height=375&mini=1&width=500&flip=0&wmode=transparent&AFNO=1-1-.…

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

  • Info Line 260, Column 103: entity was defined here
    …ports/golive/iframe/?height=375&mini=1&width=500&flip=0&wmode=transparent&AFNO…
  • Warning Line 260, Column 114: cannot generate system identifier for general entity "flip"
    …e/iframe/?height=375&mini=1&width=500&flip=0&wmode=transparent&AFNO=1-1-.99.US…

    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 260, Column 114: general entity "flip" not defined and no default entity
    …e/iframe/?height=375&mini=1&width=500&flip=0&wmode=transparent&AFNO=1-1-.99.US…

    This is usually a cascading error caused by 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 260, Column 118: reference not terminated by REFC delimiter
    …rame/?height=375&mini=1&width=500&flip=0&wmode=transparent&AFNO=1-1-.99.US.212…

    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 260, Column 118: reference to entity "flip" for which no system identifier could be generated
    …rame/?height=375&mini=1&width=500&flip=0&wmode=transparent&AFNO=1-1-.99.US.212…

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

  • Info Line 260, Column 113: entity was defined here
    …ve/iframe/?height=375&mini=1&width=500&flip=0&wmode=transparent&AFNO=1-1-.99.U…
  • Warning Line 260, Column 121: cannot generate system identifier for general entity "wmode"
    …e/?height=375&mini=1&width=500&flip=0&wmode=transparent&AFNO=1-1-.99.US.212.ty…

    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 260, Column 121: general entity "wmode" not defined and no default entity
    …e/?height=375&mini=1&width=500&flip=0&wmode=transparent&AFNO=1-1-.99.US.212.ty…

    This is usually a cascading error caused by 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 260, Column 126: reference not terminated by REFC delimiter
    …ight=375&mini=1&width=500&flip=0&wmode=transparent&AFNO=1-1-.99.US.212.typein&…

    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 260, Column 126: reference to entity "wmode" for which no system identifier could be generated
    …ight=375&mini=1&width=500&flip=0&wmode=transparent&AFNO=1-1-.99.US.212.typein&…

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

  • Info Line 260, Column 120: entity was defined here
    …me/?height=375&mini=1&width=500&flip=0&wmode=transparent&AFNO=1-1-.99.US.212.t…
  • Warning Line 260, Column 139: cannot generate system identifier for general entity "AFNO"
    …&mini=1&width=500&flip=0&wmode=transparent&AFNO=1-1-.99.US.212.typein&only=1');

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 260, Column 139: general entity "AFNO" not defined and no default entity
    …&mini=1&width=500&flip=0&wmode=transparent&AFNO=1-1-.99.US.212.typein&only=1');

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

  • Warning Line 260, Column 143: reference not terminated by REFC delimiter
    …&mini=1&width=500&flip=0&wmode=transparent&AFNO=1-1-.99.US.212.typein&only=1');

    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 260, Column 143: reference to entity "AFNO" for which no system identifier could be generated
    …&mini=1&width=500&flip=0&wmode=transparent&AFNO=1-1-.99.US.212.typein&only=1');

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

  • Info Line 260, Column 138: entity was defined here
    …&mini=1&width=500&flip=0&wmode=transparent&AFNO=1-1-.99.US.212.typein&only=1');
  • Warning Line 260, Column 166: cannot generate system identifier for general entity "only"
    …&mini=1&width=500&flip=0&wmode=transparent&AFNO=1-1-.99.US.212.typein&only=1');

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 260, Column 166: general entity "only" not defined and no default entity
    …&mini=1&width=500&flip=0&wmode=transparent&AFNO=1-1-.99.US.212.typein&only=1');

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

  • Warning Line 260, Column 170: reference not terminated by REFC delimiter
    …&mini=1&width=500&flip=0&wmode=transparent&AFNO=1-1-.99.US.212.typein&only=1');

    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 260, Column 170: reference to entity "only" for which no system identifier could be generated
    …&mini=1&width=500&flip=0&wmode=transparent&AFNO=1-1-.99.US.212.typein&only=1');

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

  • Info Line 260, Column 165: entity was defined here
    …&mini=1&width=500&flip=0&wmode=transparent&AFNO=1-1-.99.US.212.typein&only=1');
  • Warning Line 276, Column 105: reference not terminated by REFC delimiter
    …/www.livefreefun.net/signup/?AFNO=1-1-.99.US.212.typein_Jan2013&langchoice=en',

    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 276, Column 105: reference to entity "langchoice" for which no system identifier could be generated
    …/www.livefreefun.net/signup/?AFNO=1-1-.99.US.212.typein_Jan2013&langchoice=en',

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

  • Info Line 101, Column 104: entity was defined here
    …freefun.net/signup/?AFNO=1-1-.99.US.212.typein_Jan2013&langchoice=en">Girls</a>
  • Warning Line 309, Column 97: reference not terminated by REFC delimiter
    …exports/golive/iframe/?height=375&mini=1&width=500&flip=0&wmode=transparent&AF…

    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 309, Column 97: reference to entity "mini" for which no system identifier could be generated
    …exports/golive/iframe/?height=375&mini=1&width=500&flip=0&wmode=transparent&AF…

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

  • Info Line 260, Column 96: entity was defined here
    ….net/exports/golive/iframe/?height=375&mini=1&width=500&flip=0&wmode=transpare…
  • Warning Line 309, Column 105: reference not terminated by REFC delimiter
    …golive/iframe/?height=375&mini=1&width=500&flip=0&wmode=transparent&AFNO=1-1-.…

    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 309, Column 105: reference to entity "width" for which no system identifier could be generated
    …golive/iframe/?height=375&mini=1&width=500&flip=0&wmode=transparent&AFNO=1-1-.…

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

  • Info Line 260, Column 103: entity was defined here
    …ports/golive/iframe/?height=375&mini=1&width=500&flip=0&wmode=transparent&AFNO…
  • Warning Line 309, Column 114: reference not terminated by REFC delimiter
    …rame/?height=375&mini=1&width=500&flip=0&wmode=transparent&AFNO=1-1-.99.US.212…

    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 309, Column 114: reference to entity "flip" for which no system identifier could be generated
    …rame/?height=375&mini=1&width=500&flip=0&wmode=transparent&AFNO=1-1-.99.US.212…

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

  • Info Line 260, Column 113: entity was defined here
    …ve/iframe/?height=375&mini=1&width=500&flip=0&wmode=transparent&AFNO=1-1-.99.U…
  • Warning Line 309, Column 122: reference not terminated by REFC delimiter
    …ight=375&mini=1&width=500&flip=0&wmode=transparent&AFNO=1-1-.99.US.212.typein&…

    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 309, Column 122: reference to entity "wmode" for which no system identifier could be generated
    …ight=375&mini=1&width=500&flip=0&wmode=transparent&AFNO=1-1-.99.US.212.typein&…

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

  • Info Line 260, Column 120: entity was defined here
    …me/?height=375&mini=1&width=500&flip=0&wmode=transparent&AFNO=1-1-.99.US.212.t…
  • Warning Line 309, Column 139: reference not terminated by REFC delimiter
    …&mini=1&width=500&flip=0&wmode=transparent&AFNO=1-1-.99.US.212.typein&only=1');

    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 309, Column 139: reference to entity "AFNO" for which no system identifier could be generated
    …&mini=1&width=500&flip=0&wmode=transparent&AFNO=1-1-.99.US.212.typein&only=1');

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

  • Info Line 260, Column 138: entity was defined here
    …&mini=1&width=500&flip=0&wmode=transparent&AFNO=1-1-.99.US.212.typein&only=1');
  • Warning Line 309, Column 166: reference not terminated by REFC delimiter
    …&mini=1&width=500&flip=0&wmode=transparent&AFNO=1-1-.99.US.212.typein&only=1');

    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 309, Column 166: reference to entity "only" for which no system identifier could be generated
    …&mini=1&width=500&flip=0&wmode=transparent&AFNO=1-1-.99.US.212.typein&only=1');

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

  • Info Line 260, Column 165: entity was defined here
    …&mini=1&width=500&flip=0&wmode=transparent&AFNO=1-1-.99.US.212.typein&only=1');
  • Warning Line 310, Column 56: character "&" is the first character of a delimiter but occurred as data
    …f(document.createElement('video').canPlayType && ( navigator.getUserMedia )  ){

    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 310, Column 57: character "&" is the first character of a delimiter but occurred as data
    …f(document.createElement('video').canPlayType && ( navigator.getUserMedia )  ){

    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 369, Column 43: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
                    $('#chat_room').append('<p>' + data + '</p>');

    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 373, Column 10: end tag for "span" omitted, but OMITTAG NO was specified
     </script><div id='template_footer' style="height: 0px; width: 0px; overflow: h…

    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 186, Column 456: start tag was here
    …ate a Live free fun account","18000":"<span class=\\\"warning\\\">To Chat you …
  • Error Line 373, Column 10: end tag for "span" omitted, but OMITTAG NO was specified
     </script><div id='template_footer' style="height: 0px; width: 0px; overflow: h…

    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 186, Column 324: start tag was here
    … your age to start chatting","12000":"<span class=\\\"system_msg\\\">System me…
  • Error Line 373, Column 10: end tag for "span" omitted, but OMITTAG NO was specified
     </script><div id='template_footer' style="height: 0px; width: 0px; overflow: h…

    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 186, Column 218: start tag was here
    …east 18 to join Slutroulette","9000":"<span class=\\\"system_msg\\\">System me…
  • Error Line 373, Column 10: end tag for "span" omitted, but OMITTAG NO was specified
     </script><div id='template_footer' style="height: 0px; width: 0px; overflow: h…

    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 186, Column 109: start tag was here
    …Connected to partner<\/span>","5000":"<span class=\\\"system_msg\\\">System me…
  • Error Line 373, Column 10: end tag for "span" omitted, but OMITTAG NO was specified
     </script><div id='template_footer' style="height: 0px; width: 0px; overflow: h…

    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 186, Column 36: start tag was here
        object = $.parseJSON('{"3500":"<span class=\\\"status\\\">Status: Connected…
  • Error Line 390, Column 246: required attribute "alt" not specified
    ….php?zoneid=3914&amp;cb=1411055390&amp;n=ad0b8d8c' border='0' /></a></noscript>

    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 391, Column 58: required attribute "type" not specified
        <script src="http://www.crakmedia.com/js/punderad.js"></script>

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

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

  • Error Line 407, Column 246: required attribute "alt" not specified
    ….php?zoneid=4001&amp;cb=2032218722&amp;n=a0301f7c' border='0' /></a></noscript>

    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>.

Visitor Analysis

Daily Visitor
  • 9.917 visits

In Page Analysis