IT-GK Login Govt. Reimbursement Home | About RKCL | Directors | RKCL Programs | Management Team | Channel Partner Network | Highlights Select a Course Select a Product Select an Activity Content on ...

rkcl.in
  • Domain Name
    rkcl.in
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #528235
  • Page Size
    18.7 KB
  • Ip Address
    111.118.190.178
  • Heading
    H1: 14, H2: 0, H3: 0, H4: 1, H5: 0, H6: 0
  • Images
    7 GIF, 9 JPG, 1 PNG

Website Meta Analysis

  • Title
    Rajasthan knowledge Corporation Ltd.
  • Meta Keyword
  • Meta Description
    IT-GK Login Govt. Reimbursement Home | About RKCL | Directors | RKCL Programs | Management Team | Channel Partner Network | Highlights Select a Course Select a Product Select an Activity Content on this page requires a newer version of Adobe ...

Technical Analysis

  • Webserver
    Microsoft-IIS/7.5
  • Ip Address
    111.118.190.178
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from rkcl.in.

HTML Analysis

  • content-type: text/html
  • content-encoding: gzip
  • last-modified: Tue, 27 Aug 2013 12:00:59 GMT
  • accept-ranges: bytes
  • etag: "80fdc171da3ce1:0"
  • vary: Accept-Encoding
  • server: Microsoft-IIS/7.5
  • x-powered-by: ASP.NET
  • date: Tue, 27 Aug 2013 17:09:31 GMT
  • content-length: 5131
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for rkcl.in

DNS Analysis


DNS servers
ns1.rkcl.in [111.118.190.178]
ns2.rkcl.in [111.118.190.179]


DNS Records

Answer records
rkcl.in A 111.118.190.178 86400s
rkcl.in NS  ns2.rkcl.in 86400s
rkcl.in NS  ns1.rkcl.in 86400s
rkcl.in SOA
server: ns1.rkcl.in
email: hostmaster@rkcl.in
serial: 2013030105
refresh: 3600
retry: 600
expire: 1209600
minimum ttl: 86400
86400s
rkcl.in MX
preference: 1
exchange: mail.rkcl.in
86400s

Authority records

Additional records
ns2.rkcl.in A 111.118.190.179 86400s
ns1.rkcl.in A 111.118.190.178 86400s
mail.rkcl.in A 111.118.190.179 86400s

IP 111.118.190.178 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 48 Errors
  • 17 Warnings
Ratio Text/Html
  • 0.7256572414153557
Message Error
  • Error Line 102, Column 98: required attribute "alt" not specified
    …f="education-program.html"><img src="images/rs-cit.jpg" border="0" /></a><br />

    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 108, Column 114: required attribute "alt" not specified
    … src="images/DU-logo.jpg" border="0" /></a> <a href="educational-e-governance-…

    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 136, Column 47: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …January 2013 exam Event) <font color =red>Download Permission letter </font><i…
  • Error Line 136, Column 94: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … =red>Download Permission letter </font><img src=images/new.gif border=0></div>
  • Error Line 136, Column 101: NET-enabling start-tag not immediately followed by null end-tag
    … =red>Download Permission letter </font><img src=images/new.gif border=0></div>

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 136, Column 101: required attribute "alt" not specified
    … =red>Download Permission letter </font><img src=images/new.gif border=0></div>

    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 136, Column 101: end tag for "img" omitted, but OMITTAG NO was specified
    … =red>Download Permission letter </font><img src=images/new.gif border=0></div>

    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 136, Column 85: start tag was here
    … =red>Download Permission letter </font><img src=images/new.gif border=0></div>
  • Error Line 138, Column 49: element "Br" undefined
    …Corporate Presentation 2012-2013 <Br /> <span><a href="download\RKCL Profile_d…

    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).
  • Warning Line 141, Column 22: character "&" is the first character of a delimiter but occurred as data
        <h1>ANNOUNCEMNET & NOTIFICATION</h1>

    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 145, Column 59: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …deline.html"><div class="BlueBox-Text"> <span class="style8">RKCL's Center Ren…

    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 145, Column 127: end tag for "div" omitted, but OMITTAG NO was specified
    …ext"> <span class="style8">RKCL's Center Renewal Process-2013</span> </a></div>

    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 145, Column 34: start tag was here
    	<a href="renewalguideline.html"><div class="BlueBox-Text"> <span class="style8…
  • Error Line 147, Column 45: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …f="iti.html"><div class="BlueBox-Text"> <span class="style8">ITI- RKCL Project…

    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 147, Column 96: end tag for "div" omitted, but OMITTAG NO was specified
    … class="BlueBox-Text"> <span class="style8">ITI- RKCL Project</span> </a></div>

    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 147, Column 20: start tag was here
    <a href="iti.html"><div class="BlueBox-Text"> <span class="style8">ITI- RKCL Pr…
  • Error Line 149, Column 47: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …f="ncr.html"><div class="BlueBox-Text"> <span class="style8">RKCL's New Center…

    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 149, Column 125: end tag for "div" omitted, but OMITTAG NO was specified
    … class="style8">RKCL's New Center Registeration Process-2013</span> </a></div> 

    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 149, Column 22: start tag was here
    	 <a href="ncr.html"><div class="BlueBox-Text"> <span class="style8">RKCL's New…
  • Error Line 150, Column 56: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ficate.html"><div class="BlueBox-Text"> <span class="style8"><font color = whi…

    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 150, Column 93: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …"> <span class="style8"><font color = white>List of learners eligible for RSCI…
  • Error Line 150, Column 209: end tag for "div" omitted, but OMITTAG NO was specified
    …rtificates in NOV-12 , DEC-12 and JAN 2013 Exam Event </font></span> </a></div>

    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 150, Column 31: start tag was here
    	  <a href="Certificate.html"><div class="BlueBox-Text"> <span class="style8"><…
  • Error Line 150, Column 215: end tag for element "div" which is not open
    …rtificates in NOV-12 , DEC-12 and JAN 2013 Exam Event </font></span> </a></div>

    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 152, Column 8: end tag for element "div" which is not open
      </div>

    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 156, Column 6: end tag for element "div" which is not open
    </div>

    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 179, Column 19: there is no attribute "type"
          <embed type="application/x-shockwave-flash" src="https://picasaweb.google…

    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 179, Column 55: there is no attribute "src"
    …e="application/x-shockwave-flash" src="https://picasaweb.google.com/s/c/bin/sl…

    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 179, Column 114: there is no attribute "width"
    …ogle.com/s/c/bin/slideshow.swf" width="288" height="192" flashvars="host=picas…

    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 179, Column 127: there is no attribute "height"
    …bin/slideshow.swf" width="288" height="192" flashvars="host=picasaweb.google.c…

    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 179, Column 143: there is no attribute "flashvars"
    …f" width="288" height="192" flashvars="host=picasaweb.google.com&hl=en_US&feat…

    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 179, Column 170: cannot generate system identifier for general entity "hl"
    … flashvars="host=picasaweb.google.com&hl=en_US&feat=flashalbum&RGB=0x000000&fe…

    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 179, Column 170: general entity "hl" not defined and no default entity
    … flashvars="host=picasaweb.google.com&hl=en_US&feat=flashalbum&RGB=0x000000&fe…

    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 179, Column 172: reference not terminated by REFC delimiter
    …lashvars="host=picasaweb.google.com&hl=en_US&feat=flashalbum&RGB=0x000000&feed…

    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 179, Column 172: reference to external entity in attribute value
    …lashvars="host=picasaweb.google.com&hl=en_US&feat=flashalbum&RGB=0x000000&feed…

    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 179, Column 172: reference to entity "hl" for which no system identifier could be generated
    …lashvars="host=picasaweb.google.com&hl=en_US&feat=flashalbum&RGB=0x000000&feed…

    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 179, Column 169: entity was defined here
    …" flashvars="host=picasaweb.google.com&hl=en_US&feat=flashalbum&RGB=0x000000&f…
  • Warning Line 179, Column 179: cannot generate system identifier for general entity "feat"
    …s="host=picasaweb.google.com&hl=en_US&feat=flashalbum&RGB=0x000000&feed=https%…

    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 179, Column 179: general entity "feat" not defined and no default entity
    …s="host=picasaweb.google.com&hl=en_US&feat=flashalbum&RGB=0x000000&feed=https%…

    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 179, Column 183: reference not terminated by REFC delimiter
    …ost=picasaweb.google.com&hl=en_US&feat=flashalbum&RGB=0x000000&feed=https%3A%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 179, Column 183: reference to external entity in attribute value
    …ost=picasaweb.google.com&hl=en_US&feat=flashalbum&RGB=0x000000&feed=https%3A%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 179, Column 183: reference to entity "feat" for which no system identifier could be generated
    …ost=picasaweb.google.com&hl=en_US&feat=flashalbum&RGB=0x000000&feed=https%3A%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 179, Column 178: entity was defined here
    …rs="host=picasaweb.google.com&hl=en_US&feat=flashalbum&RGB=0x000000&feed=https…
  • Warning Line 179, Column 195: cannot generate system identifier for general entity "RGB"
    …b.google.com&hl=en_US&feat=flashalbum&RGB=0x000000&feed=https%3A%2F%2Fpicasawe…

    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 179, Column 195: general entity "RGB" not defined and no default entity
    …b.google.com&hl=en_US&feat=flashalbum&RGB=0x000000&feed=https%3A%2F%2Fpicasawe…

    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 179, Column 198: reference not terminated by REFC delimiter
    …oogle.com&hl=en_US&feat=flashalbum&RGB=0x000000&feed=https%3A%2F%2Fpicasaweb.g…

    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 179, Column 198: reference to external entity in attribute value
    …oogle.com&hl=en_US&feat=flashalbum&RGB=0x000000&feed=https%3A%2F%2Fpicasaweb.g…

    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 179, Column 198: reference to entity "RGB" for which no system identifier could be generated
    …oogle.com&hl=en_US&feat=flashalbum&RGB=0x000000&feed=https%3A%2F%2Fpicasaweb.g…

    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 179, Column 194: entity was defined here
    …eb.google.com&hl=en_US&feat=flashalbum&RGB=0x000000&feed=https%3A%2F%2Fpicasaw…
  • Warning Line 179, Column 208: cannot generate system identifier for general entity "feed"
    …hl=en_US&feat=flashalbum&RGB=0x000000&feed=https%3A%2F%2Fpicasaweb.google.com%…

    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 179, Column 208: general entity "feed" not defined and no default entity
    …hl=en_US&feat=flashalbum&RGB=0x000000&feed=https%3A%2F%2Fpicasaweb.google.com%…

    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 179, Column 212: reference not terminated by REFC delimiter
    …n_US&feat=flashalbum&RGB=0x000000&feed=https%3A%2F%2Fpicasaweb.google.com%2Fda…

    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 179, Column 212: reference to external entity in attribute value
    …n_US&feat=flashalbum&RGB=0x000000&feed=https%3A%2F%2Fpicasaweb.google.com%2Fda…

    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 179, Column 212: reference to entity "feed" for which no system identifier could be generated
    …n_US&feat=flashalbum&RGB=0x000000&feed=https%3A%2F%2Fpicasaweb.google.com%2Fda…

    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 179, Column 207: entity was defined here
    …&hl=en_US&feat=flashalbum&RGB=0x000000&feed=https%3A%2F%2Fpicasaweb.google.com…
  • Error Line 179, Column 403: there is no attribute "pluginspage"
    …%3D117430825858274909430" pluginspage="http://www.macromedia.com/go/getflashpl…

    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 179, Column 448: element "embed" undefined
    …09430" pluginspage="http://www.macromedia.com/go/getflashplayer"></embed></div>

    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).
  • Warning Line 183, Column 113: reference not terminated by REFC delimiter
    …videoseries?list=PLEE1AED6AAA0EDB27&hl=en_US" frameborder="0" allowfullscreen>…

    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 183, Column 113: reference to external entity in attribute value
    …videoseries?list=PLEE1AED6AAA0EDB27&hl=en_US" frameborder="0" allowfullscreen>…

    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 183, Column 113: reference to entity "hl" for which no system identifier could be generated
    …videoseries?list=PLEE1AED6AAA0EDB27&hl=en_US" frameborder="0" allowfullscreen>…

    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 179, Column 169: entity was defined here
    …" flashvars="host=picasaweb.google.com&hl=en_US&feat=flashalbum&RGB=0x000000&f…
  • Error Line 183, Column 152: "allowfullscreen" is not a member of a group specified for any attribute
    …ies?list=PLEE1AED6AAA0EDB27&hl=en_US" frameborder="0" allowfullscreen></iframe>
  • Error Line 195, Column 56: required attribute "type" not specified
    	  <script src="http://widgets.twimg.com/j/2/widget.js"></script>

    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 196, Column 14: required attribute "type" not specified
          <script>

    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 244, Column 6: end tag for element "div" which is not open
    </div>

    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 261, Column 21: there is no attribute "class"
            <Span class="spacing">© 2008 - 2012. All Rights Reserved.</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 261, Column 30: element "Span" undefined
            <Span class="spacing">© 2008 - 2012. All Rights Reserved.</Span>

    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 269, Column 61: element "Span" undefined
    …<a href="schemes.asp">Schemes</a><Span> | </Span> <a href="webcasting.html">We…

    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 269, Column 119: element "Span" undefined
    …"webcasting.html">Webcasting </a><Span> | </Span> <a href="http://rkcl.in/supp…

    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 269, Column 218: end tag for element "Span" which is not open
    …>e-HelpDesk Service</a><span> | </Span> <a href="schemes1.html">Government Rei…

    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 269, Column 293: end tag for "span" omitted, but OMITTAG NO was specified
    …pan> <a href="schemes1.html">Government Reimbursement</a><span> | </span></div>

    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 269, Column 203: start tag was here
    …target="_blank">e-HelpDesk Service</a><span> | </Span> <a href="schemes1.html"…
  • Error Line 271, Column 75: required attribute "alt" not specified
    <img src="images/bottom-icon.png" border="0" align="right" usemap="#Map" />

    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>.

  • Warning Line 301, Column 70: character "&" is the first character of a delimiter but occurred as data
      <li ><a href="enabling-program.html">IT Infrastructure Development & <br />

    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.

Visitor Analysis

Daily Visitor
  • 268 visits