Série spéciale : Profitez de 3 options offertes pendant 3 ans sur votre assurance tous risques (assistance, panne 0km, véhicule de remplacement, bagages et effets transportés). Réalisez votre devis gratuit assurances auto, moto, ...

maaf.fr
  • Domain Name
    maaf.fr
  • Favicon
  • Google Page Rank
    6
  • Alexa Rank
    #50900
  • Page Size
    27.4 KB
  • Ip Address
    212.234.93.158
  • Heading
    H1: 1, H2: 4, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 5 PNG

Website Meta Analysis

  • Title
    MAAF Assurances : mutuelle assurance auto moto habitation santé – Devis assurance en ligne
  • Meta Keyword
    Assurances, assurances en ligne, MAF, MAFF
  • Meta Description
    Série spéciale : Profitez de 3 options offertes pendant 3 ans sur votre assurance tous risques (assistance, panne 0km, véhicule de remplacement, bagages et effets transportés). Réalisez votre devis gratuit assurances auto, moto, habitation, santé, vie... Souscrivez votre assurance en ligne, en agence, au téléphone.

Technical Analysis

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

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

HTML Analysis

  • date: Fri, 01 Mar 2013 15:16:05 GMT
  • x-jcms-ajax-id: AjaxCtxt-0-1362150963065
  • content-encoding: gzip
  • vary: Accept-Encoding
  • content-type: text/html;charset=UTF-8
  • content-length: 8279
  • age: 135
  • x-google-cache-control: remote-cache-hit
  • via: HTTP/1.1 GWA (remote cache hit)
%%
%% This is the AFNIC Whois server.
%%
%% complete date format : DD/MM/YYYY
%% short date format : DD/MM
%% version : FRNIC-2.5
%%
%% Rights restricted by copyright.
%% See http://www.afnic.fr/afnic/web/mentions-legales-whois_en
%%
%% Use '-h' option to obtain more information about this service.
%%
%% [8.22.201.32 REQUEST] >> maaf.fr
%%
%% RL Net [##########] - RL IP [#########.]
%%

domain: maaf.fr
status: ACTIVE
hold: NO
holder-c: M6900-FRNIC
admin-c: DJ1033-FRNIC
tech-c: VD1435-FRNIC
tech-c: HMA1-FRNIC
zone-c: NFC1-FRNIC
nsl-id: NSL8652-FRNIC
registrar: MELBOURNE IT LIMITED
anniversary: 26/01
created: 20/05/1996
last-update: 27/05/2009
source: FRNIC

ns-list: NSL8652-FRNIC
nserver: m007400.maaf.fr [195.6.162.3]
nserver: a4.nstld.com
nserver: f4.nstld.com
source: FRNIC

registrar: MELBOURNE IT LIMITED
type: Isp Option 1
address: Level 2
address: 120 King St
address: 3000 MELBOURNE, VICTORIA
country: AU
phone: +61 3 8624 2300
fax-no: +61 3 8624 2499
e-mail: email
website: http://www.melbourneit.com.au
anonymous: NO
registered: 16/03/2007
source: FRNIC

nic-hdl: VD1435-FRNIC
type: ROLE
contact: Verisign DBMS
address: Verisign
address: 487 E. Middlefield Rd
address: Mailstop MV3-1-2
address: 94043 Mountain View, Ca
country: US
phone: +1 8005792848
fax-no: +1 6506182574
e-mail: email
admin-c: VS96-FRNIC
tech-c: DT58-FRNIC
changed: 27/05/2009 email
anonymous: NO
obsoleted: NO
source: FRNIC

nic-hdl: DJ1033-FRNIC
type: PERSON
contact: Direction Juridique
address: MAAF ASSURANCES
address: Chaban-De-Chauray
address: 79036 Niort Cedex 9
country: FR
phone: +33 5 49 34 35 36
fax-no: +33 5 49 34 39 92
e-mail: email
changed: 27/05/2009 email
anonymous: NO
obsoleted: NO
source: FRNIC

nic-hdl: M6900-FRNIC
type: ORGANIZATION
contact: MAAF ASSURANCES
address: Chaban de Chauray
address: 79036 Niort
country: FR
phone: +33 5 49 34 35 36
fax-no: +33 5 49 34 39 92
e-mail: email
changed: 20/09/2010 email
anonymous: NO
obsoleted: NO
eligstatus: ok
eligdate: 20/09/2010 15:34:40
source: FRNIC

nic-hdl: HMA1-FRNIC
type: PERSON
contact: Hostmaster Maaf Assurances
address: MAAF ASSURANCES
address: Chaban-De-Chauray
address: 79036 Niort Cedex 9
country: FR
phone: +33 5 49 34 31 72
fax-no: +33 5 49 34 90 90
e-mail: email
changed: 27/05/2009 email
anonymous: NO
obsoleted: NO
source: FRNIC

DNS Analysis


DNS servers
a4.nstld.com [69.36.158.33]
m007400.maaf.fr [195.6.162.3]
f4.nstld.com [192.35.51.33]


DNS Records

Answer records
maaf.fr SOA
server: m007400.maaf.fr
email: postmaster@maaf.fr
serial: 2000100716
refresh: 3600
retry: 1200
expire: 1296000
minimum ttl: 900
3600s
maaf.fr NS  a4.nstld.com 3600s
maaf.fr NS  m007400.maaf.fr 3600s
maaf.fr NS  f4.nstld.com 3600s
maaf.fr A 212.234.93.158 3600s
maaf.fr MX
preference: 50
exchange: m007300.maaf.fr
3600s
maaf.fr MX
preference: 10
exchange: m004100.maaf.fr
3600s

Authority records

Additional records
m007400.maaf.fr A 195.6.162.3 3600s
m007300.maaf.fr A 195.6.162.2 3600s
m004100.maaf.fr A 212.234.93.144 3600s

IP 212.234.93.158 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 42 Errors
  • 3 Warnings
Ratio Text/Html
  • 0.5526137859862639
Message Error
  • Error Line 22, Column 53: document type does not allow element "script" here; assuming missing "head" start-tag
    …ge="javascript" type="text/javascript">var dRecRequest=new Date();var tRecRequ…
  • Error Line 23, Column 6: document type does not allow element "head" here
    <head>

    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 69, Column 6: document type does not allow element "body" here
    <body>

    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 377, Column 83: required attribute "alt" not specified
    …mg src="home/20130301-abcdtesting/1B1/images/maaf-ass-solo.png" usemap="#Map"/>

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

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

  • Error Line 379, Column 84: required attribute "alt" not specified
    …rea shape="rect" coords="0,0,500,135" href="fr/c_6312/devis-auto-particulier"/>

    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 398, Column 20: there is no attribute "data-onglet"
    		<div data-onglet="1" class="onglet1">&nbsp;</div>

    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 440, Column 73: required attribute "alt" not specified
    			<img src="home/20130301-abcdtesting/1B1/images/maaf-ass+credit.png" />

    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 449, Column 74: required attribute "alt" not specified
    			<img src="home/20130301-abcdtesting/1B1/images/maaf-moisepargne.png" />

    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 533, Column 27: document type does not allow element "strong" here
            "offline":"<strong>Par tchat</strong><br/>Nos conseillers tchat sont ac…

    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 533, Column 50: document type does not allow element "br" here
    …fline":"<strong>Par tchat</strong><br/>Nos conseillers tchat sont actuellement…

    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 533, Column 116: an attribute value must be a literal unless it contains only name characters
    …actuellement occup&eacute;s.<br style=\"margin-bottom:9px;\"/><span>Vous pouve…

    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 533, Column 139: document type does not allow element "br" here
    …te;s.<br style=\"margin-bottom:9px;\"/><span>Vous pouvez nous contacter par t&…

    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 533, Column 140: end tag for "br" omitted, but OMITTAG NO was specified
    …e;s.<br style=\"margin-bottom:9px;\"/><span>Vous pouvez nous contacter par t&e…

    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 533, Column 106: start tag was here
    …chat sont actuellement occup&eacute;s.<br style=\"margin-bottom:9px;\"/><span>…
  • Error Line 533, Column 145: document type does not allow element "span" here
    …br style=\"margin-bottom:9px;\"/><span>Vous pouvez nous contacter par t&eacute…

    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 534, Column 24: document type does not allow element "strong" here
            "busy":"<strong>Par tchat</strong><br/>Nos conseillers tchat sont actue…

    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 534, Column 47: document type does not allow element "br" here
    …"busy":"<strong>Par tchat</strong><br/>Nos conseillers tchat sont actuellement…

    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 534, Column 113: an attribute value must be a literal unless it contains only name characters
    …actuellement occup&eacute;s.<br style=\"margin-bottom:9px;\"/><span>Vous pouve…

    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 534, Column 136: document type does not allow element "br" here
    …te;s.<br style=\"margin-bottom:9px;\"/><span>Vous pouvez nous contacter par t&…

    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 534, Column 137: end tag for "br" omitted, but OMITTAG NO was specified
    …e;s.<br style=\"margin-bottom:9px;\"/><span>Vous pouvez nous contacter par t&e…

    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 534, Column 103: start tag was here
    …chat sont actuellement occup&eacute;s.<br style=\"margin-bottom:9px;\"/><span>…
  • Error Line 534, Column 142: document type does not allow element "span" here
    …br style=\"margin-bottom:9px;\"/><span>Vous pouvez nous contacter par t&eacute…

    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 535, Column 26: document type does not allow element "strong" here
            "online":"<strong>Par tchat</strong><br/>Discutez en direct avec un con…

    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 535, Column 49: document type does not allow element "br" here
    …nline":"<strong>Par tchat</strong><br/>Discutez en direct avec un conseiller p…

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Warning Line 570, Column 96: reference not terminated by REFC delimiter
    …c.iadvize.com/chat_init.js?sid=37&lang=fr' type='text/javascript'%3E%3C/script…

    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.

  • Error Line 611, Column 11: end tag for "span" omitted, but OMITTAG NO was specified
    							</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 609, Column 9: start tag was here
    								<span class="services_description">
  • Error Line 667, Column 56: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    				<span class="facebook" >&nbsp;<p id="frameFacebook"></p></span>						

    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 729, Column 193: document type does not allow element "iframe" here
    … a + '?" width="1" height="1" frameborder="0" style="display:none"></iframe>');

    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 821, Column 33: an attribute value must be a literal unless it contains only name characters
    		var fbIframeHtml="<iframe src=\"http://www.facebook.com/plugins/likebox.php?h…

    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 821, Column 265: an attribute value must be a literal unless it contains only name characters
    …eader=false&amp;height=68\" scrolling=\"no\" frameborder=\"0\" allowTransparen…

    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 821, Column 265: character "\" is not allowed in the value of attribute "scrolling"
    …eader=false&amp;height=68\" scrolling=\"no\" frameborder=\"0\" allowTransparen…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 821, Column 265: value of attribute "scrolling" cannot be "\"no\""; must be one of "yes", "no", "auto"
    …eader=false&amp;height=68\" scrolling=\"no\" frameborder=\"0\" allowTransparen…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 821, Column 284: an attribute value must be a literal unless it contains only name characters
    …ght=68\" scrolling=\"no\" frameborder=\"0\" allowTransparency=\"false\" id=\"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 821, Column 284: character "\" is not allowed in the value of attribute "frameborder"
    …ght=68\" scrolling=\"no\" frameborder=\"0\" allowTransparency=\"false\" id=\"f…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 821, Column 284: value of attribute "frameborder" cannot be "\"0\""; must be one of "1", "0"
    …ght=68\" scrolling=\"no\" frameborder=\"0\" allowTransparency=\"false\" id=\"f…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 821, Column 308: there is no attribute "allowTransparency"
    …" frameborder=\"0\" allowTransparency=\"false\" id=\"fbFace\" class=\"fb face\…

    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 821, Column 308: an attribute value must be a literal unless it contains only name characters
    …" frameborder=\"0\" allowTransparency=\"false\" id=\"fbFace\" class=\"fb face\…

    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 821, Column 321: an attribute value must be a literal unless it contains only name characters
    …r=\"0\" allowTransparency=\"false\" id=\"fbFace\" class=\"fb face\"></iframe>";

    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 821, Column 321: character "\" is not allowed in the value of attribute "id"
    …r=\"0\" allowTransparency=\"false\" id=\"fbFace\" class=\"fb face\"></iframe>";

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 821, Column 338: an attribute value must be a literal unless it contains only name characters
    …r=\"0\" allowTransparency=\"false\" id=\"fbFace\" class=\"fb face\"></iframe>";

    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 821, Column 347: "face" is not a member of a group specified for any attribute
    …r=\"0\" allowTransparency=\"false\" id=\"fbFace\" class=\"fb face\"></iframe>";
  • Error Line 821, Column 349: document type does not allow element "iframe" here
    …r=\"0\" allowTransparency=\"false\" id=\"fbFace\" class=\"fb face\"></iframe>";

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Warning Line 838, Column 172: character "&" is the first character of a delimiter but occurred as data
    …Load(){var ret=true;if(onloadFunctions&&(onloadFunctions instanceof Function))…

    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 838, Column 173: character "&" is the first character of a delimiter but occurred as data
    …oad(){var ret=true;if(onloadFunctions&&(onloadFunctions instanceof Function)){…

    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 840, Column 7: "head" not finished but containing element ended
    </html>
  • Error Line 840, Column 7: end tag for "head" omitted, but OMITTAG NO was specified
    </html>

    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 22, Column 1: start tag was here
    <script language="javascript" type="text/javascript">var dRecRequest=new Date()…
  • Error Line 840, Column 7: end tag for "html" which is not finished
    </html>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

Visitor Analysis

Daily Visitor
  • 3.150 visits
Daily Visitor