mol.fi

Siirry suoraan sivun sisältöön Haku Asiahakemisto Yhteystiedot På svenska In English     Etusivu  |  Työnhakijan palvelut  |  Työnantajan palvelut  |  Työsuhdeasiat  |  Koulutus ja ammatinvalinta  |  Yrittäjyyspalvelu  |  Paikalliset TE-palvelut ... ...

Display Widget for this domain on your website. Click Here
This data was last updated from 10-03-2013 10:28:36  (update).

Overview Info

  • Domain Name
    mol.fi
  • Favicon
  • Alexa Rank
    #16601
  • Google Page Rank
    PR 7
  • Ip Address
    194.100.117.199
  • Page Size
    11.6 KB
  • Images
    3 GIF, 1 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 5 1 0 0 0

Website Meta Analysis



  • Title
    mol.fi
  • Meta Keyword
  • Meta Description
    Siirry suoraan sivun sisältöön Haku Asiahakemisto Yhteystiedot På svenska In English     Etusivu  |  Työnhakijan palvelut  |  Työnantajan palvelut  |  Työsuhdeasiat  |  Koulutus ja ammatinvalinta  |  Yrittäjyyspalvelu  |  Paikalliset TE-palvelut ...

Technical Analysis



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

Hyper Text Transfer Protocol (HTTP) header show data header response from mol.fi.

HTML Analysis

  • date: Sun, 10 Mar 2013 10:28:32 GMT
  • server: Apache/2.2.3 (CentOS)
  • last-modified: Sun, 10 Mar 2013 10:15:02 GMT
  • etag: "33d0027-3166-4d78f54551580"
  • accept-ranges: bytes
  • content-length: 12646
  • connection: close
  • content-type: text/html; charset=UTF-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

domain: mol.fi
descr: Työ- ja elinkeinoministeriö
descr: 21603070
address: Ari Wäck
address: PL 32
address: 00023
address: VALTIONEUVOSTO
phone: 010606000
status: Granted
created: 2.12.2009
modified: 12.8.2011
expires: 2.12.2012
nserver: ns.mol.fi [Ok]
nserver: ns-fi.elisa.net [Ok]
nserver: ns-se.elisa.net [Ok]
dnssec: no

More information is available at https://domain.fi/
Copyright (c) Finnish Communications Regulatory Authority

DNS Analysis


DNS servers
ltt-dns-01.tdcnet.fi
ari-dns-01.tdcnet.fi
ldg-dns-01.tdcnet.fi
ns.mol.fi [194.100.117.166]


DNS Records

Answer records
mol.fi SOA
server: ns.mol.fi
email: hostmaster@mol.fi
serial: 2012110801
refresh: 7200
retry: 7200
expire: 2419200
minimum ttl: 86400
300s
mol.fi NS  ltt-dns-01.tdcnet.fi 300s
mol.fi NS  ari-dns-01.tdcnet.fi 300s
mol.fi NS  ldg-dns-01.tdcnet.fi 300s
mol.fi NS  ns.mol.fi 300s
mol.fi MX
preference: 10
exchange: smtp-in.vy-verkko.fi
300s
mol.fi TXT v=spf1 mx a:helka.mol.fi include:smtp-in.vy-verkko.fi ~all 300s
mol.fi A 194.100.117.200 300s
mol.fi A 194.100.117.199 300s

Authority records

Additional records
ns.mol.fi A 194.100.117.166 300s

IP 194.100.117.199 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 15 Errors
  • 6 Warnings
Ratio Text/Html
  • 0.6684896928901978
Message Error
  • Error Line 22, Column 31: there is no attribute "CONTENT"
    <meta name="DC.title" CONTENT="Etusivu" />

    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 22, Column 42: required attribute "content" not specified
    <meta name="DC.title" CONTENT="Etusivu" />

    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 23, Column 64: required attribute "content" not specified
    <meta name="DC.creator" CONTENT="Työ- ja elinkeinoministeriö" />

    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 24, Column 41: required attribute "content" not specified
    <meta name="DC.subject" CONTENT="null" />

    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 41: required attribute "content" not specified
    <meta name="DC.description" CONTENT="" />

    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 26, Column 51: required attribute "content" not specified
    <meta name="DC.date.issued" CONTENT="24.01.2013" />

    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 27, Column 40: required attribute "content" not specified
    <meta name="DC.language" CONTENT="fi" />

    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 28, Column 82: required attribute "content" not specified
    …ta name="DC.contributor" CONTENT="Onesta Solutions Oy, http://www.onesta.fi" />

    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 63, Column 85: character "#" is not allowed in the value of attribute "name"
    …<a href="#sisalto">Siirry suoraan sivun sisältöön</a> <a name="#top"></a></div>

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Warning Line 195, Column 74: cannot generate system identifier for general entity "destination"
    …ol.fi/asva/kirj_valinta?Action=cmdOth&destination=https://asiointi.mol.fi:443/…

    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 195, Column 74: general entity "destination" not defined and no default entity
    …ol.fi/asva/kirj_valinta?Action=cmdOth&destination=https://asiointi.mol.fi:443/…

    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 195, Column 85: reference not terminated by REFC delimiter
    …kirj_valinta?Action=cmdOth&destination=https://asiointi.mol.fi:443/ilmi/&desti…

    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 195, Column 85: reference to external entity in attribute value
    …kirj_valinta?Action=cmdOth&destination=https://asiointi.mol.fi:443/ilmi/&desti…

    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 195, Column 85: reference to entity "destination" for which no system identifier could be generated
    …kirj_valinta?Action=cmdOth&destination=https://asiointi.mol.fi:443/ilmi/&desti…

    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 195, Column 73: entity was defined here
    …mol.fi/asva/kirj_valinta?Action=cmdOth&destination=https://asiointi.mol.fi:443…
  • Warning Line 195, Column 120: cannot generate system identifier for general entity "destination_no_tunn"
    …ion=https://asiointi.mol.fi:443/ilmi/&destination_no_tunn=http://lomake.fi/for…

    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 195, Column 120: general entity "destination_no_tunn" not defined and no default entity
    …ion=https://asiointi.mol.fi:443/ilmi/&destination_no_tunn=http://lomake.fi/for…

    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 195, Column 139: reference not terminated by REFC delimiter
    …i.mol.fi:443/ilmi/&destination_no_tunn=http://lomake.fi/forms/xml/TM/716/fi">I…

    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 195, Column 139: reference to external entity in attribute value
    …i.mol.fi:443/ilmi/&destination_no_tunn=http://lomake.fi/forms/xml/TM/716/fi">I…

    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 195, Column 139: reference to entity "destination_no_tunn" for which no system identifier could be generated
    …i.mol.fi:443/ilmi/&destination_no_tunn=http://lomake.fi/forms/xml/TM/716/fi">I…

    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 195, Column 119: entity was defined here
    …tion=https://asiointi.mol.fi:443/ilmi/&destination_no_tunn=http://lomake.fi/fo…
  • Error Line 243, Column 85: required attribute "alt" not specified
    …	<img src="/mol/kuva_arkisto/logot_bannerit/te-palvelut_pysty.jpg" width="100">

    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 243, Column 86: end tag for "img" omitted, but OMITTAG NO was specified
    …	<img src="/mol/kuva_arkisto/logot_bannerit/te-palvelut_pysty.jpg" width="100">

    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 243, Column 8: start tag was here
    							<img src="/mol/kuva_arkisto/logot_bannerit/te-palvelut_pysty.jpg" width=…

Visitor Analysis

Daily Visitor
  • 8.167 visits
Daily Visitor

In Page Analysis