is an adult video tube, where presented only hot teen girls. Young and delicious bodies are trembling of lust and desire. Our teens want your attention! ...

charmingteen.net
  • Domain Name
    charmingteen.net
  • Favicon
  • Google Page Rank
    0
  • Alexa Rank
    #168099
  • Page Size
    33.2 KB
  • Ip Address
    173.244.205.243
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    1 GIF, 100 JPG, 0 PNG

Website Meta Analysis

  • Title
    Charming Teen- Bluemovies, porno of tube for the grown man!We offer the free viewing of video!
  • Meta Keyword
    charmingteen, teen videos, charming tube,tube teen videos, free tube videos, tube teen, charming teen ,tube porn,free teen videos,teen porn
  • Meta Description
    is an adult video tube, where presented only hot teen girls. Young and delicious bodies are trembling of lust and desire. Our teens want your attention!

Technical Analysis

  • Webserver
    nginx/0.7.46
  • Ip Address
    173.244.205.243
  • Domain Age
    11 Months, 15 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from charmingteen.net.

HTML Analysis

  • server: nginx/0.7.46
  • date: Sun, 15 Sep 2013 18:49:43 GMT
  • content-type: text/html; charset=UTF-8
  • connection: keep-alive
  • x-powered-by: PHP/5.1.6
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for charmingteen.net

DNS Analysis


DNS servers
ns1.nudegirlsgalleries.net [184.82.156.154]
ns2.nudegirlsgalleries.net [184.82.156.155]


DNS Records

Answer records
charmingteen.net TXT v=spf1 ip4:184.82.156.154 a mx ~all 3600s
charmingteen.net SOA
server: agressormail.server.com
email: root@agressormail.server.com
serial: 2012100504
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 86400
3600s
charmingteen.net NS  ns1.sexxxytube.net 3600s
charmingteen.net NS  ns2.sexxxytube.net 3600s
charmingteen.net MX
preference: 10
exchange: mail.charmingteen.net
3600s
charmingteen.net MX
preference: 20
exchange: mail.charmingteen.net
3600s
charmingteen.net A 184.82.156.154 3600s

Authority records

Additional records
ns1.sexxxytube.net A 184.82.156.154 3600s
ns2.sexxxytube.net A 184.82.156.155 3600s
mail.charmingteen.net A 184.82.156.155 3600s

IP 173.244.205.243 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 188 Errors
  • 121 Warnings
Ratio Text/Html
  • 0.8088537688737442
Message Error
  • Error Line 1, Column 1: no document type declaration; will parse without validation
    <script type="text/javascript" src="tools/flash_detect.js"></script>

    The document type could not be determined, because the document had no correct DOCTYPE declaration. The document does not look like HTML, therefore automatic fallback could not be performed, and the document was only checked against basic markup syntax.

    Learn how to add a doctype to your document from our FAQ, or use the validator's Document Type option to validate your document against a specific Document Type.

  • Error Line 2, Column 31: document type does not allow element "SCRIPT" here
    <script type="text/javascript"> 

    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 5, Column 71: cannot generate system identifier for general entity "p"
    …/charmingteen.net/tp/out.php?link=google_com&p=100&url=http://google.com"     	

    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 5, Column 71: general entity "p" not defined and no default entity
    …/charmingteen.net/tp/out.php?link=google_com&p=100&url=http://google.com"     	

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

  • Error Line 5, Column 72: reference to entity "p" for which no system identifier could be generated
    …/charmingteen.net/tp/out.php?link=google_com&p=100&url=http://google.com"     	

    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 5, Column 70: entity was defined here
    …/charmingteen.net/tp/out.php?link=google_com&p=100&url=http://google.com"     	

Visitor Analysis

Daily Visitor
  • 618 visits