Hardenize has joined Red Sift! Find out more in our blog post.
Web Security Overview
Supported and well configured
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.

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
Supported and well configured
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.

For important sites VERY IMPORTANT medium EFFORT
Supported and well configured
HSTS Preloaded

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

For important sites VERY IMPORTANT medium EFFORT
Supported and well configured
Content Security Policy

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

For important sites IMPORTANT high EFFORT
Email Security Overview
Supported and well configured
STARTTLS

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

For all sites VERY IMPORTANT low EFFORT
Supported and well configured
SPF

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

For important sites IMPORTANT low EFFORT
Supported and well configured
DMARC

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

For important sites IMPORTANT low EFFORT

Domain Registration

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

Test passed
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.

Registrant -
Lookup Time 19 May 2024 03:34 UTC
Source https://rdap.verisign.com/com/v1/domain/hubspot.com
Registrar
Registrar MarkMonitor Inc.
Registrar IANA ID 292
Events
Registration 06 Feb 2005 20:02 UTC
Update 06 Jan 2023 09:36 UTC
Expiration 06 Feb 2025 20:02 UTC
Configuration
Statuses clientDeleteProhibited
clientTransferProhibited
clientUpdateProhibited
Registrar Lock
Registry Lock
Nameservers jerry.ns.cloudflare.com
yolanda.ns.cloudflare.com
Contacts
Registrar MarkMonitor Inc.
Abuse Email: abusecomplaints@markmonitor.com
Phone: +1.2086851750

Analysis

Powerup!
Consider locking this domain name at registry level
Some domain name locks are better than others. Most registrars can configure a lock that they control, which we call a registrar lock. This lock is useful, but at the next level there is the registry lock, which requires a further interaction with the registry for any changes. Registry locks should be used wherever possible for business-critical domain names.

WHOIS

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

Registrant HubSpot, Inc.
Lookup Time 19 May 2024 03:34 UTC
Source whois.markmonitor.com:43
Registrar
Registrar MarkMonitor, Inc.
Registrar IANA ID 292
Events
Registration 06 Feb 2005 20:02 UTC
Update 11 May 2023 20:02 UTC
Expiration 06 Feb 2025 00:00 UTC
Configuration
Statuses clientTransferProhibited
clientUpdateProhibited
clientDeleteProhibited
Registrar Lock
Registry Lock
Nameservers yolanda.ns.cloudflare.com
jerry.ns.cloudflare.com
Contacts
Registrar MarkMonitor, Inc.
MarkMonitor, Inc.
Abuse Email: abusecomplaints@markmonitor.com
Phone: +1.2086851750
Registrant HubSpot, Inc.
US
Email: Select Request Email Form at https://domains.markmonitor.com/whois/hubspot.com
Administrative HubSpot, Inc.
US
Email: Select Request Email Form at https://domains.markmonitor.com/whois/hubspot.com
Technical HubSpot, Inc.
US
Email: Select Request Email Form at https://domains.markmonitor.com/whois/hubspot.com

Analysis

Powerup!
Consider locking this domain name at registry level
Some domain name locks are better than others. Most registrars can configure a lock that they control, which we call a registrar lock. This lock is useful, but at the next level there is the registry lock, which requires a further interaction with the registry for any changes. Registry locks should be used wherever possible for business-critical domain names.

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
jerry.ns.cloudflare.com. PRIMARY
108.162.193.182
172.64.33.182
173.245.59.182
2606:4700:58::adf5:3bb6
2803:f800:50::6ca2:c1b6
2a06:98c1:50::ac40:21b6
The server is online. Name resolves to an IPv4 address. Name resolves to an IPv6 address. SOA REFERRAL NS
yolanda.ns.cloudflare.com.
108.162.192.241
172.64.32.241
173.245.58.241
2606:4700:50::adf5:3af1
2803:f800:50::6ca2:c0f1
2a06:98c1:50::ac40:20f1
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.241
yolanda.ns.cloudflare.com.
PTR: yolanda.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, GLUE 1232
108.162.193.182 PRIMARY
jerry.ns.cloudflare.com.
PTR: jerry.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, GLUE 1232
172.64.32.241
yolanda.ns.cloudflare.com.
PTR: yolanda.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, GLUE 1232
172.64.33.182 PRIMARY
jerry.ns.cloudflare.com.
PTR: jerry.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, GLUE 1232
173.245.58.241
yolanda.ns.cloudflare.com.
PTR: yolanda.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, GLUE 1232
173.245.59.182 PRIMARY
jerry.ns.cloudflare.com.
PTR: jerry.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, GLUE 1232
2606:4700:50::adf5:3af1
yolanda.ns.cloudflare.com.
PTR: yolanda.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, GLUE 1232
2606:4700:58::adf5:3bb6 PRIMARY
jerry.ns.cloudflare.com.
PTR: jerry.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, GLUE 1232
2803:f800:50::6ca2:c0f1
yolanda.ns.cloudflare.com.
PTR: yolanda.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, GLUE 1232
2803:f800:50::6ca2:c1b6 PRIMARY
jerry.ns.cloudflare.com.
PTR: jerry.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, GLUE 1232
2a06:98c1:50::ac40:20f1
yolanda.ns.cloudflare.com.
PTR: yolanda.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, GLUE 1232
2a06:98c1:50::ac40:21b6 PRIMARY
jerry.ns.cloudflare.com.
PTR: jerry.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, GLUE 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 jerry.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 -1953442799
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
hubspot.com.     300 A 104.16.117.116            
hubspot.com.     300 A 104.16.118.116            
www.hubspot.com.     300 A 104.18.39.114            
www.hubspot.com.     300 A 172.64.148.142            
hubspot.com.     300 AAAA 2606:4700:0:0:0:0:6810:7674            
hubspot.com.     300 AAAA 2606:4700:0:0:0:0:6810:7574            
www.hubspot.com.     300 AAAA 2606:4700:4400:0:0:0:ac40:948e            
www.hubspot.com.     300 AAAA 2606:4700:4400:0:0:0:6812:2772            
hubspot.com.     3600 DNSKEY 257 3 13 mdsswUyr3DPW132mOi8V9xESWE8jTo0dxCjjnopKl+GqJxpVXckHAeF+KkxLbxILfDLUT0rAK9iUzy1L53eKGQ==            
hubspot.com.     3600 DNSKEY 256 3 13 oJMRESz5E4gYzS/q6XDrvU1qMPYIjCWzJaOau8XNEZeqCYKD5ar0IRd8KqXXFJkqmVfRvMGPmM1x8fGAa2XhSA==            
hubspot.com.     300 HTTPS 1 . alpn=h2 ipv4hint=104.16.117.116,104.16.118.116 ipv6hint=2606:4700:0:0:0:0:6810:7574,2606:4700:0:0:0:0:6810:7674            
www.hubspot.com.     300 HTTPS 1 . alpn=h2 ipv4hint=104.18.39.114,172.64.148.142 ipv6hint=2606:4700:4400:0:0:0:6812:2772,2606:4700:4400:0:0:0:ac40:948e            
hubspot.com.     300 MX 5 us-smtp-inbound-1.mimecast.com.            
hubspot.com.     300 MX 5 us-smtp-inbound-2.mimecast.com.            
hubspot.com.     86400 NS jerry.ns.cloudflare.com.            
hubspot.com.     86400 NS yolanda.ns.cloudflare.com.            
hubspot.com.     1800 SOA jerry.ns.cloudflare.com. dns.cloudflare.com. 2341524497 10000 2400 604800 1800            
hubspot.com.     300 TXT "apple-domain-verification=yMRAjA0cp0ZxAXJO"            
hubspot.com.     300 TXT "atlassian-domain-verification=J3f6YdOOu6/tNWzA7xI39Nqm5B5qOZ0ayDbcEHv5nntPWOkwTUQ3Fs6ha4CtCD4v"            
hubspot.com.     300 TXT "atlassian-domain-verification=znAKxFvnc6Sp4Vrf/Q8BIiqYFzh8awjMd8bRRibzNLriS6CnZy/sepMsnPHgVU/P"            
hubspot.com.     300 TXT "canva-site-verification=2q1KYRxYvE35Tv1_-IhwKQ"            
hubspot.com.     300 TXT "detectify-verification=46f357acabb7675925ab09872da42f0e"            
hubspot.com.     300 TXT "facebook-domain-verification=v0z7wt3tvx72qwt80eu2sf2z7zb9yi"            
hubspot.com.     300 TXT "google-site-verification=0msnYMjxgKXxDJXEIP6WB4AA2HVYl6Sz2Cy541f4ono"            
hubspot.com.     300 TXT "google-site-verification=125dhZzE7NHja1SJMBfKB-vGsx-WIdbQlVFXzuzUINU"            
hubspot.com.     300 TXT "google-site-verification=4S-EduW2OFChAhn0kW_SjNR8vrLW_kQQsWp7ZuXn6Xk"            
hubspot.com.     300 TXT "google-site-verification=J2I6jE_EJoX1m4waFuwZdKBpo7HLDNQKMfsvDUB2R4k"            
hubspot.com.     300 TXT "google-site-verification=J9pq_P2VWxNeuYsXn4sCdHCCTcnYPMGEjt0EjVwA85g"            
hubspot.com.     300 TXT "google-site-verification=P7ETKNIUHAbZHGHRwCOz3PZtuNT3JQsqGG-Ts73Ghrc"            
hubspot.com.     300 TXT "google-site-verification=ULhWgbGcguDpe6LuicAUc0CpIkFGccp1YmucGWoeut4"            
hubspot.com.     300 TXT "google-site-verification=hN2qgnvz-VyYXBoCdrN1ZU8Ye8F83DmhBJM2C0j43OE"            
hubspot.com.     300 TXT "google-site-verification=kJC6kA1mklSsAWS9kJ--0uRIdsMfupq6NoM3Jf2udf4"            
hubspot.com.     300 TXT "google-site-verification=rwNRWYjcqZUsYDG1huk_dIsBRCfOesjoHPT5wh4_5lg"            
hubspot.com.     300 TXT "h1-domain-verification=Xb9onaruo7KoR9XNxCyu9vUNz7rPj4uYMiteXKXLWjYs1Sy4"            
hubspot.com.     300 TXT "hubspot-developer-verification=MzVhYTQwYmUtN2UyZS00MGE4LWJlN2EtMzQ0NGQwNmQwNTg2"            
hubspot.com.     300 TXT "onetrust-domain-verification=99a8a3a51efe4a8fbd72bd2e15a76f1e"            
hubspot.com.     300 TXT "openai-domain-verification=dv-tkdJ2BeBSodzZLfRQMyFwfp7"            
hubspot.com.     300 TXT "smartsheet-site-validation=AacCig3iKBx3y4SHCYU0WdrlNTIIBX0D"            
hubspot.com.     300 TXT "status-page-domain-verification=m19bvpv5sk0s"            
hubspot.com.     300 TXT "stripe-verification=e499b7aac3e600c9cda9629ef657da9a1ea6cd57ce5e7e138cdeeff98419b3ff"            
hubspot.com.     300 TXT "v=spf1 redirect=_hspf.hubspot.com"            
hubspot.com.     300 TXT "zapier-domain-verification-challenge=6da904b8-8498-4ea6-bc47-a7d3e3761143"            
hubspot.com.     300 TXT "zoom-domain-verification=1bd4b6dc-56ce-4215-8de0-5543d26ced6f"            
hubspot.com.     300 TXT "MS=ms42818833"            
hubspot.com.     300 TXT "Probely=a59314eb-85a7-45be-b13b-52794692a2b2"            
hubspot.com.     300 TXT "\"\""            
hubspot.com.     300 TXT "adobe-idp-site-verification=67b8fd17615e71f28b3fc9b31fa84e8671d0fc28c4a80c23cef37c22f26a059e"            
_dmarc.hubspot.com.     300 TXT "v=DMARC1;p=reject;pct=100;rua=mailto:bdlk5ayo@ag.dmarcian.com;ruf=mailto:bdlk5ayo@fr.dmarcian.com"            
_domainkey.hubspot.com.     300 TXT "v=spf1 ~all"            
_mta-sts.hubspot.com.     300 TXT "v=spf1 ~all"            
_smtp._tls.hubspot.com.     300 TXT "v=spf1 ~all"            

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.

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

Analysis

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

Email (SMTP)

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

Test passed
Everything seems to be well configured. Well done.
Some TLS and PKI information shown may have been retrieved from cache. The notes provide more information.
Server Preference Operational STARTTLS TLS PKI DNSSEC DANE
us-smtp-inbound-2.mimecast.com
207.211.30.141
PTR: us-smtp-inbound-2.mimecast.com
5
220 us-smtp-inbound-1.mimecast.com ESMTP; Mon, 13 May 2024 13:40:04 -0400

EHLO outbound.hardenize.com
250-us-smtp-inbound-1.mimecast.com Hello [172.99.67.55]
250-STARTTLS
250 HELP

STARTTLS
220 Starting TLS [TQVUbbOIPuSRQ_dUeyiuSg.us257]
Supports STARTTLS. Not supported. Not applicable,
requires TLS.
us-smtp-inbound-2.mimecast.com
207.211.30.221
PTR: us-smtp-inbound-2.mimecast.com
5
220 us-smtp-inbound-1.mimecast.com ESMTP; Mon, 13 May 2024 13:40:08 -0400

EHLO outbound.hardenize.com
250-us-smtp-inbound-1.mimecast.com Hello [172.99.67.55]
250-STARTTLS
250 HELP

STARTTLS
220 Starting TLS [-MYw3XRoOCCoNXLhG7-fJw.us147]
Supports STARTTLS. Not supported. Not applicable,
requires TLS.
us-smtp-inbound-2.mimecast.com
205.139.110.221
PTR: us-smtp-inbound-1.mimecast.com
5
220 us-smtp-inbound-1.mimecast.com ESMTP; Mon, 13 May 2024 13:40:05 -0400

EHLO outbound.hardenize.com
250-us-smtp-inbound-1.mimecast.com Hello [172.99.67.55]
250-STARTTLS
250 HELP

STARTTLS
220 Starting TLS [0pGzMtmXNKaHNRInCiS5bQ.us180]
Supports STARTTLS. Not supported. Not applicable,
requires TLS.
us-smtp-inbound-2.mimecast.com
205.139.110.242
PTR: us-smtp-inbound-1.mimecast.com
5
220 us-smtp-inbound-1.mimecast.com ESMTP; Mon, 13 May 2024 13:40:04 -0400

EHLO outbound.hardenize.com
250-us-smtp-inbound-1.mimecast.com Hello [172.99.67.55]
250-STARTTLS
250 HELP

STARTTLS
220 Starting TLS [mikGdWpjNHey-0DPpDWHLw.us18]
Supports STARTTLS. Not supported. Not applicable,
requires TLS.
us-smtp-inbound-2.mimecast.com
205.139.110.141
PTR: us-smtp-inbound-2.mimecast.com
5
220 us-smtp-inbound-1.mimecast.com ESMTP; Mon, 13 May 2024 13:40:08 -0400

EHLO outbound.hardenize.com
250-us-smtp-inbound-1.mimecast.com Hello [172.99.67.55]
250-STARTTLS
250 HELP

STARTTLS
220 Starting TLS [nqZ_YFtFNRuRkv6rfvIG_g.us326]
Supports STARTTLS. Not supported. Not applicable,
requires TLS.
us-smtp-inbound-2.mimecast.com
207.211.30.242
PTR: us-smtp-inbound-2.mimecast.com
5
220 us-smtp-inbound-1.mimecast.com ESMTP; Mon, 13 May 2024 13:40:09 -0400

EHLO outbound.hardenize.com
250-us-smtp-inbound-1.mimecast.com Hello [172.99.67.55]
250-STARTTLS
250 HELP

STARTTLS
220 Starting TLS [J0MDncRfNXacLvORbqsLvw.us619]
Supports STARTTLS. Not supported. Not applicable,
requires TLS.
us-smtp-inbound-1.mimecast.com
207.211.30.242
PTR: us-smtp-inbound-2.mimecast.com
5
220 us-smtp-inbound-1.mimecast.com ESMTP; Mon, 13 May 2024 13:40:10 -0400

EHLO outbound.hardenize.com
250-us-smtp-inbound-1.mimecast.com Hello [172.99.67.55]
250-STARTTLS
250 HELP

STARTTLS
220 Starting TLS [H-cjwthHMMa_GAhhT2VdCg.us241]
Supports STARTTLS. Not supported. Not applicable,
requires TLS.
us-smtp-inbound-1.mimecast.com
205.139.110.141
PTR: us-smtp-inbound-2.mimecast.com
5
220 us-smtp-inbound-1.mimecast.com ESMTP; Mon, 13 May 2024 13:40:09 -0400

EHLO outbound.hardenize.com
250-us-smtp-inbound-1.mimecast.com Hello [172.99.67.55]
250-STARTTLS
250 HELP

STARTTLS
220 Starting TLS [Vdz0WNRMM9q1drWK9nf5aQ.us66]
Supports STARTTLS. Not supported. Not applicable,
requires TLS.
us-smtp-inbound-1.mimecast.com
207.211.30.141
PTR: us-smtp-inbound-2.mimecast.com
5
220 us-smtp-inbound-1.mimecast.com ESMTP; Mon, 13 May 2024 13:40:11 -0400

EHLO outbound.hardenize.com
250-us-smtp-inbound-1.mimecast.com Hello [172.99.67.55]
250-STARTTLS
250 HELP

STARTTLS
220 Starting TLS [l2CQU2U-N0Kty2DBSVcZsQ.us271]
Supports STARTTLS. Not supported. Not applicable,
requires TLS.
us-smtp-inbound-1.mimecast.com
205.139.110.242
PTR: us-smtp-inbound-1.mimecast.com
5
220 us-smtp-inbound-1.mimecast.com ESMTP; Mon, 13 May 2024 13:40:10 -0400

EHLO outbound.hardenize.com
250-us-smtp-inbound-1.mimecast.com Hello [172.99.67.55]
250-STARTTLS
250 HELP

STARTTLS
220 Starting TLS [3GitcERwOtGpkW-N3_aoow.us226]
Supports STARTTLS. Not supported. Not applicable,
requires TLS.
us-smtp-inbound-1.mimecast.com
205.139.110.221
PTR: us-smtp-inbound-1.mimecast.com
5
220 us-smtp-inbound-1.mimecast.com ESMTP; Mon, 13 May 2024 13:40:11 -0400

EHLO outbound.hardenize.com
250-us-smtp-inbound-1.mimecast.com Hello [172.99.67.55]
250-STARTTLS
250 HELP

STARTTLS
220 Starting TLS [vkhnDV9XM-qChjKNN5sAvw.us160]
Supports STARTTLS. Not supported. Not applicable,
requires TLS.
us-smtp-inbound-1.mimecast.com
207.211.30.221
PTR: us-smtp-inbound-2.mimecast.com
5
220 us-smtp-inbound-1.mimecast.com ESMTP; Mon, 13 May 2024 13:40:10 -0400

EHLO outbound.hardenize.com
250-us-smtp-inbound-1.mimecast.com Hello [172.99.67.55]
250-STARTTLS
250 HELP

STARTTLS
220 Starting TLS [qiG3RuczP5y8zZcZ4zCCNQ.us403]
Supports STARTTLS. Not supported. Not applicable,
requires TLS.

Analysis

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

Latest cache timestamp: 13 May 2024 17:40 UTC

Earliest cache timestamp: 13 May 2024 17:40 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: us-smtp-inbound-2.mimecast.com (207.211.30.141) 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 ecdh_x25519 (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
13 May 2024 17:40 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: us-smtp-inbound-2.mimecast.com (207.211.30.221) 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 ecdh_x25519 (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
13 May 2024 17:40 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: us-smtp-inbound-2.mimecast.com (205.139.110.221) 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 ecdh_x25519 (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
13 May 2024 17:40 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: us-smtp-inbound-2.mimecast.com (205.139.110.242) 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 ecdh_x25519 (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
13 May 2024 17:40 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: us-smtp-inbound-2.mimecast.com (205.139.110.141) 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 ecdh_x25519 (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
13 May 2024 17:40 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: us-smtp-inbound-2.mimecast.com (207.211.30.242) 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 ecdh_x25519 (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
13 May 2024 17:40 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: us-smtp-inbound-1.mimecast.com (207.211.30.242) 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 ecdh_x25519 (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
13 May 2024 17:40 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: us-smtp-inbound-1.mimecast.com (205.139.110.141) 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 ecdh_x25519 (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
13 May 2024 17:40 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: us-smtp-inbound-1.mimecast.com (207.211.30.141) 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 ecdh_x25519 (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
13 May 2024 17:40 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: us-smtp-inbound-1.mimecast.com (205.139.110.242) 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 ecdh_x25519 (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
13 May 2024 17:40 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: us-smtp-inbound-1.mimecast.com (205.139.110.221) 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 ecdh_x25519 (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
13 May 2024 17:40 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: us-smtp-inbound-1.mimecast.com (207.211.30.221) 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 ecdh_x25519 (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
13 May 2024 17:40 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 *.mimecast.com
Issuer: DigiCert
Not Before: 30 Jan 2024 00:00:00 UTC
Not After: 25 Feb 2025 23:59:59 UTC (expires in 9 months 6 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
*.mimecast.com | 20359a9
Not After: 25 Feb 2025 23:59:59 UTC (expires in 9 months 6 days)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Intermediate certificate
DigiCert Global G2 TLS RSA SHA256 2020 CA1 | c8025f9
Not After: 29 Mar 2031 23:59:59 UTC (expires in 6 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 7 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 hubspot.com
SPF version used by this policy.v spf1
This modifier is intended for consolidating both
authorizations and policy into a common set to be
shared within a single administrative domain.
redirect
_hspf.hubspot.com

Analysis

Info
SPF policy found

Policy text: v=spf1 redirect=_hspf.hubspot.com

Location: hubspot.com

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

SPF Policy Information Included policy

Host where this policy is located.Location _hspf.hubspot.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
_hspf1.hubspot.com
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
66.102.0.0/20
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
54.174.53.128/30
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
54.174.52.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
54.174.57.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
54.174.59.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
54.174.60.0/23
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
54.174.63.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
166.78.68.0/22
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
192.254.112.0/20
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
72.14.192.0/18
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
161.38.192.0/20
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
35.190.247.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
159.183.0.0/16
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
158.247.16.0/20
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
207.211.30.128/25
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
207.211.31.0/25
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
216.239.32.0/19
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
124.47.150.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
141.193.184.64/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

SPF Policy Information Included policy

Host where this policy is located.Location _hspf1.hubspot.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
_hspf2.hubspot.com
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
35.191.0.0/16
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
50.31.32.0/19
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
185.58.84.93
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
124.47.189.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
141.193.185.64/26
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
159.135.140.80/29
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
143.55.224.0/20
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
159.135.224.0/20
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
62.140.7.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
139.180.17.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
147.28.36.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
91.220.42.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
198.244.48.0/20
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
143.244.80.0/20
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
146.20.113.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
18.208.124.128/25
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
204.220.160.0/20
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
146.20.191.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
168.245.0.0/17
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 _hspf2.hubspot.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
_hspf3.hubspot.com
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
207.8.244.204
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
198.21.0.0/21
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
74.125.0.0/16
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
180.189.28.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
207.211.30.64/26
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
216.205.24.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
18.236.56.161
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
208.117.48.0/20
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
172.253.56.0/21
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
103.13.69.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
146.101.78.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
194.104.108.21
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
172.253.112.0/20
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
223.165.113.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
223.165.115.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
223.165.118.0/23
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
223.165.120.0/23
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
209.85.128.0/17
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
198.37.144.0/20
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 _hspf3.hubspot.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
_hspf4.hubspot.com
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
194.104.110.21
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
34.218.116.3
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
209.61.151.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
3.93.157.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
192.237.158.0/23
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
23.253.182.0/23
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
141.193.184.128/25
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
141.193.185.128/25
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
87.253.232.0/21
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
185.189.236.0/22
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
198.61.254.0/23
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
173.194.0.0/16
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
103.96.20.22
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
207.211.41.113
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
185.58.85.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
185.58.86.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
146.20.112.0/26
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
104.130.122.0/23
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
170.10.128.0/23
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 _hspf4.hubspot.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
_hspf5.hubspot.com
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
103.96.22.22
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
207.82.80.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
170.10.133.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
3.210.190.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
41.74.192.0/21
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
216.58.192.0/19
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
41.74.200.0/23
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
41.74.204.0/23
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
41.74.206.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
208.74.204.0/22
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
195.130.217.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
104.130.96.0/28
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
185.250.236.0/22
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
207.8.247.102
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
213.167.75.0/25
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
213.167.81.0/25
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
205.139.110.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
185.211.120.0/22
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
159.135.132.128/25
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 _hspf5.hubspot.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
_hspf6.hubspot.com
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
130.211.0.0/22
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
108.179.144.0/20
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
51.163.158.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
46.19.170.16
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
193.7.206.0/25
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
193.7.207.0/25
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
23.253.216.90
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
149.72.0.0/16
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
63.128.21.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
103.96.21.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
103.96.23.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
69.72.32.0/20
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
194.104.108.240/29
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
194.104.109.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
194.104.111.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
103.96.20.96/28
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
103.96.22.96/28
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
141.193.184.32/27
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
194.104.110.240/28
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 _hspf6.hubspot.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
_hspf7.hubspot.com
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
141.193.185.32/27
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
159.112.240.0/20
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
62.140.10.21
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
172.217.0.0/19
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
108.177.8.0/21
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
141.193.32.0/23
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
172.217.32.0/20
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
66.249.80.0/20
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
108.177.96.0/19
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
172.217.128.0/19
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
64.233.160.0/19
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
172.217.160.0/20
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
172.217.192.0/19
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
216.145.217.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv6 network.
ip6
2a00:1450:4000::/36
This mechanism tests whether the IP address being
tested is contained within a given IPv6 network.
ip6
2c0f:fb50:4000::/36
This mechanism tests whether the IP address being
tested is contained within a given IPv6 network.
ip6
2800:3f0:4000::/36
This mechanism tests whether the IP address being
tested is contained within a given IPv6 network.
ip6
2404:6800:4000::/36
This policy element always matches. It's normally used
at the end of a policy to specify the handling of hosts
that don't match earlier mechanisms.
-all

SPF Policy Information Included policy

Host where this policy is located.Location _hspf7.hubspot.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
20.51.98.61
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
167.89.0.0/17
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
216.145.221.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv6 network.
ip6
2607:f8b0:4000::/36
This mechanism tests whether the IP address being
tested is contained within a given IPv6 network.
ip6
2001:4860:4000::/36
This policy element always matches. It's normally used
at the end of a policy to specify the handling of hosts
that don't match earlier mechanisms.
-all

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.hubspot.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
reject
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:bdlk5ayo@ag.dmarcian.com
Addresses to which message-specific failure
information is to be reported.
ruf
mailto:bdlk5ayo@fr.dmarcian.com

Analysis

Info
DMARC policy found

Policy: v=DMARC1;p=reject;pct=100;rua=mailto:bdlk5ayo@ag.dmarcian.com;ruf=mailto:bdlk5ayo@fr.dmarcian.com

Host: _dmarc.hubspot.com

Good
Valid external destination

Permission record location: hubspot.com._report._dmarc.ag.dmarcian.com

External destination: mailto:bdlk5ayo@ag.dmarcian.com

Permission record contents: v=DMARC1;

Good
Valid external destination

Permission record location: hubspot.com._report._dmarc.fr.dmarcian.com

External destination: mailto:bdlk5ayo@fr.dmarcian.com

Permission record contents: v=DMARC1;

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

MTA Strict Transport Security

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

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

SMTP TLS Reporting

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

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

HTTP (80)

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

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

URL: http://hubspot.com/

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

Analysis

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

URL: http://www.hubspot.com/

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

1
https://hubspot.com/
HTTP/1.1 301 Moved Permanently
2
https://www.hubspot.com/
HTTP/1.1 200 OK

URL: https://www.hubspot.com/

1
https://www.hubspot.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.

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

TLS Configuration: www.hubspot.com (2606:4700:4400:0:0:0:ac40:948e)

Encryption protocol version determines what features are
available for negotiation between client and server.
Supported protocols
TLS v1.3
TLS v1.2
Servers should always enforce their own cipher
suite preference, as that is the only approach
that guarantees that the best possible suite is
selected.
Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3
Server preference
Suite: TLS_CHACHA20_POLY1305_SHA256
Suite ID: 0x1303
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_AES_128_GCM_SHA256
Suite ID: 0x1301
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_AES_256_GCM_SHA384
Suite ID: 0x1302
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2
Server preference
Suite: AGL_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcc13
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
AGL_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcca8
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0xc02f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0x9c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_GCM_SHA256
 128 bits
Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x2f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_128_CBC_SHA
 128 bits
Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0x9d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA384
TLS_RSA_WITH_AES_256_GCM_SHA384
 256 bits
Suite: TLS_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x35
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0xc027
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0x3c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_CBC_SHA256
 128 bits
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc028
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_256_CBC_SHA256
Suite ID: 0x3d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_256_CBC_SHA256
 256 bits

Analysis

Good
TLS 1.3 supported
Excellent. This server supports TLS 1.3, which is the latest revision of the TLS protocol and a significant improvement over earlier versions. Developed over a period of several years and extensively analyzed prior to the release, TLS 1.3 removed insecure features, and improved both security and performance.
Good
TLS 1.2 supported
Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.
Good
Deprecated protocols not supported
Excellent. This server doesn't support any of the deprecated protocol (TLS 1.1 and earlier).
Good
Strong key exchange detected
Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.
Good
Server prefers forward secrecy and authenticated encryption suites
Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.
Good
Server enforces cipher suite preferences
Excellent. This server enforces server cipher suite preference, which means that it is able to select the best suite from the options submitted by clients. Combined with a well designed list of supported cipher suites, this settings enables negotiation of best security.
Good
All TLS connections with this server satisfy Apple's CT requirements
All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

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: hubspot.com (2606:4700:0:0:0:0:6810:7574)

Encryption protocol version determines what features are
available for negotiation between client and server.
Supported protocols
TLS v1.3
TLS v1.2
Servers should always enforce their own cipher
suite preference, as that is the only approach
that guarantees that the best possible suite is
selected.
Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3
Server preference
Suite: TLS_CHACHA20_POLY1305_SHA256
Suite ID: 0x1303
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_AES_128_GCM_SHA256
Suite ID: 0x1301
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_AES_256_GCM_SHA384
Suite ID: 0x1302
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2
Server preference
Suite: AGL_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcc13
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
AGL_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcca8
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0xc02f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0x9c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_GCM_SHA256
 128 bits
Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x2f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_128_CBC_SHA
 128 bits
Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0x9d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA384
TLS_RSA_WITH_AES_256_GCM_SHA384
 256 bits
Suite: TLS_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x35
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0xc027
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0x3c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_CBC_SHA256
 128 bits
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc028
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_256_CBC_SHA256
Suite ID: 0x3d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_256_CBC_SHA256
 256 bits

Analysis

Good
TLS 1.3 supported
Excellent. This server supports TLS 1.3, which is the latest revision of the TLS protocol and a significant improvement over earlier versions. Developed over a period of several years and extensively analyzed prior to the release, TLS 1.3 removed insecure features, and improved both security and performance.
Good
TLS 1.2 supported
Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.
Good
Deprecated protocols not supported
Excellent. This server doesn't support any of the deprecated protocol (TLS 1.1 and earlier).
Good
Strong key exchange detected
Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.
Good
Server prefers forward secrecy and authenticated encryption suites
Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.
Good
Server enforces cipher suite preferences
Excellent. This server enforces server cipher suite preference, which means that it is able to select the best suite from the options submitted by clients. Combined with a well designed list of supported cipher suites, this settings enables negotiation of best security.
Good
All TLS connections with this server satisfy Apple's CT requirements
All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

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: hubspot.com (104.16.117.116)

Encryption protocol version determines what features are
available for negotiation between client and server.
Supported protocols
TLS v1.3
TLS v1.2
Servers should always enforce their own cipher
suite preference, as that is the only approach
that guarantees that the best possible suite is
selected.
Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3
Server preference
Suite: TLS_CHACHA20_POLY1305_SHA256
Suite ID: 0x1303
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_AES_128_GCM_SHA256
Suite ID: 0x1301
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_AES_256_GCM_SHA384
Suite ID: 0x1302
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2
Server preference
Suite: AGL_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcc13
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
AGL_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcca8
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0xc02f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0x9c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_GCM_SHA256
 128 bits
Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x2f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_128_CBC_SHA
 128 bits
Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0x9d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA384
TLS_RSA_WITH_AES_256_GCM_SHA384
 256 bits
Suite: TLS_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x35
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0xc027
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0x3c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_CBC_SHA256
 128 bits
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc028
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_256_CBC_SHA256
Suite ID: 0x3d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_256_CBC_SHA256
 256 bits

Analysis

Good
TLS 1.3 supported
Excellent. This server supports TLS 1.3, which is the latest revision of the TLS protocol and a significant improvement over earlier versions. Developed over a period of several years and extensively analyzed prior to the release, TLS 1.3 removed insecure features, and improved both security and performance.
Good
TLS 1.2 supported
Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.
Good
Deprecated protocols not supported
Excellent. This server doesn't support any of the deprecated protocol (TLS 1.1 and earlier).
Good
Strong key exchange detected
Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.
Good
Server prefers forward secrecy and authenticated encryption suites
Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.
Good
Server enforces cipher suite preferences
Excellent. This server enforces server cipher suite preference, which means that it is able to select the best suite from the options submitted by clients. Combined with a well designed list of supported cipher suites, this settings enables negotiation of best security.
Good
All TLS connections with this server satisfy Apple's CT requirements
All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

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: www.hubspot.com (172.64.148.142)

Encryption protocol version determines what features are
available for negotiation between client and server.
Supported protocols
TLS v1.3
TLS v1.2
Servers should always enforce their own cipher
suite preference, as that is the only approach
that guarantees that the best possible suite is
selected.
Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3
Server preference
Suite: TLS_CHACHA20_POLY1305_SHA256
Suite ID: 0x1303
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_AES_128_GCM_SHA256
Suite ID: 0x1301
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_AES_256_GCM_SHA384
Suite ID: 0x1302
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2
Server preference
Suite: AGL_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcc13
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
AGL_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcca8
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0xc02f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0x9c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_GCM_SHA256
 128 bits
Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x2f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_128_CBC_SHA
 128 bits
Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0x9d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA384
TLS_RSA_WITH_AES_256_GCM_SHA384
 256 bits
Suite: TLS_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x35
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0xc027
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0x3c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_CBC_SHA256
 128 bits
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc028
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_256_CBC_SHA256
Suite ID: 0x3d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_256_CBC_SHA256
 256 bits

Analysis

Good
TLS 1.3 supported
Excellent. This server supports TLS 1.3, which is the latest revision of the TLS protocol and a significant improvement over earlier versions. Developed over a period of several years and extensively analyzed prior to the release, TLS 1.3 removed insecure features, and improved both security and performance.
Good
TLS 1.2 supported
Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.
Good
Deprecated protocols not supported
Excellent. This server doesn't support any of the deprecated protocol (TLS 1.1 and earlier).
Good
Strong key exchange detected
Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.
Good
Server prefers forward secrecy and authenticated encryption suites
Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.
Good
Server enforces cipher suite preferences
Excellent. This server enforces server cipher suite preference, which means that it is able to select the best suite from the options submitted by clients. Combined with a well designed list of supported cipher suites, this settings enables negotiation of best security.
Good
All TLS connections with this server satisfy Apple's CT requirements
All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

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: hubspot.com (2606:4700:0:0:0:0:6810:7674)

Encryption protocol version determines what features are
available for negotiation between client and server.
Supported protocols
TLS v1.3
TLS v1.2
Servers should always enforce their own cipher
suite preference, as that is the only approach
that guarantees that the best possible suite is
selected.
Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3
Server preference
Suite: TLS_CHACHA20_POLY1305_SHA256
Suite ID: 0x1303
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_AES_128_GCM_SHA256
Suite ID: 0x1301
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_AES_256_GCM_SHA384
Suite ID: 0x1302
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2
Server preference
Suite: AGL_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcc13
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
AGL_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcca8
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0xc02f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0x9c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_GCM_SHA256
 128 bits
Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x2f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_128_CBC_SHA
 128 bits
Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0x9d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA384
TLS_RSA_WITH_AES_256_GCM_SHA384
 256 bits
Suite: TLS_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x35
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0xc027
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0x3c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_CBC_SHA256
 128 bits
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc028
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_256_CBC_SHA256
Suite ID: 0x3d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_256_CBC_SHA256
 256 bits

Analysis

Good
TLS 1.3 supported
Excellent. This server supports TLS 1.3, which is the latest revision of the TLS protocol and a significant improvement over earlier versions. Developed over a period of several years and extensively analyzed prior to the release, TLS 1.3 removed insecure features, and improved both security and performance.
Good
TLS 1.2 supported
Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.
Good
Deprecated protocols not supported
Excellent. This server doesn't support any of the deprecated protocol (TLS 1.1 and earlier).
Good
Strong key exchange detected
Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.
Good
Server prefers forward secrecy and authenticated encryption suites
Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.
Good
Server enforces cipher suite preferences
Excellent. This server enforces server cipher suite preference, which means that it is able to select the best suite from the options submitted by clients. Combined with a well designed list of supported cipher suites, this settings enables negotiation of best security.
Good
All TLS connections with this server satisfy Apple's CT requirements
All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

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: www.hubspot.com (104.18.39.114)

Encryption protocol version determines what features are
available for negotiation between client and server.
Supported protocols
TLS v1.3
TLS v1.2
Servers should always enforce their own cipher
suite preference, as that is the only approach
that guarantees that the best possible suite is
selected.
Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3
Server preference
Suite: TLS_CHACHA20_POLY1305_SHA256
Suite ID: 0x1303
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_AES_128_GCM_SHA256
Suite ID: 0x1301
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_AES_256_GCM_SHA384
Suite ID: 0x1302
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2
Server preference
Suite: AGL_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcc13
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
AGL_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcca8
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0xc02f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0x9c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_GCM_SHA256
 128 bits
Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x2f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_128_CBC_SHA
 128 bits
Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0x9d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA384
TLS_RSA_WITH_AES_256_GCM_SHA384
 256 bits
Suite: TLS_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x35
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0xc027
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0x3c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_CBC_SHA256
 128 bits
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc028
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_256_CBC_SHA256
Suite ID: 0x3d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_256_CBC_SHA256
 256 bits

Analysis

Good
TLS 1.3 supported
Excellent. This server supports TLS 1.3, which is the latest revision of the TLS protocol and a significant improvement over earlier versions. Developed over a period of several years and extensively analyzed prior to the release, TLS 1.3 removed insecure features, and improved both security and performance.
Good
TLS 1.2 supported
Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.
Good
Deprecated protocols not supported
Excellent. This server doesn't support any of the deprecated protocol (TLS 1.1 and earlier).
Good
Strong key exchange detected
Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.
Good
Server prefers forward secrecy and authenticated encryption suites
Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.
Good
Server enforces cipher suite preferences
Excellent. This server enforces server cipher suite preference, which means that it is able to select the best suite from the options submitted by clients. Combined with a well designed list of supported cipher suites, this settings enables negotiation of best security.
Good
All TLS connections with this server satisfy Apple's CT requirements
All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

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: hubspot.com (104.16.118.116)

Encryption protocol version determines what features are
available for negotiation between client and server.
Supported protocols
TLS v1.3
TLS v1.2
Servers should always enforce their own cipher
suite preference, as that is the only approach
that guarantees that the best possible suite is
selected.
Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3
Server preference
Suite: TLS_CHACHA20_POLY1305_SHA256
Suite ID: 0x1303
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_AES_128_GCM_SHA256
Suite ID: 0x1301
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_AES_256_GCM_SHA384
Suite ID: 0x1302
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2
Server preference
Suite: AGL_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcc13
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
AGL_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcca8
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0xc02f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0x9c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_GCM_SHA256
 128 bits
Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x2f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_128_CBC_SHA
 128 bits
Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0x9d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA384
TLS_RSA_WITH_AES_256_GCM_SHA384
 256 bits
Suite: TLS_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x35
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0xc027
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0x3c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_CBC_SHA256
 128 bits
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc028
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_256_CBC_SHA256
Suite ID: 0x3d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_256_CBC_SHA256
 256 bits

Analysis

Good
TLS 1.3 supported
Excellent. This server supports TLS 1.3, which is the latest revision of the TLS protocol and a significant improvement over earlier versions. Developed over a period of several years and extensively analyzed prior to the release, TLS 1.3 removed insecure features, and improved both security and performance.
Good
TLS 1.2 supported
Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.
Good
Deprecated protocols not supported
Excellent. This server doesn't support any of the deprecated protocol (TLS 1.1 and earlier).
Good
Strong key exchange detected
Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.
Good
Server prefers forward secrecy and authenticated encryption suites
Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.
Good
Server enforces cipher suite preferences
Excellent. This server enforces server cipher suite preference, which means that it is able to select the best suite from the options submitted by clients. Combined with a well designed list of supported cipher suites, this settings enables negotiation of best security.
Good
All TLS connections with this server satisfy Apple's CT requirements
All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

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: www.hubspot.com (2606:4700:4400:0:0:0:6812:2772)

Encryption protocol version determines what features are
available for negotiation between client and server.
Supported protocols
TLS v1.3
TLS v1.2
Servers should always enforce their own cipher
suite preference, as that is the only approach
that guarantees that the best possible suite is
selected.
Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3
Server preference
Suite: TLS_CHACHA20_POLY1305_SHA256
Suite ID: 0x1303
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_AES_128_GCM_SHA256
Suite ID: 0x1301
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_AES_256_GCM_SHA384
Suite ID: 0x1302
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2
Server preference
Suite: AGL_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcc13
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
AGL_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcca8
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0xc02f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0x9c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_GCM_SHA256
 128 bits
Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x2f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_128_CBC_SHA
 128 bits
Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0x9d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA384
TLS_RSA_WITH_AES_256_GCM_SHA384
 256 bits
Suite: TLS_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x35
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0xc027
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0x3c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_CBC_SHA256
 128 bits
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc028
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_256_CBC_SHA256
Suite ID: 0x3d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_256_CBC_SHA256
 256 bits

Analysis

Good
TLS 1.3 supported
Excellent. This server supports TLS 1.3, which is the latest revision of the TLS protocol and a significant improvement over earlier versions. Developed over a period of several years and extensively analyzed prior to the release, TLS 1.3 removed insecure features, and improved both security and performance.
Good
TLS 1.2 supported
Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.
Good
Deprecated protocols not supported
Excellent. This server doesn't support any of the deprecated protocol (TLS 1.1 and earlier).
Good
Strong key exchange detected
Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.
Good
Server prefers forward secrecy and authenticated encryption suites
Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.
Good
Server enforces cipher suite preferences
Excellent. This server enforces server cipher suite preference, which means that it is able to select the best suite from the options submitted by clients. Combined with a well designed list of supported cipher suites, this settings enables negotiation of best security.
Good
All TLS connections with this server satisfy Apple's CT requirements
All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

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.

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: hubspot.com

Leaf certificate hubspot.com
Issuer: Google Trust Services LLC
Not Before: 03 Apr 2024 04:34:00 UTC
Not After: 02 Jul 2024 04:33:59 UTC (expires in 1 month 13 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
hubspot.com | e60fae5
Not After: 02 Jul 2024 04:33:59 UTC (expires in 1 month 13 days)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Intermediate certificate
GTS CA 1P5 | 97d4200
Not After: 30 Sep 2027 00:00:42 UTC (expires in 3 years 4 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Intermediate certificate
GTS Root R1 | 3ee0278
Not After: 28 Jan 2028 00:00:42 UTC (expires in 3 years 8 months)
Authentication: RSA 4096 bits (SHA256withRSA)
 View details
Root certificate
GlobalSign Root CA | b41b2fb
Not After: 28 Jan 2014 12:00:00 UTC (expired 10 years 3 months ago)
Authentication: RSA 2048 bits (MD5withRSA)
 View details

Analysis

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

Certificate: www.hubspot.com

Leaf certificate www.hubspot.com
Issuer: Google Trust Services LLC
Not Before: 03 May 2024 19:36:55 UTC
Not After: 01 Aug 2024 19:36:54 UTC (expires in 2 months 13 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
 View details

Analysis

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

Certificate Trust

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

Platform Trusted
Apple
Google AOSP
Microsoft
Mozilla

Certificate Chain

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

Leaf certificate
www.hubspot.com | 7d24902
Not After: 01 Aug 2024 19:36:54 UTC (expires in 2 months 13 days)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Intermediate certificate
GTS CA 1P5 | 97d4200
Not After: 30 Sep 2027 00:00:42 UTC (expires in 3 years 4 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Intermediate certificate
GTS Root R1 | 3ee0278
Not After: 28 Jan 2028 00:00:42 UTC (expires in 3 years 8 months)
Authentication: RSA 4096 bits (SHA256withRSA)
 View details
Root certificate
GlobalSign Root CA | b41b2fb
Not After: 28 Jan 2014 12:00:00 UTC (expired 10 years 3 months ago)
Authentication: RSA 2048 bits (MD5withRSA)
 View details

Analysis

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

DANE (443)

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

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

Cookies

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

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

HTTP Cookie: __cfruid

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

Analysis

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

Analysis

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

Mixed Content

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

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

Embedded Resources

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

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

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.

6 link(s)
  6 out of 6 are encrypted  View all