Mahshar محشرمحبوبترين چت روم سرگرمي راديو تلويزيون فارسي فال حافظ مسنجر فال سال تولد قرآن:mahshar, محشر, جوك, sms, چت روم, تصوير, فال, موبايل, رايگان, آي دي, ياهو, دانلود, آموزش, مخفي, زن, دختر, پسر, ...

mahshar.com
  • Domain Name
    mahshar.com
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #29892
  • Page Size
    47.1 KB
  • Ip Address
    46.4.103.120
  • Heading
    H1: 19, H2: 2, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    19 GIF, 2 JPG, 21 PNG

Website Meta Analysis

  • Title
    Mahshar محشرمحبوبترين چت روم سرگرمي راديو تلويزيون فارسي فال حافظ مسنجر فال سال تولد قرآن
  • Meta Keyword
    mahshar, محشر, جوك, sms, چت روم, تصوير, فال, موبايل, رايگان, آي دي, ياهو, دانلود, آموزش, مخفي, زن, دختر, پسر, مرد, جوان, دوربين, باردار, سايت, تلفن, تصاوير, برنامه, آگهي, ورزش, نقشه, بيني, سرگرمي, عشق, سنجش, وبلاگ, فونت, ترين ها, اخبار, فال حافظ, هند, ترفند, پرچم, پول, فارسي, تست, راديو, تلويزيون, پخش زنده, ميوه, كودك, آشپزي, ترشيجات, دسر, شيريني, غذا, ركورد, اسم, فال تولد, طالع, پنير, رنگ, فصل, خواب, شغل, هفته, وزن, ورق, حكومت, ايتاليا, پرندگان, تاروت, درخت, متولدين, مصر
  • Meta Description
    Mahshar محشرمحبوبترين چت روم سرگرمي راديو تلويزيون فارسي فال حافظ مسنجر فال سال تولد قرآن:mahshar, محشر, جوك, sms, چت روم, تصوير, فال, موبايل, رايگان, آي دي, ياهو, دانلود, آموزش, مخفي, زن, دختر, پسر, مرد, جوان, دوربين, باردار, سايت, تلفن, تصاوير, برنامه, آگهي, ورزش, نقشه, بيني, سرگرمي, عشق, سنجش, وبلاگ, فونت, ترين ها, اخبار, فال حافظ, هند, ترفند, پرچم, پول, فارسي, تست, راديو, تلويزيون, پخش زنده, ميوه, كودك, آشپزي, ترشيجات, دسر, شيريني, غذا, ركورد, اسم, فال تولد, طالع, پنير, رنگ, فصل, خواب, شغل, هفته, وزن, ورق, حكومت, ايتاليا, پرندگان, تاروت, شبکه هوشمند, متولدين, مصر

Technical Analysis

  • Webserver
    Apache/2
  • Ip Address
    46.4.103.120
  • Domain Age
    9 Years, 4 Months, 0 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Sun, 03 Feb 2013 10:49:13 GMT
  • server: Apache/2
  • last-modified: Fri, 01 Feb 2013 19:01:31 GMT
  • etag: "a1ba-4d4ae5f193dd2-gzip"
  • accept-ranges: bytes
  • vary: Accept-Encoding,User-Agent
  • content-encoding: gzip
  • content-length: 8662
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
abdolali fazeli niaki email +98.9123833830 +98.9123833830
mehdi vakilian
tehran
tehran,tehran,MY 81050

Domain Domain Name:mahshar.com
Updated: 2012-03-16 03:14:00
Created: 9/24/2003
Expires: 09/24/2015

Name Servers:
ns1.secure-and-strong-web-host.com ns2.secure-and-strong-web-host.com
Administrator:
Domain Name:(mehdi vakilian)
Email:( email ) tel- +98.9123833830
fax:(+98.9123833830)
mehdi vakilian
tehran
tehran
tehran,
MY
zipcode:81050
Technical Contactor:
Domain Name:(mehdi vakilian)
Email:( email ) tel- +98.9123833830
fax:(+98.9123833830)
mehdi vakilian
tehran
tehran
tehran,
MY
zipcode:81050
Billing Contactor:
Domain Name:(mehdi vakilian)
Email:( email ) tel- +98.9123833830
fax:(+98.9123833830)
mehdi vakilian
tehran
tehran
tehran,
MY
zipcode:81050

DNS Analysis


DNS servers
ns1.secure-and-strong-web-host.com [174.142.210.109]
ns2.secure-and-strong-web-host.com [174.142.210.109]


DNS Records

Answer records
mahshar.com SOA
server: ns1.secure-and-strong-web-host.com
email: hostmaster@mahshar.com
serial: 2013012300
refresh: 14400
retry: 3600
expire: 1209600
minimum ttl: 86400
14400s
mahshar.com NS  ns.netafraz.com 14400s
mahshar.com NS  ns2.netafraz.com 14400s
mahshar.com A 46.4.103.120 14400s
mahshar.com TXT v=spf1 a mx ip4:46.4.103.120 ~all 14400s
mahshar.com MX
preference: 10
exchange: mail.mahshar.com
14400s

Authority records

Additional records
ns.netafraz.com A 174.142.210.107 14400s
ns2.netafraz.com A 5.9.15.85 14400s
mail.mahshar.com A 46.4.103.120 14400s

IP 46.4.103.120 Analysis

  • Country Code
    DE
  • Country Code3
    DEU
  • Country Name
    Germany
  • City
    EU
  • Continent Code
    51° North
  • Latitude
    9.
  • Longitude
  • No whois ip data for 46.4.103.120

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 113 Errors
  • 37 Warnings
Ratio Text/Html
  • 0.625225486740343
Message Error
  • Error Line 23, Column 14: there is no attribute "target"
    <base target="_blank" />

    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 23, Column 24: required attribute "href" not specified
    <base target="_blank" />

    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 26, Column 12: there is no attribute "align"
    <div align="center">

    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 31, Column 38: there is no attribute "target"
    <a href="http://mahshar.com/" target="_top">صفحه نخست</a>-

    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 24: there is no attribute "width"
    <td valign="top" width="230"><br />

    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 104, Column 170: cannot generate system identifier for general entity "token"
    …//live.irib.ir/preplayer.php?cat_id=1&token=dbb0a2b58becbe476ede295676d73189',…

    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 104, Column 170: general entity "token" not defined and no default entity
    …//live.irib.ir/preplayer.php?cat_id=1&token=dbb0a2b58becbe476ede295676d73189',…

    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 104, Column 175: reference not terminated by REFC delimiter
    …e.irib.ir/preplayer.php?cat_id=1&token=dbb0a2b58becbe476ede295676d73189','پخش …

    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 104, Column 175: reference to external entity in attribute value
    …e.irib.ir/preplayer.php?cat_id=1&token=dbb0a2b58becbe476ede295676d73189','پخش …

    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 104, Column 175: reference to entity "token" for which no system identifier could be generated
    …e.irib.ir/preplayer.php?cat_id=1&token=dbb0a2b58becbe476ede295676d73189','پخش …

    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 104, Column 169: entity was defined here
    …://live.irib.ir/preplayer.php?cat_id=1&token=dbb0a2b58becbe476ede295676d73189'…
  • Warning Line 106, Column 175: reference not terminated by REFC delimiter
    …e.irib.ir/preplayer.php?cat_id=2&token=dbb0a2b58becbe476ede295676d73189','پخش …

    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 106, Column 175: reference to external entity in attribute value
    …e.irib.ir/preplayer.php?cat_id=2&token=dbb0a2b58becbe476ede295676d73189','پخش …

    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 106, Column 175: reference to entity "token" for which no system identifier could be generated
    …e.irib.ir/preplayer.php?cat_id=2&token=dbb0a2b58becbe476ede295676d73189','پخش …

    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 104, Column 169: entity was defined here
    …://live.irib.ir/preplayer.php?cat_id=1&token=dbb0a2b58becbe476ede295676d73189'…
  • Warning Line 108, Column 175: reference not terminated by REFC delimiter
    …e.irib.ir/preplayer.php?cat_id=3&token=dbb0a2b58becbe476ede295676d73189','پخش …

    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 108, Column 175: reference to external entity in attribute value
    …e.irib.ir/preplayer.php?cat_id=3&token=dbb0a2b58becbe476ede295676d73189','پخش …

    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 108, Column 175: reference to entity "token" for which no system identifier could be generated
    …e.irib.ir/preplayer.php?cat_id=3&token=dbb0a2b58becbe476ede295676d73189','پخش …

    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 104, Column 169: entity was defined here
    …://live.irib.ir/preplayer.php?cat_id=1&token=dbb0a2b58becbe476ede295676d73189'…
  • Warning Line 110, Column 175: reference not terminated by REFC delimiter
    …e.irib.ir/preplayer.php?cat_id=4&token=dbb0a2b58becbe476ede295676d73189','پخش …

    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 110, Column 175: reference to external entity in attribute value
    …e.irib.ir/preplayer.php?cat_id=4&token=dbb0a2b58becbe476ede295676d73189','پخش …

    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 110, Column 175: reference to entity "token" for which no system identifier could be generated
    …e.irib.ir/preplayer.php?cat_id=4&token=dbb0a2b58becbe476ede295676d73189','پخش …

    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 104, Column 169: entity was defined here
    …://live.irib.ir/preplayer.php?cat_id=1&token=dbb0a2b58becbe476ede295676d73189'…
  • Warning Line 112, Column 175: reference not terminated by REFC delimiter
    …e.irib.ir/preplayer.php?cat_id=5&token=dbb0a2b58becbe476ede295676d73189','پخش …

    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 112, Column 175: reference to external entity in attribute value
    …e.irib.ir/preplayer.php?cat_id=5&token=dbb0a2b58becbe476ede295676d73189','پخش …

    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 112, Column 175: reference to entity "token" for which no system identifier could be generated
    …e.irib.ir/preplayer.php?cat_id=5&token=dbb0a2b58becbe476ede295676d73189','پخش …

    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 104, Column 169: entity was defined here
    …://live.irib.ir/preplayer.php?cat_id=1&token=dbb0a2b58becbe476ede295676d73189'…
  • Error Line 150, Column 80: there is no attribute "border"
    …mg alt="فال و طالع بینی روزانه - امروز" border="0" src="i/chess.gif"></a><br />

    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 150, Column 105: end tag for "img" omitted, but OMITTAG NO was specified
    …mg alt="فال و طالع بینی روزانه - امروز" border="0" src="i/chess.gif"></a><br />

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

  • Info Line 150, Column 31: start tag was here
    فال و طالع بینی روزانه - امروز<img alt="فال و طالع بینی روزانه - امروز" border=…
  • Error Line 242, Column 8: element "center" undefined
    <center>

    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 243, Column 16: there is no attribute "border"
    <iframe border="0" class="agahibanerindex" frameborder="0" marginheight="0" mar…

    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 243, Column 26: there is no attribute "class"
    <iframe border="0" class="agahibanerindex" frameborder="0" marginheight="0" mar…

    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 243, Column 56: there is no attribute "frameborder"
    …" class="agahibanerindex" frameborder="0" marginheight="0" marginwidth="0" scr…

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

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

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

  • Error Line 243, Column 73: there is no attribute "marginheight"
    …erindex" frameborder="0" marginheight="0" marginwidth="0" scrolling="no" src="…

    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 243, Column 89: there is no attribute "marginwidth"
    …rder="0" marginheight="0" marginwidth="0" scrolling="no" src="agahi/L210_100_B…

    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 243, Column 103: there is no attribute "scrolling"
    …rginheight="0" marginwidth="0" scrolling="no" src="agahi/L210_100_B_right.htm">

    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 243, Column 112: there is no attribute "src"
    …rginheight="0" marginwidth="0" scrolling="no" src="agahi/L210_100_B_right.htm">

    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 243, Column 140: element "iframe" undefined
    …rginheight="0" marginwidth="0" scrolling="no" src="agahi/L210_100_B_right.htm">

    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 336, Column 42: end tag for "br" omitted, but OMITTAG NO was specified
    <a href="photoshop">فتوشاپ آنلاین</a><br>

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

  • Info Line 336, Column 38: start tag was here
    <a href="photoshop">فتوشاپ آنلاین</a><br>
  • Error Line 339, Column 50: end tag for "br" omitted, but OMITTAG NO was specified
    <strong><i>قالب رایگان وبلاگ</i></strong></a><br>

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

  • Info Line 339, Column 46: start tag was here
    <strong><i>قالب رایگان وبلاگ</i></strong></a><br>
  • Warning Line 340, Column 41: cannot generate system identifier for general entity "rct"
    … href="http://www.google.com/url?sa=t&rct=j&q=%D8%B7%D8%B1%D8%A7%D8%AD%DB%8C%2…

    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 340, Column 41: general entity "rct" not defined and no default entity
    … href="http://www.google.com/url?sa=t&rct=j&q=%D8%B7%D8%B1%D8%A7%D8%AD%DB%8C%2…

    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 340, Column 44: reference not terminated by REFC delimiter
    …ef="http://www.google.com/url?sa=t&rct=j&q=%D8%B7%D8%B1%D8%A7%D8%AD%DB%8C%20%D…

    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 340, Column 44: reference to external entity in attribute value
    …ef="http://www.google.com/url?sa=t&rct=j&q=%D8%B7%D8%B1%D8%A7%D8%AD%DB%8C%20%D…

    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 340, Column 44: reference to entity "rct" for which no system identifier could be generated
    …ef="http://www.google.com/url?sa=t&rct=j&q=%D8%B7%D8%B1%D8%A7%D8%AD%DB%8C%20%D…

    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 340, Column 40: entity was defined here
    …a href="http://www.google.com/url?sa=t&rct=j&q=%D8%B7%D8%B1%D8%A7%D8%AD%DB%8C%…
  • Warning Line 340, Column 47: cannot generate system identifier for general entity "q"
    …"http://www.google.com/url?sa=t&rct=j&q=%D8%B7%D8%B1%D8%A7%D8%AD%DB%8C%20%D9%8…

    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 340, Column 47: general entity "q" not defined and no default entity
    …"http://www.google.com/url?sa=t&rct=j&q=%D8%B7%D8%B1%D8%A7%D8%AD%DB%8C%20%D9%8…

    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 340, Column 48: reference not terminated by REFC delimiter
    …http://www.google.com/url?sa=t&rct=j&q=%D8%B7%D8%B1%D8%A7%D8%AD%DB%8C%20%D9%88…

    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 340, Column 48: reference to external entity in attribute value
    …http://www.google.com/url?sa=t&rct=j&q=%D8%B7%D8%B1%D8%A7%D8%AD%DB%8C%20%D9%88…

    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 340, Column 48: reference to entity "q" for which no system identifier could be generated
    …http://www.google.com/url?sa=t&rct=j&q=%D8%B7%D8%B1%D8%A7%D8%AD%DB%8C%20%D9%88…

    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 340, Column 46: entity was defined here
    …="http://www.google.com/url?sa=t&rct=j&q=%D8%B7%D8%B1%D8%A7%D8%AD%DB%8C%20%D9%…
  • Warning Line 340, Column 122: cannot generate system identifier for general entity "source"
    …9%88%D8%A8%20%D8%B3%D8%A7%DB%8C%D8%AA&source=web&cd=63&ved=0CEYQFjACODw&url=ht…

    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 340, Column 122: general entity "source" not defined and no default entity
    …9%88%D8%A8%20%D8%B3%D8%A7%DB%8C%D8%AA&source=web&cd=63&ved=0CEYQFjACODw&url=ht…

    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 340, Column 128: reference not terminated by REFC delimiter
    …8%A8%20%D8%B3%D8%A7%DB%8C%D8%AA&source=web&cd=63&ved=0CEYQFjACODw&url=http%3A%…

    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 340, Column 128: reference to external entity in attribute value
    …8%A8%20%D8%B3%D8%A7%DB%8C%D8%AA&source=web&cd=63&ved=0CEYQFjACODw&url=http%3A%…

    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 340, Column 128: reference to entity "source" for which no system identifier could be generated
    …8%A8%20%D8%B3%D8%A7%DB%8C%D8%AA&source=web&cd=63&ved=0CEYQFjACODw&url=http%3A%…

    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 340, Column 121: entity was defined here
    …D9%88%D8%A8%20%D8%B3%D8%A7%DB%8C%D8%AA&source=web&cd=63&ved=0CEYQFjACODw&url=h…
  • Warning Line 340, Column 133: cannot generate system identifier for general entity "cd"
    …20%D8%B3%D8%A7%DB%8C%D8%AA&source=web&cd=63&ved=0CEYQFjACODw&url=http%3A%2F%2F…

    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 340, Column 133: general entity "cd" not defined and no default entity
    …20%D8%B3%D8%A7%DB%8C%D8%AA&source=web&cd=63&ved=0CEYQFjACODw&url=http%3A%2F%2F…

    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 340, Column 135: reference not terminated by REFC delimiter
    …%D8%B3%D8%A7%DB%8C%D8%AA&source=web&cd=63&ved=0CEYQFjACODw&url=http%3A%2F%2Fww…

    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 340, Column 135: reference to external entity in attribute value
    …%D8%B3%D8%A7%DB%8C%D8%AA&source=web&cd=63&ved=0CEYQFjACODw&url=http%3A%2F%2Fww…

    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 340, Column 135: reference to entity "cd" for which no system identifier could be generated
    …%D8%B3%D8%A7%DB%8C%D8%AA&source=web&cd=63&ved=0CEYQFjACODw&url=http%3A%2F%2Fww…

    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 340, Column 132: entity was defined here
    …%20%D8%B3%D8%A7%DB%8C%D8%AA&source=web&cd=63&ved=0CEYQFjACODw&url=http%3A%2F%2…
  • Warning Line 340, Column 139: cannot generate system identifier for general entity "ved"
    …B3%D8%A7%DB%8C%D8%AA&source=web&cd=63&ved=0CEYQFjACODw&url=http%3A%2F%2Fwww.va…

    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 340, Column 139: general entity "ved" not defined and no default entity
    …B3%D8%A7%DB%8C%D8%AA&source=web&cd=63&ved=0CEYQFjACODw&url=http%3A%2F%2Fwww.va…

    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 340, Column 142: reference not terminated by REFC delimiter
    …D8%A7%DB%8C%D8%AA&source=web&cd=63&ved=0CEYQFjACODw&url=http%3A%2F%2Fwww.vakil…

    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 340, Column 142: reference to external entity in attribute value
    …D8%A7%DB%8C%D8%AA&source=web&cd=63&ved=0CEYQFjACODw&url=http%3A%2F%2Fwww.vakil…

    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 340, Column 142: reference to entity "ved" for which no system identifier could be generated
    …D8%A7%DB%8C%D8%AA&source=web&cd=63&ved=0CEYQFjACODw&url=http%3A%2F%2Fwww.vakil…

    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 340, Column 138: entity was defined here
    …%B3%D8%A7%DB%8C%D8%AA&source=web&cd=63&ved=0CEYQFjACODw&url=http%3A%2F%2Fwww.v…
  • Warning Line 340, Column 156: cannot generate system identifier for general entity "url"
    …%AA&source=web&cd=63&ved=0CEYQFjACODw&url=http%3A%2F%2Fwww.vakilian.com%2F&ei=…

    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 340, Column 156: general entity "url" not defined and no default entity
    …%AA&source=web&cd=63&ved=0CEYQFjACODw&url=http%3A%2F%2Fwww.vakilian.com%2F&ei=…

    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 340, Column 159: reference not terminated by REFC delimiter
    …&source=web&cd=63&ved=0CEYQFjACODw&url=http%3A%2F%2Fwww.vakilian.com%2F&ei=D2w…

    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 340, Column 159: reference to external entity in attribute value
    …&source=web&cd=63&ved=0CEYQFjACODw&url=http%3A%2F%2Fwww.vakilian.com%2F&ei=D2w…

    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 340, Column 159: reference to entity "url" for which no system identifier could be generated
    …&source=web&cd=63&ved=0CEYQFjACODw&url=http%3A%2F%2Fwww.vakilian.com%2F&ei=D2w…

    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 340, Column 155: entity was defined here
    …8%AA&source=web&cd=63&ved=0CEYQFjACODw&url=http%3A%2F%2Fwww.vakilian.com%2F&ei…
  • Warning Line 340, Column 193: cannot generate system identifier for general entity "ei"
    …&url=http%3A%2F%2Fwww.vakilian.com%2F&ei=D2w3T-LDE46XhQff_PyWAg&usg=AFQjCNEULx…

    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 340, Column 193: general entity "ei" not defined and no default entity
    …&url=http%3A%2F%2Fwww.vakilian.com%2F&ei=D2w3T-LDE46XhQff_PyWAg&usg=AFQjCNEULx…

    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 340, Column 195: reference not terminated by REFC delimiter
    …rl=http%3A%2F%2Fwww.vakilian.com%2F&ei=D2w3T-LDE46XhQff_PyWAg&usg=AFQjCNEULxLY…

    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 340, Column 195: reference to external entity in attribute value
    …rl=http%3A%2F%2Fwww.vakilian.com%2F&ei=D2w3T-LDE46XhQff_PyWAg&usg=AFQjCNEULxLY…

    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 340, Column 195: reference to entity "ei" for which no system identifier could be generated
    …rl=http%3A%2F%2Fwww.vakilian.com%2F&ei=D2w3T-LDE46XhQff_PyWAg&usg=AFQjCNEULxLY…

    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 340, Column 192: entity was defined here
    …w&url=http%3A%2F%2Fwww.vakilian.com%2F&ei=D2w3T-LDE46XhQff_PyWAg&usg=AFQjCNEUL…
  • Warning Line 340, Column 219: cannot generate system identifier for general entity "usg"
    …lian.com%2F&ei=D2w3T-LDE46XhQff_PyWAg&usg=AFQjCNEULxLY6bLpuiPkZx1Jp_v9kLs5mg" …

    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 340, Column 219: general entity "usg" not defined and no default entity
    …lian.com%2F&ei=D2w3T-LDE46XhQff_PyWAg&usg=AFQjCNEULxLY6bLpuiPkZx1Jp_v9kLs5mg" …

    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 340, Column 222: reference not terminated by REFC delimiter
    …n.com%2F&ei=D2w3T-LDE46XhQff_PyWAg&usg=AFQjCNEULxLY6bLpuiPkZx1Jp_v9kLs5mg" tit…

    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 340, Column 222: reference to external entity in attribute value
    …n.com%2F&ei=D2w3T-LDE46XhQff_PyWAg&usg=AFQjCNEULxLY6bLpuiPkZx1Jp_v9kLs5mg" tit…

    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 340, Column 222: reference to entity "usg" for which no system identifier could be generated
    …n.com%2F&ei=D2w3T-LDE46XhQff_PyWAg&usg=AFQjCNEULxLY6bLpuiPkZx1Jp_v9kLs5mg" tit…

    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 340, Column 218: entity was defined here
    …ilian.com%2F&ei=D2w3T-LDE46XhQff_PyWAg&usg=AFQjCNEULxLY6bLpuiPkZx1Jp_v9kLs5mg"…
  • Error Line 355, Column 59: required attribute "alt" not specified
    <img border="0" src="agahi/free-sharj-irancell-talia2.png"></a><br>

    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 355, Column 63: end tag for "img" omitted, but OMITTAG NO was specified
    <img border="0" src="agahi/free-sharj-irancell-talia2.png"></a><br>

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

  • Info Line 355, Column 1: start tag was here
    <img border="0" src="agahi/free-sharj-irancell-talia2.png"></a><br>
  • Error Line 355, Column 68: end tag for "br" omitted, but OMITTAG NO was specified
    <img border="0" src="agahi/free-sharj-irancell-talia2.png"></a><br>

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

  • Info Line 355, Column 64: start tag was here
    <img border="0" src="agahi/free-sharj-irancell-talia2.png"></a><br>
  • Error Line 388, Column 8: element "center" undefined
    <center>

    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 389, Column 43: there is no attribute "height"
    …ame border="0" frameborder="0" height="22" scrolling="no" src="d/" width="195"…

    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 389, Column 78: there is no attribute "width"
    …ame border="0" frameborder="0" height="22" scrolling="no" src="d/" width="195">

    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 389, Column 83: element "iframe" undefined
    …ame border="0" frameborder="0" height="22" scrolling="no" src="d/" width="195">

    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 403, Column 18: value of attribute "align" cannot be "middle"; must be one of "left", "center", "right", "justify", "char"
    <td align="middle" style="border: 1px solid #D7F659; BACKGROUND-COLOR: #FFFFFF">

    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 404, Column 22: required attribute "type" not specified
    <script src="chat.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 419, Column 56: value of attribute "method" cannot be "GET"; must be one of "get", "post"
    …orm action="http://www.google.com/search" method="GET" style="font-size: 10pt">

    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 420, Column 102: 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="q" size="18" style="color: #008000; font-family: Tahoma; font-size: 10pt" />

    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 421, Column 56: 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 name="domains" type="hidden" value="mahshar.com">

    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 421, Column 57: end tag for "input" omitted, but OMITTAG NO was specified
    <input name="domains" type="hidden" value="mahshar.com">

    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 421, Column 1: start tag was here
    <input name="domains" type="hidden" value="mahshar.com">
  • Error Line 422, Column 64: 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 class="button" name="btnG" type="submit" value="جستجو" /><br />

    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 422, Column 70: document type does not allow element "br" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    <input class="button" name="btnG" type="submit" value="جستجو" /><br />

    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 423, Column 62: 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
    …t id="ggl_www" name="sitesearch" type="radio" value="" /><label for="ggl_www"> 

    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 423, Column 83: 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
    …t id="ggl_www" name="sitesearch" type="radio" value="" /><label for="ggl_www"> 

    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 424, Column 21: document type does not allow element "br" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    اینترنت</label><br />

    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 425, Column 31: syntax of attribute value does not conform to declared value
    <input id="ggl_site" checked="" name="sitesearch" type="radio" value="mahshar.c…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 425, Column 31: value of attribute "checked" cannot be ""; must be one of "checked"
    <input id="ggl_site" checked="" name="sitesearch" type="radio" value="mahshar.c…

    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 425, Column 85: 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
    …ame="sitesearch" type="radio" value="mahshar.com" /><label for="ggl_site">محشر 

    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 425, Column 107: 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
    …ame="sitesearch" type="radio" value="mahshar.com" /><label for="ggl_site">محشر 

    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 426, Column 19: document type does not allow element "br" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    دات کام</label><br><a href="keyboard.html">صفحه کلید فارسی:تایپ فارسی</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 426, Column 20: end tag for "br" omitted, but OMITTAG NO was specified
    دات کام</label><br><a href="keyboard.html">صفحه کلید فارسی:تایپ فارسی</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 426, Column 16: start tag was here
    دات کام</label><br><a href="keyboard.html">صفحه کلید فارسی:تایپ فارسی</a>
  • Error Line 426, Column 43: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    دات کام</label><br><a href="keyboard.html">صفحه کلید فارسی:تایپ فارسی</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 433, Column 37: element "center" undefined
    <td valign="top" width="480"><center>

    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 460, Column 43: there is no attribute "name"
    <iframe frameborder="0" height="650" name="fun" src="lolin.htm" width="437">

    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 460, Column 76: element "iframe" undefined
    <iframe frameborder="0" height="650" name="fun" src="lolin.htm" width="437">

    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 464, Column 13: there is no attribute "color"
    <font color="#FF5E00">کلیه محتوای این سایت برابر 

    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 464, Column 22: element "font" undefined
    <font color="#FF5E00">کلیه محتوای این سایت برابر 

    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 465, Column 42: end tag for "br" omitted, but OMITTAG NO was specified
    با قوانین جمهوری اسلامی ایران می باشد<br>

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

  • Info Line 465, Column 38: start tag was here
    با قوانین جمهوری اسلامی ایران می باشد<br>
  • Error Line 468, Column 42: required attribute "alt" not specified
    <img border="0" src="ads/mahshar_ads.gif"></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 468, Column 46: end tag for "img" omitted, but OMITTAG NO was specified
    <img border="0" src="ads/mahshar_ads.gif"></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 468, Column 1: start tag was here
    <img border="0" src="ads/mahshar_ads.gif"></a>
  • Error Line 475, Column 8: element "center" undefined
    <center>

    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 476, Column 67: element "iframe" undefined
    <iframe class="uframe" frameborder="0" scrolling="no" src="lu.htm">

    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 479, Column 70: required attribute "alt" not specified
    <img border="0" src="agahi/safarnet/120.gif" width="120" height="240"></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 479, Column 74: end tag for "img" omitted, but OMITTAG NO was specified
    <img border="0" src="agahi/safarnet/120.gif" width="120" height="240"></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 479, Column 1: start tag was here
    <img border="0" src="agahi/safarnet/120.gif" width="120" height="240"></a>
  • Error Line 485, Column 4: document type does not allow element "h2" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <h2>مطالب جدید روزانه حتماً ببینید</h2>

    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 511, Column 20: there is no attribute "direction"
    <marquee direction="right"><font size="1">محشر 

    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 511, Column 27: element "marquee" undefined
    <marquee direction="right"><font size="1">محشر 

    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 511, Column 39: there is no attribute "size"
    <marquee direction="right"><font size="1">محشر 

    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 511, Column 42: element "font" undefined
    <marquee direction="right"><font size="1">محشر 

    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 517, Column 60: end tag for "img" omitted, but OMITTAG NO was specified
    <img border="0" src="update/38.png" alt="فتوشاپ آنلاین"></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 517, Column 1: start tag was here
    <img border="0" src="update/38.png" alt="فتوشاپ آنلاین"></a>
  • Error Line 518, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

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

  • Info Line 518, Column 1: start tag was here
    <br>
  • Error Line 521, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

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

  • Info Line 521, Column 1: start tag was here
    <br>
  • Error Line 571, Column 8: element "center" undefined
    <center>

    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 572, Column 139: element "iframe" undefined
    …arginheight="0" marginwidth="0" scrolling="no" src="agahi/L210_100_A_left.htm">

    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 597, Column 15: element "font" undefined
    <font size="1">(پیش‌شماره تلفنی کشورهای 

    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 616, Column 8: element "center" undefined
    <center>

    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 617, Column 139: element "iframe" undefined
    …arginheight="0" marginwidth="0" scrolling="no" src="agahi/L210_100_C_left.htm">

    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 742, Column 46: end tag for "img" omitted, but OMITTAG NO was specified
    <img alt="طالع بینی چینی" src="i/ho.png"></td>

    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 742, Column 1: start tag was here
    <img alt="طالع بینی چینی" src="i/ho.png"></td>
  • Error Line 786, Column 36: end tag for "img" omitted, but OMITTAG NO was specified
    <img alt="تغذيه" src="i/nu.gif"></a></td>

    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 786, Column 1: start tag was here
    <img alt="تغذيه" src="i/nu.gif"></a></td>
  • Error Line 830, Column 73: element "iframe" undefined
    <iframe frameborder="0" height="260" src="mahshar/1_170.htm" width="217">

    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 832, Column 8: element "center" undefined
    <center><a href="chat" title="چت روم">

    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 1019, Column 8: element "center" undefined
    <center><a href="font">

    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 1022, Column 120: required attribute "alt" not specified
    …ok.com/sharer.php?u=http://mahshar.com/" target="_blank"><img src="i/fb.png" />

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

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

  • Error Line 1025, Column 24: required attribute "alt" not specified
    <img src="i/icio.png" />

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

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

  • Error Line 1027, Column 126: required attribute "alt" not specified
    …mit?phase=2&amp;url=http://mahshar.com/" target="_blank"><img src="i/di.png" />

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

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

  • Warning Line 1029, Column 183: character "<" is the first character of a delimiter but occurred as data
    …ال و طالع بینی کارت تبریک فارسی و هزارن امکانات محشر دیگر<img src="i/st.png" />

    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 1029, Column 195: NET-enabling start-tag not immediately followed by null end-tag
    …ال و طالع بینی کارت تبریک فارسی و هزارن امکانات محشر دیگر<img src="i/st.png" />

    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 1029, Column 25: literal is missing closing delimiter
    <a rel="nofollow" href="http://www.stumbleupon.com/submit?url=http://mahshar.co…

    Did you forget to close a (double) quote mark?

  • Error Line 1032, Column 22: required attribute "alt" not specified
    <img src="i/tw.png" />

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

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

  • Error Line 1037, Column 11: element "g:plusone" undefined
    <g:plusone></g:plusone>

    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 1039, Column 8: required attribute "type" not specified
    <script>(function(d, s, id) {

    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 1046, Column 32: there is no attribute "data-href"
    <div class="fb-like" data-href="http://www.mahshar.com/" data-send="true" data-…

    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 1046, Column 68: there is no attribute "data-send"
    …f="http://www.mahshar.com/" data-send="true" data-layout="button_count" data-w…

    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 1046, Column 87: there is no attribute "data-layout"
    …ar.com/" data-send="true" data-layout="button_count" data-width="450" data-sho…

    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 1046, Column 113: there is no attribute "data-width"
    …true" data-layout="button_count" data-width="450" data-show-faces="true"></div>

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

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

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

  • Error Line 1046, Column 135: there is no attribute "data-show-faces"
    …true" data-layout="button_count" data-width="450" data-show-faces="true"></div>

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

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

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

  • Error Line 1057, Column 5: end tag for element "td" which is not open
    </td>

    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 1058, Column 5: end tag for element "tr" which is not open
    </tr>

    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 1059, Column 8: end tag for element "table" which is not open
    </table>

    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 1061, Column 18: there is no attribute "language"
    <script language="JavaScript" src="click.js"></script>

    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 1061, Column 45: required attribute "type" not specified
    <script language="JavaScript" src="click.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>.

Visitor Analysis

Daily Visitor
  • 7.000 visits
Daily Visitor