pinktube.com

pinktube.com has Alexa Rank 24.547 and Google Page Rank is 2

Display Widget for this domain on your website. Click Here
This data was last updated from 30-07-2013 02:46:47  (update).

Overview Info

  • Domain Name
    pinktube.com
  • Favicon
  • Alexa Rank
    #24547
  • Google Page Rank
    PR 2
  • Ip Address
    64.188.48.195
  • Page Size
    70.2 KB
  • Images
    1 GIF, 55 JPG, 1 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 1 0 0 0 0

Technical Analysis



  • Webserver
    nginx
  • Ip Address
    64.188.48.195
  • Domain Age
    7 Years, 0 Months, 10 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx
  • date: Tue, 30 Jul 2013 14:46:42 GMT
  • content-type: text/html; charset=utf-8
  • connection: keep-alive
  • vary: Accept-Encoding
  • expires: Mon, 26 Jul 1997 05:00:00 GMT
  • last-modified: Tue, 30 Jul 2013 14:46:42 GMT
  • cache-control: no-store, no-cache, must-revalidate
  • pragma: no-cache
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: PINKTUBE.COM
Registrar: MONIKER

Registrant [2589955]:
Program Three LLC. email
Program Three LLC.
6955 NW 52 St.
Miami
FLORIDA
33166
US


Administrative Contact [2589955]:
Program Three LLC. email
Program Three LLC.
6955 NW 52 St.
Miami
FLORIDA
33166
US
Phone: +1.3056952500
Fax: +1.3056952524


Billing Contact [2589955]:
Program Three LLC. email
Program Three LLC.
6955 NW 52 St.
Miami
FLORIDA
33166
US
Phone: +1.3056952500
Fax: +1.3056952524


Technical Contact [2589955]:
Program Three LLC. email
Program Three LLC.
6955 NW 52 St.
Miami
FLORIDA
33166
US
Phone: +1.3056952500
Fax: +1.3056952524


Domain servers in listed order:

NS2.ISPRIME.COM
NS.ISPRIME.COM

Record created on: 2006-07-27 09:43:13.0
Database last updated on: 2011-06-30 16:57:51.457
Domain Expires on: 2020-07-27 09:43:13.0

DNS Analysis


DNS servers
ns.isprime.com [76.9.7.3]
ns2.isprime.com [66.230.160.1]

DNS Records

Answer records
pinktube.com SOA
server: ns.isprime.com
email: support@isprime.com
serial: 1284046475
refresh: 16384
retry: 2048
expire: 1048576
minimum ttl: 2560
2560s
pinktube.com MX
preference: 10
exchange: mail.pinktube.com
60s
pinktube.com NS  ns2.isprime.com 172800s
pinktube.com NS  ns.isprime.com 172800s
pinktube.com A 64.188.48.195 900s

Authority records

Additional records
mail.pinktube.com A 64.111.221.30 900s
ns2.isprime.com A 66.230.160.1 172800s
ns.isprime.com A 76.9.7.3 172800s

IP 64.188.48.195 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Weehawken
  • Continent Code
    07086
  • Latitude
    201
  • Longitude
    501
  • No whois ip data for 64.188.48.195

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 17 Errors
  • 18 Warnings
Ratio Text/Html
  • 0.842146265459149
Message Error
  • Error Line 50, Column 103: required attribute "alt" not specified
    …bemedia.com/siteimages/site/logo.png"/></a>                    <h1>Pinktube th…

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

  • Warning Line 94, Column 86: cannot generate system identifier for general entity "a"
    …naked.com/popular/?domain=camster.com&a=pinktube&cmp=playertablink" target="_n…

    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 94, Column 86: general entity "a" not defined and no default entity
    …naked.com/popular/?domain=camster.com&a=pinktube&cmp=playertablink" target="_n…

    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.

  • Warning Line 94, Column 87: reference not terminated by REFC delimiter
    …aked.com/popular/?domain=camster.com&a=pinktube&cmp=playertablink" target="_ne…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 94, Column 87: reference to external entity in attribute value
    …aked.com/popular/?domain=camster.com&a=pinktube&cmp=playertablink" target="_ne…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 94, Column 87: reference to entity "a" for which no system identifier could be generated
    …aked.com/popular/?domain=camster.com&a=pinktube&cmp=playertablink" target="_ne…

    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 94, Column 85: entity was defined here
    ….naked.com/popular/?domain=camster.com&a=pinktube&cmp=playertablink" target="_…
  • Warning Line 94, Column 97: cannot generate system identifier for general entity "cmp"
    …opular/?domain=camster.com&a=pinktube&cmp=playertablink" target="_new" rel="no…

    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 94, Column 97: general entity "cmp" not defined and no default entity
    …opular/?domain=camster.com&a=pinktube&cmp=playertablink" target="_new" rel="no…

    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.

  • Warning Line 94, Column 100: reference not terminated by REFC delimiter
    …lar/?domain=camster.com&a=pinktube&cmp=playertablink" target="_new" rel="nofol…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 94, Column 100: reference to external entity in attribute value
    …lar/?domain=camster.com&a=pinktube&cmp=playertablink" target="_new" rel="nofol…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 94, Column 100: reference to entity "cmp" for which no system identifier could be generated
    …lar/?domain=camster.com&a=pinktube&cmp=playertablink" target="_new" rel="nofol…

    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 94, Column 96: entity was defined here
    …popular/?domain=camster.com&a=pinktube&cmp=playertablink" target="_new" rel="n…
  • Warning Line 745, Column 77: cannot generate system identifier for general entity "utm_campaign"
    …//www.adbucks.com?utm_source=pinktube&utm_campaign=ftr_ad&utm_medium=txt_ad" t…

    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 745, Column 77: general entity "utm_campaign" not defined and no default entity
    …//www.adbucks.com?utm_source=pinktube&utm_campaign=ftr_ad&utm_medium=txt_ad" t…

    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.

  • Warning Line 745, Column 89: reference not terminated by REFC delimiter
    …s.com?utm_source=pinktube&utm_campaign=ftr_ad&utm_medium=txt_ad" target="_new"…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 745, Column 89: reference to external entity in attribute value
    …s.com?utm_source=pinktube&utm_campaign=ftr_ad&utm_medium=txt_ad" target="_new"…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 745, Column 89: reference to entity "utm_campaign" for which no system identifier could be generated
    …s.com?utm_source=pinktube&utm_campaign=ftr_ad&utm_medium=txt_ad" target="_new"…

    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 745, Column 76: entity was defined here
    …://www.adbucks.com?utm_source=pinktube&utm_campaign=ftr_ad&utm_medium=txt_ad" …
  • Warning Line 745, Column 97: cannot generate system identifier for general entity "utm_medium"
    …m_source=pinktube&utm_campaign=ftr_ad&utm_medium=txt_ad" target="_new" rel="no…

    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 745, Column 97: general entity "utm_medium" not defined and no default entity
    …m_source=pinktube&utm_campaign=ftr_ad&utm_medium=txt_ad" target="_new" rel="no…

    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.

  • Warning Line 745, Column 107: reference not terminated by REFC delimiter
    …inktube&utm_campaign=ftr_ad&utm_medium=txt_ad" target="_new" rel="nofollow">AD…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 745, Column 107: reference to external entity in attribute value
    …inktube&utm_campaign=ftr_ad&utm_medium=txt_ad" target="_new" rel="nofollow">AD…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 745, Column 107: reference to entity "utm_medium" for which no system identifier could be generated
    …inktube&utm_campaign=ftr_ad&utm_medium=txt_ad" target="_new" rel="nofollow">AD…

    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 745, Column 96: entity was defined here
    …tm_source=pinktube&utm_campaign=ftr_ad&utm_medium=txt_ad" target="_new" rel="n…
  • Error Line 755, Column 22: required attribute "type" not specified
    </div>        <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>.

  • Warning Line 757, Column 56: cannot generate system identifier for general entity "s"
                var redirectUrl = '/index.php?widget=false&s='+componentPath;

    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 757, Column 56: general entity "s" not defined and no default entity
                var redirectUrl = '/index.php?widget=false&s='+componentPath;

    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.

  • Warning Line 757, Column 57: reference not terminated by REFC delimiter
                var redirectUrl = '/index.php?widget=false&s='+componentPath;

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Error Line 757, Column 57: reference to entity "s" for which no system identifier could be generated
                var redirectUrl = '/index.php?widget=false&s='+componentPath;

    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 757, Column 55: entity was defined here
                var redirectUrl = '/index.php?widget=false&s='+componentPath;
  • Warning Line 822, Column 51: cannot generate system identifier for general entity "q"
                loadModule('container','search.search&q='+jQuery('#search').val());

    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 822, Column 51: general entity "q" not defined and no default entity
                loadModule('container','search.search&q='+jQuery('#search').val());

    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.

  • Warning Line 822, Column 52: reference not terminated by REFC delimiter
                loadModule('container','search.search&q='+jQuery('#search').val());

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Error Line 822, Column 52: reference to entity "q" for which no system identifier could be generated
                loadModule('container','search.search&q='+jQuery('#search').val());

    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 822, Column 50: entity was defined here
                loadModule('container','search.search&q='+jQuery('#search').val());

Visitor Analysis

Daily Visitor
  • 2.567 visits

In Page Analysis