csc.net.kw has Alexa Rank 62.568 and Google Page Rank is 7

csc.net.kw
  • Domain Name
    csc.net.kw
  • Favicon
  • Google Page Rank
    7
  • Alexa Rank
    #62568
  • Page Size
    145 B
  • Ip Address
    168.187.185.40
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
  • Meta Keyword
  • Meta Description

Technical Analysis

  • Webserver
    Microsoft-IIS/6.0
  • Ip Address
    168.187.185.40
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from csc.net.kw.

HTML Analysis

  • age: 1
  • date: Tue, 24 Sep 2013 01:51:37 GMT
  • cache-control: private
  • connection: Keep-Alive
  • via: NS-CACHE-9.2: 1
  • etag: "81c7d8e897f4cd1:564"
  • cteonnt-length: 129
  • content-type: text/html
  • content-location: http://csc.net.kw/login.htm
  • last-modified: Thu, 17 Jan 2013 09:49:14 GMT
  • accept-ranges: bytes
  • server: Microsoft-IIS/6.0
  • content-encoding: gzip
  • content-length: 132
  • x-google-cache-control: remote-fetch
No data whois for csc.net.kw

DNS Analysis


DNS servers
dns1.csc.net.kw [168.187.185.61]
dns.csc.net.kw [168.187.185.60]
dns2.csc.net.kw [168.187.185.62]
Query for DNS records for csc.net.kw failed: Timed out

DNS Records

IP 168.187.185.40 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 4 Errors
  • 5 Warnings
Ratio Text/Html
  • 0.8896551724137931
Message Error
  • Error Line 1, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
    <html>

    The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.

  • Warning Line 4, Column 90: NET-enabling start-tag requires SHORTTAG YES
    …-equiv="Refresh" content="0;URL='http://www.csc.net.kw:8888/csc/ar/home.jsp'"/>

    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 91: character data is not allowed here
    …-equiv="Refresh" content="0;URL='http://www.csc.net.kw:8888/csc/ar/home.jsp'"/>

    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.
  • Error Line 5, Column 7: end tag for "HEAD" which is not finished
    </head>

    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.

  • Error Line 6, Column 7: end tag for "HTML" which is not finished
    </html>

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