Buy and Sell cars, properties, gadgets, clothes and more. Find great deals near you or Post your ad for Free at AyosDito.ph ...

ayosdito.ph
  • Domain Name
    ayosdito.ph
  • Favicon
  • Google Page Rank
    6
  • Alexa Rank
    #7581
  • Page Size
    35.1 KB
  • Ip Address
    125.5.107.107
  • Heading
    H1: 1, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    11 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
    Buy and Sell in the Philippines - AyosDito.ph
  • Meta Keyword
    ayosdito, buy, sell, for sale, classifieds, free classifieds, property for sale, property, cars, cars for sale, mobile phones, computers, music, movies, books, hobby, collectables, sports, jobs, services, pets, home, garden, clothes, watches, electronics, children
  • Meta Description
    Buy and Sell cars, properties, gadgets, clothes and more. Find great deals near you or Post your ad for Free at AyosDito.ph

Technical Analysis

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

Hyper Text Transfer Protocol (HTTP) header show data header response from ayosdito.ph.

HTML Analysis

  • server: nginx
  • date: Thu, 18 Jul 2013 18:42:27 GMT
  • content-type: text/html; charset=ISO-8859-1
  • content-length: 8531
  • connection: keep-alive
  • vary: Accept-Encoding,User-Agent
  • content-encoding: gzip
  • p3p: CP='NOI DSP COR PSAo PSDo'
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for ayosdito.ph

DNS Analysis


DNS servers
ns2.ipmirror.com
adns1.ipmirror.com
ns1.ipmirror.com


DNS Records

Answer records
ayosdito.ph SOA
server: ns2.ipmirror.com
email: support@ipmirror.com
serial: 1037104107
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 10800
300s
ayosdito.ph TXT google-site-verification=N3_2V9ejpTFgOCuxBrWkv4S2G9lh4ODyJl4VRgFo4XU 10800s
ayosdito.ph MX
preference: 20
exchange: ASPMX2.GOOGLEMAIL.com
10800s
ayosdito.ph MX
preference: 20
exchange: ASPMX3.GOOGLEMAIL.com
10800s
ayosdito.ph MX
preference: 11
exchange: ASPMX.L.GOOGLE.com
10800s
ayosdito.ph MX
preference: 15
exchange: ALT1.ASPMX.L.GOOGLE.com
10800s
ayosdito.ph MX
preference: 15
exchange: ALT2.ASPMX.L.GOOGLE.com
10800s
ayosdito.ph A 125.5.107.107 10800s
ayosdito.ph NS  ns1.ipmirror.com 300s
ayosdito.ph NS  ns2.ipmirror.com 300s
ayosdito.ph NS  adns1.ipmirror.com 300s

Authority records

Additional records
ns1.ipmirror.com A 202.172.170.44 60s
ns2.ipmirror.com A 203.100.62.35 60s
adns1.ipmirror.com A 194.0.2.5 300s
adns1.ipmirror.com 28 [16 bytes] 300s

IP 125.5.107.107 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 71 Errors
  • 37 Warnings
Ratio Text/Html
  • 0.8753684444691618
Message Error
  • Error Line 1, Column 592: end tag for "meta" omitted, but OMITTAG NO was specified
    …e best deal among 195896 ads online!"><meta name="keywords" content="ayosdito,…

    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 1, Column 367: start tag was here
    …v="X-UA-Compatible" content="IE=9" /> <meta name="description" content="Buy an…
  • Error Line 1, Column 889: end tag for "meta" omitted, but OMITTAG NO was specified
    …thes, watches, electronics, children"> <meta property="fb:admins" content="100…

    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 1, Column 592: start tag was here
    …e best deal among 195896 ads online!"><meta name="keywords" content="ayosdito,…
  • Error Line 1, Column 905: there is no attribute "property"
    …lectronics, children"> <meta property="fb:admins" content="100000343536744" />…

    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 1, Column 1173: end tag for "meta" omitted, but OMITTAG NO was specified
    …e best deal among 195896 ads online!"> <meta property="og:title" content="Buy …

    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 1, Column 945: start tag was here
    …b:admins" content="100000343536744" /><meta name="og:description" content="Buy…
  • Error Line 1, Column 1256: end tag for "meta" omitted, but OMITTAG NO was specified
    …ell in the Philippines - AyosDito.ph"> <meta property="og:type" content="websi…

    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 1, Column 1174: start tag was here
    … best deal among 195896 ads online!"> <meta property="og:title" content="Buy a…
  • Error Line 1, Column 1300: end tag for "meta" omitted, but OMITTAG NO was specified
    … property="og:type" content="website"> <meta property="og:image" content="http…

    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 1, Column 1257: start tag was here
    …ll in the Philippines - AyosDito.ph"> <meta property="og:type" content="websit…
  • Error Line 1, Column 1385: end tag for "meta" omitted, but OMITTAG NO was specified
    …ayosdito.ph/img/ayosdito_og_icon.jpg"> <meta property="fb:app_id" content="183…

    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 1, Column 1301: start tag was here
    …property="og:type" content="website"> <meta property="og:image" content="http:…
  • Error Line 1, Column 1439: end tag for "meta" omitted, but OMITTAG NO was specified
    …"fb:app_id" content="183764338334178"> <meta property="og:site_name" content="…

    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 1, Column 1386: start tag was here
    …yosdito.ph/img/ayosdito_og_icon.jpg"> <meta property="fb:app_id" content="1837…
  • Error Line 1, Column 1492: end tag for "meta" omitted, but OMITTAG NO was specified
    …="og:site_name" content="ayosdito.ph"> <meta property="og:url" content="http:/…

    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 1, Column 1440: start tag was here
    …fb:app_id" content="183764338334178"> <meta property="og:site_name" content="a…
  • Error Line 1, Column 1632: end tag for "link" omitted, but OMITTAG NO was specified
    …145" rel="stylesheet" type="text/css">    <link rel="shortcut icon" href="/img…

    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 1, Column 1553: start tag was here
    …" content="http://www.ayosdito.ph" /> <link href="/css/ayosdito_index_min.css?…
  • Error Line 1, Column 1706: end tag for "link" omitted, but OMITTAG NO was specified
    …/img/favicon.ico" type="image/x-icon">  <link href="https://plus.google.com/10…

    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 1, Column 1636: start tag was here
    … rel="stylesheet" type="text/css">    <link rel="shortcut icon" href="/img/fav…
  • Error Line 1, Column 2213: end tag for "br" omitted, but OMITTAG NO was specified
    …/a>    </div>       <br class="clear"> <div class="idx-header"> <h1 id="index_…

    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 1, Column 2195: start tag was here
    …>f</label></span></a>    </div>       <br class="clear"> <div class="idx-heade…
  • Warning Line 1, Column 2455: cannot generate system identifier for general entity "url"
    …www.ayosdito.ph/redir?s=icon_insertad&url=http://www2.ayosdito.ph/ai" onclick=…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 1, Column 2455: general entity "url" not defined and no default entity
    …www.ayosdito.ph/redir?s=icon_insertad&url=http://www2.ayosdito.ph/ai" onclick=…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 1, Column 2458: reference not terminated by REFC delimiter
    ….ayosdito.ph/redir?s=icon_insertad&url=http://www2.ayosdito.ph/ai" onclick="re…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 1, Column 2458: reference to external entity in attribute value
    ….ayosdito.ph/redir?s=icon_insertad&url=http://www2.ayosdito.ph/ai" onclick="re…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 1, Column 2458: reference to entity "url" for which no system identifier could be generated
    ….ayosdito.ph/redir?s=icon_insertad&url=http://www2.ayosdito.ph/ai" onclick="re…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 1, Column 2454: entity was defined here
    …/www.ayosdito.ph/redir?s=icon_insertad&url=http://www2.ayosdito.ph/ai" onclick…
  • Error Line 1, Column 2682: end tag for "br" omitted, but OMITTAG NO was specified
    …d</a> </div> </div> <br class="clear"> <div class="intro_text">  <p>Out of <a …

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1, Column 2664: start tag was here
    …item you don't need</a> </div> </div> <br class="clear"> <div class="intro_tex…
  • Error Line 99, Column 21: end tag for "br" omitted, but OMITTAG NO was specified
      <br class="clear"> <div class="testimonial">  Sobra-sobrang ayos! Salamat ng …

    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 99, Column 3: start tag was here
      <br class="clear"> <div class="testimonial">  Sobra-sobrang ayos! Salamat ng …
  • Error Line 99, Column 317: end tag for "br" omitted, but OMITTAG NO was specified
    …C.</strong>  </div> <br class="clear">  </div> <div id="ph_map" class="sprite_…

    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 99, Column 299: start tag was here
    …/><strong>- BRYAN C.</strong>  </div> <br class="clear">  </div> <div id="ph_m…
  • Error Line 99, Column 448: required attribute "alt" not specified
    …light_area" src="/img/transparent.gif"> <img id="area_map" src="/img/transpare…

    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 99, Column 449: end tag for "img" omitted, but OMITTAG NO was specified
    …ight_area" src="/img/transparent.gif"> <img id="area_map" src="/img/transparen…

    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 99, Column 397: start tag was here
    …p_philippines"> <div id="area_image"> <img id="highlight_area" src="/img/trans…
  • Error Line 99, Column 558: end tag for "img" omitted, but OMITTAG NO was specified
    …pines map" usemap="#philippines_map" > </div> </div> <div class="regions"> <di…

    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 99, Column 450: start tag was here
    …ght_area" src="/img/transparent.gif"> <img id="area_map" src="/img/transparent…
  • Error Line 99, Column 891: there is no attribute "alt"
    …);" onmouseout="hide_image(1,1);" alt="ABRA, APAYAO, BENGUET, IFUGAO, KALINGA,…

    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 99, Column 1083: there is no attribute "xtclib"
    …/www.ayosdito.ph/CAR/for-sale" xtclib="index_regiontext_CAR">CAR</a> </li> <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 99, Column 9162: end tag for "br" omitted, but OMITTAG NO was specified
    …</li>  </ol> </div> <br class="clear"> <div id="footer"> <ul> <li><a onclick="…

    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 99, Column 9144: start tag was here
    …xt_ARMM">ARMM</a> </li>  </ol> </div> <br class="clear"> <div id="footer"> <ul…
  • Warning Line 99, Column 9470: cannot generate system identifier for general entity "page"
    …ww.ayosdito.ph/about/index.htm?ca=5_s&page=rules" rel="nofollow">Rules</a></li…

    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 99, Column 9470: general entity "page" not defined and no default entity
    …ww.ayosdito.ph/about/index.htm?ca=5_s&page=rules" rel="nofollow">Rules</a></li…

    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 99, Column 9474: reference not terminated by REFC delimiter
    …yosdito.ph/about/index.htm?ca=5_s&page=rules" rel="nofollow">Rules</a></li> <l…

    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 99, Column 9474: reference to external entity in attribute value
    …yosdito.ph/about/index.htm?ca=5_s&page=rules" rel="nofollow">Rules</a></li> <l…

    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 99, Column 9474: reference to entity "page" for which no system identifier could be generated
    …yosdito.ph/about/index.htm?ca=5_s&page=rules" rel="nofollow">Rules</a></li> <l…

    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 99, Column 9469: entity was defined here
    …www.ayosdito.ph/about/index.htm?ca=5_s&page=rules" rel="nofollow">Rules</a></l…
  • Warning Line 99, Column 10503: cannot generate system identifier for general entity "id"
    …ww2.ayosdito.ph/support/form/0?ca=5_s&id=20" rel="nofollow">Help</a></li> <li>…

    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 99, Column 10503: general entity "id" not defined and no default entity
    …ww2.ayosdito.ph/support/form/0?ca=5_s&id=20" rel="nofollow">Help</a></li> <li>…

    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 99, Column 10505: reference not terminated by REFC delimiter
    …2.ayosdito.ph/support/form/0?ca=5_s&id=20" rel="nofollow">Help</a></li> <li><a…

    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 99, Column 10505: reference to external entity in attribute value
    …2.ayosdito.ph/support/form/0?ca=5_s&id=20" rel="nofollow">Help</a></li> <li><a…

    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 99, Column 10505: reference to entity "id" for which no system identifier could be generated
    …2.ayosdito.ph/support/form/0?ca=5_s&id=20" rel="nofollow">Help</a></li> <li><a…

    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 99, Column 10502: entity was defined here
    …www2.ayosdito.ph/support/form/0?ca=5_s&id=20" rel="nofollow">Help</a></li> <li…
  • Warning Line 99, Column 10673: reference not terminated by REFC delimiter
    …yosdito.ph/about/index.htm?ca=5_s&page=terms" rel="nofollow">Terms & Condition…

    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 99, Column 10673: reference to external entity in attribute value
    …yosdito.ph/about/index.htm?ca=5_s&page=terms" rel="nofollow">Terms & Condition…

    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 99, Column 10673: reference to entity "page" for which no system identifier could be generated
    …yosdito.ph/about/index.htm?ca=5_s&page=terms" rel="nofollow">Terms & Condition…

    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 99, Column 9469: entity was defined here
    …www.ayosdito.ph/about/index.htm?ca=5_s&page=rules" rel="nofollow">Rules</a></l…
  • Warning Line 99, Column 10702: character "&" is the first character of a delimiter but occurred as data
    …=5_s&page=terms" rel="nofollow">Terms & Conditions</a></li> </ul>  <p> Travell…

    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 99, Column 10873: there is no attribute "target"
    …ggeliopolis.gr" title="Greece" target="_blank">aggeliopolis.gr</a>&nbsp; <a hr…

    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 129, Column 54: required attribute "id" not specified
    … area --> <map name="philippines_map" > <area shape="poly" onmouseover="change…

    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 129, Column 617: there is no attribute "xtclib"
    …/www.ayosdito.ph/CAR/for-sale" xtclib="indexmap_CAR"> <area shape="poly" onmou…

    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 129, Column 632: end tag for "area" omitted, but OMITTAG NO was specified
    …h/CAR/for-sale" xtclib="indexmap_CAR"> <area shape="poly" onmouseover="change_…

    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 129, Column 56: start tag was here
    …rea --> <map name="philippines_map" > <area shape="poly" onmouseover="change_i…
  • Error Line 129, Column 1206: end tag for "area" omitted, but OMITTAG NO was specified
    …sale" xtclib="indexmap_Ilocos Region"> <area shape="poly" onmouseover="change_…

    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 129, Column 633: start tag was here
    …/CAR/for-sale" xtclib="indexmap_CAR"> <area shape="poly" onmouseover="change_i…
  • Error Line 129, Column 1767: end tag for "area" omitted, but OMITTAG NO was specified
    …ale" xtclib="indexmap_Cagayan Region"> <area shape="poly" onmouseover="change_…

    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 129, Column 1207: start tag was here
    …ale" xtclib="indexmap_Ilocos Region"> <area shape="poly" onmouseover="change_i…
  • Error Line 129, Column 2381: end tag for "area" omitted, but OMITTAG NO was specified
    …sale" xtclib="indexmap_Central Luzon"> <area shape="poly" onmouseover="change_…

    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 129, Column 1768: start tag was here
    …le" xtclib="indexmap_Cagayan Region"> <area shape="poly" onmouseover="change_i…
  • Error Line 129, Column 3124: end tag for "area" omitted, but OMITTAG NO was specified
    …h/NCR/for-sale" xtclib="indexmap_NCR"> <area shape="poly" onmouseover="change_…

    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 129, Column 2382: start tag was here
    …ale" xtclib="indexmap_Central Luzon"> <area shape="poly" onmouseover="change_i…
  • Error Line 129, Column 3675: end tag for "area" omitted, but OMITTAG NO was specified
    …or-sale" xtclib="indexmap_CALABARZON"> <area shape="poly" onmouseover="change_…

    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 129, Column 3125: start tag was here
    …/NCR/for-sale" xtclib="indexmap_NCR"> <area shape="poly" onmouseover="change_i…
  • Error Line 129, Column 4269: end tag for "area" omitted, but OMITTAG NO was specified
    …/for-sale" xtclib="indexmap_MIMAROPA"> <area shape="poly" onmouseover="change_…

    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 129, Column 3676: start tag was here
    …r-sale" xtclib="indexmap_CALABARZON"> <area shape="poly" onmouseover="change_i…
  • Error Line 129, Column 4817: end tag for "area" omitted, but OMITTAG NO was specified
    …col/for-sale" xtclib="indexmap_Bicol"> <area shape="poly" onmouseover="change_…

    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 129, Column 4270: start tag was here
    …for-sale" xtclib="indexmap_MIMAROPA"> <area shape="poly" onmouseover="change_i…
  • Error Line 129, Column 5401: end tag for "area" omitted, but OMITTAG NO was specified
    …le" xtclib="indexmap_Western Visayas"> <area shape="poly" onmouseover="change_…

    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 129, Column 4818: start tag was here
    …ol/for-sale" xtclib="indexmap_Bicol"> <area shape="poly" onmouseover="change_i…
  • Error Line 129, Column 5974: end tag for "area" omitted, but OMITTAG NO was specified
    …le" xtclib="indexmap_Central Visayas"> <area shape="poly" onmouseover="change_…

    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 129, Column 5402: start tag was here
    …e" xtclib="indexmap_Western Visayas"> <area shape="poly" onmouseover="change_i…
  • Error Line 129, Column 6557: end tag for "area" omitted, but OMITTAG NO was specified
    …le" xtclib="indexmap_Eastern Visayas"> <area shape="poly" onmouseover="change_…

    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 129, Column 5975: start tag was here
    …e" xtclib="indexmap_Central Visayas"> <area shape="poly" onmouseover="change_i…
  • Error Line 129, Column 7118: end tag for "area" omitted, but OMITTAG NO was specified
    …xtclib="indexmap_Zamboanga Peninsula"> <area shape="poly" onmouseover="change_…

    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 129, Column 6558: start tag was here
    …e" xtclib="indexmap_Eastern Visayas"> <area shape="poly" onmouseover="change_i…
  • Error Line 129, Column 7753: end tag for "area" omitted, but OMITTAG NO was specified
    …" xtclib="indexmap_Northern Mindanao"> <area shape="poly" onmouseover="change_…

    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 129, Column 7119: start tag was here
    …tclib="indexmap_Zamboanga Peninsula"> <area shape="poly" onmouseover="change_i…
  • Error Line 129, Column 8373: end tag for "area" omitted, but OMITTAG NO was specified
    …-sale" xtclib="indexmap_Davao Region"> <area shape="poly" onmouseover="change_…

    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 129, Column 7754: start tag was here
    … xtclib="indexmap_Northern Mindanao"> <area shape="poly" onmouseover="change_i…
  • Error Line 129, Column 9042: end tag for "area" omitted, but OMITTAG NO was specified
    …for-sale" xtclib="indexmap_SOCSARGEN"> <area shape="poly" onmouseover="change_…

    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 129, Column 8374: start tag was here
    …sale" xtclib="indexmap_Davao Region"> <area shape="poly" onmouseover="change_i…
  • Error Line 129, Column 9596: end tag for "area" omitted, but OMITTAG NO was specified
    …GA/for-sale" xtclib="indexmap_CARAGA"> <area shape="poly" onmouseover="change_…

    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 129, Column 9043: start tag was here
    …or-sale" xtclib="indexmap_SOCSARGEN"> <area shape="poly" onmouseover="change_i…
  • Error Line 129, Column 10220: end tag for "area" omitted, but OMITTAG NO was specified
    …sdito.ph/ARMM/for-sale" xtclib="indexmap_ARMM">  </map> <!-- end map area -->  

    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 129, Column 9597: start tag was here
    …A/for-sale" xtclib="indexmap_CARAGA"> <area shape="poly" onmouseover="change_i…
  • Error Line 131, Column 8: required attribute "type" not specified
    <script>

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

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

  • Error Line 140, Column 47: required attribute "alt" not specified
    			// '<img width="1" height="1" src="'+url+'">

    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 140, Column 47: document type does not allow element "img" here
    			// '<img width="1" height="1" src="'+url+'">

    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 140, Column 48: end tag for "img" omitted, but OMITTAG NO was specified
    			// '<img width="1" height="1" src="'+url+'">

    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 140, Column 8: start tag was here
    			// '<img width="1" height="1" src="'+url+'">
  • Error Line 171, Column 43: 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.

  • Warning Line 173, Column 368: character "&" is the first character of a delimiter but occurred as data
    …puid"+n}b=b+".gif?r="+l.getTime();if(e&&getCookie(e)){b+="&"+e+"=1"}if(documen…

    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 173, Column 370: cannot generate system identifier for general entity "getCookie"
    …id"+n}b=b+".gif?r="+l.getTime();if(e&&getCookie(e)){b+="&"+e+"=1"}if(document.…

    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 173, Column 370: general entity "getCookie" not defined and no default entity
    …id"+n}b=b+".gif?r="+l.getTime();if(e&&getCookie(e)){b+="&"+e+"=1"}if(document.…

    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 173, Column 379: reference not terminated by REFC delimiter
    …+".gif?r="+l.getTime();if(e&&getCookie(e)){b+="&"+e+"=1"}if(document.write_org…

    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 173, Column 379: reference to entity "getCookie" for which no system identifier could be generated
    …+".gif?r="+l.getTime();if(e&&getCookie(e)){b+="&"+e+"=1"}if(document.write_org…

    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 173, Column 369: entity was defined here
    …uid"+n}b=b+".gif?r="+l.getTime();if(e&&getCookie(e)){b+="&"+e+"=1"}if(document…
  • Warning Line 173, Column 388: character "&" is the first character of a delimiter but occurred as data
    …"+l.getTime();if(e&&getCookie(e)){b+="&"+e+"=1"}if(document.write_org!=null){d…

    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 173, Column 499: required attribute "alt" not specified
    …'" height="1" width="1" id="stats_1x1">')}else{document.write('<img src="'+b+'…

    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 173, Column 499: document type does not allow element "img" here
    …'" height="1" width="1" id="stats_1x1">')}else{document.write('<img src="'+b+'…

    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 173, Column 500: end tag for "img" omitted, but OMITTAG NO was specified
    …" height="1" width="1" id="stats_1x1">')}else{document.write('<img src="'+b+'"…

    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 173, Column 447: start tag was here
    ….write_org!=null){document.write_org('<img src="'+b+'" height="1" width="1" id…
  • Error Line 173, Column 566: ID "stats_1x1" already defined
    …}else{document.write('<img src="'+b+'" height="1" width="1" id="stats_1x1">')}}

    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 173, Column 489: ID "stats_1x1" first defined here
    … src="'+b+'" height="1" width="1" id="stats_1x1">')}else{document.write('<img …
  • Error Line 173, Column 576: required attribute "alt" not specified
    …}else{document.write('<img src="'+b+'" height="1" width="1" id="stats_1x1">')}}

    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 173, Column 576: document type does not allow element "img" here
    …}else{document.write('<img src="'+b+'" height="1" width="1" id="stats_1x1">')}}

    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 173, Column 577: end tag for "img" omitted, but OMITTAG NO was specified
    …}else{document.write('<img src="'+b+'" height="1" width="1" id="stats_1x1">')}}

    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 173, Column 524: start tag was here
    …d="stats_1x1">')}else{document.write('<img src="'+b+'" height="1" width="1" id…
  • Warning Line 239, Column 76: cannot generate system identifier for general entity "s2"
    …ght="1" src="http://logc172.xiti.com/hit.xiti?s=413425&s2=1&p=Homepage&di=&" />

    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 239, Column 76: general entity "s2" not defined and no default entity
    …ght="1" src="http://logc172.xiti.com/hit.xiti?s=413425&s2=1&p=Homepage&di=&" />

    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 239, Column 78: reference not terminated by REFC delimiter
    …ght="1" src="http://logc172.xiti.com/hit.xiti?s=413425&s2=1&p=Homepage&di=&" />

    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 239, Column 78: reference to external entity in attribute value
    …ght="1" src="http://logc172.xiti.com/hit.xiti?s=413425&s2=1&p=Homepage&di=&" />

    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 239, Column 78: reference to entity "s2" for which no system identifier could be generated
    …ght="1" src="http://logc172.xiti.com/hit.xiti?s=413425&s2=1&p=Homepage&di=&" />

    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 239, Column 75: entity was defined here
    …ght="1" src="http://logc172.xiti.com/hit.xiti?s=413425&s2=1&p=Homepage&di=&" />
  • Warning Line 239, Column 81: cannot generate system identifier for general entity "p"
    …ght="1" src="http://logc172.xiti.com/hit.xiti?s=413425&s2=1&p=Homepage&di=&" />

    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 239, Column 81: general entity "p" not defined and no default entity
    …ght="1" src="http://logc172.xiti.com/hit.xiti?s=413425&s2=1&p=Homepage&di=&" />

    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 239, Column 82: reference not terminated by REFC delimiter
    …ght="1" src="http://logc172.xiti.com/hit.xiti?s=413425&s2=1&p=Homepage&di=&" />

    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 239, Column 82: reference to external entity in attribute value
    …ght="1" src="http://logc172.xiti.com/hit.xiti?s=413425&s2=1&p=Homepage&di=&" />

    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 239, Column 82: reference to entity "p" for which no system identifier could be generated
    …ght="1" src="http://logc172.xiti.com/hit.xiti?s=413425&s2=1&p=Homepage&di=&" />

    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 239, Column 80: entity was defined here
    …ght="1" src="http://logc172.xiti.com/hit.xiti?s=413425&s2=1&p=Homepage&di=&" />
  • Warning Line 239, Column 92: cannot generate system identifier for general entity "di"
    …ght="1" src="http://logc172.xiti.com/hit.xiti?s=413425&s2=1&p=Homepage&di=&" />

    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 239, Column 92: general entity "di" not defined and no default entity
    …ght="1" src="http://logc172.xiti.com/hit.xiti?s=413425&s2=1&p=Homepage&di=&" />

    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 239, Column 94: reference not terminated by REFC delimiter
    …ght="1" src="http://logc172.xiti.com/hit.xiti?s=413425&s2=1&p=Homepage&di=&" />

    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 239, Column 94: reference to external entity in attribute value
    …ght="1" src="http://logc172.xiti.com/hit.xiti?s=413425&s2=1&p=Homepage&di=&" />

    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 239, Column 94: reference to entity "di" for which no system identifier could be generated
    …ght="1" src="http://logc172.xiti.com/hit.xiti?s=413425&s2=1&p=Homepage&di=&" />

    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 239, Column 91: entity was defined here
    …ght="1" src="http://logc172.xiti.com/hit.xiti?s=413425&s2=1&p=Homepage&di=&" />
  • Warning Line 239, Column 95: character "&" is the first character of a delimiter but occurred as data
    …ght="1" src="http://logc172.xiti.com/hit.xiti?s=413425&s2=1&p=Homepage&di=&" />

    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 239, Column 99: required attribute "alt" not specified
    …ght="1" src="http://logc172.xiti.com/hit.xiti?s=413425&s2=1&p=Homepage&di=&" />

    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 239, Column 99: document type does not allow element "img" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "address", "fieldset", "ins", "del" start-tag
    …ght="1" src="http://logc172.xiti.com/hit.xiti?s=413425&s2=1&p=Homepage&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 249, Column 8: required attribute "type" not specified
    <script>

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

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

  • Error Line 252, Column 8: required attribute "type" not specified
    <script>

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

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

  • Warning Line 264, Column 51: cannot generate system identifier for general entity "c2"
    …http://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 264, Column 51: general entity "c2" not defined and no default entity
    …http://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 264, Column 53: reference not terminated by REFC delimiter
    …tp://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" …

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 264, Column 53: reference to external entity in attribute value
    …tp://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" …

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 264, Column 53: reference to entity "c2" for which no system identifier could be generated
    …tp://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" …

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 264, Column 50: entity was defined here
    …"http://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=…
  • Warning Line 264, Column 62: cannot generate system identifier for general entity "c3"
    …p://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" />

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 264, Column 62: general entity "c3" not defined and no default entity
    …p://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" />

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 264, Column 64: reference not terminated by REFC delimiter
    …p://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" />

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 264, Column 64: reference to external entity in attribute value
    …p://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" />

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 264, Column 64: reference to entity "c3" for which no system identifier could be generated
    …p://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" />

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 264, Column 61: entity was defined here
    …p://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" />
  • Warning Line 264, Column 66: cannot generate system identifier for general entity "c4"
    …p://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" />

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 264, Column 66: general entity "c4" not defined and no default entity
    …p://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" />

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 264, Column 68: reference not terminated by REFC delimiter
    …p://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" />

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 264, Column 68: reference to external entity in attribute value
    …p://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" />

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 264, Column 68: reference to entity "c4" for which no system identifier could be generated
    …p://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" />

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 264, Column 65: entity was defined here
    …p://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" />
  • Warning Line 264, Column 74: cannot generate system identifier for general entity "c5"
    …p://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" />

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 264, Column 74: general entity "c5" not defined and no default entity
    …p://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" />

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 264, Column 76: reference not terminated by REFC delimiter
    …p://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" />

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 264, Column 76: reference to external entity in attribute value
    …p://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" />

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 264, Column 76: reference to entity "c5" for which no system identifier could be generated
    …p://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" />

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 264, Column 73: entity was defined here
    …p://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" />
  • Warning Line 264, Column 78: cannot generate system identifier for general entity "c6"
    …p://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" />

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 264, Column 78: general entity "c6" not defined and no default entity
    …p://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" />

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 264, Column 80: reference not terminated by REFC delimiter
    …p://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" />

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 264, Column 80: reference to external entity in attribute value
    …p://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" />

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 264, Column 80: reference to entity "c6" for which no system identifier could be generated
    …p://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" />

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 264, Column 77: entity was defined here
    …p://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" />
  • Warning Line 264, Column 82: cannot generate system identifier for general entity "c15"
    …p://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" />

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 264, Column 82: general entity "c15" not defined and no default entity
    …p://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" />

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 264, Column 85: reference not terminated by REFC delimiter
    …p://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" />

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 264, Column 85: reference to external entity in attribute value
    …p://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" />

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 264, Column 85: reference to entity "c15" for which no system identifier could be generated
    …p://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" />

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 264, Column 81: entity was defined here
    …p://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" />
  • Warning Line 264, Column 87: cannot generate system identifier for general entity "cj"
    …p://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" />

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 264, Column 87: general entity "cj" not defined and no default entity
    …p://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" />

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 264, Column 89: reference not terminated by REFC delimiter
    …p://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" />

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 264, Column 89: reference to external entity in attribute value
    …p://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" />

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 264, Column 89: reference to entity "cj" for which no system identifier could be generated
    …p://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" />

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 264, Column 86: entity was defined here
    …p://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" />
  • Error Line 264, Column 94: required attribute "alt" not specified
    …p://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=1" />

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

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

  • Error Line 264, Column 94: document type does not allow element "img" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "address", "fieldset", "ins", "del" start-tag
    …p://b.scorecardresearch.com/p?c1=2&c2=7290418&c3=&c4=home&c5=&c6=&c15=&cj=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>").

Visitor Analysis

Daily Visitor
  • 24.500 visits