Webcam chat live show avec des jeunes femmes sexy. Inscription gratuite pour voir les webcams live les plus sexy, avec des jeunes femmes, des couples ou des lesbiennes. ...

xlovecam.fr
  • Domain Name
    xlovecam.fr
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #39509
  • Page Size
    31.3 KB
  • Ip Address
    91.208.175.119
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    4 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
    XloveCam - webcam / sexcam live show gratuit
  • Meta Keyword
    gratuit, sexcam, live show, chat, jeunes femmes, sex, lesbiennes, live, sexy, webcam
  • Meta Description
    Webcam chat live show avec des jeunes femmes sexy. Inscription gratuite pour voir les webcams live les plus sexy, avec des jeunes femmes, des couples ou des lesbiennes.

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    91.208.175.119
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from xlovecam.fr.

HTML Analysis

  • date: Sat, 16 Feb 2013 02:57:22 GMT
  • server: Apache
  • 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
  • content-encoding: gzip
  • content-length: 9122
  • connection: close
  • content-type: text/html; charset=ISO-8859-1
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for xlovecam.fr

DNS Analysis


DNS servers
ns1.eurodns.com [80.92.65.2]
ns2.eurodns.com [80.92.89.242]


DNS Records

Answer records
xlovecam.fr MX
preference: 10
exchange: mail.xlovecam.fr
3600s
xlovecam.fr A 91.208.175.119 3600s
xlovecam.fr SOA
server: ns1.eurodns.com
email: hostmaster@eurodns.com
serial: 2011060802
refresh: 86400
retry: 7200
expire: 604800
minimum ttl: 86400
86400s
xlovecam.fr NS  ns2.eurodns.com 86400s
xlovecam.fr NS  ns1.eurodns.com 86400s

Authority records

Additional records

IP 91.208.175.119 Analysis

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 35 Errors
  • 7 Warnings
Ratio Text/Html
  • 0.308388183548055
Message Error
  • Error Line 1, Column 1556: there is no attribute "property"
    …content="Restricted" /><meta property="og:title" content="XloveCam - webcam / …

    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 1, Column 4379: cannot generate system identifier for general entity "v"
    …ttp://js.wlresources.com/min/?g=alljs&v=2" type="text/javascript"></script><sc…

    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 1, Column 4379: general entity "v" not defined and no default entity
    …ttp://js.wlresources.com/min/?g=alljs&v=2" type="text/javascript"></script><sc…

    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 1, Column 4380: reference not terminated by REFC delimiter
    …tp://js.wlresources.com/min/?g=alljs&v=2" type="text/javascript"></script><scr…

    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 1, Column 4380: reference to external entity in attribute value
    …tp://js.wlresources.com/min/?g=alljs&v=2" type="text/javascript"></script><scr…

    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 1, Column 4380: reference to entity "v" for which no system identifier could be generated
    …tp://js.wlresources.com/min/?g=alljs&v=2" type="text/javascript"></script><scr…

    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 1, Column 4378: entity was defined here
    …http://js.wlresources.com/min/?g=alljs&v=2" type="text/javascript"></script><s…
  • Error Line 3, Column 1660: an attribute value must be a literal unless it contains only name characters
    …== '' ){field.innerHTML = '<div class=\"no_flash_detect\">Pour pouvoir regarde…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 3, Column 1679: document type does not allow element "div" here
    …HTML = '<div class=\"no_flash_detect\">Pour pouvoir regarder les modèles en we…

    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 3, Column 1762: an attribute value must be a literal unless it contains only name characters
    …et naviguer sur notre  site, <a class=\"txt2b\" href=\"http:\/\/get.adobe.com\…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 3, Column 1777: an attribute value must be a literal unless it contains only name characters
    … notre  site, <a class=\"txt2b\" href=\"http:\/\/get.adobe.com\/fr\/flashplaye…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 3, Column 1830: there is no attribute "target"
    …adobe.com\/fr\/flashplayer\/\" target=\"_blank\">veuillez télécharger la derni…

    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 3, Column 1830: an attribute value must be a literal unless it contains only name characters
    …adobe.com\/fr\/flashplayer\/\" target=\"_blank\">veuillez télécharger la derni…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Warning Line 3, Column 1910: character "<" is the first character of a delimiter but occurred as data
    …e version du Plugin Adobe Flash Player<\/a>.<\/div>' ;}}}var timer = setTimeou…

    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 3, Column 1916: character "<" is the first character of a delimiter but occurred as data
    …ion du Plugin Adobe Flash Player<\/a>.<\/div>' ;}}}var timer = setTimeout(prin…

    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 3, Column 1987: end tag for "a" omitted, but OMITTAG NO was specified
    …ut(printGetFlashPlayer, 200) ;</script></div><div style="color:#CC9; font-size…

    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 3, Column 1753: start tag was here
    …n webcam et naviguer sur notre  site, <a class=\"txt2b\" href=\"http:\/\/get.a…
  • Error Line 3, Column 1987: end tag for "div" omitted, but OMITTAG NO was specified
    …ut(printGetFlashPlayer, 200) ;</script></div><div style="color:#CC9; font-size…

    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 3, Column 1649: start tag was here
    …(/\s/g,'') == '' ){field.innerHTML = '<div class=\"no_flash_detect\">Pour pouv…
  • Error Line 3, Column 21656: an attribute value must be a literal unless it contains only name characters
    …== '' ){field.innerHTML = '<div class=\"no_flash_detect\">Pour pouvoir regarde…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 3, Column 21675: document type does not allow element "div" here
    …HTML = '<div class=\"no_flash_detect\">Pour pouvoir regarder les modèles en we…

    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 3, Column 21758: an attribute value must be a literal unless it contains only name characters
    …et naviguer sur notre  site, <a class=\"txt2b\" href=\"http:\/\/get.adobe.com\…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 3, Column 21773: an attribute value must be a literal unless it contains only name characters
    … notre  site, <a class=\"txt2b\" href=\"http:\/\/get.adobe.com\/fr\/flashplaye…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 3, Column 21826: an attribute value must be a literal unless it contains only name characters
    …adobe.com\/fr\/flashplayer\/\" target=\"_blank\">veuillez télécharger la derni…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Warning Line 3, Column 21906: character "<" is the first character of a delimiter but occurred as data
    …e version du Plugin Adobe Flash Player<\/a>.<\/div>' ;}}}var timer = setTimeou…

    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 3, Column 21912: character "<" is the first character of a delimiter but occurred as data
    …ion du Plugin Adobe Flash Player<\/a>.<\/div>' ;}}}var timer = setTimeout(prin…

    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 3, Column 21983: end tag for "a" omitted, but OMITTAG NO was specified
    …ut(printGetFlashPlayer, 200) ;</script></div><div style="padding-top:7px; 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 3, Column 21749: start tag was here
    …n webcam et naviguer sur notre  site, <a class=\"txt2b\" href=\"http:\/\/get.a…
  • Error Line 3, Column 21983: end tag for "div" omitted, but OMITTAG NO was specified
    …ut(printGetFlashPlayer, 200) ;</script></div><div style="padding-top:7px; 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 3, Column 21645: start tag was here
    …(/\s/g,'') == '' ){field.innerHTML = '<div class=\"no_flash_detect\">Pour pouv…
  • Error Line 4, Column 914: document type does not allow element "div" here
    …"text/javascript">document.write('<div><a class=\"txt_bas\" href=\"sex-cam-liv…

    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 4, Column 924: an attribute value must be a literal unless it contains only name characters
    …script">document.write('<div><a class=\"txt_bas\" href=\"sex-cam-live-show-reg…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 4, Column 941: an attribute value must be a literal unless it contains only name characters
    …write('<div><a class=\"txt_bas\" href=\"sex-cam-live-show-regul2257-declaratio…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 4, Column 1077: an attribute value must be a literal unless it contains only name characters
    …-18-usc-2257.html?popup=true\" target=\"_blank\"> </a></div>'); </script><br /…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 4, Column 1261: document type does not allow element "br" here
    …r Internet avec ces programmes : <br /><a class=adminTxt target=\"_blank\" hre…

    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 4, Column 1271: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … avec ces programmes : <br /><a class=adminTxt target=\"_blank\" href=\"http:/…
  • Error Line 4, Column 1287: an attribute value must be a literal unless it contains only name characters
    …mmes : <br /><a class=adminTxt target=\"_blank\" href=\"http://www.netnanny.co…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 4, Column 1303: an attribute value must be a literal unless it contains only name characters
    …class=adminTxt target=\"_blank\" href=\"http://www.netnanny.com\">NetNanny</a>…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 4, Column 1330: document type does not allow element "a" here
    …ank\" href=\"http://www.netnanny.com\">NetNanny</a> - <a class=adminTxt target…

    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 4, Column 1355: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …etnanny.com\">NetNanny</a> - <a class=adminTxt target=\"_blank\" href=\"http:/…
  • Error Line 4, Column 1371: an attribute value must be a literal unless it contains only name characters
    …tNanny</a> - <a class=adminTxt target=\"_blank\" href=\"http://www.cyberpatrol…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 4, Column 1387: an attribute value must be a literal unless it contains only name characters
    …class=adminTxt target=\"_blank\" href=\"http://www.cyberpatrol.com\">CyberPatr…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 4, Column 1417: document type does not allow element "a" here
    …\" href=\"http://www.cyberpatrol.com\">CyberPatrol</a> - <a class=adminTxt tar…

    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 4, Column 1445: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …trol.com\">CyberPatrol</a> - <a class=adminTxt target=\"_blank\" href=\"http:/…
  • Error Line 4, Column 1461: an attribute value must be a literal unless it contains only name characters
    …Patrol</a> - <a class=adminTxt target=\"_blank\" href=\"http://www.solidoak.co…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 4, Column 1477: an attribute value must be a literal unless it contains only name characters
    …class=adminTxt target=\"_blank\" href=\"http://www.solidoak.com\">CyberSitter<…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 4, Column 1504: document type does not allow element "a" here
    …target=\"_blank\" href=\"http://www.solidoak.com\">CyberSitter</a>'); </script>

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

Visitor Analysis

Daily Visitor
  • 5.717 visits
Daily Visitor