takdokhtar.ir

X بستن تبلیغات X بستن تبلیغات سایت تفریحی تک دختر انجمن تک دختر کاملا دوستانه و به دور از هر گونه دعوا و اضطرابی میباشد در انجمن تفریحی ما مسابقات گوناگون و جذابی ...

This data was last updated from 02-08-2013 05:31:53  (update).

Overview Info



  • Domain Name
    takdokhtar.ir
  • Favicon
  • Alexa Rank
    #194755
  • Google Page Rank
    1
  • Ip Address
    88.198.9.154
  • Page Size
    68.7 KB
  • Images
    3 GIF, 0 JPG, 112 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    5 1 0 6 0 0

Website Meta Analysis



  • Title
    سایت تفریحی تک دختر
  • Meta Keyword
    تفریحی، دختر، خنده دار، عکس، انجمن , AgW0q0ZGvHXjl-h-p5Hwjdewd9E
  • Meta Description
    X بستن تبلیغات X بستن تبلیغات سایت تفریحی تک دختر انجمن تک دختر کاملا دوستانه و به دور از هر گونه دعوا و اضطرابی میباشد در انجمن تفریحی ما مسابقات گوناگون و جذابی همه روزه ایجاد میشود، تا انجمن شادابی و تنوع خود را از دست ندهد صندلی داغ های ...

Technical Analysis



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

Hyper Text Transfer Protocol (HTTP) header show data header response from takdokhtar.ir.

HTML Analysis

  • content-encoding: gzip
  • vary: Accept-Encoding
  • date: Fri, 02 Aug 2013 17:31:47 GMT
  • server: LiteSpeed
  • connection: close
  • x-powered-by: PHP/5.3.25
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for takdokhtar.ir

DNS Analysis


DNS servers
ns53.mihanwebhost.com
ns54.mihanwebhost.com [5.9.16.61]


DNS Records

Answer records
takdokhtar.ir MX
preference: 0
exchange: takdokhtar.ir
14400s
takdokhtar.ir SOA
server: ns53.mihanwebhost.com
email: dzr323@gmail.com
serial: 2013031501
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
takdokhtar.ir NS  ns54.mihanwebhost.com 86400s
takdokhtar.ir NS  ns53.mihanwebhost.com 86400s
takdokhtar.ir A 5.9.16.61 14400s

Authority records

Additional records
takdokhtar.ir A 5.9.16.61 14400s

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 102 Errors
  • 1 Warnings
Ratio Text/Html
  • 0.7121684090747458
Message Error
  • Error Line 6, Column 7: required attribute "type" not specified
    <style>

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

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

  • Error Line 27, Column 27: document type does not allow element "div" here; assuming missing "object" start-tag
    <div style="display:none;"><h1>سایت تفریحی تک دختر</h1></div>
  • Error Line 30, Column 67: document type does not allow element "meta" here
    <meta name="alexaVerifyID" content="AgW0q0ZGvHXjl-h-p5Hwjdewd9E" />

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

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

  • Error Line 31, Column 67: document type does not allow element "meta" here
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">

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

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

  • Error Line 31, Column 68: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">

    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 31, Column 1: start tag was here
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  • Error Line 32, Column 43: document type does not allow element "meta" here
    <meta name="designer" content="Ali Milani">

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

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

  • Error Line 32, Column 44: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="designer" content="Ali Milani">

    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 32, Column 1: start tag was here
    <meta name="designer" content="Ali Milani">
  • Error Line 33, Column 16: there is no attribute "itemprop"
    <meta itemprop="image" content="http://takdokhtar.ir/">

    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 33, Column 55: document type does not allow element "meta" here
    <meta itemprop="image" content="http://takdokhtar.ir/">

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

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

  • Error Line 33, Column 56: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta itemprop="image" content="http://takdokhtar.ir/">

    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 33, Column 1: start tag was here
    <meta itemprop="image" content="http://takdokhtar.ir/">
  • Error Line 34, Column 52: document type does not allow element "meta" here
    <meta itemprop="name" content="سایت تفریحی تک دختر">

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

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

  • Error Line 34, Column 53: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta itemprop="name" content="سایت تفریحی تک دختر">

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

  • Info Line 34, Column 1: start tag was here
    <meta itemprop="name" content="سایت تفریحی تک دختر">
  • Error Line 35, Column 38: document type does not allow element "meta" here
    <meta name="language" content="Farsi">

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

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

  • Error Line 35, Column 39: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="language" content="Farsi">

    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 35, Column 1: start tag was here
    <meta name="language" content="Farsi">
  • Error Line 36, Column 61: document type does not allow element "meta" here
    <meta name="designerUrl" content="http://www.takdokhtar.ir/">

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

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

  • Error Line 36, Column 62: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="designerUrl" content="http://www.takdokhtar.ir/">

    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 36, Column 1: start tag was here
    <meta name="designerUrl" content="http://www.takdokhtar.ir/">
  • Error Line 37, Column 47: document type does not allow element "meta" here
    <meta name="classification" content="تفریحی" />

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

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

  • Error Line 38, Column 59: document type does not allow element "meta" here
    <meta http-equiv="reply-to" content="info@takdokhtar.ir" />

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

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

  • Error Line 39, Column 45: document type does not allow element "meta" here
    <meta name="robots" content="Index,Follow" />

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

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

  • Error Line 40, Column 65: document type does not allow element "meta" here
    <meta name="copyright" content="Copyright by Tak Dokhtar 2012" />

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

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

  • Error Line 41, Column 70: document type does not allow element "meta" here
    <meta itemprop="description" content="بزگترین سایت تفريحي فارسی زبان">

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

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

  • Error Line 41, Column 71: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta itemprop="description" content="بزگترین سایت تفريحي فارسی زبان">

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

  • Info Line 41, Column 1: start tag was here
    <meta itemprop="description" content="بزگترین سایت تفريحي فارسی زبان">
  • Error Line 42, Column 97: document type does not allow element "meta" here
    …ds" content="تفریحی، دختر، خنده دار، عکس، انجمن , AgW0q0ZGvHXjl-h-p5Hwjdewd9E">

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

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

  • Error Line 42, Column 98: end tag for "meta" omitted, but OMITTAG NO was specified
    …ds" content="تفریحی، دختر، خنده دار، عکس، انجمن , AgW0q0ZGvHXjl-h-p5Hwjdewd9E">

    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 42, Column 1: start tag was here
    <meta name="keywords" content="تفریحی، دختر، خنده دار، عکس، انجمن , AgW0q0ZGvHX…
  • Error Line 43, Column 41: document type does not allow element "meta" here
    <meta name="author" content="Ali Milani">

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

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

  • Error Line 43, Column 42: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="author" content="Ali Milani">

    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 43, Column 1: start tag was here
    <meta name="author" content="Ali Milani">
  • Error Line 44, Column 7: end tag for "object" omitted, but OMITTAG NO was specified
    </head>

    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 27, Column 1: start tag was here
    <div style="display:none;"><h1>سایت تفریحی تک دختر</h1></div>
  • Error Line 51, Column 12: there is no attribute "align"
    <div align="left" style="margin-left: 2%;">

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

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

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

  • Error Line 52, Column 12: element "takdokhtar" undefined
    <takdokhtar>

    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 54, Column 21: there is no attribute "data-title"
    		<li><a data-title="خانه" href="#"></a></li>

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

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

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

  • Error Line 63, Column 68: 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
    <a class="navidiranian-logo" href="http://www.forum.takdokhtar.ir/"></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 66, Column 14: there is no attribute "name"
    <iframe name="lastpost" src="http://www.forum.takdokhtar.ir/last.php" border="0…

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

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

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

  • Error Line 66, Column 29: there is no attribute "src"
    <iframe name="lastpost" src="http://www.forum.takdokhtar.ir/last.php" border="0…

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

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

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

  • Error Line 66, Column 78: there is no attribute "border"
    ….forum.takdokhtar.ir/last.php" border="0" frameborder="0" width="550" height="…

    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 66, Column 94: there is no attribute "frameborder"
    …r.ir/last.php" border="0" frameborder="0" width="550" height="200" scrolling="…

    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 66, Column 104: there is no attribute "width"
    …php" border="0" frameborder="0" width="550" height="200" scrolling="yes"></ifr…

    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 66, Column 117: there is no attribute "height"
    …" border="0" frameborder="0" width="550" height="200" scrolling="yes"></iframe>

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

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

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

  • Error Line 66, Column 133: there is no attribute "scrolling"
    …" border="0" frameborder="0" width="550" height="200" scrolling="yes"></iframe>

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

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

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

  • Error Line 66, Column 138: element "iframe" undefined
    …" border="0" frameborder="0" width="550" height="200" scrolling="yes"></iframe>

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

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

    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 68, Column 10: end tag for element "br" which is not open
    </br></br></br></br></br></br></br></br></br>

    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 68, Column 15: end tag for element "br" which is not open
    </br></br></br></br></br></br></br></br></br>

    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 68, Column 20: end tag for element "br" which is not open
    </br></br></br></br></br></br></br></br></br>

    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 68, Column 25: end tag for element "br" which is not open
    </br></br></br></br></br></br></br></br></br>

    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 68, Column 30: end tag for element "br" which is not open
    </br></br></br></br></br></br></br></br></br>

    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 68, Column 35: end tag for element "br" which is not open
    </br></br></br></br></br></br></br></br></br>

    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 68, Column 40: end tag for element "br" which is not open
    </br></br></br></br></br></br></br></br></br>

    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 68, Column 45: end tag for element "br" which is not open
    </br></br></br></br></br></br></br></br></br>

    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 71, Column 21: there is no attribute "target"
           <form target='_blank' method=get action=http://www.google.com/search cla…

    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 71, Column 37: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
           <form target='_blank' method=get action=http://www.google.com/search cla…
  • Error Line 71, Column 48: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …orm target='_blank' method=get action=http://www.google.com/search class="form…
  • Error Line 71, Column 54: NET-enabling start-tag not immediately followed by null end-tag
    …rm target='_blank' method=get action=http://www.google.com/search class="form">

    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 71, Column 54: character data is not allowed here
    …rm target='_blank' method=get action=http://www.google.com/search class="form">

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 72, Column 67: 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
    … name="btnG"value="" id="searchSubmit">    <input onfocus="if(this.value=='متن…

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

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

  • Error Line 72, Column 68: end tag for "input" omitted, but OMITTAG NO was specified
    …name="btnG"value="" id="searchSubmit">    <input onfocus="if(this.value=='متن …

    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 72, Column 9: start tag was here
            <input type="submit" name="btnG"value="" id="searchSubmit">    <input o…
  • Error Line 72, Column 252: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …alue="متن مورد نظر را وارد كنيد"  name=q size=15 maxlength="300" class="input">
  • Error Line 72, Column 259: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …alue="متن مورد نظر را وارد كنيد"  name=q size=15 maxlength="300" class="input">
  • Error Line 72, Column 291: 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
    …alue="متن مورد نظر را وارد كنيد"  name=q size=15 maxlength="300" class="input">

    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 72, Column 292: end tag for "input" omitted, but OMITTAG NO was specified
    …alue="متن مورد نظر را وارد كنيد"  name=q size=15 maxlength="300" class="input">

    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 72, Column 72: start tag was here
    …="btnG"value="" id="searchSubmit">    <input onfocus="if(this.value=='متن مورد…
  • Error Line 73, Column 61: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …     <input value='http://www.forum.takdokhtar.ir' type=hidden name=sitesearch>
  • Error Line 73, Column 73: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …     <input value='http://www.forum.takdokhtar.ir' type=hidden name=sitesearch>
  • Error Line 73, Column 83: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …     <input value='http://www.forum.takdokhtar.ir' type=hidden name=sitesearch>

    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 73, Column 84: end tag for "input" omitted, but OMITTAG NO was specified
    …     <input value='http://www.forum.takdokhtar.ir' type=hidden name=sitesearch>

    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 73, Column 10: start tag was here
             <input value='http://www.forum.takdokhtar.ir' type=hidden name=sitesea…
  • Error Line 74, Column 19: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
          <input type=hidden name=ie value=UTF-8><input type=hidden name=oe value=U…
  • Error Line 74, Column 31: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
          <input type=hidden name=ie value=UTF-8><input type=hidden name=oe value=U…
  • Error Line 74, Column 40: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …     <input type=hidden name=ie value=UTF-8><input type=hidden name=oe value=U…
  • Error Line 74, Column 45: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …<input type=hidden name=ie value=UTF-8><input type=hidden name=oe value=UTF-8>…

    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 74, Column 46: end tag for "input" omitted, but OMITTAG NO was specified
    …input type=hidden name=ie value=UTF-8><input type=hidden name=oe value=UTF-8><…

    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 74, Column 7: start tag was here
          <input type=hidden name=ie value=UTF-8><input type=hidden name=oe value=U…
  • Error Line 74, Column 58: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … type=hidden name=ie value=UTF-8><input type=hidden name=oe value=UTF-8></form>
  • Error Line 74, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … type=hidden name=ie value=UTF-8><input type=hidden name=oe value=UTF-8></form>
  • Error Line 74, Column 79: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … type=hidden name=ie value=UTF-8><input type=hidden name=oe value=UTF-8></form>
  • Error Line 74, Column 84: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    … type=hidden name=ie value=UTF-8><input type=hidden name=oe value=UTF-8></form>

    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 74, Column 91: end tag for element "form" which is not open
    … type=hidden name=ie value=UTF-8><input type=hidden name=oe value=UTF-8></form>

    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 74, Column 91: end tag for "input" omitted, but OMITTAG NO was specified
    … type=hidden name=ie value=UTF-8><input type=hidden name=oe value=UTF-8></form>

    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 74, Column 46: start tag was here
    …input type=hidden name=ie value=UTF-8><input type=hidden name=oe value=UTF-8><…
  • Error Line 74, Column 91: character data is not allowed here
    … type=hidden name=ie value=UTF-8><input type=hidden name=oe value=UTF-8></form>

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 78, Column 5: end tag for element "br" which is not open
    </br></br></br></br>

    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 78, Column 10: end tag for element "br" which is not open
    </br></br></br></br>

    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 78, Column 15: end tag for element "br" which is not open
    </br></br></br></br>

    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 78, Column 20: end tag for element "br" which is not open
    </br></br></br></br>

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

    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 83, Column 10: end tag for element "br" which is not open
    </br></br></br></br>

    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 83, Column 15: end tag for element "br" which is not open
    </br></br></br></br>

    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 83, Column 20: end tag for element "br" which is not open
    </br></br></br></br>

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

    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 88, Column 6: end tag for element "div" which is not open
    </div>

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

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

    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 98, Column 84: there is no attribute "language"
    …"rtl" align="right"></div><script language="JavaScript" type="text/javascript">

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

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

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

  • Error Line 209, Column 24: document type does not allow element "style" here
    	<style type="text/css">

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

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

  • Error Line 245, Column 61: there is no attribute "target"
    …w.takdokhtar.ir/" title="خانه" target=_blank><img src="http://www.takdokhtar.i…

    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 245, Column 61: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …w.takdokhtar.ir/" title="خانه" target=_blank><img src="http://www.takdokhtar.i…
  • Error Line 245, Column 258: required attribute "alt" not specified
    … onmouseout="this.src='http://www.takdokhtar.ir/menu_img/home.png'" /></a></li>

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

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

  • Error Line 246, Column 68: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    ….takdokhtar.ir/" title="انجمن" target=_blank><img src="http://www.takdokhtar.i…
  • Error Line 246, Column 268: required attribute "alt" not specified
    …onmouseout="this.src='http://www.takdokhtar.ir/menu_img/forum.png'" /></a></li>

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

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

  • Error Line 247, Column 79: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ar.ir/" title="جوک و اس ام اس" target=_blank><img src="http://www.takdokhtar.i…
  • Error Line 247, Column 273: required attribute "alt" not specified
    …" onmouseout="this.src='http://www.takdokhtar.ir/menu_img/sms.png'" /></a></li>

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

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

  • Error Line 248, Column 257: required attribute "alt" not specified
    …'" onmouseout="this.src='http://www.takdokhtar.ir/menu_img/up.png'" /></a></li>

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

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

  • Error Line 249, Column 264: required attribute "alt" not specified
    … onmouseout="this.src='http://www.takdokhtar.ir/menu_img/link.png'" /></a></li>

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

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

  • Error Line 250, Column 256: required attribute "alt" not specified
    … onmouseout="this.src='http://www.takdokhtar.ir/menu_img/love.png'" /></a></li>

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

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

  • Error Line 251, Column 267: required attribute "alt" not specified
    …mouseout="this.src='http://www.takdokhtar.ir/menu_img/contact.png'" /></a></li>

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

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

  • Error Line 256, Column 11: 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 259, Column 92: 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
    …ats.aspx?code=2904268" target="_blank">&#1570;&#1605;&#1575;&#1585;</a></noscr…

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

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

Visitor Analysis

Daily Visitor
  • 828 visits

In Page Analysis