Hardenize has joined Red Sift! Find out more in our blog post.
Hardenize Logo

Public Report | selea.se

TEST ANOTHER

selea.se

27 Oct 2024 21:45 UTC

Domain Name System

Domain Registrationgood
DNS Zonegood
DNS Recordsgood
DNSSECneutral
CAAgood

Email

Mail serverserror
TLSerror
Certificateswarning
MTA-STSneutral
TLS-RPTgood
DANEneutral
SPFgood
DMARCgood

WWW

HTTP (80)error
HTTPS (443)good
TLSerror
Certificatesgood
Cookiesgood
HTML Contentgood
Strict Transport Securitywarning
Content Security Policyneutral
Subresource Integritygood
Frame Optionsgood
XSS Protectionneutral
Content Type Optionsgood
Web Security Overview
Error
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
Not supported
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
Not supported
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
Error
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.
There are issues with this site's SMTP configuration.

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
Everything seems to be well configured. Well done.

Registration Data Access Protocol (RDAP)

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

Not available: RDAP service not available

WHOIS

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

Parsed Raw Data Model
Registrant -
Lookup Time 27 Oct 2024 21:43 UTC
Registrar
Registrar Loopia AB
Events
Registration 15 Nov 2014 00:00 UTC
Update 16 Feb 2024 00:00 UTC
Expiration 15 Nov 2024 00:00 UTC
Configuration
Statuses ok
Registrar Lock -
Registry Lock -
Nameservers ben.ns.cloudflare.com
199.27.135.11
abby.ns.cloudflare.com
199.27.134.11
Contacts
Registrar Loopia AB
Loopia AB




Email:
Phone:
Fax:

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
abby.ns.cloudflare.com. PRIMARY
108.162.192.100
172.64.32.100
173.245.58.100
2606:4700:50::adf5:3a64
2803:f800:50::6ca2:c064
2a06:98c1:50::ac40:2064 		The server is online. Name resolves to an IPv4 address. Name resolves to an IPv6 address. SOA REFERRAL NS
ben.ns.cloudflare.com.
108.162.193.103
172.64.33.103
173.245.59.103
2606:4700:58::adf5:3b67
2803:f800:50::6ca2:c167
2a06:98c1:50::ac40:2167 		The server is online. Name resolves to an IPv4 address. Name resolves 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
108.162.192.100 PRIMARY
abby.ns.cloudflare.com.
PTR: abby.ns.cloudflare.com. 		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
108.162.193.103
ben.ns.cloudflare.com.
PTR: ben.ns.cloudflare.com. 		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
172.64.32.100 PRIMARY
abby.ns.cloudflare.com.
PTR: abby.ns.cloudflare.com. 		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
172.64.33.103
ben.ns.cloudflare.com.
PTR: ben.ns.cloudflare.com. 		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
173.245.58.100 PRIMARY
abby.ns.cloudflare.com.
PTR: abby.ns.cloudflare.com. 		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
173.245.59.103
ben.ns.cloudflare.com.
PTR: ben.ns.cloudflare.com. 		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
2606:4700:50::adf5:3a64 PRIMARY
abby.ns.cloudflare.com.
PTR: abby.ns.cloudflare.com. 		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
2606:4700:58::adf5:3b67
ben.ns.cloudflare.com.
PTR: ben.ns.cloudflare.com. 		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
2803:f800:50::6ca2:c064 PRIMARY
abby.ns.cloudflare.com.
PTR: abby.ns.cloudflare.com. 		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
2803:f800:50::6ca2:c167
ben.ns.cloudflare.com.
PTR: ben.ns.cloudflare.com. 		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
2a06:98c1:50::ac40:2064 PRIMARY
abby.ns.cloudflare.com.
PTR: abby.ns.cloudflare.com. 		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
2a06:98c1:50::ac40:2167
ben.ns.cloudflare.com.
PTR: ben.ns.cloudflare.com. 		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 abby.ns.cloudflare.com.
Email address of the persons responsible for this zone. Also known as RNAME.Admin email dns.cloudflare.com.
Zone serial or version number.Serial number -1940019682
The length of time secondary nameservers should wait before querying the primary for changes.Refresh interval 10,000 seconds (about 2 hours 46 minutes)
The length of time secondary nameservers should wait before querying an unresponsive primary again.Retry interval 2,400 seconds (about 40 minutes)
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 1,800 seconds (about 30 minutes)
Time To Live (TTL) indicates for how long a record remains valid. SOA record TTL 1,800 seconds (about 30 minutes)

Analysis

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
Everything seems to be well configured. Well done.

DNS Records

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

Name TTL Type Data
selea.se.     300 A 54.37.233.253            
selea.se.     300 A 54.37.235.108            
selea.se.     300 A 54.37.234.237            
www.selea.se.     300 CNAME home.selea.tech.            
home.selea.tech.     300 A 92.33.194.250            
selea.se.     300 AAAA 2001:41d0:601:1100:0:0:0:3a27            
selea.se.     300 AAAA 2001:41d0:601:1100:0:0:0:4118            
selea.se.     300 CAA 0 issuewild "comodoca.com"            
selea.se.     300 CAA 0 iodef "mailto:admin@selea.se"            
selea.se.     300 CAA 0 issue "ssl.com"            
selea.se.     300 CAA 0 issuewild "letsencrypt.org"            
selea.se.     300 CAA 0 issue "comodoca.com"            
selea.se.     300 CAA 0 issuewild "ssl.com"            
selea.se.     300 CAA 0 issue "digicert.com; cansignhttpexchanges=yes"            
selea.se.     300 CAA 0 issuewild "pki.goog; cansignhttpexchanges=yes"            
selea.se.     300 CAA 0 issuewild "digicert.com; cansignhttpexchanges=yes"            
selea.se.     300 CAA 0 issue "letsencrypt.org"            
selea.se.     300 CAA 0 issue "rapidssl.com"            
selea.se.     300 CAA 0 issue "pki.goog; cansignhttpexchanges=yes"            
selea.se.     300 MX 20 mx.portsit.se.            
selea.se.     300 MX 20 mx.portsit.com.            
selea.se.     300 MX 0 mx1.selea.se.            
selea.se.     86400 NS abby.ns.cloudflare.com.            
selea.se.     86400 NS ben.ns.cloudflare.com.            
selea.se.     1800 SOA abby.ns.cloudflare.com. dns.cloudflare.com. 2354947614 10000 2400 604800 1800            
selea.se.     300 TXT "pybt6s039d69x0076l75xf4vm3p869gn"            
selea.se.     300 TXT "brave-ledger-verification=61961becd4a0a26ae03beecfecd849a5bf9c233291e79af7faf0fa2e9b624643"            
selea.se.     300 TXT "v=spf1 a mx include:relay.selea.se include:spf.ports.email include:spf.portsgroup.com ~all"            
selea.se.     300 TXT "abuseipdb-verification=wA2x8VjA"            
selea.se.     300 TXT "google-site-verification=gVvB1CWrc52N3ZyBY_zMc8TnOOd9JS1lmrJAAZGJaYo"            
_dmarc.selea.se.     300 TXT "v=DMARC1;p=quarantine;adkim=r;aspf=r;rua=mailto:92b4e5f335ae448481e8d213a31f24ad@dmarc-reports.cloudflare.net,mailto:dmarc@selea.se;ruf=mailto:dmarc@selea.se"            
_smtp._tls.selea.se.     3600 TXT "v=TLSRPTv1; rua=mailto:tlsrpt@selease.uriports.com,mailto:reports@selea.se"            

Backing DNS Queries

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

ID Server Question Name Type Status

DNSSEC

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

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

Useful DNSSEC Tools

Certification Authority Authorization

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

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

CAA Policy Information

The DNS hostname where this policy is located.Policy host selea.se
The issue property tag is used to request that certificate
issuers perform CAA issue restriction processing for the domain
and to grant authorization to specific certificate issuers.issue 		comodoca.com  flags: 0
The issue property tag is used to request that certificate
issuers perform CAA issue restriction processing for the domain
and to grant authorization to specific certificate issuers.issue 		rapidssl.com  flags: 0
The issue property tag is used to request that certificate
issuers perform CAA issue restriction processing for the domain
and to grant authorization to specific certificate issuers.issue 		letsencrypt.org  flags: 0
The issuewild property has the same syntax and semantics as
the issue property except that issuewild properties only grant
authorization to issue certificates that specify a wildcard domain
and issuewild properties take precedence over issue properties when
specified.issuewild 		letsencrypt.org  flags: 0
The issuewild property has the same syntax and semantics as
the issue property except that issuewild properties only grant
authorization to issue certificates that specify a wildcard domain
and issuewild properties take precedence over issue properties when
specified.issuewild 		ssl.com  flags: 0
The issue property tag is used to request that certificate
issuers perform CAA issue restriction processing for the domain
and to grant authorization to specific certificate issuers.issue 		digicert.com; cansignhttpexchanges=yes  flags: 0
The issue property tag is used to request that certificate
issuers perform CAA issue restriction processing for the domain
and to grant authorization to specific certificate issuers.issue 		ssl.com  flags: 0
The issuewild property has the same syntax and semantics as
the issue property except that issuewild properties only grant
authorization to issue certificates that specify a wildcard domain
and issuewild properties take precedence over issue properties when
specified.issuewild 		pki.goog; cansignhttpexchanges=yes  flags: 0
The issue property tag is used to request that certificate
issuers perform CAA issue restriction processing for the domain
and to grant authorization to specific certificate issuers.issue 		pki.goog; cansignhttpexchanges=yes  flags: 0
The iodef property specifies a means of reporting certificate
issue requests or cases of certificate issue for the corresponding
domain that violate the security policy of the issuer or the domain
name holder.iodef 		mailto:admin@selea.se  flags: 0
The issuewild property has the same syntax and semantics as
the issue property except that issuewild properties only grant
authorization to issue certificates that specify a wildcard domain
and issuewild properties take precedence over issue properties when
specified.issuewild 		digicert.com; cansignhttpexchanges=yes  flags: 0
The issuewild property has the same syntax and semantics as
the issue property except that issuewild properties only grant
authorization to issue certificates that specify a wildcard domain
and issuewild properties take precedence over issue properties when
specified.issuewild 		comodoca.com  flags: 0

Analysis

Powerup!
Issuance of S/MIME certificates not restricted
This policy doesn't restrict the issuance of S/MIME certificates. Consider using the `issuemail` directive to restrict which CAs, if any, can issue.
Powerup!
Issuance of BIMI not restricted
This policy doesn't restrict issuance of BIMI certificates. Consider using the `issuevmc` directive to restrict which CAs, if any, can issue.
Good
CAA policy restricts issuance
Great. This domain name uses CAA to restrict which CAs are allowed to issue certificates for it.
Good
Policy uses reporting
Good. This policy uses reporting, which means that your contact information is available should someone need to contact you about a CAA violation. Do note that you're not guaranteed to be notified, given that CAs generally don't support notifications yet.

Email (SMTP)

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

Test failed
We've detected serious problems that require your immediate attention.
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
mx1.selea.se
2001:41d0:701:1100:0:0:0:5ff0
PTR: mx1.selea.se		 0 Error: Connect timed out Unable to determine without a
successful SMTP connection. 		Not applicable,
requires STARTTLS. 		Not applicable,
requires TLS. 		Not supported. Not applicable,
requires TLS.
mx1.selea.se
54.38.158.213
PTR: mx1.selea.se		 0 
220-mx1.selea.se ESMTP Postfix
220 mx1.selea.se ESMTP Postfix

EHLO outbound.hardenize.com
250-mx1.selea.se
250-PIPELINING
250-SIZE 15728640
250-ETRN
250-STARTTLS
250-ENHANCEDSTATUSCODES
250-8BITMIME
250-DSN
250-SMTPUTF8
250 CHUNKING

STARTTLS
220 2.0.0 Ready to start TLS
Supports STARTTLS. Not supported. Not applicable,
requires TLS.
mx.portsit.se
193.14.90.100
PTR: mx.portsit.se		 20 Error: Connect timed out Unable to determine without a
successful SMTP connection. 		Not applicable,
requires STARTTLS. 		Not applicable,
requires TLS. 		Not supported. Not applicable,
requires TLS.
mx.portsit.com
94.237.29.21
PTR: mx.portsit.com		 20 
220 mx.portsit.com ESMTP

EHLO outbound.hardenize.com
250-mx.portsit.com
250-PIPELINING
250-SIZE 104857600
250-STARTTLS
250-ENHANCEDSTATUSCODES
250 8BITMIME

STARTTLS
220 2.0.0 Ready to start TLS
Supports STARTTLS. Not applicable,
requires TLS.

Analysis

Error
Network Error
A network error occurred while we were trying to communicate with a server.

Address: 2001:41d0:701:1100::5ff0

Error message: Connect timed out

Host: mx1.selea.se

Error
Network Error
A network error occurred while we were trying to communicate with a server.

Address: 193.14.90.100

Error message: Connect timed out

Host: mx.portsit.se

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: 22 Oct 2024 21:36 UTC

Earliest cache timestamp: 21 Oct 2024 10:04 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 failed
We've detected serious problems that require your immediate attention.
Some TLS and PKI information shown may have been retrieved from cache. The notes provide more information.

TLS Configuration: mx1.selea.se (54.38.158.213) 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_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)
These results have been retrieved from
our cache. This row indicates when was
that the original test ran.Retrieved from cache 		22 Oct 2024 21:36 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: mx.portsit.com (94.237.29.21) 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 secp256r1 (256 bits)
Forward secrecy: Yes
PRF: SHA384
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384  256 bits (ECDHE 256 bits)
These results have been retrieved from
our cache. This row indicates when was
that the original test ran.Retrieved from cache 		21 Oct 2024 10:04 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.

Analysis

Error
Network Error
A network error occurred while we were trying to communicate with a server.

Hostname: mx1.selea.se

Error message: Connect timed out

IP address: 2001:41d0:701:1100::5ff0

Error
Network Error
A network error occurred while we were trying to communicate with a server.

Hostname: mx.portsit.se

Error message: Connect timed out

IP address: 193.14.90.100

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, but there are warnings
Some aspect of your site's configuration require your attention.
Some TLS and PKI information shown may have been retrieved from cache. The notes provide more information.

Certificate #1  Cached

Leaf certificate *.selea.se
Issuer: Sectigo
Not Before: 24 Mar 2024 00:00:00 UTC
Not After: 24 Mar 2025 23:59:59 UTC (expires in 4 months 25 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.
Warning
Certificate chain is incorrect
This certificate is delivered as part of an incorrect certificate chain. The problems in the chain render the certificate invalid too. Although some clients (typically browsers) are able to fix or rebuild certificate chains, it's generally not safe to assume that all browsers can.

Certificate Chain

Leaf certificate
*.selea.se | 5d5a8a8
Not After: 24 Mar 2025 23:59:59 UTC (expires in 4 months 25 days)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details

Analysis

Warning
Poorly constructed certificate chain
This server is not configured with a correct certificate chain. The possible problems include missing certificates, incorrect certificate order, or unrelated certificates present in the chain. In a correct chain, one certificate is immediately followed by its parent. The final, root, certificate can be omitted. This problem is often difficult to troubleshoot because some clients know how to reconstruct a chain starting with the leaf. Although this behavior is common in browsers, it cannot be relied upon in a general case.

Certificate #2  Cached

Leaf certificate halon.portsit.se
Issuer: DigiCert
Not Before: 30 Jul 2024 00:00:00 UTC
Not After: 17 May 2025 23:59:59 UTC (expires in 6 months 20 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.
Notice
Symantec subordinate CA excluded from early expiration
Although the leaf certificate ultimately chains to a Symantec root, it has been issued from an independently-operated subordinate CA that has been excluded from early expiration.

Certificate Chain

Leaf certificate
halon.portsit.se | 76fb819
Not After: 17 May 2025 23:59:59 UTC (expires in 6 months 20 days)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Intermediate certificate
DigiCert Global G2 TLS RSA SHA256 2020 CA1 | 1f8eb9e
Not After: 23 Sep 2030 23:59:59 UTC (expires in 5 years 10 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Root certificate
DigiCert Global Root G2 | cb3ccbb
Not After: 15 Jan 2038 12:00:00 UTC (expires in 13 years 2 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 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 selea.se
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
This mechanism matches if the sending IP address
is one of the MX hosts for the domain name. mx
Evaluates SPF policy specified in another DNS location. This
directive is typically used to allow hosts controlled by
another organization. include 		relay.selea.se
Evaluates SPF policy specified in another DNS location. This
directive is typically used to allow hosts controlled by
another organization. include 		spf.ports.email
Evaluates SPF policy specified in another DNS location. This
directive is typically used to allow hosts controlled by
another organization. include 		spf.portsgroup.com
This policy element always matches. It's normally used
at the end of a policy to specify the handling of hosts
that don't match earlier mechanisms. ~all

Analysis

Info
SPF policy found

Policy text: v=spf1 a mx include:relay.selea.se include:spf.ports.email include:spf.portsgroup.com ~all

Location: selea.se

Good
SPF policy is valid
Good. Your SPF policy is syntactically valid.
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: 7

SPF Policy Information Included policy

Host where this policy is located.Location relay.selea.se
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
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		70.34.207.137
This mechanism tests whether the IP address being
tested is contained within a given IPv6 network. ip6 		2a05:f480:2000:1685:5400:03ff:fef7:3eb5
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		54.38.158.213
This mechanism tests whether the IP address being
tested is contained within a given IPv6 network. ip6 		2001:41d0:701:1100::5ff0
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		70.34.207.6
This mechanism tests whether the IP address being
tested is contained within a given IPv6 network. ip6 		2a05:f480:2000:2356:5400:4ff:fe0c:fe1e
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.ports.email
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 		193.14.90.143
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		193.14.90.133
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		193.12.211.236
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		193.12.211.136
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		212.247.54.50
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		193.12.211.21
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		193.14.90.131
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.portsgroup.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 		193.14.90.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		193.12.211.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		212.247.54.50
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 		mx.portsit.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

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.selea.se
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 		quarantine
Indicates whether strict or relaxed DKIM
alignment mode is required.adkim 		r
Indicates whether strict or relaxed SPF
alignment mode is required.aspf 		r
Addresses to which aggregate feedback is to be sent.rua mailto:92b4e5f335ae448481e8d213a31f24ad@dmarc-reports.cloudflare.net,mailto:dmarc@selea.se
Addresses to which message-specific failure
information is to be reported.ruf 		mailto:dmarc@selea.se

Analysis

Info
DMARC policy found

Policy: v=DMARC1;p=quarantine;adkim=r;aspf=r;rua=mailto:92b4e5f335ae448481e8d213a31f24ad@dmarc-reports.cloudflare.net,mailto:dmarc@selea.se;ruf=mailto:dmarc@selea.se

Host: _dmarc.selea.se

Good
Valid external destination

Permission record location: selea.se._report._dmarc.dmarc-reports.cloudflare.net

External destination: mailto:92b4e5f335ae448481e8d213a31f24ad@dmarc-reports.cloudflare.net

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.

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

TLS-RPT Policy

Location from which we retrieved the policy indicator.Location _smtp._tls.selea.se
TLS-RPT standard version used by this policy indicator.Version TLSRPTv1
Reporting endpoints specified in the policy.Reporting Endpoints mailto:reports@selea.se
mailto:tlsrpt@selease.uriports.com

Analysis

Good
SMTP TLS-RPT policy valid
Good. Your TLS-RPT policy is valid. SMTP TLS Reporting is a young standard that is not yet widely supported, but support is probably going to increase over time.

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 failed
We've detected serious problems that require your immediate attention.

URL: http://selea.se/

1
http://selea.se/
HTTP/1.1 200 OK

Analysis

Error
Plaintext HTTP server doesn't redirect to HTTPS
This plaintext HTTP server doesn't redirect to HTTPS, leaving its user vulnerable to content sniffing and active network attacks. From late July 2018, Chrome marks plaintext web sites as 'not secure'. We recommend that a redirection is added as soon as possible.

URL: http://www.selea.se/

1
http://www.selea.se/
HTTP/1.1 200 OK

Analysis

Error
Plaintext HTTP server doesn't redirect to HTTPS
This plaintext HTTP server doesn't redirect to HTTPS, leaving its user vulnerable to content sniffing and active network attacks. From late July 2018, Chrome marks plaintext web sites as 'not secure'. We recommend that a redirection is added as soon as possible.

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://selea.se/

1
https://selea.se/
HTTP/1.1 200 OK

URL: https://www.selea.se/

1
https://www.selea.se/
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 failed
We've detected serious problems that require your immediate attention.

TLS Configuration: selea.se (2001:41d0:601:1100:0:0:0:4118)

Analysis

Error
TLS connection failed
We failed to connect to the server using TLS.

Error message: Connect timed out

TLS Configuration: selea.se (54.37.233.253)

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

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 setting 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

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

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

TLS Configuration: selea.se (54.37.234.237)

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

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 setting 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

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

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

TLS Configuration: selea.se (54.37.235.108)

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

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 setting 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

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

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

TLS Configuration: selea.se (2001:41d0:601:1100:0:0:0:3a27)

Analysis

Error
TLS connection failed
We failed to connect to the server using TLS.

Error message: Connect timed out

TLS Configuration: www.selea.se (92.33.194.250)

Encryption protocol version determines what features are
available for negotiation between client and server.Supported protocols 		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.2
Server preference 		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_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_DHE_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0x9f
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA384
 TLS_DHE_RSA_WITH_AES_256_GCM_SHA384  256 bits (DHE 2048 bits)
Suite: TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0x9e
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA256
 TLS_DHE_RSA_WITH_AES_128_GCM_SHA256  128 bits (DHE 2048 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_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_DHE_RSA_WITH_AES_256_CCM_8
Suite ID: 0xc0a3
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA256
 TLS_DHE_RSA_WITH_AES_256_CCM_8  256 bits (DHE 2048 bits)
Suite: TLS_DHE_RSA_WITH_AES_256_CCM
Suite ID: 0xc09f
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA256
 TLS_DHE_RSA_WITH_AES_256_CCM  256 bits (DHE 2048 bits)
Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
Suite ID: 0x6b
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA256
 TLS_DHE_RSA_WITH_AES_256_CBC_SHA256  256 bits (DHE 2048 bits)
Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x39
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
 TLS_DHE_RSA_WITH_AES_256_CBC_SHA  256 bits (DHE 2048 bits)

Analysis

Powerup!
TLS 1.3 not supported
TLS 1.3 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. This version of TLS should be the main protocol used with modern clients.
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 setting 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

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

Good
DHE server parameter not reused
This server does not reuse the private value used for the Diffie-Hellman 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.selea.se

Leaf certificate *.selea.se
Issuer: Sectigo
Not Before: 24 Mar 2024 00:00:00 UTC
Not After: 24 Mar 2025 23:59:59 UTC (expires in 4 months 25 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
*.selea.se | 5d5a8a8
Not After: 24 Mar 2025 23:59:59 UTC (expires in 4 months 25 days)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Intermediate certificate
Sectigo RSA Domain Validation Secure Server CA | 7fa4ff6
Not After: 31 Dec 2030 23:59:59 UTC (expires in 6 years 2 months)
Authentication: RSA 2048 bits (SHA384withRSA)
 View details
Root certificate
USERTrust RSA Certification Authority | e793c9b
Not After: 18 Jan 2038 23:59:59 UTC (expires in 13 years 2 months)
Authentication: RSA 4096 bits (SHA384withRSA)
 View details

Analysis

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

Certificate: selea.se

Leaf certificate selea.se
Issuer: Let's Encrypt
Not Before: 10 Oct 2024 03:18:14 UTC
Not After: 08 Jan 2025 03:18:13 UTC (expires in 2 months 11 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
selea.se | 61ea071
Not After: 08 Jan 2025 03:18:13 UTC (expires in 2 months 11 days)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Intermediate certificate
R10 | 9d7c3f1
Not After: 12 Mar 2027 23:59:59 UTC (expires in 2 years 4 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Root certificate
ISRG Root X1 | 96bcec0
Not After: 04 Jun 2035 11:04:38 UTC (expires in 10 years 7 months)
Authentication: RSA 4096 bits (SHA256withRSA)
 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.

HTML 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
Everything seems to be well configured. Well done.

Encryption of Embedded Resources

In this section we look at the transport 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.

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

Encryption of 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.

0 link(s)
  0 out of 0 are encrypted

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.selea.se/
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.
Good
Policy covers subdomains
When subdomains are included, network attackers are unable to manufacture arbitrary subdomains to manipulate cookies and trick users.
Notice
Preload directive has no effect here
This policy doesn't enable preloading, but that's all right. The preload directive doesn't have any effect unless it's used on an apex hostname.
Warning
Missing redirection
This host uses HSTS, but doesn't have a redirection from HTTP on port 80 to HTTPS on port 443. As a result, clients who visit the plaintext host won't notice and activate HSTS.

Starting point: http://www.selea.se

Expected redirection: https://www.selea.se

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.

Analysis

Warning
Policy set on plaintext port
HSTS policies must not be transmitted over insecure channels.

Location: http://www.selea.se/

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.

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

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.

Test passed
Everything seems to be well configured. Well done.
No external scripts
  SRI not needed
No external stylesheets
  SRI not needed

Analysis

Good
No remote resources
The homepage of this site doesn't contain any remote resources so SRI is not needed.

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.

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

Analysis

Powerup!
Explicitly disable browser XSS protection
For best security, every web site should explicitly disable browser-based XSS protection. This is because this type of functionality can be used to introduce vulnerabilities into otherwise error-free web sites.

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.
Close Details