indianhiddencams.com

Indian Hidden Cams - Indian voyeur porn and sex scandal of sexy indian babes. Watch Indian couples making love in their bedrooms unaware of hidden cam fixed by their relatives or neighbours ...

Display Widget for this domain on your website. Click Here
This data was last updated from 08-02-2013 12:15:16  (update).

Overview Info

  • Domain Name
    indianhiddencams.com
  • Favicon
  • Alexa Rank
    #32724
  • Google Page Rank
    PR 0
  • Ip Address
    64.6.102.230
  • Page Size
    4.5 KB
  • Images
    0 GIF, 4 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 2 0 0 0 0

Website Meta Analysis

  • Title
    Indian Hidden Cams, Indian Sex Scandals, Indian Homemade Porn
  • Meta Keyword
    indian, hidden, cams, sex, scandal, voyeur, couple, desi, video, movies
  • Meta Description
    Indian Hidden Cams - Indian voyeur porn and sex scandal of sexy indian babes. Watch Indian couples making love in their bedrooms unaware of hidden cam fixed by their relatives or neighbours

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    64.6.102.230
  • Domain Age
    4 Years, 11 Months, 26 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Fri, 08 Feb 2013 00:15:17 GMT
  • server: Apache
  • x-powered-by: PHP/5.2.17
  • content-length: 4681
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: INDIANHIDDENCAMS.COM
Created on: 09-Mar-08
Expires on: 09-Mar-14
Last Updated on: 13-Feb-12

Registrant:
Domains By Proxy, LLC
DomainsByProxy.com
14747 N Northsight Blvd Suite 111, PMB 309
Scottsdale, Arizona 85260
United States

Administrative Contact:
Private, Registration email
Domains By Proxy, LLC
DomainsByProxy.com
14747 N Northsight Blvd Suite 111, PMB 309
Scottsdale, Arizona 85260
United States
(480) 624-2599 Fax -- (480) 624-2598

Technical Contact:
Private, Registration email
Domains By Proxy, LLC
DomainsByProxy.com
14747 N Northsight Blvd Suite 111, PMB 309
Scottsdale, Arizona 85260
United States
(480) 624-2599 Fax -- (480) 624-2598

Domain servers in listed order:
NS1.INDIANHIDDENCAMS.COM
NS2.INDIANHIDDENCAMS.COM

DNS Analysis


DNS servers
ns1.indianhiddencams.com [216.17.96.210]
ns2.indianhiddencams.com [216.17.104.103]


DNS Records

Answer records
indianhiddencams.com SOA
server: ns1.phatservers.com
email: root@indianhiddencams.com
serial: 2011061303
refresh: 400
retry: 3600
expire: 1209600
minimum ttl: 86400
14400s
indianhiddencams.com NS  ns2.phatservers.com 400s
indianhiddencams.com NS  ns1.phatservers.com 400s
indianhiddencams.com A 64.6.102.230 400s
indianhiddencams.com MX
preference: 10
exchange: mail.indianhiddencams.com
400s
indianhiddencams.com TXT v=spf1 ip4:64.6.102.230 ptr:pbpoint.amerinoc.com mx:mail.247mg.com a:pbpoint.amerinoc.com mx:pbpoint.amerinoc.com ~all 14400s

Authority records

Additional records
ns1.phatservers.com A 216.17.96.210 86400s
ns2.phatservers.com A 216.17.104.103 86400s
mail.indianhiddencams.com A 64.6.102.230 400s

IP 64.6.102.230 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    San Diego
  • Continent Code
    92117
  • Latitude
    858
  • Longitude
    825
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 64.6.102.230"
    #
    # Use "?" to get help.
    #

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

    NetRange: 64.6.96.0 - 64.6.111.255
    CIDR: 64.6.96.0/20
    OriginAS: AS30266
    NetName: A1COLO
    NetHandle: NET-64-6-96-0-1
    Parent: NET-64-0-0-0-0
    NetType: Direct Allocation
    RegDate: 2008-04-10
    Updated: 2008-12-04
    Ref: http://whois.arin.net/rest/net/NET-64-6-96-0-1

    OrgName: A1COLO.COM
    OrgId: A1COL
    Address: PMB #241 3089 - C CLAIREMONT DR.
    City: San Diego
    StateProv: CA
    PostalCode: 92117
    Country: US
    RegDate: 2004-08-13
    Updated: 2011-09-24
    Ref: http://whois.arin.net/rest/org/A1COL

    OrgAbuseHandle: TECHA4-ARIN
    OrgAbuseName: Tech Admin
    OrgAbusePhone: +1-877-805-6542
    OrgAbuseEmail: poc@a1colo.com
    OrgAbuseRef: http://whois.arin.net/rest/poc/TECHA4-ARIN

    OrgTechHandle: TECHA4-ARIN
    OrgTechName: Tech Admin
    OrgTechPhone: +1-877-805-6542
    OrgTechEmail: poc@a1colo.com
    OrgTechRef: http://whois.arin.net/rest/poc/TECHA4-ARIN

    RAbuseHandle: TECHA4-ARIN
    RAbuseName: Tech Admin
    RAbusePhone: +1-877-805-6542
    RAbuseEmail: poc@a1colo.com
    RAbuseRef: http://whois.arin.net/rest/poc/TECHA4-ARIN

    RNOCHandle: TECHA4-ARIN
    RNOCName: Tech Admin
    RNOCPhone: +1-877-805-6542
    RNOCEmail: poc@a1colo.com
    RNOCRef: http://whois.arin.net/rest/poc/TECHA4-ARIN

    RTechHandle: TECHA4-ARIN
    RTechName: Tech Admin
    RTechPhone: +1-877-805-6542
    RTechEmail: poc@a1colo.com
    RTechRef: http://whois.arin.net/rest/poc/TECHA4-ARIN

    #
    # ARIN WHOIS data and services are subject to the Terms of Use
    # available at: https://www.arin.net/whois_tou.html
    #

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 8 Errors
  • 4 Warnings
Ratio Text/Html
  • 0.5027969018932874
Message Error
  • Error Line 2, Column 1: Missing xmlns attribute for element html. The value should be: http://www.w3.org/1999/xhtml
    <html>

    Many Document Types based on XML need a mandatory xmlns attribute on the root element. For example, the root element for XHTML might look like:
    <html xmlns="http://www.w3.org/1999/xhtml">

  • Error Line 7, Column 12: there is no attribute "NAME"
    <META NAME="KEYWORDS" CONTENT="indian, hidden, cams, sex, scandal, voyeur, coup…

    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 7, Column 31: there is no attribute "CONTENT"
    <META NAME="KEYWORDS" CONTENT="indian, hidden, cams, sex, scandal, voyeur, coup…

    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 7, Column 105: element "META" undefined
    …ENT="indian, hidden, cams, sex, scandal, voyeur, couple, desi, video, movies"/>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 25, Column 46: end tag for "link" omitted, but OMITTAG NO was specified
    <link rel="shortcut icon" href="favicon.ico">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 25, Column 1: start tag was here
    <link rel="shortcut icon" href="favicon.ico">
  • Warning Line 59, Column 169: cannot generate system identifier for general entity "step"
    …re.indianhiddencams.com/signup/signup.php?nats=MC4wLjMuMy4wLjAuMC4wLjA&step=2">

    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 59, Column 169: general entity "step" not defined and no default entity
    …re.indianhiddencams.com/signup/signup.php?nats=MC4wLjMuMy4wLjAuMC4wLjA&step=2">

    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 59, Column 173: reference not terminated by REFC delimiter
    …re.indianhiddencams.com/signup/signup.php?nats=MC4wLjMuMy4wLjAuMC4wLjA&step=2">

    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 59, Column 173: reference to external entity in attribute value
    …re.indianhiddencams.com/signup/signup.php?nats=MC4wLjMuMy4wLjAuMC4wLjA&step=2">

    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 59, Column 173: reference to entity "step" for which no system identifier could be generated
    …re.indianhiddencams.com/signup/signup.php?nats=MC4wLjMuMy4wLjAuMC4wLjA&step=2">

    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 59, Column 168: entity was defined here
    …re.indianhiddencams.com/signup/signup.php?nats=MC4wLjMuMy4wLjAuMC4wLjA&step=2">
  • Warning Line 70, Column 77: character "&" is the first character of a delimiter but occurred as data
    …f="http://www.indianhiddencams.com/terms.htm">Terms & Condition</a></font></u> 

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 73, Column 7: end tag for "br" omitted, but OMITTAG NO was specified
    		<br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 73, Column 3: start tag was here
    		<br>

Visitor Analysis

Daily Visitor
  • 4.550 visits
Daily Visitor

In Page Analysis