One of the most completed lists with tube sex videos, enjoy full lenght porno tube videos where people are fucking all day long from sites like Xhamster, Hardsextube, Shufuni, Tube8. ...

videosbang.com
  • Domain Name
    videosbang.com
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #24072
  • Page Size
    354.4 KB
  • Ip Address
    213.174.155.135
  • Heading
    H1: 2, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 189 JPG, 0 PNG

Website Meta Analysis

  • Title
    Tube Sex Videos, Porno Tube Vids, Xhamster, Hardsextube, Tube8, Shufuni at VideosBang.com - page 1
  • Meta Keyword
    flash porn, flash stream, tube porn, streaming porn, hardcore, tube movies
  • Meta Description
    One of the most completed lists with tube sex videos, enjoy full lenght porno tube videos where people are fucking all day long from sites like Xhamster, Hardsextube, Shufuni, Tube8.

Technical Analysis

  • Webserver
    nginx/1.2.7
  • Ip Address
    213.174.155.135
  • Domain Age
    6 Years, 9 Months, 1 days.
  • Javascript Library
    yui
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx/1.2.7
  • date: Wed, 07 Aug 2013 03:18:23 GMT
  • content-type: text/html
  • connection: keep-alive
  • x-powered-by: PHP/5.2.17
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

Domain Name: VIDEOSBANG.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: NS5.PUBLIC-NS.COM
Name Server: NS6.PUBLIC-NS.COM

DNS Analysis


DNS servers
ns5.public-ns.com [207.226.173.74]
ns6.public-ns.com [88.208.58.214]


DNS Records

Answer records
videosbang.com SOA
server: ns5.public-ns.com
email: admin@videosbang.com
serial: 1339245893
refresh: 21600
retry: 3600
expire: 691200
minimum ttl: 38400
1200s
videosbang.com NS  ns5.public-ns.com 1200s
videosbang.com NS  ns6.public-ns.com 1200s
videosbang.com MX
preference: 10
exchange: mail.videosbang.com
1200s
videosbang.com MX
preference: 20
exchange: mail2.videosbang.com
1200s
videosbang.com A 46.229.160.120 1200s

Authority records

Additional records
ns5.public-ns.com A 207.226.173.74 1200s
ns6.public-ns.com A 88.208.58.214 1200s
mail.videosbang.com A 206.161.193.141 1200s
mail2.videosbang.com A 205.252.166.180 1200s

IP 213.174.155.135 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    NA
  • Continent Code
    38° North
  • Latitude
    97.
  • Longitude
  • No whois ip data for 213.174.155.135

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 10 Errors
  • 12 Warnings
Ratio Text/Html
  • 0.7724728622568351
Message Error
  • Warning Line 315, Column 86: cannot generate system identifier for general entity "idsite"
    …ication.exoclick.com/splash.php?cat=2&idsite=72262&idzone=297474&login=btnetwo…

    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 "&" (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 æ 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 315, Column 86: general entity "idsite" not defined and no default entity
    …ication.exoclick.com/splash.php?cat=2&idsite=72262&idzone=297474&login=btnetwo…

    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 315, Column 92: reference not terminated by REFC delimiter
    …n.exoclick.com/splash.php?cat=2&idsite=72262&idzone=297474&login=btnetwork&typ…

    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 315, Column 92: reference to external entity in attribute value
    …n.exoclick.com/splash.php?cat=2&idsite=72262&idzone=297474&login=btnetwork&typ…

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

  • Error Line 315, Column 92: reference to entity "idsite" for which no system identifier could be generated
    …n.exoclick.com/splash.php?cat=2&idsite=72262&idzone=297474&login=btnetwork&typ…

    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 315, Column 85: entity was defined here
    …dication.exoclick.com/splash.php?cat=2&idsite=72262&idzone=297474&login=btnetw…
  • Warning Line 315, Column 99: cannot generate system identifier for general entity "idzone"
    …ick.com/splash.php?cat=2&idsite=72262&idzone=297474&login=btnetwork&type=3"></…

    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 315, Column 99: general entity "idzone" not defined and no default entity
    …ick.com/splash.php?cat=2&idsite=72262&idzone=297474&login=btnetwork&type=3"></…

    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 315, Column 105: reference not terminated by REFC delimiter
    …m/splash.php?cat=2&idsite=72262&idzone=297474&login=btnetwork&type=3"></script…

    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 315, Column 105: reference to external entity in attribute value
    …m/splash.php?cat=2&idsite=72262&idzone=297474&login=btnetwork&type=3"></script…

    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 315, Column 105: reference to entity "idzone" for which no system identifier could be generated
    …m/splash.php?cat=2&idsite=72262&idzone=297474&login=btnetwork&type=3"></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 315, Column 98: entity was defined here
    …lick.com/splash.php?cat=2&idsite=72262&idzone=297474&login=btnetwork&type=3"><…
  • Warning Line 315, Column 113: cannot generate system identifier for general entity "login"
    …m/splash.php?cat=2&idsite=72262&idzone=297474&login=btnetwork&type=3"></script>

    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 315, Column 113: general entity "login" not defined and no default entity
    …m/splash.php?cat=2&idsite=72262&idzone=297474&login=btnetwork&type=3"></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.

  • Warning Line 315, Column 118: reference not terminated by REFC delimiter
    …m/splash.php?cat=2&idsite=72262&idzone=297474&login=btnetwork&type=3"></script>

    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 315, Column 118: reference to external entity in attribute value
    …m/splash.php?cat=2&idsite=72262&idzone=297474&login=btnetwork&type=3"></script>

    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 315, Column 118: reference to entity "login" for which no system identifier could be generated
    …m/splash.php?cat=2&idsite=72262&idzone=297474&login=btnetwork&type=3"></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 315, Column 112: entity was defined here
    …m/splash.php?cat=2&idsite=72262&idzone=297474&login=btnetwork&type=3"></script>
  • Warning Line 315, Column 129: cannot generate system identifier for general entity "type"
    …m/splash.php?cat=2&idsite=72262&idzone=297474&login=btnetwork&type=3"></script>

    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 315, Column 129: general entity "type" not defined and no default entity
    …m/splash.php?cat=2&idsite=72262&idzone=297474&login=btnetwork&type=3"></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.

  • Warning Line 315, Column 133: reference not terminated by REFC delimiter
    …m/splash.php?cat=2&idsite=72262&idzone=297474&login=btnetwork&type=3"></script>

    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 315, Column 133: reference to external entity in attribute value
    …m/splash.php?cat=2&idsite=72262&idzone=297474&login=btnetwork&type=3"></script>

    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 315, Column 133: reference to entity "type" for which no system identifier could be generated
    …m/splash.php?cat=2&idsite=72262&idzone=297474&login=btnetwork&type=3"></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 315, Column 128: entity was defined here
    …m/splash.php?cat=2&idsite=72262&idzone=297474&login=btnetwork&type=3"></script>
  • Error Line 316, Column 18: there is no attribute "Language"
    <script Language="JavaScript">

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

Visitor Analysis

Daily Visitor
  • 2.683 visits