See Celebrity Fakes the way you always wanted to see them! Free fun fake celebrity site! Updates often with new nude celebrity pics. For adults only! ...

cfake.com
  • Domain Name
    cfake.com
  • Favicon
  • Google Page Rank
    1
  • Alexa Rank
    #16016
  • Page Size
    5.2 KB
  • Ip Address
    64.237.54.187
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
    Celebrity Fake | CFake.com
  • Meta Keyword
    fake, nude, naked, celebs, celebrity, bundy, mwc, sex, adult, xxx, porn, fuck, hardcore, erotic, pic, image, thumbnail, female, woman, women, christina, applegate, katey, sagal, amanda, bearse, kelly, peggy, marcy, famous, star, free, fun, married, story
  • Meta Description
    See Celebrity Fakes the way you always wanted to see them! Free fun fake celebrity site! Updates often with new nude celebrity pics. For adults only!

Technical Analysis

  • Webserver
    Apache/2.2.16 (Ubuntu)
  • Ip Address
    64.237.54.187
  • Domain Age
    6 Years, 2 Months, 1 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Tue, 25 Jun 2013 21:31:27 GMT
  • server: Apache/2.2.16 (Ubuntu)
  • x-powered-by: PHP/5.3.3-1ubuntu9.6
  • content-encoding: gzip
  • vary: Accept-Encoding
  • content-length: 2343
  • content-type: text/html; charset=utf-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: CFAKE.COM

Registrant:
PrivacyProtect.org
Domain Admin ( email )
ID#10760, PO Box 16
Note - All Postal Mails Rejected, visit Privacyprotect.org
Nobby Beach
null,QLD 4218
AU
Tel. +45.36946676

Creation Date: 27-Apr-2007
Expiration Date: 27-Apr-2013

Domain servers in listed order:
ns5.bzctoons.net
ns6.bzctoons.net
ns7.bzctoons.net
ns8.bzctoons.net


Administrative Contact:
PrivacyProtect.org
Domain Admin ( email )
ID#10760, PO Box 16
Note - All Postal Mails Rejected, visit Privacyprotect.org
Nobby Beach
null,QLD 4218
AU
Tel. +45.36946676

Technical Contact:
PrivacyProtect.org
Domain Admin ( email )
ID#10760, PO Box 16
Note - All Postal Mails Rejected, visit Privacyprotect.org
Nobby Beach
null,QLD 4218
AU
Tel. +45.36946676

Billing Contact:
PrivacyProtect.org
Domain Admin ( email )
ID#10760, PO Box 16
Note - All Postal Mails Rejected, visit Privacyprotect.org
Nobby Beach
null,QLD 4218
AU
Tel. +45.36946676

Status:LOCKED

DNS Analysis


DNS servers
ns5.bzctoons.net
ns6.bzctoons.net
ns7.bzctoons.net
ns8.bzctoons.net


DNS Records

Answer records
cfake.com MX
preference: 20
exchange: alt2.aspmx.l.google.com
28800s
cfake.com MX
preference: 30
exchange: aspmx4.googlemail.com
28800s
cfake.com NS  ns8.bzctoons.net 38400s
cfake.com NS  ns6.bzctoons.net 38400s
cfake.com MX
preference: 30
exchange: aspmx3.googlemail.com
28800s
cfake.com NS  ns5.bzctoons.net 38400s
cfake.com A 64.237.54.187 28800s
cfake.com MX
preference: 30
exchange: aspmx2.googlemail.com
28800s
cfake.com SOA
server: ns8.bzctoons.net
email: eratox@gmail.com
serial: 2011021002
refresh: 7200
retry: 7200
expire: 172800
minimum ttl: 7200
38400s
cfake.com MX
preference: 20
exchange: alt1.aspmx.l.google.com
28800s
cfake.com MX
preference: 30
exchange: aspmx5.googlemail.com
28800s
cfake.com MX
preference: 10
exchange: aspmx.l.google.com
28800s
cfake.com NS  ns7.bzctoons.net 38400s

Authority records

Additional records

IP 64.237.54.187 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Sayreville
  • Continent Code
    08872
  • Latitude
    732
  • Longitude
    501
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 64.237.54.187"
    #
    # Use "?" to get help.
    #

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

    Choopa LLC NET-64-237-54-184-29 (NET-64-237-54-184-1) 64.237.54.184 - 64.237.54.191
    Choopa, LLC CHOOPA-NETBLK01 (NET-64-237-32-0-1) 64.237.32.0 - 64.237.63.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
  • 12 Errors
  • 5 Warnings
Ratio Text/Html
  • 0.4821259693588046
Message Error
  • Error Line 1, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
    <html>

    The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.

  • Error Line 4, Column 22: value of attribute "NAME" must be a single token
    <meta name="voluntary content rating" content="adult">

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Warning Line 8, Column 93: NET-enabling start-tag requires SHORTTAG YES
    …gle-site-verification" content="Quu5wM4qofNeZ9uGJCE1fEeonSEh2EFBj74RRKFPdzg" />

    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 9, Column 57: document type does not allow element "META" here
    <meta http-equiv="Content-Style-Type" content="text/css">

    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 10, Column 54: NET-enabling start-tag requires SHORTTAG YES
    <link rel="icon" type="image/ico" href="favicon.ico" />

    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 10, Column 54: document type does not allow element "LINK" here
    <link rel="icon" type="image/ico" href="favicon.ico" />

    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 12, Column 23: document type does not allow element "STYLE" here
    <style type="text/css">

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

  • Error Line 27, Column 54: document type does not allow element "BODY" here
    <body  text="#999999" alink="#999999" vlink="#CCCCCC">

    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 37, Column 62: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <table border="0" cellspacing="2" cellpadding="0" width="450">

    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 38, Column 85: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …d><font face="arial,helvetica" size="1"  color="#666666"><b><p align="justify">

    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 50, Column 62: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <table border="0" cellspacing="2" cellpadding="0" width="450">

    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 83, Column 13: end tag for "SPAN" omitted, but its declaration does not permit this
            </td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 80, Column 23: start tag was here
            </font></span><span class="Style2"><font size="4" face="arial,helvetica…

Visitor Analysis

Daily Visitor
  • 6.883 visits
Daily Visitor