prelaunchx.com

sign up log in Most Recent Profitable Trade Details Profit: +6.8% Currency Pair: EUR/USD Action: Sell/Short Enter Price: 1.3004 Exit Price: 1.2977 Chart: See below At prelaunchX, we help companies launch new products ...

Display Widget for this domain on your website. Click Here
This data was last updated from 20-07-2013 11:24:19  (update).

Overview Info

  • Domain Name
    prelaunchx.com
  • Favicon
  • Alexa Rank
    #11747
  • Google Page Rank
    PR 4
  • Ip Address
    107.20.152.119
  • Page Size
    5.9 KB
  • Images
    3 GIF, 0 JPG, 3 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 0 0 0 0

Website Meta Analysis



  • Title
    prelaunchX
  • Meta Keyword
  • Meta Description
    sign up log in Most Recent Profitable Trade Details Profit: +6.8% Currency Pair: EUR/USD Action: Sell/Short Enter Price: 1.3004 Exit Price: 1.2977 Chart: See below At prelaunchX, we help companies launch new products and services. Our current ...

Technical Analysis



  • Webserver
    nginx
  • Ip Address
    107.20.152.119
  • Domain Age
    1 Years, 9 Months, 22 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • cache-control: no-cache, must-revalidate
  • content-encoding: gzip
  • content-type: text/html
  • date: Sat, 20 Jul 2013 11:24:17 GMT
  • etag: 056df0ac91b0756cce0b7194d7a2943efd1c7cbf
  • expires: Sat, 1 Jan 2000 01:00:00 GMT
  • last-modified: Sat, 20 Jul 2013 11:24:17 GMT
  • pragma: no-cache
  • server: nginx
  • content-length: 2232
  • connection: keep-alive
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain name: prelaunchx.com

Registrant Contact:
WhoisGuard
WhoisGuard Protected ()

Fax:
11400 W. Olympic Blvd. Suite 200
Los Angeles, CA 90064
US

Administrative Contact:
WhoisGuard
WhoisGuard Protected ( email )
+1.6613102107
Fax: +1.6613102107
11400 W. Olympic Blvd. Suite 200
Los Angeles, CA 90064
US

Technical Contact:
WhoisGuard
WhoisGuard Protected ( email )
+1.6613102107
Fax: +1.6613102107
11400 W. Olympic Blvd. Suite 200
Los Angeles, CA 90064
US

Status: Locked

Name Servers:
ns-1414.awsdns-48.org
ns-1544.awsdns-01.co.uk
ns-186.awsdns-23.com
ns-842.awsdns-41.net

Creation date: 07 Oct 2011 23:35:00
Expiration date: 07 Oct 2013 15:35:00

DNS Analysis


DNS servers
ns-186.awsdns-23.com [205.251.192.186]
ns-842.awsdns-41.net
ns-1544.awsdns-01.co.uk
ns-1414.awsdns-48.org [205.251.197.134]


DNS Records

Answer records
prelaunchx.com A 107.22.209.23 60s
prelaunchx.com NS  ns-1414.awsdns-48.org 172800s
prelaunchx.com NS  ns-1544.awsdns-01.co.uk 172800s
prelaunchx.com NS  ns-186.awsdns-23.com 172800s
prelaunchx.com NS  ns-842.awsdns-41.net 172800s
prelaunchx.com SOA
server: ns-186.awsdns-23.com
email: awsdns-hostmaster@amazon.com
serial: 1
refresh: 86400
retry: 900
expire: 1209600
minimum ttl: 172800
43200s
prelaunchx.com MX
preference: 1
exchange: aspmx.l.google.com
3600s
prelaunchx.com MX
preference: 10
exchange: aspmx2.googlemail.com
3600s
prelaunchx.com MX
preference: 10
exchange: aspmx3.googlemail.com
3600s
prelaunchx.com MX
preference: 5
exchange: alt1.aspmx.l.google.com
3600s
prelaunchx.com MX
preference: 5
exchange: alt2.aspmx.l.google.com
3600s
prelaunchx.com TXT spf2.0/pra include:amazonses.com ?all 172800s
prelaunchx.com TXT v=spf1 include:_spf.google.com include:amazonses.com ~all 172800s

Authority records

Additional records

IP 107.20.152.119 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 7 Errors
  • 2 Warnings
Ratio Text/Html
  • 0.5949013157894737
Message Error
  • Warning Line 4, Column 70: NET-enabling start-tag requires SHORTTAG YES
      <meta http-equiv="content-type" content="text/html; charset=UTF-8" />

    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 4, Column 71: character data is not allowed here
      <meta http-equiv="content-type" content="text/html; charset=UTF-8" />

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Warning Line 7, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …="https://d2d8s538k9yc1m.cloudfront.net/images/icon-32.png" type="image/png" />

    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 8, Column 104: document type does not allow element "LINK" here
    …8s538k9yc1m.cloudfront.net/styles.v03.gz.css" type="text/css" rel="stylesheet">

    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 9, 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 61, Column 16: end tag for element "HEAD" which is not open
    </script></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 62, 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 100, Column 78: required attribute "ALT" not specified
      <img src="//d2d8s538k9yc1m.cloudfront.net/images/ffx/charts/1357306188.png">

    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 126, Column 300: required attribute "ALT" not specified
    … 32px; width: 32px; margin-right: 12px; vertical-align: -5px;">Sign Up</button>

    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
  • 5.017 visits

In Page Analysis