uff.fi ▷ Etusivu

Quick Summary

Online Status

Offline

Server IP address resolved: No
Http response code: None
Last Checked: 11/05/2024

Uff.fi traffic volume is 90 unique daily visitors and their 90 pageviews. The web value rate of uff.fi is 0 USD. Each visitor makes around 1.07 page views on average.

By Alexa's traffic estimates uff.fi placed at 49,797 position over the world.

Uff.fi server is located in Finland, therefore, we cannot identify the countries where the traffic is originated and if the distance can potentially affect the page load time. See the list of other web pages hosted by Planeetta Internet Oy.

Uff.fi registered under .FI top-level domain. Check other websites in .FI zone.

The last verification results, performed on (October 03, 2024) uff.fi show that uff.fi has a valid and up-to-date wildcard SSL certificate issued by Let's Encrypt expiring on December 15, 2024. Click “Refresh” button for SSL Information at the Safety Information section. Check the list of websites using SSL certificates issued by Let's Encrypt.

In accordance with Google Safe Browsing, Google Safe Search, Symantec and Web of Trust uff.fi is pretty a safe domain.

Relying Google MobileFriendly test uff.fi is well optimized for mobile and tablet devices, however web page loading speed may be improved.

Uff.fi General Information

Global Rank

8,241,595

Average Load Time

0.00sec

Links In Count

Website Value

Audience Geography. Where are uff.fi visitors located?

Country	Visitors

Country	Pageviews

Country	Rank

Where do visitors go on uff.fi?

Subdomain	Pageviews

Subdomain	Pageviews per User

Subdomain	Reach

How popular is uff.fi?

Period	Global Rank	Global Rank Delta
past 3 months	8241595	6081639

Days	Pageviews Rank	Pageviews Rank Delta	Pageviews per Million	Pageviews per Million Delta	Pageviews per User	Pageviews per User Delta
90	7929996	5726763	0	-91.803%	1	-25.5%

Days	Reach Rank	Reach Rank Delta	Reach per Million	Reach per Million Delta
90	8299548	6056701	2	-88.525%

Uff.fi Safety Information

Overview

Last Updated: 11/05/2024

Overall result - uff.fi is safe.

We gather website safety and reputation data and compare it with available third-party sources so we calculate own safety and trustworthiness rate based on information that we get.

Norton Connect Safe

Last Updated: 02/07/2024

uff.fi is safe.

Norton ConnectSafe evaluates uff.fi for any unsafe and insecure content. The results are critical for families with young children.

Google Safe Search

Last Updated: 02/12/2017

uff.fi is safe.

SafeSearch is used as a parental control tool to filter out any inappropriate for your children search results on your devices: phones, tablets or personal computers.

Google Safe Browsing

Last Updated: 01/09/2019

uff.fi is safe.
Malware: not found.
Phishing: not detected.
Unwanted software: not found.
Harmfull applications: not found.

Google Safe Browsing notifies when websites are compromised by malicious actors. These protections work across Google products and provide a safer online experience.

Site Advisor

Last Updated: 01/26/2021

uff.fi is safe.

McAfee assesses uff.fi for a meaningful set of security threats. Featured dangers from annoying pop-ups to hidden Trojans, that can steal your identity, will be revealed. McAfee does not analyze uff.fi for mature or inappropriate content, only security checks are evaluated.

Web of Trust

Last Updated: 01/11/2019

uff.fi child safety is very good.

The WOT calculates reputation of the uff.fi. This reputation system receives ratings from users and information from third-party sources, assesses the uff.fi for safety features and confirms, whether uff.fi is suitable for children.

SSL Information

SSL Checker Tool

Domain	*.uff.fi
Issuer Organization	Let's Encrypt
Issuer	R10
Algorithm	RSA-SHA256
Valid form	09/16/2024
Expiration	12/15/2024
Signed	Certificate is not self signed
Additional Domains	.uff.fi .vaatekerays.fi uff.fi vaatekerays.fi

Uff.fi Server Information

Server Location

Geolocation Tool

ASN Information

ASN Lookup Tool

ASN ID: 58003
ASN Title: Planeetta Internet Oy

Last Update: 03/12/2024

ASN Whois

% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See http://www.ripe.net/db/support/db-terms-conditions.pdf

% Note: this output has been filtered.
% To receive output for a database update, use the "-B" flag.

% Information related to 'AS56320 - AS58367'

as-block: AS56320 - AS58367
descr: RIPE NCC ASN block
remarks: These AS Numbers are assigned to network operators in the RIPE NCC service region.
mnt-by: RIPE-NCC-HM-MNT
created: 2015-09-30T14:19:22Z
last-modified: 2015-09-30T14:19:22Z
source: RIPE

% Information related to 'AS58003'

% Abuse contact for 'AS58003' is 'abuse@planeetta.fi'

aut-num: AS58003
as-name: PLANEETTA-AS
org: ORG-PIO3-RIPE
remarks: *** TRANSITS ***
import: from AS174 accept ANY
export: to AS174 announce AS58003
import: from AS3356 accept ANY
export: to AS3356 announce AS58003
import: from AS47605 accept ANY
export: to AS47605 announce AS58003
import: from AS1759 accept AS-TSF-Customers AS-TSF-PEER
export: to AS1759 announce AS58003
remarks: *** PEERS at TREX ***
import: from AS29432 accept AS29432:AS-PEERING AS29432:RS-PEERING
export: to AS29432 announce AS58003
import: from AS197032 accept AS197032:AS-ALL
export: to AS197032 announce AS58003
import: from AS1741 accept AS-FUNET
export: to AS1741 announce AS58003
import: from AS16302 accept AS-SUOMICOM
export: to AS16302 announce AS58003
import: from AS20569 accept AS-AINAIP
export: to AS20569 announce AS58003
import: from AS20904 accept AS-NETPLAZA
export: to AS20904 announce AS58003
import: from AS29154 accept AS-TELECITYGROUP-FI
export: to AS29154 announce AS58003
admin-c: PLIN-RIPE
admin-c: LUPU-RIPE
tech-c: PLIN-RIPE
tech-c: LUPU-RIPE
status: ASSIGNED
mnt-by: RIPE-NCC-END-MNT
mnt-by: PLANEETTA-MNT
mnt-routes: PLANEETTA-MNT
created: 2012-03-30T08:40:11Z
last-modified: 2017-11-15T12:24:29Z
source: RIPE # Filtered

organisation: ORG-PIO3-RIPE
org-name: Planeetta Internet Oy
org-type: LIR
address: Televisiokatu 3
address: 00240
address: Helsinki
address: FINLAND
phone: +358105251440
fax-no: +358105251449
mnt-ref: PLANEETTA-MNT
mnt-ref: RIPE-NCC-HM-MNT
mnt-by: RIPE-NCC-HM-MNT
mnt-by: PLANEETTA-MNT
abuse-c: PLIN-RIPE
created: 2012-03-15T16:28:40Z
last-modified: 2017-11-09T15:03:28Z
source: RIPE # Filtered
admin-c: PLZ-RIPE
admin-c: LUPU-RIPE
admin-c: AXU-RIPE
admin-c: LK1557-RIPE

role: Planeetta Internet Hostmaster
address: Planeetta Internet Oy
address: Mannerheimintie 105
address: 00280 Helsinki
address: Finland
phone: +358 10 525 1440
fax-no: +358 10 525 1449
org: ORG-PIO1-RIPE
admin-c: LK1557-RIPE
admin-c: LUPU-RIPE
tech-c: LK1557-RIPE
tech-c: LUPU-RIPE
nic-hdl: PLIN-RIPE
mnt-by: PLANEETTA-MNT
created: 2005-08-16T15:32:32Z
last-modified: 2017-11-09T15:01:39Z
source: RIPE # Filtered
abuse-mailbox: abuse@planeetta.fi

person: Lupu Pitkanen
address: Planeetta Internet Oy
address: Televisiokatu 3
address: 00240 Helsinki
address: Finland
phone: +358 10 525 1440
org: ORG-PIO1-RIPE
nic-hdl: LUPU-RIPE
mnt-by: PLANEETTA-MNT
created: 2005-01-04T00:14:30Z
last-modified: 2017-10-30T21:46:32Z
source: RIPE # Filtered

% This query was served by the RIPE Database Query Service version 1.91.2 (HEREFORD)

Uff.fi Domain Name Information

WHOIS

WHOIS Lookup Tool

Domain Whois

domain.............: uff.fi
status.............: Registered
created............: 15.9.1999 09:35:00
expires............: 31.8.2024 00:00:00
available..........: 30.9.2024 00:00:00
modified...........: 28.10.2022 15:36:56
RegistryLock.......: no

Nameservers

nserver............: ns2.hostingpalvelu.fi [35.204.23.201] [OK]
nserver............: ns1.hostingpalvelu.fi [31.217.192.71] [OK]

DNSSEC

dnssec.............: no

Holder

name...............: U-LANDSHJ�LP FR�N FOLK TILL FOLK I FINLAND RF
register number....: 0783118-1
address............: J�rvihaantie 12
postal.............: 01800
city...............: KLAUKKALA
country............: Finland
phone..............:
holder email.......:

Registrar

registrar..........: Planeetta Internet Oy
www................: www.planeetta.fi

Tech

name...............: Hostingpalvelu
email..............: hostmaster@hostingpalvelu.fi

>>> Last update of WHOIS database: 9.11.2022 18:15:07 (EET)

DNS Records

DNS Lookup Tool

Host	A Record	TTL
uff.fi	188.117.30.117	3600

Host	MX Record	Priority	TTL
uff.fi	secure.dotcom.fi	10	3600
uff.fi	uff-fi.mail.protection.outlook.com	0	3600

Host	NS Record	TTL
uff.fi	ns.nebula.fi	3600
uff.fi	ns2.nebula.fi	3600

Host	TXT Record	TTL
uff.fi	v=spf1 a mx ip4:83.145.209.142 include:spf.protection.outlook.com include:spf.lianamailer.com ~all	3600
uff.fi	MS=ms99022657	3600

ns.nebula.fi
TTL: 3600
Email address: hostmaster.nebula.fi
Serial: 2017032127
Refresh: 649211
Retry: 600
Expire: 2419200
Minimum: 3600

Uff.fi HTML Validation

HTML Validation Tool

Warnings

Consider avoiding viewport values that prevent users from resizing documents.

The “type” attribute is unnecessary for JavaScript resources.

The “type” attribute for the “style” element is not needed and should be omitted.

The “banner” role is unnecessary for element “header”.

The “navigation” role is unnecessary for element “nav”.

Section lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all sections.

The first occurrence of ID “entry-33576” was here.

The first occurrence of ID “mk-love-33576” was here.

The first occurrence of ID “entry-33542” was here.

The first occurrence of ID “mk-love-33542” was here.

The first occurrence of ID “entry-33553” was here.

The first occurrence of ID “mk-love-33553” was here.

This document appears to be written in Finnish but the “html” start tag has “lang="en-US"”. Consider using “lang="fi"” (or variant) instead.

Errors

CSS: “background-color”: Parse Error.

Attribute “css-attach” not allowed on element “div” at this point.

No space between attributes.

CSS: “margin-right”: “px” is not a “margin-right” value.

CSS: “border-style”: Parse Error.

CSS: “margin-left”: “px” is not a “margin-left” value.

Bad value “22/09/2019” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Attribute “pubdate” not allowed on element “time” at this point.

Bad value “21/09/2019” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “16/08/2019” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “14/08/2019” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “02/08/2019” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “16/07/2019” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “03/07/2019” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “15/05/2019” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “02/05/2019” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “25/04/2019” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “25/03/2019” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “22/03/2019” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “15/03/2019” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “08/03/2019” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “07/03/2019” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “04/03/2019” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “20/02/2019” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “22/01/2019” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “20/01/2019” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “11/01/2019” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “04/01/2019” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “17/12/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “13/12/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “10/12/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “07/12/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “03/12/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “30/11/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “25/11/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “22/11/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “19/11/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “14/11/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “01/11/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “26/10/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “25/10/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “16/10/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “11/10/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “09/10/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “26/09/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “20/09/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “17/09/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “31/08/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “29/08/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “21/08/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “20/08/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “05/08/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “30/07/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “21/06/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “14/05/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “04/05/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “03/05/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “30/04/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “20/04/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “19/04/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “04/03/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “14/02/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “23/01/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “17/01/2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “27/12/2017” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “13/12/2017” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “21/11/2017” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “25/08/2019” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “19/08/2019” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Duplicate ID “entry-33576”.

End tag “a” violates nesting rules.

No “i” element in scope but a “i” end tag seen.

Duplicate ID “mk-love-33576”.

Duplicate ID “entry-33542”.

Duplicate ID “mk-love-33542”.

Duplicate ID “entry-33553”.

Duplicate ID “mk-love-33553”.

Element “span” not allowed as child of element “ul” in this context. (Suppressing further errors from this subtree.)

Element “a” not allowed as child of element “ul” in this context. (Suppressing further errors from this subtree.)

CSS: “text-transform”: Parse Error.

Bad value “contentinfo” for attribute “role” on element “section”.

Uff.fi Desktop Insights

Last tested: 09/05/2016

Desktop

Desktop Speed

77%

Optimize images

Leverage browser caching

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Enable compression

Minify CSS

Minify HTML

Desktop Resource Breakdown

Total Resources	19
Number of Hosts	3
Static Resources	17
JavaScript Resources	3
CSS Resources	3

Uff.fi Mobile Insights

Last tested: 12/11/2019

Mobile

Mobile Usability

97%

Size tap targets appropriately

Mobile Speed

Optimize images

Enable compression

Leverage browser caching

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Reduce server response time

Minify JavaScript

Minify CSS

Mobile Resource Breakdown

Total Resources	124
Number of Hosts	4
Static Resources	121
JavaScript Resources	32
CSS Resources	17

Uff.fi Typos

www.uff.com
www.uff.net
www.uff.org
www.uff.info
www.uff.biz
www.uff.us
www.uff.mobi
www.ff.fi
www.uff.fi
www.yff.fi
www.uyff.fi
www.yuff.fi
www.hff.fi
www.uhff.fi
www.huff.fi
www.jff.fi
www.ujff.fi
www.juff.fi
www.iff.fi
www.uiff.fi
www.iuff.fi
www.uf.fi
www.ucf.fi
www.ufcf.fi
www.ucff.fi
www.udf.fi
www.ufdf.fi
www.udff.fi
www.urf.fi
www.ufrf.fi
www.urff.fi
www.utf.fi
www.uftf.fi
www.utff.fi
www.ugf.fi
www.ufgf.fi
www.ugff.fi
www.uvf.fi
www.ufvf.fi
www.uvff.fi
www.ufc.fi
www.uffc.fi
www.ufd.fi
www.uffd.fi
www.ufr.fi
www.uffr.fi
www.uft.fi
www.ufft.fi
www.ufg.fi
www.uffg.fi
www.ufv.fi
www.uffv.fi

Uff.fi Etusivu - UFF

Kierrättämällä jokainen voi vaikuttaa ilmastoon ja kestävään kehitykseen. Jatkamme lahjoitettujen, käyttökelpoisten vaatteiden elinkaarta ja hyödynnäm...

Quick Summary

Uff.fi General Information

Uff.fi Safety Information

Uff.fi Server Information

Uff.fi Domain Name Information

Uff.fi HTML Validation

Uff.fi Desktop Insights

Uff.fi Mobile Insights

Uff.fi Nearest Competitors

Uff.fi Typos