rar,zip,7z,tar,tgz,ace,jar,swf,3gp,sis ...

btbbt.biz
  • Domain Name
    btbbt.biz
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #33060
  • Page Size
    7.6 KB
  • Ip Address
    76.73.50.35
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    2 GIF, 0 JPG, 1 PNG

Website Meta Analysis

  • Title
    BTBBT.BIZ File - Free Files Hosting
  • Meta Keyword
    free,upload,zip.rar,file,exe,upload file,free download file,asp hosting,dedicated servers,domains name,dual xeon series,free file hosting,free hosting,ftp hosting,images hosting,jsp hosting,php hosting,server co-location,unmetered servers,virtual private servers,windows 2000 server,windows 2003 server,zip,rar,7z tar,tgz,ace,jar,swf,3gp,sis,mobilephone,nokia,motorola,ringtone,sonyericsson,samsung,siemens,nec
  • Meta Description
    rar,zip,7z,tar,tgz,ace,jar,swf,3gp,sis

Technical Analysis

  • Webserver
    nginx/0.8.54
  • Ip Address
    76.73.50.35
  • Domain Age
    7 Years, 5 Months, 19 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from btbbt.biz.

HTML Analysis

  • server: nginx/0.8.54
  • date: Sat, 02 Mar 2013 05:03:02 GMT
  • content-type: text/html
  • connection: keep-alive
  • x-powered-by: PHP/5.2.17
  • vary: Accept-Encoding
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain ID: D10967986-BIZ
Registrar: ENOM, INC.
Sponsoring Registrar IANA ID: 48
Registrar URL (registration services): whois.enom.com
Domain Domain Status: clientTransferProhibited
Registrant ID: DE5D760F8B257E3B
Registrant Domain Name: Hakata honda
Registrant Organization:
Registrant Address1: Japan,Chiba Prefecture,Matsudo,Higure 4-8-,Foramu Hachu,201,
Registrant City: Zheng Su
Registrant State/Province: P
Registrant Postal Code: 999001
Registrant Country: Japan
Registrant Country Code: JP
Registrant Phone Number: +1.4156653417
Registrant Email: email
Administrative Contact ID: DE5D760F8B257E3B
Administrative Contact Domain Name: Hakata honda
Administrative Contact Organization:
Administrative Contact Address1: Japan,Chiba Prefecture,Matsudo,Higure 4-8-,Foramu Hachu,201,
Administrative Contact City: Zheng Su
Administrative Contact State/Province: P
Administrative Contact Postal Code: 999001
Administrative Contact Country: Japan
Administrative Contact Country Code: JP
Administrative Contact Phone Number: +1.4156653417
Administrative Contact Email: email
Billing Contact ID: DE5D760F8B257E3B
Billing Contact Domain Name: Hakata honda
Billing Contact Organization:
Billing Contact Address1: Japan,Chiba Prefecture,Matsudo,Higure 4-8-,Foramu Hachu,201,
Billing Contact City: Zheng Su
Billing Contact State/Province: P
Billing Contact Postal Code: 999001
Billing Contact Country: Japan
Billing Contact Country Code: JP
Billing Contact Phone Number: +1.4156653417
Billing Contact Email: email
Technical Contact ID: DE5D760F8B257E3B
Technical Contact Domain Name: Hakata honda
Technical Contact Organization:
Technical Contact Address1: Japan,Chiba Prefecture,Matsudo,Higure 4-8-,Foramu Hachu,201,
Technical Contact City: Zheng Su
Technical Contact State/Province: P
Technical Contact Postal Code: 999001
Technical Contact Country: Japan
Technical Contact Country Code: JP
Technical Contact Phone Number: +1.4156653417
Technical Contact Email: email
Name Servers: DNS5.NAME-SERVICES.COM
Name Servers: DNS4.NAME-SERVICES.COM
Name Servers: DNS3.NAME-SERVICES.COM
Name Servers: DNS2.NAME-SERVICES.COM
Name Servers: DNS1.NAME-SERVICES.COM
Created by Registrar: ENOM, INC.
Last Updated by Registrar: ENOM, INC.
Created: Tue Sep 20 00:04:54 GMT 2005
Expires: Wed Sep 19 23:59:59 GMT 2012
Updated: Thu Sep 22 12:05:48 GMT 2011

IP 76.73.50.35 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Chicago
  • Continent Code
    60604
  • Latitude
    312
  • Longitude
    602
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 76.73.50.35"
    #
    # Use "?" to get help.
    #

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

    FDCservers.net FDCSERVERS (NET-76-73-0-0-1) 76.73.0.0 - 76.73.127.255
    FDCservers.net FDCSERVERS-DENVER (NET-76-73-0-0-2) 76.73.0.0 - 76.73.127.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
  • 27 Errors
  • 7 Warnings
Ratio Text/Html
  • 0.7394266615246176
Message Error
  • Error Line 2, 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.

  • Warning Line 12, Column 90: NET-enabling start-tag requires SHORTTAG YES
    …tylesheet" title="User Defined Style" href="image/style.css" type="text/css" />

    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.

  • Warning Line 13, Column 66: NET-enabling start-tag requires SHORTTAG YES
    <link rel="shortcut icon" href="favicon.ico" type="image/x-icon" /></head>

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

    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 13, Column 74: end tag for element "HEAD" which is not open
    <link rel="shortcut icon" href="favicon.ico" type="image/x-icon" /></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 14, Column 56: required attribute "TYPE" not specified
    <script language="JavaScript" src="image/hidestatus.js"></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 16, Column 52: required attribute "TYPE" not specified
    <script language="JavaScript" src="image/submit.js"></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 17, 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 18, Column 6: document type does not allow element "BODY" here
    <body>

    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 22, Column 119: required attribute "ALT" not specified
    …it your file here to share with your friend!" width="183" height="93"></a></td>

    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 23, Column 28: there is no attribute "BACKGROUND"
    <td width="555" background="image/hbg.png" align="center" height="93">

    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 24, Column 59: there is no attribute "HEIGHT"
    <table cellpadding="0" cellspacing="0" width="555" height="93">

    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 27, Column 130: required attribute "ALT" not specified
    …img border="0" src="/extra/diyicon_extra.gif" width="520" height="41"></a></td>

    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 55, Column 57: required attribute "TYPE" not specified
    <SCRIPT SRC="image/ads_top_728.js" LANGUAGE="JavaScript"></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 66, Column 66: required attribute "TYPE" not specified
    <SCRIPT SRC="image/ads_adengage_300x250.js" LANGUAGE="JavaScript"></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 70, Column 54: required attribute "TYPE" not specified
    <SCRIPT SRC="image/adengage.js" LANGUAGE="JavaScript"></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 75, Column 89: an attribute value must be a literal unless it contains only name characters
    …e hosting service. Read the <a target=\"_blank\" href="/content.php?link-rules…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 83, Column 30: 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 88, Column 144: required attribute "ALT" not specified
    … href="http://www.ioifunny.com/"><img border="0" src="/image/hed_logo.gif"></a>

    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 94, Column 103: an attribute value must be a literal unless it contains only name characters
    …'submit' value=' Host it ' name='Submit' id="submitbtn" onclick=showDiv()></td>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 102, Column 30: 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 110, Column 64: required attribute "TYPE" not specified
    …nter><script language="JavaScript" src="image/banner_ads.js"></script></center>

    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 115, Column 12: an attribute value must be a literal unless it contains only name characters
    	<a target=\"_self\" href="content.php?link-rules.html">Copyright</a> &copy; 20…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 117, Column 12: an attribute value must be a literal unless it contains only name characters
    	<a target=\"_self\" href="/content.php?link-linksto.html">Link to Btbbt.Biz</a>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Warning Line 125, Column 54: cannot generate system identifier for general entity "web_id"
    …tp://s22.cnzz.com/stat.php?id=3105293&web_id=3105293" language="JavaScript"></…

    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 125, Column 54: general entity "web_id" not defined and no default entity
    …tp://s22.cnzz.com/stat.php?id=3105293&web_id=3105293" language="JavaScript"></…

    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 125, Column 60: reference to entity "web_id" for which no system identifier could be generated
    …22.cnzz.com/stat.php?id=3105293&web_id=3105293" language="JavaScript"></script…

    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 125, Column 53: entity was defined here
    …ttp://s22.cnzz.com/stat.php?id=3105293&web_id=3105293" language="JavaScript"><…
  • Error Line 125, Column 91: required attribute "TYPE" not specified
    …22.cnzz.com/stat.php?id=3105293&web_id=3105293" language="JavaScript"></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 126, Column 110: document type does not allow element "NOSCRIPT" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …rs.51.la/993853.js"></script><noscript><a href="http://www.51.la/?993853" targ…

    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>").

  • Warning Line 126, Column 227: NET-enabling start-tag requires SHORTTAG YES
    …g src="http://img.users.51.la/993853.asp" style="border:none" /></a></noscript>

    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 126, Column 227: required attribute "ALT" not specified
    …g src="http://img.users.51.la/993853.asp" style="border:none" /></a></noscript>

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

Visitor Analysis

Daily Visitor
  • 4.550 visits
Daily Visitor