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

Public Report | runbox.com

TEST ANOTHER

runbox.com

08 Nov 2024 08:43 UTC

Domain Name System

DNS Zonegood
DNS Recordsgood
DNSSECgood
CAAgood

Email

Mail serversgood
TLSgood
Certificatesgood
MTA-STSgood
TLS-RPTgood
DANEgood
SPFgood
DMARCgood

WWW

HTTP (80)good
HTTPS (443)good
TLSneutral
Certificatesgood
Cookiesgood
HTML Contentwarning
Strict Transport Securitywarning
Content Security Policygood
Subresource Integritygood
Frame Optionserror
XSS Protectionwarning
Content Type Optionsgood
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

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
dns61.copyleft.no. PRIMARY
185.226.148.4
2a0c:5a00:148::4 		The server is online. Name resolves to an IPv4 address. Name resolves to an IPv6 address. NS SOA REFERRAL
dns62.copyleft.no.
178.255.144.4
2a02:20c8:1422:1::4 		The server is online. Name resolves to an IPv4 address. Name resolves to an IPv6 address. NS REFERRAL
dns63.copyleft.no.
151.252.14.13
2a02:d140:1:3c::3 		The server is online. Name resolves to an IPv4 address. Name resolves to an IPv6 address. NS REFERRAL

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
151.252.14.13
dns63.copyleft.no.
PTR: dns63.copyleft.no. 		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
178.255.144.4
dns62.copyleft.no.
PTR: dns62.copyleft.no. 		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
185.226.148.4 PRIMARY
dns61.copyleft.no.
PTR: dns61.copyleft.no. 		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
2a02:20c8:1422:1::4
dns62.copyleft.no.
PTR: dns62.copyleft.no. 		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
2a02:d140:1:3c::3
dns63.copyleft.no.
PTR: dns63.copyleft.no. 		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
2a0c:5a00:148::4 PRIMARY
dns61.copyleft.no.
PTR: dns61.copyleft.no. 		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 dns61.copyleft.no.
Email address of the persons responsible for this zone. Also known as RNAME.Admin email hostmaster.copyleft.no.
Zone serial or version number.Serial number -1294956972
The length of time secondary nameservers should wait before querying the primary for changes.Refresh interval 14,400 seconds (about 4 hours)
The length of time secondary nameservers should wait before querying an unresponsive primary again.Retry interval 3,600 seconds (about 1 hour)
The length of time after which secondary nameservers should stop responding to queries for a zone, assuming no updates were obtained from the primary.Expire interval 1,296,000 seconds (about 15 days)
TTL for purposes of negative response caching. Negative cache TTL 3,600 seconds (about 1 hour)
Time To Live (TTL) indicates for how long a record remains valid. SOA record TTL 86,400 seconds (about 1 day)

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
runbox.com.     60 A 185.226.149.25            
www.runbox.com.     60 CNAME runbox.com.            
runbox.com.     60 CAA 0 issuewild "letsencrypt.org"            
runbox.com.     60 CAA 0 iodef "mailto:hostmaster@runbox.com"            
runbox.com.     60 CAA 0 issue "buypass.no"            
runbox.com.     60 CAA 0 issue "letsencrypt.org"            
runbox.com.     86400 DNSKEY 257 3 13 PsX8BFnFQJmwlRtNtbT4t26UHs7oT+aJ35PDmRCUpArqpEn2jfWa0UM86axBLepHY3AgmFAgUauzn09nFdYU6w==            
runbox.com.     86400 DNSKEY 256 3 13 SBCb5FeQ/lVtSttuzi8dgdc3kDDclqbvAsG2Hqi0nrfsN9KXzmP1cHqY5YDW85u54ofO7fdQGAij0qw0p+n+UQ==            
runbox.com.     60 MX 10 mx.runbox.com.            
runbox.com.     3600 NS dns62.copyleft.no.            
runbox.com.     3600 NS dns63.copyleft.no.            
runbox.com.     3600 NS dns61.copyleft.no.            
runbox.com.     86400 SOA dns61.copyleft.no. hostmaster.copyleft.no. 3000010324 14400 3600 1296000 3600            
runbox.com.     60 TXT "google-site-verification=fcQSXdsUMQ8FBKgOgrsTP2TvSnXN974zsfz5J63wQVg"            
runbox.com.     60 TXT "v=spf1 include:spf.runbox.com -all"            
_dmarc.runbox.com.     3600 TXT "v=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc@runbox.com"            
_mta-sts.runbox.com.     60 TXT "v=STSv1; id=20190605;"            
_smtp._tls.runbox.com.     60 TXT "v=TLSRPTv1; rua=mailto:postmaster@runbox.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.

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

Analysis

Good
DNSSEC is well configured
Good. This domain name has well-configured DNSSEC.

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 runbox.com
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 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 		buypass.no  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:hostmaster@runbox.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 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
mx.runbox.com
185.226.149.25
PTR: aibo.runbox.com		 10 
220 aibo.runbox.com ESMTP Exim 4.93 Ubuntu Tue, 05 Nov 2024 15:03:26 +0100

EHLO outbound.hardenize.com
250-aibo.runbox.com Hello outbound.hardenize.com [172.99.67.55]
250-SIZE 136314880
250-8BITMIME
250-PIPELINING
250-CHUNKING
250-STARTTLS
250 HELP

STARTTLS
220 TLS go ahead
Supports STARTTLS.

Analysis

Good
Email servers match MTA-STS policy
Good. This host supports MTA-STS, which means that it restricts which MX servers can be used and how they are configured. We've verified that all MX servers listed here match the policy.
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.

Cache timestamp: 05 Nov 2024 14:03 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: mx.runbox.com (185.226.149.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_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 		05 Nov 2024 14:03 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 runbox.com
Issuer: Buypass
Not Before: 10 May 2024 07:07:19 UTC
Not After: 26 May 2025 21:59:00 UTC (expires in 6 months 18 days)
Key: RSA 4096 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
runbox.com | 89a844a
Not After: 26 May 2025 21:59:00 UTC (expires in 6 months 18 days)
Authentication: RSA 4096 bits (SHA256withRSA)
 View details
Intermediate certificate
Buypass Class 3 CA 2 | daa0435
Not After: 26 Oct 2030 08:16:17 UTC (expires in 5 years 11 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Root certificate
Buypass Class 3 Root CA | edf7ebb
Not After: 26 Oct 2040 08:28:58 UTC (expires in 15 years 11 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.

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.

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.

DANE: mx.runbox.com (185.226.149.25)

Specifies which certificate in the chain
is being pinned and how validation should
be performed.Certificate Usage 		Trust anchor assertion / DANE-TA (2) Creates a pin for a trust anchor that must be
present in the certificate chain. PKIX validation is
performed, under the assumption that the pinned
anchor is trusted.
Determines if the association is made with
a certificate or with a public key (via
its SPKI structure).Selector 		SPKI structure (1)
Determines how matching is done; directly or via a hash. Matching Type SHA2-256 (1)
Contains the data necessary to perform the matching. Data b03d87b056d08cc9d4e675ef19ca83ab53532168a8258598be72e6d85c7dd7c1

Intermediate certificate: RSA 4096 bits
Subject: CN=Buypass Class 3 Root CA, O=Buypass AS-983163327, C=NO
Issuer: CN=Buypass Class 3 Root CA, O=Buypass AS-983163327, C=NO Buypass Class 3 Root CA (RSA 4096 bits)

Analysis

Good
Valid DANE configuration
Excellent. Your DANE configuration matches the certificate chain(s) provided by the service. Your TLS configuration enjoys the additional benefit of DANE validation.

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 runbox.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.runbox.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 include:spf.runbox.com -all

Location: runbox.com

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: 1

SPF Policy Information Included policy

Host where this policy is located.Location spf.runbox.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 		91.220.196.211
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		91.220.196.212
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		91.220.196.225
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		185.226.149.25
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		185.226.149.26
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		185.226.149.37
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		185.226.149.38
This mechanism tests whether the IP address being
tested is contained within a given IPv6 network. ip6 		2a0c:5a00:149::25
This mechanism tests whether the IP address being
tested is contained within a given IPv6 network. ip6 		2a0c:5a00:149::26
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.runbox.com
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
Percentage of messages from mail stream to
which the DMARC policy is to be applied.pct 		100
Addresses to which aggregate feedback is to be sent.rua mailto:dmarc@runbox.com

Analysis

Info
DMARC policy found

Policy: v=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc@runbox.com

Host: _dmarc.runbox.com

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.

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

MTA-STS Policy Indicator

Location from which we retrieved the policy indicator.Location _mta-sts.runbox.com
MTA-STS standard version used by this policy indicator.Version STSv1
Unique policy identifier, whose value must change
every time the underlying policy changes.ID 		20190605

Analysis

Good
MTA-STS policy indicator valid
Good. Your MTA-STS policy indicator is valid.

MTA-STS Policy

The URL from which the policy was obtained.Location https://mta-sts.runbox.com/.well-known/mta-sts.txt
Policy standard version.version STSv1
Policy duration, which specifies how long the sending
MTAs should remember and enforce the server policy for.max‑age 		86,400 seconds (about 1 day)
Policy mode, which can be one of 'none', 'testing' and
'enforcing'. Guess which is best! :)mode 		testing
One 'mx' directive specifies one email server
pattern that's allowed for this host.mx 		mx.runbox.com
One 'mx' directive specifies one email server
pattern that's allowed for this host.mx 		aibo.runbox.com

Analysis

Good
MTA-STS policy is valid
Good. Your MTA-STS policy is valid.
Good
Policy host certificate is valid
Good. Your MTA-STS policy is delivered via a web server that has a valid publicly trusted certificate. This is a necessary condition for the policy to be recognized.
Notice
Policy HTTPS response information

Status code: 200

Length: 82 bytes

Content-Type: text/plain

Certificate: mta-sts.runbox.com

Leaf certificate runbox.com
Issuer: Buypass
Not Before: 10 May 2024 07:07:19 UTC
Not After: 26 May 2025 21:59:00 UTC (expires in 6 months 18 days)
Key: RSA 4096 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
runbox.com | 89a844a
Not After: 26 May 2025 21:59:00 UTC (expires in 6 months 18 days)
Authentication: RSA 4096 bits (SHA256withRSA)
 View details
Intermediate certificate
Buypass Class 3 CA 2 | daa0435
Not After: 26 Oct 2030 08:16:17 UTC (expires in 5 years 11 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Root certificate
Buypass Class 3 Root CA | edf7ebb
Not After: 26 Oct 2040 08:28:58 UTC (expires in 15 years 11 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.

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.runbox.com
TLS-RPT standard version used by this policy indicator.Version TLSRPTv1
Reporting endpoints specified in the policy.Reporting Endpoints mailto:postmaster@runbox.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 passed
Everything seems to be well configured. Well done.

URL: http://runbox.com/

1
http://runbox.com/
HTTP/1.1 301 Moved Permanently
2
https://runbox.com/
HTTP/1.1 200 OK

Analysis

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

URL: http://www.runbox.com/

1
http://www.runbox.com/
HTTP/1.1 301 Moved Permanently
2
https://runbox.com/
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://runbox.com/

1
https://runbox.com/
HTTP/1.1 200 OK

URL: https://www.runbox.com/

1
https://www.runbox.com/
HTTP/1.1 301 Moved Permanently
2
https://runbox.com/
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.

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

TLS Configuration: runbox.com (185.226.149.25)

Analysis

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

Error message: Connection refused

TLS Configuration: www.runbox.com (185.226.149.25)

Analysis

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

Error message: Connect timed out

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.runbox.com

Leaf certificate runbox.com
Issuer: Buypass
Not Before: 10 May 2024 07:07:19 UTC
Not After: 26 May 2025 21:59:00 UTC (expires in 6 months 18 days)
Key: RSA 4096 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
runbox.com | 89a844a
Not After: 26 May 2025 21:59:00 UTC (expires in 6 months 18 days)
Authentication: RSA 4096 bits (SHA256withRSA)
 View details
Intermediate certificate
Buypass Class 3 CA 2 | daa0435
Not After: 26 Oct 2030 08:16:17 UTC (expires in 5 years 11 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Root certificate
Buypass Class 3 Root CA | edf7ebb
Not After: 26 Oct 2040 08:28:58 UTC (expires in 15 years 11 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.

Certificate: runbox.com

Leaf certificate runbox.com
Issuer: Buypass
Not Before: 10 May 2024 07:07:19 UTC
Not After: 26 May 2025 21:59:00 UTC (expires in 6 months 18 days)
Key: RSA 4096 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
runbox.com | 89a844a
Not After: 26 May 2025 21:59:00 UTC (expires in 6 months 18 days)
Authentication: RSA 4096 bits (SHA256withRSA)
 View details
Intermediate certificate
Buypass Class 3 CA 2 | daa0435
Not After: 26 Oct 2030 08:16:17 UTC (expires in 5 years 11 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Root certificate
Buypass Class 3 Root CA | edf7ebb
Not After: 26 Oct 2040 08:28:58 UTC (expires in 15 years 11 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, but there are warnings
Some aspect of your site's configuration require your attention.

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.

4 script(s)
  4 out of 4 are secure  View all
1 CSS file(s)
  1 out of 1 are secure  View all
35 media file(s)
  35 out of 35 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.

17 link(s)
  11 out of 17 are encrypted
http://www.jssor.com
http://blog.runbox.com/category/news/
http://www.visa.com
http://www.visa.com
http://www.mastercard.com
http://www.mastercard.com
 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://runbox.com/
Specifies policy duration. Once activated, HSTS stays in force
until this time lapses. Browsers update policy cache duration
every time they receive a new HSTS header from a site.max‑age 		63,072,000 seconds (about 2 years)
When present, this directive forces HSTS activation
on allsubdomains. For best security, HSTS should be
deployed on the bare domain name (e.g., example.com)
and all its subdomains.includeSubDomains
Presence of this directive indicates that a web site wishes to
permanently use HSTS and that its policy information should be
preloaded (embedded in browsers).preload

Analysis

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.

HSTS Policy  Apex host

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

Analysis

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

frame-src blob:   'self'   https://js.stripe.com   https://hcaptcha.com   https://*.hcaptcha.com   https://video.runbox.com/  
script-src 'self'   https://support.runbox.com/   https://video.runbox.com/   https://js.stripe.com   https://hcaptcha.com   https://*.hcaptcha.com   https://assets.hcaptcha.com   This parameter shouldn't be used because it reenables
insecure behavior that CSP disables by default.'unsafe-inline'   This parameter shouldn't be used because it reenables
insecure behavior that CSP disables by default.'unsafe-eval'  
object-src 'self'  
img-src 'self'   data:   https://*   http://*  
media-src 'self'  
child-src 'self'   blob:  
font-src 'self'  
connect-src 'self'   wss://runbox.com   https://sentry.runbox.com   https://video.runbox.com/   https://js.stripe.com   https://gravatar.com   https://hcaptcha.com   https://*.hcaptcha.com  
style-src 'self'   https://hcaptcha.com   https://*.hcaptcha.com   This parameter shouldn't be used because it reenables
insecure behavior that CSP disables by default.'unsafe-inline'  

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: frame-src blob: https://runbox.com https://js.stripe.com https://hcaptcha.com https://*.hcaptcha.com https://video.runbox.com/; script-src https://runbox.com https://support.runbox.com/ https://video.runbox.com/ https://js.stripe.com https://hcaptcha.com https://*.hcaptcha.com https://assets.hcaptcha.com 'unsafe-inline' 'unsafe-eval'; object-src https://runbox.com; img-src 'self' data: https://* http://*; media-src 'self'; child-src https://runbox.com blob:; font-src 'self'; connect-src 'self' wss://runbox.com https://sentry.runbox.com https://video.runbox.com/ https://js.stripe.com https://gravatar.com https://hcaptcha.com https://*.hcaptcha.com; style-src 'self' https://hcaptcha.com https://*.hcaptcha.com 'unsafe-inline'

Location: https://runbox.com/

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.
4 script(s)
  4 out of 4 are secure  View all
1 CSS file(s)
  1 out of 1 are secure  View all

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

Analysis

Info
Header information

Name: X-Frame-Options

Value: SAMEORIGIN

Info
Header information

Name: X-Frame-Options

Value: SAMEORIGIN

Error
Multiple headers
Multiple X-Frame-Options headers are not allowed.

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