havairan.com

سایت هوا شناسی .پیش بینی مستقیم آب و هوا از مركز هواشناسی ایران, آب و هوای ١٢٥٩٨٦ منطقه ایران ...

Display Widget for this domain on your website. Click Here
This data was last updated from 18-05-2013 07:08:44  (update).

Overview Info

  • Domain Name
    havairan.com
  • Favicon
  • Alexa Rank
    #11747
  • Google Page Rank
    PR 5
  • Ip Address
    79.99.2.179
  • Page Size
    49.1 KB
  • Images
    2 GIF, 0 JPG, 1 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 8 52 52 0 0

Website Meta Analysis



  • Title
    HAVAIRAN.COM | سایت هواشناسی - هواشناسی ١٢٥٩٨٦ منطقه در ایران
  • Meta Keyword
    ایران,آب و هوا,هواشناسی
  • Meta Description
    سایت هوا شناسی .پیش بینی مستقیم آب و هوا از مركز هواشناسی ایران, آب و هوای ١٢٥٩٨٦ منطقه ایران

Technical Analysis



  • Webserver
    Apache/2.2.8 (Ubuntu)
  • Ip Address
    79.99.2.179
  • Domain Age
    4 Years, 5 Months, 1 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Sat, 18 May 2013 19:08:41 GMT
  • server: Apache/2.2.8 (Ubuntu)
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-length: 7257
  • connection: close
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain name: havairan.com

Registrant Contact:
Ample
Ample Ample ()

Fax:
Box 27 111
Stockholm, 10252
SE

Administrative Contact:
Binero AB
Registry Department ( email )
+1.86240800
Fax: +46.851480140
Finlandsgatan 12
Kista, 16474
SE

Technical Contact:
Binero AB
Registry Department ( email )
+1.86240800
Fax: +46.851480140
Finlandsgatan 12
Kista, 16474
SE

Status: Locked

Name Servers:
ns3.binero.se
ns4.binero.se
ns5.binero.se
ns6.binero.se
ns7.binero.se

Creation date: 09 Dec 2008 09:18:40
Expiration date: 09 Dec 2012 09:18:40

DNS Analysis


DNS servers
ns3.binero.se [156.154.64.58]
ns4.binero.se [156.154.67.58]
ns5.binero.se [156.154.64.59]
ns6.binero.se [156.154.67.59]
ns7.binero.se [195.74.38.250]


DNS Records

Answer records
havairan.com 48 [136 bytes] 3600s
mgjtu329mon547ecsft2bjkkfa81gpv8.havairan.com 50 [36 bytes] 86400s
havairan.com SOA
server: ns3.binero.se
email: registry@binero.se
serial: 1357776000
refresh: 43200
retry: 3600
expire: 604800
minimum ttl: 3600
7200s
havairan.com NS  ns5.binero.se 86400s
havairan.com 48 [136 bytes] 3600s

Authority records

Additional records

IP 79.99.2.179 Analysis

  • Country Code
    SE
  • Country Code3
    SWE
  • Country Name
    Sweden
  • City
    Falkenberg
  • Continent Code
    EU
  • Latitude
    56.8981
  • Longitude
    12.5019
  • No whois ip data for 79.99.2.179

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 25 Errors
  • 5 Warnings
Ratio Text/Html
  • 0.6264142689546837
Message Error
  • Error Line 13, Column 16: there is no attribute "property"
    <meta property="fb:admins" content="100001299868754" />

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

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

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

  • Warning Line 43, Column 265: character "<" is the first character of a delimiter but occurred as data
    …apper");b.style.marginLeft="auto";if(a<912){b.style.marginLeft="0"}else{if(a>9…

    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 43, Column 307: character "&" is the first character of a delimiter but occurred as data
    …){b.style.marginLeft="0"}else{if(a>911&&a<1056){b.style.marginLeft=((a-912)/2)…

    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 43, Column 309: cannot generate system identifier for general entity "a"
    …b.style.marginLeft="0"}else{if(a>911&&a<1056){b.style.marginLeft=((a-912)/2)+"…

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

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

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

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

  • Error Line 43, Column 309: general entity "a" not defined and no default entity
    …b.style.marginLeft="0"}else{if(a>911&&a<1056){b.style.marginLeft=((a-912)/2)+"…

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

  • Warning Line 43, Column 310: reference not terminated by REFC delimiter
    ….style.marginLeft="0"}else{if(a>911&&a<1056){b.style.marginLeft=((a-912)/2)+"p…

    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 43, Column 310: reference to entity "a" for which no system identifier could be generated
    ….style.marginLeft="0"}else{if(a>911&&a<1056){b.style.marginLeft=((a-912)/2)+"p…

    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 43, Column 308: entity was defined here
    …{b.style.marginLeft="0"}else{if(a>911&&a<1056){b.style.marginLeft=((a-912)/2)+…
  • Warning Line 43, Column 310: character "<" is the first character of a delimiter but occurred as data
    ….style.marginLeft="0"}else{if(a>911&&a<1056){b.style.marginLeft=((a-912)/2)+"p…

    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 123, Column 15: ID "google-ads" already defined
    					<div id="google-ads" style="margin: 1pt 0pt 0pt auto; clear: both; text-al…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 122, Column 14: ID "google-ads" first defined here
    				<div id="google-ads" style="clear:both;text-align:center;">
  • Error Line 166, Column 74: document type does not allow element "form" here; missing one of "object", "ins", "del", "map" start-tag
    							<form action="https://www.paypal.com/cgi-bin/webscr" method="post">

    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 167, Column 57: 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="cmd" value="_s-xclick">

    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 167, Column 58: end tag for "input" omitted, but OMITTAG NO was specified
    							<input type="hidden" name="cmd" value="_s-xclick">

    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 167, Column 8: start tag was here
    							<input type="hidden" name="cmd" value="_s-xclick">
  • Error Line 168, Column 69: 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="hosted_button_id" value="10379407">

    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 168, Column 70: end tag for "input" omitted, but OMITTAG NO was specified
    							<input type="hidden" name="hosted_button_id" value="10379407">

    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 168, Column 8: start tag was here
    							<input type="hidden" name="hosted_button_id" value="10379407">
  • Error Line 169, Column 103: there is no attribute "border"
    …tn/btn_donateCC_LG_global.gif" border="0" name="submit" alt="PayPal - The safe…

    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 169, Column 172: 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
    …" border="0" name="submit" alt="PayPal - The safer, easier way to pay online.">

    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 169, Column 173: end tag for "input" omitted, but OMITTAG NO was specified
    …" border="0" name="submit" alt="PayPal - The safer, easier way to pay online.">

    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 169, Column 8: start tag was here
    							<input type="image" src="https://www.paypal.com/en_US/i/btn/btn_donateCC…
  • Error Line 170, Column 27: there is no attribute "border"
    							<img alt="" border="0" src="https://www.paypal.com/en_US/i/scr/pixel.gif…

    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 170, Column 102: document type does not allow element "img" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "address", "fieldset", "ins", "del" start-tag
    …er="0" src="https://www.paypal.com/en_US/i/scr/pixel.gif" width="1" height="1">

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

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

  • Error Line 170, Column 103: end tag for "img" omitted, but OMITTAG NO was specified
    …er="0" src="https://www.paypal.com/en_US/i/scr/pixel.gif" width="1" height="1">

    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 170, Column 8: start tag was here
    							<img alt="" border="0" src="https://www.paypal.com/en_US/i/scr/pixel.gif…
  • Error Line 187, Column 17: 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 187, Column 23: 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).
  • Error Line 188, Column 63: required attribute "type" not specified
    …ect.facebook.net/en_US/all.js#xfbml=1"></script><fb:like href="http://www.hava…

    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 188, Column 87: there is no attribute "href"
    …ll.js#xfbml=1"></script><fb:like href="http://www.havairan.com" layout="box_co…

    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 188, Column 120: there is no attribute "layout"
    …href="http://www.havairan.com" layout="box_count" show_faces="true" width="140…

    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 188, Column 143: there is no attribute "show_faces"
    …//www.havairan.com" layout="box_count" show_faces="true" width="140"></fb:like>

    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 188, Column 156: there is no attribute "width"
    …//www.havairan.com" layout="box_count" show_faces="true" width="140"></fb:like>

    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 188, Column 161: element "fb:like" undefined
    …//www.havairan.com" layout="box_count" show_faces="true" width="140"></fb:like>

    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 194, Column 14: there is no attribute "start"
    			<ol start="6" dir="rtl">

    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 430, Column 26: end tag for "ol" omitted, but OMITTAG NO was specified
                        </div>

    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 418, Column 16: start tag was here
    					</ol>					<ol dir="rtl">						<li>

Visitor Analysis

Daily Visitor
  • 11.667 visits
Daily Visitor