neti.ee

NETI on Eesti parim kataloog ja otsingumootor. NETI igapäevanekasutajate arv ületab 350 000. ...

Display Widget for this domain on your website. Click Here
Processing update domain...

Overview Info

  • Domain Name
    neti.ee
  • Favicon
  • Alexa Rank
    #18386
  • Google Page Rank
    PR 6
  • Ip Address
    195.50.209.246
  • Page Size
    37.1 KB
  • Images
    8 GIF, 0 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 6 11 0 0 0

Website Meta Analysis



  • Title
    NETI - Eesti Interneti Kataloog ja Otsingusüsteem
  • Meta Keyword
  • Meta Description
    NETI on Eesti parim kataloog ja otsingumootor. NETI igapäevanekasutajate arv ületab 350 000.

Technical Analysis



  • Webserver
    Apache
  • Ip Address
    195.50.209.246
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from neti.ee.

HTML Analysis

  • date: Sat, 14 Sep 2013 07:45:07 GMT
  • content-type: text/html
  • content-length: 9207
  • connection: keep-alive
  • server: Apache
  • content-encoding: gzip
  • vary: Accept-Encoding
  • etag: "23f7-a5d4d5c3"
  • cache-control: s-maxage=3600, max-age=57600
  • expires: Sat, 14 Sep 2013 23:17:10 GMT
  • accept-ranges: bytes
  • age: 1676
  • x-cache: HIT
  • x-google-cache-control: remote-cache-hit
  • via: HTTP/1.1 GWA (remote cache hit)
% This Whois Server contains information on
% Estonian Top Level Domain ee TLD

domain: neti.ee
registrant: CID:ELION:128410387539
admin-c: CID:ELION:128410387445
nsset: NSSID:ELION:ID001
registrar: elion
status: paid and in zone
registered: 04.07.2010 03:59:33
changed: 10.09.2010 10:31:49
expire: 10.09.2013

contact: CID:ELION:128410387539
name: ELION ETTEVÕTTED AKTSIASELTS
e-mail: Not Disclosed - Visit www.eestiinternet.ee for webbased WHOIS
registrar: elion
created: 10.09.2010 10:31:16

contact: CID:ELION:128410387445
name: Päärn Brauer
e-mail: Not Disclosed - Visit www.eestiinternet.ee for webbased WHOIS
registrar: elion
created: 10.09.2010 10:31:14

nsset: NSSID:ELION:ID001
nserver: ns.elion.ee (213.168.18.146)
nserver: ns2.elion.ee (195.50.193.163)
tech-c: CID:ELION:ID001
registrar: elion
created: 06.07.2010 17:14:36

contact: CID:ELION:ID001
org: Elion Ettevõtted AS
name: Elion Ettevõtted AS
e-mail: Not Disclosed - Visit www.eestiinternet.ee for webbased WHOIS
registrar: elion
created: 06.07.2010 17:12:53


DNS Analysis


DNS servers
ns.elion.ee [213.168.18.146]
ns2.elion.ee [195.50.193.163]

DNS Records

Answer records
neti.ee MX
preference: 10
exchange: mx1.elion.ee
300s
neti.ee MX
preference: 20
exchange: zen.estpak.ee
300s
neti.ee NS  ns.elion.ee 86400s
neti.ee NS  ns2.elion.ee 86400s
neti.ee A 195.50.209.246 86400s
neti.ee SOA
server: ns.elion.ee
email: hostmaster@elion.ee
serial: 2012102300
refresh: 28800
retry: 7200
expire: 604800
minimum ttl: 86400
86400s

Authority records

Additional records

IP 195.50.209.246 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 27 Errors
  • 17 Warnings
Ratio Text/Html
  • 0.6591274125174438
Message Error
  • Error Line 219, Column 117: there is no attribute "nml:tab-name"
    …" class="selected sprite fc-tab-link" nml:tab-name="kataloog">Kataloog</a></li>

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

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

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

  • Error Line 230, Column 46: there is no attribute "nml:tab-name"
        <div class="fc-tab-content" nml:tab-name="kataloog" style="display: block">

    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 677, Column 47: end tag for "ul" which is not finished
                <ul class="nav-dropdown-rows"></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.

  • Warning Line 702, Column 859: cannot generate system identifier for general entity "x"
    …(new Date()).getTime().toString(36)+"&x="+screen.width+"x"+screen.height+"x"+s…

    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 702, Column 859: general entity "x" not defined and no default entity
    …(new Date()).getTime().toString(36)+"&x="+screen.width+"x"+screen.height+"x"+s…

    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 702, Column 860: reference not terminated by REFC delimiter
    …new Date()).getTime().toString(36)+"&x="+screen.width+"x"+screen.height+"x"+sc…

    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 702, Column 860: reference to entity "x" for which no system identifier could be generated
    …new Date()).getTime().toString(36)+"&x="+screen.width+"x"+screen.height+"x"+sc…

    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 702, Column 858: entity was defined here
    …+(new Date()).getTime().toString(36)+"&x="+screen.width+"x"+screen.height+"x"+…
  • Error Line 702, Column 998: character ";" not allowed in attribute specification list
    …function q(e,w){for(var m=0;m<w.length;m+=1){if(w[m]==e){return"~"+m}}w.push(e…
  • Error Line 702, Column 998: element "w.length" undefined
    …function q(e,w){for(var m=0;m<w.length;m+=1){if(w[m]==e){return"~"+m}}w.push(e…

    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 702, Column 1082: character "&" is the first character of a delimiter but occurred as data
    …rn e}function u(x,z){var m,y,w,e,A=/[+&,;=~]/g,B;if(!z){z=[]}switch(typeof x){…

    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 702, Column 1378: character "&" is the first character of a delimiter but occurred as data
    …ll"}m=[];if(typeof x.length==="number"&&!(x.propertyIsEnumerable("length"))){e…

    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 702, Column 1379: character "&" is the first character of a delimiter but occurred as data
    …l"}m=[];if(typeof x.length==="number"&&!(x.propertyIsEnumerable("length"))){e=…

    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 702, Column 1439: character ";" not allowed in attribute specification list
    …ble("length"))){e=x.length;for(y=0;y<e;y+=1){m.push(q(u(x[y],z),z)||"null")}re…
  • Error Line 702, Column 1439: element "e" undefined
    …ble("length"))){e=x.length;for(y=0;y<e;y+=1){m.push(q(u(x[y],z),z)||"null")}re…

    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 702, Column 1546: character "&" is the first character of a delimiter but occurred as data
    … in x){if(typeof w==="string"){if(w!=k&&w!=i){B=u(x[w],z);if(B){m.push(q(u(w,z…

    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 702, Column 1548: cannot generate system identifier for general entity "w"
    …n x){if(typeof w==="string"){if(w!=k&&w!=i){B=u(x[w],z);if(B){m.push(q(u(w,z)+…

    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 702, Column 1548: general entity "w" not defined and no default entity
    …n x){if(typeof w==="string"){if(w!=k&&w!=i){B=u(x[w],z);if(B){m.push(q(u(w,z)+…

    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 702, Column 1549: reference not terminated by REFC delimiter
    … x){if(typeof w==="string"){if(w!=k&&w!=i){B=u(x[w],z);if(B){m.push(q(u(w,z)+"…

    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 702, Column 1549: reference to entity "w" for which no system identifier could be generated
    … x){if(typeof w==="string"){if(w!=k&&w!=i){B=u(x[w],z);if(B){m.push(q(u(w,z)+"…

    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 702, Column 1547: entity was defined here
    …in x){if(typeof w==="string"){if(w!=k&&w!=i){B=u(x[w],z);if(B){m.push(q(u(w,z)…
  • Error Line 710, Column 9: end tag for "e" omitted, but OMITTAG NO was specified
    </script> 

    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 702, Column 1437: start tag was here
    …rable("length"))){e=x.length;for(y=0;y<e;y+=1){m.push(q(u(x[y],z),z)||"null")}…
  • Error Line 710, Column 9: end tag for "w.length" omitted, but OMITTAG NO was specified
    </script> 

    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 702, Column 989: start tag was here
    …return w}function q(e,w){for(var m=0;m<w.length;m+=1){if(w[m]==e){return"~"+m}…

Visitor Analysis

Daily Visitor
  • 9.100 visits

In Page Analysis