solotouch.com has Alexa Rank 77.705 and Google Page Rank is 4

solotouch.com
  • Domain Name
    solotouch.com
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #77705
  • Page Size
    18.3 KB
  • Ip Address
    70.42.141.152
  • Heading
    H1: 1, H2: 0, H3: 2, H4: 0, H5: 0, H6: 0
  • Images
    1 GIF, 2 JPG, 0 PNG

Website Meta Analysis

  • Title
    | Solo Touch
  • Meta Keyword
    masturbation,sexuality,solotouch,
  • Meta Description

Technical Analysis

  • Webserver
    Apache/2.2.3 (CentOS)
  • Ip Address
    70.42.141.152
  • Domain Age
    10 Years, 11 Months, 26 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Sun, 29 Sep 2013 02:35:05 GMT
  • server: Apache/2.2.3 (CentOS)
  • x-powered-by: PHP/5.3.10
  • x-cp1: AC:bf
  • content-length: 17998
  • content-type: text/html; charset=UTF-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: SOLOTOUCH.COM
Created on: 30-Oct-02
Expires on: 30-Oct-13
Last Updated on: 22-Apr-11

Registrant:
Stripe Media Inc.
534 16th Ave. W
Kirkland, Washington 98033
United States

Administrative Contact:
Spaits, Todd email
Stripe Media Inc.
534 16th Ave. W
Kirkland, Washington 98033
United States
2064992879 Fax -- 2065295150

Technical Contact:
Spaits, Todd email
Stripe Media Inc.
534 16th Ave. W
Kirkland, Washington 98033
United States
2064992879 Fax -- 2065295150

Domain servers in listed order:
DNS01.JOLOKIANET.NET
DNS02.JOLOKIANET.NET

DNS Analysis


DNS servers
dns01.jolokianet.net
dns02.jolokianet.net


DNS Records

Answer records
solotouch.com SOA
server: dns01.jolokianet.net
email: support@yankssupport.com
serial: 2010123000
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 3600
86400s
solotouch.com MX
preference: 10
exchange: mail.solotouch.com
86400s
solotouch.com NS  dns01.jolokianet.net 86400s
solotouch.com A 70.42.141.152 3600s
solotouch.com NS  dns02.jolokianet.net 86400s

Authority records

Additional records
mail.solotouch.com A 74.217.67.46 86400s

IP 70.42.141.152 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Scotts Valley
  • Continent Code
    95066
  • Latitude
    831
  • Longitude
    828
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 70.42.141.152"
    #
    # Use "?" to get help.
    #

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

    Jolokia Corp. INAP-SJE-JOLOKIA-30323 (NET-70-42-141-0-1) 70.42.141.0 - 70.42.141.255
    Internap Network Services Corporation PNAP-09-2005 (NET-70-42-0-0-1) 70.42.0.0 - 70.42.255.255


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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 47 Errors
  • 33 Warnings
Ratio Text/Html
  • 0.49168
Message Error
  • Error Line 13, Column 12: there is no attribute "name"
    <META name="verify-v1" content="iSRG9s5w/Cr13pFUzvQMUl3ZJ80/QNg4j0Ut0Zaham4=" />

    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 13, Column 32: there is no attribute "content"
    <META name="verify-v1" content="iSRG9s5w/Cr13pFUzvQMUl3ZJ80/QNg4j0Ut0Zaham4=" />

    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 13, Column 80: element "META" undefined
    <META name="verify-v1" content="iSRG9s5w/Cr13pFUzvQMUl3ZJ80/QNg4j0Ut0Zaham4=" />

    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 37, Column 1037: cannot generate system identifier for general entity "step"
    …="https://join.solotouch.com/signup/signup.php?nats=MC4wLjkuOS4wLjAuMC4w&step=2

    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 37, Column 1037: general entity "step" not defined and no default entity
    …="https://join.solotouch.com/signup/signup.php?nats=MC4wLjkuOS4wLjAuMC4w&step=2

    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 37, Column 1041: reference not terminated by REFC delimiter
    …="https://join.solotouch.com/signup/signup.php?nats=MC4wLjkuOS4wLjAuMC4w&step=2

    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 37, Column 1041: reference to external entity in attribute value
    …="https://join.solotouch.com/signup/signup.php?nats=MC4wLjkuOS4wLjAuMC4w&step=2

    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 37, Column 1041: reference to entity "step" for which no system identifier could be generated
    …="https://join.solotouch.com/signup/signup.php?nats=MC4wLjkuOS4wLjAuMC4w&step=2

    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 37, Column 1036: entity was defined here
    …="https://join.solotouch.com/signup/signup.php?nats=MC4wLjkuOS4wLjAuMC4w&step=2
  • Error Line 38, Column 124: there is no attribute "HREF"
    …</a></p></div><p class="cent"><A HREF="http://www.eff.org/br" target="blank"><…

    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 38, Column 155: there is no attribute "target"
    …A HREF="http://www.eff.org/br" target="blank"><IMG SRC="http://www.eff.org/br/…

    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 38, Column 162: element "A" undefined
    …"http://www.eff.org/br" target="blank"><IMG SRC="http://www.eff.org/br/brstrip…

    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 38, Column 172: there is no attribute "SRC"
    …://www.eff.org/br" target="blank"><IMG SRC="http://www.eff.org/br/brstrip.gif" 

    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 39, Column 5: there is no attribute "ALT"
    ALT="Join the Blue Ribbon Online Free Speech Campaign"

    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 40, Column 8: there is no attribute "HEIGHT"
    HEIGHT="41" WIDTH="150" BORDER="0" ALIGN="MIDDLE">

    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 40, Column 19: there is no attribute "WIDTH"
    HEIGHT="41" WIDTH="150" BORDER="0" ALIGN="MIDDLE">

    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 40, Column 32: there is no attribute "BORDER"
    HEIGHT="41" WIDTH="150" BORDER="0" ALIGN="MIDDLE">

    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 40, Column 42: there is no attribute "ALIGN"
    HEIGHT="41" WIDTH="150" BORDER="0" ALIGN="MIDDLE">

    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 40, Column 50: element "IMG" undefined
    HEIGHT="41" WIDTH="150" BORDER="0" ALIGN="MIDDLE">

    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 41, Column 6: end tag for element "img" which is not open
    </img></a></p></div>

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

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

  • Error Line 41, Column 10: end tag for element "a" which is not open
    </img></a></p></div>

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

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

  • Error Line 41, Column 14: end tag for "IMG" omitted, but OMITTAG NO was specified
    </img></a></p></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 38, Column 163: start tag was here
    …http://www.eff.org/br" target="blank"><IMG SRC="http://www.eff.org/br/brstrip.…
  • Error Line 41, Column 14: end tag for "A" omitted, but OMITTAG NO was specified
    </img></a></p></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 38, Column 116: start tag was here
    …Entrance</a></p></div><p class="cent"><A HREF="http://www.eff.org/br" target="…
  • Error Line 44, Column 205: end tag for "img" omitted, but OMITTAG NO was specified
    …uch.com/images/icra.gif" alt="ICRA" width="88" height="31" border="0"></a></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 44, Column 109: start tag was here
    ….com/protectkids.php" target="_blank"><img src="http://solotouch.com/images/ic…
  • Error Line 49, Column 204: end tag for "img" omitted, but OMITTAG NO was specified
    …touch.com/images/rta.gif" alt="RTA" width="88" height="31" border="0"></a></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 49, Column 110: start tag was here
    ….com/protectkids.php" target="_blank"><img src="http://solotouch.com/images/rt…

Visitor Analysis

Daily Visitor
  • 1.517 visits