mediadico.com

Dictionnaire de la langue française, de la langue anglaise : définitions, synonymes, conjugaison, traduction, expressions, citations ...

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

Overview Info

  • Domain Name
    mediadico.com
  • Favicon
  • Alexa Rank
    #27056
  • Google Page Rank
    PR 6
  • Ip Address
    158.255.103.22
  • Page Size
    55.5 KB
  • Images
    1 GIF, 14 JPG, 9 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 7 2 0 0 0

Website Meta Analysis



  • Title
    Dictionnaire MEDIADICO –Traduction, dictionnaires : définitions, synonymes, conjugaisons, expressions, francais, anglais
  • Meta Keyword
    dictionnaire, définition dictionnaire, définition, dictionnaire définition, définitions, dictionnaire dictionnaire, dictionnaire dictionnaire français, dictionnaire dictionnaire francais, dictionnaire dictionnaire en ligne, dictionnaire dictionnaire gratuit, dictionnaire dictionnaire langue, dictionnaire dictionnaire langue française, télécharger dictionnaire
  • Meta Description
    Dictionnaire de la langue française, de la langue anglaise : définitions, synonymes, conjugaison, traduction, expressions, citations

Technical Analysis



  • Webserver
    Microsoft-IIS/7.5
  • Ip Address
    158.255.103.22
  • Domain Age
    13 Years, 9 Months, 13 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • cache-control: private
  • content-type: text/html; charset=utf-8
  • server: Microsoft-IIS/7.5
  • x-aspnetmvc-version: 2.0
  • x-aspnet-version: 4.0.30319
  • x-powered-by: ASP.NET
  • date: Fri, 26 Jul 2013 16:44:22 GMT
  • vary: Accept-Encoding
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
domain: mediadico.com
reg_created: 1999-10-06 15:15:11
expires: 2013-10-06 15:15:11
created: 2009-10-30 17:05:18
changed: 2012-07-23 16:59:30
transfer-prohibited: yes
ns0: a.dns.gandi.net
ns1: b.dns.gandi.net
ns2: c.dns.gandi.net
owner-c:
nic-hdl: TR54-GANDI
owner-name: Infoduc
organisation: Infoduc
person: Toussaint ROZE
address: 1bis avenue de la République
zipcode: 75011
city: PARIS
country: France
phone: +33.144849510
fax: +33.147007199
email: email
lastupdated: 2012-07-13 11:16:39
admin-c:
nic-hdl: TR54-GANDI
owner-name: Infoduc
organisation: Infoduc
person: Toussaint ROZE
address: 1bis avenue de la République
zipcode: 75011
city: PARIS
country: France
phone: +33.144849510
fax: +33.147007199
email: email
lastupdated: 2012-07-13 11:16:39
tech-c:
nic-hdl: TR54-GANDI
owner-name: Infoduc
organisation: Infoduc
person: Toussaint ROZE
address: 1bis avenue de la République
zipcode: 75011
city: PARIS
country: France
phone: +33.144849510
fax: +33.147007199
email: email
lastupdated: 2012-07-13 11:16:39
bill-c:
nic-hdl: TR54-GANDI
owner-name: Infoduc
organisation: Infoduc
person: Toussaint ROZE
address: 1bis avenue de la République
zipcode: 75011
city: PARIS
country: France
phone: +33.144849510
fax: +33.147007199
email: email
lastupdated: 2012-07-13 11:16:39

DNS Analysis


DNS servers
a.dns.gandi.net [173.246.97.2]
b.dns.gandi.net [217.70.184.40]
c.dns.gandi.net [217.70.182.20]


DNS Records

Answer records
mediadico.com NS  c.dns.gandi.net 10800s
mediadico.com NS  b.dns.gandi.net 10800s
mediadico.com NS  a.dns.gandi.net 10800s
mediadico.com MX
preference: 10
exchange: spool.mail.gandi.net
10800s
mediadico.com MX
preference: 50
exchange: fb.mail.gandi.net
10800s
mediadico.com A 158.255.103.22 300s
mediadico.com SOA
server: a.dns.gandi.net
email: hostmaster@gandi.net
serial: 1358902805
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 10800
10800s

Authority records

Additional records

IP 158.255.103.22 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    NA
  • Continent Code
    38° North
  • Latitude
    97.
  • Longitude
  • No whois ip data for 158.255.103.22

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 99 Errors
  • 24 Warnings
Ratio Text/Html
  • 0.6259406428018848
Message Error
  • Error Line 3, Column 1: Missing xmlns attribute for element html. The value should be: http://www.w3.org/1999/xhtml
    <html>

    Many Document Types based on XML need a mandatory xmlns attribute on the root element. For example, the root element for XHTML might look like:
    <html xmlns="http://www.w3.org/1999/xhtml">

  • Error Line 27, Column 24: there is no attribute "property"
            <meta property="fb:app_id" content="230479493662567" />

    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 60, Column 99: "async" is not a member of a group specified for any attribute
    …' src='http://media.notrefamille.com/javascript/nf.js?20091116' async></script>
  • Error Line 61, Column 93: "async" is not a member of a group specified for any attribute
    …script' src='http://media.notrefamille.com/javascript/flash.js' async></script>
  • Error Line 66, Column 75: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …pt type="text/javascript" src="/Content/Scripts/facebox.min.js" defer></script>

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Error Line 68, Column 90: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …avascript" src="/Content/Scripts/jquery.ui.autocomplete.min.js" defer></script>

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Error Line 69, Column 85: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …ext/javascript" src="/Content/Scripts/mediadico20111109.min.js" defer></script>

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Error Line 81, Column 90: there is no attribute "border"
    …rc="/images/environnement/notrefamille/nav/home.jpg" alt="Homepage" border="0">

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 81, Column 94: end tag for "img" omitted, but OMITTAG NO was specified
    …rc="/images/environnement/notrefamille/nav/home.jpg" alt="Homepage" border="0">

    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 81, Column 9: start tag was here
            <img src="/images/environnement/notrefamille/nav/home.jpg" alt="Homepag…
  • Warning Line 97, Column 53: character "&" is the first character of a delimiter but occurred as data
          <a href="http://beaute.notrefamille.com">Mode & Beauté</a>

    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 140, Column 12: element "header" undefined
        <header>

    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 143, Column 124: end tag for "img" omitted, but OMITTAG NO was specified
    …trefamille/nav/logo-dico.jpg" alt="Mediadico avec Notrefamille.com" border="0">

    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 143, Column 11: start tag was here
              <img src="/images/environnement/notrefamille/nav/logo-dico.jpg" alt="…
  • Error Line 147, Column 77: there is no attribute "placeholder"
    …rm-text placeholder dico" placeholder="monmail@gmail.com" size="35" id="edit-s…

    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 152, Column 18: there is no attribute "class"
          <nav class="menu01 on">

    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 152, Column 29: element "nav" undefined
          <nav class="menu01 on">

    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 379, Column 98: character "&" is the first character of a delimiter but occurred as data
    …notrefamille.com/v2/services-villes-villages/default.asp">Villes & Villages</a>

    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 514, Column 36: document type does not allow element "span" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
            <span class="txt-recherche">

    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 515, Column 27: value of attribute "for" must be a single token
                <label for="Je cherche">Je cherche une définition :</label>

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 518, Column 58: 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="text" id="mot" name="mot" value="" />

    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 519, Column 95: 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
    …d="btn-recherche" class="btn-recherche" type="submit" name="" value="Trouver"/>

    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 536, Column 27: end tag for "br" omitted, but OMITTAG NO was specified
            Encore plus de<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 536, Column 23: start tag was here
            Encore plus de<br>
  • Error Line 539, Column 86: there is no attribute "alt"
    …<a href="/mots-croises/mots-meles/jeux-lettres.asp" alt="Mots-Mêlés">Mots-Mêlés

    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 762, Column 21: document type does not allow element "ul" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <ul class="partager">

    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 764, Column 35: there is no attribute "target"
        <li class="twitter"><a target="_blank" href="http://twitthis.com/twit?url=h…

    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 787, Column 21: document type does not allow element "ul" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <ul class="partager">

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

  • Warning Line 918, Column 40: S separator in comment declaration
        <script type="text/javascript"><!--

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Warning Line 919, Column 1: S separator in comment declaration
            google_ad_client = "ca-pub-7952851555421315";

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Warning Line 919, Column 2: S separator in comment declaration
            google_ad_client = "ca-pub-7952851555421315";

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Warning Line 919, Column 3: S separator in comment declaration
            google_ad_client = "ca-pub-7952851555421315";

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Warning Line 919, Column 4: S separator in comment declaration
            google_ad_client = "ca-pub-7952851555421315";

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Warning Line 919, Column 5: S separator in comment declaration
            google_ad_client = "ca-pub-7952851555421315";

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Warning Line 919, Column 6: S separator in comment declaration
            google_ad_client = "ca-pub-7952851555421315";

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Warning Line 919, Column 7: S separator in comment declaration
            google_ad_client = "ca-pub-7952851555421315";

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Warning Line 919, Column 8: S separator in comment declaration
            google_ad_client = "ca-pub-7952851555421315";

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Error Line 919, Column 9: invalid comment declaration: found name start character outside comment but inside comment declaration
            google_ad_client = "ca-pub-7952851555421315";
  • Info Line 916, Column 1: comment declaration started here
    <!--
  • Error Line 924, Column 13: end tag for element "script" which is not open
        </script>

    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 941, Column 38: document type does not allow element "div" here
    <div style="margin: 0px; padding: 0;">

    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 942, Column 18: there is no attribute "language"
    <script language="JavaScript" type="text/javascript">

    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 951, Column 28: an attribute value must be a literal unless it contains only name characters
                s += '<a class=\"googleAdSenseTitle\"  href=\"' + google_info.feedb…

    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 951, Column 57: an attribute value must be a literal unless it contains only name characters
    …<a class=\"googleAdSenseTitle\"  href=\"' + google_info.feedback_url + '\" sty…

    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 951, Column 61: character "+" not allowed in attribute specification list
    …lass=\"googleAdSenseTitle\"  href=\"' + google_info.feedback_url + '\" style=\…
  • Error Line 951, Column 61: document type does not allow element "a" here
    …lass=\"googleAdSenseTitle\"  href=\"' + google_info.feedback_url + '\" style=\…

    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 951, Column 138: document type does not allow element "br" here
    … google_info.feedback_url + '\" style=\"color:000000\">Ads By Google </a><br>';

    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 951, Column 139: end tag for "br" omitted, but OMITTAG NO was specified
    … google_info.feedback_url + '\" style=\"color:000000\">Ads By Google </a><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 951, Column 135: start tag was here
    … google_info.feedback_url + '\" style=\"color:000000\">Ads By Google </a><br>';
  • Error Line 955, Column 48: document type does not allow element "div" here
                    s += '<div id="google-afc-zone">';

    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 956, Column 32: an attribute value must be a literal unless it contains only name characters
                    s += '<a class=\"googleAdSenseTitle\"  href=\"' + google_info.f…

    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 956, Column 61: an attribute value must be a literal unless it contains only name characters
    …<a class=\"googleAdSenseTitle\"  href=\"' + google_info.feedback_url + '\" sty…

    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 956, Column 65: character "+" not allowed in attribute specification list
    …lass=\"googleAdSenseTitle\"  href=\"' + google_info.feedback_url + '\" style=\…
  • Error Line 956, Column 143: end tag for "br" omitted, but OMITTAG NO was specified
    … google_info.feedback_url + '\" style=\"color:000000\">Ads By Google </a><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 956, Column 139: start tag was here
    … google_info.feedback_url + '\" style=\"color:000000\">Ads By Google </a><br>';
  • Warning Line 957, Column 31: character "<" is the first character of a delimiter but occurred as data
                    for (i = 0; i < google_ads.length; ++i) {

    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 995, Column 22: end tag for "script" omitted, but OMITTAG NO was specified
                    </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 929, Column 5: start tag was here
        <script type="text/javascript"><!--
  • Error Line 1005, Column 101: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …artadserver.com/call/pubjumpi/9483/91021/4208/S/[timestamp]/?" target="_blank">

    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 1019, Column 180: end tag for "img" omitted, but OMITTAG NO was specified
    …: The Amazing Spider-Man" title="Frissons : The Amazing Spider-Man" border="0">

    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 1019, Column 5: start tag was here
    				<img src="http://media.notrefamille.com/images/cms/videos-ext/210x139/11116…
  • Error Line 1026, Column 368: end tag for "img" omitted, but OMITTAG NO was specified
    … très mécontent saccage un magasin T-Mobile" border="0"><span>&nbsp;</span></a>

    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 1026, Column 134: start tag was here
    …in-t-mobile-v111161.html" class="img"><img src="http://media.notrefamille.com/…
  • Error Line 1028, Column 225: end tag for "img" omitted, but OMITTAG NO was specified
    …oir-video-m.png" alt="" border="0"></a></p><div class="separation">&nbsp;</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 1028, Column 135: start tag was here
    …n-t-mobile-v111161.html" class="lien"><img src="/images/environnement/notrefam…
  • Error Line 1031, Column 311: end tag for "img" omitted, but OMITTAG NO was specified
    …s" title="Un ourson s'échappe de son enclos" border="0"><span>&nbsp;</span></a>

    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 1031, Column 115: start tag was here
    …-son-enclos-v111142.html" class="img"><img src="http://media.notrefamille.com/…
  • Error Line 1033, Column 206: end tag for "img" omitted, but OMITTAG NO was specified
    …oir-video-m.png" alt="" border="0"></a></p><div class="separation">&nbsp;</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 1033, Column 116: start tag was here
    …son-enclos-v111142.html" class="lien"><img src="/images/environnement/notrefam…
  • Error Line 1036, Column 350: end tag for "img" omitted, but OMITTAG NO was specified
    …l'or, l'argent et le bronze mis en lieu sûr" border="0"><span>&nbsp;</span></a>

    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 1036, Column 124: start tag was here
    …en-lieu-sur-v111148.html" class="img"><img src="http://media.notrefamille.com/…
  • Error Line 1038, Column 215: end tag for "img" omitted, but OMITTAG NO was specified
    …oir-video-m.png" alt="" border="0"></a></p><div class="separation">&nbsp;</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 1038, Column 125: start tag was here
    …n-lieu-sur-v111148.html" class="lien"><img src="/images/environnement/notrefam…
  • Error Line 1044, Column 341: end tag for "img" omitted, but OMITTAG NO was specified
    …L'urinoir parlant contre l'alcool au volant" border="0"><span>&nbsp;</span></a>

    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 1044, Column 125: start tag was here
    …l-au-volant-v111159.html" class="img"><img src="http://media.notrefamille.com/…
  • Error Line 1046, Column 244: end tag for "img" omitted, but OMITTAG NO was specified
    …oir-video-m.png" alt="" border="0"></a></p><div class="separation">&nbsp;</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 1046, Column 125: start tag was here
    …-au-volant-v111159.html" class="lien"><img src="http://media.notrefamille.com/…
  • Error Line 1049, Column 329: end tag for "img" omitted, but OMITTAG NO was specified
    …e="Un best-seller annoncé pour J.K. Rowling" border="0"><span>&nbsp;</span></a>

    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 1049, Column 119: start tag was here
    …-jk-rowling-v111166.html" class="img"><img src="http://media.notrefamille.com/…
  • Error Line 1051, Column 238: end tag for "img" omitted, but OMITTAG NO was specified
    …oir-video-m.png" alt="" border="0"></a></p><div class="separation">&nbsp;</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 1051, Column 119: start tag was here
    …jk-rowling-v111166.html" class="lien"><img src="http://media.notrefamille.com/…
  • Error Line 1054, Column 252: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …alt="Les Espagnols toujours "Campeones"" title="Les Espagnols toujours "Campeo…

    Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".

  • Error Line 1054, Column 253: end tag for "img" omitted, but OMITTAG NO was specified
    …lt="Les Espagnols toujours "Campeones"" title="Les Espagnols toujours "Campeon…

    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 1054, Column 111: start tag was here
    …s-campeones-v111147.html" class="img"><img src="http://media.notrefamille.com/…
  • Error Line 1056, Column 230: end tag for "img" omitted, but OMITTAG NO was specified
    …oir-video-m.png" alt="" border="0"></a></p><div class="separation">&nbsp;</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 1056, Column 111: start tag was here
    …-campeones-v111147.html" class="lien"><img src="http://media.notrefamille.com/…
  • Error Line 1059, Column 325: end tag for "img" omitted, but OMITTAG NO was specified
    …tle="La statue de la Liberté entre au musée" border="0"><span>&nbsp;</span></a>

    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 1059, Column 119: start tag was here
    …re-au-musee-v111153.html" class="img"><img src="http://media.notrefamille.com/…
  • Error Line 1061, Column 238: end tag for "img" omitted, but OMITTAG NO was specified
    …oir-video-m.png" alt="" border="0"></a></p><div class="separation">&nbsp;</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 1061, Column 119: start tag was here
    …e-au-musee-v111153.html" class="lien"><img src="http://media.notrefamille.com/…
  • Error Line 1064, Column 302: end tag for "img" omitted, but OMITTAG NO was specified
    …..." title="Une braqueuse très souriante..." border="0"><span>&nbsp;</span></a>

    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 1064, Column 110: start tag was here
    …s-souriante-v111144.html" class="img"><img src="http://media.notrefamille.com/…
  • Error Line 1066, Column 229: end tag for "img" omitted, but OMITTAG NO was specified
    …oir-video-m.png" alt="" border="0"></a></p><div class="separation">&nbsp;</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 1066, Column 110: start tag was here
    …-souriante-v111144.html" class="lien"><img src="http://media.notrefamille.com/…
  • Error Line 1072, Column 8: 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 1088, Column 13: there is no attribute "src"
    <iframe src="http://www.facebook.com/plugins/likebox.php?href=http%3A%2F%2Fwww.…

    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 1089, Column 15: there is no attribute "scrolling"
        scrolling="no" frameborder="0" style="border: none; overflow: hidden; width…

    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 1089, Column 32: there is no attribute "frameborder"
        scrolling="no" frameborder="0" style="border: none; overflow: hidden; width…

    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 1089, Column 42: there is no attribute "style"
    … scrolling="no" frameborder="0" style="border: none; overflow: hidden; width: …

    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 1089, Column 122: there is no attribute "allowtransparency"
    … none; overflow: hidden; width: 300px; height: 62px;" allowtransparency="true">

    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 1089, Column 128: element "iframe" undefined
    … none; overflow: hidden; width: 300px; height: 62px;" allowtransparency="true">

    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 1100, Column 8: 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 1164, Column 16: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
            target=_blank>
  • Error Line 1165, Column 158: end tag for "img" omitted, but OMITTAG NO was specified
    …ttp://www.mediadico.com/Content/Images/300x250-mediadico-iphone.jpg"></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 1165, Column 9: start tag was here
            <img border="0" alt="dictionnaire iPhone" width="300px" height="250px" …
  • Error Line 1198, Column 54: there is no attribute "iconurl"
    …nclick="return install(event);" iconurl="http://www.mediadico.com/favicon.ico">

    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 1243, Column 13: there is no attribute "SRC"
    <IFRAME SRC="http://optimized-by.rubiconproject.com/a/8552/13848/27851-15.html?…

    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 1243, Column 94: there is no attribute "FRAMEBORDER"
    …552/13848/27851-15.html?" FRAMEBORDER="0" MARGINWIDTH="0" MARGINHEIGHT="0" SCR…

    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 1243, Column 110: there is no attribute "MARGINWIDTH"
    …15.html?" FRAMEBORDER="0" MARGINWIDTH="0" MARGINHEIGHT="0" SCROLLING="NO" WIDT…

    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 1243, Column 127: there is no attribute "MARGINHEIGHT"
    …RDER="0" MARGINWIDTH="0" MARGINHEIGHT="0" SCROLLING="NO" WIDTH="300" HEIGHT="2…

    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 1243, Column 141: there is no attribute "SCROLLING"
    …GINWIDTH="0" MARGINHEIGHT="0" SCROLLING="NO" WIDTH="300" HEIGHT="250"></IFRAME>

    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 1243, Column 152: there is no attribute "WIDTH"
    …GINWIDTH="0" MARGINHEIGHT="0" SCROLLING="NO" WIDTH="300" HEIGHT="250"></IFRAME>

    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 1243, Column 165: there is no attribute "HEIGHT"
    …GINWIDTH="0" MARGINHEIGHT="0" SCROLLING="NO" WIDTH="300" HEIGHT="250"></IFRAME>

    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 1243, Column 170: element "IFRAME" undefined
    …GINWIDTH="0" MARGINHEIGHT="0" SCROLLING="NO" WIDTH="300" HEIGHT="250"></IFRAME>

    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 1244, Column 4: element "BR" undefined
    <BR><BR>

    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 1244, Column 8: element "BR" undefined
    <BR><BR>

    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 1245, Column 4: element "BR" undefined
    <BR>

    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 1258, Column 22: end tag for "BR" omitted, but OMITTAG NO was specified
                    </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 1245, Column 1: start tag was here
    <BR>
  • Error Line 1258, Column 22: end tag for "BR" omitted, but OMITTAG NO was specified
                    </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 1244, Column 5: start tag was here
    <BR><BR>
  • Error Line 1258, Column 22: end tag for "BR" omitted, but OMITTAG NO was specified
                    </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 1244, Column 1: start tag was here
    <BR><BR>
  • Error Line 1269, Column 174: element "IFRAME" undefined
    …RGINWIDTH="0" MARGINHEIGHT="0" SCROLLING="NO" WIDTH="728" HEIGHT="90"></IFRAME>

    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 1368, Column 50: character "&" is the first character of a delimiter but occurred as data
                                    Langue française &<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.
  • Error Line 1425, Column 109: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …artadserver.com/call/pubjumpi/9483/91021/4200/S/[timestamp]/?" target="_blank">

    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 1435, Column 93: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …f="http://www.smartadserver.com/call/pubjumpi/9483/91021/5423/S/[timestamp]/?">

    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 1448, Column 113: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …artadserver.com/call/pubjumpi/9483/91021/4198/S/[timestamp]/?" target="_blank">

    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 1452, Column 73: required attribute "type" not specified
    … <script src="http://www.smartadserver.com/iframeout/iframeout.js?v2"></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 1473, Column 34: required attribute "type" not specified
        <script language="JavaScript">

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 1476, Column 70: required attribute "type" not specified
        <script language="JavaScript" src="http://w.estat.com/js/whap.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 1477, Column 34: required attribute "type" not specified
        <script language="JavaScript">

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Warning Line 1485, Column 70: cannot generate system identifier for general entity "v"
    …http://prof.estat.com/m/web/800000207026?type=whap&v=0.01" border="0" width="1"

    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 1485, Column 70: general entity "v" not defined and no default entity
    …http://prof.estat.com/m/web/800000207026?type=whap&v=0.01" border="0" width="1"

    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 1485, Column 71: reference not terminated by REFC delimiter
    …http://prof.estat.com/m/web/800000207026?type=whap&v=0.01" border="0" width="1"

    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 1485, Column 71: reference to external entity in attribute value
    …http://prof.estat.com/m/web/800000207026?type=whap&v=0.01" border="0" width="1"

    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 1485, Column 71: reference to entity "v" for which no system identifier could be generated
    …http://prof.estat.com/m/web/800000207026?type=whap&v=0.01" border="0" width="1"

    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 1485, Column 69: entity was defined here
    …http://prof.estat.com/m/web/800000207026?type=whap&v=0.01" border="0" width="1"
  • Error Line 1486, Column 25: required attribute "alt" not specified
                height="1" />

    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 1486, Column 25: document type does not allow element "img" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "address", "fieldset", "ins", "del" start-tag
                height="1" />

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

  • Warning Line 515, Column 28: reference to non-existent ID "cherche"
                <label for="Je cherche">Je cherche une définition :</label>

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

  • Warning Line 515, Column 25: reference to non-existent ID "Je"
                <label for="Je cherche">Je cherche une définition :</label>

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

Visitor Analysis

Daily Visitor
  • 5.367 visits

In Page Analysis