شبکه مترجمین ایران پیشرو در ارائه خدمات نوین ترجمه . ترجمه فارسی ترجمه انگلیسی و 37 زبان ، ترجمه متن ، کتاب و مقاله در زمینه های تخصصی نظیر مدیریت ، کامپیوتر ...

worldtranslators.net
  • Domain Name
    worldtranslators.net
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #157608
  • Page Size
    52.5 KB
  • Ip Address
    94.232.175.116
  • Heading
    H1: 7, H2: 0, H3: 0, H4: 0, H5: 4, H6: 0
  • Images
    33 GIF, 2 JPG, 39 PNG

Website Meta Analysis

  • Title
    ترجمه فارسی ترجمه انگلیسی ترجمه متن به 37 زبان - شبکه مترجمین ایران
  • Meta Keyword
    ترجمه،tarjomeh,motarjem,انگلیسی به فارسی, فارسی به انگلیسی , مترجم ، ترجمه متن ترجمه کتاب و مقاله به فارسی, آلمانی به فارسی, فارسی به آلمانی, عربی به فارسی, فارسی به عربی, ترکی استانبولی به فارسی , فارسی به ترکی استانبولی ,اسپانیایی به فارسی, فارسی به اسپانیایی, ایتالیایی به فارسی, فارسی به ایتالیایی, روسی به فارسی, فارسی به روسی, چینی به فارسی, فارسی به چینی, کره ای به فارسی, فارسی به کره ای, ترجمه ,مترجم, استخدام مترجم, سایت ترجمه متن انگلیسی, سایت ترجمه آنلاین, سایت ترجمه انگلیسی, ترجمه آنلاین, ترجمه فارسی به انگلیسی, ترجمه فارسی به انگلیسی, ترجمه انگلیسی به فارسی, مترجم فارسی, مترجم انگلیسی, دارالترجمه, خدمات ترجمه, ترجمه تخصصی,ترجمه فارسی
  • Meta Description
    شبکه مترجمین ایران پیشرو در ارائه خدمات نوین ترجمه . ترجمه فارسی ترجمه انگلیسی و 37 زبان ، ترجمه متن ، کتاب و مقاله در زمینه های تخصصی نظیر مدیریت ، کامپیوتر ، برق الکترونیک ، پزشکی. تنها موسسه دارای استاندارد En15038 در ایران . سفارش آنلاین ، قیمت گذاری رایگان ، کنترل کیفی ، قیمت ترجمه عادلانه ، تحویل در اسرع وقت.

Technical Analysis

  • Webserver
    Microsoft-IIS/7.5
  • Ip Address
    94.232.175.116
  • Domain Age
    4 Years, 5 Months, 16 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from worldtranslators.net.

HTML Analysis

  • cache-control: private
  • content-type: text/html; charset=utf-8
  • content-encoding: gzip
  • vary: Accept-Encoding
  • server: Microsoft-IIS/7.5
  • x-aspnet-version: 2.0.50727
  • x-powered-by: ASP.NET
  • date: Fri, 16 Aug 2013 22:15:06 GMT
  • content-length: 19339
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for worldtranslators.net

DNS Analysis


DNS servers
dns1.hostfa.com
dns2.hostfa.com
dns3.hostfa.com
dns4.hostfa.com


DNS Records

Answer records
worldtranslators.net NS  dns2.hostfa.com 38400s
worldtranslators.net TXT v=spf1 redirect=_spf.mailhostbox.com 38400s
worldtranslators.net NS  dns3.hostfa.com 38400s
worldtranslators.net NS  dns1.hostfa.com 38400s
worldtranslators.net SOA
server: dns1.hostfa.com
email: saeednejad@gmail.com
serial: 2012102901
refresh: 7200
retry: 7200
expire: 172800
minimum ttl: 7200
14400s
worldtranslators.net A 94.232.175.116 28800s
worldtranslators.net NS  dns4.hostfa.com 38400s

Authority records

Additional records

IP 94.232.175.116 Analysis

  • Country Code
    IR
  • Country Code3
    IRN
  • Country Name
    Iran, Islamic Republic of
  • City
    AS
  • Continent Code
    32° North
  • Latitude
    53.
  • Longitude
  • No whois ip data for 94.232.175.116

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 36 Errors
  • 11 Warnings
Ratio Text/Html
  • 0.5636004913821986
Message Error
  • Error Line 47, Column 16: there is no attribute "name"
        <form name="aspnetForm" method="post" action="home.aspx" id="aspnetForm">

    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 116: 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" id="__VIEWSTATE" value="/wEPDwUKMTgwNDUzMzM3N2QYAQUIY3RsMDAkbXYPD2RmZA==" />

    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 64, Column 62: there is no attribute "target"
    …tp://satraa.com" title="ساترا" target="_blank">سامانه ترجمه رسمی آنلاین</a></l…

    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 77, Column 87: there is no attribute "color"
    …"ctl00_Password" id="ctl00_Label4"><font color="Black">کلمه عبور</font></label>

    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 77, Column 94: element "font" undefined
    …"ctl00_Password" id="ctl00_Label4"><font color="Black">کلمه عبور</font></label>

    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 84, Column 79: element "font" undefined
    …              <span id="ctl00_LabelLoginError"><font color="Red"></font></span>

    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).
  • Warning Line 96, Column 30: reference not terminated by REFC delimiter
                        </a>&nbsp<a href="/Fr/">

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

  • Warning Line 99, Column 30: reference not terminated by REFC delimiter
                        </a>&nbsp<a href="/Ru/">

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

  • Error Line 122, Column 62: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
                                        <div class="logoEidImage">

    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 190, Column 38: there is no attribute "language"
                        <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 210, Column 88: NET-enabling start-tag not immediately followed by null end-tag
    … ورود به سایت" src="/cdn/img/Login.png"/ height="75px" width="75px"/></a><br />

    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 210, Column 88: end tag for "img" omitted, but OMITTAG NO was specified
    … ورود به سایت" src="/cdn/img/Login.png"/ height="75px" width="75px"/></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 210, Column 29: start tag was here
                                <img alt="ثبت نام و ورود به سایت" src="/cdn/img/Log…
  • Error Line 567, Column 80: there is no attribute "border"
    …/tgif.gif" width="1" height="1" border="0" alt="ترجمه متن" title="ترجمه متن" />

    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 776, Column 37: there is no attribute "alt"
                                <li alt="1"></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 809, Column 84: there is no attribute "temp_src"
    …"ctl00_lblNamadLogo"><iframe temp_src='http://enamad.ir/trustseal/symbol.aspx'…

    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 809, Column 129: there is no attribute "src"
    …/enamad.ir/trustseal/symbol.aspx' src='http://enamad.ir/trustseal/symbol.aspx'…

    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 809, Column 176: there is no attribute "width"
    …namad.ir/trustseal/symbol.aspx' width='125' scrolling='no' height='140' frameb…

    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 809, Column 192: there is no attribute "scrolling"
    …al/symbol.aspx' width='125' scrolling='no' height='140' frameborder='0' style=…

    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 809, Column 204: there is no attribute "height"
    …px' width='125' scrolling='no' height='140' frameborder='0' style='margin: 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 809, Column 222: there is no attribute "frameborder"
    …rolling='no' height='140' frameborder='0' style='margin: 0; padding: 0; border…

    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 809, Column 232: there is no attribute "style"
    …o' height='140' frameborder='0' style='margin: 0; padding: 0; border: 1px'> </…

    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 809, Column 268: element "iframe" undefined
    …0' frameborder='0' style='margin: 0; padding: 0; border: 1px'> </iframe></span>

    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 815, Column 53: there is no attribute "size"
                                        <g:plusone size="tall"></g:plusone>

    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 815, Column 59: element "g:plusone" undefined
                                        <g:plusone size="tall"></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).
  • Warning Line 939, Column 21: character "<" is the first character of a delimiter but occurred as data
            if(wordCount<250)

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 943, Column 107: cannot generate system identifier for general entity "l"
    …t//WordCountPop.aspx?f='  + field + "&l=" + lang + "&w=" + wordCount , '_blank…

    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 943, Column 107: general entity "l" not defined and no default entity
    …t//WordCountPop.aspx?f='  + field + "&l=" + lang + "&w=" + wordCount , '_blank…

    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 943, Column 108: reference not terminated by REFC delimiter
    …//WordCountPop.aspx?f='  + field + "&l=" + lang + "&w=" + wordCount , '_blank'…

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

  • Error Line 943, Column 108: reference to entity "l" for which no system identifier could be generated
    …//WordCountPop.aspx?f='  + field + "&l=" + lang + "&w=" + wordCount , '_blank'…

    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 943, Column 106: entity was defined here
    …et//WordCountPop.aspx?f='  + field + "&l=" + lang + "&w=" + wordCount , '_blan…
  • Warning Line 943, Column 122: cannot generate system identifier for general entity "w"
    ….aspx?f='  + field + "&l=" + lang + "&w=" + wordCount , '_blank', 'width=680, …

    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 943, Column 122: general entity "w" not defined and no default entity
    ….aspx?f='  + field + "&l=" + lang + "&w=" + wordCount , '_blank', 'width=680, …

    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 943, Column 123: reference not terminated by REFC delimiter
    …aspx?f='  + field + "&l=" + lang + "&w=" + wordCount , '_blank', 'width=680, h…

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

  • Error Line 943, Column 123: reference to entity "w" for which no system identifier could be generated
    …aspx?f='  + field + "&l=" + lang + "&w=" + wordCount , '_blank', 'width=680, h…

    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 943, Column 121: entity was defined here
    …p.aspx?f='  + field + "&l=" + lang + "&w=" + wordCount , '_blank', 'width=680,…
  • Warning Line 954, Column 27: character "<" is the first character of a delimiter but occurred as data
            for (var i = 0; i < str.length; i++) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 956, Column 25: character "<" is the first character of a delimiter but occurred as data
                if (oneChar < 48 || oneChar > 57) { alert("تعداد کلمات باید عدد صحی…

    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 1006, Column 74: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
                                            <span id="ctl00_lblLastCourse"><p>

    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 1008, Column 3: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <p>

    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 1010, Column 47: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <p style="text-align: right; font-size: 14px;">

    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 1109, Column 119: document type does not allow element "a" here
    … 'book.c' + 'om/T' + 'ran' + 'snet.ir">' + '<img alt="فی' + 'سب' + 'وک شبکه مت…

    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 1109, Column 257: end tag for element "a" which is not open
    … + 'س' + 'بو' + 'ک شبکه مترجمین ایران" src="/cdn/img/fb.png" /></a>' + '</a>');

    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 1110, Column 93: document type does not allow element "a" here
    …dtranslat' + 'ors.net/login.' + 'aspx"><im' + 'g alt="SSL" src=' + '"/cdn/img/…

    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 1110, Column 97: an attribute specification must start with a name or name token
    …nslat' + 'ors.net/login.' + 'aspx"><im' + 'g alt="SSL" src=' + '"/cdn/img/icon…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 1110, Column 97: element "im" undefined
    …nslat' + 'ors.net/login.' + 'aspx"><im' + 'g alt="SSL" src=' + '"/cdn/img/icon…

    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 1110, Column 161: end tag for "im" omitted, but OMITTAG NO was specified
    …+ 'aspx"><im' + 'g alt="SSL" src=' + '"/cdn/img/icon_padloc' + 'k.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 1110, Column 94: start tag was here
    …translat' + 'ors.net/login.' + 'aspx"><im' + 'g alt="SSL" src=' + '"/cdn/img/i…
  • Warning Line 830, Column 17: reference to non-existent ID "ddlFeild"
        <label for="ddlFeild">

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

  • Warning Line 870, Column 17: reference to non-existent ID "ddllang"
        <label for="ddllang">

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

Visitor Analysis

Daily Visitor
  • 1.143 visits