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
Warning
HTTP Strict Transport Security

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

For important sites VERY IMPORTANT medium EFFORT
Not supported
HSTS Preloaded

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

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

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

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

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

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

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

For important sites IMPORTANT low EFFORT
Supported and well configured
DMARC

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

For important sites IMPORTANT low EFFORT

Domain Registration

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

Test passed
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 05:52 UTC
Source https://rdap.verisign.com/com/v1/domain/aol.com
Registrar
Registrar MarkMonitor Inc.
Registrar IANA ID 292
Events
Registration 22 Jun 1995 04:00 UTC
Update 22 Oct 2023 09:10 UTC
Expiration 23 Nov 2024 12:02 UTC
Configuration
Statuses clientDeleteProhibited
clientTransferProhibited
clientUpdateProhibited
serverDeleteProhibited
serverTransferProhibited
serverUpdateProhibited
Registrar Lock
Registry Lock
Nameservers ns1.yahoo.com
ns2.yahoo.com
ns3.yahoo.com
ns4.yahoo.com
ns5.yahoo.com
Contacts
Registrar MarkMonitor Inc.
Abuse Email: abusecomplaints@markmonitor.com
Phone: +1.2086851750

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 Yahoo Assets LLC
Lookup Time 19 May 2024 05:52 UTC
Source whois.markmonitor.com:43
Registrar
Registrar MarkMonitor, Inc.
Registrar IANA ID 292
Events
Registration 22 Jun 1995 04:00 UTC
Update 22 Oct 2023 09:10 UTC
Expiration 23 Nov 2024 00:00 UTC
Configuration
Statuses serverDeleteProhibited
clientTransferProhibited
serverTransferProhibited
clientUpdateProhibited
clientDeleteProhibited
serverUpdateProhibited
Registrar Lock
Registry Lock
Nameservers ns2.yahoo.com
ns1.yahoo.com
ns4.yahoo.com
ns5.yahoo.com
ns3.yahoo.com
Contacts
Registrar MarkMonitor, Inc.
MarkMonitor, Inc.
Abuse Email: abusecomplaints@markmonitor.com
Phone: +1.2086851750
Registrant Yahoo Assets LLC
US
Email: Select Request Email Form at https://domains.markmonitor.com/whois/aol.com
Administrative Yahoo Assets LLC
US
Email: Select Request Email Form at https://domains.markmonitor.com/whois/aol.com
Technical Yahoo Assets LLC
US
Email: Select Request Email Form at https://domains.markmonitor.com/whois/aol.com

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
hidden-master.yahoo.com. STEALTH PRIMARY
68.180.131.16
The server is online. Name resolves to an IPv4 address. Name doesn't resolve to an IPv6 address. SOA
ns1.yahoo.com.
68.180.131.16
2001:4998:1b0::7961:686f:6f21
The server is online. Name resolves to an IPv4 address. Name resolves to an IPv6 address. REFERRAL NS
ns2.yahoo.com.
68.142.255.16
2001:4998:1c0::7961:686f:6f21
The server is online. Name resolves to an IPv4 address. Name resolves to an IPv6 address. REFERRAL NS
ns3.yahoo.com.
27.123.42.42
2406:8600:f03f:1f8::1003
The server is online. Name resolves to an IPv4 address. Name resolves to an IPv6 address. REFERRAL NS
ns4.yahoo.com.
98.138.11.157
The server is online. Name resolves to an IPv4 address. Name doesn't resolve to an IPv6 address. REFERRAL NS
ns5.yahoo.com.
202.165.97.53
2406:2000:1d0::7961:686f:6f21
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
202.165.97.53
ns5.yahoo.com.
PTR: ns5.yahoo.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 1272
27.123.42.42
ns3.yahoo.com.
PTR: ns3.yahoo.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 1272
68.142.255.16
ns2.yahoo.com.
PTR: ns2.yahoo.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 1272
68.180.131.16 PRIMARY
hidden-master.yahoo.com.
ns1.yahoo.com.
PTR: ns1.yahoo.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 1272
98.138.11.157
ns4.yahoo.com.
PTR: ns4.yahoo.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 1272
2001:4998:1b0::7961:686f:6f21
ns1.yahoo.com.
PTR: ns1.yahoo.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 1272
2001:4998:1c0::7961:686f:6f21
ns2.yahoo.com.
PTR: ns2.yahoo.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 1272
2406:2000:1d0::7961:686f:6f21
ns5.yahoo.com.
PTR: ns5.yahoo.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 1272
2406:8600:f03f:1f8::1003
ns3.yahoo.com.
PTR: ns3.yahoo.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 1272

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 hidden-master.yahoo.com.
Email address of the persons responsible for this zone. Also known as RNAME.Admin email hostmaster.yahoo-inc.com.
Zone serial or version number.Serial number 2024051601
The length of time secondary nameservers should wait before querying the primary for changes.Refresh interval 28,800 seconds (about 8 hours)
The length of time secondary nameservers should wait before querying an unresponsive primary again.Retry interval 900 seconds (about 15 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 600 seconds (about 10 minutes)
Time To Live (TTL) indicates for how long a record remains valid. SOA record TTL 3,600 seconds (about 1 hour)

Analysis

Powerup!
Improve IPv6 support
The Internet is in a slow transition to supporting IPv6 widely. Although at this time it is expected that most recursive DNS servers will use IPv4, adding support for IPv6 will enable transition to networks that use IPv6 exclusively.
Good
No problems detected with the zone configuration
Excellent. This DNS zone is in a good working order. No problems detected.

Backing DNS Queries

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

ID Server Transport Question Name Type Status

DNS Records

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

Test failed
We've detected serious problems that require your immediate attention.

DNS Records

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

Name TTL Type Data
aol.com.     3600 A 13.248.158.7            
aol.com.     3600 A 76.223.84.192            
www.aol.com.     30 CNAME edge.gycpi.b.yahoodns.net.            
edge.gycpi.b.yahoodns.net.     60 A 69.147.92.12            
edge.gycpi.b.yahoodns.net.     60 A 69.147.92.11            
edge.gycpi.b.yahoodns.net.     60 AAAA 2001:4998:14:800:0:0:0:1000            
edge.gycpi.b.yahoodns.net.     60 AAAA 2001:4998:14:800:0:0:0:1001            
aol.com.     3600 CAA 0 issue "globalsign.com"            
aol.com.     3600 CAA 0 issue "digicert.com"            
aol.com.     3600 CAA 0 iodef "mailto:security@yahooinc.com"            
aol.com.     3600 MX 10 mx-aol.mail.gm0.yahoodns.net.            
aol.com.     172800 NS ns1.yahoo.com.            
aol.com.     172800 NS ns4.yahoo.com.            
aol.com.     172800 NS ns3.yahoo.com.            
aol.com.     172800 NS ns2.yahoo.com.            
aol.com.     172800 NS ns5.yahoo.com.            
aol.com.     3600 SOA hidden-master.yahoo.com. hostmaster.yahoo-inc.com. 2024051601 28800 900 604800 600            
_sipfederationtls._tcp.aol.com.     3600 SRV 0 1 5061 sip.oscar.aol.com.            
_xmpp-server._tcp.aol.com.     300 SRV 10 1 5269 nxpfs.ucfederationcloud.com.            
aol.com.     3600 TXT "v=spf1 redirect=_spf.mail.yahoo.com"            
aol.com.     3600 TXT "'4a751cdeec084ee2bc9e2cb2e94ba8af'"            
aol.com.     3600 TXT "google-site-verification=vWa8DccevgR6DN9S4K4ydAcrlRn7SCXHx6sQRmqElLc"            
aol.com.     3600 TXT "knowbe4-site-verification=bc3830115833f4f956e30f506f1da8c8"            
aol.com.     3600 TXT "google-site-verification=NqM_NKWhteDHiJCOfhlQqKT4nxexIeFRie5MmWA1RBk"            
aol.com.     3600 TXT "facebook-domain-verification=ervjrx9gun9l4uhc6o4d05p65r2824"            
aol.com.     3600 TXT "google-site-verification=Urd7MSITHYcx-rtP1PTVfeiC8RZ2QaKF_6bd6mW_51U"            
aol.com.     3600 TXT "google-site-verification=BNb5wrsmDzzWz2SS35sCfIYkrZOQWWY-3ZdY-pgip4k"            
aol.com.     3600 TXT "google-site-verification=ducLuHpystFIiiH_U1devs1CL3q7nhkjCV3BQQtxwWM"            
aol.com.     3600 TXT "google-site-verification=rrvUvV8gUjL0YugQKfcRVnaeQSBJT50UYL_CRwTdKAc"            
aol.com.     3600 TXT "_globalsign-domain-verification=W22K-ATZWdBDmzMIsFCF5smJ_T5-7Zl-JDnV8qNe-i"            
_dmarc.aol.com.     3600 TXT "v=DMARC1; p=reject; pct=100; rua=mailto:d@rua.agari.com; ruf=mailto:d@ruf.agari.com;"            

Analysis

Error
Dangling DNS configuration
We've detected a dangling DNS configuration that may be vulnerable to takeover. This problem most commonly occurs with CNAME records that point to another name that is subsequently deleted, creating a subdomain takeover vulnerability. Similar problems are possible with other records, for example MX, SRV, and HTTPS.

Error: Dangling DNS record: _sipfederationtls._tcp.aol.com./SRV (destination: sip.oscar.aol.com.)

Backing DNS Queries

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

ID Server Question Name Type Status

DNSSEC

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

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

Useful DNSSEC Tools

Certification Authority Authorization

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

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

CAA Policy Information

The DNS hostname where this policy is located.Policy host aol.com
The iodef property specifies a means of reporting certificate
issue requests or cases of certificate issue for the corresponding
domain that violate the security policy of the issuer or the domain
name holder.
iodef
mailto:security@yahooinc.com  flags: 0
The issue property tag is used to request that certificate
issuers perform CAA issue restriction processing for the domain
and to grant authorization to specific certificate issuers.
issue
globalsign.com  flags: 0
The issue property tag is used to request that certificate
issuers perform CAA issue restriction processing for the domain
and to grant authorization to specific certificate issuers.
issue
digicert.com  flags: 0

Analysis

Good
CAA policy found
Good. This domain name uses CAA to restrict which CAs are allowed to issue certificates for it.
Good
Policy uses reporting
Great. This policy uses reporting, which means that your contact information is available should someone need to contact you about a CAA violation. Do note that you're not guaranteed to be notified, given that CAs generally don't support notifications yet.

Email (SMTP)

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

Test passed
Everything seems to be well configured. Well done.
Some TLS and PKI information shown may have been retrieved from cache. The notes provide more information.
Server Preference Operational STARTTLS TLS PKI DNSSEC DANE
mx-aol.mail.gm0.yahoodns.net
67.195.204.75
PTR: mtaproxy1.aol.mail.vip.bf1.yahoo.com
10
220 mtaproxy124.aol.mail.bf1.yahoo.com ESMTP ready

EHLO outbound.hardenize.com
250-mtaproxy124.aol.mail.bf1.yahoo.com
250-PIPELINING
250-SIZE 41943040
250-8BITMIME
250 STARTTLS

STARTTLS
220 Ready for TLS
Supports STARTTLS. Not supported. Not applicable,
requires TLS.
mx-aol.mail.gm0.yahoodns.net
98.136.96.92
PTR: mtaproxy1.aol.mail.vip.ne1.yahoo.com
10
220 mtaproxy115.aol.mail.ne1.yahoo.com ESMTP ready

EHLO outbound.hardenize.com
250-mtaproxy115.aol.mail.ne1.yahoo.com
250-PIPELINING
250-SIZE 41943040
250-8BITMIME
250 STARTTLS

STARTTLS
220 Ready for TLS
Supports STARTTLS. Not supported. Not applicable,
requires TLS.
mx-aol.mail.gm0.yahoodns.net
67.195.228.84
PTR: mtaproxy2.aol.mail.vip.gq1.yahoo.com
10
220 mtaproxy204.aol.mail.gq1.yahoo.com ESMTP ready

EHLO outbound.hardenize.com
250-mtaproxy204.aol.mail.gq1.yahoo.com
250-PIPELINING
250-SIZE 41943040
250-8BITMIME
250 STARTTLS

STARTTLS
220 Ready for TLS
Supports STARTTLS. Not supported. Not applicable,
requires TLS.
mx-aol.mail.gm0.yahoodns.net
67.195.204.80
PTR: mtaproxy2.aol.mail.vip.bf1.yahoo.com
10
220 mtaproxy216.aol.mail.bf1.yahoo.com ESMTP ready

EHLO outbound.hardenize.com
250-mtaproxy216.aol.mail.bf1.yahoo.com
250-PIPELINING
250-SIZE 41943040
250-8BITMIME
250 STARTTLS

STARTTLS
220 Ready for TLS
Supports STARTTLS. Not supported. Not applicable,
requires TLS.
mx-aol.mail.gm0.yahoodns.net
67.195.228.86
PTR: mtaproxy1.aol.mail.vip.gq1.yahoo.com
10
220 mtaproxy110.aol.mail.gq1.yahoo.com ESMTP ready

EHLO outbound.hardenize.com
250-mtaproxy110.aol.mail.gq1.yahoo.com
250-PIPELINING
250-SIZE 41943040
250-8BITMIME
250 STARTTLS

STARTTLS
220 Ready for TLS
Supports STARTTLS. Not supported. Not applicable,
requires TLS.
mx-aol.mail.gm0.yahoodns.net
98.136.96.93
PTR: mtaproxy2.aol.mail.vip.ne1.yahoo.com
10
220 mtaproxy210.aol.mail.ne1.yahoo.com ESMTP ready

EHLO outbound.hardenize.com
250-mtaproxy210.aol.mail.ne1.yahoo.com
250-PIPELINING
250-SIZE 41943040
250-8BITMIME
250 STARTTLS

STARTTLS
220 Ready for TLS
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 23:15 UTC

Earliest cache timestamp: 13 May 2024 23:15 UTC

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

Email TLS (SMTP)

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

Test passed
Everything seems to be well configured. Well done.
Some TLS and PKI information shown may have been retrieved from cache. The notes provide more information.

TLS Configuration: mx-aol.mail.gm0.yahoodns.net (67.195.204.75) 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_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)
These results have been retrieved from
our cache. This row indicates when was
that the original test ran.
Retrieved from cache
13 May 2024 23:15 UTC

Analysis

Good
TLS 1.2 supported
Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.
Good
Strong key exchange detected
Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.
Notice
Partial results shown
SMTP assessments usually take a long time. To get you some results faster, we initially perform shallow checks. If you come back later we may be able to show you complete results.
Notice
Relaxed TLS assessment criteria applied to SMTP on port 25
We apply relaxed assessment criteria when evaluating TLS configuration of SMTP servers on port 25. This is because most delivery agents fall back to delivering via plaintext on failure to negotiate encryption. Some configuration elements that can be abused to attack other ports and protocols (e.g., SSLv2 and export cipher suites) are penalized in the same way as for other protocols. We will review this policy in the future.

TLS Configuration: mx-aol.mail.gm0.yahoodns.net (98.136.96.92) 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_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)
These results have been retrieved from
our cache. This row indicates when was
that the original test ran.
Retrieved from cache
13 May 2024 23:15 UTC

Analysis

Good
TLS 1.2 supported
Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.
Good
Strong key exchange detected
Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.
Notice
Partial results shown
SMTP assessments usually take a long time. To get you some results faster, we initially perform shallow checks. If you come back later we may be able to show you complete results.
Notice
Relaxed TLS assessment criteria applied to SMTP on port 25
We apply relaxed assessment criteria when evaluating TLS configuration of SMTP servers on port 25. This is because most delivery agents fall back to delivering via plaintext on failure to negotiate encryption. Some configuration elements that can be abused to attack other ports and protocols (e.g., SSLv2 and export cipher suites) are penalized in the same way as for other protocols. We will review this policy in the future.

TLS Configuration: mx-aol.mail.gm0.yahoodns.net (67.195.228.84) 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_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)
These results have been retrieved from
our cache. This row indicates when was
that the original test ran.
Retrieved from cache
13 May 2024 23:15 UTC

Analysis

Good
TLS 1.2 supported
Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.
Good
Strong key exchange detected
Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.
Notice
Partial results shown
SMTP assessments usually take a long time. To get you some results faster, we initially perform shallow checks. If you come back later we may be able to show you complete results.
Notice
Relaxed TLS assessment criteria applied to SMTP on port 25
We apply relaxed assessment criteria when evaluating TLS configuration of SMTP servers on port 25. This is because most delivery agents fall back to delivering via plaintext on failure to negotiate encryption. Some configuration elements that can be abused to attack other ports and protocols (e.g., SSLv2 and export cipher suites) are penalized in the same way as for other protocols. We will review this policy in the future.

TLS Configuration: mx-aol.mail.gm0.yahoodns.net (67.195.204.80) 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_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)
These results have been retrieved from
our cache. This row indicates when was
that the original test ran.
Retrieved from cache
13 May 2024 23:15 UTC

Analysis

Good
TLS 1.2 supported
Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.
Good
Strong key exchange detected
Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.
Notice
Partial results shown
SMTP assessments usually take a long time. To get you some results faster, we initially perform shallow checks. If you come back later we may be able to show you complete results.
Notice
Relaxed TLS assessment criteria applied to SMTP on port 25
We apply relaxed assessment criteria when evaluating TLS configuration of SMTP servers on port 25. This is because most delivery agents fall back to delivering via plaintext on failure to negotiate encryption. Some configuration elements that can be abused to attack other ports and protocols (e.g., SSLv2 and export cipher suites) are penalized in the same way as for other protocols. We will review this policy in the future.

TLS Configuration: mx-aol.mail.gm0.yahoodns.net (67.195.228.86) 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_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)
These results have been retrieved from
our cache. This row indicates when was
that the original test ran.
Retrieved from cache
13 May 2024 23:15 UTC

Analysis

Good
TLS 1.2 supported
Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.
Good
Strong key exchange detected
Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.
Notice
Partial results shown
SMTP assessments usually take a long time. To get you some results faster, we initially perform shallow checks. If you come back later we may be able to show you complete results.
Notice
Relaxed TLS assessment criteria applied to SMTP on port 25
We apply relaxed assessment criteria when evaluating TLS configuration of SMTP servers on port 25. This is because most delivery agents fall back to delivering via plaintext on failure to negotiate encryption. Some configuration elements that can be abused to attack other ports and protocols (e.g., SSLv2 and export cipher suites) are penalized in the same way as for other protocols. We will review this policy in the future.

TLS Configuration: mx-aol.mail.gm0.yahoodns.net (98.136.96.93) 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_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)
These results have been retrieved from
our cache. This row indicates when was
that the original test ran.
Retrieved from cache
13 May 2024 23:15 UTC

Analysis

Good
TLS 1.2 supported
Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.
Good
Strong key exchange detected
Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.
Notice
Partial results shown
SMTP assessments usually take a long time. To get you some results faster, we initially perform shallow checks. If you come back later we may be able to show you complete results.
Notice
Relaxed TLS assessment criteria applied to SMTP on port 25
We apply relaxed assessment criteria when evaluating TLS configuration of SMTP servers on port 25. This is because most delivery agents fall back to delivering via plaintext on failure to negotiate encryption. Some configuration elements that can be abused to attack other ports and protocols (e.g., SSLv2 and export cipher suites) are penalized in the same way as for other protocols. We will review this policy in the future.

Email Certificates (SMTP)

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

Test passed
Everything seems to be well configured. Well done.
Some TLS and PKI information shown may have been retrieved from cache. The notes provide more information.

Certificate #1  Cached

Leaf certificate *.mail.am0.yahoodns.net
Issuer: DigiCert
Not Before: 02 Jan 2024 00:00:00 UTC
Not After: 26 Jun 2024 23:59:59 UTC (expires in 1 month 7 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
 View details

Analysis

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

Certificate Chain

Leaf certificate
*.mail.am0.yahoodns.net | 73a668d
Not After: 26 Jun 2024 23:59:59 UTC (expires in 1 month 7 days)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Intermediate certificate
DigiCert SHA2 High Assurance Server CA | 19400be
Not After: 22 Oct 2028 12:00:00 UTC (expires in 4 years 5 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Root certificate
DigiCert High Assurance EV Root CA | 7431e5f
Not After: 10 Nov 2031 00:00:00 UTC (expires in 7 years 5 months)
Authentication: RSA 2048 bits (SHA1withRSA)
 View details

Analysis

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

Email DANE (SMTP)

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

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

SPF

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

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

SPF Policy Information Main policy

Host where this policy is located.Location aol.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
_spf.mail.yahoo.com

Analysis

Info
SPF policy found

Policy text: v=spf1 redirect=_spf.mail.yahoo.com

Location: aol.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: 3

SPF Policy Information Included policy

Host where this policy is located.Location _spf.mail.yahoo.com
SPF version used by this policy.v spf1
This mechanism tests whether the DNS reverse-mapping
for the tested IP address exists and correctly points
to a domain name within a particular domain.
ptr
yahoo.com
This mechanism tests whether the DNS reverse-mapping
for the tested IP address exists and correctly points
to a domain name within a particular domain.
ptr
yahoo.net
This policy element always matches. It's normally used
at the end of a policy to specify the handling of hosts
that don't match earlier mechanisms.
?all

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.aol.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:d@rua.agari.com
Addresses to which message-specific failure
information is to be reported.
ruf
mailto:d@ruf.agari.com

Analysis

Info
DMARC policy found

Policy: v=DMARC1; p=reject; pct=100; rua=mailto:d@rua.agari.com; ruf=mailto:d@ruf.agari.com;

Host: _dmarc.aol.com

Good
Valid external destination

Permission record location: aol.com._report._dmarc.ruf.agari.com

External destination: mailto:d@ruf.agari.com

Permission record contents: v=DMARC1;

Good
Valid external destination

Permission record location: aol.com._report._dmarc.rua.agari.com

External destination: mailto:d@rua.agari.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://aol.com/

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

Analysis

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

URL: http://www.aol.com/

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

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

URL: https://www.aol.com/

1
https://www.aol.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.aol.com (2001:4998:14:800:0:0:0:1001)

Encryption protocol version determines what features are
available for negotiation between client and server.
Supported protocols
TLS v1.3
TLS v1.2
TLS v1.1
TLS v1.0
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_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)
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)
Shows cipher suite configuration for this protocol version.TLS v1.2
Server preference
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
Suite ID: 0xc02b
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc02c
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcca9
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcca8
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0xc02f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
Suite ID: 0xc023
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc024
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc009
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc00a
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_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_ECDHE_RSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc028
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0x9c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_GCM_SHA256
 128 bits
Suite: TLS_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0x9d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA384
TLS_RSA_WITH_AES_256_GCM_SHA384
 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: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_CBC_SHA256
 128 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: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_256_CBC_SHA256
 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: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Shows cipher suite configuration for this protocol version.TLS v1.1
Server preference
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc009
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc00a
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_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: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Shows cipher suite configuration for this protocol version.TLS v1.0
Server preference
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc009
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc00a
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_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: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits

Analysis

Notice
Deprecated protocols supported
TLS 1.0 and TLS 1.1 are deprecated protocols that should be disabled if possible. TLS 1.0, in particular, is a weak older protocol that has many weaknesses. Sites that aim at a wide audience might still need to support TLS 1.0 for the time being, because many older clients don't support newer protocol versions. Sites with a modern user base might be able to disable TLS 1.0 even now. We recommend that you enable logging of encryption parameters, after which you can examine your protocol usage and make a decision with confidence. As of July 2018, PCI DSS doesn't allow use of TLS 1.0. Exceptions apply in some cases.
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
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: aol.com (76.223.84.192)

Encryption protocol version determines what features are
available for negotiation between client and server.
Supported protocols
TLS v1.3
TLS v1.2
TLS v1.1
TLS v1.0
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_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)
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)
Shows cipher suite configuration for this protocol version.TLS v1.2
Server preference
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
Suite ID: 0xc02b
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc02c
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcca9
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcca8
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0xc02f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
Suite ID: 0xc023
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc024
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc009
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc00a
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_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_ECDHE_RSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc028
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0x9c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_GCM_SHA256
 128 bits
Suite: TLS_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0x9d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA384
TLS_RSA_WITH_AES_256_GCM_SHA384
 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: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_CBC_SHA256
 128 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: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_256_CBC_SHA256
 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: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Shows cipher suite configuration for this protocol version.TLS v1.1
Server preference
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc009
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc00a
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_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: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Shows cipher suite configuration for this protocol version.TLS v1.0
Server preference
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc009
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc00a
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_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: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits

Analysis

Notice
Deprecated protocols supported
TLS 1.0 and TLS 1.1 are deprecated protocols that should be disabled if possible. TLS 1.0, in particular, is a weak older protocol that has many weaknesses. Sites that aim at a wide audience might still need to support TLS 1.0 for the time being, because many older clients don't support newer protocol versions. Sites with a modern user base might be able to disable TLS 1.0 even now. We recommend that you enable logging of encryption parameters, after which you can examine your protocol usage and make a decision with confidence. As of July 2018, PCI DSS doesn't allow use of TLS 1.0. Exceptions apply in some cases.
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
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.aol.com (2001:4998:14:800:0:0:0:1000)

Encryption protocol version determines what features are
available for negotiation between client and server.
Supported protocols
TLS v1.3
TLS v1.2
TLS v1.1
TLS v1.0
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_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)
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)
Shows cipher suite configuration for this protocol version.TLS v1.2
Server preference
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
Suite ID: 0xc02b
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc02c
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcca9
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcca8
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0xc02f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
Suite ID: 0xc023
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc024
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc009
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc00a
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_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_ECDHE_RSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc028
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0x9c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_GCM_SHA256
 128 bits
Suite: TLS_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0x9d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA384
TLS_RSA_WITH_AES_256_GCM_SHA384
 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: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_CBC_SHA256
 128 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: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_256_CBC_SHA256
 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: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Shows cipher suite configuration for this protocol version.TLS v1.1
Server preference
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc009
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc00a
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_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: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Shows cipher suite configuration for this protocol version.TLS v1.0
Server preference
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc009
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc00a
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_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: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits

Analysis

Notice
Deprecated protocols supported
TLS 1.0 and TLS 1.1 are deprecated protocols that should be disabled if possible. TLS 1.0, in particular, is a weak older protocol that has many weaknesses. Sites that aim at a wide audience might still need to support TLS 1.0 for the time being, because many older clients don't support newer protocol versions. Sites with a modern user base might be able to disable TLS 1.0 even now. We recommend that you enable logging of encryption parameters, after which you can examine your protocol usage and make a decision with confidence. As of July 2018, PCI DSS doesn't allow use of TLS 1.0. Exceptions apply in some cases.
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
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.aol.com (69.147.92.11)

Encryption protocol version determines what features are
available for negotiation between client and server.
Supported protocols
TLS v1.3
TLS v1.2
TLS v1.1
TLS v1.0
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_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)
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)
Shows cipher suite configuration for this protocol version.TLS v1.2
Server preference
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
Suite ID: 0xc02b
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc02c
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcca9
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcca8
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0xc02f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
Suite ID: 0xc023
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc024
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc009
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc00a
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_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_ECDHE_RSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc028
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0x9c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_GCM_SHA256
 128 bits
Suite: TLS_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0x9d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA384
TLS_RSA_WITH_AES_256_GCM_SHA384
 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: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_CBC_SHA256
 128 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: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_256_CBC_SHA256
 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: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Shows cipher suite configuration for this protocol version.TLS v1.1
Server preference
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc009
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc00a
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_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: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Shows cipher suite configuration for this protocol version.TLS v1.0
Server preference
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc009
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc00a
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_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: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits

Analysis

Notice
Deprecated protocols supported
TLS 1.0 and TLS 1.1 are deprecated protocols that should be disabled if possible. TLS 1.0, in particular, is a weak older protocol that has many weaknesses. Sites that aim at a wide audience might still need to support TLS 1.0 for the time being, because many older clients don't support newer protocol versions. Sites with a modern user base might be able to disable TLS 1.0 even now. We recommend that you enable logging of encryption parameters, after which you can examine your protocol usage and make a decision with confidence. As of July 2018, PCI DSS doesn't allow use of TLS 1.0. Exceptions apply in some cases.
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
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.aol.com (69.147.92.12)

Encryption protocol version determines what features are
available for negotiation between client and server.
Supported protocols
TLS v1.3
TLS v1.2
TLS v1.1
TLS v1.0
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_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)
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)
Shows cipher suite configuration for this protocol version.TLS v1.2
Server preference
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
Suite ID: 0xc02b
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc02c
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcca9
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcca8
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0xc02f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
Suite ID: 0xc023
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc024
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc009
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc00a
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_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_ECDHE_RSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc028
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0x9c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_GCM_SHA256
 128 bits
Suite: TLS_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0x9d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA384
TLS_RSA_WITH_AES_256_GCM_SHA384
 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: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_CBC_SHA256
 128 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: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_256_CBC_SHA256
 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: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Shows cipher suite configuration for this protocol version.TLS v1.1
Server preference
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc009
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc00a
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_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: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Shows cipher suite configuration for this protocol version.TLS v1.0
Server preference
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc009
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc00a
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_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: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits

Analysis

Notice
Deprecated protocols supported
TLS 1.0 and TLS 1.1 are deprecated protocols that should be disabled if possible. TLS 1.0, in particular, is a weak older protocol that has many weaknesses. Sites that aim at a wide audience might still need to support TLS 1.0 for the time being, because many older clients don't support newer protocol versions. Sites with a modern user base might be able to disable TLS 1.0 even now. We recommend that you enable logging of encryption parameters, after which you can examine your protocol usage and make a decision with confidence. As of July 2018, PCI DSS doesn't allow use of TLS 1.0. Exceptions apply in some cases.
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
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: aol.com (13.248.158.7)

Encryption protocol version determines what features are
available for negotiation between client and server.
Supported protocols
TLS v1.3
TLS v1.2
TLS v1.1
TLS v1.0
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_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)
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)
Shows cipher suite configuration for this protocol version.TLS v1.2
Server preference
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
Suite ID: 0xc02b
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc02c
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcca9
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcca8
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0xc02f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
Suite ID: 0xc023
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc024
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc009
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc00a
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_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_ECDHE_RSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc028
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0x9c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_GCM_SHA256
 128 bits
Suite: TLS_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0x9d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA384
TLS_RSA_WITH_AES_256_GCM_SHA384
 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: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_CBC_SHA256
 128 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: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_256_CBC_SHA256
 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: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Shows cipher suite configuration for this protocol version.TLS v1.1
Server preference
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc009
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc00a
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_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: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Shows cipher suite configuration for this protocol version.TLS v1.0
Server preference
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc009
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc00a
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_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: 4096 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits

Analysis

Notice
Deprecated protocols supported
TLS 1.0 and TLS 1.1 are deprecated protocols that should be disabled if possible. TLS 1.0, in particular, is a weak older protocol that has many weaknesses. Sites that aim at a wide audience might still need to support TLS 1.0 for the time being, because many older clients don't support newer protocol versions. Sites with a modern user base might be able to disable TLS 1.0 even now. We recommend that you enable logging of encryption parameters, after which you can examine your protocol usage and make a decision with confidence. As of July 2018, PCI DSS doesn't allow use of TLS 1.0. Exceptions apply in some cases.
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
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: aol.com

Leaf certificate src6.yahoo.com
Issuer: DigiCert
Not Before: 02 May 2024 00:00:00 UTC
Not After: 09 Oct 2024 23:59:59 UTC (expires in 4 months 20 days)
Key: RSA 4096 bits
Signature: SHA256withRSA
 View details

Analysis

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

Certificate Trust

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

Platform Trusted
Apple
Google AOSP
Microsoft
Mozilla

Certificate Chain

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

Leaf certificate
src6.yahoo.com | a9897f5
Not After: 09 Oct 2024 23:59:59 UTC (expires in 4 months 20 days)
Authentication: RSA 4096 bits (SHA256withRSA)
 View details
Intermediate certificate
DigiCert SHA2 High Assurance Server CA | 19400be
Not After: 22 Oct 2028 12:00:00 UTC (expires in 4 years 5 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Root certificate
DigiCert High Assurance EV Root CA | 7431e5f
Not After: 10 Nov 2031 00:00:00 UTC (expires in 7 years 5 months)
Authentication: RSA 2048 bits (SHA1withRSA)
 View details

Analysis

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

Certificate: www.aol.com

Leaf certificate jp.techcrunch.com
Issuer: DigiCert
Not Before: 09 May 2024 00:00:00 UTC
Not After: 07 Aug 2024 23:59:59 UTC (expires in 2 months 19 days)
Key: EC 256 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
jp.techcrunch.com | 384d4e8
Not After: 07 Aug 2024 23:59:59 UTC (expires in 2 months 19 days)
Authentication: EC 256 bits (SHA256withRSA)
 View details
Intermediate certificate
DigiCert SHA2 High Assurance Server CA | 19400be
Not After: 22 Oct 2028 12:00:00 UTC (expires in 4 years 5 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Root certificate
DigiCert High Assurance EV Root CA | 7431e5f
Not After: 10 Nov 2031 00:00:00 UTC (expires in 7 years 5 months)
Authentication: RSA 2048 bits (SHA1withRSA)
 View details

Analysis

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

Certificate: www.aol.com

Leaf certificate jp.techcrunch.com
Issuer: DigiCert
Not Before: 09 May 2024 00:00:00 UTC
Not After: 07 Aug 2024 23:59:59 UTC (expires in 2 months 19 days)
Key: RSA 4096 bits
Signature: SHA256withRSA
 View details

Analysis

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

Certificate Trust

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

Platform Trusted
Apple
Google AOSP
Microsoft
Mozilla

Certificate Chain

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

Leaf certificate
jp.techcrunch.com | 5251570
Not After: 07 Aug 2024 23:59:59 UTC (expires in 2 months 19 days)
Authentication: RSA 4096 bits (SHA256withRSA)
 View details
Intermediate certificate
DigiCert SHA2 High Assurance Server CA | 19400be
Not After: 22 Oct 2028 12:00:00 UTC (expires in 4 years 5 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Root certificate
DigiCert High Assurance EV Root CA | 7431e5f
Not After: 10 Nov 2031 00:00:00 UTC (expires in 7 years 5 months)
Authentication: RSA 2048 bits (SHA1withRSA)
 View details

Analysis

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

Certificate: aol.com

Leaf certificate src6.yahoo.com
Issuer: DigiCert
Not Before: 02 May 2024 00:00:00 UTC
Not After: 09 Oct 2024 23:59:59 UTC (expires in 4 months 20 days)
Key: EC 256 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
src6.yahoo.com | 7270b5c
Not After: 09 Oct 2024 23:59:59 UTC (expires in 4 months 20 days)
Authentication: EC 256 bits (SHA256withRSA)
 View details
Intermediate certificate
DigiCert SHA2 High Assurance Server CA | 19400be
Not After: 22 Oct 2028 12:00:00 UTC (expires in 4 years 5 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Root certificate
DigiCert High Assurance EV Root CA | 7431e5f
Not After: 10 Nov 2031 00:00:00 UTC (expires in 7 years 5 months)
Authentication: RSA 2048 bits (SHA1withRSA)
 View details

Analysis

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

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

Cookie value. As far as the cookie RFC is concerned, the value
is an opaque string which only the application should interpret.
Value
d=AQABBKKTSWYCEA5EgN_zWjF_mHxgDqX53MUFEgEBAQHlSmZTZtxS0iMA_eMAAA&S=AQAAAte7GE-nTfuDl3-HMqui5Wo
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
aol.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
lax

Analysis

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

HTTP Cookie: A1

Cookie value. As far as the cookie RFC is concerned, the value
is an opaque string which only the application should interpret.
Value
d=AQABBKKTSWYCEA5EgN_zWjF_mHxgDqX53MUFEgEBAQHlSmZTZtxS0iMA_eMAAA&S=AQAAAte7GE-nTfuDl3-HMqui5Wo
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
aol.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
/
Cookies are designed to always expire. Session cookies
are truly ephemeral and remain cached until the browser
is closed. The Expires and Max-Age cookie attributes can
be used to specify that a cookie should stay alive for
longer.
Expires
Mon May 19 11:52:37 UTC 2025 (1 year 5 hours)
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
lax

Analysis

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

HTTP Cookie: A3

Cookie value. As far as the cookie RFC is concerned, the value
is an opaque string which only the application should interpret.
Value
d=AQABBKKTSWYCEA5EgN_zWjF_mHxgDqX53MUFEgEBAQHlSmZTZtxS0iMA_eMAAA&S=AQAAAte7GE-nTfuDl3-HMqui5Wo
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
aol.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
/
Cookies are designed to always expire. Session cookies
are truly ephemeral and remain cached until the browser
is closed. The Expires and Max-Age cookie attributes can
be used to specify that a cookie should stay alive for
longer.
Expires
Mon May 19 11:52:37 UTC 2025 (1 year 5 hours)
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.

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

0 link(s)
  0 out of 0 are encrypted

HTTP Strict Transport Security

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

Test passed, but there are warnings
Some aspect of your site's configuration require your attention.

HSTS Policy  Main host

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

Analysis

Good
Policy is valid
OK. Your HSTS policy uses correct syntax.
Good
Long policy age
Your HSTS policy has a long max-age value, which offers better protection.
Powerup!
No subdomains
This HSTS policy doesn't cover subdomains. Without full coverage, HSTS can't protect from certain cookie attacks that typically allow active network attackers to inject cookies into an application. Additionally, subdomain coverage is one of the requirements to allow preloading.
Notice
Preload directive has no effect here
This policy doesn't enable preloading, but that's all right. The preload directive doesn't have any effect unless it's used on an apex hostname.
Good
Redirection from HTTP to HTTPS to the same host
Good. The redirection from HTTP to HTTPS is to the same host. This approach ensures that HSTS is activated on the hostname when it's accessed via plaintext.
Powerup!
No parent protection
This host could benefit from further protection if the apex hostname would be configured with a HSTS policy that uses 'includeSubDomains'. Enabling HSTS on an entire domain name is the only approach that provides robust security.

HSTS Policy  Apex host

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

Analysis

Good
Policy is valid
OK. Your HSTS policy uses correct syntax.
Good
Long policy age
Your HSTS policy has a long max-age value, which offers better protection.
Powerup!
No subdomains
This HSTS policy doesn't cover subdomains. Without full coverage, HSTS can't protect from certain cookie attacks that typically allow active network attackers to inject cookies into an application. Additionally, subdomain coverage is one of the requirements to allow preloading.
Powerup!
Preloading not enabled
This policy doesn't give browsers permission to embed it and provide protection even to the first request to the web site. Sites that wish to use preloading can apply at hstspreload.org.
Warning
Redirection from HTTP to HTTPS not to the same host
When HSTS is used, the plaintext port should redirect to the HTTPS variant of the same hostname. This approach ensures that HSTS is enabled on that hostname, even if later the client is sent elsewhere. A redirection to another host is only safe if it is for a parent host that has HSTS with includeSubDomains enabled, but that's not the case here.

Starting point: http://aol.com

Current redirection: https://www.aol.com/

Expected redirection: https://aol.com

HTTP Public Key Pinning

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

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

Content Security Policy

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

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

content-security-policy

upgrade-insecure-requests
block-all-mixed-content -
sandbox allow-modals   allow-forms   allow-same-origin   allow-scripts   allow-popups   allow-popups-to-escape-sandbox   allow-presentation   allow-orientation-lock   allow-pointer-lock  

Analysis

Good
Mixed content upgraded
Good. This CSP policy instructs browsers to seamlessly upgrade plaintext resources to encryption.
Good
All mixed content is blocked
Good. This CSP policy blocks all mixed content, which includes insecure images that browsers allow.
Powerup!
Form targets not restricted
The 'form-action' directive is not explicitly set. Because this directive doesn't fall back to default sources, this means that all targets are allowed.

Analysis

Info
CSP policy detected

Header: content-security-policy

Value: upgrade-insecure-requests; block-all-mixed-content; sandbox allow-modals allow-forms allow-same-origin allow-scripts allow-popups allow-popups-to-escape-sandbox allow-presentation allow-orientation-lock allow-pointer-lock;

Location: https://www.aol.com/

Subresource Integrity

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

Feature not applicable, not implemented, or disabled
Your server doesn't support this feature.
3 script(s)
  0 out of 3 are secure
https://s.yimg.com/...enji/benji-2.1.42.js
https://s.yimg.com/oa/consent.js
https://consent.cmp.oath.com/...version/6.4.1/cmp.js
 View all
13 CSS file(s)
  0 out of 13 are secure
https://s.aolcdn.com/...ut/main.289df0da.css
https://s.aolcdn.com/.../custom.5fcdebca.css
https://s.aolcdn.com/...page_v2.450ca5fa.css
https://s.aolcdn.com/...52199b28fa7ca442.css
https://s.aolcdn.com/...7ea76f4ec7bd00ce.css
https://s.aolcdn.com/...35f949ab045720f0.css
https://s.aolcdn.com/...2b279353b9563d0a.css
https://s.aolcdn.com/...ae48c4e59d83a951.css
https://s.aolcdn.com/...83a88a4e4e6cf5eb.css
https://s.aolcdn.com/...03794bc12e05390f.css
https://s.aolcdn.com/...b51cf15ff5cfd424.css
https://s.aolcdn.com/...9fd2039b03cca64a.css
https://s.aolcdn.com/...8f2cf9375f417c47.css
 View all