Hardenize Report: uio.no

Web Security Overview

HTTPS

Web sites need to use encryption to help their visitors know they're in the right place, as well as provide confidentiality and content integrity. Sites that don't support HTTPS may expose sensitive data and have their pages modified and subverted.
There are issues with this site's HTTPS configuration.

For all sites VERY IMPORTANT medium EFFORT

HTTPS Redirection

To deploy HTTPS properly, web sites must redirect all unsafe (plaintext) traffic to the encrypted variant. This approach ensures that no sensitive data is exposed and that further security technologies can be activated.

For all sites VERY IMPORTANT low EFFORT

HTTP Strict Transport Security

HTTP Strict Transport Security (HSTS) is an HTTPS extension that instructs browsers to remember sites that use encryption and enforce strict security requirements. Without HSTS, active network attacks are easy to carry out.
There are issues with this site's HSTS configuration.

For important sites VERY IMPORTANT medium EFFORT

HSTS Preloaded

HSTS Preloading is informing browsers in advance about a site's use of HSTS, which means that strict security can be enforced even on the first visit. This approach provides best HTTPS security available today.

For important sites VERY IMPORTANT medium EFFORT

Content Security Policy

Content Security Policy (CSP) is an additional security layer that enables web sites to control browser behavior, creating a safety net that can counter attacks such as cross-site scripting.

For important sites IMPORTANT high EFFORT

Email Security Overview

STARTTLS

All hosts that receive email need encryption to ensure confidentiality of email messages. Email servers thus need to support STARTTLS, as well as provide decent TLS configuration and correct certificates.

For all sites VERY IMPORTANT low EFFORT

SPF

Sender Policy Framework (SPF) enables organizations to designate servers that are allowed to send email messages on their behalf. With SPF in place, spam is easier to identify.

For important sites IMPORTANT low EFFORT

DMARC

Domain-based Message Authentication, Reporting, and Conformance (DMARC) is a mechanism that allows organizations to specify how unauthenticated email (identified using SPF and DKIM) should be handled.

For important sites IMPORTANT low EFFORT

Domain Registration

Your security begins with the security of your domain name. If someone takes control of your domain name then they can update the name server configuration to send users elsewhere, or they can transfer the domain name to another party. For best results, fully lock your domain names at registry and registrar levels.

Test passed

Everything seems to be well configured. Well done.

Registration Data Access Protocol (RDAP)

The RDAP protocol enables users to access current registration data and was created as an eventual replacement for the WHOIS protocol. RDAP has several advantages over the WHOIS protocol, including support for internationalization, secure access to data, and the ability to provide differentiated access to registration data.

Parsed Raw Data Model

Registrant	-
Lookup Time	18 Apr 2024 22:52 UTC
Source	https://rdap.norid.no/domain/uio.no
Registrar
Registrar	SIKT - KUNNSKAPSSEKTORENS TJENESTELEVERANDØR
Registrar IANA ID	919477822
Events
Registration	14 Nov 1999 23:00 UTC
Update	15 Nov 2023 02:19 UTC
Expiration	-
Configuration
Statuses	-
Registrar Lock	-
Registry Lock	-
Nameservers	ns1.uio.no 129.240.2.6 2001:700:100:2:0:0:0:6 ns2.uio.no 129.240.2.42 2001:700:100:425:0:0:0:42 nn.uninett.no 158.38.0.181 2001:700:0:503:0:0:aa:5302 server.nordu.net
Contacts
Technical	UiO.no Hostmaster NORWAY Email: hostmaster@usit.uio.no Phone: +47.22852470
Registrar	SIKT - KUNNSKAPSSEKTORENS TJENESTELEVERANDØR Postboks 5782 Torgarden NO-7437 NORWAY Email: kontakt@sikt.no Phone: +47.73557900

{
  "meta": {
    "timestamp": "2024-04-18T22:52:53Z",
    "id": "74b4cb37-b04e-4ee3-a0ea-94b611535a51",
    "type": "HZ_REGISTRABLE_DOMAIN",
    "schemaVersion": "2022-02-02",
    "producer": "whois-rdap-clients/2022-03-23",
    "source": "NET",
    "status": "OK",
    "duration": "0.179s"
  },
  "name": "uio.no",
  "punyName": "uio.no",
  "source": "SOURCE_RDAP",
  "sourceLocation": "https://rdap.norid.no/domain/uio.no",
  "sourceRaw": "{\"entities\":[{\"events\":[{\"eventAction\":\"registration\",\"eventDate\":\"2022-06-03T09:26:53Z\"}],\"handle\":\"UH2415R-NORID\",\"links\":[{\"href\":\"https://rdap.norid.no/entity/UH2415R-NORID\",\"rel\":\"self\",\"type\":\"application/rdap+json\",\"value\":\"https://rdap.norid.no/entity/UH2415R-NORID\"}],\"objectClassName\":\"entity\",\"roles\":[\"technical\"],\"vcardArray\":[\"vcard\",[[\"version\",{},\"text\",\"4.0\"],[\"fn\",{},\"text\",\"UiO.no Hostmaster\"],[\"kind\",{},\"text\",\"group\"],[\"adr\",{},\"text\",[\"\",\"\",[],\"\",\"\",\"\",\"NORWAY\"]],[\"tel\",{\"type\":[\"voice\"]},\"uri\",\"tel:+47.22852470\"],[\"email\",{\"pref\":\"1\"},\"text\",\"hostmaster@usit.uio.no\"]]]},{\"events\":[{\"eventAction\":\"registration\",\"eventDate\":\"2022-05-31T10:08:09Z\"},{\"eventAction\":\"last changed\",\"eventDate\":\"2023-12-01T08:37:54Z\"}],\"handle\":\"reg1103-NORID\",\"links\":[{\"href\":\"https://rdap.norid.no/entity/reg1103-NORID\",\"rel\":\"self\",\"type\":\"application/rdap+json\",\"value\":\"https://rdap.norid.no/entity/reg1103-NORID\"}],\"objectClassName\":\"entity\",\"publicIds\":[{\"identifier\":\"919477822\",\"type\":\"Norwegian organization number\"},{\"identifier\":\"reg1103\",\"type\":\"Norid registrar ID\"}],\"roles\":[\"registrar\"],\"vcardArray\":[\"vcard\",[[\"version\",{},\"text\",\"4.0\"],[\"fn\",{},\"text\",\"SIKT - KUNNSKAPSSEKTORENS TJENESTELEVERANDØR\"],[\"kind\",{},\"text\",\"org\"],[\"adr\",{},\"text\",[\"\",\"\",[\"Postboks 5782 Torgarden\"],\"Trondheim\",\"\",\"NO-7437\",\"NORWAY\"]],[\"tel\",{\"type\":[\"voice\"]},\"uri\",\"tel:+47.73557900\"],[\"email\",{\"pref\":\"1\"},\"text\",\"kontakt@sikt.no\"]]]}],\"events\":[{\"eventAction\":\"registration\",\"eventDate\":\"1999-11-14T23:00:00Z\"},{\"eventAction\":\"last changed\",\"eventDate\":\"2023-11-15T02:19:28Z\"}],\"handle\":\"UIO16D-NORID\",\"ldhName\":\"uio.no\",\"links\":[{\"href\":\"https://rdap.norid.no/domain/uio.no\",\"rel\":\"self\",\"type\":\"application/rdap+json\",\"value\":\"https://rdap.norid.no/domain/uio.no\"}],\"nameservers\":[{\"entities\":[{\"events\":[{\"eventAction\":\"registration\",\"eventDate\":\"2018-07-03T12:29:46Z\"},{\"eventAction\":\"last changed\",\"eventDate\":\"2018-07-05T12:33:59Z\"}],\"handle\":\"UH1688R-NORID\",\"links\":[{\"href\":\"https://rdap.norid.no/entity/UH1688R-NORID\",\"rel\":\"self\",\"type\":\"application/rdap+json\",\"value\":\"https://rdap.norid.no/entity/UH1688R-NORID\"}],\"objectClassName\":\"entity\",\"roles\":[\"technical\"],\"vcardArray\":[\"vcard\",[[\"version\",{},\"text\",\"4.0\"],[\"fn\",{},\"text\",\"UiO.no Hostmaster\"],[\"kind\",{},\"text\",\"group\"],[\"adr\",{},\"text\",[\"\",\"\",[],\"\",\"\",\"\",\"NORWAY\"]],[\"tel\",{\"type\":[\"voice\"]},\"uri\",\"tel:+47.22852470\"],[\"email\",{\"pref\":\"1\"},\"text\",\"hostmaster@usit.uio.no\"]]]}],\"events\":[{\"eventAction\":\"registration\",\"eventDate\":\"2010-10-01T16:29:49Z\"},{\"eventAction\":\"last changed\",\"eventDate\":\"2022-06-28T07:00:42Z\"}],\"handle\":\"NSUI125H-NORID\",\"ipAddresses\":{\"v4\":[\"129.240.2.6\"],\"v6\":[\"2001:700:100:2::6\"]},\"ldhName\":\"ns1.uio.no\",\"links\":[{\"href\":\"https://rdap.norid.no/nameserver_handle/NSUI125H-NORID\",\"rel\":\"self\",\"type\":\"application/rdap+json\",\"value\":\"https://rdap.norid.no/nameserver_handle/NSUI125H-NORID\"}],\"objectClassName\":\"nameserver\"},{\"entities\":[{\"events\":[{\"eventAction\":\"registration\",\"eventDate\":\"2018-07-03T12:29:46Z\"},{\"eventAction\":\"last changed\",\"eventDate\":\"2018-07-05T12:33:59Z\"}],\"handle\":\"UH1688R-NORID\",\"links\":[{\"href\":\"https://rdap.norid.no/entity/UH1688R-NORID\",\"rel\":\"self\",\"type\":\"application/rdap+json\",\"value\":\"https://rdap.norid.no/entity/UH1688R-NORID\"}],\"objectClassName\":\"entity\",\"roles\":[\"technical\"],\"vcardArray\":[\"vcard\",[[\"version\",{},\"text\",\"4.0\"],[\"fn\",{},\"text\",\"UiO.no Hostmaster\"],[\"kind\",{},\"text\",\"group\"],[\"adr\",{},\"text\",[\"\",\"\",[],\"\",\"\",\"\",\"NORWAY\"]],[\"tel\",{\"type\":[\"voice\"]},\"uri\",\"tel:+47.22852470\"],[\"email\",{\"pref\":\"1\"},\"text\",\"hostmaster@usit.uio.no\"]]]}],\"events\":[{\"eventAction\":\"registration\",\"eventDate\":\"2010-10-01T16:29:49Z\"},{\"eventAction\":\"last changed\",\"eventDate\":\"2022-06-28T07:00:42Z\"}],\"handle\":\"NSUI126H-NORID\",\"ipAddresses\":{\"v4\":[\"129.240.2.42\"],\"v6\":[\"2001:700:100:425::42\"]},\"ldhName\":\"ns2.uio.no\",\"links\":[{\"href\":\"https://rdap.norid.no/nameserver_handle/NSUI126H-NORID\",\"rel\":\"self\",\"type\":\"application/rdap+json\",\"value\":\"https://rdap.norid.no/nameserver_handle/NSUI126H-NORID\"}],\"objectClassName\":\"nameserver\"},{\"entities\":[{\"events\":[{\"eventAction\":\"registration\",\"eventDate\":\"2010-10-01T16:26:22Z\"},{\"eventAction\":\"last changed\",\"eventDate\":\"2020-11-09T14:14:42Z\"}],\"handle\":\"UH9R-NORID\",\"links\":[{\"href\":\"https://rdap.norid.no/entity/UH9R-NORID\",\"rel\":\"self\",\"type\":\"application/rdap+json\",\"value\":\"https://rdap.norid.no/entity/UH9R-NORID\"}],\"objectClassName\":\"entity\",\"roles\":[\"technical\"],\"vcardArray\":[\"vcard\",[[\"version\",{},\"text\",\"4.0\"],[\"fn\",{},\"text\",\"UNINETT Hostmaster\"],[\"kind\",{},\"text\",\"group\"],[\"adr\",{},\"text\",[\"\",\"\",[],\"\",\"\",\"\",\"NORWAY\"]],[\"tel\",{\"type\":[\"voice\"]},\"uri\",\"tel:+47.73557900\"],[\"email\",{\"pref\":\"1\"},\"text\",\"kontakt@uninett.no\"]]]}],\"events\":[{\"eventAction\":\"registration\",\"eventDate\":\"2010-10-01T16:29:36Z\"},{\"eventAction\":\"last changed\",\"eventDate\":\"2022-06-28T07:00:53Z\"}],\"handle\":\"NN172H-NORID\",\"ipAddresses\":{\"v4\":[\"158.38.0.181\"],\"v6\":[\"2001:700:0:503::aa:5302\"]},\"ldhName\":\"nn.uninett.no\",\"links\":[{\"href\":\"https://rdap.norid.no/nameserver_handle/NN172H-NORID\",\"rel\":\"self\",\"type\":\"application/rdap+json\",\"value\":\"https://rdap.norid.no/nameserver_handle/NN172H-NORID\"}],\"objectClassName\":\"nameserver\"},{\"events\":[{\"eventAction\":\"registration\",\"eventDate\":\"2010-10-01T16:31:08Z\"}],\"handle\":\"SERV111H-NORID\",\"ldhName\":\"server.nordu.net\",\"links\":[{\"href\":\"https://rdap.norid.no/nameserver_handle/SERV111H-NORID\",\"rel\":\"self\",\"type\":\"application/rdap+json\",\"value\":\"https://rdap.norid.no/nameserver_handle/SERV111H-NORID\"}],\"objectClassName\":\"nameserver\"}],\"notices\":[{\"description\":[\"By looking up information in the domain registration directory\",\"service, you confirm that you accept the terms and conditions\",\"of the service.\",\"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.\"],\"links\":[{\"href\":\"https://www.norid.no/en/domeneoppslag/vilkar\",\"rel\":\"alternate\",\"type\":\"text/html\",\"value\":\"https://rdap.norid.no/domain/uio.no\"}],\"title\":\"Terms of use\"}],\"objectClassName\":\"domain\",\"rdapConformance\":[\"rdap_level_0\",\"rdap_objectTag_level_0\",\"norid_level_0\"]}",
  "tld": "no",
  "suffix": "no",
  "createTime": "1999-11-14T23:00:00Z",
  "updateTime": "2023-11-15T02:19:28Z",
  "registrarName": "SIKT - KUNNSKAPSSEKTORENS TJENESTELEVERANDØR",
  "registrarIanaId": "919477822",
  "nameservers": [{
    "name": "ns1.uio.no",
    "punyName": "",
    "addresses": ["129.240.2.6", "2001:700:100:2:0:0:0:6"]
  }, {
    "name": "ns2.uio.no",
    "punyName": "",
    "addresses": ["129.240.2.42", "2001:700:100:425:0:0:0:42"]
  }, {
    "name": "nn.uninett.no",
    "punyName": "",
    "addresses": ["158.38.0.181", "2001:700:0:503:0:0:aa:5302"]
  }, {
    "name": "server.nordu.net",
    "punyName": "",
    "addresses": []
  }],
  "statuses": [],
  "sourceStatuses": [],
  "contacts": [{
    "type": "CONTACT_TECHNICAL",
    "organization": "UiO.no Hostmaster",
    "country": "NORWAY",
    "email": "hostmaster@usit.uio.no",
    "phone": "+47.22852470"
  }, {
    "type": "CONTACT_REGISTRAR",
    "organization": "SIKT - KUNNSKAPSSEKTORENS TJENESTELEVERANDØR",
    "street1": "Postboks 5782 Torgarden",
    "postcode": "NO-7437",
    "country": "NORWAY",
    "email": "kontakt@sikt.no",
    "phone": "+47.73557900"
  }]
}

{
  "entities": [
    {
      "events": [
        {
          "eventAction": "registration",
          "eventDate": "2022-06-03T09:26:53Z"
        }
      ],
      "handle": "UH2415R-NORID",
      "links": [
        {
          "href": "https://rdap.norid.no/entity/UH2415R-NORID",
          "rel": "self",
          "type": "application/rdap+json",
          "value": "https://rdap.norid.no/entity/UH2415R-NORID"
        }
      ],
      "objectClassName": "entity",
      "roles": [
        "technical"
      ],
      "vcardArray": [
        "vcard",
        [
          [
            "version",
            {},
            "text",
            "4.0"
          ],
          [
            "fn",
            {},
            "text",
            "UiO.no Hostmaster"
          ],
          [
            "kind",
            {},
            "text",
            "group"
          ],
          [
            "adr",
            {},
            "text",
            [
              "",
              "",
              [],
              "",
              "",
              "",
              "NORWAY"
            ]
          ],
          [
            "tel",
            {
              "type": [
                "voice"
              ]
            },
            "uri",
            "tel:+47.22852470"
          ],
          [
            "email",
            {
              "pref": "1"
            },
            "text",
            "hostmaster@usit.uio.no"
          ]
        ]
      ]
    },
    {
      "events": [
        {
          "eventAction": "registration",
          "eventDate": "2022-05-31T10:08:09Z"
        },
        {
          "eventAction": "last changed",
          "eventDate": "2023-12-01T08:37:54Z"
        }
      ],
      "handle": "reg1103-NORID",
      "links": [
        {
          "href": "https://rdap.norid.no/entity/reg1103-NORID",
          "rel": "self",
          "type": "application/rdap+json",
          "value": "https://rdap.norid.no/entity/reg1103-NORID"
        }
      ],
      "objectClassName": "entity",
      "publicIds": [
        {
          "identifier": "919477822",
          "type": "Norwegian organization number"
        },
        {
          "identifier": "reg1103",
          "type": "Norid registrar ID"
        }
      ],
      "roles": [
        "registrar"
      ],
      "vcardArray": [
        "vcard",
        [
          [
            "version",
            {},
            "text",
            "4.0"
          ],
          [
            "fn",
            {},
            "text",
            "SIKT - KUNNSKAPSSEKTORENS TJENESTELEVERANDØR"
          ],
          [
            "kind",
            {},
            "text",
            "org"
          ],
          [
            "adr",
            {},
            "text",
            [
              "",
              "",
              [
                "Postboks 5782 Torgarden"
              ],
              "Trondheim",
              "",
              "NO-7437",
              "NORWAY"
            ]
          ],
          [
            "tel",
            {
              "type": [
                "voice"
              ]
            },
            "uri",
            "tel:+47.73557900"
          ],
          [
            "email",
            {
              "pref": "1"
            },
            "text",
            "kontakt@sikt.no"
          ]
        ]
      ]
    }
  ],
  "events": [
    {
      "eventAction": "registration",
      "eventDate": "1999-11-14T23:00:00Z"
    },
    {
      "eventAction": "last changed",
      "eventDate": "2023-11-15T02:19:28Z"
    }
  ],
  "handle": "UIO16D-NORID",
  "ldhName": "uio.no",
  "links": [
    {
      "href": "https://rdap.norid.no/domain/uio.no",
      "rel": "self",
      "type": "application/rdap+json",
      "value": "https://rdap.norid.no/domain/uio.no"
    }
  ],
  "nameservers": [
    {
      "entities": [
        {
          "events": [
            {
              "eventAction": "registration",
              "eventDate": "2018-07-03T12:29:46Z"
            },
            {
              "eventAction": "last changed",
              "eventDate": "2018-07-05T12:33:59Z"
            }
          ],
          "handle": "UH1688R-NORID",
          "links": [
            {
              "href": "https://rdap.norid.no/entity/UH1688R-NORID",
              "rel": "self",
              "type": "application/rdap+json",
              "value": "https://rdap.norid.no/entity/UH1688R-NORID"
            }
          ],
          "objectClassName": "entity",
          "roles": [
            "technical"
          ],
          "vcardArray": [
            "vcard",
            [
              [
                "version",
                {},
                "text",
                "4.0"
              ],
              [
                "fn",
                {},
                "text",
                "UiO.no Hostmaster"
              ],
              [
                "kind",
                {},
                "text",
                "group"
              ],
              [
                "adr",
                {},
                "text",
                [
                  "",
                  "",
                  [],
                  "",
                  "",
                  "",
                  "NORWAY"
                ]
              ],
              [
                "tel",
                {
                  "type": [
                    "voice"
                  ]
                },
                "uri",
                "tel:+47.22852470"
              ],
              [
                "email",
                {
                  "pref": "1"
                },
                "text",
                "hostmaster@usit.uio.no"
              ]
            ]
          ]
        }
      ],
      "events": [
        {
          "eventAction": "registration",
          "eventDate": "2010-10-01T16:29:49Z"
        },
        {
          "eventAction": "last changed",
          "eventDate": "2022-06-28T07:00:42Z"
        }
      ],
      "handle": "NSUI125H-NORID",
      "ipAddresses": {
        "v4": [
          "129.240.2.6"
        ],
        "v6": [
          "2001:700:100:2::6"
        ]
      },
      "ldhName": "ns1.uio.no",
      "links": [
        {
          "href": "https://rdap.norid.no/nameserver_handle/NSUI125H-NORID",
          "rel": "self",
          "type": "application/rdap+json",
          "value": "https://rdap.norid.no/nameserver_handle/NSUI125H-NORID"
        }
      ],
      "objectClassName": "nameserver"
    },
    {
      "entities": [
        {
          "events": [
            {
              "eventAction": "registration",
              "eventDate": "2018-07-03T12:29:46Z"
            },
            {
              "eventAction": "last changed",
              "eventDate": "2018-07-05T12:33:59Z"
            }
          ],
          "handle": "UH1688R-NORID",
          "links": [
            {
              "href": "https://rdap.norid.no/entity/UH1688R-NORID",
              "rel": "self",
              "type": "application/rdap+json",
              "value": "https://rdap.norid.no/entity/UH1688R-NORID"
            }
          ],
          "objectClassName": "entity",
          "roles": [
            "technical"
          ],
          "vcardArray": [
            "vcard",
            [
              [
                "version",
                {},
                "text",
                "4.0"
              ],
              [
                "fn",
                {},
                "text",
                "UiO.no Hostmaster"
              ],
              [
                "kind",
                {},
                "text",
                "group"
              ],
              [
                "adr",
                {},
                "text",
                [
                  "",
                  "",
                  [],
                  "",
                  "",
                  "",
                  "NORWAY"
                ]
              ],
              [
                "tel",
                {
                  "type": [
                    "voice"
                  ]
                },
                "uri",
                "tel:+47.22852470"
              ],
              [
                "email",
                {
                  "pref": "1"
                },
                "text",
                "hostmaster@usit.uio.no"
              ]
            ]
          ]
        }
      ],
      "events": [
        {
          "eventAction": "registration",
          "eventDate": "2010-10-01T16:29:49Z"
        },
        {
          "eventAction": "last changed",
          "eventDate": "2022-06-28T07:00:42Z"
        }
      ],
      "handle": "NSUI126H-NORID",
      "ipAddresses": {
        "v4": [
          "129.240.2.42"
        ],
        "v6": [
          "2001:700:100:425::42"
        ]
      },
      "ldhName": "ns2.uio.no",
      "links": [
        {
          "href": "https://rdap.norid.no/nameserver_handle/NSUI126H-NORID",
          "rel": "self",
          "type": "application/rdap+json",
          "value": "https://rdap.norid.no/nameserver_handle/NSUI126H-NORID"
        }
      ],
      "objectClassName": "nameserver"
    },
    {
      "entities": [
        {
          "events": [
            {
              "eventAction": "registration",
              "eventDate": "2010-10-01T16:26:22Z"
            },
            {
              "eventAction": "last changed",
              "eventDate": "2020-11-09T14:14:42Z"
            }
          ],
          "handle": "UH9R-NORID",
          "links": [
            {
              "href": "https://rdap.norid.no/entity/UH9R-NORID",
              "rel": "self",
              "type": "application/rdap+json",
              "value": "https://rdap.norid.no/entity/UH9R-NORID"
            }
          ],
          "objectClassName": "entity",
          "roles": [
            "technical"
          ],
          "vcardArray": [
            "vcard",
            [
              [
                "version",
                {},
                "text",
                "4.0"
              ],
              [
                "fn",
                {},
                "text",
                "UNINETT Hostmaster"
              ],
              [
                "kind",
                {},
                "text",
                "group"
              ],
              [
                "adr",
                {},
                "text",
                [
                  "",
                  "",
                  [],
                  "",
                  "",
                  "",
                  "NORWAY"
                ]
              ],
              [
                "tel",
                {
                  "type": [
                    "voice"
                  ]
                },
                "uri",
                "tel:+47.73557900"
              ],
              [
                "email",
                {
                  "pref": "1"
                },
                "text",
                "kontakt@uninett.no"
              ]
            ]
          ]
        }
      ],
      "events": [
        {
          "eventAction": "registration",
          "eventDate": "2010-10-01T16:29:36Z"
        },
        {
          "eventAction": "last changed",
          "eventDate": "2022-06-28T07:00:53Z"
        }
      ],
      "handle": "NN172H-NORID",
      "ipAddresses": {
        "v4": [
          "158.38.0.181"
        ],
        "v6": [
          "2001:700:0:503::aa:5302"
        ]
      },
      "ldhName": "nn.uninett.no",
      "links": [
        {
          "href": "https://rdap.norid.no/nameserver_handle/NN172H-NORID",
          "rel": "self",
          "type": "application/rdap+json",
          "value": "https://rdap.norid.no/nameserver_handle/NN172H-NORID"
        }
      ],
      "objectClassName": "nameserver"
    },
    {
      "events": [
        {
          "eventAction": "registration",
          "eventDate": "2010-10-01T16:31:08Z"
        }
      ],
      "handle": "SERV111H-NORID",
      "ldhName": "server.nordu.net",
      "links": [
        {
          "href": "https://rdap.norid.no/nameserver_handle/SERV111H-NORID",
          "rel": "self",
          "type": "application/rdap+json",
          "value": "https://rdap.norid.no/nameserver_handle/SERV111H-NORID"
        }
      ],
      "objectClassName": "nameserver"
    }
  ],
  "notices": [
    {
      "description": [
        "By looking up information in the domain registration directory",
        "service, you confirm that you accept the terms and conditions",
        "of the service.",
        "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."
      ],
      "links": [
        {
          "href": "https://www.norid.no/en/domeneoppslag/vilkar",
          "rel": "alternate",
          "type": "text/html",
          "value": "https://rdap.norid.no/domain/uio.no"
        }
      ],
      "title": "Terms of use"
    }
  ],
  "objectClassName": "domain",
  "rdapConformance": [
    "rdap_level_0",
    "rdap_objectTag_level_0",
    "norid_level_0"
  ]
}

WHOIS

WHOIS is a TCP-based transaction-oriented query/response protocol that is widely used to provide information services to Internet users. While originally used to provide "white pages" services and information about registered domain names, current deployments cover a much broader range of information services.

Parsed Raw Data Model

Registrant	-
Lookup Time	18 Apr 2024 22:52 UTC
Source	whois.norid.no:43
Registrar
Registrar	SIKT - KUNNSKAPSSEKTORENS TJENESTELEVERANDØR
Events
Registration	15 Nov 1999 00:00 UTC
Update	15 Nov 2023 00:00 UTC
Expiration	-
Configuration
Statuses	-
Registrar Lock	-
Registry Lock	-
Nameservers	nn.uninett.no ns1.uio.no ns2.uio.no server.nordu.net
Contacts
Registrar	SIKT - KUNNSKAPSSEKTORENS TJENESTELEVERANDØR SIKT - KUNNSKAPSSEKTORENS TJENESTELEVERANDØR Postboks 5782 Torgarden; NO-7437 Trondheim; NO Email: kontakt@sikt.no Phone: +47.73557900
Technical	Email: hostmaster@usit.uio.no Phone: +47.22852470

{
  "meta": {
    "timestamp": "2024-04-18T22:52:56Z",
    "id": "48889eb6-f04e-42fe-8f6b-e0b4e5f4e977",
    "type": "HZ_REGISTRABLE_DOMAIN",
    "schemaVersion": "2022-02-02",
    "producer": "whois-rdap-clients/2022-03-23",
    "source": "NET",
    "status": "OK",
    "duration": "0.110s"
  },
  "name": "uio.no",
  "punyName": "uio.no",
  "source": "SOURCE_WHOIS",
  "sourceLocation": "whois.norid.no:43",
  "sourceRaw": "% By looking up information in the domain registration directory\n% service, you confirm that you accept the terms and conditions of the\n% service:\n% https://www.norid.no/en/domeneoppslag/vilkar/\n%\n% Norid AS holds the copyright to the lookup service, content,\n% layout and the underlying collections of information used in the\n% service (cf. the Act on Intellectual Property of May 2, 1961, No.\n% 2). Any commercial use of information from the service, including\n% targeted marketing, is prohibited. Using information from the domain\n% registration directory service in violation of the terms and\n% conditions may result in legal prosecution.\n%\n% The whois service at port 43 is intended to contribute to resolving\n% technical problems where individual domains threaten the\n% functionality, security and stability of other domains or the\n% internet as an infrastructure. It does not give any information\n% about who the holder of a domain is. To find information about a\n% domain holder, please visit our website:\n% https://www.norid.no/en/domeneoppslag/\n\nDomain Information\n\nNORID Handle...............: UIO16D-NORID\nDomain Name................: uio.no\nRegistrar Handle...........: REG1103-NORID\nTech-c Handle..............: UH2415R-NORID\nName Server Handle.........: NN172H-NORID\nName Server Handle.........: NSUI125H-NORID\nName Server Handle.........: NSUI126H-NORID\nName Server Handle.........: SERV111H-NORID\n\nAdditional information:\nCreated:         1999-11-15\nLast updated:    2023-11-15\n\n",
  "tld": "no",
  "suffix": "no",
  "createTime": "1999-11-15T00:00:00Z",
  "updateTime": "2023-11-15T00:00:00Z",
  "registrarName": "SIKT - KUNNSKAPSSEKTORENS TJENESTELEVERANDØR",
  "nameservers": [{
    "name": "nn.uninett.no",
    "punyName": "",
    "addresses": []
  }, {
    "name": "ns1.uio.no",
    "punyName": "",
    "addresses": []
  }, {
    "name": "ns2.uio.no",
    "punyName": "",
    "addresses": []
  }, {
    "name": "server.nordu.net",
    "punyName": "",
    "addresses": []
  }],
  "statuses": [],
  "sourceStatuses": [],
  "contacts": [{
    "type": "CONTACT_REGISTRAR",
    "id": "REG1103-NORID",
    "firstName": "SIKT - KUNNSKAPSSEKTORENS TJENESTELEVERANDØR",
    "organization": "SIKT - KUNNSKAPSSEKTORENS TJENESTELEVERANDØR",
    "street1": "Postboks 5782 Torgarden; NO-7437 Trondheim; NO",
    "email": "kontakt@sikt.no",
    "phone": "+47.73557900"
  }, {
    "type": "CONTACT_TECHNICAL",
    "id": "UH2415R-NORID",
    "email": "hostmaster@usit.uio.no",
    "phone": "+47.22852470"
  }]
}

% 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...............: UIO16D-NORID
Domain Name................: uio.no
Registrar Handle...........: REG1103-NORID
Tech-c Handle..............: UH2415R-NORID
Name Server Handle.........: NN172H-NORID
Name Server Handle.........: NSUI125H-NORID
Name Server Handle.........: NSUI126H-NORID
Name Server Handle.........: SERV111H-NORID

Additional information:
Created:         1999-11-15
Last updated:    2023-11-15

DNS Zone

The global DNS infrastructure is organized as a series of hierarchical DNS zones. The root zone hosts a number of global and country TLDs, which in turn host further zones that are delegated to their customers. Each organization that controls a zone can delegate parts of its namespace to other zones. In this test we perform detailed inspection of a DNS zone, but only if the host being tested matches the zone.

Test passed

Everything seems to be well configured. Well done.

Nameserver Names

Nameservers can be referred to by name and by address. In this section we show the names, which can appear in the NS records, the referrals from the parent zone, and the SOA record. In some situations, servers from the parent zone respond authoritatively, in which case we will include them in the list as well.

Nameserver	Operational	IPv4	IPv6	Sources
nn.uninett.no. 158.38.0.181 2001:700:0:503::aa:5302				REFERRAL NS
ns1.uio.no. PRIMARY 129.240.2.6 2001:700:100:2::6				REFERRAL NS SOA
ns2.uio.no. 129.240.2.42 2001:700:100:425::42				REFERRAL NS
server.nordu.net. 193.10.252.19 2001:948:4:2::19				REFERRAL NS

Nameserver Addresses

This section shows the configuration of all discovered nameservers by their IP address. To find all applicable nameservers, we inspect the parent zone nameservers for names and glue and then the tested zone nameservers for NS records. We then resolve all discovered names to IP addresses. Finally, we test each address individually.

Nameserver	Sources	Payload Size
129.240.2.42 ns2.uio.no. PTR: ns2.uio.no.	NAME, GLUE	1232
129.240.2.6 PRIMARY ns1.uio.no. PTR: ns1.uio.no.	NAME, GLUE	1232
158.38.0.181 nn.uninett.no. PTR: nn.uninett.no.	NAME, GLUE	1232
193.10.252.19 server.nordu.net. PTR: server.nordu.net.	NAME	1232
2001:700:0:503::aa:5302 nn.uninett.no. PTR: nn.uninett.no.	NAME, GLUE	1232
2001:700:100:2::6 PRIMARY ns1.uio.no. PTR: ns1.uio.no.	NAME, GLUE	1232
2001:700:100:425::42 ns2.uio.no. PTR: ns2.uio.no.	NAME, GLUE	1232
2001:948:4:2::19 server.nordu.net. PTR: server.nordu.net.	NAME	1232

Start of Authority (SOA) Record

Start of Authority (SOA) records contain administrative information pertaining to one DNS zone, especially the configuration that's used for zone transfers between the primary nameserver and the secondaries. Only one SOA record should exist, with all nameservers providing the same information.

The domain name of the primary nameserver for the zone. Also known as MNAME.Primary nameserver	ns1.uio.no.
Email address of the persons responsible for this zone. Also known as RNAME.Admin email	hostmaster.uio.no.
Zone serial or version number.Serial number	-1054549277
The length of time secondary nameservers should wait before querying the primary for changes.Refresh interval	10,800 seconds (about 3 hours)
The length of time secondary nameservers should wait before querying an unresponsive primary again.Retry interval	3,600 seconds (about 1 hour)
The length of time after which secondary nameservers should stop responding to queries for a zone, assuming no updates were obtained from the primary.Expire interval	1,814,400 seconds (about 21 days)
TTL for purposes of negative response caching. Negative cache TTL	43,200 seconds (about 12 hours)
Time To Live (TTL) indicates for how long a record remains valid. SOA record TTL	43,200 seconds (about 12 hours)

Analysis

No problems detected with the zone configuration

Excellent. This DNS zone is in a good working order. No problems detected.

Backing DNS Queries

Below are all DNS queries we submitted during the zone inspection.

	ID	Server	Transport	Question Name	Type	Status

DNS Records

Correctly functioning name servers are necessary to hold and distribute information that's necessary for your domain name to operate correctly. Examples include converting names to IP addresses, determining where email should go, and so on. More recently, the DNS is being used to communicate email and other security policies.

Test passed, but there are warnings

Some aspect of your site's configuration require your attention.

DNS Records

These are the results of individual DNS queries against your nameserver for common resource record types.

Name	TTL	Type	Data
uio.no.	43200	A	129.240.118.130
www.uio.no.	43200	A	129.240.118.130
uio.no.	43200	AAAA	2001:700:100:118:0:0:0:130
www.uio.no.	43200	AAAA	2001:700:100:118:0:0:0:130
uio.no.	43200	CAA	0 iodef "mailto:cert@uio.no"
uio.no.	43200	CAA	0 issue "sectigo.com"
uio.no.	43200	CAA	0 issuewild "sectigo.com"
uio.no.	43200	MX	50 smtp.uio.no.
uio.no.	43200	NS	ns1.uio.no.
uio.no.	43200	NS	server.nordu.net.
uio.no.	43200	NS	nn.uninett.no.
uio.no.	43200	NS	ns2.uio.no.
uio.no.	43200	SOA	ns1.uio.no. hostmaster.uio.no. 3240418019 10800 3600 1814400 43200
_sip._tls.uio.no.	43200	SRV	100 1 443 sipdir.online.lync.com.
_sipfederationtls._tcp.uio.no.	43200	SRV	100 1 5061 sipfed.online.lync.com.
uio.no.	43200	TXT	"google-site-verification=YnB-rpdnKO3Nu0Pca31WNRW0f3B_ZMMfWVG7C8__eUw"
uio.no.	43200	TXT	"google-site-verification=T_O8tqZhYYOTcgWMdJTU_uz-FzAF5CCesip9GSMxDCw"
uio.no.	43200	TXT	"v=spf1 mx include:spf.uio.no include:_spf.google.com include:spf.protection.outlook.com -all"
uio.no.	43200	TXT	"google-site-verification=zX3VnlZeZs0LSs86a_UdKaZFrfjrNqYITG8HDhcdk2I"
uio.no.	43200	TXT	"dropbox-domain-verification=eovcv1nrw2n5"
uio.no.	43200	TXT	"apple-domain-verification=hBIkEpfAYcNs7R31"
uio.no.	43200	TXT	"University of Oslo, Norway"

Analysis

Dangling DNS configuration

We've detected a dangling DNS configuration that doesn't look serious. This problem most commonly occurs with CNAME records that point to another name that is subsequently deleted.

Error: Dangling DNS record: _sip._tls.uio.no./SRV (destination: sipdir.online.lync.com.)

Backing DNS Queries

Below are all DNS queries we submitted while inspecting the resource records.

	ID	Server	Question Name	Type	Status

DNSSEC

DNSSEC is an extension of the DNS protocol that provides cryptographic assurance of the authenticity and integrity of responses; it's intended as a defense against network attackers who are able to manipulate DNS to redirect their victims to servers of their choice. DNSSEC is controversial, with the industry split largely between those who think it's essential and those who believe that it's problematic and unnecessary.

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

Useful DNSSEC Tools

Certification Authority Authorization

CAA (RFC 8659) is a new standard that allows domain name owners to restrict which CAs are allowed to issue certificates for their domains. This can help to reduce the chance of misissuance, either accidentally or maliciously. In September 2017, CAA became mandatory for CAs to implement.

Test passed

Everything seems to be well configured. Well done.

CAA Policy Information

The DNS hostname where this policy is located.Policy host	uio.no
The iodef property specifies a means of reporting certificate issue requests or cases of certificate issue for the corresponding domain that violate the security policy of the issuer or the domain name holder.iodef	mailto:cert@uio.no flags: 0
The issuewild property has the same syntax and semantics as the issue property except that issuewild properties only grant authorization to issue certificates that specify a wildcard domain and issuewild properties take precedence over issue properties when specified.issuewild	sectigo.com flags: 0
The issue property tag is used to request that certificate issuers perform CAA issue restriction processing for the domain and to grant authorization to specific certificate issuers.issue	sectigo.com flags: 0

Analysis

CAA policy found

Good. This domain name uses CAA to restrict which CAs are allowed to issue certificates for it.

Policy uses reporting

Great. This policy uses reporting, which means that your contact information is available should someone need to contact you about a CAA violation. Do note that you're not guaranteed to be notified, given that CAs generally don't support notifications yet.

Email (SMTP)

An internet hostname can be served by zero or more mail servers, as specified by MX (mail exchange) DNS resource records. Each server can further resolve to multiple IP addresses, for example to handle IPv4 and IPv6 clients. Thus, in practice, hosts that wish to receive email reliably are supported by many endpoint.

Test passed

Everything seems to be well configured. Well done.

Some TLS and PKI information shown may have been retrieved from cache. The notes provide more information.

Server

Preference

Operational

STARTTLS

TLS

PKI

DNSSEC

DANE

smtp.uio.no
129.240.2.125
PTR: smtp.uio.no

50

Analysis

Some SMTP server assessments have been retrieved from cache

Some SMTP server assessment results have been retrieved from our cache. Because many hosts point to the same SMTP servers, we use a short-term cache to avoid testing the same SMTP servers over and over again.

Cache timestamp: 12 Apr 2024 10:43 UTC

Some SMTP server assessments contain partial information

Comprehensive TLS assessments require many connections, which is exactly what many SMTP servers don't like. We implement a two-tier assessment approach. To give you some results as fast as possible, we perform shallow assessments that use only one connection per SMTP server. We then have a background process that performs complete assessments slowly, trying to accommodate each server individually. The results presented here contain partial information. If you come back later we may be able to provide complete assessment resuls.

Email TLS (SMTP)

Transport Layer Security (TLS) is the most widely used encryption protocol on the Internet. In combination with valid certificates, servers can establish trusted communication channels even with users who have never visited them before. Network attackers can't uncover what is being communicated, even when they can see all the traffic.

Test passed

Everything seems to be well configured. Well done.

Some TLS and PKI information shown may have been retrieved from cache. The notes provide more information.

TLS Configuration: smtp.uio.no (129.240.2.125) Cached

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.2
Shows cipher suite configuration for this protocol version.TLS v1.2	Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 Suite ID: 0xc023 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC secp256r1 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 128 bits (ECDHE 256 bits)
These results have been retrieved from our cache. This row indicates when was that the original test ran.Retrieved from cache	12 Apr 2024 10:43 UTC

Analysis

TLS 1.2 supported

Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.

Strong key exchange detected

Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.

Partial results shown

SMTP assessments usually take a long time. To get you some results faster, we initially perform shallow checks. If you come back later we may be able to show you complete results.

Relaxed TLS assessment criteria applied to SMTP on port 25

We apply relaxed assessment criteria when evaluating TLS configuration of SMTP servers on port 25. This is because most delivery agents fall back to delivering via plaintext on failure to negotiate encryption. Some configuration elements that can be abused to attack other ports and protocols (e.g., SSLv2 and export cipher suites) are penalized in the same way as for other protocols. We will review this policy in the future.

Email Certificates (SMTP)

A certificate is a digital document that contains a public key, some information about the entity associated with it, and a digital signature from the certificate issuer. It’s a mechanism that enables us to exchange, store, and use public keys. Being able to reliably verify the identity of a remote server is crucial in order to achieve secure encrypted communication.

Test passed

Everything seems to be well configured. Well done.

Some TLS and PKI information shown may have been retrieved from cache. The notes provide more information.

Certificate #1 Cached

Leaf certificate

smtp.uio.no
Issuer: Sectigo
Not Before: 11 Oct 2023 00:00:00 UTC
Not After: 10 Oct 2024 23:59:59 UTC (expires in 5 months 22 days)
Key: EC 256 bits
Signature: SHA256withECDSA
View details

Names	smtp.uio.no mail-mx01.uio.no mail-mx02.uio.no mail-mx03.uio.no mail-mx04.uio.no mail-mx05.uio.no mail-mx06.uio.no mail-mx07.uio.no mail-mx08.uio.no mail-mx09.uio.no mail-mx10.uio.no mail-mx11.uio.no mail-mx12.uio.no mail-mx13.uio.no mail-mx14.uio.no
Subject DN	CN=smtp.uio.no, O=Universitetet i Oslo, ST=Oslo, C=NO
Subject Key Identifier	29aea0ef642de897ef116b19fce10465a096dc19
Serial	c80b0f7cf10d2e91055e4168f4456367
Not Before	11 Oct 2023 00:00:00 UTC
Not After	10 Oct 2024 23:59:59 UTC
Validity period	366 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=GEANT OV ECC CA 4, O=GEANT Vereniging, C=NL
Certification Authority	Sectigo
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:edb4a0336a1b0891b6bdfa4192bd9aabab63f453
Parent Certificate	http://GEANT.crt.sectigo.com/GEANTOVECCCA4.crt
CRL	http://GEANT.crl.sectigo.com/GEANTOVECCCA4.crl
OCSP	http://GEANT.ocsp.sectigo.com
Certificate Transparency
Signed Certificate Timestamps	11 Oct 2023 09:04:35 UTC \| Google 'Xenon2024' log \| Qualified 11 Oct 2023 09:04:35 UTC \| Cloudflare 'Nimbus2024' Log \| Qualified 11 Oct 2023 09:04:35 UTC \| Google 'Argon2024' log \| Qualified
Fingerprints
SHA1	ba477a4cc0b2ac987bd653639ed02e466ba8fcd7
SHA256	cf62b3a163f87cea227e853aa54cb461883ea94bacbc22638f50f583ba9cf820
SPKI SHA256	2a5e59f03aa630e9cd84d92deca0fa4b2a47024a1fdc70445d0022ff3dfe70e8

Analysis

Strong private key

Good. The private key associated with this certificate is secure.

Strong signature algorithm

Good. This certificate uses a strong signature algorithm.

Certificate matches hostname

Good. The provided certificate matches the expected hostnames.

Certificate dates match

Good. The certificate is valid for use at this point of time.

Certificate has not been revoked

Good. This certificate has not been revoked.

Certificate satisfies Apple's CT compliance requirements

Good. This certificate satisfies Apple's CT requirements at present.

Certificate Chain

Leaf certificate

smtp.uio.no | cf62b3a
Not After: 10 Oct 2024 23:59:59 UTC (expires in 5 months 22 days)
Authentication: EC 256 bits (SHA256withECDSA)
View details

Names	smtp.uio.no mail-mx01.uio.no mail-mx02.uio.no mail-mx03.uio.no mail-mx04.uio.no mail-mx05.uio.no mail-mx06.uio.no mail-mx07.uio.no mail-mx08.uio.no mail-mx09.uio.no mail-mx10.uio.no mail-mx11.uio.no mail-mx12.uio.no mail-mx13.uio.no mail-mx14.uio.no
Subject DN	CN=smtp.uio.no, O=Universitetet i Oslo, ST=Oslo, C=NO
Subject Key Identifier	29aea0ef642de897ef116b19fce10465a096dc19
Serial	c80b0f7cf10d2e91055e4168f4456367
Not Before	11 Oct 2023 00:00:00 UTC
Not After	10 Oct 2024 23:59:59 UTC
Validity period	366 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=GEANT OV ECC CA 4, O=GEANT Vereniging, C=NL
Certification Authority	Sectigo
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:edb4a0336a1b0891b6bdfa4192bd9aabab63f453
Parent Certificate	http://GEANT.crt.sectigo.com/GEANTOVECCCA4.crt
CRL	http://GEANT.crl.sectigo.com/GEANTOVECCCA4.crl
OCSP	http://GEANT.ocsp.sectigo.com
Certificate Transparency
Signed Certificate Timestamps	11 Oct 2023 09:04:35 UTC \| Google 'Xenon2024' log \| Qualified 11 Oct 2023 09:04:35 UTC \| Cloudflare 'Nimbus2024' Log \| Qualified 11 Oct 2023 09:04:35 UTC \| Google 'Argon2024' log \| Qualified
Fingerprints
SHA1	ba477a4cc0b2ac987bd653639ed02e466ba8fcd7
SHA256	cf62b3a163f87cea227e853aa54cb461883ea94bacbc22638f50f583ba9cf820
SPKI SHA256	2a5e59f03aa630e9cd84d92deca0fa4b2a47024a1fdc70445d0022ff3dfe70e8

Intermediate certificate

GEANT OV ECC CA 4 | 083799e
Not After: 01 May 2033 23:59:59 UTC (expires in 9 years 13 days)
Authentication: EC 256 bits (SHA384withECDSA)
View details

Subject DN	CN=GEANT OV ECC CA 4, O=GEANT Vereniging, C=NL
Subject Key Identifier	edb4a0336a1b0891b6bdfa4192bd9aabab63f453
Serial	eb8e81197129f4af64ef814a2f50cee9
Not Before	18 Feb 2020 00:00:00 UTC
Not After	01 May 2033 23:59:59 UTC
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	serverAuth, clientAuth
Issuer
Issuer DN	CN=USERTrust ECC Certification Authority, O=The USERTRUST Network, L=Jersey City, ST=New Jersey, C=US
Certification Authority	Sectigo
Validation Type	Not Applicable
Authority Key Identifier	keyid:3ae10986d4cf19c29676744976dce035c663639a
Parent Certificate	http://crt.usertrust.com/USERTrustECCAddTrustCA.crt
CRL	http://crl.usertrust.com/USERTrustECCCertificationAuthority.crl
OCSP	http://ocsp.usertrust.com
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	8a63c019620165b85120c8deb3362d0795020486
SHA256	083799e8b2b9016e44702ebf9bf369ce253fe1fbeb650e5df10ef44d87bf3bae
SPKI SHA256	9cc638bee15581f92658138371bf9348686ce2c8af7a0765b8660f19d99cf9a7

Root certificate

USERTrust ECC Certification Authority | 4ff460d
Not After: 18 Jan 2038 23:59:59 UTC (expires in 13 years 9 months)
Authentication: EC 384 bits (SHA384withECDSA)
View details

Subject DN	CN=USERTrust ECC Certification Authority, O=The USERTRUST Network, L=Jersey City, ST=New Jersey, C=US
Subject Key Identifier	3ae10986d4cf19c29676744976dce035c663639a
Serial	5c8b99c55a94c5d27156decd8980cc26
Not Before	01 Feb 2010 00:00:00 UTC
Not After	18 Jan 2038 23:59:59 UTC
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=USERTrust ECC Certification Authority, O=The USERTRUST Network, L=Jersey City, ST=New Jersey, C=US
Certification Authority	Sectigo
Validation Type	Self-signed
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	d1cbca5db2d52a7f693b674de5f05a1d0c957df0
SHA256	4ff460d54b9c86dabfbcfc5712e0400d2bed3fbc4d4fbdaa86e06adcd2a9ad7a
SPKI SHA256	2021917e98263945c859c43f1d73cb4139053c414fa03ca3bc7ee88614298f3b

Analysis

Certificate chain is correct

Good. This chain contains all the right certificates and in the right order.

Certificate #2 Cached

Leaf certificate

smtp.uio.no
Issuer: Sectigo
Not Before: 11 Oct 2023 00:00:00 UTC
Not After: 10 Oct 2024 23:59:59 UTC (expires in 5 months 22 days)
Key: RSA 2048 bits
Signature: SHA384withRSA
View details

Names	smtp.uio.no mail-mx01.uio.no mail-mx02.uio.no mail-mx03.uio.no mail-mx04.uio.no mail-mx05.uio.no mail-mx06.uio.no mail-mx07.uio.no mail-mx08.uio.no mail-mx09.uio.no mail-mx10.uio.no mail-mx11.uio.no mail-mx12.uio.no mail-mx13.uio.no mail-mx14.uio.no
Subject DN	CN=smtp.uio.no, O=Universitetet i Oslo, ST=Oslo, C=NO
Subject Key Identifier	4d95a65e3bdfd796cec98c06a065049f1d98ed4e
Serial	8ad70438100bcec63842077cfbd54acb
Not Before	11 Oct 2023 00:00:00 UTC
Not After	10 Oct 2024 23:59:59 UTC
Validity period	366 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=GEANT OV RSA CA 4, O=GEANT Vereniging, C=NL
Certification Authority	Sectigo
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:6f1d3549106c32fa59a09ebc8ae81f95be717a0c
Parent Certificate	http://GEANT.crt.sectigo.com/GEANTOVRSACA4.crt
CRL	http://GEANT.crl.sectigo.com/GEANTOVRSACA4.crl
OCSP	http://GEANT.ocsp.sectigo.com
Certificate Transparency
Signed Certificate Timestamps	11 Oct 2023 09:04:41 UTC \| Google 'Xenon2024' log \| Qualified 11 Oct 2023 09:04:41 UTC \| Cloudflare 'Nimbus2024' Log \| Qualified 11 Oct 2023 09:04:41 UTC \| Google 'Argon2024' log \| Qualified
Fingerprints
SHA1	09a1e4d9d2e523a4c7b4c530590c5ea985d55e92
SHA256	987823d0d120b7b02f5de9f9f4c7499f67c5fc1d348754076a000dd487de763f
SPKI SHA256	fd3acda652cfd6928912de12dffdc9fbf13e4c934ab5065a626db77ded6b9b51

Analysis

Strong private key

Good. The private key associated with this certificate is secure.

Strong signature algorithm

Good. This certificate uses a strong signature algorithm.

Certificate matches hostname

Good. The provided certificate matches the expected hostnames.

Certificate dates match

Good. The certificate is valid for use at this point of time.

Certificate has not been revoked

Good. This certificate has not been revoked.

Certificate satisfies Apple's CT compliance requirements

Good. This certificate satisfies Apple's CT requirements at present.

Certificate Chain

Leaf certificate

smtp.uio.no | 987823d
Not After: 10 Oct 2024 23:59:59 UTC (expires in 5 months 22 days)
Authentication: RSA 2048 bits (SHA384withRSA)
View details

Names	smtp.uio.no mail-mx01.uio.no mail-mx02.uio.no mail-mx03.uio.no mail-mx04.uio.no mail-mx05.uio.no mail-mx06.uio.no mail-mx07.uio.no mail-mx08.uio.no mail-mx09.uio.no mail-mx10.uio.no mail-mx11.uio.no mail-mx12.uio.no mail-mx13.uio.no mail-mx14.uio.no
Subject DN	CN=smtp.uio.no, O=Universitetet i Oslo, ST=Oslo, C=NO
Subject Key Identifier	4d95a65e3bdfd796cec98c06a065049f1d98ed4e
Serial	8ad70438100bcec63842077cfbd54acb
Not Before	11 Oct 2023 00:00:00 UTC
Not After	10 Oct 2024 23:59:59 UTC
Validity period	366 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=GEANT OV RSA CA 4, O=GEANT Vereniging, C=NL
Certification Authority	Sectigo
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:6f1d3549106c32fa59a09ebc8ae81f95be717a0c
Parent Certificate	http://GEANT.crt.sectigo.com/GEANTOVRSACA4.crt
CRL	http://GEANT.crl.sectigo.com/GEANTOVRSACA4.crl
OCSP	http://GEANT.ocsp.sectigo.com
Certificate Transparency
Signed Certificate Timestamps	11 Oct 2023 09:04:41 UTC \| Google 'Xenon2024' log \| Qualified 11 Oct 2023 09:04:41 UTC \| Cloudflare 'Nimbus2024' Log \| Qualified 11 Oct 2023 09:04:41 UTC \| Google 'Argon2024' log \| Qualified
Fingerprints
SHA1	09a1e4d9d2e523a4c7b4c530590c5ea985d55e92
SHA256	987823d0d120b7b02f5de9f9f4c7499f67c5fc1d348754076a000dd487de763f
SPKI SHA256	fd3acda652cfd6928912de12dffdc9fbf13e4c934ab5065a626db77ded6b9b51

Intermediate certificate

GEANT OV RSA CA 4 | 37834fa
Not After: 01 May 2033 23:59:59 UTC (expires in 9 years 13 days)
Authentication: RSA 4096 bits (SHA384withRSA)
View details

Subject DN	CN=GEANT OV RSA CA 4, O=GEANT Vereniging, C=NL
Subject Key Identifier	6f1d3549106c32fa59a09ebc8ae81f95be717a0c
Serial	da43bd139bd258bb4dd61cacc4f3dbe0
Not Before	18 Feb 2020 00:00:00 UTC
Not After	01 May 2033 23:59:59 UTC
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	serverAuth, clientAuth
Issuer
Issuer DN	CN=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, ST=New Jersey, C=US
Certification Authority	Sectigo
Validation Type	Not Applicable
Authority Key Identifier	keyid:5379bf5aaa2b4acf5480e1d89bc09df2b20366cb
Parent Certificate	http://crt.usertrust.com/USERTrustRSAAddTrustCA.crt
CRL	http://crl.usertrust.com/USERTrustRSACertificationAuthority.crl
OCSP	http://ocsp.usertrust.com
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	c2826e266d7405d34ef89762636ae4b36e86cb5e
SHA256	37834fa5ea40fbf7b61196955962e1ca0558872435e4206653d3f620dd8e988e
SPKI SHA256	8f4a912bd4b4a146daf5be2db5974aa78d90e13d89f12e0514a3cd1b91531550

Root certificate

USERTrust RSA Certification Authority | e793c9b
Not After: 18 Jan 2038 23:59:59 UTC (expires in 13 years 9 months)
Authentication: RSA 4096 bits (SHA384withRSA)
View details

Subject DN	CN=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, ST=New Jersey, C=US
Subject Key Identifier	5379bf5aaa2b4acf5480e1d89bc09df2b20366cb
Serial	1fd6d30fca3ca51a81bbc640e35032d
Not Before	01 Feb 2010 00:00:00 UTC
Not After	18 Jan 2038 23:59:59 UTC
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, ST=New Jersey, C=US
Certification Authority	Sectigo
Validation Type	Self-signed
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	2b8f1b57330dbba2d07a6c51f70ee90ddab9ad8e
SHA256	e793c9b02fd8aa13e21c31228accb08119643b749c898964b1746d46c3d4cbd2
SPKI SHA256	c784333d20bcd742b9fdc3236f4e509b8937070e73067e254dd3bf9c45bf4dde

Analysis

Certificate chain is correct

Good. This chain contains all the right certificates and in the right order.

Email DANE (SMTP)

DNS-based Authentication of Named Entities (DANE) is a bridge between DNSSEC and TLS. In one possible scenario, DANE can be used for public key pinning, building on an existing publicly-trusted certificate. In another approach, it can be used to completely bypass the CA ecosystem and establish trust using DNSSEC alone.

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

SPF

Sender Policy Framework (SPF) is a protocol that allows domain name owners to control which internet hosts are allowed to send email on their behalf. This simple mechanism can be used to reduce the effect of email spoofing and cut down on spam.

Test passed

Everything seems to be well configured. Well done.

SPF Policy Information Main policy

Host where this policy is located.Location	uio.no
SPF version used by this policy.v	spf1
This mechanism matches if the sending IP address is one of the MX hosts for the domain name. mx
Evaluates SPF policy specified in another DNS location. This directive is typically used to allow hosts controlled by another organization. include	spf.uio.no
Evaluates SPF policy specified in another DNS location. This directive is typically used to allow hosts controlled by another organization. include	_spf.google.com
Evaluates SPF policy specified in another DNS location. This directive is typically used to allow hosts controlled by another organization. include	spf.protection.outlook.com
This policy element always matches. It's normally used at the end of a policy to specify the handling of hosts that don't match earlier mechanisms. -all

Analysis

SPF policy found

Policy text: v=spf1 mx include:spf.uio.no include:_spf.google.com include:spf.protection.outlook.com -all

Location: uio.no

SPF policy is valid

Good. Your SPF policy is syntactically valid.

Policy uses default fail

Excellent. This policy fails hosts that are not allowed to send email for this domain name.

Policy DNS lookups under limit

Good. Your policy stays under the limit of up to 10 DNS queries. The SPF specification Section 4.6.4. requires implementations to limit the total number of DNS queries. Policies that exceed the limit should not be used and may not work in practice.

Lookups: 8

SPF Policy Information Included policy

Host where this policy is located.Location	spf.uio.no
SPF version used by this policy.v	spf1
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	129.240.10.0/25
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2001:700:100:10::/64
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2001:700:100:8210::/64
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	129.240.1.0/26
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2001:700:100:8211::/64
Evaluates SPF policy specified in another DNS location. This directive is typically used to allow hosts controlled by another organization. include	spf.protection.outlook.com
This policy element always matches. It's normally used at the end of a policy to specify the handling of hosts that don't match earlier mechanisms. ?all

SPF Policy Information Included policy

Host where this policy is located.Location	spf.protection.outlook.com
SPF version used by this policy.v	spf1
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	40.92.0.0/15
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	40.107.0.0/16
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	52.100.0.0/14
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	104.47.0.0/17
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2a01:111:f400::/48
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2a01:111:f403::/49
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2a01:111:f403:8000::/51
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2a01:111:f403:c000::/51
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2a01:111:f403:f000::/52
This policy element always matches. It's normally used at the end of a policy to specify the handling of hosts that don't match earlier mechanisms. -all

SPF Policy Information Included policy

Host where this policy is located.Location	_spf.google.com
SPF version used by this policy.v	spf1
Evaluates SPF policy specified in another DNS location. This directive is typically used to allow hosts controlled by another organization. include	_netblocks.google.com
Evaluates SPF policy specified in another DNS location. This directive is typically used to allow hosts controlled by another organization. include	_netblocks2.google.com
Evaluates SPF policy specified in another DNS location. This directive is typically used to allow hosts controlled by another organization. include	_netblocks3.google.com
This policy element always matches. It's normally used at the end of a policy to specify the handling of hosts that don't match earlier mechanisms. ~all

SPF Policy Information Included policy

Host where this policy is located.Location	_netblocks.google.com
SPF version used by this policy.v	spf1
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	35.190.247.0/24
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	64.233.160.0/19
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	66.102.0.0/20
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	66.249.80.0/20
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	72.14.192.0/18
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	74.125.0.0/16
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	108.177.8.0/21
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	173.194.0.0/16
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	209.85.128.0/17
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	216.58.192.0/19
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	216.239.32.0/19
This policy element always matches. It's normally used at the end of a policy to specify the handling of hosts that don't match earlier mechanisms. ~all

SPF Policy Information Included policy

Host where this policy is located.Location	_netblocks2.google.com
SPF version used by this policy.v	spf1
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2001:4860:4000::/36
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2404:6800:4000::/36
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2607:f8b0:4000::/36
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2800:3f0:4000::/36
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2a00:1450:4000::/36
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2c0f:fb50:4000::/36
This policy element always matches. It's normally used at the end of a policy to specify the handling of hosts that don't match earlier mechanisms. ~all

SPF Policy Information Included policy

Host where this policy is located.Location	_netblocks3.google.com
SPF version used by this policy.v	spf1
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	172.217.0.0/19
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	172.217.32.0/20
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	172.217.128.0/19
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	172.217.160.0/20
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	172.217.192.0/19
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	172.253.56.0/21
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	172.253.112.0/20
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	108.177.96.0/19
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	35.191.0.0/16
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	130.211.0.0/22
This policy element always matches. It's normally used at the end of a policy to specify the handling of hosts that don't match earlier mechanisms. ~all

SPF Policy Information Included policy

Host where this policy is located.Location	spf.protection.outlook.com
SPF version used by this policy.v	spf1
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	40.92.0.0/15
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	40.107.0.0/16
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	52.100.0.0/14
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	104.47.0.0/17
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2a01:111:f400::/48
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2a01:111:f403::/49
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2a01:111:f403:8000::/51
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2a01:111:f403:c000::/51
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2a01:111:f403:f000::/52
This policy element always matches. It's normally used at the end of a policy to specify the handling of hosts that don't match earlier mechanisms. -all

DMARC

Domain-based Message Authentication, Reporting, and Conformance (DMARC) is a scalable mechanism by which a mail-originating organization can express domain-level policies and preferences for message validation, disposition, and reporting, that a mail-receiving organization can use to improve mail handling.

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

MTA Strict Transport Security

SMTP Mail Transfer Agent Strict Transport Security (MTA-STS) is a mechanism enabling mail service providers to declare their ability to receive Transport Layer Security (TLS) secure SMTP connections, and to specify whether sending SMTP servers should refuse to deliver to MX hosts that do not offer TLS with a trusted server certificate.

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

SMTP TLS Reporting

SMTP TLS Reporting (RFC 8460), or TLS-RPT for short, describes a reporting mechanism and format by which systems sending email can share statistics and specific information about potential failures with recipient domains. Recipient domains can then use this information to both detect potential attacks and diagnose unintentional misconfigurations. TLS-RPT can be used with DANE or MTA-STS.

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

HTTP (80)

To observe your HTTP implementation, we submit a request to the homepage of your site on port 80, follow all redirections (even when they take us to other domain names), and record the returned HTTP headers.

Test passed

Everything seems to be well configured. Well done.

URL: http://uio.no/

1

http://uio.no/

HTTP/1.1 301 Moved Permanently

content-length	0
location	https://uio.no/
cache-control	max-age=86400, stale-while-revalidate=21600, stale-if-error=31536000
strict-transport-security	max-age=63072000

2

https://uio.no/

HTTP/1.1 301 Moved Permanently

server	nginx
date	Thu, 18 Apr 2024 22:52:57 GMT
content-type	text/html; charset=utf-8
location	https://www.uio.no/
x-cacheable	NO:Varnish
vary	Accept-Encoding
age	0
via	1.1 varnish (Varnish
cache-control	max-age=86400, stale-while-revalidate=21600, stale-if-error=31536000
strict-transport-security	max-age=63072000

3

https://www.uio.no/

HTTP/1.1 200 OK

server	nginx
date	Thu, 18 Apr 2024 22:49:06 GMT
content-type	text/html;charset=utf-8
strict-transport-security	max-age=31536000
content-security-policy	frame-ancestors *; upgrade-insecure-requests; object-src 'none'
permissions-policy	fullscreen=(self "https://.uio.no" "https://uio.cloud.panopto.eu"), picture-in-picture=(self "https://.uio.no" "https://uio.cloud.panopto.eu"), interest-cohort=(), browsing-topics=(), join-ad-interest-group=(), run-ad-auction=(), accelerometer=(), ambient-light-sensor=(), autoplay=(), battery=(), camera=(), display-capture=(), encrypted-media=(), gamepad=(), geolocation=(), gyroscope=(), layout-animations=(self), legacy-image-formats=(), magnetometer=(), microphone=(), midi=(), oversized-images=(self), payment=(), publickey-credentials-get=(), speaker-selection=(), sync-xhr=(self), unoptimized-images=(self), unsized-media=(self), usb=(), screen-wake-lock=(), web-share=(), xr-spatial-tracking=(), clipboard-read=(), clipboard-write=(), hid=(), serial=(), cross-origin-isolated=(), execution-while-not-rendered=(self), execution-while-out-of-viewport=(self), keyboard-map=(), navigation-override=()
cache-control	max-age=300
x-cacheable	YES
vary	Cookie, Origin, Accept-Encoding
age	231
via	1.1 varnish (Varnish
accept-ranges	bytes
x-content-type-options	nosniff
x-permitted-cross-domain-policies	none
x-xss-protection	0
x-frame-options	SAMEORIGIN
referrer-policy	strict-origin-when-cross-origin

Analysis

HTTP redirects to HTTPS

Good. This plaintext HTTP server redirects to HTTPS.

URL: http://www.uio.no/

1

http://www.uio.no/

HTTP/1.1 301 Moved Permanently

content-length	0
location	https://www.uio.no/
cache-control	max-age=86400, stale-while-revalidate=21600, stale-if-error=31536000
strict-transport-security	max-age=63072000

2

https://www.uio.no/

HTTP/1.1 200 OK

server	nginx
date	Thu, 18 Apr 2024 22:50:36 GMT
content-type	text/html;charset=utf-8
strict-transport-security	max-age=31536000
content-security-policy	frame-ancestors *; upgrade-insecure-requests; object-src 'none'
permissions-policy	fullscreen=(self "https://.uio.no" "https://uio.cloud.panopto.eu"), picture-in-picture=(self "https://.uio.no" "https://uio.cloud.panopto.eu"), interest-cohort=(), browsing-topics=(), join-ad-interest-group=(), run-ad-auction=(), accelerometer=(), ambient-light-sensor=(), autoplay=(), battery=(), camera=(), display-capture=(), encrypted-media=(), gamepad=(), geolocation=(), gyroscope=(), layout-animations=(self), legacy-image-formats=(), magnetometer=(), microphone=(), midi=(), oversized-images=(self), payment=(), publickey-credentials-get=(), speaker-selection=(), sync-xhr=(self), unoptimized-images=(self), unsized-media=(self), usb=(), screen-wake-lock=(), web-share=(), xr-spatial-tracking=(), clipboard-read=(), clipboard-write=(), hid=(), serial=(), cross-origin-isolated=(), execution-while-not-rendered=(self), execution-while-out-of-viewport=(self), keyboard-map=(), navigation-override=()
cache-control	max-age=300
x-cacheable	YES
vary	Cookie, Origin, Accept-Encoding
age	141
via	1.1 varnish (Varnish
accept-ranges	bytes
x-content-type-options	nosniff
x-permitted-cross-domain-policies	none
x-xss-protection	0
x-frame-options	SAMEORIGIN
referrer-policy	strict-origin-when-cross-origin

Analysis

HTTP redirects to HTTPS

Good. This plaintext HTTP server redirects to HTTPS.

HTTP (443)

To observe your HTTPS implementation, we submit a request to the homepage of your site on port 443, follow all redirections (even when they take us to other domain names), and record the returned HTTP headers. We use the most recent set of headers returned from the tested hostname for further tests such as HSTS and HPKP.

Test passed

Everything seems to be well configured. Well done.

URL: https://uio.no/

1

https://uio.no/

HTTP/1.1 301 Moved Permanently

server	nginx
date	Thu, 18 Apr 2024 22:52:59 GMT
content-type	text/html; charset=utf-8
location	https://www.uio.no/
x-cacheable	NO:Varnish
vary	Accept-Encoding
age	0
via	1.1 varnish (Varnish
cache-control	max-age=86400, stale-while-revalidate=21600, stale-if-error=31536000
strict-transport-security	max-age=63072000

2

https://www.uio.no/

HTTP/1.1 200 OK

server	nginx
date	Thu, 18 Apr 2024 22:49:06 GMT
content-type	text/html;charset=utf-8
strict-transport-security	max-age=31536000
content-security-policy	frame-ancestors *; upgrade-insecure-requests; object-src 'none'
permissions-policy	fullscreen=(self "https://.uio.no" "https://uio.cloud.panopto.eu"), picture-in-picture=(self "https://.uio.no" "https://uio.cloud.panopto.eu"), interest-cohort=(), browsing-topics=(), join-ad-interest-group=(), run-ad-auction=(), accelerometer=(), ambient-light-sensor=(), autoplay=(), battery=(), camera=(), display-capture=(), encrypted-media=(), gamepad=(), geolocation=(), gyroscope=(), layout-animations=(self), legacy-image-formats=(), magnetometer=(), microphone=(), midi=(), oversized-images=(self), payment=(), publickey-credentials-get=(), speaker-selection=(), sync-xhr=(self), unoptimized-images=(self), unsized-media=(self), usb=(), screen-wake-lock=(), web-share=(), xr-spatial-tracking=(), clipboard-read=(), clipboard-write=(), hid=(), serial=(), cross-origin-isolated=(), execution-while-not-rendered=(self), execution-while-out-of-viewport=(self), keyboard-map=(), navigation-override=()
cache-control	max-age=300
x-cacheable	YES
vary	Cookie, Origin, Accept-Encoding
age	234
via	1.1 varnish (Varnish
accept-ranges	bytes
x-content-type-options	nosniff
x-permitted-cross-domain-policies	none
x-xss-protection	0
x-frame-options	SAMEORIGIN
referrer-policy	strict-origin-when-cross-origin

URL: https://www.uio.no/

1

https://www.uio.no/

HTTP/1.1 200 OK

server	nginx
date	Thu, 18 Apr 2024 22:50:36 GMT
content-type	text/html;charset=utf-8
strict-transport-security	max-age=31536000
content-security-policy	frame-ancestors *; upgrade-insecure-requests; object-src 'none'
permissions-policy	fullscreen=(self "https://.uio.no" "https://uio.cloud.panopto.eu"), picture-in-picture=(self "https://.uio.no" "https://uio.cloud.panopto.eu"), interest-cohort=(), browsing-topics=(), join-ad-interest-group=(), run-ad-auction=(), accelerometer=(), ambient-light-sensor=(), autoplay=(), battery=(), camera=(), display-capture=(), encrypted-media=(), gamepad=(), geolocation=(), gyroscope=(), layout-animations=(self), legacy-image-formats=(), magnetometer=(), microphone=(), midi=(), oversized-images=(self), payment=(), publickey-credentials-get=(), speaker-selection=(), sync-xhr=(self), unoptimized-images=(self), unsized-media=(self), usb=(), screen-wake-lock=(), web-share=(), xr-spatial-tracking=(), clipboard-read=(), clipboard-write=(), hid=(), serial=(), cross-origin-isolated=(), execution-while-not-rendered=(self), execution-while-out-of-viewport=(self), keyboard-map=(), navigation-override=()
cache-control	max-age=300
x-cacheable	YES
vary	Cookie, Origin, Accept-Encoding
age	144
via	1.1 varnish (Varnish
accept-ranges	bytes
x-content-type-options	nosniff
x-permitted-cross-domain-policies	none
x-xss-protection	0
x-frame-options	SAMEORIGIN
referrer-policy	strict-origin-when-cross-origin

WWW TLS

Transport Layer Security (TLS) is the most widely used encryption protocol on the Internet. In combination with valid certificates, servers can establish trusted communication channels even with users who have never visited them before. Network attackers can't uncover what is being communicated, even when they can see all the traffic.

Test passed

Everything seems to be well configured. Well done.

TLS Configuration: uio.no (2001:700:100:118:0:0:0:130)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.3 TLS v1.2
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3 Server preference	Suite: TLS_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_AES_128_GCM_SHA256 Suite ID: 0x1301 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_AES_256_GCM_SHA384 Suite ID: 0x1302 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca9 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02b Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc02c Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits)

Analysis

TLS 1.3 supported

Excellent. This server supports TLS 1.3, which is the latest revision of the TLS protocol and a significant improvement over earlier versions. Developed over a period of several years and extensively analyzed prior to the release, TLS 1.3 removed insecure features, and improved both security and performance.

TLS 1.2 supported

Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.

Deprecated protocols not supported

Excellent. This server doesn't support any of the deprecated protocol (TLS 1.1 and earlier).

Strong key exchange detected

Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.

Only strong suites supported

Excellent. This server supports only strong cipher suites, which use strong authenticated encryption and provide forward secrecy.

All TLS connections with this server satisfy Apple's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

All TLS connections with this server satisfy Chrome's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

DHE suites not supported

This server doesn't support the Diffie-Hellman (DH) key exchange.

TLS Configuration: www.uio.no (2001:700:100:118:0:0:0:130)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.3 TLS v1.2
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3 Server preference	Suite: TLS_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_AES_128_GCM_SHA256 Suite ID: 0x1301 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_AES_256_GCM_SHA384 Suite ID: 0x1302 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca9 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02b Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc02c Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits)

Analysis

TLS 1.3 supported

Excellent. This server supports TLS 1.3, which is the latest revision of the TLS protocol and a significant improvement over earlier versions. Developed over a period of several years and extensively analyzed prior to the release, TLS 1.3 removed insecure features, and improved both security and performance.

TLS 1.2 supported

Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.

Deprecated protocols not supported

Excellent. This server doesn't support any of the deprecated protocol (TLS 1.1 and earlier).

Strong key exchange detected

Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.

Only strong suites supported

Excellent. This server supports only strong cipher suites, which use strong authenticated encryption and provide forward secrecy.

All TLS connections with this server satisfy Apple's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

All TLS connections with this server satisfy Chrome's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

DHE suites not supported

This server doesn't support the Diffie-Hellman (DH) key exchange.

TLS Configuration: uio.no (129.240.118.130)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.3 TLS v1.2
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3 Server preference	Suite: TLS_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_AES_128_GCM_SHA256 Suite ID: 0x1301 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_AES_256_GCM_SHA384 Suite ID: 0x1302 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca9 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02b Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc02c Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits)

Analysis

TLS 1.3 supported

Excellent. This server supports TLS 1.3, which is the latest revision of the TLS protocol and a significant improvement over earlier versions. Developed over a period of several years and extensively analyzed prior to the release, TLS 1.3 removed insecure features, and improved both security and performance.

TLS 1.2 supported

Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.

Deprecated protocols not supported

Excellent. This server doesn't support any of the deprecated protocol (TLS 1.1 and earlier).

Strong key exchange detected

Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.

Only strong suites supported

Excellent. This server supports only strong cipher suites, which use strong authenticated encryption and provide forward secrecy.

All TLS connections with this server satisfy Apple's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

All TLS connections with this server satisfy Chrome's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

DHE suites not supported

This server doesn't support the Diffie-Hellman (DH) key exchange.

TLS Configuration: www.uio.no (129.240.118.130)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.3 TLS v1.2
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3 Server preference	Suite: TLS_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_AES_128_GCM_SHA256 Suite ID: 0x1301 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_AES_256_GCM_SHA384 Suite ID: 0x1302 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca9 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02b Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc02c Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits)

Analysis

TLS 1.3 supported

Excellent. This server supports TLS 1.3, which is the latest revision of the TLS protocol and a significant improvement over earlier versions. Developed over a period of several years and extensively analyzed prior to the release, TLS 1.3 removed insecure features, and improved both security and performance.

TLS 1.2 supported

Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.

Deprecated protocols not supported

Excellent. This server doesn't support any of the deprecated protocol (TLS 1.1 and earlier).

Strong key exchange detected

Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.

Only strong suites supported

Excellent. This server supports only strong cipher suites, which use strong authenticated encryption and provide forward secrecy.

All TLS connections with this server satisfy Apple's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

All TLS connections with this server satisfy Chrome's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

DHE suites not supported

This server doesn't support the Diffie-Hellman (DH) key exchange.

WWW Certificates

A certificate is a digital document that contains a public key, some information about the entity associated with it, and a digital signature from the certificate issuer. It’s a mechanism that enables us to exchange, store, and use public keys. Being able to reliably verify the identity of a remote server is crucial in order to achieve secure encrypted communication.

Test passed

Everything seems to be well configured. Well done.

Certificate: www.uio.no

Leaf certificate

uio.no
Issuer: Sectigo
Not Before: 16 Oct 2023 00:00:00 UTC
Not After: 15 Oct 2024 23:59:59 UTC (expires in 5 months 27 days)
Key: EC 256 bits
Signature: SHA256withECDSA
View details

Names	uio.no www-int.uio.no www.uio.no
Subject DN	CN=uio.no, O=Universitetet i Oslo, ST=Oslo, C=NO
Subject Key Identifier	08d84c9b5d79473b88d9786dbc6bb9cf682488d6
Serial	b240b7a5a3734cac0a0c7b6774c6cb9b
Not Before	16 Oct 2023 00:00:00 UTC
Not After	15 Oct 2024 23:59:59 UTC
Validity period	366 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=GEANT OV ECC CA 4, O=GEANT Vereniging, C=NL
Certification Authority	Sectigo
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:edb4a0336a1b0891b6bdfa4192bd9aabab63f453
Parent Certificate	http://GEANT.crt.sectigo.com/GEANTOVECCCA4.crt
CRL	http://GEANT.crl.sectigo.com/GEANTOVECCCA4.crl
OCSP	http://GEANT.ocsp.sectigo.com
Certificate Transparency
Signed Certificate Timestamps	16 Oct 2023 09:07:42 UTC \| Google 'Xenon2024' log \| Qualified 16 Oct 2023 09:07:42 UTC \| Cloudflare 'Nimbus2024' Log \| Qualified 16 Oct 2023 09:07:42 UTC \| Google 'Argon2024' log \| Qualified
Fingerprints
SHA1	659065eb3f02ab2bfead01d6de23884ede50330e
SHA256	39979343096b6413330415b8f76a69736057252d232bc80c2fe5e85e0b37ae32
SPKI SHA256	a82eff703891a0421b67b051eadac87b293e764888585d9de5a3d91f5d88c386

Analysis

Strong private key

Good. The private key associated with this certificate is secure.

Strong signature algorithm

Good. This certificate uses a strong signature algorithm.

Certificate matches hostname

Good. The provided certificate matches the expected hostnames.

Certificate dates match

Good. The certificate is valid for use at this point of time.

Certificate has not been revoked

Good. This certificate has not been revoked.

Certificate satisfies Apple's CT compliance requirements

Good. This certificate satisfies Apple's CT requirements at present.

Certificate Trust

Determining whether a certificate is considered valid is a complicated process that depends on the exact configuration of the validating party. For trust to be established, the certificate must form a chain that ends with a trusted root. In this section we evaluate the server's certificate against major root stores.

Platform	Trusted
Apple
Google AOSP
Microsoft
Mozilla

Certificate Chain

For a server certificate to be valid, it must be presented as part of a complete and valid certificate chain. The last certificate in the chain should be the root and is usually not included in the configuration.

Leaf certificate

uio.no | 3997934
Not After: 15 Oct 2024 23:59:59 UTC (expires in 5 months 27 days)
Authentication: EC 256 bits (SHA256withECDSA)
View details

Names	uio.no www-int.uio.no www.uio.no
Subject DN	CN=uio.no, O=Universitetet i Oslo, ST=Oslo, C=NO
Subject Key Identifier	08d84c9b5d79473b88d9786dbc6bb9cf682488d6
Serial	b240b7a5a3734cac0a0c7b6774c6cb9b
Not Before	16 Oct 2023 00:00:00 UTC
Not After	15 Oct 2024 23:59:59 UTC
Validity period	366 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=GEANT OV ECC CA 4, O=GEANT Vereniging, C=NL
Certification Authority	Sectigo
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:edb4a0336a1b0891b6bdfa4192bd9aabab63f453
Parent Certificate	http://GEANT.crt.sectigo.com/GEANTOVECCCA4.crt
CRL	http://GEANT.crl.sectigo.com/GEANTOVECCCA4.crl
OCSP	http://GEANT.ocsp.sectigo.com
Certificate Transparency
Signed Certificate Timestamps	16 Oct 2023 09:07:42 UTC \| Google 'Xenon2024' log \| Qualified 16 Oct 2023 09:07:42 UTC \| Cloudflare 'Nimbus2024' Log \| Qualified 16 Oct 2023 09:07:42 UTC \| Google 'Argon2024' log \| Qualified
Fingerprints
SHA1	659065eb3f02ab2bfead01d6de23884ede50330e
SHA256	39979343096b6413330415b8f76a69736057252d232bc80c2fe5e85e0b37ae32
SPKI SHA256	a82eff703891a0421b67b051eadac87b293e764888585d9de5a3d91f5d88c386

Intermediate certificate

GEANT OV ECC CA 4 | 083799e
Not After: 01 May 2033 23:59:59 UTC (expires in 9 years 13 days)
Authentication: EC 256 bits (SHA384withECDSA)
View details

Subject DN	CN=GEANT OV ECC CA 4, O=GEANT Vereniging, C=NL
Subject Key Identifier	edb4a0336a1b0891b6bdfa4192bd9aabab63f453
Serial	eb8e81197129f4af64ef814a2f50cee9
Not Before	18 Feb 2020 00:00:00 UTC
Not After	01 May 2033 23:59:59 UTC
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	serverAuth, clientAuth
Issuer
Issuer DN	CN=USERTrust ECC Certification Authority, O=The USERTRUST Network, L=Jersey City, ST=New Jersey, C=US
Certification Authority	Sectigo
Validation Type	Not Applicable
Authority Key Identifier	keyid:3ae10986d4cf19c29676744976dce035c663639a
Parent Certificate	http://crt.usertrust.com/USERTrustECCAddTrustCA.crt
CRL	http://crl.usertrust.com/USERTrustECCCertificationAuthority.crl
OCSP	http://ocsp.usertrust.com
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	8a63c019620165b85120c8deb3362d0795020486
SHA256	083799e8b2b9016e44702ebf9bf369ce253fe1fbeb650e5df10ef44d87bf3bae
SPKI SHA256	9cc638bee15581f92658138371bf9348686ce2c8af7a0765b8660f19d99cf9a7

Root certificate

USERTrust ECC Certification Authority | 4ff460d
Not After: 18 Jan 2038 23:59:59 UTC (expires in 13 years 9 months)
Authentication: EC 384 bits (SHA384withECDSA)
View details

Subject DN	CN=USERTrust ECC Certification Authority, O=The USERTRUST Network, L=Jersey City, ST=New Jersey, C=US
Subject Key Identifier	3ae10986d4cf19c29676744976dce035c663639a
Serial	5c8b99c55a94c5d27156decd8980cc26
Not Before	01 Feb 2010 00:00:00 UTC
Not After	18 Jan 2038 23:59:59 UTC
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=USERTrust ECC Certification Authority, O=The USERTRUST Network, L=Jersey City, ST=New Jersey, C=US
Certification Authority	Sectigo
Validation Type	Self-signed
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	d1cbca5db2d52a7f693b674de5f05a1d0c957df0
SHA256	4ff460d54b9c86dabfbcfc5712e0400d2bed3fbc4d4fbdaa86e06adcd2a9ad7a
SPKI SHA256	2021917e98263945c859c43f1d73cb4139053c414fa03ca3bc7ee88614298f3b

Analysis

Certificate chain is correct

Good. This chain contains all the right certificates and in the right order.

Certificate: uio.no

Leaf certificate

uio.no
Issuer: Sectigo
Not Before: 16 Oct 2023 00:00:00 UTC
Not After: 15 Oct 2024 23:59:59 UTC (expires in 5 months 27 days)
Key: EC 256 bits
Signature: SHA256withECDSA
View details

Names	uio.no www-int.uio.no www.uio.no
Subject DN	CN=uio.no, O=Universitetet i Oslo, ST=Oslo, C=NO
Subject Key Identifier	08d84c9b5d79473b88d9786dbc6bb9cf682488d6
Serial	b240b7a5a3734cac0a0c7b6774c6cb9b
Not Before	16 Oct 2023 00:00:00 UTC
Not After	15 Oct 2024 23:59:59 UTC
Validity period	366 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=GEANT OV ECC CA 4, O=GEANT Vereniging, C=NL
Certification Authority	Sectigo
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:edb4a0336a1b0891b6bdfa4192bd9aabab63f453
Parent Certificate	http://GEANT.crt.sectigo.com/GEANTOVECCCA4.crt
CRL	http://GEANT.crl.sectigo.com/GEANTOVECCCA4.crl
OCSP	http://GEANT.ocsp.sectigo.com
Certificate Transparency
Signed Certificate Timestamps	16 Oct 2023 09:07:42 UTC \| Google 'Xenon2024' log \| Qualified 16 Oct 2023 09:07:42 UTC \| Cloudflare 'Nimbus2024' Log \| Qualified 16 Oct 2023 09:07:42 UTC \| Google 'Argon2024' log \| Qualified
Fingerprints
SHA1	659065eb3f02ab2bfead01d6de23884ede50330e
SHA256	39979343096b6413330415b8f76a69736057252d232bc80c2fe5e85e0b37ae32
SPKI SHA256	a82eff703891a0421b67b051eadac87b293e764888585d9de5a3d91f5d88c386

Analysis

Strong private key

Good. The private key associated with this certificate is secure.

Strong signature algorithm

Good. This certificate uses a strong signature algorithm.

Certificate matches hostname

Good. The provided certificate matches the expected hostnames.

Certificate dates match

Good. The certificate is valid for use at this point of time.

Certificate has not been revoked

Good. This certificate has not been revoked.

Certificate satisfies Apple's CT compliance requirements

Good. This certificate satisfies Apple's CT requirements at present.

Certificate Trust

Determining whether a certificate is considered valid is a complicated process that depends on the exact configuration of the validating party. For trust to be established, the certificate must form a chain that ends with a trusted root. In this section we evaluate the server's certificate against major root stores.

Platform	Trusted
Apple
Google AOSP
Microsoft
Mozilla

Certificate Chain

For a server certificate to be valid, it must be presented as part of a complete and valid certificate chain. The last certificate in the chain should be the root and is usually not included in the configuration.

Leaf certificate

uio.no | 3997934
Not After: 15 Oct 2024 23:59:59 UTC (expires in 5 months 27 days)
Authentication: EC 256 bits (SHA256withECDSA)
View details

Names	uio.no www-int.uio.no www.uio.no
Subject DN	CN=uio.no, O=Universitetet i Oslo, ST=Oslo, C=NO
Subject Key Identifier	08d84c9b5d79473b88d9786dbc6bb9cf682488d6
Serial	b240b7a5a3734cac0a0c7b6774c6cb9b
Not Before	16 Oct 2023 00:00:00 UTC
Not After	15 Oct 2024 23:59:59 UTC
Validity period	366 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=GEANT OV ECC CA 4, O=GEANT Vereniging, C=NL
Certification Authority	Sectigo
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:edb4a0336a1b0891b6bdfa4192bd9aabab63f453
Parent Certificate	http://GEANT.crt.sectigo.com/GEANTOVECCCA4.crt
CRL	http://GEANT.crl.sectigo.com/GEANTOVECCCA4.crl
OCSP	http://GEANT.ocsp.sectigo.com
Certificate Transparency
Signed Certificate Timestamps	16 Oct 2023 09:07:42 UTC \| Google 'Xenon2024' log \| Qualified 16 Oct 2023 09:07:42 UTC \| Cloudflare 'Nimbus2024' Log \| Qualified 16 Oct 2023 09:07:42 UTC \| Google 'Argon2024' log \| Qualified
Fingerprints
SHA1	659065eb3f02ab2bfead01d6de23884ede50330e
SHA256	39979343096b6413330415b8f76a69736057252d232bc80c2fe5e85e0b37ae32
SPKI SHA256	a82eff703891a0421b67b051eadac87b293e764888585d9de5a3d91f5d88c386

Intermediate certificate

GEANT OV ECC CA 4 | 083799e
Not After: 01 May 2033 23:59:59 UTC (expires in 9 years 13 days)
Authentication: EC 256 bits (SHA384withECDSA)
View details

Subject DN	CN=GEANT OV ECC CA 4, O=GEANT Vereniging, C=NL
Subject Key Identifier	edb4a0336a1b0891b6bdfa4192bd9aabab63f453
Serial	eb8e81197129f4af64ef814a2f50cee9
Not Before	18 Feb 2020 00:00:00 UTC
Not After	01 May 2033 23:59:59 UTC
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	serverAuth, clientAuth
Issuer
Issuer DN	CN=USERTrust ECC Certification Authority, O=The USERTRUST Network, L=Jersey City, ST=New Jersey, C=US
Certification Authority	Sectigo
Validation Type	Not Applicable
Authority Key Identifier	keyid:3ae10986d4cf19c29676744976dce035c663639a
Parent Certificate	http://crt.usertrust.com/USERTrustECCAddTrustCA.crt
CRL	http://crl.usertrust.com/USERTrustECCCertificationAuthority.crl
OCSP	http://ocsp.usertrust.com
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	8a63c019620165b85120c8deb3362d0795020486
SHA256	083799e8b2b9016e44702ebf9bf369ce253fe1fbeb650e5df10ef44d87bf3bae
SPKI SHA256	9cc638bee15581f92658138371bf9348686ce2c8af7a0765b8660f19d99cf9a7

Root certificate

USERTrust ECC Certification Authority | 4ff460d
Not After: 18 Jan 2038 23:59:59 UTC (expires in 13 years 9 months)
Authentication: EC 384 bits (SHA384withECDSA)
View details

Subject DN	CN=USERTrust ECC Certification Authority, O=The USERTRUST Network, L=Jersey City, ST=New Jersey, C=US
Subject Key Identifier	3ae10986d4cf19c29676744976dce035c663639a
Serial	5c8b99c55a94c5d27156decd8980cc26
Not Before	01 Feb 2010 00:00:00 UTC
Not After	18 Jan 2038 23:59:59 UTC
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=USERTrust ECC Certification Authority, O=The USERTRUST Network, L=Jersey City, ST=New Jersey, C=US
Certification Authority	Sectigo
Validation Type	Self-signed
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	d1cbca5db2d52a7f693b674de5f05a1d0c957df0
SHA256	4ff460d54b9c86dabfbcfc5712e0400d2bed3fbc4d4fbdaa86e06adcd2a9ad7a
SPKI SHA256	2021917e98263945c859c43f1d73cb4139053c414fa03ca3bc7ee88614298f3b

Analysis

Certificate chain is correct

Good. This chain contains all the right certificates and in the right order.

DANE (443)

DNS-based Authentication of Named Entities (DANE) is a bridge between DNSSEC and TLS. In one possible scenario, DANE can be used for public key pinning, building on an existing publicly-trusted certificate. In another approach, it can be used to completely bypass the CA ecosystem and establish trust using DNSSEC alone.

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

Cookies

Cookies are small chunks of text that are sent between your browser and a website. They are often essential to the operation of the site and sometimes contain sensitive information. Session cookies sent from secure sites must be explicitly marked as secure to prevent being obtained by active network attackers.

Test passed

Everything seems to be well configured. Well done.

Mixed Content

On virtually all web sites, HTML markup, images, style sheets, JavaScript, and other page resources arrive not only over multiple connections but possibly from multiple servers and sites spread across the entire Internet. For a page to be properly encrypted, it’s necessary that all the content is retrieved over HTTPS. In practice, that’s very often not the case, leading to mixed content security problems.

Test passed, but there are warnings

Some aspect of your site's configuration require your attention.

Embedded Resources

In this section we look at the security of all embedded resources. Mixed active content occurs when there are unprotected scripts or styles embedded in a page. This is typically not allowed by modern browsers. Mixed passive content (images, videos and such) are typically allowed, but shouldn't be present.

7 script(s)
7 out of 7 are secure View all

Status	Link
Encrypted	https://www.uio.no/...ources/js/consent.js
Encrypted	https://www.uio.no/.../internal-network.js
Encrypted	https://www.uio.no/...io2/js/jquery.min.js
Encrypted	https://vrtx.uio.no/...nalytics/v2/uioGa.js
Encrypted	https://www.uio.no/.../external-network.js
Encrypted	https://vrtx.uio.no/....no/customTracker.js
Encrypted	https://www.uio.no/...rces/uio2/js/uio2.js

1 CSS file(s)
1 out of 1 are secure View all

Status	Link
Encrypted	https://www.uio.no/.../uio2/css/style2.css

16 media file(s)
16 out of 16 are secure View all

Status	Link
Encrypted	https://www.uio.no/...nter-uio_804x473.jpg
Encrypted	https://www.uio.no/...blindern-768x576.jpg
Encrypted	https://www.uio.no/...-komopst_690x517.jpg
Encrypted	https://www.uio.no/...edbilde_1000x562.jpg
Encrypted	https://www.uv.uio.no/...o-fra-colourbox.webp
Encrypted	https://www.sv.uio.no/...1000x563--siste-.png
Encrypted	https://www.sv.uio.no/...b-nyrup_1000x563.png
Encrypted	https://www.uio.no/...omus-bibliotheca.jpg
Encrypted	https://www.uio.no/.../podkast-595x595.png
Encrypted	https://www.ub.uio.no/...hut-up-and-write.png
Encrypted	https://www.ub.uio.no/...arn_nylogo_nett.jpeg
Encrypted	https://www.nhm.uio.no/...er-nettside-1200.jpg
Encrypted	https://www.nhm.uio.no/...er-nettside-1200.jpg
Encrypted	https://www.historiskmuseum.no/...nesondagantikken.png
Encrypted	https://www.uio.no/...eu-theguild-logo.png
Encrypted	https://www.uio.no/...oter/uio-logo-no.svg

Outbound Links

Ideally, an encrypted page should only have links that lead to other encrypted pages. If plaintext links are used, passive network attackers can see where people go after they visit your web site. It's also possible that some sensitive information is leaked in the Referer header.

30 link(s)
25 out of 30 are encrypted

http://canvas.uio.no

http://minestudier.no

http://www.facebook.com/uniOslo

http://www.twitter.com/unioslo

http://instagram.com/unioslo

View all

Status	Link
Encrypted	https://for-ansatte.uio.no/index.html
Encrypted	https://minestudier.no/nb/index.html
Plaintext	http://canvas.uio.no
Plaintext	http://minestudier.no
Encrypted	https://ub.uio.no
Encrypted	https://www.uv.uio.no/...el-av-losningen.html
Encrypted	https://www.uv.uio.no/...el-av-losningen.html
Encrypted	https://www.sv.uio.no/.../eos-utredning-.html
Encrypted	https://www.sv.uio.no/.../eos-utredning-.html
Encrypted	https://www.sv.uio.no/...ske-regjeringer.html
Encrypted	https://www.sv.uio.no/...ske-regjeringer.html
Encrypted	https://open.spotify.com/...14R1zUo11XFJoohJhaaW
Encrypted	https://podcasts.apple.com/...plassen/id1520200628
Encrypted	https://www.ub.uio.no/...-and-write-0419.html
Encrypted	https://www.ub.uio.no/...-and-write-0419.html
Encrypted	https://link.mazemap.com/lZs2TEpg
Encrypted	https://www.ub.uio.no/...2024/2024.04.19.html
Encrypted	https://www.ub.uio.no/...2024/2024.04.19.html
Encrypted	https://www.nhm.uio.no/...eomvisning/0420.html
Encrypted	https://www.nhm.uio.no/...eomvisning/0420.html
Encrypted	https://www.nhm.uio.no/...eomvisning/0421.html
Encrypted	https://www.nhm.uio.no/...eomvisning/0421.html
Encrypted	https://www.historiskmuseum.no/...e-egypt21042024.html
Encrypted	https://www.historiskmuseum.no/...e-egypt21042024.html
Plaintext	http://www.facebook.com/uniOslo
Plaintext	http://www.twitter.com/unioslo
Plaintext	http://instagram.com/unioslo
Encrypted	https://www.youtube.com/user/UiOinfo
Encrypted	https://uustatus.no/...db-b3f2-54df3b231a44
Encrypted	https://www-adm.uio.no/index.html

Analysis

Plaintext outbound links in HTTPS page

When outbound links are not encrypted, a passive network attacker can see where your users go after visiting your web site.

HTTP Strict Transport Security

HTTP Strict Transport Security (HSTS) vastly improves security of the network encryption layer. With HSTS enabled, browsers no longer allow clicking through certificate warnings errors, which are typically trivial to exploit. Additionally, they will no longer submit insecure (plaintext) requests to the site in question, even if asked.

Test passed, but there are warnings

Some aspect of your site's configuration require your attention.

HSTS Policy Main host

URL from which this policy was obtained.Location	https://www.uio.no/
Specifies policy duration. Once activated, HSTS stays in force until this time lapses. Browsers update policy cache duration every time they receive a new HSTS header from a site.max‑age	31,536,000 seconds (about 1 year)
When present, this directive forces HSTS activation on allsubdomains. For best security, HSTS should be deployed on the bare domain name (e.g., example.com) and all its subdomains.includeSubDomains
Presence of this directive indicates that a web site wishes to permanently use HSTS and that its policy information should be preloaded (embedded in browsers).preload

Analysis

Policy is valid

OK. Your HSTS policy uses correct syntax.

Long policy age

Your HSTS policy has a long max-age value, which offers better protection.

No subdomains

This HSTS policy doesn't cover subdomains. Without full coverage, HSTS can't protect from certain cookie attacks that typically allow active network attackers to inject cookies into an application. Additionally, subdomain coverage is one of the requirements to allow preloading.

Preload directive has no effect here

This policy doesn't enable preloading, but that's all right. The preload directive doesn't have any effect unless it's used on an apex hostname.

Redirection from HTTP to HTTPS to the same host

Good. The redirection from HTTP to HTTPS is to the same host. This approach ensures that HSTS is activated on the hostname when it's accessed via plaintext.

No parent protection

This host could benefit from further protection if the apex hostname would be configured with a HSTS policy that uses 'includeSubDomains'. Enabling HSTS on an entire domain name is the only approach that provides robust security.

HSTS Policy Apex host

URL from which this policy was obtained.Location	https://uio.no/
Specifies policy duration. Once activated, HSTS stays in force until this time lapses. Browsers update policy cache duration every time they receive a new HSTS header from a site.max‑age	63,072,000 seconds (about 2 years)
When present, this directive forces HSTS activation on allsubdomains. For best security, HSTS should be deployed on the bare domain name (e.g., example.com) and all its subdomains.includeSubDomains
Presence of this directive indicates that a web site wishes to permanently use HSTS and that its policy information should be preloaded (embedded in browsers).preload

Analysis

Policy is valid

OK. Your HSTS policy uses correct syntax.

Long policy age

Your HSTS policy has a long max-age value, which offers better protection.

No subdomains

This HSTS policy doesn't cover subdomains. Without full coverage, HSTS can't protect from certain cookie attacks that typically allow active network attackers to inject cookies into an application. Additionally, subdomain coverage is one of the requirements to allow preloading.

Preloading not enabled

This policy doesn't give browsers permission to embed it and provide protection even to the first request to the web site. Sites that wish to use preloading can apply at hstspreload.org.

Redirection from HTTP to HTTPS to the same host

Good. The redirection from HTTP to HTTPS is to the same host. This approach ensures that HSTS is activated on the hostname when it's accessed via plaintext.

Analysis

Policy set on plaintext port

HSTS policies must not be transmitted over insecure channels.

Location: http://uio.no/

Policy set on plaintext port

HSTS policies must not be transmitted over insecure channels.

Location: http://www.uio.no/

HTTP Public Key Pinning

HTTP Public Key Pinning (HPKP) enables site operators to restrict which certificates are considered valid for their domain names. With a valid HPKP configuration, sites can defeat man in the middle (MITM) attacks using fraudulent or misissued certificates. HPKP is an advanced feature, suitable for use by only high-profile web sites.

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

Content Security Policy

Content Security Policy (CSP) is a security mechanism that allows web sites control how browsers process their pages. In essence, sites can restrict what types of resources are loaded and from where. CSP policies can be used to defend against cross-site scripting, prevent mixed content issues, as well as report violations for investigation.

Test passed

Everything seems to be well configured. Well done.

content-security-policy

frame-ancestors	*
upgrade-insecure-requests
object-src	'none'

Analysis

Mixed content upgraded

Good. This CSP policy instructs browsers to seamlessly upgrade plaintext resources to encryption.

Form targets not restricted

The 'form-action' directive is not explicitly set. Because this directive doesn't fall back to default sources, this means that all targets are allowed.

Analysis

CSP policy detected

Header: content-security-policy

Value: frame-ancestors *; upgrade-insecure-requests; object-src 'none'

Location: https://www.uio.no/

Subresource Integrity

Subresource Integrity (SRI) is a new standard that enables browsers to verify the integrity of embedded page resources (e.g., scripts and stylesheets) when they are loaded from third-party web sites. With SRI deployed, remote resources can be used safely, without fear of them being modified by malicious parties.

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

7 script(s)
5 out of 7 are secure

https://vrtx.uio.no/...nalytics/v2/uioGa.js

https://vrtx.uio.no/....no/customTracker.js

View all

Status	Link
Local	/vrtx/dist/resources/js/consent.js
Local	/vrtx/__vrtx/app-services/internal-network.js
Local	/vrtx/dist/resources/uio2/js/jquery.min.js
Remote	https://vrtx.uio.no/js/analytics/v2/uioGa.js
Local	/vrtx/__vrtx/app-services/external-network.js
Remote	https://vrtx.uio.no/js/analytics/v2/www.uio.no/customTracker.js
Local	/vrtx/dist/resources/uio2/js/uio2.js

1 CSS file(s)
1 out of 1 are secure View all

Status	Link
Local	/vrtx/dist/resources/uio2/css/style2.css

Analysis

SRI required

This page contains remote resources that are under the control of third parties. Deploy SRI to protect them from modification.

Expect CT

Expect-CT is a deprecated response HTTP header designed to enable web sites to monitor problems related to their Certificate Transparency (CT) compliance. Should any CT issues arise, browsers that supported this header will submit reports to the specified reporting endpoint. Chrome was the browser that introduced support for this response header, but later deprecated it and removed it in version 107.

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

Analysis

Deploy Expect-CT to enable reporting

An Expect-CT policy enables web sites to monitor for any problems related to their Expect-CT compliance, detecting potentially serious issues quickly. When issues arise, compliant browsers will submit reports to the specified reporting endpoints. Before CT became required for all public certificates the Expect-CT was also used to require CT, but that use case no longer applies.

Frame Options

The X-Frame-Options header controls page framing, which occurs when a page is incorporated into some other page, possibly on a different site. If framing is allowed, attackers can employ clever tricks to make victims perform arbitrary actions on your site; they do this by showing their web site while forwarding the victim's clicks to yours.

Test passed

Everything seems to be well configured. Well done.

Analysis

Header information

Name: x-frame-options

Value: SAMEORIGIN

Framing allowed from the same origin only

OK. Your site allows page framing only from itself. This should generally be safe, except maybe on sites that host user content.

XSS Protection

Some browsers ship with so-called XSS Auditors, built-in defenses against XSS. Although these defenses work against simple reflective XSS attacks, they can be abused by skillful attackers to add weaknesses to otherwise secure web sites. These dangers are present in both filtering and blocking modes. At this time, the Safari browser ships with its XSS defenses enabled by default. For this reason, the best approach is to explicitly disable this functionality.

Test passed

Everything seems to be well configured. Well done.

Analysis

Header information

Name: x-xss-protection

Value: 0

Browser XSS protection disabled

Great. XSS protection is explicitly disabled, making this web site safe even with browsers that have this functionality enabled by default.

Content Type Options

Some browsers use a technique called content sniffing to override response MIME types provided by HTTP servers and interpret responses as something else (usually HTML). This behavior, which could potentially lead to security issues, should be disabled by attaching an X-Content-Type-Options header to all responses.

Test passed

Everything seems to be well configured. Well done.

Analysis

Header information

Name: x-content-type-options

Value: nosniff

Valid configuration

Good. Your configuration is valid. This means that browsers won't try to guess file MIME type on this web site.

Public Report | uio.no

uio.no

Domain Name System

Email

WWW

Domain Registration

Registration Data Access Protocol (RDAP)

WHOIS

DNS Zone

Nameserver Names

Nameserver Addresses

Start of Authority (SOA) Record

Analysis

Backing DNS Queries

DNS Records

DNS Records

Analysis

Backing DNS Queries

DNSSEC

Useful DNSSEC Tools

Certification Authority Authorization

CAA Policy Information

Analysis

Email (SMTP)

Analysis

Email TLS (SMTP)

TLS Configuration: smtp.uio.no (129.240.2.125) Cached

Analysis

Email Certificates (SMTP)

Certificate #1 Cached

Analysis

Certificate Chain

Analysis

Certificate #2 Cached

Analysis

Certificate Chain

Analysis

Email DANE (SMTP)

SPF

SPF Policy Information Main policy

Analysis

SPF Policy Information Included policy

SPF Policy Information Included policy

SPF Policy Information Included policy

SPF Policy Information Included policy

SPF Policy Information Included policy

SPF Policy Information Included policy

SPF Policy Information Included policy

DMARC

MTA Strict Transport Security

SMTP TLS Reporting

HTTP (80)

URL: http://uio.no/

Analysis

URL: http://www.uio.no/

Analysis

HTTP (443)

URL: https://uio.no/

URL: https://www.uio.no/

WWW TLS

TLS Configuration: uio.no (2001:700:100:118:0:0:0:130)

Analysis

TLS Configuration: www.uio.no (2001:700:100:118:0:0:0:130)

Analysis

TLS Configuration: uio.no (129.240.118.130)

Analysis

TLS Configuration: www.uio.no (129.240.118.130)

Analysis

WWW Certificates

Certificate: www.uio.no

Analysis

Certificate Trust

Certificate Chain

Analysis

Certificate: uio.no

Analysis

Certificate Trust

Certificate Chain

Analysis

DANE (443)