bartarinha.ir

پربازدیدترین مجله اینترنتی ایران در زمینه های سبک زندگی سلامت دکوراسیون موفقیت کودک می باشد ...

Display Widget for this domain on your website. Click Here
This data was last updated from 09-01-2013 04:05:15  (update).

Overview Info

  • Domain Name
    bartarinha.ir
  • Favicon
  • Alexa Rank
    #1061
  • Google Page Rank
    PR 4
  • Ip Address
    94.182.146.16
  • Page Size
    139.4 KB
  • Images
    245 GIF, 68 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 96 13 0 0 0

Website Meta Analysis



  • Title
    مجله اینترنتی برترین ها | پورتال خبری و سبک زندگی
  • Meta Keyword
    مجله اینترنتی،برترین ها،سبک زندگی،سلامت،دکوراسیون،موفقیت،کودک،سرگرمی
  • Meta Description
    پربازدیدترین مجله اینترنتی ایران در زمینه های سبک زندگی سلامت دکوراسیون موفقیت کودک می باشد

Technical Analysis



  • Webserver
    Apache/2.2.3 (CentOS)
  • Ip Address
    94.182.146.16
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Wed, 09 Jan 2013 04:05:16 GMT
  • server: Apache/2.2.3 (CentOS)
  • x-powered-by: PHP/5.2.17
  • expires: Mon, 26 Jul 1997 05:00:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-length: 23179
  • content-type: text/html; charset=utf-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
% This is the IRNIC Whois server v1.6.2.
% Available on web at http://whois.nic.ir/
% Find the terms and conditions of use on http://www.nic.ir/
%
% This server uses UTF-8 as the encoding for requests and responses.

% NOTE: This output has been filtered.

% Information related to 'bartarinha.ir'


domain: bartarinha.ir
ascii: bartarinha.ir
remarks: (Domain Holder) Seyed Morteza Javadi Moghadam
remarks: (Domain Holder Address) Unit 1, Second Floor, No. 43, Hedyeh Deadend, Shariati St.,, Tehran, Tehran, IR
holder-c: mj52-irnic
admin-c: mj52-irnic
tech-c: mj52-irnic
nserver: ns1.sepehrict.com
nserver: ns2.sepehrict.com
last-updated: 2011-03-17
expire-date: 2015-08-14
source: IRNIC # Filtered

nic-hdl: mj52-irnic
person: Seyed Morteza Javadi Moghadam
e-mail: email
address: Unit 1, Second Floor, No. 43, Hedyeh Deadend, Shariati St.,, Tehran, Tehran, IR
phone: 0098-21-2264319
fax-no: 0098-21-2264319
source: IRNIC # Filtered

DNS Analysis


DNS servers
ns2.iransamaneh.com [94.182.130.2]
ns1.iransamaneh.com [94.182.146.2]

DNS Records

Answer records
bartarinha.ir MX
preference: 10
exchange: mail.bartarinha.ir
300s
bartarinha.ir TXT v=spf1 +a +mx -all 300s
bartarinha.ir SOA
server: ns1.iransamaneh.com
email: admin@iransamaneh.com
serial: 2012110400
refresh: 7200
retry: 3600
expire: 604800
minimum ttl: 300
300s
bartarinha.ir NS  ns1.iransamaneh.com 300s
bartarinha.ir NS  ns2.iransamaneh.com 300s
bartarinha.ir A 94.182.146.16 300s

Authority records

Additional records
mail.bartarinha.ir A 94.182.146.16 300s
ns1.iransamaneh.com A 94.182.146.2 300s
ns2.iransamaneh.com A 94.182.130.2 300s

IP 94.182.146.16 Analysis

  • Country Code
    IR
  • Country Code3
    IRN
  • Country Name
    Iran, Islamic Republic of
  • City
    Tehran
  • Continent Code
    AS
  • Latitude
    32.7026
  • Longitude
    51.1537
  • No whois ip data for 94.182.146.16

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 19 Errors
  • 4 Warnings
Ratio Text/Html
  • 0.7755029138182226
Message Error
  • Warning Line 1, Column 484: NET-enabling start-tag requires SHORTTAG YES
    …content="TURy8zj79J8oII23RLk6Jc2jLT4" /> <meta name="google-site-verification"…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1, Column 485: character data is not allowed here
    …ontent="TURy8zj79J8oII23RLk6Jc2jLT4" /> <meta name="google-site-verification" …

    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.
  • Warning Line 1, Column 579: NET-enabling start-tag requires SHORTTAG YES
    …gle-site-verification" content="YGcpxQUutVQ0ZPkSICdbVF11mw31uYA0iMx1AOIr38k" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 2, Column 93: NET-enabling start-tag requires SHORTTAG YES
    …gle-site-verification" content="YGcpxQUutVQ0ZPkSICdbVF11mw31uYA0iMx1AOIr38k" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 3, Column 71: NET-enabling start-tag requires SHORTTAG YES
    …nt="072E435796F114C6A87146843B114626" /> <meta http-equiv="X-UA-Compatible" co…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 3, Column 1828: there is no attribute "HEIGHT"
    …0" cellspacing="0" width="468" height="88" align="center" style="text-align: c…

    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 3, Column 1839: there is no attribute "ALIGN"
    …ing="0" width="468" height="88" align="center" style="text-align: center;"> 		…

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

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

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

  • Error Line 3, Column 1921: there is no attribute "WIDTH"
    …<tr> 							<td valign="middle" width="468" height="88"> 								 	<div class …

    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 3, Column 1934: there is no attribute "HEIGHT"
    …td valign="middle" width="468" height="88"> 								 	<div class =ads style="d…

    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 9, Column 4050: there is no attribute "TARGET"
    …inha.ir/fa/ads/redirect/a/404" target="_blank"><img alt="" style="width:150px;…

    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 15, Column 794: there is no attribute "BORDER"
    …s/fa/main/img/bolet_r_sar.gif" border="0"> 						<a class="title5" href="/fa/n…

    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 135: duplicate specification of attribute "TARGET"
    …nk" href="/fa/news/40119/انجمن-سینماگران-بزرگ-غائب-در-جشنواره" target="_blank">

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

  • Error Line 50, Column 130: duplicate specification of attribute "TARGET"
    …blank" href="/fa/news/39837/تاثیرگذارترین-مردان-و-زنان-جهان-5" target="_blank">

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

  • Error Line 67, Column 133: duplicate specification of attribute "TARGET"
    …ank" href="/fa/news/40213/عجايب-شش‌گانه-روز-نخست-نمایشگاه-ces" target="_blank">

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

  • Error Line 84, Column 132: duplicate specification of attribute "TARGET"
    …ank" href="/fa/news/39971/دستور-تهیه-6-غذای-بی-نظیر-ایتالیایی" target="_blank">

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

  • Error Line 101, Column 124: duplicate specification of attribute "TARGET"
    …"_blank" href="/fa/news/37843/همه-چیز-درباره-خرید-عطر-و-ادکلن" target="_blank">

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

  • Error Line 114, Column 23: end tag for "UL" which is not finished
    			<ul id="c_nav"></ul>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 117, Column 35694: invalid comment declaration: found name start character outside comment but inside comment declaration
    …d GardeshGari -->   				 				<!--<!-- Start Koodak -->    				 	 	  	  	  	  	…
  • Info Line 117, Column 35685: comment declaration started here
    …		<!-- End GardeshGari -->   				 				<!--<!-- Start Koodak -->    				 	 	  	…
  • Error Line 166, Column 56: document type does not allow element "INPUT" here
    <input type="hidden" name="poll_id" value="5" dir="rtl"><tr>

    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 174, Column 53: document type does not allow element "INPUT" here; missing one of "P", "H1", "H2", "H3", "H4", "H5", "H6", "PRE", "DIV", "ADDRESS" start-tag
    …idden" name="_vote_submit" value="yes"></form> </div>  		</div> 		<!-- End Con…

    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 639, Column 14732: document type does not allow element "INPUT" here; missing one of "P", "H1", "H2", "H3", "H4", "H5", "H6", "PRE", "DIV", "ADDRESS" start-tag
    ….." name="query" class="search_input2">  						</form> 					</div> 					<a hre…

    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 639, Column 14747: end tag for "FORM" which is not finished
    …" class="search_input2">  						</form> 					</div> 					<a href="javascript:d…

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 739, Column 1999: end tag for element "DIV" which is not open
    …<!-- End Footer --> 		 	<div class="wrapper"></div>     </div>	 </body> </html>

    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.

Visitor Analysis

Daily Visitor
  • 116.667 visits
Daily Visitor

In Page Analysis