amfam.com

Shop Online and Save on Auto Insurance, Life Insurance, Homeowners Insurance, Business Insurance and Retirement Savings Plans ...

Display Widget for this domain on your website. Click Here
This data was last updated from 20-02-2013 11:36:09  (update).

Overview Info

  • Domain Name
    amfam.com
  • Favicon
  • Alexa Rank
    #50611
  • Google Page Rank
    PR 6
  • Ip Address
    204.29.134.64
  • Page Size
    75.8 KB
  • Images
    5 GIF, 12 JPG, 9 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 6 6 12 0 0

Website Meta Analysis



  • Title
    Auto Insurance, Car Insurance, Life, Homeowners & More | American Family Insurance
  • Meta Keyword
    auto insurance, car insurance, life insurance, homeowners insurance, business insurance, annuities
  • Meta Description
    Shop Online and Save on Auto Insurance, Life Insurance, Homeowners Insurance, Business Insurance and Retirement Savings Plans

Technical Analysis



  • Webserver
    Microsoft-IIS/7.0
  • Ip Address
    204.29.134.64
  • Domain Age
    18 Years, 11 Months, 3 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • cache-control: private
  • content-length: 81874
  • content-type: text/html
  • server: Microsoft-IIS/7.0
  • x-powered-by: ASP.NET
  • date: Wed, 20 Feb 2013 11:36:09 GMT
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for amfam.com

DNS Analysis


DNS servers
cbru.br.ns.els-gms.att.net [199.191.128.105]
cmtu.mt.ns.els-gms.att.net [12.127.16.69]
nsmr1.amfam.com [204.29.134.131]


DNS Records

Answer records
amfam.com A 204.29.134.64 900s
amfam.com TXT v=spf1 mx ~all 43200s
amfam.com MX
preference: 15
exchange: gmr.amfam.com
300s
amfam.com MX
preference: 15
exchange: nmr.amfam.com
300s
amfam.com SOA
server: NSMR1.amfam.com
email: postmaster@amfam.com
serial: 2013020416
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 43200
43200s
amfam.com NS  NSMR1.amfam.com 604800s
amfam.com NS  cbru.br.ns.els-gms.att.net 604800s
amfam.com NS  cmtu.mt.ns.els-gms.att.net 604800s

Authority records

Additional records
gmr.amfam.com A 165.200.128.135 604800s
nmr.amfam.com A 204.29.134.135 604800s
NSMR1.amfam.com A 204.29.134.131 28800s

IP 204.29.134.64 Analysis

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

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 138 Errors
  • 24 Warnings
Ratio Text/Html
  • 0.6539636307398864
Message Error
  • Error Line 48, Column 41: there is no attribute "language"
    <script type="text/javascript" language="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 48, Column 53: document type does not allow element "script" here; assuming missing "body" start-tag
    <script type="text/javascript" language="javascript">
  • Error Line 52, Column 96: document type does not allow element "link" here
    …heet" charset="utf-8" href="homepages/css/home-carousel.css" type="text/css" />

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

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

  • Error Line 58, Column 16: document type does not allow element "body" here
    <body id="home">

    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 64, Column 62: required attribute "type" not specified
    <script language="JavaScript" src="/site-assets/js/s_code.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 90, Column 7: required attribute "type" not specified
    <style>

    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 90, Column 7: document type does not allow element "style" here
    <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).

  • Warning Line 117, Column 16: character "<" is the first character of a delimiter but occurred as data
    		if(cookieend < cookiebegin) { cookieend = document.cookie.length; }

    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 142, Column 47: document type does not allow element "div" here
    	msg_en = msg_en + "<div class='system_notice'>"

    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 148, Column 47: document type does not allow element "div" here
    	msg_es = msg_es + "<div class='system_notice'>"

    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 164, Column 22: character "&" is the first character of a delimiter but occurred as data
    	if ((cDate > sDate) && (cDate < eDate)) {

    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 164, Column 23: character "&" is the first character of a delimiter but occurred as data
    	if ((cDate > sDate) && (cDate < eDate)) {

    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 164, Column 32: character "<" is the first character of a delimiter but occurred as data
    	if ((cDate > sDate) && (cDate < eDate)) {

    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 280, Column 34: document type does not allow element "div" here; assuming missing "li" start-tag
            <div id="myAccountFlyout"> 
  • Error Line 285, Column 113: there is no attribute "autocomplete"
    …m.com/siteminderagent/forms/myacct_login.fcc" method="post" autocomplete="OFF">

    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 292, Column 36: value of attribute "type" cannot be "PASSWORD"; must be one of "text", "password", "checkbox", "radio", "submit", "reset", "file", "hidden", "image", "button"
                  <input type="PASSWORD" id="textFieldPWD"  name="PASSWORD" size="1…

    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 292, Column 210: there is no attribute "width"
    …ite-assets/img/btns/log_in.gif" width="80" height="26" title="Login to My Acco…

    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 292, Column 222: there is no attribute "height"
    …mg/btns/log_in.gif" width="80" height="26" title="Login to My Account" />&nbsp…

    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 292, Column 505: there is no attribute "target"
    …age/understand-my-account.asp" target="_blank"><img src="http://www.amfam.com/…

    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 292, Column 599: required attribute "alt" not specified
    …ttp://www.amfam.com/site-assets/img/btns/faq.png" width="80" height="26" /></a>

    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 300, Column 66: 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="hidden" name="SMENC" value="ISO-8859-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>").

  • Error Line 301, 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="hidden" name="SMLOCALE" value="US-EN"/>

    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 302, Column 86: 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="hidden" name="target" value="https://my.amfam.com/MyAccount/home"/>

    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 306, Column 30: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
             <li class="closeBtn"><a href="#" title="close">Close</a></li>

    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 307, Column 11: end tag for "div" omitted, but OMITTAG NO was specified
          </ul>

    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 280, Column 9: start tag was here
            <div id="myAccountFlyout"> 
  • Error Line 307, Column 11: end tag for "li" omitted, but OMITTAG NO was specified
          </ul>

    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 280, Column 9: start tag was here
            <div id="myAccountFlyout"> 
  • Error Line 422, Column 34: "mporgnav" is not a member of a group specified for any attribute
        <li class="last"><a mporgnav href="http://www.amfamlatino.com/enes/" 
  • Error Line 435, Column 82: there is no attribute "target"
    …ction="http://Search3.amfam.com/search" target="_blank" accept-charset="utf-8">

    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 483, Column 30: 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 501, Column 41: invalid comment declaration: found name character outside comment but inside comment declaration
      <!-- homepage body content goes here--->
  • Info Line 501, Column 3: comment declaration started here
      <!-- homepage body content goes here--->
  • Error Line 558, Column 35: document type does not allow element "style" here
    <style type="text/css" media="all">

    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 577, Column 34: value of attribute "method" cannot be "GET"; must be one of "get", "post"
                    <form method="GET" action="http://www.amfam.com/get-a-quote/aut…

    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 577, Column 120: there is no attribute "name"
    …w.amfam.com/get-a-quote/auto-quote-launch.asp" id="zipStamps" name="zipStamps">

    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 578, Column 48: 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="hidden" name="tid" value="bn116" />

    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 579, Column 55: document type does not allow element "label" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …                  <label id="getAutoQ" for="zipCode">Get an Auto Quote:</label>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 582, Column 78: 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="hidden" value="en" id="autoLang" name="lang">

    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 582, Column 79: end tag for "input" omitted, but OMITTAG NO was specified
                        <input type="hidden" value="en" id="autoLang" name="lang">

    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 582, Column 21: start tag was here
                        <input type="hidden" value="en" id="autoLang" name="lang">
  • Error Line 585, Column 150: duplicate specification of attribute "title"
    …lue="ZIP Code" title="ZIP Code" class="inputText lightText" title="ZIP Code" />

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 585, Column 162: 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
    …lue="ZIP Code" title="ZIP Code" class="inputText lightText" title="ZIP Code" />

    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 587, Column 93: 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="image" src="/homepages/images/btn_go2.png" id="goAutoLLD" />

    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 624, Column 75: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …                       <option value="auto" class="auto" selected>Auto</option>

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

  • Warning Line 633, Column 59: character "&" is the first character of a delimiter but occurred as data
                                    <option value="farm">Farm & Ranch</option>

    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 638, Column 116: value of attribute "method" cannot be "GET"; must be one of "get", "post"
    …o" action="get-a-quote/auto-quote-launch.asp" method="GET" class="active">     

    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 639, Column 71: 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="hidden" name="tid" value="ss10" />

    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 642, Column 62: ID "autoLang" already defined
    …                    <input type="hidden" name="lang" id="autoLang" value="en"/>

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

  • Info Line 582, Column 57: ID "autoLang" first defined here
                        <input type="hidden" value="en" id="autoLang" name="lang">
  • Error Line 642, Column 83: 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="hidden" name="lang" id="autoLang" value="en"/>

    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 654, Column 107: value of attribute "method" cannot be "GET"; must be one of "get", "post"
    …e="zipStamps" id="quoteRent" action="get-a-quote/add-session.asp" method="GET">

    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 657, Column 81: 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="hidden" name="lang"id="pieLang" value="en"/>

    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 673, Column 69: 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="hidden" name="lang" value="en"/>

    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 720, Column 78: 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="hidden" name="SMENC" value="ISO-8859-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>").

  • Error Line 721, Column 76: 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="hidden" name="SMLOCALE" value="US-EN"/>

    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 722, Column 113: 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
    …e="hidden" name="target" value="https://my.amfam.com/MyAccount/home?tid=ss15"/>

    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 733, Column 75: 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="hidden" name="tid" value="ss17" />

    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 734, Column 84: 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="hidden" name="action" value="searchByName">

    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 734, Column 85: end tag for "input" omitted, but OMITTAG NO was specified
    …                       <input type="hidden" name="action" value="searchByName">

    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 734, Column 29: start tag was here
                                <input type="hidden" name="action" value="searchByN…
  • Error Line 735, Column 96: 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="hidden" name="fbrowserCompatible" value="searchByName">

    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 735, Column 97: end tag for "input" omitted, but OMITTAG NO was specified
    …           <input type="hidden" name="fbrowserCompatible" value="searchByName">

    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 735, Column 29: start tag was here
                                <input type="hidden" name="fbrowserCompatible" valu…
  • Error Line 736, Column 73: 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="hidden" name="lang" value="en"/>

    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 782, Column 45: ID "go" already defined
                                    <button id="go">Go</button>

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

  • Info Line 678, Column 41: ID "go" first defined here
                                <button id="go">Go</button>
  • Error Line 790, Column 80: 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="hidden" value="en" name="sideBarLang"/>

    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 796, Column 54: value of attribute "type" cannot be "TEXT"; must be one of "text", "password", "checkbox", "radio", "submit", "reset", "file", "hidden", "image", "button"
    …                     <input type="TEXT" name="zipcode" id="zipcode" size="16" …

    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 837, Column 122: value of attribute "method" cannot be "POST"; must be one of "get", "post"
    …/pmcwb/processPayment.do" method="POST" target="PayNow" onsubmit="return popup…

    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 838, Column 75: 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="hidden" name="paymentMethod" value="CWB"/>

    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 839, Column 74: 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="hidden" name="method" value="setUpPage"/>

    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 848, Column 24: end tag for element "p" which is not open
                        </p>

    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 855, Column 96: required attribute "alt" not specified
    …"/homepages/images/img_autoQuote.png" /><span>Get an Auto Quote</span></a></li>

    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 856, Column 100: required attribute "alt" not specified
    …es/images/img_dreamcamp2013-phase2.png" /><span>2013 Dream Camp</span></a></li>

    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 857, Column 92: required attribute "alt" not specified
    …homepages/images/img_commercial.png" /><span>Business Insurance</span></a></li…

    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 858, Column 93: required attribute "alt" not specified
    …mepages/images/img_farmandranch.png" /><span>Farm & Ranch Insurance</span></a>…

    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 858, Column 105: character "&" is the first character of a delimiter but occurred as data
    …ges/images/img_farmandranch.png" /><span>Farm & Ranch Insurance</span></a></li>

    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 859, Column 95: required attribute "alt" not specified
    …mg src="/homepages/images/img_dreampage.png" /><span>Your Dream</span></a></li>

    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 908, Column 77: document type does not allow element "h4" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ng-center/my-home/dream-vault.asp"><h4>Take Stock of Your Dreams</h4></a><div …

    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 911, Column 47: required attribute "alt" not specified
    …="/homepage-news/dreamvault-logo.jpg"/></li><li class="news_item"><a href="/pr…

    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 911, Column 122: document type does not allow element "h4" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …/products/insurance-discounts.asp"><h4>Are You Saving All You Can?</h4></a><di…

    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 914, Column 46: required attribute "alt" not specified
    …c="/homepage-news/discounts-home.jpg"/></li><li class="news_item"><a href="/ab…

    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 914, Column 154: document type does not allow element "h4" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ustomer-testimonials.asp?tid=fp36"><h4>Your Story is Our Story</h4></a><div cl…

    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 917, Column 49: required attribute "alt" not specified
    …/homepage-news/cust-testimonials.jpg"/></li></ul><ul id="tool" class="newsBloc…

    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 918, Column 70: document type does not allow element "h4" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …/products/insurance-discounts.asp"><h4>Are You Saving All You Can?</h4></a><di…

    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 921, Column 46: required attribute "alt" not specified
    …c="/homepage-news/discounts-home.jpg"/></li><!--mp_trans_remove_start --><li c…

    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 921, Column 167: document type does not allow element "h4" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …my-money/annuities-calculator.asp"><h4>Try Our Annuities Calculator</h4></a><d…

    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 924, Column 50: required attribute "alt" not specified
    …images/annuities_calculator_home.jpg"/></li><!--mp_trans_remove_end --><!--mp_…

    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 924, Column 197: cannot generate system identifier for general entity "LS"
    …ferences.com/amfam/SignUp.aspx?LANG=E&LS=AFH2"class="iframe" ><h4>Sign up for …

    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 924, Column 197: general entity "LS" not defined and no default entity
    …ferences.com/amfam/SignUp.aspx?LANG=E&LS=AFH2"class="iframe" ><h4>Sign up for …

    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 924, Column 199: reference not terminated by REFC delimiter
    …rences.com/amfam/SignUp.aspx?LANG=E&LS=AFH2"class="iframe" ><h4>Sign up for Ou…

    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 924, Column 199: reference to external entity in attribute value
    …rences.com/amfam/SignUp.aspx?LANG=E&LS=AFH2"class="iframe" ><h4>Sign up for Ou…

    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 924, Column 199: reference to entity "LS" for which no system identifier could be generated
    …rences.com/amfam/SignUp.aspx?LANG=E&LS=AFH2"class="iframe" ><h4>Sign up for Ou…

    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 924, Column 196: entity was defined here
    …eferences.com/amfam/SignUp.aspx?LANG=E&LS=AFH2"class="iframe" ><h4>Sign up for…
  • Error Line 924, Column 224: document type does not allow element "h4" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …spx?LANG=E&LS=AFH2"class="iframe" ><h4>Sign up for Our E-Newsletter</h4></a><d…

    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 926, Column 66: reference not terminated by REFC delimiter
    …rences.com/amfam/SignUp.aspx?LANG=E&LS=AFH2" class="news_button iframe">Regist…

    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 926, Column 66: reference to external entity in attribute value
    …rences.com/amfam/SignUp.aspx?LANG=E&LS=AFH2" class="news_button iframe">Regist…

    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 926, Column 66: reference to entity "LS" for which no system identifier could be generated
    …rences.com/amfam/SignUp.aspx?LANG=E&LS=AFH2" class="news_button iframe">Regist…

    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 924, Column 196: entity was defined here
    …eferences.com/amfam/SignUp.aspx?LANG=E&LS=AFH2"class="iframe" ><h4>Sign up for…
  • Error Line 927, Column 44: required attribute "alt" not specified
    …src="/homepage-news/@dvisor-home.jpg"/></li><!--mp_trans_remove_end --><!--mp_…

    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 930, Column 117: document type does not allow element "h4" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ref="/microsites/landlordtoolbox/"><h4>Landlord Toolbox</h4></a><div class="co…

    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 933, Column 48: required attribute "alt" not specified
    …"/homepage-news/landlord-toolbox.jpg"/></li><!--mp_trans_remove_start --><li c…

    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 933, Column 170: document type does not allow element "h4" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …y-money/life-needs-calculator.asp"><h4>Life Insurance Needs Calculator</h4></a…

    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 936, Column 47: required attribute "alt" not specified
    …="/homepage-news/life-needs-calc.jpg"/></li><!--mp_trans_remove_end --><li cla…

    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 936, Column 177: document type does not allow element "h4" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …/business-accelerator-program.asp"><h4>Turbo-Charge Your Business</h4></a><div…

    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 939, Column 48: required attribute "alt" not specified
    …"/homepage-news/Accelerator-home.jpg"/></li></ul><ul id="product" class="newsB…

    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 940, Column 70: document type does not allow element "h4" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …/products/insurance-discounts.asp"><h4>Are You Saving All You Can?</h4></a><di…

    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 943, Column 46: required attribute "alt" not specified
    …c="/homepage-news/discounts-home.jpg"/></li><li class="news_item"><a href="/mi…

    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 943, Column 128: document type does not allow element "h4" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ites/teen-safe-driver/default.asp"><h4>Teen Safe Driver Program</h4></a><div c…

    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 946, Column 40: required attribute "alt" not specified
    …img src="/images/teen-safe-drive.jpg"/></li><li class="news_item"><a href="/pr…

    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 946, Column 127: document type does not allow element "h4" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …me/renters-insurance.asp?tid=fp19"><h4>Renters Insurance</h4></a><div class="c…

    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 949, Column 39: required attribute "alt" not specified
    <img src="/homepage-news/renters.jpg"/></li></ul>

    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 963, Column 10: element "NOSCRIPT" undefined
    <NOSCRIPT>

    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 964, Column 10: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <img src=https://cb.adbureau.net/TrackAction/ADVID=14/DESTINATION1=1 width=1 he…
  • Error Line 964, Column 17: NET-enabling start-tag not immediately followed by null end-tag
    <img src=https://cb.adbureau.net/TrackAction/ADVID=14/DESTINATION1=1 width=1 he…

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

  • Error Line 964, Column 17: required attribute "alt" not specified
    <img src=https://cb.adbureau.net/TrackAction/ADVID=14/DESTINATION1=1 width=1 he…

    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 964, Column 17: end tag for "img" omitted, but OMITTAG NO was specified
    <img src=https://cb.adbureau.net/TrackAction/ADVID=14/DESTINATION1=1 width=1 he…

    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 964, Column 1: start tag was here
    <img src=https://cb.adbureau.net/TrackAction/ADVID=14/DESTINATION1=1 width=1 he…
  • Warning Line 969, Column 5: S separator in comment declaration
    <!-- DoubleClick Information Start -->

    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 969, Column 6: invalid comment declaration: found name start character outside comment but inside comment declaration
    <!-- DoubleClick Information Start -->
  • Info Line 967, Column 1: comment declaration started here
    <!--mp_trans_add<NOSCRIPT>
  • Error Line 971, Column 18: there is no attribute "language"
    <SCRIPT language="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 971, Column 30: element "SCRIPT" undefined
    <SCRIPT language="JavaScript">

    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 974, Column 30: there is no attribute "SRC"
        document.write('<IMG SRC="http://ad.doubleclick.net/activity;src=1800773;ty…

    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 974, Column 132: there is no attribute "WIDTH"
    …3;type=homep956;cat=amfam525;ord=1;num='+ a + '?" WIDTH=1 HEIGHT=1 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 974, Column 132: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …3;type=homep956;cat=amfam525;ord=1;num='+ a + '?" WIDTH=1 HEIGHT=1 BORDER=0>');
  • Error Line 974, Column 141: there is no attribute "HEIGHT"
    …3;type=homep956;cat=amfam525;ord=1;num='+ a + '?" WIDTH=1 HEIGHT=1 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 974, Column 141: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …3;type=homep956;cat=amfam525;ord=1;num='+ a + '?" WIDTH=1 HEIGHT=1 BORDER=0>');
  • Error Line 974, Column 150: there is no attribute "BORDER"
    …3;type=homep956;cat=amfam525;ord=1;num='+ a + '?" WIDTH=1 HEIGHT=1 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 974, Column 150: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …3;type=homep956;cat=amfam525;ord=1;num='+ a + '?" WIDTH=1 HEIGHT=1 BORDER=0>');
  • Error Line 974, Column 151: element "IMG" undefined
    …3;type=homep956;cat=amfam525;ord=1;num='+ a + '?" WIDTH=1 HEIGHT=1 BORDER=0>');

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 975, Column 13: end tag for "IMG" omitted, but OMITTAG NO was specified
        </SCRIPT>

    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 974, Column 21: start tag was here
        document.write('<IMG SRC="http://ad.doubleclick.net/activity;src=1800773;ty…
  • Error Line 976, Column 10: element "NOSCRIPT" undefined
    <NOSCRIPT>

    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 977, Column 105: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …src=1800773;type=homep956;cat=amfam525;ord=1;num=1?" WIDTH=1 HEIGHT=1 BORDER=0>
  • Error Line 977, Column 114: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …src=1800773;type=homep956;cat=amfam525;ord=1;num=1?" WIDTH=1 HEIGHT=1 BORDER=0>
  • Error Line 977, Column 123: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …src=1800773;type=homep956;cat=amfam525;ord=1;num=1?" WIDTH=1 HEIGHT=1 BORDER=0>
  • Error Line 977, Column 124: element "IMG" undefined
    …src=1800773;type=homep956;cat=amfam525;ord=1;num=1?" WIDTH=1 HEIGHT=1 BORDER=0>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 978, Column 11: end tag for "IMG" omitted, but OMITTAG NO was specified
    </NOSCRIPT>

    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 977, Column 1: start tag was here
    <IMG SRC="http://ad.doubleclick.net/activity;src=1800773;type=homep956;cat=amfa…
  • Warning Line 1141, Column 78: reference not terminated by REFC delimiter
    …rences.com/amfam/SignUp.aspx?LANG=E&LS=AFH1" target="_blank" class="iframe">E-…

    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 1141, Column 78: reference to external entity in attribute value
    …rences.com/amfam/SignUp.aspx?LANG=E&LS=AFH1" target="_blank" class="iframe">E-…

    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 1141, Column 78: reference to entity "LS" for which no system identifier could be generated
    …rences.com/amfam/SignUp.aspx?LANG=E&LS=AFH1" target="_blank" class="iframe">E-…

    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 924, Column 196: entity was defined here
    …eferences.com/amfam/SignUp.aspx?LANG=E&LS=AFH2"class="iframe" ><h4>Sign up for…
  • Error Line 1159, Column 123: there is no attribute "align"
    …g src="/images/facebook_small.gif" align="left" />&nbsp;&nbsp;Facebook</a></li>

    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 1159, Column 131: required attribute "alt" not specified
    …g src="/images/facebook_small.gif" align="left" />&nbsp;&nbsp;Facebook</a></li>

    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 1170, Column 128: required attribute "alt" not specified
    …img src="/images/twitter_small.gif" align="left" />&nbsp;&nbsp;Twitter</a></li>

    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 1180, Column 162: required attribute "alt" not specified
    … src="/images/LinkedIn_Logo16px.png" align="left">&nbsp;&nbsp;Linkedin</a></li>

    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 1180, Column 163: end tag for "img" omitted, but OMITTAG NO was specified
    … src="/images/LinkedIn_Logo16px.png" align="left">&nbsp;&nbsp;Linkedin</a></li>

    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 1180, Column 109: start tag was here
    …nce" target="_blank" class="external"><img src="/images/LinkedIn_Logo16px.png"…
  • Error Line 1190, Column 122: required attribute "alt" not specified
    …nal"><img src="/images/youTube.gif" align="left" />&nbsp;&nbsp;YouTube</a></li>

    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 1200, Column 138: required attribute "alt" not specified
    …src="/images/pinterest_small.png" align="left" />&nbsp;&nbsp;Pinterest</a></li>

    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 1210, Column 147: required attribute "alt" not specified
    …al"><img src="/images/gplus-16.png" align="left" />&nbsp;&nbsp;Google+</a></li>

    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 1225, Column 126: there is no attribute "rel"
    ….amfam.com/site_files/js/getverisignsealimage.js" rel="nofollow"></script></li>

    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 1225, Column 136: required attribute "type" not specified
    ….amfam.com/site_files/js/getverisignsealimage.js" rel="nofollow"></script></li>

    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 1251, Column 30: 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 1322, Column 28: cannot generate system identifier for general entity "_RM_HTML_url_"
                    B3_url = "&_RM_HTML_url_="+escape(document.referrer);

    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 1322, Column 28: general entity "_RM_HTML_url_" not defined and no default entity
                    B3_url = "&_RM_HTML_url_="+escape(document.referrer);

    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 1322, Column 41: reference not terminated by REFC delimiter
                    B3_url = "&_RM_HTML_url_="+escape(document.referrer);

    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 1322, Column 41: reference to entity "_RM_HTML_url_" for which no system identifier could be generated
                    B3_url = "&_RM_HTML_url_="+escape(document.referrer);

    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 1322, Column 27: entity was defined here
                    B3_url = "&_RM_HTML_url_="+escape(document.referrer);
  • Warning Line 1324, Column 41: reference not terminated by REFC delimiter
                    B3_url = "&_RM_HTML_url_="+escape(document.location);

    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 1324, Column 41: reference to entity "_RM_HTML_url_" for which no system identifier could be generated
                    B3_url = "&_RM_HTML_url_="+escape(document.location);

    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 1322, Column 27: entity was defined here
                    B3_url = "&_RM_HTML_url_="+escape(document.referrer);
  • Warning Line 1325, Column 29: cannot generate system identifier for general entity "_RM_HTML_title_"
                    B3_url += "&_RM_HTML_title_="+escape(parent.document.title);

    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 1325, Column 29: general entity "_RM_HTML_title_" not defined and no default entity
                    B3_url += "&_RM_HTML_title_="+escape(parent.document.title);

    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 1325, Column 44: reference not terminated by REFC delimiter
                    B3_url += "&_RM_HTML_title_="+escape(parent.document.title);

    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 1325, Column 44: reference to entity "_RM_HTML_title_" for which no system identifier could be generated
                    B3_url += "&_RM_HTML_title_="+escape(parent.document.title);

    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 1325, Column 28: entity was defined here
                    B3_url += "&_RM_HTML_title_="+escape(parent.document.title);
  • Warning Line 1326, Column 29: cannot generate system identifier for general entity "_RM_HTML_referer_"
                    B3_url += "&_RM_HTML_referer_="+escape(parent.document.referrer…

    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 1326, Column 29: general entity "_RM_HTML_referer_" not defined and no default entity
                    B3_url += "&_RM_HTML_referer_="+escape(parent.document.referrer…

    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 1326, Column 46: reference not terminated by REFC delimiter
    …              B3_url += "&_RM_HTML_referer_="+escape(parent.document.referrer);

    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 1326, Column 46: reference to entity "_RM_HTML_referer_" for which no system identifier could be generated
    …              B3_url += "&_RM_HTML_referer_="+escape(parent.document.referrer);

    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 1326, Column 28: entity was defined here
                    B3_url += "&_RM_HTML_referer_="+escape(parent.document.referrer…
  • Error Line 1338, Column 146: required attribute "alt" not specified
    …http://servedby.flashtalking.com/spot/1012;3688;421/?DARTAmFamHomePage"/></div>

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

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

  • Error Line 1349, Column 78: document type does not allow element "link" here
    <link rel="stylesheet" type="text/css" href="/onlineopinionV5/oo_style.css" />

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

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

  • Error Line 1354, Column 11: character data is not allowed here
    <noscript>This JavaScript enables OnlineOpinion, a method for collecting secure…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 1361, Column 7: end tag for "body" 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 48, Column 1: start tag was here
    <script type="text/javascript" language="javascript">

Visitor Analysis

Daily Visitor
  • 3.150 visits
Daily Visitor

In Page Analysis