vuodatus.net

Vuodatus.net ...

Display Widget for this domain on your website. Click Here
This data was last updated from 30-07-2013 06:22:54  (update).

Overview Info

  • Domain Name
    vuodatus.net
  • Favicon
  • Alexa Rank
    #12709
  • Google Page Rank
    PR 6
  • Ip Address
    80.69.174.95
  • Page Size
    35.6 KB
  • Images
    0 GIF, 14 JPG, 17 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 2 38 0 0 0

Website Meta Analysis



  • Title
    Vuodatus.net
  • Meta Keyword
  • Meta Description
    Vuodatus.net

Technical Analysis



  • Webserver
    nginx/1.1.19
  • Ip Address
    80.69.174.95
  • Domain Age
    9 Years, 0 Months, 23 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx/1.1.19
  • content-type: text/html; charset=UTF-8
  • cache-control: private, must-revalidate
  • etag: "68aa4329cb1236be923641ed0c798b37"
  • content-encoding: gzip
  • content-length: 8215
  • accept-ranges: bytes
  • date: Tue, 30 Jul 2013 06:22:51 GMT
  • x-varnish: 1789050691
  • age: 0
  • via: 1.1 varnish
  • connection: keep-alive
  • x-google-cache-control: remote-fetch
domain: vuodatus.net
owner: Tuomas Rinta
organization: Vuodatus.net Oy
email: email
address: Aleksanterinkatu 9
city: Helsinki
postal-code: 00101
country: FI
phone: +358.503754651
admin-c: CNET-713346 email
tech-c: CNET-713347 email
billing-c: CNET-713348 email
nserver: ns1.sigmatic.fi
nserver: ns2.sigmatic.fi
status: lock
created: 2004-07-23 12:03:24 UTC
modified: 2010-07-01 06:05:44 UTC
expires: 2019-07-23 12:03:09 UTC
query-source: 65.75.186.205

contact-hdl: CNET-713346
person: Tuomas Rinta
organization: Vuodatus.net Oy
email: email
address: Aleksanterinkatu 9
city: Helsinki
postal-code: 00101
country: FI
phone: +358.503754651

contact-hdl: CNET-713347
person: Tuomas Rinta
organization: Vuodatus.net Oy
email: email
address: Aleksanterinkatu 9
city: Helsinki
postal-code: 00101
country: FI
phone: +358.503754651

contact-hdl: CNET-713348
person: Tuomas Rinta
organization: Vuodatus.net Oy
email: email
address: Aleksanterinkatu 9
city: Helsinki
postal-code: 00101
country: FI
phone: +358.503754651

source: joker.com live whois service
query-time: 0.006013
db-updated: 2012-07-22 01:29:58
NOTE: By submitting a WHOIS query, you agree to abide by the following
NOTE: terms of use: You agree that you may use this data only for lawful
NOTE: purposes and that under no circumstances will you use this data to:
NOTE: (1) allow, enable, or otherwise support the transmission of mass
NOTE: unsolicited, commercial advertising or solicitations via direct mail,
NOTE: e-mail, telephone, or facsimile; or (2) enable high volume, automated,
NOTE: electronic processes that apply to Joker.com (or its computer systems).
NOTE: The compilation, repackaging, dissemination or other use of this data
NOTE: is expressly prohibited without the prior written consent of Joker.com.

DNS Analysis


DNS servers
a.ns.joker.com [184.172.157.218]
b.ns.joker.com [159.25.97.69]
c.ns.joker.com [66.197.237.21]


DNS Records

Answer records
vuodatus.net NS  a.ns.joker.com 86400s
vuodatus.net NS  b.ns.joker.com 86400s
vuodatus.net NS  c.ns.joker.com 86400s
vuodatus.net MX
preference: 20
exchange: smtp1.edelkey.net
86400s
vuodatus.net MX
preference: 20
exchange: smtp2.edelkey.net
86400s
vuodatus.net MX
preference: 80
exchange: mx.eivoittoa.fi
86400s
vuodatus.net SOA
server: a.ns.joker.com
email: hostmaster@joker.com
serial: 2013012167
refresh: 10240
retry: 7200
expire: 1209600
minimum ttl: 86400
86400s
vuodatus.net A 83.145.196.211 86400s

Authority records

Additional records
a.ns.joker.com A 184.172.157.218 7200s
b.ns.joker.com A 159.25.97.69 7200s
c.ns.joker.com A 66.197.237.21 7200s

IP 80.69.174.95 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 84 Errors
  • 7 Warnings
Ratio Text/Html
  • 0.6802105609475242
Message Error
  • Error Line 6, Column 41: there is no attribute "value"
      <meta http-equiv="content-type" value="text/html; charset=UTF-8"/>

    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 6, Column 68: required attribute "content" not specified
      <meta http-equiv="content-type" value="text/html; charset=UTF-8"/>

    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 25, Column 10: document type does not allow element "noscript" here; assuming missing "object" start-tag
    <noscript><img src="http://vuodatus.spring-
  • Error Line 26, Column 52: end tag for "img" omitted, but OMITTAG NO was specified
    tns.net/j0=,,,;+,,cp=etusivu;;;;" alt=""></noscript> 

    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 25, Column 11: start tag was here
    <noscript><img src="http://vuodatus.spring-
  • Error Line 36, Column 154: end tag for "img" omitted, but OMITTAG NO was specified
    …e=vuodatus&amp;name=default.page" height="1" width="1" alt="*"></p></noscript> 

    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 36, Column 14: start tag was here
    <noscript><p><img src="http://b.scorecardresearch.com/p?c1=2&amp;c2=14373432&am…
  • Error Line 50, Column 9: end tag for "object" omitted, but OMITTAG NO was specified
      </head>

    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 25, Column 1: start tag was here
    <noscript><img src="http://vuodatus.spring-
  • Warning Line 78, Column 49: character "&" is the first character of a delimiter but occurred as data
                      var query = queryParams.join('&');

    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 98, Column 94: there is no attribute "onClick"
    …"user" value="Käyttäjätunnus" onClick="if($('#loginusername').attr('value')=='…

    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 104, Column 76: there is no attribute "scope"
    …align: center"><fb:login-button scope="email" onlogin="login();">Kirjaudu</fb:…

    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 104, Column 92: there is no attribute "onlogin"
    …r"><fb:login-button scope="email" onlogin="login();">Kirjaudu</fb:login-button>

    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 104, Column 102: element "fb:login-button" undefined
    …r"><fb:login-button scope="email" onlogin="login();">Kirjaudu</fb:login-button>

    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 105, Column 4: end tag for element "a" which is not open
    </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 126, Column 13: end tag for element "td" which is not open
            </td>

    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 156, Column 326: there is no attribute "allowTransparency"
    …overflow:hidden; width:300px; height:555px;" allowTransparency="true"></iframe>

    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 165, Column 7: end tag for element "td" which is not open
      </td>

    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 187, Column 144: required attribute "alt" not specified
    …g src="http://vuodatus.net/images/LABYRINTTI_w150_yhteistyossa.png"/></a></div>

    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 191, Column 165: end tag for "img" omitted, but OMITTAG NO was specified
    …e/eas?cu=2319;cre=img" border="0" alt="EmediateAd" width="768" height="90"></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 191, Column 55: start tag was here
    …//eas3.emediate.se/eas?cu=2319;ty=ct"><img src="http://eas3.emediate.se/eas?cu…
  • Error Line 198, Column 24: document type does not allow element "style" here
    	<style 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 256, Column 39: there is no attribute "onClick"
       <p><a href="javascript://" onClick="javascript:$('#loginNotification').hide(…

    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 256, Column 152: required attribute "alt" not specified
    … style="color: #FFFFFF"><img src="/images/main/login-layer-close.png"/></a></p>

    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>.

Visitor Analysis

Daily Visitor
  • 2.333 visits