01 9 Taxi 02 HQ XNXX 03 Sex Tube 04 Twilight Sex 05 Private XXX Tube 06 Free Sex Videos 07 New Xhamster 08 HQ XNXX 09 Tube 2012 10 Live Homemade 11 ...

hq-sex-tube.com
  • Domain Name
    hq-sex-tube.com
  • Favicon
  • Google Page Rank
    0
  • Alexa Rank
    #3593
  • Page Size
    92.4 KB
  • Ip Address
    88.208.53.232
  • Heading
    H1: 0, H2: 0, H3: 2, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 266 JPG, 0 PNG

Website Meta Analysis

  • Title
    HQ Sex Tube - Free Porn Movies
  • Meta Keyword
  • Meta Description
    01 9 Taxi 02 HQ XNXX 03 Sex Tube 04 Twilight Sex 05 Private XXX Tube 06 Free Sex Videos 07 New Xhamster 08 HQ XNXX 09 Tube 2012 10 Live Homemade 11 Tube X Videos 12 Hot Sex Tube 13 Fuck Tube Club 14 Admiral Tube Porn 15 Sex Rulez 16 8 Jet 17 ...

Technical Analysis

  • Webserver
    nginx/1.2.6
  • Ip Address
    88.208.53.232
  • Domain Age
    8 Months, 4 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from hq-sex-tube.com.

HTML Analysis

  • server: nginx/1.2.6
  • date: Mon, 30 Sep 2013 02:45:06 GMT
  • content-type: text/html
  • connection: keep-alive
  • x-powered-by: PHP/5.2.17
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-length: 12437
  • age: 2
  • x-google-cache-control: remote-cache-hit
  • via: HTTP/1.1 GWA (remote cache hit)

Domain Name: HQ-SEX-TUBE.COM

Abuse email: email

Registrant:
WhoisProtectService.net PROTECTSERVICE, LTD. email
27 Old Gloucester Street
London WC1N 3AX
United Kingdom
+44.02074195061

Registered Through:
AHnames.com http://www.AHnames.com/

Administrative Contact:
WhoisProtectService.net PROTECTSERVICE, LTD. email
27 Old Gloucester Street
London WC1N 3AX
United Kingdom
+44.02074195061

Technical Contact:
WhoisProtectService.net PROTECTSERVICE, LTD. email
27 Old Gloucester Street
London WC1N 3AX
United Kingdom
+44.02074195061

Billing Contact:
WhoisProtectService.net PROTECTSERVICE, LTD. email
27 Old Gloucester Street
London WC1N 3AX
United Kingdom
+44.02074195061

Name Server: NS1.PUB-NS.COM
Name Server: NS2.PUB-NS.COM

DNS Analysis


DNS servers
ns1.pub-ns.com [88.208.58.216]
ns2.pub-ns.com [209.8.161.83]


DNS Records

Answer records
hq-sex-tube.com SOA
server: ns1.pub-ns.com
email: admin@hq-sex-tube.com
serial: 1359457839
refresh: 21600
retry: 3600
expire: 691200
minimum ttl: 38400
1200s
hq-sex-tube.com NS  ns1.pub-ns.com 1200s
hq-sex-tube.com NS  ns2.pub-ns.com 1200s
hq-sex-tube.com MX
preference: 10
exchange: mail.hq-sex-tube.com
1200s
hq-sex-tube.com MX
preference: 20
exchange: mail2.hq-sex-tube.com
1200s
hq-sex-tube.com A 88.208.53.232 1200s

Authority records

Additional records
ns1.pub-ns.com A 88.208.58.216 1200s
ns2.pub-ns.com A 209.8.161.83 1200s
mail.hq-sex-tube.com A 206.161.193.141 1200s
mail2.hq-sex-tube.com A 205.252.166.180 1200s

IP 88.208.53.232 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 85 Errors
  • 18 Warnings
Ratio Text/Html
  • 0.8349085527011312
Message Error
  • Warning Line 6, Column 99: NET-enabling start-tag requires SHORTTAG YES
    …" type="text/css" href="http://world.2970882.pix-cdn.org/img_hst/styles.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.

  • Error Line 40, 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 41, 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 45, Column 104: required attribute "ALT" not specified
    …g src="http://world.2970882.pix-cdn.org/img_hst/logo.jpg" border="0"></a></div>

    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 141: there is no attribute "AUTOCOMPLETE"
    …alue='Search any porn';" autocomplete="off" onFocus="if(this.value=='Search an…

    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.

  • Warning Line 1765, Column 89: cannot generate system identifier for general entity "login"
    …tion.exoclick.com/ads.php?type=728x90&login=world&cat=97&search=&ad_title_colo…

    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.

Visitor Analysis

Daily Visitor
  • 36.167 visits