Videochat, gratis e senza registrazione. Entra in videochat per conoscere, incontrare e fare nuove amicizie. Ti basta un click. ...

ciaoamigos.it
  • Domain Name
    ciaoamigos.it
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #25725
  • Page Size
    59.3 KB
  • Ip Address
    95.110.250.228
  • Heading
    H1: 0, H2: 0, H3: 6, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 6 PNG

Website Meta Analysis

  • Title
    ciao aMigos - videochat e chat gratis senza registrazione
  • Meta Keyword
    webcam,videochat,chatta,incontri,videochat gratis ,video chat,chat,
  • Meta Description
    Videochat, gratis e senza registrazione. Entra in videochat per conoscere, incontrare e fare nuove amicizie. Ti basta un click.

Technical Analysis

  • Webserver
    nginx
  • Ip Address
    95.110.250.228
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from ciaoamigos.it.

HTML Analysis

  • server: nginx
  • date: Fri, 01 Feb 2013 14:37:26 GMT
  • content-type: text/html; charset=UTF-8
  • content-length: 13638
  • connection: close
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • vary: Accept-Encoding,User-Agent
  • content-encoding: gzip
  • accept-ranges: bytes
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for ciaoamigos.it

DNS Analysis


DNS servers
ns2.register.it
ns1.register.it


DNS Records

Answer records
ciaoamigos.it MX
preference: 10
exchange: mail.ciaoamigos.it
900s
ciaoamigos.it NS  ns1.register.it 900s
ciaoamigos.it A 95.110.250.228 900s
ciaoamigos.it SOA
server: ns1.register.it
email: hostmaster@register.it
serial: 2011030101
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 86400
900s
ciaoamigos.it NS  ns2.register.it 900s

Authority records

Additional records

IP 95.110.250.228 Analysis

  • Country Code
    IT
  • Country Code3
    ITA
  • Country Name
    Italy
  • City
    Milan
  • Continent Code
    EU
  • Latitude
    45.4667
  • Longitude
    9.2.
  • No whois ip data for 95.110.250.228

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 37 Errors
  • 36 Warnings
Ratio Text/Html
  • 0.20129068370017944
Message Error
  • Error Line 154, Column 17: syntax of attribute value does not conform to declared value
          <form id="" enctype="application/x-www-form-urlencoded" class="form_top_l…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 155, Column 11: document type does not allow element "label" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
        <label>Utente</label>

    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 156, Column 80: there is no attribute "autofocus"
    …me="email" id="email" value="" tabindex="1" autofocus="autofocus" class="text">

    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 156, Column 104: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …me="email" id="email" value="" tabindex="1" autofocus="autofocus" class="text">

    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 156, Column 105: end tag for "input" omitted, but OMITTAG NO was specified
    …me="email" id="email" value="" tabindex="1" autofocus="autofocus" class="text">

    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 156, Column 5: start tag was here
        <input type="text" name="email" id="email" value="" tabindex="1" autofocus=…
  • Error Line 157, Column 11: document type does not allow element "label" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
        <label>Password</label>

    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 158, Column 79: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
        <input type="password" name="password" id="password" value="" tabindex="2">

    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 158, Column 80: end tag for "input" omitted, but OMITTAG NO was specified
        <input type="password" name="password" id="password" value="" tabindex="2">

    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 158, Column 5: start tag was here
        <input type="password" name="password" id="password" value="" tabindex="2">
  • Error Line 159, Column 65: document type does not allow element "button" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
        <button name="submit" id="submit" type="submit" tabindex="3">Entra</button>

    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 278, Column 92: document type does not allow element "style" here
    …eneric_layout_container layout_ynadvsearch_ynadvsearch"><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).

  • Warning Line 302, Column 18: character "&" is the first character of a delimiter but occurred as data
            while (p && p.style != null) {

    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 302, Column 19: character "&" is the first character of a delimiter but occurred as data
            while (p && p.style != null) {

    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 344, Column 38: character "&" is the first character of a delimiter but occurred as data
    	        		if(item_type !=token.type && token.type != 'see_more_link' && token.…

    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 344, Column 39: character "&" is the first character of a delimiter but occurred as data
    	        		if(item_type !=token.type && token.type != 'see_more_link' && token.…

    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 344, Column 71: character "&" is the first character of a delimiter but occurred as data
    …type && token.type != 'see_more_link' && token.type != 'no_result_found_link')…

    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 344, Column 72: character "&" is the first character of a delimiter but occurred as data
    …type && token.type != 'see_more_link' && token.type != 'no_result_found_link'){

    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 366, Column 30: character "&" is the first character of a delimiter but occurred as data
    		  			if(typeof(token.type) && token.type=='see_more_link'){

    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 366, Column 31: character "&" is the first character of a delimiter but occurred as data
    		  			if(typeof(token.type) && token.type=='see_more_link'){

    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 403, Column 13: character "<" is the first character of a delimiter but occurred as data
    				while(l < trimquery.length && trimquery[l] == '#FFFFFF')

    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 403, Column 32: character "&" is the first character of a delimiter but occurred as data
    				while(l < trimquery.length && trimquery[l] == '#FFFFFF')

    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 403, Column 33: character "&" is the first character of a delimiter but occurred as data
    				while(l < trimquery.length && trimquery[l] == '#FFFFFF')

    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 406, Column 19: character "&" is the first character of a delimiter but occurred as data
    				if (trimquery && ynadvsearch.is_space == false)

    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 406, Column 20: character "&" is the first character of a delimiter but occurred as data
    				if (trimquery && ynadvsearch.is_space == false)

    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 472, Column 130: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    … name='query' id='global_search_field' size='20' maxlength='100' alt='Cerca' />

    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 545, Column 50: element "center" undefined
    …('inbox_content').innerHTML = '<center><img src="'+img_loading+'" border="0" /…

    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 545, Column 85: there is no attribute "border"
    …tent').innerHTML = '<center><img src="'+img_loading+'" border="0" /></center>';

    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 545, Column 90: required attribute "alt" not specified
    …tent').innerHTML = '<center><img src="'+img_loading+'" border="0" /></center>';

    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 550, Column 51: element "center" undefined
    …'friend_content').innerHTML = '<center><img src="'+img_loading+'" border="0" /…

    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 550, Column 91: required attribute "alt" not specified
    …tent').innerHTML = '<center><img src="'+img_loading+'" border="0" /></center>';

    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 555, Column 57: element "center" undefined
    …ication_content').innerHTML = '<center><img src="'+img_loading+'" border="0" /…

    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 555, Column 97: required attribute "alt" not specified
    …tent').innerHTML = '<center><img src="'+img_loading+'" border="0" /></center>';

    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 564, Column 51: element "center" undefined
    …end_action_'+rid).innerHTML = '<center><img src="'+img_loading+'" border="0" /…

    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 564, Column 91: required attribute "alt" not specified
    …'+rid).innerHTML = '<center><img src="'+img_loading+'" border="0" /></center>';

    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 585, Column 51: element "center" undefined
    …end_action_'+rid).innerHTML = '<center><img src="'+img_loading+'" border="0" /…

    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 585, Column 91: required attribute "alt" not specified
    …'+rid).innerHTML = '<center><img src="'+img_loading+'" border="0" /></center>';

    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 775, Column 32: character "&" is the first character of a delimiter but occurred as data
              if (inbox_msg.length && isLoaded[1] == 1) {

    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 775, Column 33: character "&" is the first character of a delimiter but occurred as data
              if (inbox_msg.length && isLoaded[1] == 1) {

    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 793, Column 28: character "&" is the first character of a delimiter but occurred as data
           if (freq_msg.length && isLoaded[0] == 1) {

    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 793, Column 29: character "&" is the first character of a delimiter but occurred as data
           if (freq_msg.length && isLoaded[0] == 1) {

    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 811, Column 39: character "&" is the first character of a delimiter but occurred as data
              if (notification_msg.length && isLoaded[2] == 1) {

    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 811, Column 40: character "&" is the first character of a delimiter but occurred as data
              if (notification_msg.length && isLoaded[2] == 1) {

    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 989, Column 26: character "&" is the first character of a delimiter but occurred as data
            if (inbox_status && inbox_count_down <= 0) {

    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 989, Column 27: character "&" is the first character of a delimiter but occurred as data
            if (inbox_status && inbox_count_down <= 0) {

    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 989, Column 46: character "<" is the first character of a delimiter but occurred as data
            if (inbox_status && inbox_count_down <= 0) {

    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 996, Column 50: character "<" is the first character of a delimiter but occurred as data
                inbox_count_down = (inbox_count_down <= 0) ? 0 : --inbox_count_down;

    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 999, Column 27: character "&" is the first character of a delimiter but occurred as data
            if (friend_status && friend_count_down <= 0) {

    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 999, Column 28: character "&" is the first character of a delimiter but occurred as data
            if (friend_status && friend_count_down <= 0) {

    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 999, Column 48: character "<" is the first character of a delimiter but occurred as data
            if (friend_status && friend_count_down <= 0) {

    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 1007, Column 52: character "<" is the first character of a delimiter but occurred as data
    …        friend_count_down = (friend_count_down <= 0) ? 0 : --friend_count_down;

    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 1009, Column 33: character "&" is the first character of a delimiter but occurred as data
            if (notification_status && notification_count_down <= 0) {

    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 1009, Column 34: character "&" is the first character of a delimiter but occurred as data
            if (notification_status && notification_count_down <= 0) {

    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 1009, Column 60: character "<" is the first character of a delimiter but occurred as data
            if (notification_status && notification_count_down <= 0) {

    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 1016, Column 64: character "<" is the first character of a delimiter but occurred as data
    …on_count_down = (notification_count_down <= 0) ? 0 : --notification_count_down;

    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 1091, Column 30: character "&" is the first character of a delimiter but occurred as data
        if (e.type != 'mouseout' && e.type != 'mouseover') return false;

    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 1091, Column 31: character "&" is the first character of a delimiter but occurred as data
        if (e.type != 'mouseout' && e.type != 'mouseover') return false;

    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 1094, Column 18: character "&" is the first character of a delimiter but occurred as data
        while (reltg && reltg != handler) reltg = reltg.parentNode;

    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 1094, Column 19: character "&" is the first character of a delimiter but occurred as data
        while (reltg && reltg != handler) reltg = reltg.parentNode;

    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 1101, 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 1126, Column 53: there is no attribute "target"
    <a href="http://www.ciaoamigos.it/videochat" target="_parent">

    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 1146, Column 14: there is no attribute "align"
        <p align="justify">Si può comunicare online con leggerezza e con un pizzico…

    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 1265, Column 61: cannot generate system identifier for general entity "GT"
        <b class="see-all-link"><a  href="/forums">guarda tutti&GT;&GT;</a></b>

    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 1265, Column 61: general entity "GT" not defined and no default entity
        <b class="see-all-link"><a  href="/forums">guarda tutti&GT;&GT;</a></b>

    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 1265, Column 63: reference to entity "GT" for which no system identifier could be generated
        <b class="see-all-link"><a  href="/forums">guarda tutti&GT;&GT;</a></b>

    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 1265, Column 60: entity was defined here
        <b class="see-all-link"><a  href="/forums">guarda tutti&GT;&GT;</a></b>
  • Error Line 1265, Column 67: reference to entity "GT" for which no system identifier could be generated
        <b class="see-all-link"><a  href="/forums">guarda tutti&GT;&GT;</a></b>

    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 1265, Column 60: entity was defined here
        <b class="see-all-link"><a  href="/forums">guarda tutti&GT;&GT;</a></b>
  • Error Line 1272, Column 13: ID "activity-feed" already defined
        <ul id="activity-feed" class="feed">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 1185, Column 13: ID "activity-feed" first defined here
        <ul id="activity-feed" class="feed">
  • Error Line 1370, Column 60: reference to entity "GT" for which no system identifier could be generated
    <b class='see-all-link'><a  href="/youchat">guarda tutti&GT;&GT;</a></b>

    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 1265, Column 60: entity was defined here
        <b class="see-all-link"><a  href="/forums">guarda tutti&GT;&GT;</a></b>
  • Error Line 1370, Column 64: reference to entity "GT" for which no system identifier could be generated
    <b class='see-all-link'><a  href="/youchat">guarda tutti&GT;&GT;</a></b>

    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 1265, Column 60: entity was defined here
        <b class="see-all-link"><a  href="/forums">guarda tutti&GT;&GT;</a></b>
  • Error Line 1391, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    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 1391, Column 1: start tag was here
    <br>
  • Error Line 1393, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br>

    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 1393, Column 1: start tag was here
    <br><br>
  • Error Line 1393, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br>

    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 1393, Column 5: start tag was here
    <br><br>
  • Error Line 1410, Column 35: there is no attribute "enabled"
        <a  href="help/terms" enabled="1" class="menu_core_footer custom_238" order…

    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 1410, Column 81: there is no attribute "order"
    …s="menu_core_footer custom_238" order="1" uri="help/terms">Condizioni di utliz…

    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 1410, Column 89: there is no attribute "uri"
    …core_footer custom_238" order="1" uri="help/terms">Condizioni di utlizzo</a>  …

    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.

Visitor Analysis

Daily Visitor
  • 7.817 visits
Daily Visitor