Description ...

sabtemelk.ir
  • Domain Name
    sabtemelk.ir
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #51075
  • Page Size
    28.7 KB
  • Ip Address
    46.209.141.10
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 2 PNG

Website Meta Analysis

  • Title
    سامانه ثبت الکترونیکی پذیرش درخواست صدور سند مالکیت
  • Meta Keyword
    Keywords
  • Meta Description
    Description

Technical Analysis

  • Webserver
    Microsoft-IIS/7.5
  • Ip Address
    46.209.141.10
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • cache-control: private
  • content-type: text/html; charset=utf-8
  • server: Microsoft-IIS/7.5
  • x-aspnet-version: 4.0.30319
  • x-powered-by: ASP.NET
  • date: Wed, 02 Oct 2013 13:19:26 GMT
  • content-length: 34475
  • 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 'sabtemelk.ir'


domain: sabtemelk.ir
ascii: sabtemelk.ir
remarks: (Domain Holder) sazman sabt asnad va amlak keshvar(The State Organization for Registration of Deeds and Properties),
remarks: (Domain Holder Address) sazmane sabte asnad va amlake keshvar,fayazbakhsh st,the east of north of parkeshahr park., tehran, tehran, IR
holder-c: sa1540-irnic
admin-c: sa1540-irnic
tech-c: sa1540-irnic
nserver: ns.parsonline.net
nserver: ns1.parsonline.net
last-updated: 2012-09-05
expire-date: 2013-07-17
source: IRNIC # Filtered

nic-hdl: sa1540-irnic
org: sazman sabt asnad va amlak keshvar(The State Organization for Registration of Deeds and Properties),
e-mail: email
address: sazmane sabte asnad va amlake keshvar,fayazbakhsh st,the east of north of parkeshahr park., tehran, tehran, IR
phone: +98 21 66702268
source: IRNIC # Filtered

DNS Analysis


DNS servers
ns.parsonline.net [213.217.60.2]


DNS Records

Answer records
sabtemelk.ir MX
preference: 5
exchange: mail.sabtemelk.ir
86400s
sabtemelk.ir SOA
server: ns.parsonline.net
email: root@ns.parsonline.net
serial: 2012090303
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 86400
86400s
sabtemelk.ir NS  ns.parsonline.net 86400s
sabtemelk.ir A 46.209.141.10 86400s

Authority records

Additional records
mail.sabtemelk.ir A 46.209.141.10 86400s
ns.parsonline.net A 213.217.60.2 3600s

IP 46.209.141.10 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • No whois ip data for 46.209.141.10

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 14 Errors
  • 9 Warnings
Ratio Text/Html
  • 0.6681730148482892
Message Error
  • Error Line 106, Column 42: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
                        <div class="MenuIcon"></div>

    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 70: document type does not allow element "link" here
    <link href="../Styles/Buttons.css" rel="stylesheet" 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 171, Column 68: document type does not allow element "link" here
    <link href="../Styles/Login.css" rel="stylesheet" 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 224, Column 31: there is no attribute "behavior"
                <marquee behavior="scroll" direction="up" scrollamount="3" onmouseo…

    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 224, Column 50: there is no attribute "direction"
    … <marquee behavior="scroll" direction="up" scrollamount="3" onmouseover="stop(…

    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 224, Column 68: there is no attribute "scrollamount"
    …="scroll" direction="up" scrollamount="3" onmouseover="stop()" onmouseout="sta…

    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 224, Column 84: there is no attribute "onmouseover"
    …ion="up" scrollamount="3" onmouseover="stop()" onmouseout="start()" style="wid…

    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 224, Column 104: there is no attribute "onmouseout"
    …t="3" onmouseover="stop()" onmouseout="start()" style="width: 100%; font-famil…

    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 224, Column 120: there is no attribute "style"
    …r="stop()" onmouseout="start()" style="width: 100%; font-family: 'B Nazanin' ,…

    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 224, Column 228: element "marquee" undefined
    …Nazanin' ,Arial,Tahoma; font-size: 12pt; text-align: justify; direction: rtl;">

    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 233, Column 66: cannot generate system identifier for general entity "ctl"
    …"http://ssaa.ir/Default.aspx?tabid=41&ctl=Edit&mid=10516&Code=4054" target="_b…

    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 233, Column 66: general entity "ctl" not defined and no default entity
    …"http://ssaa.ir/Default.aspx?tabid=41&ctl=Edit&mid=10516&Code=4054" target="_b…

    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 233, Column 69: reference not terminated by REFC delimiter
    …tp://ssaa.ir/Default.aspx?tabid=41&ctl=Edit&mid=10516&Code=4054" target="_blan…

    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 233, Column 69: reference to external entity in attribute value
    …tp://ssaa.ir/Default.aspx?tabid=41&ctl=Edit&mid=10516&Code=4054" target="_blan…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 233, Column 69: reference to entity "ctl" for which no system identifier could be generated
    …tp://ssaa.ir/Default.aspx?tabid=41&ctl=Edit&mid=10516&Code=4054" target="_blan…

    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 233, Column 65: entity was defined here
    …="http://ssaa.ir/Default.aspx?tabid=41&ctl=Edit&mid=10516&Code=4054" target="_…
  • Warning Line 233, Column 75: cannot generate system identifier for general entity "mid"
    …://ssaa.ir/Default.aspx?tabid=41&ctl=Edit&mid=10516&Code=4054" target="_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 233, Column 75: general entity "mid" not defined and no default entity
    …://ssaa.ir/Default.aspx?tabid=41&ctl=Edit&mid=10516&Code=4054" target="_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 233, Column 78: reference not terminated by REFC delimiter
    …://ssaa.ir/Default.aspx?tabid=41&ctl=Edit&mid=10516&Code=4054" target="_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.

  • Warning Line 233, Column 78: reference to external entity in attribute value
    …://ssaa.ir/Default.aspx?tabid=41&ctl=Edit&mid=10516&Code=4054" target="_blank">

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 233, Column 78: reference to entity "mid" for which no system identifier could be generated
    …://ssaa.ir/Default.aspx?tabid=41&ctl=Edit&mid=10516&Code=4054" target="_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 233, Column 74: entity was defined here
    …://ssaa.ir/Default.aspx?tabid=41&ctl=Edit&mid=10516&Code=4054" target="_blank">
  • Warning Line 233, Column 85: cannot generate system identifier for general entity "Code"
    …://ssaa.ir/Default.aspx?tabid=41&ctl=Edit&mid=10516&Code=4054" target="_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 233, Column 85: general entity "Code" not defined and no default entity
    …://ssaa.ir/Default.aspx?tabid=41&ctl=Edit&mid=10516&Code=4054" target="_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 233, Column 89: reference not terminated by REFC delimiter
    …://ssaa.ir/Default.aspx?tabid=41&ctl=Edit&mid=10516&Code=4054" target="_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.

  • Warning Line 233, Column 89: reference to external entity in attribute value
    …://ssaa.ir/Default.aspx?tabid=41&ctl=Edit&mid=10516&Code=4054" target="_blank">

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 233, Column 89: reference to entity "Code" for which no system identifier could be generated
    …://ssaa.ir/Default.aspx?tabid=41&ctl=Edit&mid=10516&Code=4054" target="_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 233, Column 84: entity was defined here
    …://ssaa.ir/Default.aspx?tabid=41&ctl=Edit&mid=10516&Code=4054" target="_blank">
  • Error Line 350, Column 74: required attribute "alt" not specified
                    <img src="../Images/LoginLogo.png" style="float: left;" />

    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 383, Column 174: there is no attribute "helptext"
    …t-size: 10pt; width: 170px;" helptext="LostDocument">شماره پرونده خود را فرامو…

    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 401, Column 74: required attribute "alt" not specified
                    <img src="../Images/LoginLogo.png" style="float: left;" />

    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 452, Column 74: document type does not allow element "link" here
        <link href="Styles/MessageBox.css" rel="stylesheet" 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).

Visitor Analysis

Daily Visitor
  • 2.648 visits