Hardenize has joined Red Sift! Find out more in our blog post.
Web Security Overview
Warning
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
Supported and well configured
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
Warning
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
Not supported
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
Supported and well configured
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
Supported and well configured
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
Supported and well configured
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
Supported and well configured
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, but there are warnings
Some aspect of your site's configuration require your attention.

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.

Registrant World Health Organization (WHO)
Lookup Time 19 May 2024 00:40 UTC
Source https://rdap.iana.org/domain/who.int
Registrar
Registrar -
Events
Registration 05 Jun 1998 00:00 UTC
Update 10 Dec 2020 00:00 UTC
Expiration -
Configuration
Statuses ok
Registrar Lock
Registry Lock
Nameservers whqdns1.who.int
158.232.12.5
whqdns2.who.int
158.232.12.6
whqdns3.who.int
211.24.11.120
ext-dns-2.cern.ch
192.91.245.85
ns1.wpro.who.int
123.176.64.11
Contacts
Registrant World Health Organization (WHO)
Administrative WHO-IMT-ESS
Email: hostmaster@who.int
Technical WHO-IMT-ESS
Email: hostmaster@who.int

Analysis

Warning
Registrar lock not in place
Most registrars should support locking a domain name to improve its security. Most commonly, the domain name is locked so that it cannot be transferred away. This is a small-effort security measure that should be used on all domain names to reduce the likelihood of hijacking.

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.

Registrant WHO-IMT-ESS
Lookup Time 19 May 2024 00:40 UTC
Source whois.iana.org:43
Registrar
Registrar -
Events
Registration 05 Jun 1998 00:00 UTC
Update 10 Dec 2020 00:00 UTC
Expiration -
Configuration
Statuses -
Registrar Lock -
Registry Lock -
Nameservers ext-dns-2.cern.ch
192.91.245.85
ns1.wpro.who.int
123.176.64.11
whqdns1.who.int
158.232.12.5
whqdns2.who.int
158.232.12.6
whqdns3.who.int
211.24.11.120
Contacts
Registrar 20, Avenue Appia, Geneva 27
Geneva CH-1211
Email: hostmaster@who.int
Phone: +41 22 791 2411
Fax: +41 22 791 3111
Administrative WHO-IMT-ESS
WHO-IMT-ESS
20, Avenue Appia, Geneva 27
Geneva CH-1211
Email: hostmaster@who.int
Phone: +41 22 791 2411
Fax: +41 22 791 3111
Technical WHO-IMT-ESS
WHO-IMT-ESS
20, Avenue Appia, Geneva 27
Geneva CH-1211
Email: hostmaster@who.int
Phone: +41 22 791 2411
Fax: +41 22 791 3111

Analysis

Warning
Registrar lock not in place
Most registrars should support locking a domain name to improve its security. Most commonly, the domain name is locked so that it cannot be transferred away. This is a small-effort security measure that should be used on all domain names to reduce the likelihood of hijacking.

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
ext-dns-2.cern.ch.
192.91.245.85
2001:1458:1:2::100:85
The server is online. Name resolves to an IPv4 address. Name resolves to an IPv6 address. REFERRAL NS
ns1.wpro.who.int.
123.176.64.11
The server is online. Name resolves to an IPv4 address. Name doesn't resolve to an IPv6 address. REFERRAL NS
whqdns1.who.int. PRIMARY
158.232.12.5
The server is online. Name resolves to an IPv4 address. Name doesn't resolve to an IPv6 address. SOA REFERRAL NS
whqdns2.who.int.
158.232.12.6
The server is online. Name resolves to an IPv4 address. Name doesn't resolve to an IPv6 address. REFERRAL NS
whqdns3.who.int.
211.24.11.120
The server is online. Name resolves to an IPv4 address. Name doesn't resolve to an IPv6 address. 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 Operational Authoritative Recursive UDP TCP Sources Payload Size
123.176.64.11
ns1.wpro.who.int.
The server appears to be online. Nameserver provides authoritative responses Nameserver doesn't provide recursive service Nameserver responds to UDP queries Nameserver responds to TCP queries NAME, GLUE 4000
158.232.12.5 PRIMARY
whqdns1.who.int.
PTR: whqdns1.who.int.
The server appears to be online. Nameserver provides authoritative responses Nameserver doesn't provide recursive service Nameserver responds to UDP queries Nameserver responds to TCP queries NAME, GLUE 1232
158.232.12.6
whqdns2.who.int.
PTR: whqdns2.who.int.
The server appears to be online. Nameserver provides authoritative responses Nameserver doesn't provide recursive service Nameserver responds to UDP queries Nameserver responds to TCP queries NAME, GLUE 1232
192.91.245.85
ext-dns-2.cern.ch.
PTR: ext-dns-2.cern.ch.
The server appears to be online. Nameserver provides authoritative responses Nameserver doesn't provide recursive service Nameserver responds to UDP queries Nameserver responds to TCP queries NAME 1232
211.24.11.120
whqdns3.who.int.
PTR: cgw-211-24-11-120.bbrtl.time.net.my.
The server appears to be online. Nameserver provides authoritative responses Nameserver doesn't provide recursive service Nameserver responds to UDP queries Nameserver responds to TCP queries NAME, GLUE 1232
2001:1458:1:2::100:85
ext-dns-2.cern.ch.
PTR: ext-dns-2.cern.ch.
The server appears to be online. Nameserver provides authoritative responses Nameserver doesn't provide recursive service Nameserver responds to UDP queries Nameserver responds to TCP queries 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 whqdns1.who.int.
Email address of the persons responsible for this zone. Also known as RNAME.Admin email hostmaster.who.int.
Zone serial or version number.Serial number 2024051001
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 604,800 seconds (about 7 days)
TTL for purposes of negative response caching. Negative cache TTL 10,800 seconds (about 3 hours)
Time To Live (TTL) indicates for how long a record remains valid. SOA record TTL 86,400 seconds (about 1 day)

Analysis

Powerup!
Nameserver addresses should have reverse names
According to RFC 1912, having reverse DNS configuration in place for every nameserver is a best practice that maximizes the chances of correct DNS operation. Further, some anti-spam techniques use reverse name resolution to allow traffic.
Powerup!
Nameserver A and AAAA records should have matching reverse records
According to RFC 1912, nameserver's PTR records must match their A and AAAA records to ensure maximum interoperability.
Powerup!
Improve IPv6 support
The Internet is in a slow transition to supporting IPv6 widely. Although at this time it is expected that most recursive DNS servers will use IPv4, adding support for IPv6 will enable transition to networks that use IPv6 exclusively.
Good
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
who.int.     900 A 192.133.11.1            
www.who.int.     86400 A 192.133.11.1            
who.int.     3600 MX 10 who-int.mail.protection.outlook.com.            
who.int.     86400 NS whqdns3.who.int.            
who.int.     86400 NS whqdns1.who.int.            
who.int.     86400 NS ext-dns-2.cern.ch.            
who.int.     86400 NS ns1.wpro.who.int.            
who.int.     86400 NS whqdns2.who.int.            
who.int.     86400 SOA whqdns1.who.int. hostmaster.who.int. 2024051001 10800 3600 604800 10800            
_sip._tls.who.int.     3600 SRV 1 100 443 sipdir.online.lync.com.            
_sipfederationtls._tcp.who.int.     3600 SRV 1 100 5061 sipfed.online.lync.com.            
_xmpp-server._tcp.who.int.     86400 SRV 5 0 5269 xmpp.who.int.            
who.int.     3600 TXT "ca3-5fc9c6c655cf481e9d53b30866a6e690"            
who.int.     3600 TXT "MS=ms38766037"            
who.int.     3600 TXT "ZOOM_verify_bTI318yfSumXtVIVnfEdzQ"            
who.int.     3600 TXT "v=spf1 ip4:158.232.12.0/24 include:spf.protection.outlook.com include:_spfincludes.who.int -all"            
who.int.     3600 TXT "apple-domain-verification=cYOp0B6FuXeoDFAX"            
who.int.     3600 TXT "ciscocidomainverification=17f32bae2ea200dbca5879cd0dc89294b7e78220da17554d099fed05e3f7e8f4"            
who.int.     3600 TXT "kfjFGux2GvIgH+XwWJgA8YLNiX6Jc9lZEtHz+2cfDoLo4cB03zeofnNz9eioELQriSHy0S6EuDQyrFY6DuoFqA=="            
who.int.     3600 TXT "docusign=9f72d1bd-efd7-4a97-b385-83d687978e8d"            
who.int.     3600 TXT "docusign=c346709c-41f2-43fd-8a5a-cf7992d6e560"            
who.int.     3600 TXT "google-gws-recovery-domain-verification=44731192"            
who.int.     3600 TXT "atlassian-domain-verification=UxKawy8Zm9aw6Yg8NrPBUbu9anpgfXtL2NS3L7DNt0MGYKfhw/WOXGuRCTcQMKqi"            
_dmarc.who.int.     600 TXT "v=DMARC1; p=reject; pct=100; fo=1; ri=3600; rua=mailto:422b6d07@inbox.ondmarc.com,mailto:dmarc-rua@who.int;"            

Analysis

Warning
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.who.int./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.

Feature not applicable, not implemented, or disabled
Your server doesn't support this feature.

Analysis

Powerup!
There is no CAA policy on this hostname
CAA policies can be used to restrict which CAs are allowed to issue certificates for a hostname. As such, CAA can be used to enforce an organization-wide policy and to prevent issuance of unauthorized certificates. The CA/Browser forum requires CAs to consult CAA configuration during certificate issuance from September 2017.

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
who-int.mail.protection.outlook.com
52.101.73.1
PTR: mail-am3pr04cu00501.inbound.protection.outlook.com
10
220 AM3PEPF00009BA1.mail.protection.outlook.com Microsoft ESMTP MAIL Service ready at Tue, 14 May 2024 00:27:03 +0000

EHLO outbound.hardenize.com
250-AM3PEPF00009BA1.mail.protection.outlook.com Hello [172.99.67.55]
250-SIZE 157286400
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-STARTTLS
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250 SMTPUTF8

STARTTLS
220 2.0.0 SMTP server ready
Supports STARTTLS. Not supported. Not applicable,
requires TLS.
who-int.mail.protection.outlook.com
52.101.68.3
PTR: mail-db7pr03cu00403.inbound.protection.outlook.com
10
220 DU2PEPF0001E9C4.mail.protection.outlook.com Microsoft ESMTP MAIL Service ready at Thu, 16 May 2024 00:34:35 +0000

EHLO outbound.hardenize.com
250-DU2PEPF0001E9C4.mail.protection.outlook.com Hello [172.99.67.55]
250-SIZE 157286400
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-STARTTLS
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250 SMTPUTF8

STARTTLS
220 2.0.0 SMTP server ready
Supports STARTTLS. Not supported. Not applicable,
requires TLS.
who-int.mail.protection.outlook.com
52.101.68.16
PTR: mail-db4pr02cu00400.inbound.protection.outlook.com
10
220 DB5PEPF00014B8C.mail.protection.outlook.com Microsoft ESMTP MAIL Service ready at Fri, 17 May 2024 00:46:22 +0000

EHLO outbound.hardenize.com
250-DB5PEPF00014B8C.mail.protection.outlook.com Hello [172.99.67.55]
250-SIZE 157286400
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-STARTTLS
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250 SMTPUTF8

STARTTLS
220 2.0.0 SMTP server ready
Supports STARTTLS. Not supported. Not applicable,
requires TLS.
who-int.mail.protection.outlook.com
52.101.68.25
PTR: mail-db8pr02cu00101.inbound.protection.outlook.com
10
220 DB3PEPF0000885B.mail.protection.outlook.com Microsoft ESMTP MAIL Service ready at Thu, 16 May 2024 00:32:37 +0000

EHLO outbound.hardenize.com
250-DB3PEPF0000885B.mail.protection.outlook.com Hello [172.99.67.55]
250-SIZE 157286400
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-STARTTLS
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250 SMTPUTF8

STARTTLS
220 2.0.0 SMTP server ready
Supports STARTTLS. Not supported. Not applicable,
requires TLS.
who-int.mail.protection.outlook.com
52.101.73.19
PTR: mail-as8pr04cu00803.inbound.protection.outlook.com
10
220 AMS1EPF0000004B.mail.protection.outlook.com Microsoft ESMTP MAIL Service ready at Sun, 19 May 2024 00:40:10 +0000

EHLO outbound.hardenize.com
250-AMS1EPF0000004B.mail.protection.outlook.com Hello [172.99.67.55]
250-SIZE 157286400
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-STARTTLS
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250 SMTPUTF8

STARTTLS
220 2.0.0 SMTP server ready
Supports STARTTLS. Not supported. Not applicable,
requires TLS.
who-int.mail.protection.outlook.com
52.101.68.18
PTR: mail-db4pr02cu00302.inbound.protection.outlook.com
10
220 DB5PEPF00014B9D.mail.protection.outlook.com Microsoft ESMTP MAIL Service ready at Sun, 19 May 2024 00:40:12 +0000

EHLO outbound.hardenize.com
250-DB5PEPF00014B9D.mail.protection.outlook.com Hello [172.99.67.55]
250-SIZE 157286400
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-STARTTLS
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250 SMTPUTF8

STARTTLS
220 2.0.0 SMTP server ready
Supports STARTTLS. Not supported. Not applicable,
requires TLS.
who-int.mail.protection.outlook.com
52.101.68.29
PTR: mail-dbapr03cu00105.inbound.protection.outlook.com
10
220 DU2PEPF00028D0C.mail.protection.outlook.com Microsoft ESMTP MAIL Service ready at Thu, 16 May 2024 00:32:34 +0000

EHLO outbound.hardenize.com
250-DU2PEPF00028D0C.mail.protection.outlook.com Hello [172.99.67.55]
250-SIZE 157286400
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-STARTTLS
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250 SMTPUTF8

STARTTLS
220 2.0.0 SMTP server ready
Supports STARTTLS. Not supported. Not applicable,
requires TLS.

Analysis

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

Latest cache timestamp: 17 May 2024 00:46 UTC

Earliest cache timestamp: 14 May 2024 00:27 UTC

Notice
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: who-int.mail.protection.outlook.com (52.101.73.1) 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_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 384 bits)
These results have been retrieved from
our cache. This row indicates when was
that the original test ran.
Retrieved from cache
14 May 2024 00:27 UTC

Analysis

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

TLS Configuration: who-int.mail.protection.outlook.com (52.101.68.3) 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_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 384 bits)
These results have been retrieved from
our cache. This row indicates when was
that the original test ran.
Retrieved from cache
16 May 2024 00:34 UTC

Analysis

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

TLS Configuration: who-int.mail.protection.outlook.com (52.101.68.16) 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_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 384 bits)
These results have been retrieved from
our cache. This row indicates when was
that the original test ran.
Retrieved from cache
17 May 2024 00:46 UTC

Analysis

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

TLS Configuration: who-int.mail.protection.outlook.com (52.101.68.25) 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_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 384 bits)
These results have been retrieved from
our cache. This row indicates when was
that the original test ran.
Retrieved from cache
16 May 2024 00:32 UTC

Analysis

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

TLS Configuration: who-int.mail.protection.outlook.com (52.101.73.19) 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_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 384 bits)

Analysis

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

TLS Configuration: who-int.mail.protection.outlook.com (52.101.68.18) 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_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 384 bits)

Analysis

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

TLS Configuration: who-int.mail.protection.outlook.com (52.101.68.29) 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_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 384 bits)
These results have been retrieved from
our cache. This row indicates when was
that the original test ran.
Retrieved from cache
16 May 2024 00:32 UTC

Analysis

Good
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.
Good
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.
Notice
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.
Notice
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 mail.protection.outlook.com
Issuer: DigiCert
Not Before: 12 Feb 2024 00:00:00 UTC
Not After: 11 Feb 2025 23:59:59 UTC (expires in 8 months 23 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
 View details

Analysis

Good
Strong private key
Good. The private key associated with this certificate is secure.
Good
Strong signature algorithm
Good. This certificate uses a strong signature algorithm.
Good
Certificate matches hostname
Good. The provided certificate matches the expected hostnames.
Good
Certificate dates match
Good. The certificate is valid for use at this point of time.
Good
Certificate has not been revoked
Good. This certificate has not been revoked.
Good
Certificate satisfies Apple's CT compliance requirements
Good. This certificate satisfies Apple's CT requirements at present.

Certificate Chain

Leaf certificate
mail.protection.outlook.com | 2735762
Not After: 11 Feb 2025 23:59:59 UTC (expires in 8 months 23 days)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Intermediate certificate
DigiCert Cloud Services CA-1 | 5f88694
Not After: 24 Sep 2030 23:59:59 UTC (expires in 6 years 4 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Root certificate
DigiCert Global Root CA | 4348a0e
Not After: 10 Nov 2031 00:00:00 UTC (expires in 7 years 5 months)
Authentication: RSA 2048 bits (SHA1withRSA)
 View details

Analysis

Good
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 who.int
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
158.232.12.0/24
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
Evaluates SPF policy specified in another DNS location. This
directive is typically used to allow hosts controlled by
another organization.
include
_spfincludes.who.int
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

Info
SPF policy found

Policy text: v=spf1 ip4:158.232.12.0/24 include:spf.protection.outlook.com include:_spfincludes.who.int -all

Location: who.int

Good
SPF policy is valid
Good. Your SPF policy is syntactically valid.
Good
Policy uses default fail
Excellent. This policy fails hosts that are not allowed to send email for this domain name.
Good
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: 9

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 _spfincludes.who.int
SPF version used by this policy.v spf1
This mechanism matches if the sending IP address
is one of the IP addresses that belong to the target
domain name. Matches both IPv4 and IPv6 addresses.
a
c.spf.service-now.com
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
160.34.64.28
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
168.245.118.121
Evaluates SPF policy specified in another DNS location. This
directive is typically used to allow hosts controlled by
another organization.
include
spf1.unicc.unicc.org
Evaluates SPF policy specified in another DNS location. This
directive is typically used to allow hosts controlled by
another organization.
include
_spf.salesforce.com
Evaluates SPF policy specified in another DNS location. This
directive is typically used to allow hosts controlled by
another organization.
include
spf_oci.taleo.net
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 spf1.unicc.unicc.org
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
64.14.177.128/26
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
193.194.138.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
192.91.247.68
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
192.91.247.70
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
146.247.11.101
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
146.247.11.102
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
195.55.64.65
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
195.55.64.66
Evaluates SPF policy specified in another DNS location. This
directive is typically used to allow hosts controlled by
another organization.
include
spf-unicc.swisscom.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-unicc.swisscom.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
spf.swisscom.com
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
188.92.48.138
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
188.92.48.139
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
188.92.48.140
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
188.92.48.141
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
188.92.48.155
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
188.92.48.167
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.swisscom.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
138.190.12.80/28
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
138.190.12.32/27
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
138.188.176.0/26
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
138.188.176.128/26
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
138.188.166.96/27
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.salesforce.com
SPF version used by this policy.v spf1
This mechanism is used to construct an arbitrary domain name
that is used for a DNS A record query. It allows for complicated
schemes involving arbitrary parts of the mail envelope to determine
what is permitted.
exists
%{i}._spf.mta.salesforce.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_oci.taleo.net
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
147.154.130.198
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
192.29.202.183
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
147.154.235.36
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
147.154.8.204
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
138.1.127.67
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
192.29.14.88
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
147.154.178.139
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
192.29.95.58
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
192.29.221.25
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
192.29.154.249
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
155.248.8.180
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
155.248.24.243

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.

Test passed
Everything seems to be well configured. Well done.

DMARC Policy Information

The location from which we obtained this policy.Policy location _dmarc.who.int
DMARC version used by this policy.v DMARC1
Indicates the policy to be enacted by the receiver at
the request of the domain owner. Possible values are:
none, quarantine, and reject.
p
reject
Percentage of messages from mail stream to
which the DMARC policy is to be applied.
pct
100
Configures failure reporting.fo 1
Interval between aggregate reports. Defaults to 86400.ri 3600
Addresses to which aggregate feedback is to be sent.rua mailto:422b6d07@inbox.ondmarc.com,mailto:dmarc-rua@who.int

Analysis

Info
DMARC policy found

Policy: v=DMARC1; p=reject; pct=100; fo=1; ri=3600; rua=mailto:422b6d07@inbox.ondmarc.com,mailto:dmarc-rua@who.int;

Host: _dmarc.who.int

Good
Valid external destination

Permission record location: who.int._report._dmarc.inbox.ondmarc.com

External destination: mailto:422b6d07@inbox.ondmarc.com

Permission record contents: v=DMARC1;

Good
Policy is valid
Good. You have a valid DMARC policy.

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://who.int/

1
http://who.int/
HTTP/1.1 301 Moved Permanently
2
https://who.int/
HTTP/1.1 301 Moved Permanently
3
https://www.who.int/
HTTP/1.1 200 OK

Analysis

Good
HTTP redirects to HTTPS
Good. This plaintext HTTP server redirects to HTTPS.

URL: http://www.who.int/

1
http://www.who.int/
HTTP/1.1 301 Moved Permanently
2
https://www.who.int/
HTTP/1.1 200 OK

Analysis

Good
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://who.int/

1
https://who.int/
HTTP/1.1 301 Moved Permanently
2
https://www.who.int/
HTTP/1.1 200 OK

URL: https://www.who.int/

1
https://www.who.int/
HTTP/1.1 200 OK

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: who.int (192.133.11.1)

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: AGL_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcc14
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
AGL_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
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_128_CBC_SHA
Suite ID: 0xc009
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
 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)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc00a
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
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 ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc024
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 256 bits)
Suite: AGL_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcc13
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
AGL_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcca8
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0xc02f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0x9c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_GCM_SHA256
 128 bits
Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x2f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_128_CBC_SHA
 128 bits
Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0x9d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA384
TLS_RSA_WITH_AES_256_GCM_SHA384
 256 bits
Suite: TLS_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x35
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0xc027
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0x3c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_CBC_SHA256
 128 bits
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc028
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_256_CBC_SHA256
Suite ID: 0x3d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_256_CBC_SHA256
 256 bits
Signed Certificate
Timestamps
TLS | 26 Mar 2024 08:21:51 UTC | Google 'Xenon2024' log | Qualified
TLS | 26 Mar 2024 08:21:40 UTC | Google 'Xenon2024' log | Qualified
TLS | 26 Mar 2024 08:21:51 UTC | Google 'Argon2024' log | Qualified
TLS | 26 Mar 2024 08:21:40 UTC | Google 'Argon2024' log | Qualified

Analysis

Good
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.
Good
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.
Good
Deprecated protocols not supported
Excellent. This server doesn't support any of the deprecated protocol (TLS 1.1 and earlier).
Good
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.
Good
Server prefers forward secrecy and authenticated encryption suites
Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.
Good
Server enforces cipher suite preferences
Excellent. This server enforces server cipher suite preference, which means that it is able to select the best suite from the options submitted by clients. Combined with a well designed list of supported cipher suites, this settings enables negotiation of best security.
Good
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, TLS

Good
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, TLS

Notice
DHE suites not supported
This server doesn't support the Diffie-Hellman (DH) key exchange.

TLS Configuration: www.who.int (192.133.11.1)

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: AGL_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcc14
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
AGL_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
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_128_CBC_SHA
Suite ID: 0xc009
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
 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)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc00a
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
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 ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc024
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 256 bits)
Suite: AGL_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcc13
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
AGL_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcca8
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0xc02f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0x9c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_GCM_SHA256
 128 bits
Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x2f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_128_CBC_SHA
 128 bits
Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0x9d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA384
TLS_RSA_WITH_AES_256_GCM_SHA384
 256 bits
Suite: TLS_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x35
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0xc027
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0x3c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_CBC_SHA256
 128 bits
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc028
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_256_CBC_SHA256
Suite ID: 0x3d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_256_CBC_SHA256
 256 bits
Signed Certificate
Timestamps
TLS | 26 Mar 2024 08:09:23 UTC | Google 'Xenon2024' log | Qualified
TLS | 26 Mar 2024 08:09:23 UTC | Google 'Argon2024' log | Qualified

Analysis

Good
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.
Good
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.
Good
Deprecated protocols not supported
Excellent. This server doesn't support any of the deprecated protocol (TLS 1.1 and earlier).
Good
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.
Good
Server prefers forward secrecy and authenticated encryption suites
Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.
Good
Server enforces cipher suite preferences
Excellent. This server enforces server cipher suite preference, which means that it is able to select the best suite from the options submitted by clients. Combined with a well designed list of supported cipher suites, this settings enables negotiation of best security.
Good
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, TLS

Good
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, TLS

Notice
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.who.int

Leaf certificate www.who.int
Issuer: Let's Encrypt
Not Before: 26 Mar 2024 07:09:15 UTC
Not After: 24 Jun 2024 07:09:14 UTC (expires in 1 month 5 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
 View details

Analysis

Good
Strong private key
Good. The private key associated with this certificate is secure.
Good
Strong signature algorithm
Good. This certificate uses a strong signature algorithm.
Good
Certificate matches hostname
Good. The provided certificate matches the expected hostnames.
Good
Certificate dates match
Good. The certificate is valid for use at this point of time.
Good
Certificate has not been revoked
Good. This certificate has not been revoked.
Good
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
www.who.int | 30fba0a
Not After: 24 Jun 2024 07:09:14 UTC (expires in 1 month 5 days)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Intermediate certificate
R3 | 67add11
Not After: 15 Sep 2025 16:00:00 UTC (expires in 1 year 3 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Intermediate certificate
ISRG Root X1 | 6d99fb2
Not After: 30 Sep 2024 18:14:03 UTC (expires in 4 months 11 days)
Authentication: RSA 4096 bits (SHA256withRSA)
 View details
Root certificate
DST Root CA X3 | 0687260
Not After: 30 Sep 2021 14:01:15 UTC (expired 2 years 7 months ago)
Authentication: RSA 2048 bits (SHA1withRSA)
 View details

Analysis

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

Certificate: www.who.int

Leaf certificate www.who.int
Issuer: Let's Encrypt
Not Before: 26 Mar 2024 07:09:22 UTC
Not After: 24 Jun 2024 07:09:21 UTC (expires in 1 month 5 days)
Key: EC 256 bits
Signature: SHA384withECDSA
 View details

Analysis

Good
Strong private key
Good. The private key associated with this certificate is secure.
Good
Strong signature algorithm
Good. This certificate uses a strong signature algorithm.
Good
Certificate matches hostname
Good. The provided certificate matches the expected hostnames.
Good
Certificate dates match
Good. The certificate is valid for use at this point of time.
Good
Certificate has not been revoked
Good. This certificate has not been revoked.
Good
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
www.who.int | 4578bc9
Not After: 24 Jun 2024 07:09:21 UTC (expires in 1 month 5 days)
Authentication: EC 256 bits (SHA384withECDSA)
 View details
Intermediate certificate
E1 | 46494e3
Not After: 15 Sep 2025 16:00:00 UTC (expires in 1 year 3 months)
Authentication: EC 384 bits (SHA384withECDSA)
 View details
Intermediate certificate
ISRG Root X2 | 8b05b68
Not After: 15 Sep 2025 16:00:00 UTC (expires in 1 year 3 months)
Authentication: EC 384 bits (SHA256withRSA)
 View details
Intermediate certificate
ISRG Root X1 | 6d99fb2
Not After: 30 Sep 2024 18:14:03 UTC (expires in 4 months 11 days)
Authentication: RSA 4096 bits (SHA256withRSA)
 View details
Root certificate
DST Root CA X3 | 0687260
Not After: 30 Sep 2021 14:01:15 UTC (expired 2 years 7 months ago)
Authentication: RSA 2048 bits (SHA1withRSA)
 View details

Analysis

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

Certificate: who.int

Leaf certificate who.int
Issuer: Let's Encrypt
Not Before: 26 Mar 2024 07:21:50 UTC
Not After: 24 Jun 2024 07:21:49 UTC (expires in 1 month 5 days)
Key: EC 256 bits
Signature: SHA384withECDSA
 View details

Analysis

Good
Strong private key
Good. The private key associated with this certificate is secure.
Good
Strong signature algorithm
Good. This certificate uses a strong signature algorithm.
Good
Certificate matches hostname
Good. The provided certificate matches the expected hostnames.
Good
Certificate dates match
Good. The certificate is valid for use at this point of time.
Good
Certificate has not been revoked
Good. This certificate has not been revoked.
Good
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
who.int | fd04015
Not After: 24 Jun 2024 07:21:49 UTC (expires in 1 month 5 days)
Authentication: EC 256 bits (SHA384withECDSA)
 View details
Intermediate certificate
E1 | 46494e3
Not After: 15 Sep 2025 16:00:00 UTC (expires in 1 year 3 months)
Authentication: EC 384 bits (SHA384withECDSA)
 View details
Intermediate certificate
ISRG Root X2 | 8b05b68
Not After: 15 Sep 2025 16:00:00 UTC (expires in 1 year 3 months)
Authentication: EC 384 bits (SHA256withRSA)
 View details
Intermediate certificate
ISRG Root X1 | 6d99fb2
Not After: 30 Sep 2024 18:14:03 UTC (expires in 4 months 11 days)
Authentication: RSA 4096 bits (SHA256withRSA)
 View details
Root certificate
DST Root CA X3 | 0687260
Not After: 30 Sep 2021 14:01:15 UTC (expired 2 years 7 months ago)
Authentication: RSA 2048 bits (SHA1withRSA)
 View details

Analysis

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

Certificate: who.int

Leaf certificate who.int
Issuer: Let's Encrypt
Not Before: 26 Mar 2024 07:21:39 UTC
Not After: 24 Jun 2024 07:21:38 UTC (expires in 1 month 5 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
 View details

Analysis

Good
Strong private key
Good. The private key associated with this certificate is secure.
Good
Strong signature algorithm
Good. This certificate uses a strong signature algorithm.
Good
Certificate matches hostname
Good. The provided certificate matches the expected hostnames.
Good
Certificate dates match
Good. The certificate is valid for use at this point of time.
Good
Certificate has not been revoked
Good. This certificate has not been revoked.
Good
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
who.int | 0dfcb6e
Not After: 24 Jun 2024 07:21:38 UTC (expires in 1 month 5 days)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Intermediate certificate
R3 | 67add11
Not After: 15 Sep 2025 16:00:00 UTC (expires in 1 year 3 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Intermediate certificate
ISRG Root X1 | 6d99fb2
Not After: 30 Sep 2024 18:14:03 UTC (expires in 4 months 11 days)
Authentication: RSA 4096 bits (SHA256withRSA)
 View details
Root certificate
DST Root CA X3 | 0687260
Not After: 30 Sep 2021 14:01:15 UTC (expired 2 years 7 months ago)
Authentication: RSA 2048 bits (SHA1withRSA)
 View details

Analysis

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

HTTP Cookie: __cfruid

Cookie value. As far as the cookie RFC is concerned, the value
is an opaque string which only the application should interpret.
Value
a1529e839e9edbef48ba83295ec74d8ba0f64b44-1716079208
Cookie domain. When domain is implied (not explicitly set in a cookie),
most browsers (but not IE) treat the cookie as host-only, meaning that
no other server can overwrite it.
Domain
www.who.int
Cookie path. This field can't be used as security measure,
but it could be of use to avoid cookie name collision
in non-adversarial contexts.
Path
/
The HttpOnly flag prevents the cookie from being accessed
from JavaScript, thus making them more difficult
to obtain after a successful XSS attack.
HttpOnly
The Secure flag signals to browsers that the cookie
should be transmitted only over an encrypted channel.
Secure
Normally, when a browser makes a request to a web site,
it sends all associated cookies. This is not always
desirable, because it might allow third-party sites
to perform site actions under the identity of the user.
This attack is known as Cross-Site Request Forgery.
With SameSite cookies (still in development, but already
supported in some browsers), you can choose to be more
strict. The possible values are 'lax' and 'strict'.
SameSite

Analysis

Good
Cookie is secure
Good. This cookie is marked secure, which means that it won't ever be transmitted over plaintext. As such, it's not vulnerable to the Sidejacking attack.

HTTP Cookie: _cfuvid

Cookie value. As far as the cookie RFC is concerned, the value
is an opaque string which only the application should interpret.
Value
SwuKrlqFly.3NRI_ELsK_YF0jqiLUoKyuiWVozK_0dY-1716079208182-0.0.1.1-604800000
Cookie domain. When domain is implied (not explicitly set in a cookie),
most browsers (but not IE) treat the cookie as host-only, meaning that
no other server can overwrite it.
Domain
www.who.int
Cookie path. This field can't be used as security measure,
but it could be of use to avoid cookie name collision
in non-adversarial contexts.
Path
/
The HttpOnly flag prevents the cookie from being accessed
from JavaScript, thus making them more difficult
to obtain after a successful XSS attack.
HttpOnly
The Secure flag signals to browsers that the cookie
should be transmitted only over an encrypted channel.
Secure
Normally, when a browser makes a request to a web site,
it sends all associated cookies. This is not always
desirable, because it might allow third-party sites
to perform site actions under the identity of the user.
This attack is known as Cross-Site Request Forgery.
With SameSite cookies (still in development, but already
supported in some browsers), you can choose to be more
strict. The possible values are 'lax' and 'strict'.
SameSite

Analysis

Good
Cookie is secure
Good. This cookie is marked secure, which means that it won't ever be transmitted over plaintext. As such, it's not vulnerable to the Sidejacking attack.

Analysis

Good
All cookies are secure
Great. All observed cookies are marked secure.

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.

3 script(s)
  3 out of 3 are secure  View all
6 CSS file(s)
  6 out of 6 are secure  View all
5 media file(s)
  5 out of 5 are secure  View all

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.

3 link(s)
  2 out of 3 are encrypted
http://www.emro.who.int/index.html
 View all

Analysis

Warning
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.who.int/
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

Good
Policy is valid
OK. Your HSTS policy uses correct syntax.
Good
Long policy age
Your HSTS policy has a long max-age value, which offers better protection.
Warning
No subdomains
This HSTS policy doesn't cover subdomains, which is a requirement for preloading. Additionally, without full coverage, HSTS can't protect from certain cookie attacks that typically allow active network attackers to inject cookies into an application.
Good
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.
Powerup!
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://who.int/
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

Good
Policy is valid
OK. Your HSTS policy uses correct syntax.
Good
Long policy age
Your HSTS policy has a long max-age value, which offers better protection.
Warning
No subdomains
This HSTS policy doesn't cover subdomains, which is a requirement for preloading. Additionally, without full coverage, HSTS can't protect from certain cookie attacks that typically allow active network attackers to inject cookies into an application.
Good
Preload intent declared
Good. With the preload directive set, browsers have a green light to embed the HSTS policy.
Good
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.
Warning
Policy not preloaded
When hostname is preloaded, that means that browsers embed your HSTS policy and apply it even to the first request sent to your web site. This server indicates preloading in its policy, but the domain name isn't actually preloaded. We classify this as a warning because it's a common problem to place the 'preload' keyword in the policy even though the infrastructure is not ready for preloading. This is dangerous because, in this situation, anyone can submit this domain name for preloading just by visiting hstspreload.org. We recommend that you either preload this domain name yourself—if it's ready—or remove the preloading indicator from the policy until it is ready.
Warning
Preload policy doesn't satisfy preload requirements
This HSTS policy specifies the preload directive but doesn't satisfy one or more preload conditions.

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

default-src 'self'   *.analysis.windows.net   *.clarity.ms   *.nativechat.com   *.tts.speech.microsoft.com   *.who.int   *.who.cloud.sitefinity.com   answers.yext-pixel.com   app.powerbi.com   assets.sitescdn.net   content.powerapps.com   covidfunding.eiu.com   dc.services.visualstudio.com   gis.azureedge.net   js.arcgis.com   liveapi.yext.com   liveapi-cached.yext.com   pbi.azureedge.net   pbipdfapp.azurewebsites.net   player.4am.ch   player.clevercast.com   polyfill.io   services.arcgis.com   staging-dot-eiu-wellcome-7664.nw.r.appspot.com   tiles.arcgis.com   utility.arcgisonline.com   visuals.azureedge.net   wabi-north-europe-redirect.analysis.windows.net   westeurope.tts.speech.microsoft.com   who.cloudflareaccess.com   who-answers.pagescdn.com   who-covid-answers.int.pagescdn.com   whotest.appiancloud.com   www.arcgis.com   www.googleadservices.com   iris.who.int  
script-src 'self'   *.googleapis.com   *.gstatic.com   www.google.com   apis.google.com   connect.facebook.net   ajax.aspnetcdn.com   https://www.youtube.com   platform.twitter.com   https://syndication.twitter.com/   https://s.ytimg.com   https://publish.twitter.com   *.twimg.com   platform.linkedin.com   http://platform.stumbleupon.com/1/widgets.js   https://*.googletagmanager.com   https://app-script.monsido.com/v2/monsido-script.js   https://heatmaps.monsido.com/   https://tracking.monsido.com/   https://pagecorrect.monsido.com/v1/page-correct.js   https://cdn.monsido.com/   This parameter shouldn't be used because it reenables
insecure behavior that CSP disables by default.
'unsafe-eval'
  This parameter shouldn't be used because it reenables
insecure behavior that CSP disables by default.
'unsafe-inline'
  data:   apps.who.int/gho/athena/data/   *.clarity.ms   *.doubleclick.net   *.eloqua.com   *.en25.com   *.google-analytics.com   *.googletagmanager.com   *.jwpcdn.com   *.msecnd.net   *.nativechat.com   *.pingdom.net   *.sharethis.com   assets.pinterest.com   assets.sitescdn.net   cdn.ampproject.org   cdn.insight.sitefinity.com   cdn.jsdelivr.net   cdnjs.cloudflare.com   covidfunding.eiu.com   https://dec.azureedge.net/   https://www.youtube.com/iframe_api   js.arcgis.com   js.hs-analytics.net   js.hs-scripts.com   kendo.cdn.telerik.com   munchkin.marketo.net   npmcdn.com   polyfill.io   public.tableau.com   services.arcgis.com   staging-dot-eiu-wellcome-7664.nw.r.appspot.com   storage.googleapis.com   tagmanager.google.com   tiles.arcgis.com   utility.arcgisonline.com   who-answers.pagescdn.com   who-covid-answers.int.pagescdn.com   whosearch.searchblox.com   www.arcgis.com   www.clarity.ms   www.googletagmanager.com   www.who.int   www.youtube.com   youtu.be   app-script.monsido.com   https://cdn.insight.sitefinity.com   https://dec.azureedge.net   js.hs-banner.com   js.hsleadflows.net   forms.hubspot.com   js.hscollectedforms.net   web-chat.nativechat.com  
style-src 'self'   *.googleapis.com   *.gstatic.com   netdna.bootstrapcdn.com   kendo.cdn.telerik.com   www.google.com   platform.twitter.com/css/   *.twimg.com   This parameter shouldn't be used because it reenables
insecure behavior that CSP disables by default.
'unsafe-inline'
  tiles.arcgis.com   www.arcgis.com   services.arcgis.com   utility.arcgisonline.com   js.arcgis.com   *.nativechat.com   *.sharethis.com   cdn.insight.sitefinity.com   cdnjs.cloudflare.com   https://dec.azureedge.net   use.fontawesome.com   www.who.int   player.4am.ch   player.clevercast.com   whosearch.searchblox.com   tagmanager.google.com   blob:   https://cdn.insight.sitefinity.com   web-chat.nativechat.com  
img-src 'self'   *.gstatic.com   *.googleapis.com   platform.tumblr.com   web.facebook.com   www.facebook.com   www.redditstatic.com   www.linkedin.com   i.ytimg.com   https://syndication.twitter.com   https://static.licdn.com/scds/common/u/images/apps/connect/sprites/sprite_connect_v14.png   pbs.twimg.com   platform.twitter.com/css/   *.twimg.com   data:   blob:   https://*.googletagmanager.com   tracking.monsido.com   iris.who.int   tiles.arcgis.com   www.arcgis.com   services.arcgis.com   utility.arcgisonline.com   cdn.insight.sitefinity.com   js.arcgis.com   *.nativechat.com   *.sharethis.com   *.google-analytics.com   *.clarity.ms   https://delicious.com   https://dec.azureedge.net   https://apps.who.int   https://*.dec.sitefinity.com   *.eloqua.com   track.hubspot.com   stats.g.doubleclick.net   *.who.int   *.who.cloud.sitefinity.com   yt3.ggpht.com   addthis.com   *.googleusercontent.com   *.googletagmanager.com   script.hotjar.com   www.addthis.com   log.pinterest.com   whosearch.searchblox.com   app.powerbi.com   pbi.azureedge.net   kendo.cdn.telerik.com   img.youtube.com   *.analytics.google.com   *.g.doubleclick.net   *.google.com   https://cdn.insight.sitefinity.com   js.hsleadflows.net   forms.hsforms.com   web-chat.nativechat.com  
font-src 'self'   fonts.gstatic.com   kendo.cdn.telerik.com   netdna.bootstrapcdn.com   data:   tiles.arcgis.com   www.arcgis.com   services.arcgis.com   utility.arcgisonline.com   js.arcgis.com   *.nativechat.com   *.sharethis.com   use.fontawesome.com   www.who.int   player.4am.ch   player.clevercast.com   whosearch.searchblox.com   script.hotjar.com   app.powerbi.com   pbi.azureedge.net   *.clarity.ms   cdn.jsdelivr.net  
frame-src 'self'   *.kunstmatrix.com   *.doubleclick.net   *.nativechat.com   *.sitefinity.cloud   *.who.int   *.who.cloud.sitefinity.com   app.powerbi.com   app.sli.do   apps.who.int   assets.pinterest.com   covidfunding.eiu.com   creativecommons.org   experience.arcgis.com   html5-player.libsyn.com   js.arcgis.com   pbi.azureedge.net   platform.twitter.com   player.4am.ch   player.clevercast.com   player.vimeo.com   vimeo.com   public.tableau.com   services.arcgis.com   staging-dot-eiu-wellcome-7664.nw.r.appspot.com   syndication.twitter.com   tiles.arcgis.com   utility.arcgisonline.com   wabi-north-europe-g-primary-redirect.analysis.windows.net   who.maps.arcgis.com   who-answers.pagescdn.com   who-covid-answers.int.pagescdn.com   whotest.appiancloud.com   www.arcgis.com   www.facebook.com   www.youtube.com   www.youtube-nocookie.com   youtube-nocookie.com   https://app.powerbi.com/   appianportals.com   forms.hsforms.com   web-chat.nativechat.com  
connect-src 'self'   data:   accounts.google.com   *.gstatic.com   https://*.googletagmanager.com   whpelasticdsta01.blob.core.windows.net   whpelasticpsta01.blob.core.windows.net   heatmaps.monsido.com   tracking.monsido.com   frontdoor-l4uikgap6gz3m.azurefd.net   whotest.appiancloud.com   geocode.arcgis.com   tiles.arcgis.com   www.arcgis.com   services.arcgis.com   static.arcgis.com   utility.arcgisonline.com   js.arcgis.com   cdn.jsdelivr.net   stats.g.doubleclick.net   https://*.dec.sitefinity.com   *.nativechat.com   *.mktoresp.com   *.who.int   *.who.cloud.sitefinity.com   *.clarity.ms   dc.services.visualstudio.com   whosearch.searchblox.com   *.google-analytics.com   smartsuggest.searchblox.com   m.addthis.com   liveapi-cached.yext.com   liveapi.yext.com   answers.yext-pixel.com   wss://westeurope.tts.speech.microsoft.com   in.hotjar.com   wss://*.hotjar.com   *.hotjar.com   vc.hotjar.io   app.powerbi.com   pbi.azureedge.net   pbipdfapp.azurewebsites.net   wabi-north-europe-redirect.analysis.windows.net   *.analytics.google.com   *.googletagmanager.com   *.g.doubleclick.net   *.google.com   https://*.insight.sitefinity.com   forms.hubspot.com   *.hsforms.com  
media-src 'self'   data:   blob:   tiles.arcgis.com   www.arcgis.com   services.arcgis.com   utility.arcgisonline.com   js.arcgis.com   terrance.who.int   *.who.int   *.who.cloud.sitefinity.com  
child-src 'self'   https://platform.twitter.com/   https://syndication.twitter.com/   https://www.youtube.com/   https://www.youtube-nocookie.com   https://player.vimeo.com/   https://w.soundcloud.com/   apis.google.com   accounts.google.com   staticxx.facebook.com   www.facebook.com   web.facebook.com   badge.stumbleupon.com   blob:   tiles.arcgis.com   www.arcgis.com   apps.who.int/gho/athena/data/   services.arcgis.com   utility.arcgisonline.com   js.arcgis.com   *.nativechat.com   https://vimeo.com   www.who.int   web-chat.nativechat.com  
frame-ancestors tiles.arcgis.com   www.arcgis.com   services.arcgis.com   utility.arcgisonline.com   js.arcgis.com   app.powerbi.com   pbi.azureedge.net   *.who.int   *.who.cloud.sitefinity.com   appianportals.com   'self'  
object-src tiles.arcgis.com   www.arcgis.com   services.arcgis.com   utility.arcgisonline.com   js.arcgis.com   app.powerbi.com   pbi.azureedge.net   pbipdfapp.azurewebsites.net   wabi-north-europe-redirect.analysis.windows.net   'self'  

Analysis

Powerup!
Inline scripts are allowed
By default, CSP doesn't allow inline script execution, but this policy overrides that behavior by specifying 'unsafe-inline' in the 'script-src' directive. As a result, all XSS defenses provided by CSP are significantly weakened.
Powerup!
Inline styles are allowed
This policy allows inline styles. Although they are not as bad as inline scripts in terms of security, an injection bug in script area would allow the attacker to modify page appearance.
Powerup!
Dynamic code execution is allowed
By default, CSP doesn't allow dynamic script execution via eval and friends, but this policy overrides that behavior by specifyin 'unsafe-eval' in the 'script-src' directive. As a result, XSS defenses provided by CSP are significantly weakened.
Powerup!
Mixed content not blocked
This CSP policy doesn't use any of the directives designed to handle mixed content. Consider using the 'block-all-mixed-content' and 'upgrade-insecure-requests' directives as appropriate to ensure that no mixed content is allowed.
Powerup!
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

Info
CSP policy detected

Header: Content-Security-Policy

Value: default-src 'self' *.analysis.windows.net *.clarity.ms *.nativechat.com *.tts.speech.microsoft.com *.who.int *.who.cloud.sitefinity.com answers.yext-pixel.com app.powerbi.com assets.sitescdn.net content.powerapps.com covidfunding.eiu.com dc.services.visualstudio.com gis.azureedge.net js.arcgis.com liveapi.yext.com liveapi-cached.yext.com pbi.azureedge.net pbipdfapp.azurewebsites.net player.4am.ch player.clevercast.com polyfill.io services.arcgis.com staging-dot-eiu-wellcome-7664.nw.r.appspot.com tiles.arcgis.com utility.arcgisonline.com visuals.azureedge.net wabi-north-europe-redirect.analysis.windows.net westeurope.tts.speech.microsoft.com who.cloudflareaccess.com who-answers.pagescdn.com who-covid-answers.int.pagescdn.com whotest.appiancloud.com www.arcgis.com www.googleadservices.com iris.who.int; script-src 'self' *.googleapis.com *.gstatic.com www.google.com apis.google.com connect.facebook.net ajax.aspnetcdn.com https://www.youtube.com platform.twitter.com https://syndication.twitter.com/ https://s.ytimg.com https://publish.twitter.com *.twimg.com platform.linkedin.com http://platform.stumbleupon.com/1/widgets.js https://*.googletagmanager.com https://app-script.monsido.com/v2/monsido-script.js https://heatmaps.monsido.com/ https://tracking.monsido.com/ https://pagecorrect.monsido.com/v1/page-correct.js https://cdn.monsido.com/ 'unsafe-eval' 'unsafe-inline' data: apps.who.int/gho/athena/data/ *.clarity.ms *.doubleclick.net *.eloqua.com *.en25.com *.google-analytics.com *.googletagmanager.com *.jwpcdn.com *.msecnd.net *.nativechat.com *.pingdom.net *.sharethis.com assets.pinterest.com assets.sitescdn.net cdn.ampproject.org cdn.insight.sitefinity.com cdn.jsdelivr.net cdnjs.cloudflare.com covidfunding.eiu.com https://dec.azureedge.net/ https://www.youtube.com/iframe_api js.arcgis.com js.hs-analytics.net js.hs-scripts.com kendo.cdn.telerik.com munchkin.marketo.net npmcdn.com polyfill.io public.tableau.com services.arcgis.com staging-dot-eiu-wellcome-7664.nw.r.appspot.com storage.googleapis.com tagmanager.google.com tiles.arcgis.com utility.arcgisonline.com who-answers.pagescdn.com who-covid-answers.int.pagescdn.com whosearch.searchblox.com www.arcgis.com www.clarity.ms www.googletagmanager.com www.who.int www.youtube.com youtu.be app-script.monsido.com https://cdn.insight.sitefinity.com https://dec.azureedge.net js.hs-banner.com js.hsleadflows.net forms.hubspot.com js.hscollectedforms.net web-chat.nativechat.com; style-src 'self' *.googleapis.com *.gstatic.com netdna.bootstrapcdn.com kendo.cdn.telerik.com www.google.com platform.twitter.com/css/ *.twimg.com 'unsafe-inline' tiles.arcgis.com www.arcgis.com services.arcgis.com utility.arcgisonline.com js.arcgis.com *.nativechat.com *.sharethis.com cdn.insight.sitefinity.com cdnjs.cloudflare.com https://dec.azureedge.net use.fontawesome.com www.who.int player.4am.ch player.clevercast.com whosearch.searchblox.com tagmanager.google.com blob: https://cdn.insight.sitefinity.com web-chat.nativechat.com; img-src 'self' *.gstatic.com *.googleapis.com platform.tumblr.com web.facebook.com www.facebook.com www.redditstatic.com www.linkedin.com i.ytimg.com https://syndication.twitter.com https://static.licdn.com/scds/common/u/images/apps/connect/sprites/sprite_connect_v14.png pbs.twimg.com platform.twitter.com/css/ *.twimg.com data: blob: https://*.googletagmanager.com tracking.monsido.com iris.who.int tiles.arcgis.com www.arcgis.com services.arcgis.com utility.arcgisonline.com cdn.insight.sitefinity.com js.arcgis.com *.nativechat.com *.sharethis.com *.google-analytics.com *.clarity.ms https://delicious.com https://dec.azureedge.net https://apps.who.int https://*.dec.sitefinity.com *.eloqua.com track.hubspot.com stats.g.doubleclick.net *.who.int *.who.cloud.sitefinity.com yt3.ggpht.com addthis.com *.googleusercontent.com *.googletagmanager.com script.hotjar.com www.addthis.com log.pinterest.com whosearch.searchblox.com app.powerbi.com pbi.azureedge.net kendo.cdn.telerik.com img.youtube.com *.analytics.google.com *.g.doubleclick.net *.google.com https://cdn.insight.sitefinity.com js.hsleadflows.net forms.hsforms.com web-chat.nativechat.com; font-src 'self' fonts.gstatic.com kendo.cdn.telerik.com netdna.bootstrapcdn.com data: tiles.arcgis.com www.arcgis.com services.arcgis.com utility.arcgisonline.com js.arcgis.com *.nativechat.com *.sharethis.com use.fontawesome.com www.who.int player.4am.ch player.clevercast.com whosearch.searchblox.com script.hotjar.com app.powerbi.com pbi.azureedge.net *.clarity.ms cdn.jsdelivr.net; frame-src 'self' *.kunstmatrix.com *.doubleclick.net *.nativechat.com *.sitefinity.cloud *.who.int *.who.cloud.sitefinity.com app.powerbi.com app.sli.do apps.who.int assets.pinterest.com covidfunding.eiu.com creativecommons.org experience.arcgis.com html5-player.libsyn.com js.arcgis.com pbi.azureedge.net platform.twitter.com player.4am.ch player.clevercast.com player.vimeo.com vimeo.com public.tableau.com services.arcgis.com staging-dot-eiu-wellcome-7664.nw.r.appspot.com syndication.twitter.com tiles.arcgis.com utility.arcgisonline.com wabi-north-europe-g-primary-redirect.analysis.windows.net who.maps.arcgis.com who-answers.pagescdn.com who-covid-answers.int.pagescdn.com whotest.appiancloud.com www.arcgis.com www.facebook.com www.youtube.com www.youtube-nocookie.com youtube-nocookie.com https://app.powerbi.com/ appianportals.com forms.hsforms.com web-chat.nativechat.com; connect-src 'self' data: accounts.google.com *.gstatic.com https://*.googletagmanager.com whpelasticdsta01.blob.core.windows.net whpelasticpsta01.blob.core.windows.net heatmaps.monsido.com tracking.monsido.com frontdoor-l4uikgap6gz3m.azurefd.net whotest.appiancloud.com geocode.arcgis.com tiles.arcgis.com www.arcgis.com services.arcgis.com static.arcgis.com utility.arcgisonline.com js.arcgis.com cdn.jsdelivr.net stats.g.doubleclick.net https://*.dec.sitefinity.com *.nativechat.com *.mktoresp.com *.who.int *.who.cloud.sitefinity.com *.clarity.ms dc.services.visualstudio.com whosearch.searchblox.com *.google-analytics.com smartsuggest.searchblox.com m.addthis.com liveapi-cached.yext.com liveapi.yext.com answers.yext-pixel.com wss://westeurope.tts.speech.microsoft.com in.hotjar.com wss://*.hotjar.com *.hotjar.com vc.hotjar.io app.powerbi.com pbi.azureedge.net pbipdfapp.azurewebsites.net wabi-north-europe-redirect.analysis.windows.net *.analytics.google.com *.googletagmanager.com *.g.doubleclick.net *.google.com https://*.insight.sitefinity.com forms.hubspot.com *.hsforms.com; media-src 'self' data: blob: tiles.arcgis.com www.arcgis.com services.arcgis.com utility.arcgisonline.com js.arcgis.com terrance.who.int *.who.int *.who.cloud.sitefinity.com; child-src 'self' https://platform.twitter.com/ https://syndication.twitter.com/ https://www.youtube.com/ https://www.youtube-nocookie.com https://player.vimeo.com/ https://w.soundcloud.com/ apis.google.com accounts.google.com staticxx.facebook.com www.facebook.com web.facebook.com badge.stumbleupon.com blob: tiles.arcgis.com www.arcgis.com apps.who.int/gho/athena/data/ services.arcgis.com utility.arcgisonline.com js.arcgis.com *.nativechat.com https://vimeo.com www.who.int web-chat.nativechat.com; frame-ancestors tiles.arcgis.com www.arcgis.com services.arcgis.com utility.arcgisonline.com js.arcgis.com app.powerbi.com pbi.azureedge.net *.who.int *.who.cloud.sitefinity.com appianportals.com 'self'; object-src tiles.arcgis.com www.arcgis.com services.arcgis.com utility.arcgisonline.com js.arcgis.com app.powerbi.com pbi.azureedge.net pbipdfapp.azurewebsites.net wabi-north-europe-redirect.analysis.windows.net 'self'

Location: https://www.who.int/

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.
3 script(s)
  3 out of 3 are secure  View all
6 CSS file(s)
  4 out of 6 are secure
https://fonts.googleapis.com/css2
https://use.fontawesome.com/.../v5.15.4/css/all.css
 View all

Analysis

Powerup!
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

Powerup!
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

Info
Header information

Name: X-Frame-Options

Value: SAMEORIGIN

Good
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, but there are warnings
Some aspect of your site's configuration require your attention.

Analysis

Info
Header information

Name: X-XSS-Protection

Value: 1; mode=block

Warning
XSS auditor blocking is dangerous
Your configuration requests blocking when XSS attacks are detected, which is potentially dangerous as it allows attackers to selectively disable portions of JavaScript code. The only safe approach is to explicitly disable browser-based XSS protection.

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

Info
Header information

Name: X-Content-Type-Options

Value: nosniff

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