Favorite Preteens BANNED PT pics and vids here :) Hard to find CUSTOM SETS! 12yo~17yo Jailbait Lols FRESH homemade LOLs galleries Huge archive of FREE content! LITTLE Russian F#CKs Fresh Daily NN pics ...

9to12.org
  • Domain Name
    9to12.org
  • Favicon
  • Google Page Rank
    1
  • Alexa Rank
    #245019
  • Page Size
    156.7 KB
  • Ip Address
    94.102.52.50
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    240 GIF, 76 JPG, 0 PNG

Website Meta Analysis

  • Title
    9 to 12 - Only little petite preteen models 9 to 12 years old. Free Nonude NN totty lolly galleries
  • Meta Keyword
  • Meta Description
    Favorite Preteens BANNED PT pics and vids here :) Hard to find CUSTOM SETS! 12yo~17yo Jailbait Lols FRESH homemade LOLs galleries Huge archive of FREE content! LITTLE Russian F#CKs Fresh Daily NN pics and VIDS New HQ VIDEOS added daily Lolli ...

Technical Analysis

  • Webserver
    nginx
  • Ip Address
    94.102.52.50
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from 9to12.org.

HTML Analysis

  • server: nginx
  • date: Sat, 15 Jun 2013 11:59:04 GMT
  • content-type: text/html
  • connection: close
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for 9to12.org

DNS Analysis


DNS servers
ns1.nnlightspeed.com [94.102.52.48]
ns2.nnlightspeed.com [94.102.52.49]


DNS Records

Answer records
9to12.org MX
preference: 10
exchange: mail.9to12.org
14400s
9to12.org TXT v=spf1 a mx ip4:94.102.52.50 ~all 14400s
9to12.org SOA
server: ns1.nnlightspeed.com
email: hostmaster@9to12.org
serial: 2011101200
refresh: 14400
retry: 3600
expire: 1209600
minimum ttl: 86400
14400s
9to12.org NS  ns1.nnlightspeed.com 14400s
9to12.org NS  ns2.nnlightspeed.com 14400s
9to12.org A 94.102.52.50 14400s

Authority records

Additional records
mail.9to12.org A 94.102.52.50 14400s
ns1.nnlightspeed.com A 94.102.52.48 14400s
ns2.nnlightspeed.com A 94.102.52.49 14400s

IP 94.102.52.50 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 855 Errors
  • 20 Warnings
Ratio Text/Html
  • 0.6953283725336226
Message Error
  • Error Line 33, Column 28: required attribute "TYPE" not specified
    <script language=JavaScript>

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

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

  • Error Line 71, Column 8: required attribute "TYPE" not specified
    <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>.

  • Warning Line 75, Column 38: NET-enabling start-tag requires SHORTTAG YES
    <script language=javascript type=text/javascript>

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

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

  • Error Line 85, Column 9: end tag for element "SCRIPT" which is not open
    </script>

    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 88, Column 22: document type does not allow element "BASE" here
    <base target="_blank">

    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 94, Column 7: end tag for element "HEAD" which is not open
    </head>

    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.

Visitor Analysis

Daily Visitor
  • 840 visits
Daily Visitor