2girlsteachsex.com

Learn authentic, honest techniques to give your girl the most incredible, heart pounding orgasms of her entire life. ...

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

Overview Info

  • Domain Name
    2girlsteachsex.com
  • Favicon
  • Alexa Rank
    #96347
  • Google Page Rank
    PR 1
  • Ip Address
    184.106.32.193
  • Page Size
    12.5 KB
  • Images
    1 GIF, 4 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 0 0 0 0

Website Meta Analysis

  • Title
    2 Girls Teach Sex
  • Meta Keyword
    2 girls teach sex, shawna lenee, bobby brandshaw, sex advice
  • Meta Description
    Learn authentic, honest techniques to give your girl the most incredible, heart pounding orgasms of her entire life.

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    184.106.32.193
  • Domain Age
    4 Years, 2 Months, 25 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Fri, 21 Jun 2013 08:48:08 GMT
  • server: Apache
  • last-modified: Fri, 22 Feb 2013 22:57:12 GMT
  • etag: "20e1d4d-2e3a-4d6581c978200"
  • accept-ranges: bytes
  • content-length: 11834
  • x-powered-by: PleskLin
  • connection: close
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
JGP
755 boylton street
502
Boston, Massachusetts 02116
United States
Domain Domain Name: 2GIRLSTEACHSEX.COM
Created: 18-Apr-09
Expires: 18-Apr-19
Updated: 19-Jun-11
Administrative Contact:
Golder, Josh email
JGP
755 boylton street
502
Boston, Massachusetts 02116
United States
+1.6172838693 Fax -
Technical Contact:
Golder, Josh email
JGP
755 boylton street
502
Boston, Massachusetts 02116
United States
+1.6172838693 Fax -
Name Servers:
NS.RACKSPACE.COM
NS2.RACKSPACE.COM

0

DNS Analysis


DNS servers
ns2.rackspace.com [65.61.188.4]
ns.rackspace.com [69.20.95.4]


DNS Records

Answer records
2girlsteachsex.com SOA
server: ns.rackspace.com
email: hostmaster@rackspace.com
serial: 1353477774
refresh: 3600
retry: 300
expire: 1814400
minimum ttl: 300
300s
2girlsteachsex.com A 184.106.32.193 86400s
2girlsteachsex.com TXT v=spf1 a mx ptr a:2girlsteachsex.com mx:mail.2girlsteachsex.com include:icpbounce.com ip4:72.3.253.68 ip4:184.106.32.193 ip4:64.50.144.0/20 ~all 86400s
2girlsteachsex.com MX
preference: 10
exchange: mail.2girlsteachsex.com
86400s
2girlsteachsex.com NS  ns.rackspace.com 86400s
2girlsteachsex.com NS  ns2.rackspace.com 86400s

Authority records

Additional records
mail.2girlsteachsex.com A 184.106.32.193 86400s

IP 184.106.32.193 Analysis

  • Country Code
    GB
  • Country Code3
    GBR
  • Country Name
    United Kingdom
  • City
    London
  • Continent Code
    EU
  • Latitude
    51.5002
  • Longitude
    0.1262
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 184.106.32.193"
    #
    # Use "?" to get help.
    #

    #
    # The following results may also be obtained via:
    # http://whois.arin.net/rest/nets;q=184.106.32.193?showDetails=true&showARIN=false&ext=netref2
    #

    Booth Bv RACKS-8-1286245806983319 (NET-184-106-32-192-1) 184.106.32.192 - 184.106.32.199
    Rackspace Hosting RACKS-8-NET-4 (NET-184-106-0-0-1) 184.106.0.0 - 184.106.255.255


    #
    # ARIN WHOIS data and services are subject to the Terms of Use
    # available at: https://www.arin.net/whois_tou.html
    #

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 82 Errors
  • 10 Warnings
Ratio Text/Html
  • 0.44939239513916107
Message Error
  • Error Line 11, Column 8: required attribute "type" not specified
    <script>function utmx_section(){}function utmx(){}(function(){var

    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 15, Column 56: character "<" is the first character of a delimiter but occurred as data
    indexOf(';',i);return escape(c.substring(i+n.length+1,j<0?c.

    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 17, Column 5: an attribute specification must start with a name or name token
    '<sc'+'ript src="'+'http'+(l.protocol=='https:'?'s://ssl':

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 17, Column 5: element "sc" undefined
    '<sc'+'ript src="'+'http'+(l.protocol=='https:'?'s://ssl':

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 19, Column 3: cannot generate system identifier for general entity "utmx"
    '&utmx='+(x?x:'')+'&utmxx='+(xx?xx:'')+'&utmxtime='+new Date().

    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 19, Column 3: general entity "utmx" not defined and no default entity
    '&utmx='+(x?x:'')+'&utmxx='+(xx?xx:'')+'&utmxtime='+new Date().

    This is usually a cascading error caused by 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 19, Column 7: reference not terminated by REFC delimiter
    '&utmx='+(x?x:'')+'&utmxx='+(xx?xx:'')+'&utmxtime='+new Date().

    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 19, Column 7: reference to entity "utmx" for which no system identifier could be generated
    '&utmx='+(x?x:'')+'&utmxx='+(xx?xx:'')+'&utmxtime='+new Date().

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

  • Info Line 19, Column 2: entity was defined here
    '&utmx='+(x?x:'')+'&utmxx='+(xx?xx:'')+'&utmxtime='+new Date().
  • Warning Line 19, Column 21: cannot generate system identifier for general entity "utmxx"
    '&utmx='+(x?x:'')+'&utmxx='+(xx?xx:'')+'&utmxtime='+new Date().

    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 19, Column 21: general entity "utmxx" not defined and no default entity
    '&utmx='+(x?x:'')+'&utmxx='+(xx?xx:'')+'&utmxtime='+new Date().

    This is usually a cascading error caused by 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 19, Column 26: reference not terminated by REFC delimiter
    '&utmx='+(x?x:'')+'&utmxx='+(xx?xx:'')+'&utmxtime='+new Date().

    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 19, Column 26: reference to entity "utmxx" for which no system identifier could be generated
    '&utmx='+(x?x:'')+'&utmxx='+(xx?xx:'')+'&utmxtime='+new Date().

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

  • Info Line 19, Column 20: entity was defined here
    '&utmx='+(x?x:'')+'&utmxx='+(xx?xx:'')+'&utmxtime='+new Date().
  • Warning Line 19, Column 42: cannot generate system identifier for general entity "utmxtime"
    '&utmx='+(x?x:'')+'&utmxx='+(xx?xx:'')+'&utmxtime='+new Date().

    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 19, Column 42: general entity "utmxtime" not defined and no default entity
    '&utmx='+(x?x:'')+'&utmxx='+(xx?xx:'')+'&utmxtime='+new Date().

    This is usually a cascading error caused by 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 19, Column 50: reference not terminated by REFC delimiter
    '&utmx='+(x?x:'')+'&utmxx='+(xx?xx:'')+'&utmxtime='+new Date().

    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 19, Column 50: reference to entity "utmxtime" for which no system identifier could be generated
    '&utmx='+(x?x:'')+'&utmxx='+(xx?xx:'')+'&utmxtime='+new Date().

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

  • Info Line 19, Column 41: entity was defined here
    '&utmx='+(x?x:'')+'&utmxx='+(xx?xx:'')+'&utmxtime='+new Date().
  • Warning Line 20, Column 16: cannot generate system identifier for general entity "utmxhash"
    valueOf()+(h?'&utmxhash='+escape(h.substr(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 20, Column 16: general entity "utmxhash" not defined and no default entity
    valueOf()+(h?'&utmxhash='+escape(h.substr(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 20, Column 24: reference not terminated by REFC delimiter
    valueOf()+(h?'&utmxhash='+escape(h.substr(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 20, Column 24: reference to entity "utmxhash" for which no system identifier could be generated
    valueOf()+(h?'&utmxhash='+escape(h.substr(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 20, Column 15: entity was defined here
    valueOf()+(h?'&utmxhash='+escape(h.substr(1)):'')+
  • Warning Line 21, Column 43: character "<" is the first character of a delimiter but occurred as data
    '" type="text/javascript" charset="utf-8"><\/sc'+'ript>')})();

    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 22, Column 9: end tag for "sc" omitted, but OMITTAG NO was specified
    </script><script>utmx('url','A/B');</script>

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

  • Info Line 17, Column 2: start tag was here
    '<sc'+'ript src="'+'http'+(l.protocol=='https:'?'s://ssl':
  • Error Line 22, Column 17: required attribute "type" not specified
    </script><script>utmx('url','A/B');</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 42, Column 13: there is no attribute "name"
    	<META name="keywords" content="2 girls teach sex, shawna lenee, bobby brandsha…

    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 42, Column 32: there is no attribute "content"
    	<META name="keywords" content="2 girls teach sex, shawna lenee, bobby brandsha…

    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 42, Column 94: element "META" undefined
    …ywords" content="2 girls teach sex, shawna lenee, bobby brandshaw, sex advice">

    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 44, Column 153: element "META" undefined
    …ive your girl the most incredible, heart pounding orgasms of her entire life.">

    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 48, Column 13: there is no attribute "NAME"
    	<META NAME="distribution" CONTENT="Global">

    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 48, Column 36: there is no attribute "CONTENT"
    	<META NAME="distribution" CONTENT="Global">

    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 48, Column 44: element "META" undefined
    	<META NAME="distribution" CONTENT="Global">

    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 50, Column 50: element "META" undefined
    	<META NAME="Classification" CONTENT="sex advice">

    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 52, Column 155: element "META" undefined
    … Rights Reserved, No duplication of any content is permitted without consent.">

    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 54, Column 45: element "META" undefined
    	<META name="Revisit-After" content="3 Days">

    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 56, Column 45: element "META" undefined
    	<META name="robots" content="index, follow">

    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 58, Column 39: element "META" undefined
    	<META name="Rating" content="General">

    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 60, Column 35: element "META" undefined
    	<META name="Robots" content="All">

    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 221, Column 7: end tag for "META" omitted, but OMITTAG NO was specified
    </head>

    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 60, Column 2: start tag was here
    	<META name="Robots" content="All">
  • Error Line 221, Column 7: end tag for "META" omitted, but OMITTAG NO was specified
    </head>

    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 58, Column 2: start tag was here
    	<META name="Rating" content="General">
  • Error Line 221, Column 7: end tag for "META" omitted, but OMITTAG NO was specified
    </head>

    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 56, Column 2: start tag was here
    	<META name="robots" content="index, follow">
  • Error Line 221, Column 7: end tag for "META" omitted, but OMITTAG NO was specified
    </head>

    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 54, Column 2: start tag was here
    	<META name="Revisit-After" content="3 Days">
  • Error Line 221, Column 7: end tag for "META" omitted, but OMITTAG NO was specified
    </head>

    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 52, Column 2: start tag was here
    	<META name="Copyright" content="Copyright (c) 2009-2012, ISN Education, All Ri…
  • Error Line 221, Column 7: end tag for "META" omitted, but OMITTAG NO was specified
    </head>

    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 50, Column 2: start tag was here
    	<META NAME="Classification" CONTENT="sex advice">
  • Error Line 221, Column 7: end tag for "META" omitted, but OMITTAG NO was specified
    </head>

    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 48, Column 2: start tag was here
    	<META NAME="distribution" CONTENT="Global">
  • Error Line 221, Column 7: end tag for "META" omitted, but OMITTAG NO was specified
    </head>

    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 44, Column 2: start tag was here
    	<META name="description" content="Learn authentic, honest techniques to give y…
  • Error Line 221, Column 7: end tag for "META" omitted, but OMITTAG NO was specified
    </head>

    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 42, Column 2: start tag was here
    	<META name="keywords" content="2 girls teach sex, shawna lenee, bobby brandsha…
  • Error Line 241, Column 403: required attribute "alt" not specified
    …rm you\'re 18 years old, Enter your email before you can continue. ')" /><br />

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

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

  • Error Line 242, Column 120: required attribute "alt" not specified
    …om/graphics/template_subheader_as_seen_on_maxim.jpg" width="898" height="35" />

    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 259, Column 106: there is no attribute "border"
    …51" height="822" bgcolor="#FFFFFF" style="border-color:#2C181BF"border="1"><ul>

    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 260, Column 32: document type does not allow element "div" here; assuming missing "li" start-tag
                <div align="center">
  • Error Line 263, Column 149: required attribute "alt" not specified
    …http://2girlsteachsex.com/graphics/2gts4.jpg" width="192" height="263" /><br />

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

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

  • Error Line 267, Column 26: end tag for element "script" which is not open
                  <p></script><form method=post action="https://app.icontact.com/ic…

    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 267, Column 40: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …             <p></script><form method=post action="https://app.icontact.com/ic…
  • Error Line 267, Column 193: document type does not allow element "form" here; missing one of "object", "applet", "map", "iframe", "ins", "del" start-tag
    …icpsignup4174" accept-charset="UTF-8" onsubmit="return verifyRequired4174();" >

    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 268, Column 13: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <input type=hidden name=redirect value="http://www.2girlsteachsex.com/cmd.php?a…
  • Error Line 268, Column 25: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <input type=hidden name=redirect value="http://www.2girlsteachsex.com/cmd.php?a…
  • Error Line 269, Column 13: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <input type=hidden name=errorredirect value="http://www.2girlsteachsex.com/cmd.…
  • Error Line 269, Column 25: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <input type=hidden name=errorredirect value="http://www.2girlsteachsex.com/cmd.…
  • Error Line 274, Column 29: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
          <td colspan="2" align=right valign=top class="style96"><div align="center…
  • Error Line 274, Column 42: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …   <td colspan="2" align=right valign=top class="style96"><div align="center">…
  • Error Line 281, Column 17: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
          <td align=right valign=top class="style96">Email      </td>
  • Error Line 281, Column 30: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
          <td align=right valign=top class="style96">Email      </td>
  • Error Line 282, Column 17: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
          <td align=left>
  • Error Line 283, Column 41: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
            <input name="fields_email" type=text size="30">      </td>
  • Error Line 283, Column 56: end tag for "input" omitted, but OMITTAG NO was specified
            <input name="fields_email" type=text size="30">      </td>

    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 283, Column 9: start tag was here
            <input name="fields_email" type=text size="30">      </td>
  • Error Line 285, Column 17: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        <input type=hidden name="listid" value="27262">
  • Error Line 285, Column 51: document type does not allow element "input" here
        <input type=hidden name="listid" value="27262">

    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 285, Column 52: end tag for "input" omitted, but OMITTAG NO was specified
        <input type=hidden name="listid" value="27262">

    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 285, Column 5: start tag was here
        <input type=hidden name="listid" value="27262">
  • Error Line 286, Column 17: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        <input type=hidden name="specialid:27262" value="CXQ1">
  • Error Line 286, Column 59: document type does not allow element "input" here
        <input type=hidden name="specialid:27262" value="CXQ1">

    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 286, Column 60: end tag for "input" omitted, but OMITTAG NO was specified
        <input type=hidden name="specialid:27262" value="CXQ1">

    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 286, Column 5: start tag was here
        <input type=hidden name="specialid:27262" value="CXQ1">
  • Error Line 288, Column 17: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        <input type=hidden name=clientid value="575967">
  • Error Line 288, Column 29: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        <input type=hidden name=clientid value="575967">
  • Error Line 288, Column 52: document type does not allow element "input" here
        <input type=hidden name=clientid value="575967">

    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 288, Column 53: end tag for "input" omitted, but OMITTAG NO was specified
        <input type=hidden name=clientid value="575967">

    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 288, Column 5: start tag was here
        <input type=hidden name=clientid value="575967">
  • Error Line 289, Column 17: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        <input type=hidden name=formid value="4174">
  • Error Line 289, Column 29: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        <input type=hidden name=formid value="4174">
  • Error Line 289, Column 48: document type does not allow element "input" here
        <input type=hidden name=formid value="4174">

    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 289, Column 49: end tag for "input" omitted, but OMITTAG NO was specified
        <input type=hidden name=formid value="4174">

    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 289, Column 5: start tag was here
        <input type=hidden name=formid value="4174">
  • Error Line 290, Column 17: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        <input type=hidden name=reallistid value="1">
  • Error Line 290, Column 29: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        <input type=hidden name=reallistid value="1">
  • Error Line 290, Column 49: document type does not allow element "input" here
        <input type=hidden name=reallistid value="1">

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

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

  • Error Line 290, Column 50: end tag for "input" omitted, but OMITTAG NO was specified
        <input type=hidden name=reallistid 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 290, Column 5: start tag was here
        <input type=hidden name=reallistid value="1">
  • Error Line 291, Column 17: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        <input type=hidden name=doubleopt value="0">
  • Error Line 291, Column 29: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        <input type=hidden name=doubleopt value="0">
  • Error Line 291, Column 48: document type does not allow element "input" here
        <input type=hidden name=doubleopt value="0">

    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 291, Column 49: end tag for "input" omitted, but OMITTAG NO was specified
        <input type=hidden name=doubleopt value="0">

    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 291, Column 5: start tag was here
        <input type=hidden name=doubleopt value="0">
  • Error Line 300, Column 115: end tag for "input" omitted, but OMITTAG NO was specified
    …ubmit" value="Submit" src="http://2girlsteachsex.com/graphics/amn_button.gif" >

    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 300, Column 9: start tag was here
            <input type="image" name="Submit" value="Submit" src="http://2girlsteac…
  • Error Line 306, Column 23: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
                        <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 327, Column 18: end tag for "p" 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 267, Column 15: start tag was here
                  <p></script><form method=post action="https://app.icontact.com/ic…
  • Error Line 328, Column 15: end tag for "li" omitted, but OMITTAG NO was specified
              </ul>

    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 260, Column 13: start tag was here
                <div align="center">
  • Error Line 366, Column 26: document type does not allow element "blockquote" here; assuming missing "li" start-tag
                  <blockquote>
  • Error Line 395, Column 15: end tag for "li" omitted, but OMITTAG NO was specified
              </ul></td>

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

  • Info Line 366, Column 15: start tag was here
                  <blockquote>

Visitor Analysis

Daily Visitor
  • 6.767 visits
Daily Visitor

In Page Analysis