free proxy proxite.net anonymously free browsing proxy on fast network. ...

proxite.net
  • Domain Name
    proxite.net
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #42419
  • Page Size
    24.5 KB
  • Ip Address
    173.224.125.91
  • Heading
    H1: 1, H2: 2, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    1 GIF, 0 JPG, 1 PNG

Website Meta Analysis

  • Title
    proxite.net :: free anonymous proxy, uncensored free web browsing. Fast free web proxy, 110 Gbit Network.
  • Meta Keyword
    free proxy, free, proxy, web proxy, free vpn, vpn, bypass fast proxy
  • Meta Description
    free proxy proxite.net anonymously free browsing proxy on fast network.

Technical Analysis

  • Webserver
    Microsoft-IIS/7.0
  • Ip Address
    173.224.125.91
  • Domain Age
    4 Years, 1 Months, 19 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • cache-control: no-store, no-cache, must-revalidate,post-check=0, pre-check=0
  • pragma: no-cache
  • content-length: 24993
  • content-type: text/html
  • last-modified: Sun, 12 Dec 2010 17:34:33 GMT
  • server: Microsoft-IIS/7.0
  • x-powered-by: PHP/5.2.6
  • x-ua-compatible: IE=EmulateIE7
  • date: Tue, 17 Sep 2013 13:48:06 GMT
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Cakinberk Telekominikasyon ve Internet Servis Himetleri Ltd. Sti.

Domain Name: PROXITE.NET

Name Servers:
NS1.NAMESERVERSERVICE.COM
USPRO682B.NOIP.ME

For complete domain details go to:
http://who.godaddy.com/whoischeck.aspx?Domain=PROXITE.NET

DNS Analysis


DNS servers
ns1.nameserverservice.com
ns2.nameserverservice.com


DNS Records

Answer records
proxite.net NS  ns1.nameserverservice.com 86400s
proxite.net NS  ns2.nameserverservice.com 86400s
proxite.net MX
preference: 100
exchange: mail.proxite.net
86400s
proxite.net SOA
server: ns1.nameserverservice.com
email: hostmaster@ns1.nameserverservice.com
serial: 2011021001
refresh: 40000
retry: 20000
expire: 1500000
minimum ttl: 86400
2560s
proxite.net A 173.224.125.91 86400s

Authority records

Additional records
ns1.nameserverservice.com A 69.64.45.121 86400s
ns2.nameserverservice.com A 69.64.44.21 86400s
mail.proxite.net A 173.224.125.91 86400s

IP 173.224.125.91 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Saint Louis
  • Continent Code
    63101
  • Latitude
    314
  • Longitude
    609
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 173.224.125.91"
    #
    # Use "?" to get help.
    #

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

    NetRange: 173.224.112.0 - 173.224.127.255
    CIDR: 173.224.112.0/20
    OriginAS: AS30083
    NetName: HSI-3
    NetHandle: NET-173-224-112-0-1
    Parent: NET-173-0-0-0-0
    NetType: Direct Allocation
    RegDate: 2010-01-19
    Updated: 2012-05-10
    Ref: http://whois.arin.net/rest/net/NET-173-224-112-0-1

    OrgName: Hosting Solutions International, Inc.
    OrgId: SERVE-6
    Address: 210 North Tucker Blvd.
    Address: Suite 910
    City: Saint Louis
    StateProv: MO
    PostalCode: 63101
    Country: US
    RegDate: 2003-04-15
    Updated: 2012-05-10
    Comment: Please forward abuse complaints to abuse@hostingsolutionsint.com
    Ref: http://whois.arin.net/rest/org/SERVE-6

    OrgNOCHandle: SWI19-ARIN
    OrgNOCName: Wintz, Sascha
    OrgNOCPhone: +1-314-480-6840
    OrgNOCEmail: s.wintz@hostingsolutionsinternational.com
    OrgNOCRef: http://whois.arin.net/rest/poc/SWI19-ARIN

    OrgTechHandle: SWI19-ARIN
    OrgTechName: Wintz, Sascha
    OrgTechPhone: +1-314-480-6840
    OrgTechEmail: s.wintz@hostingsolutionsinternational.com
    OrgTechRef: http://whois.arin.net/rest/poc/SWI19-ARIN

    OrgAbuseHandle: HAD15-ARIN
    OrgAbuseName: HSI Abuse Department
    OrgAbusePhone: +1-314-266-3638
    OrgAbuseEmail: abuse@hostingsolutionsint.com
    OrgAbuseRef: http://whois.arin.net/rest/poc/HAD15-ARIN

    RTechHandle: SWI19-ARIN
    RTechName: Wintz, Sascha
    RTechPhone: +1-314-480-6840
    RTechEmail: s.wintz@hostingsolutionsinternational.com
    RTechRef: http://whois.arin.net/rest/poc/SWI19-ARIN

    RNOCHandle: SWI19-ARIN
    RNOCName: Wintz, Sascha
    RNOCPhone: +1-314-480-6840
    RNOCEmail: s.wintz@hostingsolutionsinternational.com
    RNOCRef: http://whois.arin.net/rest/poc/SWI19-ARIN

    RAbuseHandle: HAD15-ARIN
    RAbuseName: HSI Abuse Department
    RAbusePhone: +1-314-266-3638
    RAbuseEmail: abuse@hostingsolutionsint.com
    RAbuseRef: http://whois.arin.net/rest/poc/HAD15-ARIN

    #
    # 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
  • 10 Errors
  • 11 Warnings
Ratio Text/Html
  • 0.5450775549264324
Message Error
  • Error Line 7, Column 50: duplicate specification of attribute "CONTENT"
    …"keywords" content="keywords" content="free proxy, free, proxy, web proxy, fre…

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Warning Line 210, Column 312: NET-enabling start-tag requires SHORTTAG YES
    …mp;n=a5d95544&amp;ct0=INSERT_CLICKURL_HERE' border='0' alt='' /></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.

  • Warning Line 256, Column 244: NET-enabling start-tag requires SHORTTAG YES
    …b=INSERT_RANDOM_NUMBER_HERE&amp;n=a5c188ec' border='0' alt='' /></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 264, Column 56: there is no attribute "FB:LIKE:LAYOUT"
    <a class="addthis_button_facebook_like" fb:like:layout="button_count"></a>

    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 297, Column 157: end tag for element "SPAN" which is not open
    …t="_blank">256Bit SSL Connection :: Click Here for High Secure Proxy</a></span>

    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.

  • Warning Line 299, Column 164: NET-enabling start-tag requires SHORTTAG YES
    …zvzMKD18zSNvVIeHkQnEeCvx"></script><br/><a style="font-family: arial; font-siz…

    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 323, Column 108: end tag for element "A" which is not open
    …y Web Deppo :: 110 Gbit Network :: </a> v1.1 :: <a href="privacy.php">Privacy<…

    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.

  • Warning Line 328, Column 227: NET-enabling start-tag requires SHORTTAG YES
    …time for 110 Gbit Network Status: Last 30 days" width="210" height="120" /></a>

    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 330, Column 241: NET-enabling start-tag requires SHORTTAG YES
    …time for 110 Gbit Network Status: Last 30 days" width="210" height="120" /></a>

    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 332, Column 189: NET-enabling start-tag requires SHORTTAG YES
    ….png" alt="Network Management Software" width="80" height="65" border="0"/></a>

    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 335, Column 6: end tag for element "DIV" which is not open
    </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 346, Column 9: an attribute value must be a literal unless it contains only name characters
    <a href=\"http://www.proxysites.com\"></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.

  • Error Line 347, Column 9: an attribute value must be a literal unless it contains only name characters
    <a href=\"http://www.proxysites.com\" target=\"_blank\"></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.

  • Error Line 347, Column 46: an attribute value must be a literal unless it contains only name characters
    <a href=\"http://www.proxysites.com\" target=\"_blank\"></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 365, Column 3117: NET-enabling start-tag requires SHORTTAG YES
    …s.com">Proxy Sites</a> | <a href=http://proxysites.ca>Proxy Sites</a> | <a hre…

    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 365, Column 3147: end tag for element "A" which is not open
    …ef=http://proxysites.ca>Proxy Sites</a> | <a href="http://www.waytoproxy.com">…

    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.

  • Warning Line 365, Column 4500: NET-enabling start-tag requires SHORTTAG YES
    …nblock.me">unblock</a> | <a href=http://www.juvos.com>Proxy</a> | <a href="htt…

    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 365, Column 4524: end tag for element "A" which is not open
    … <a href=http://www.juvos.com>Proxy</a> | <a href="http://www.intoeasy.com">Pr…

    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.

  • Warning Line 386, Column 136: NET-enabling start-tag requires SHORTTAG YES
    …2.gif" style="display: none;" border="0" height="1" width="1" alt="Quantcast"/>

    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.

Visitor Analysis

Daily Visitor
  • 1.633 visits