onlinecci.com

Welcome Login Technical Requirements Is Online Learning For Me? Welcome User ID Password * a possible cause for unsuccessful login may be missing dashes in your Student ID Number (xxx-xx-xxxx). Forgot your Password? ...

Display Widget for this domain on your website. Click Here
This data was last updated from 26-07-2013 09:29:32  (update).

Overview Info

  • Domain Name
    onlinecci.com
  • Favicon
  • Alexa Rank
    #25651
  • Google Page Rank
    PR 0
  • Ip Address
    159.182.165.124
  • Page Size
    9.9 KB
  • Images
    5 GIF, 0 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 0 0 0 0 0

Website Meta Analysis



  • Title
    Corinthian Colleges Inc. | Welcome
  • Meta Keyword
  • Meta Description
    Welcome Login Technical Requirements Is Online Learning For Me? Welcome User ID Password * a possible cause for unsuccessful login may be missing dashes in your Student ID Number (xxx-xx-xxxx). Forgot your Password? Need additional help signing ...

Technical Analysis



  • Webserver
    Microsoft-IIS/6.0
  • Ip Address
    159.182.165.124
  • Domain Age
    13 Years, 0 Months, 29 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Fri, 26 Jul 2013 09:29:29 GMT
  • server: Microsoft-IIS/6.0
  • p3p: CP="NOI ADM DEV PSAi COM NAV OUR OTR STP IND DEM"
  • x-powered-by: ASP.NET
  • content-length: 9361
  • content-type: text/html
  • cache-control: private
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Corinthian Colleges, Inc.
6 Hutton Centre Drive
Suite 400
Santa Ana, California 92707
United States

Domain Name: ONLINECCI.COM
Created on: 05-Jul-00
Expires on: 05-Jul-14
Last Updated on: 28-Jun-11

Administrative Contact:
Brock, Joe email
Corinthian Colleges, Inc.
6 Hutton Centre Drive
Suite 400
Santa Ana, California 92707
United States
+1.7144273000

Technical Contact:
Roach, Scott email
Corinthian Colleges, Inc.
6 Hutton Centre Drive
Suite 400
Santa Ana, California 92707
United States
7144273000

Domain servers in listed order:
NS1.REALEDUCATION.COM
DNS1.REALED.COM

DNS Analysis


DNS servers
dns1.realed.com [159.182.160.50]
ns1.realeducation.com [216.241.110.27]


DNS Records

Answer records
onlinecci.com A 159.182.165.124 300s
onlinecci.com NS  dns1.ecollege.com 300s
onlinecci.com NS  ns1.ecollege.com 300s
onlinecci.com SOA
server: dns1.ecollege.com
email: administrator@ecollege.com
serial: 2004061628
refresh: 3600
retry: 600
expire: 86400
minimum ttl: 300
300s
onlinecci.com MX
preference: 200
exchange: ecollege.com.s6a2.psmtp.com
300s
onlinecci.com MX
preference: 300
exchange: ecollege.com.s6b1.psmtp.com
300s
onlinecci.com MX
preference: 400
exchange: ecollege.com.s6b2.psmtp.com
300s
onlinecci.com MX
preference: 100
exchange: ecollege.com.s6a1.psmtp.com
300s
onlinecci.com TXT v=spf1 300s

Authority records

Additional records
dns1.ecollege.com A 159.182.160.50 300s
ns1.ecollege.com A 216.241.110.27 300s

IP 159.182.165.124 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 16 Errors
  • 7 Warnings
Ratio Text/Html
  • 0.39469287469287473
Message Error
  • Error Line 2, 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.

  • Error Line 7, 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>.

  • Error Line 51, Column 81: end tag for element "A" which is not open
    … <a href="javascript:openwindow('http://www.wherever.com');">hyperlink text</a>

    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 185, Column 38: there is no attribute "MARGINHEIGHT"
    <BODY onLoad="resize()" marginheight="0" marginwidth="0" topmargin="0" leftmarg…

    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 185, Column 54: there is no attribute "MARGINWIDTH"
    …nLoad="resize()" marginheight="0" marginwidth="0" topmargin="0" leftmargin="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 185, Column 68: there is no attribute "TOPMARGIN"
    …nLoad="resize()" marginheight="0" marginwidth="0" topmargin="0" leftmargin="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 185, Column 83: there is no attribute "LEFTMARGIN"
    …nLoad="resize()" marginheight="0" marginwidth="0" topmargin="0" leftmargin="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 192, Column 17: there is no attribute "VALIGN"
    		<table valign="top" cellpadding="10">

    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 227, Column 97: document type does not allow element "META" here
    …"REFRESH" content="0;url=https://enroll.everestonline.edu/ecollege/login.aspx">

    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 241, Column 30: invalid comment declaration: found name character outside comment but inside comment declaration
    		<!--- BEGIN Nested Table --->
  • Info Line 241, Column 3: comment declaration started here
    		<!--- BEGIN Nested Table --->
  • Error Line 245, Column 53: there is no attribute "AUTOCOMPLETE"
    … ALIGN="center"><input type=text autocomplete="off" name=Username size=11></TD>

    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 251, Column 38: invalid comment declaration: found name character outside comment but inside comment declaration
    		</TABLE>		<!--- END Nested Table --->
  • Info Line 251, Column 13: comment declaration started here
    		</TABLE>		<!--- END Nested Table --->
  • Warning Line 274, Column 74: cannot generate system identifier for general entity "subaction"
    …e.com/corin/index.learn?action=errors&subaction=problems">Forgot your Password…

    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 274, Column 74: general entity "subaction" not defined and no default entity
    …e.com/corin/index.learn?action=errors&subaction=problems">Forgot your Password…

    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.

  • Error Line 274, Column 83: reference to entity "subaction" for which no system identifier could be generated
    …m/corin/index.learn?action=errors&subaction=problems">Forgot your Password?</a>

    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 274, Column 73: entity was defined here
    …ge.com/corin/index.learn?action=errors&subaction=problems">Forgot your Passwor…
  • Error Line 276, Column 83: reference to entity "subaction" for which no system identifier could be generated
    …in/index.learn?action=errors&subaction=contact">Need additional help signing i…

    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 274, Column 73: entity was defined here
    …ge.com/corin/index.learn?action=errors&subaction=problems">Forgot your Passwor…
  • Error Line 284, Column 10: end tag for element "P" which is not open
    						</P>

    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.

  • Warning Line 290, Column 5: NET-enabling start-tag requires SHORTTAG YES
    <br />

    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.

  • Warning Line 295, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …llege.gif" width="79" height="42" border="0" alt="Empowered by eCollege" /></a>

    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.

Visitor Analysis

Daily Visitor
  • 1.400 visits

In Page Analysis