fo.no ▶ Fellesorganisasjonen (FO) | Stå opp for trygghet

Fo.no | Key Trends

Online Status

Offline

Server IP address resolved: No
Http response code: None
Last Checked: 01/30/2026

Fo.no attracts 1,514 unique visitors daily, generating 3,028 pageviews. The estimated value of fo.no is 2,311 USD. Each visitor views approximately 2.14 pages on average.

According to Majestic's traffic estimates, fo.no ranks 20,882 globally.

See the list of other websites hosted by DIGITALOCEAN-ASN - DigitalOcean, LLC, US.

Fo.no is registered with the .NO top-level domain. Explore additional websites within the .NO zone.

A recent examination on (July 04, 2025), indicates that fo.no has an expired SSL certificate issued by Let's Encrypt (expired on August 28, 2025). Click the "Refresh" button in the Safety Information section for updated SSL details. See the list of websites using SSL certificates issued by Let's Encrypt.

According to Google Safe Browsing, Google Safe Search and Symantec fo.no appears to be a safe domain.

Fo.no | General Site Information

Global Rank

Average Load Time

1.02sec

Links In Count

Website Value

$2,160

Audience Geography. Where are fo.no visitors located?

Country	Visitors

Country	Pageviews

Country	Rank

Where do visitors go on fo.no?

Subdomain	Pageviews

Subdomain	Pageviews per User

Subdomain	Reach

How popular is fo.no?

Period	Global Rank	Global Rank Delta

Days	Pageviews Rank	Pageviews Rank Delta	Pageviews per Million	Pageviews per Million Delta	Pageviews per User	Pageviews per User Delta

Days	Reach Rank	Reach Rank Delta	Reach per Million	Reach per Million Delta

Fo.no | Safety and Security Details

Overview

Last Updated: 01/30/2026

Overall result - fo.no 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/19/2025

fo.no is safe.

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

Google Safe Search

Last Updated: 04/24/2017

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

fo.no 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: 02/17/2021

fo.no is safe.

McAfee assesses fo.no 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 fo.no for mature or inappropriate content, only security checks are evaluated.

Web of Trust

Last Updated: 01/30/2026

fo.no child safety is unknown.

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

Fo.no | SSL Certificate Information

SSL Checker Tool

Domain	fo.prod13.dekodes.no
Issuer Organization	Let's Encrypt
Issuer	R10
Algorithm	RSA-SHA256
Valid form	05/30/2025
Expiration	08/28/2025
Signed	Certificate is not self signed
Additional Domains	brosjyrer.fo.no fo.no fo.prod13.dekodes.no ifsw2025.no www.fo.no www.ifsw2025.no

Fo.no | Server and Hosting Details

Server Location

Geolocation Tool

Fo.no ASN Information

ASN Lookup Tool

ASN ID: 14061
ASN Title: DIGITALOCEAN-ASN - DigitalOcean, LLC, US

Last Update: 09/11/2025

ASN Whois

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou.html
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/whois_reporting/index.html
#
# Copyright 1997-2018, American Registry for Internet Numbers, Ltd.
#

ASNumber: 14061
ASName: DIGITALOCEAN-ASN
ASHandle: AS14061
RegDate: 2012-09-25
Updated: 2012-09-25
Ref: https://rdap.arin.net/registry/autnum/14061

OrgName: DigitalOcean, LLC
OrgId: DO-13
Address: 101 Ave of the Americas
Address: 10th Floor
City: New York
StateProv: NY
PostalCode: 10013
Country: US
RegDate: 2012-05-14
Updated: 2018-07-17
Comment: http://www.digitalocean.com
Comment: Simple Cloud Hosting
Ref: https://rdap.arin.net/registry/entity/DO-13

OrgAbuseHandle: ABUSE5232-ARIN
OrgAbuseName: Abuse, DigitalOcean
OrgAbusePhone: +1-347-875-6044
OrgAbuseEmail: abuse@digitalocean.com
OrgAbuseRef: https://rdap.arin.net/registry/entity/ABUSE5232-ARIN

OrgNOCHandle: NOC32014-ARIN
OrgNOCName: Network Operations Center
OrgNOCPhone: +1-347-875-6044
OrgNOCEmail: noc@digitalocean.com
OrgNOCRef: https://rdap.arin.net/registry/entity/NOC32014-ARIN

OrgTechHandle: NOC32014-ARIN
OrgTechName: Network Operations Center
OrgTechPhone: +1-347-875-6044
OrgTechEmail: noc@digitalocean.com
OrgTechRef: https://rdap.arin.net/registry/entity/NOC32014-ARIN

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou.html
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/whois_reporting/index.html
#
# Copyright 1997-2018, American Registry for Internet Numbers, Ltd.
#

Fo.no | Domain Name Information

WHOIS

WHOIS Lookup Tool

Domain Whois

% By looking up information in the domain registration directory
% service, you confirm that you accept the terms and conditions of the
% service:
% https://www.norid.no/en/domeneoppslag/vilkar/
%
% Norid AS holds the copyright to the lookup service, content,
% layout and the underlying collections of information used in the
% service (cf. the Act on Intellectual Property of May 2, 1961, No.
% 2). Any commercial use of information from the service, including
% targeted marketing, is prohibited. Using information from the domain
% registration directory service in violation of the terms and
% conditions may result in legal prosecution.
%
% The whois service at port 43 is intended to contribute to resolving
% technical problems where individual domains threaten the
% functionality, security and stability of other domains or the
% internet as an infrastructure. It does not give any information
% about who the holder of a domain is. To find information about a
% domain holder, please visit our website:
% https://www.norid.no/en/domeneoppslag/

Domain Information

NORID Handle...............: FO50D-NORID
Domain Name................: fo.no
Registrar Handle...........: REG42-NORID
Tech-c Handle..............: DH38R-NORID
Name Server Handle.........: NSHY11H-NORID
Name Server Handle.........: NSHY46H-NORID
Name Server Handle.........: NSHY81H-NORID
DNSSEC.....................: Signed
DS Key Tag 1...........: 30549
Algorithm 1...........: 15
Digest Type 1...........: 2
Digest 1...........: ad3f3d75df6c63375b908793346d480c5e217aaab19f4f2fb9ef1b09c3aadb20
DS Key Tag 2...........: 30549
Algorithm 2...........: 15
Digest Type 2...........: 4
Digest 2...........: 8fbf7ad8d882882123fdf1b62b80c1869cf8c0756f295a3807f9ac8096bd55432a25bbd475054d77fedc4ba5f5ae4b6f

Additional information:
Created: 2001-02-27
Last updated: 2023-01-01

DNS Records

DNS Lookup Tool

Host	A Record	TTL

Host	MX Record	Priority	TTL

Host	NS Record	TTL

Host	TXT Record	TTL

Fo.no | HTML Validation Report

HTML Validation Tool

Warnings

The “type” attribute is unnecessary for JavaScript resources.

Consider using the “h1” element as a top-level heading only (all “h1” elements are treated as top-level headings by many screen readers and other tools).

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

The first occurrence of ID “Group_212” was here.

The first occurrence of ID “Group_193” was here.

The first occurrence of ID “Group_192” was here.

The first occurrence of ID “Path_176” was here.

The first occurrence of ID “Group_195” was here.

The first occurrence of ID “Group_194” was here.

The first occurrence of ID “Path_177” was here.

The first occurrence of ID “Group_197” was here.

The first occurrence of ID “Group_196” was here.

The first occurrence of ID “Path_178” was here.

The first occurrence of ID “Group_199” was here.

The first occurrence of ID “Group_198” was here.

The first occurrence of ID “Path_179” was here.

The first occurrence of ID “Group_201” was here.

The first occurrence of ID “Group_200” was here.

The first occurrence of ID “Path_180” was here.

The first occurrence of ID “Group_203” was here.

The first occurrence of ID “Group_202” was here.

The first occurrence of ID “Path_181” was here.

The first occurrence of ID “Group_205” was here.

The first occurrence of ID “Group_204” was here.

The first occurrence of ID “Path_182” was here.

The first occurrence of ID “Group_207” was here.

The first occurrence of ID “Group_206” was here.

The first occurrence of ID “Path_183” was here.

The first occurrence of ID “Group_209” was here.

The first occurrence of ID “Group_208” was here.

The first occurrence of ID “Ellipse_14” was here.

The first occurrence of ID “Group_211” was here.

The first occurrence of ID “Group_210” was here.

The first occurrence of ID “Ellipse_15” was here.

The first occurrence of ID “Capa_1” was here.

The first occurrence of ID “Group_225” was here.

The first occurrence of ID “Group_214” was here.

The first occurrence of ID “Group_213” was here.

The first occurrence of ID “Path_184” was here.

The first occurrence of ID “Group_216” was here.

The first occurrence of ID “Group_215” was here.

The first occurrence of ID “Path_185” was here.

The first occurrence of ID “Group_218” was here.

The first occurrence of ID “Group_217” was here.

The first occurrence of ID “Path_186” was here.

The first occurrence of ID “Group_220” was here.

The first occurrence of ID “Group_219” was here.

The first occurrence of ID “Path_187” was here.

The first occurrence of ID “Group_222” was here.

The first occurrence of ID “Group_221” was here.

The first occurrence of ID “Path_188” was here.

The first occurrence of ID “Group_224” was here.

The first occurrence of ID “Group_223” was here.

The first occurrence of ID “Path_189” was here.

The first occurrence of ID “Group_191” was here.

The first occurrence of ID “Group_168” was here.

The first occurrence of ID “Group_167” was here.

The first occurrence of ID “Path_163” was here.

The first occurrence of ID “Group_170” was here.

The first occurrence of ID “Group_169” was here.

The first occurrence of ID “Path_164” was here.

The first occurrence of ID “Group_172” was here.

The first occurrence of ID “Group_171” was here.

The first occurrence of ID “Path_165” was here.

The first occurrence of ID “Group_174” was here.

The first occurrence of ID “Group_173” was here.

The first occurrence of ID “Path_166” was here.

The first occurrence of ID “Group_176” was here.

The first occurrence of ID “Group_175” was here.

The first occurrence of ID “Path_167” was here.

The first occurrence of ID “Group_178” was here.

The first occurrence of ID “Group_177” was here.

The first occurrence of ID “Path_168” was here.

The first occurrence of ID “Group_180” was here.

The first occurrence of ID “Group_179” was here.

The first occurrence of ID “Path_169” was here.

The first occurrence of ID “Group_182” was here.

The first occurrence of ID “Group_181” was here.

The first occurrence of ID “Path_170” was here.

The first occurrence of ID “Group_184” was here.

The first occurrence of ID “Group_183” was here.

The first occurrence of ID “Path_171” was here.

The first occurrence of ID “Group_186” was here.

The first occurrence of ID “Group_185” was here.

The first occurrence of ID “Path_172” was here.

The first occurrence of ID “Group_188” was here.

The first occurrence of ID “Group_187” was here.

The first occurrence of ID “Path_173” was here.

The first occurrence of ID “Group_190” was here.

The first occurrence of ID “Group_189” was here.

The first occurrence of ID “Path_174” was here.

Errors

Saw “<?”. Probable cause: Attempt to use an XML processing instruction in HTML. (XML processing instructions are not supported in HTML.)

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

Duplicate ID “Group_212”.

Duplicate ID “Group_193”.

Duplicate ID “Group_192”.

Duplicate ID “Path_176”.

Duplicate ID “Group_195”.

Duplicate ID “Group_194”.

Duplicate ID “Path_177”.

Duplicate ID “Group_197”.

Duplicate ID “Group_196”.

Duplicate ID “Path_178”.

Duplicate ID “Group_199”.

Duplicate ID “Group_198”.

Duplicate ID “Path_179”.

Duplicate ID “Group_201”.

Duplicate ID “Group_200”.

Duplicate ID “Path_180”.

Duplicate ID “Group_203”.

Duplicate ID “Group_202”.

Duplicate ID “Path_181”.

Duplicate ID “Group_205”.

Duplicate ID “Group_204”.

Duplicate ID “Path_182”.

Duplicate ID “Group_207”.

Duplicate ID “Group_206”.

Duplicate ID “Path_183”.

Duplicate ID “Group_209”.

Duplicate ID “Group_208”.

Duplicate ID “Ellipse_14”.

Duplicate ID “Group_211”.

Duplicate ID “Group_210”.

Duplicate ID “Ellipse_15”.

Duplicate ID “Capa_1”.

Duplicate ID “Group_225”.

Duplicate ID “Group_214”.

Duplicate ID “Group_213”.

Duplicate ID “Path_184”.

Duplicate ID “Group_216”.

Duplicate ID “Group_215”.

Duplicate ID “Path_185”.

Duplicate ID “Group_218”.

Duplicate ID “Group_217”.

Duplicate ID “Path_186”.

Duplicate ID “Group_220”.

Duplicate ID “Group_219”.

Duplicate ID “Path_187”.

Duplicate ID “Group_222”.

Duplicate ID “Group_221”.

Duplicate ID “Path_188”.

Duplicate ID “Group_224”.

Duplicate ID “Group_223”.

Duplicate ID “Path_189”.

Duplicate ID “Group_191”.

Duplicate ID “Group_168”.

Duplicate ID “Group_167”.

Duplicate ID “Path_163”.

Duplicate ID “Group_170”.

Duplicate ID “Group_169”.

Duplicate ID “Path_164”.

Duplicate ID “Group_172”.

Duplicate ID “Group_171”.

Duplicate ID “Path_165”.

Duplicate ID “Group_174”.

Duplicate ID “Group_173”.

Duplicate ID “Path_166”.

Duplicate ID “Group_176”.

Duplicate ID “Group_175”.

Duplicate ID “Path_167”.

Duplicate ID “Group_178”.

Duplicate ID “Group_177”.

Duplicate ID “Path_168”.

Duplicate ID “Group_180”.

Duplicate ID “Group_179”.

Duplicate ID “Path_169”.

Duplicate ID “Group_182”.

Duplicate ID “Group_181”.

Duplicate ID “Path_170”.

Duplicate ID “Group_184”.

Duplicate ID “Group_183”.

Duplicate ID “Path_171”.

Duplicate ID “Group_186”.

Duplicate ID “Group_185”.

Duplicate ID “Path_172”.

Duplicate ID “Group_188”.

Duplicate ID “Group_187”.

Duplicate ID “Path_173”.

Duplicate ID “Group_190”.

Duplicate ID “Group_189”.

Duplicate ID “Path_174”.

Bad value “placeholder-content-4 news” for attribute “id” on element “section”: An ID must not contain whitespace.

End tag “h1” seen, but there were open elements.

End tag “h3” seen, but there were open elements.

Bad value “placeholder-content-5 activities” for attribute “id” on element “section”: An ID must not contain whitespace.

An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.

The text content of element “time” was not in the required format: The literal did not satisfy the time-datetime format.

Start tag “a” seen but an element of the same type was already open.

End tag “a” violates nesting rules.

Cannot recover after last error. Any further errors will be ignored.

Fo.no | Desktop Performance Insights

Last tested: 05/15/2017

Desktop

Desktop Speed

78%

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

Optimize images

Leverage browser caching

Prioritize visible content

Minify JavaScript

Desktop Resource Breakdown

Total Resources	36
Number of Hosts	4
Static Resources	33
JavaScript Resources	8
CSS Resources	2

Fo.no | Mobile Performance Insights

Last tested: 06/09/2018

Mobile

Mobile Usability

60%

Use legible font sizes

Size tap targets appropriately

Configure the viewport

Size content to viewport

Mobile Speed

57%

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

Optimize images

Prioritize visible content

Reduce server response time

Leverage browser caching

Minify JavaScript

Minify HTML

Mobile Resource Breakdown

Total Resources	41
Number of Hosts	5
Static Resources	35
JavaScript Resources	8
CSS Resources	2

Fo.no | Common Typographical Errors

www.fo.com
www.fo.net
www.fo.org
www.fo.info
www.fo.biz
www.fo.us
www.fo.mobi
www.o.no
www.fo.no
www.co.no
www.fco.no
www.cfo.no
www.do.no
www.fdo.no
www.dfo.no
www.ro.no
www.fro.no
www.rfo.no
www.to.no
www.fto.no
www.tfo.no
www.go.no
www.fgo.no
www.gfo.no
www.vo.no
www.fvo.no
www.vfo.no
www.f.no
www.fi.no
www.foi.no
www.fio.no
www.fk.no
www.fok.no
www.fko.no
www.fl.no
www.fol.no
www.flo.no
www.fp.no
www.fop.no
www.fpo.no

Fo.no Fellesorganisasjonen (FO) | Stå opp for trygghet | Bli medlem

FO er fagforeningen for sosialarbeidere, og organiserer nærmere 35 000 barnevernspedagoger, sosionomer, vernepleiere og velferdsvitere. Les mer >>

Fo.no | Key Trends

Fo.no | General Site Information

Fo.no | Safety and Security Details

Fo.no | Server and Hosting Details

Fo.no | Domain Name Information

Fo.no | HTML Validation Report

Fo.no | Desktop Performance Insights

Fo.no | Mobile Performance Insights

Fo.no | Competitors Analysis

Fo.no | Common Typographical Errors