Get paid to take real surveys from market research companies. ...

clixsenseresearch.com
  • Domain Name
    clixsenseresearch.com
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #34000
  • Page Size
    101.7 KB
  • Ip Address
    66.129.126.94
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    1 GIF, 0 JPG, 6 PNG

Website Meta Analysis

  • Title
    ClixSense Research
  • Meta Keyword
    money, surveys, cash, paid surveys, work from home
  • Meta Description
    Get paid to take real surveys from market research companies.

Technical Analysis

  • Webserver
    Microsoft-IIS/7.0
  • Ip Address
    66.129.126.94
  • Domain Age
  • Javascript Library
    jquery, yui
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • cache-control: no-cache
  • pragma: no-cache
  • content-type: text/html; charset=utf-8
  • expires: -1
  • server: Microsoft-IIS/7.0
  • x-aspnet-version: 4.0.30319
  • x-powered-by: ASP.NET
  • date: Wed, 06 Feb 2013 18:53:46 GMT
  • content-length: 97610
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: clixsenseresearch.com

Registrant:
Web Support
1675 Larimer St
Suite 640
Denver, CO 80202
United States

Administrative Contact:
Web Support
1675 Larimer St
Suite 640
Denver, CO 80202
United States
email
+1 3035343333

Technical Contact:
Web Support
1675 Larimer St
Suite 640
Denver, CO 80202
United States
email
+1 3035343333

Record expires on 2013/02/17 UTC
Record created on 2011/02/17 UTC

Domain servers in listed order:
ns1.clt.peak-10.com
ns1.jax.peak-10.com

DNS Analysis


DNS servers
ns1.clt.peak-10.com [66.129.64.148]
ns1.jax.peak-10.com [66.129.80.148]


DNS Records

Answer records
clixsenseresearch.com SOA
server: ns1.clt.peak-10.com
email: jeremy@hutchings.oceansideten.com
serial: 2012062700
refresh: 28800
retry: 7200
expire: 604800
minimum ttl: 10800
10800s
clixsenseresearch.com NS  ns1.jax.peak-10.com 10800s
clixsenseresearch.com NS  ns1.clt.peak-10.com 10800s
clixsenseresearch.com A 66.129.126.94 10800s

Authority records

Additional records
ns1.clt.peak-10.com A 66.129.64.148 86400s
ns1.jax.peak-10.com A 66.129.80.148 86400s

IP 66.129.126.94 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Jacksonville
  • Continent Code
    32256
  • Latitude
    904
  • Longitude
    561
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 66.129.126.94"
    #
    # Use "?" to get help.
    #

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

    River Bay Investments, LLC P10-4281-7E50-28A (NET-66-129-126-80-1) 66.129.126.80 - 66.129.126.95
    Peak 10, Inc. PEAK10-NETBLK-02 (NET-66-129-64-0-1) 66.129.64.0 - 66.129.127.255


    #
    # 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
  • 19 Errors
  • 3 Warnings
Ratio Text/Html
  • 0.6778918654128767
Message Error
  • Warning Line 18, Column 43: character "&" is the first character of a delimiter but occurred as data
            if (top.location != self.location && BreakOut()) {

    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.
  • Warning Line 18, Column 44: character "&" is the first character of a delimiter but occurred as data
            if (top.location != self.location && BreakOut()) {

    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 125, Column 23: document type does not allow element "style" here
    <style type="text/css">

    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 133, Column 70: there is no attribute "lrid"
    …Header_ucLogin_hlForgotPassword" lrid="1021" href="ForgotPassword.aspx">Forgot…

    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 173, Column 67: there is no attribute "lrid"
    …       <span id="ctl01_ucHeader_ucLogin_lblWelcome" lrid="1041">Welcome</span>,

    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 250, Column 175: there is no attribute "border"
    …uageSelector_imgFlagUsa" src="App_Themes/web/images/flag_usa.gif" border="0" />

    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 259, Column 86: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …an id="ctl01_cpBody_cpMainContent"><div style="text-align: left; width: 100%;">

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 288, Column 1097: document type does not allow element "ul" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …le="line-height:100%;padding:5px;"><ul><li>Step 1: Complete the personal profi…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 298, Column 38: there is no attribute "lrid"
        <div class="sweeps_content" lrid="191931">

    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 312, Column 99: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …s_lblWinner1"><div class='winner_name'>James R.</div> <div class='winner_body'…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 312, Column 139: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ames R.</div> <div class='winner_body'>from Merritt Island, FL won the daily s…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 316, Column 99: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …s_lblWinner2"><div class='winner_name'>Dale A.</div> <div class='winner_body'>…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 316, Column 138: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …Dale A.</div> <div class='winner_body'>from Hartsville, SC won the weekly swee…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 320, Column 99: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …s_lblWinner3"><div class='winner_name'>Reyna M.</div> <div class='winner_body'…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 320, Column 139: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …eyna M.</div> <div class='winner_body'>from Fort Lupton, CO won the monthly sw…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 325, Column 120: required attribute "alt" not specified
    …cSweeps_imgContent" src="App_Themes/cvs/images/lower_content.png" border="0" />

    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 332, Column 113: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …Body_cpMainContent_cpRightContent"><div style="text-align: left; width: 100%;">

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 360, Column 23: an attribute specification must start with a name or name token
    <style type="text/css"">

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 360, Column 23: document type does not allow element "style" here
    <style type="text/css"">

    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 1015, Column 216: there is no attribute "lrid"
    …y_cpMainContent_cpRightContent_btnSubmit" class="registerButton" lrid="1025" />

    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 1096, Column 55: character "<" is the first character of a delimiter but occurred as data
    …    <span id="ctl01_lblMessageHeader"><%=Translate("Validation Errors", 192220…

    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 1124, Column 25: end tag for "ul" which is not finished
                        </ul>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

Visitor Analysis

Daily Visitor
  • 5.017 visits
Daily Visitor