Hardenize Report: aol.com

Web Security Overview

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

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

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

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

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

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

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

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.

Parsed Raw Data Model

Registrant	-
Lookup Time	22 Dec 2024 19:31 UTC
Registrar
Registrar	MarkMonitor Inc.
Registrar IANA ID	292
Events
Registration	22 Jun 1995 04:00 UTC
Update	22 Oct 2024 09:10 UTC
Expiration	23 Nov 2025 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. Email: Phone: Fax:
Abuse	Email: abusecomplaints@markmonitor.com Phone: +1.2086851750 Fax:

{
  "meta": {
    "timestamp": "2024-12-22T19:31:24.735519969Z",
    "id": "acd37716-7fdd-492c-8508-ed32a5f2f4e5",
    "type": "HZ_REGISTRABLE_DOMAIN",
    "schemaVersion": "2022-02-02",
    "producer": "whois-rdap-clients/2022-03-23",
    "sequenceNo": 0,
    "source": "NET",
    "status": "OK",
    "duration": "0.608s"
  },
  "name": "aol.com",
  "punyName": "aol.com",
  "source": "SOURCE_RDAP",
  "sourceLocation": "https://rdap.verisign.com/com/v1/domain/aol.com",
  "sourceRaw": "{\"objectClassName\":\"domain\",\"handle\":\"5528881_DOMAIN_COM-VRSN\",\"ldhName\":\"AOL.COM\",\"links\":[{\"value\":\"https:\\/\\/rdap.verisign.com\\/com\\/v1\\/domain\\/AOL.COM\",\"rel\":\"self\",\"href\":\"https:\\/\\/rdap.verisign.com\\/com\\/v1\\/domain\\/AOL.COM\",\"type\":\"application\\/rdap+json\"},{\"value\":\"https:\\/\\/rdap.markmonitor.com\\/rdap\\/domain\\/AOL.COM\",\"rel\":\"related\",\"href\":\"https:\\/\\/rdap.markmonitor.com\\/rdap\\/domain\\/AOL.COM\",\"type\":\"application\\/rdap+json\"}],\"status\":[\"client delete prohibited\",\"client transfer prohibited\",\"client update prohibited\",\"server delete prohibited\",\"server transfer prohibited\",\"server update prohibited\"],\"entities\":[{\"objectClassName\":\"entity\",\"handle\":\"292\",\"roles\":[\"registrar\"],\"publicIds\":[{\"type\":\"IANA Registrar ID\",\"identifier\":\"292\"}],\"vcardArray\":[\"vcard\",[[\"version\",{},\"text\",\"4.0\"],[\"fn\",{},\"text\",\"MarkMonitor Inc.\"]]],\"entities\":[{\"objectClassName\":\"entity\",\"roles\":[\"abuse\"],\"vcardArray\":[\"vcard\",[[\"version\",{},\"text\",\"4.0\"],[\"fn\",{},\"text\",\"\"],[\"tel\",{\"type\":\"voice\"},\"uri\",\"tel:+1.2086851750\"],[\"email\",{},\"text\",\"abusecomplaints@markmonitor.com\"]]]}]}],\"events\":[{\"eventAction\":\"registration\",\"eventDate\":\"1995-06-22T04:00:00Z\"},{\"eventAction\":\"expiration\",\"eventDate\":\"2025-11-23T12:02:22Z\"},{\"eventAction\":\"last changed\",\"eventDate\":\"2024-10-22T09:10:15Z\"},{\"eventAction\":\"last update of RDAP database\",\"eventDate\":\"2024-12-22T19:31:07Z\"}],\"secureDNS\":{\"delegationSigned\":false},\"nameservers\":[{\"objectClassName\":\"nameserver\",\"ldhName\":\"NS1.YAHOO.COM\"},{\"objectClassName\":\"nameserver\",\"ldhName\":\"NS2.YAHOO.COM\"},{\"objectClassName\":\"nameserver\",\"ldhName\":\"NS3.YAHOO.COM\"},{\"objectClassName\":\"nameserver\",\"ldhName\":\"NS4.YAHOO.COM\"},{\"objectClassName\":\"nameserver\",\"ldhName\":\"NS5.YAHOO.COM\"}],\"rdapConformance\":[\"rdap_level_0\",\"icann_rdap_technical_implementation_guide_0\",\"icann_rdap_response_profile_0\"],\"notices\":[{\"title\":\"Terms of Use\",\"description\":[\"Service subject to Terms of Use.\"],\"links\":[{\"href\":\"https:\\/\\/www.verisign.com\\/domain-names\\/registration-data-access-protocol\\/terms-service\\/index.xhtml\",\"type\":\"text\\/html\"}]},{\"title\":\"Status Codes\",\"description\":[\"For more information on domain status codes, please visit https:\\/\\/icann.org\\/epp\"],\"links\":[{\"href\":\"https:\\/\\/icann.org\\/epp\",\"type\":\"text\\/html\"}]},{\"title\":\"RDDS Inaccuracy Complaint Form\",\"description\":[\"URL of the ICANN RDDS Inaccuracy Complaint Form: https:\\/\\/icann.org\\/wicf\"],\"links\":[{\"href\":\"https:\\/\\/icann.org\\/wicf\",\"type\":\"text\\/html\"}]}]}",
  "tld": "com",
  "suffix": "com",
  "createTime": "1995-06-22T04:00:00Z",
  "expireTime": "2025-11-23T12:02:22Z",
  "updateTime": "2024-10-22T09:10:15Z",
  "autoRenewal": false,
  "privacy": false,
  "registrarLock": true,
  "registryLock": true,
  "registrarName": "MarkMonitor Inc.",
  "registrarIanaId": "292",
  "nameservers": [{
    "name": "ns1.yahoo.com",
    "punyName": "",
    "addresses": []
  }, {
    "name": "ns2.yahoo.com",
    "punyName": "",
    "addresses": []
  }, {
    "name": "ns3.yahoo.com",
    "punyName": "",
    "addresses": []
  }, {
    "name": "ns4.yahoo.com",
    "punyName": "",
    "addresses": []
  }, {
    "name": "ns5.yahoo.com",
    "punyName": "",
    "addresses": []
  }],
  "statuses": ["clientDeleteProhibited", "clientTransferProhibited", "clientUpdateProhibited", "serverDeleteProhibited", "serverTransferProhibited", "serverUpdateProhibited"],
  "sourceStatuses": ["client delete prohibited", "client transfer prohibited", "client update prohibited", "server delete prohibited", "server transfer prohibited", "server update prohibited"],
  "contacts": [{
    "type": "CONTACT_REGISTRAR",
    "id": "",
    "firstName": "",
    "lastName": "",
    "organization": "MarkMonitor Inc.",
    "street1": "",
    "street2": "",
    "city": "",
    "state": "",
    "postcode": "",
    "country": "",
    "countryCode": "",
    "email": "",
    "phone": "",
    "fax": ""
  }, {
    "type": "CONTACT_ABUSE",
    "id": "",
    "firstName": "",
    "lastName": "",
    "organization": "",
    "street1": "",
    "street2": "",
    "city": "",
    "state": "",
    "postcode": "",
    "country": "",
    "countryCode": "",
    "email": "abusecomplaints@markmonitor.com",
    "phone": "+1.2086851750",
    "fax": ""
  }]
}

{
  "objectClassName": "domain",
  "handle": "5528881_DOMAIN_COM-VRSN",
  "ldhName": "AOL.COM",
  "links": [
    {
      "value": "https://rdap.verisign.com/com/v1/domain/AOL.COM",
      "rel": "self",
      "href": "https://rdap.verisign.com/com/v1/domain/AOL.COM",
      "type": "application/rdap+json"
    },
    {
      "value": "https://rdap.markmonitor.com/rdap/domain/AOL.COM",
      "rel": "related",
      "href": "https://rdap.markmonitor.com/rdap/domain/AOL.COM",
      "type": "application/rdap+json"
    }
  ],
  "status": [
    "client delete prohibited",
    "client transfer prohibited",
    "client update prohibited",
    "server delete prohibited",
    "server transfer prohibited",
    "server update prohibited"
  ],
  "entities": [
    {
      "objectClassName": "entity",
      "handle": "292",
      "roles": [
        "registrar"
      ],
      "publicIds": [
        {
          "type": "IANA Registrar ID",
          "identifier": "292"
        }
      ],
      "vcardArray": [
        "vcard",
        [
          [
            "version",
            {},
            "text",
            "4.0"
          ],
          [
            "fn",
            {},
            "text",
            "MarkMonitor Inc."
          ]
        ]
      ],
      "entities": [
        {
          "objectClassName": "entity",
          "roles": [
            "abuse"
          ],
          "vcardArray": [
            "vcard",
            [
              [
                "version",
                {},
                "text",
                "4.0"
              ],
              [
                "fn",
                {},
                "text",
                ""
              ],
              [
                "tel",
                {
                  "type": "voice"
                },
                "uri",
                "tel:+1.2086851750"
              ],
              [
                "email",
                {},
                "text",
                "abusecomplaints@markmonitor.com"
              ]
            ]
          ]
        }
      ]
    }
  ],
  "events": [
    {
      "eventAction": "registration",
      "eventDate": "1995-06-22T04:00:00Z"
    },
    {
      "eventAction": "expiration",
      "eventDate": "2025-11-23T12:02:22Z"
    },
    {
      "eventAction": "last changed",
      "eventDate": "2024-10-22T09:10:15Z"
    },
    {
      "eventAction": "last update of RDAP database",
      "eventDate": "2024-12-22T19:31:07Z"
    }
  ],
  "secureDNS": {
    "delegationSigned": false
  },
  "nameservers": [
    {
      "objectClassName": "nameserver",
      "ldhName": "NS1.YAHOO.COM"
    },
    {
      "objectClassName": "nameserver",
      "ldhName": "NS2.YAHOO.COM"
    },
    {
      "objectClassName": "nameserver",
      "ldhName": "NS3.YAHOO.COM"
    },
    {
      "objectClassName": "nameserver",
      "ldhName": "NS4.YAHOO.COM"
    },
    {
      "objectClassName": "nameserver",
      "ldhName": "NS5.YAHOO.COM"
    }
  ],
  "rdapConformance": [
    "rdap_level_0",
    "icann_rdap_technical_implementation_guide_0",
    "icann_rdap_response_profile_0"
  ],
  "notices": [
    {
      "title": "Terms of Use",
      "description": [
        "Service subject to Terms of Use."
      ],
      "links": [
        {
          "href": "https://www.verisign.com/domain-names/registration-data-access-protocol/terms-service/index.xhtml",
          "type": "text/html"
        }
      ]
    },
    {
      "title": "Status Codes",
      "description": [
        "For more information on domain status codes, please visit https://icann.org/epp"
      ],
      "links": [
        {
          "href": "https://icann.org/epp",
          "type": "text/html"
        }
      ]
    },
    {
      "title": "RDDS Inaccuracy Complaint Form",
      "description": [
        "URL of the ICANN RDDS Inaccuracy Complaint Form: https://icann.org/wicf"
      ],
      "links": [
        {
          "href": "https://icann.org/wicf",
          "type": "text/html"
        }
      ]
    }
  ]
}

WHOIS

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

Parsed Raw Data Model

Registrant	AOL Media LLC
Lookup Time	22 Dec 2024 19:31 UTC
Registrar
Registrar	MarkMonitor, Inc.
Registrar IANA ID	292
Events
Registration	22 Jun 1995 04:00 UTC
Update	22 Oct 2024 09:10 UTC
Expiration	23 Nov 2025 00:00 UTC
Configuration
Statuses	serverUpdateProhibited clientUpdateProhibited clientDeleteProhibited clientTransferProhibited serverDeleteProhibited serverTransferProhibited
Registrar Lock
Registry Lock
Nameservers	ns1.yahoo.com ns5.yahoo.com ns3.yahoo.com ns2.yahoo.com ns4.yahoo.com
Contacts
Registrar	MarkMonitor, Inc. MarkMonitor, Inc. Email: Phone: Fax:
Abuse	Email: abusecomplaints@markmonitor.com Phone: +1.2086851750 Fax:
Registrant	AOL Media LLC US Email: Select Request Email Form at https://domains.markmonitor.com/whois/aol.com Phone: Fax:
Administrative	AOL Media LLC US Email: Select Request Email Form at https://domains.markmonitor.com/whois/aol.com Phone: Fax:
Technical	AOL Media LLC US Email: Select Request Email Form at https://domains.markmonitor.com/whois/aol.com Phone: Fax:

{
  "meta": {
    "timestamp": "2024-12-22T19:31:26.608714480Z",
    "id": "f34931bd-52f9-4df8-bf8d-24604941639e",
    "type": "HZ_REGISTRABLE_DOMAIN",
    "schemaVersion": "2022-02-02",
    "producer": "whois-rdap-clients/2022-03-23",
    "sequenceNo": 0,
    "source": "NET",
    "status": "OK",
    "duration": "1.872s"
  },
  "name": "aol.com",
  "punyName": "aol.com",
  "source": "SOURCE_WHOIS",
  "sourceLocation": "whois.markmonitor.com:43",
  "sourceRaw": "Domain Name: aol.com\nRegistry Domain ID: 5528881_DOMAIN_COM-VRSN\nRegistrar WHOIS Server: whois.markmonitor.com\nRegistrar URL: http://www.markmonitor.com\nUpdated Date: 2024-10-22T09:10:15+0000\nCreation Date: 1995-06-22T04:00:00+0000\nRegistrar Registration Expiration Date: 2025-11-23T00:00:00+0000\nRegistrar: MarkMonitor, Inc.\nRegistrar IANA ID: 292\nRegistrar Abuse Contact Email: abusecomplaints@markmonitor.com\nRegistrar Abuse Contact Phone: +1.2086851750\nDomain Status: clientUpdateProhibited (https://www.icann.org/epp#clientUpdateProhibited)\nDomain Status: clientTransferProhibited (https://www.icann.org/epp#clientTransferProhibited)\nDomain Status: clientDeleteProhibited (https://www.icann.org/epp#clientDeleteProhibited)\nDomain Status: serverUpdateProhibited (https://www.icann.org/epp#serverUpdateProhibited)\nDomain Status: serverTransferProhibited (https://www.icann.org/epp#serverTransferProhibited)\nDomain Status: serverDeleteProhibited (https://www.icann.org/epp#serverDeleteProhibited)\nRegistrant Organization: AOL Media LLC\nRegistrant State/Province: VA\nRegistrant Country: US\nRegistrant Email: Select Request Email Form at https://domains.markmonitor.com/whois/aol.com\nAdmin Organization: AOL Media LLC\nAdmin State/Province: VA\nAdmin Country: US\nAdmin Email: Select Request Email Form at https://domains.markmonitor.com/whois/aol.com\nTech Organization: AOL Media LLC\nTech State/Province: VA\nTech Country: US\nTech Email: Select Request Email Form at https://domains.markmonitor.com/whois/aol.com\nName Server: ns1.yahoo.com\nName Server: ns5.yahoo.com\nName Server: ns3.yahoo.com\nName Server: ns2.yahoo.com\nName Server: ns4.yahoo.com\nDNSSEC: unsigned\nURL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/\n\u003e\u003e\u003e Last update of WHOIS database: 2024-12-22T19:29:00+0000 \u003c\u003c\u003c\n\nFor more information on WHOIS status codes, please visit:\n  https://www.icann.org/resources/pages/epp-status-codes\n\nIf you wish to contact this domain’s Registrant, Administrative, or Technical\ncontact, and such email address is not visible above, you may do so via our web\nform, pursuant to ICANN’s Temporary Specification. To verify that you are not a\nrobot, please enter your email address to receive a link to a page that\nfacilitates email communication with the relevant contact(s).\n\nWeb-based WHOIS:\n  https://domains.markmonitor.com/whois\n\nIf you have a legitimate interest in viewing the non-public WHOIS details, send\nyour request and the reasons for your request to whoisrequest@markmonitor.com\nand specify the domain name in the subject line. We will review that request and\nmay ask for supporting documentation and explanation.\n\nThe data in MarkMonitor’s WHOIS database is provided for information purposes,\nand to assist persons in obtaining information about or related to a domain\nname’s registration record. While MarkMonitor believes the data to be accurate,\nthe data is provided \"as is\" with no guarantee or warranties regarding its\naccuracy.\n\nBy submitting a WHOIS query, you agree that you will use this data only for\nlawful purposes and that, under no circumstances will you use this data to:\n  (1) allow, enable, or otherwise support the transmission by email, telephone,\nor facsimile of mass, unsolicited, commercial advertising, or spam; or\n  (2) enable high volume, automated, or electronic processes that send queries,\ndata, or email to MarkMonitor (or its systems) or the domain name contacts (or\nits systems).\n\nMarkMonitor reserves the right to modify these terms at any time.\n\nBy submitting this query, you agree to abide by this policy.\n\nMarkMonitor Domain Management(TM)\nProtecting companies and consumers in a digital world.\n\nVisit MarkMonitor at https://www.markmonitor.com\nContact us at +1.8007459229\nIn Europe, at +44.02032062220\n--\n",
  "tld": "com",
  "suffix": "com",
  "createTime": "1995-06-22T04:00:00Z",
  "expireTime": "2025-11-23T00:00:00Z",
  "updateTime": "2024-10-22T09:10:15Z",
  "autoRenewal": false,
  "privacy": false,
  "registrarLock": true,
  "registryLock": true,
  "registrarName": "MarkMonitor, Inc.",
  "registrarIanaId": "292",
  "registrarUrl": "http://www.markmonitor.com",
  "registrant": "AOL Media LLC",
  "nameservers": [{
    "name": "ns1.yahoo.com",
    "punyName": "",
    "addresses": []
  }, {
    "name": "ns5.yahoo.com",
    "punyName": "",
    "addresses": []
  }, {
    "name": "ns3.yahoo.com",
    "punyName": "",
    "addresses": []
  }, {
    "name": "ns2.yahoo.com",
    "punyName": "",
    "addresses": []
  }, {
    "name": "ns4.yahoo.com",
    "punyName": "",
    "addresses": []
  }],
  "statuses": ["serverUpdateProhibited", "clientUpdateProhibited", "clientDeleteProhibited", "clientTransferProhibited", "serverDeleteProhibited", "serverTransferProhibited"],
  "sourceStatuses": ["clientUpdateProhibited (https://www.icann.org/epp#clientUpdateProhibited)", "clientTransferProhibited (https://www.icann.org/epp#clientTransferProhibited)", "clientDeleteProhibited (https://www.icann.org/epp#clientDeleteProhibited)", "serverUpdateProhibited (https://www.icann.org/epp#serverUpdateProhibited)", "serverTransferProhibited (https://www.icann.org/epp#serverTransferProhibited)", "serverDeleteProhibited (https://www.icann.org/epp#serverDeleteProhibited)"],
  "contacts": [{
    "type": "CONTACT_REGISTRAR",
    "id": "",
    "firstName": "MarkMonitor, Inc.",
    "lastName": "",
    "organization": "MarkMonitor, Inc.",
    "street1": "",
    "street2": "",
    "city": "",
    "state": "",
    "postcode": "",
    "country": "",
    "countryCode": "",
    "email": "",
    "phone": "",
    "fax": ""
  }, {
    "type": "CONTACT_ABUSE",
    "id": "",
    "firstName": "",
    "lastName": "",
    "organization": "",
    "street1": "",
    "street2": "",
    "city": "",
    "state": "",
    "postcode": "",
    "country": "",
    "countryCode": "",
    "email": "abusecomplaints@markmonitor.com",
    "phone": "+1.2086851750",
    "fax": ""
  }, {
    "type": "CONTACT_REGISTRANT",
    "id": "",
    "firstName": "",
    "lastName": "",
    "organization": "AOL Media LLC",
    "street1": "",
    "street2": "",
    "city": "",
    "state": "VA",
    "postcode": "",
    "country": "US",
    "countryCode": "",
    "email": "Select Request Email Form at https://domains.markmonitor.com/whois/aol.com",
    "phone": "",
    "fax": ""
  }, {
    "type": "CONTACT_ADMINISTRATIVE",
    "id": "",
    "firstName": "",
    "lastName": "",
    "organization": "AOL Media LLC",
    "street1": "",
    "street2": "",
    "city": "",
    "state": "VA",
    "postcode": "",
    "country": "US",
    "countryCode": "",
    "email": "Select Request Email Form at https://domains.markmonitor.com/whois/aol.com",
    "phone": "",
    "fax": ""
  }, {
    "type": "CONTACT_TECHNICAL",
    "id": "",
    "firstName": "",
    "lastName": "",
    "organization": "AOL Media LLC",
    "street1": "",
    "street2": "",
    "city": "",
    "state": "VA",
    "postcode": "",
    "country": "US",
    "countryCode": "",
    "email": "Select Request Email Form at https://domains.markmonitor.com/whois/aol.com",
    "phone": "",
    "fax": ""
  }]
}

Domain Name: aol.com
Registry Domain ID: 5528881_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.markmonitor.com
Registrar URL: http://www.markmonitor.com
Updated Date: 2024-10-22T09:10:15+0000
Creation Date: 1995-06-22T04:00:00+0000
Registrar Registration Expiration Date: 2025-11-23T00:00:00+0000
Registrar: MarkMonitor, Inc.
Registrar IANA ID: 292
Registrar Abuse Contact Email: abusecomplaints@markmonitor.com
Registrar Abuse Contact Phone: +1.2086851750
Domain Status: clientUpdateProhibited (https://www.icann.org/epp#clientUpdateProhibited)
Domain Status: clientTransferProhibited (https://www.icann.org/epp#clientTransferProhibited)
Domain Status: clientDeleteProhibited (https://www.icann.org/epp#clientDeleteProhibited)
Domain Status: serverUpdateProhibited (https://www.icann.org/epp#serverUpdateProhibited)
Domain Status: serverTransferProhibited (https://www.icann.org/epp#serverTransferProhibited)
Domain Status: serverDeleteProhibited (https://www.icann.org/epp#serverDeleteProhibited)
Registrant Organization: AOL Media LLC
Registrant State/Province: VA
Registrant Country: US
Registrant Email: Select Request Email Form at https://domains.markmonitor.com/whois/aol.com
Admin Organization: AOL Media LLC
Admin State/Province: VA
Admin Country: US
Admin Email: Select Request Email Form at https://domains.markmonitor.com/whois/aol.com
Tech Organization: AOL Media LLC
Tech State/Province: VA
Tech Country: US
Tech Email: Select Request Email Form at https://domains.markmonitor.com/whois/aol.com
Name Server: ns1.yahoo.com
Name Server: ns5.yahoo.com
Name Server: ns3.yahoo.com
Name Server: ns2.yahoo.com
Name Server: ns4.yahoo.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2024-12-22T19:29:00+0000 <<<

For more information on WHOIS status codes, please visit:
  https://www.icann.org/resources/pages/epp-status-codes

If you wish to contact this domain’s Registrant, Administrative, or Technical
contact, and such email address is not visible above, you may do so via our web
form, pursuant to ICANN’s Temporary Specification. To verify that you are not a
robot, please enter your email address to receive a link to a page that
facilitates email communication with the relevant contact(s).

Web-based WHOIS:
  https://domains.markmonitor.com/whois

If you have a legitimate interest in viewing the non-public WHOIS details, send
your request and the reasons for your request to whoisrequest@markmonitor.com
and specify the domain name in the subject line. We will review that request and
may ask for supporting documentation and explanation.

The data in MarkMonitor’s WHOIS database is provided for information purposes,
and to assist persons in obtaining information about or related to a domain
name’s registration record. While MarkMonitor believes the data to be accurate,
the data is provided "as is" with no guarantee or warranties regarding its
accuracy.

By submitting a WHOIS query, you agree that you will use this data only for
lawful purposes and that, under no circumstances will you use this data to:
  (1) allow, enable, or otherwise support the transmission by email, telephone,
or facsimile of mass, unsolicited, commercial advertising, or spam; or
  (2) enable high volume, automated, or electronic processes that send queries,
data, or email to MarkMonitor (or its systems) or the domain name contacts (or
its systems).

MarkMonitor reserves the right to modify these terms at any time.

By submitting this query, you agree to abide by this policy.

MarkMonitor Domain Management(TM)
Protecting companies and consumers in a digital world.

Visit MarkMonitor at https://www.markmonitor.com
Contact us at +1.8007459229
In Europe, at +44.02032062220
--

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				SOA
ns1.yahoo.com. 68.180.131.16 2001:4998:1b0::7961:686f:6f21				NS REFERRAL
ns2.yahoo.com. 68.142.255.16 2001:4998:1c0::7961:686f:6f21				NS REFERRAL
ns3.yahoo.com. 27.123.42.42 2406:8600:f03f:1f8::1003				NS REFERRAL
ns4.yahoo.com. 98.138.11.157				NS REFERRAL
ns5.yahoo.com. 202.165.97.53 2406:2000:1d0::7961:686f:6f21				NS REFERRAL

Nameserver Addresses

This section shows the configuration of all discovered nameservers by their IP address. To find all applicable nameservers, we inspect the parent zone nameservers for names and glue and then the tested zone nameservers for NS records. We then resolve all discovered names to IP addresses. Finally, we test each address individually.

Nameserver	Sources	Payload Size
202.165.97.53 ns5.yahoo.com. PTR: ns5.yahoo.com.	NAME, GLUE	1272
27.123.42.42 ns3.yahoo.com. PTR: ns3.yahoo.com.	NAME, GLUE	1272
68.142.255.16 ns2.yahoo.com. PTR: ns2.yahoo.com.	NAME, GLUE	1272
68.180.131.16 PRIMARY hidden-master.yahoo.com. ns1.yahoo.com. PTR: ns1.yahoo.com.	NAME, GLUE	1272
98.138.11.157 ns4.yahoo.com. PTR: ns4.yahoo.com.	NAME, GLUE	1272
2001:4998:1b0::7961:686f:6f21 ns1.yahoo.com. PTR: ns1.yahoo.com.	NAME, GLUE	1272
2001:4998:1c0::7961:686f:6f21 ns2.yahoo.com. PTR: ns2.yahoo.com.	NAME, GLUE	1272
2406:2000:1d0::7961:686f:6f21 ns5.yahoo.com. PTR: ns5.yahoo.com.	NAME, GLUE	1272
2406:8600:f03f:1f8::1003 ns3.yahoo.com. PTR: ns3.yahoo.com.	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	2024121802
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

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.

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.11
edge.gycpi.b.yahoodns.net.	60	A	69.147.92.12
edge.gycpi.b.yahoodns.net.	60	AAAA	2001:4998:14:800:0:0:0:1001
edge.gycpi.b.yahoodns.net.	60	AAAA	2001:4998:14:800:0:0:0:1000
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.	86400	NS	ns1.yahoo.com.
aol.com.	86400	NS	ns5.yahoo.com.
aol.com.	86400	NS	ns2.yahoo.com.
aol.com.	86400	NS	ns4.yahoo.com.
aol.com.	86400	NS	ns3.yahoo.com.
aol.com.	600	SOA	hidden-master.yahoo.com. hostmaster.yahoo-inc.com. 2024121802 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	"knowbe4-site-verification=bc3830115833f4f956e30f506f1da8c8"
aol.com.	3600	TXT	"facebook-domain-verification=ervjrx9gun9l4uhc6o4d05p65r2824"
aol.com.	3600	TXT	"google-site-verification=rrvUvV8gUjL0YugQKfcRVnaeQSBJT50UYL_CRwTdKAc"
aol.com.	3600	TXT	"v=spf1 redirect=_spf.mail.yahoo.com"
aol.com.	3600	TXT	"google-site-verification=NqM_NKWhteDHiJCOfhlQqKT4nxexIeFRie5MmWA1RBk"
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=vWa8DccevgR6DN9S4K4ydAcrlRn7SCXHx6sQRmqElLc"
aol.com.	3600	TXT	"_globalsign-domain-verification=W22K-ATZWdBDmzMIsFCF5smJ_T5-7Zl-JDnV8qNe-i"
aol.com.	3600	TXT	"'4a751cdeec084ee2bc9e2cb2e94ba8af'"
aol.com.	3600	TXT	"google-site-verification=ducLuHpystFIiiH_U1devs1CL3q7nhkjCV3BQQtxwWM"
_dmarc.aol.com.	3600	TXT	"v=DMARC1; p=reject; pct=100; rua=mailto:d@rua.agari.com; ruf=mailto:d@ruf.agari.com;"

Analysis

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

Analysis

Issuance of S/MIME certificates not restricted

This policy doesn't restrict the issuance of S/MIME certificates. Consider using the `issuemail` directive to restrict which CAs, if any, can issue.

Issuance of BIMI not restricted

This policy doesn't restrict issuance of BIMI certificates. Consider using the `issuevmc` directive to restrict which CAs, if any, can issue.

CAA policy restricts issuance

Great. This domain name uses CAA to restrict which CAs are allowed to issue certificates for it.

Policy uses reporting

Good. This policy uses reporting, which means that your contact information is available should someone need to contact you about a CAA violation. Do note that you're not guaranteed to be notified, given that CAs generally don't support notifications yet.

Email (SMTP)

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

Test passed

Everything seems to be well configured. Well done.

Some TLS and PKI information shown may have been retrieved from cache. The notes provide more information.

Server	Preference	Operational	STARTTLS	TLS	PKI	DNSSEC	DANE
mx-aol.mail.gm0.yahoodns.net 67.195.204.80 PTR: mtaproxy2.aol.mail.vip.bf1.yahoo.com	10
mx-aol.mail.gm0.yahoodns.net 67.195.204.75 PTR: mtaproxy1.aol.mail.vip.bf1.yahoo.com	10
mx-aol.mail.gm0.yahoodns.net 67.195.228.86 PTR: mtaproxy1.aol.mail.vip.gq1.yahoo.com	10
mx-aol.mail.gm0.yahoodns.net 67.195.228.84 PTR: mtaproxy2.aol.mail.vip.gq1.yahoo.com	10
mx-aol.mail.gm0.yahoodns.net 98.136.96.93 PTR: mtaproxy2.aol.mail.vip.ne1.yahoo.com	10
mx-aol.mail.gm0.yahoodns.net 98.136.96.92 PTR: mtaproxy1.aol.mail.vip.ne1.yahoo.com	10

Analysis

Some SMTP server assessments have been retrieved from cache

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

Latest cache timestamp: 22 Dec 2024 18:15 UTC

Earliest cache timestamp: 22 Dec 2024 18:15 UTC

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.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	22 Dec 2024 18:15 UTC

Analysis

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.

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.

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.

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.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	22 Dec 2024 18:15 UTC

Analysis

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.

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.

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.

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	22 Dec 2024 18:15 UTC

Analysis

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.

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.

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.

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	22 Dec 2024 18:15 UTC

Analysis

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.

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.

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.

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	22 Dec 2024 18:15 UTC

Analysis

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.

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.

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.

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	22 Dec 2024 18:15 UTC

Analysis

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.

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.

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.

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

*.am0.yahoodns.net
Issuer: DigiCert
Not Before: 30 Jul 2024 00:00:00 UTC
Not After: 22 Jan 2025 23:59:59 UTC (expires in 1 month 4 hours)
Key: RSA 2048 bits
Signature: SHA256withRSA
View details

Names	.am0.yahoodns.net .mail.am0.yahoodns.net .sbcglobal.am0.yahoodns.net .mail.gm0.yahoodns.net .gm0.yahoodns.net .biz.mail.yahoo.com *.bullet.am0.yahoodns.net
Subject DN	CN=*.am0.yahoodns.net, O=Yahoo Holdings Inc., L=New York, ST=New York, C=US
Subject Key Identifier	30c4a9dac752a6d7bfebbbad64191328854385e0
Serial	75305d18d6ded44d265969d3764955f
Not Before	30 Jul 2024 00:00:00 UTC
Not After	22 Jan 2025 23:59:59 UTC
Validity period	177 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=DigiCert SHA2 High Assurance Server CA, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:5168ff90af0207753cccd9656462a212b859723b
Parent Certificate	http://cacerts.digicert.com/DigiCertSHA2HighAssuranceServerCA.crt
CRL	http://crl3.digicert.com/sha2-ha-server-g6.crl http://crl4.digicert.com/sha2-ha-server-g6.crl
OCSP	http://ocsp.digicert.com
Certificate Transparency
Signed Certificate Timestamps	30 Jul 2024 06:37:12 UTC \| Google 'Argon2025h1' log \| Qualified 30 Jul 2024 06:37:12 UTC \| DigiCert Nessie2025 Log \| Qualified 30 Jul 2024 06:37:12 UTC \| Cloudflare 'Nimbus2025' \| Qualified
Fingerprints
SHA1	68affd488917bb54c238fb3b99d019f92d305629
SHA256	7990dfbaed0c95d04af6b7139201a263eee914fa93a50864194f656573bf271f
SPKI SHA256	6c4f4aad64d6a2388abfde638e6b71c96649a97cae1fa051842b500eaa582936

Analysis

Strong private key

Good. The private key associated with this certificate is secure.

Strong signature algorithm

Good. This certificate uses a strong signature algorithm.

Certificate matches hostname

Good. The provided certificate matches the expected hostnames.

Certificate dates match

Good. The certificate is valid for use at this point of time.

Certificate has not been revoked

Good. This certificate has not been revoked.

Certificate satisfies Apple's CT compliance requirements

Good. This certificate satisfies Apple's CT requirements at present.

Certificate Chain

Leaf certificate

*.am0.yahoodns.net | 7990dfb
Not After: 22 Jan 2025 23:59:59 UTC (expires in 1 month 4 hours)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Names	.am0.yahoodns.net .mail.am0.yahoodns.net .sbcglobal.am0.yahoodns.net .mail.gm0.yahoodns.net .gm0.yahoodns.net .biz.mail.yahoo.com *.bullet.am0.yahoodns.net
Subject DN	CN=*.am0.yahoodns.net, O=Yahoo Holdings Inc., L=New York, ST=New York, C=US
Subject Key Identifier	30c4a9dac752a6d7bfebbbad64191328854385e0
Serial	75305d18d6ded44d265969d3764955f
Not Before	30 Jul 2024 00:00:00 UTC
Not After	22 Jan 2025 23:59:59 UTC
Validity period	177 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=DigiCert SHA2 High Assurance Server CA, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:5168ff90af0207753cccd9656462a212b859723b
Parent Certificate	http://cacerts.digicert.com/DigiCertSHA2HighAssuranceServerCA.crt
CRL	http://crl3.digicert.com/sha2-ha-server-g6.crl http://crl4.digicert.com/sha2-ha-server-g6.crl
OCSP	http://ocsp.digicert.com
Certificate Transparency
Signed Certificate Timestamps	30 Jul 2024 06:37:12 UTC \| Google 'Argon2025h1' log \| Qualified 30 Jul 2024 06:37:12 UTC \| DigiCert Nessie2025 Log \| Qualified 30 Jul 2024 06:37:12 UTC \| Cloudflare 'Nimbus2025' \| Qualified
Fingerprints
SHA1	68affd488917bb54c238fb3b99d019f92d305629
SHA256	7990dfbaed0c95d04af6b7139201a263eee914fa93a50864194f656573bf271f
SPKI SHA256	6c4f4aad64d6a2388abfde638e6b71c96649a97cae1fa051842b500eaa582936

Intermediate certificate

DigiCert SHA2 High Assurance Server CA | 19400be
Not After: 22 Oct 2028 12:00:00 UTC (expires in 3 years 9 months)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Subject DN	CN=DigiCert SHA2 High Assurance Server CA, OU=www.digicert.com, O=DigiCert Inc, C=US
Subject Key Identifier	5168ff90af0207753cccd9656462a212b859723b
Serial	4e1e7a4dc5cf2f36dc02b42b85d159f
Not Before	22 Oct 2013 12:00:00 UTC
Not After	22 Oct 2028 12:00:00 UTC
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	serverAuth, clientAuth
Issuer
Issuer DN	CN=DigiCert High Assurance EV Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Not Applicable
Authority Key Identifier	keyid:b13ec36903f8bf4701d498261a0802ef63642bc3
CRL	http://crl4.digicert.com/DigiCertHighAssuranceEVRootCA.crl
OCSP	http://ocsp.digicert.com
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	a031c46782e6e6c662c2c87c76da9aa62ccabd8e
SHA256	19400be5b7a31fb733917700789d2f0a2471c0c9d506c0e504c06c16d7cb17c0
SPKI SHA256	936bfae7bc41b0e55ed4f411c0eb07b30ddbb064f657322acf92bee7db0d430b

Root certificate

DigiCert High Assurance EV Root CA | 7431e5f
Not After: 10 Nov 2031 00:00:00 UTC (expires in 6 years 10 months)
Authentication: RSA 2048 bits (SHA1withRSA)
View details

Subject DN	CN=DigiCert High Assurance EV Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
Subject Key Identifier	b13ec36903f8bf4701d498261a0802ef63642bc3
Serial	2ac5c266a0b409b8f0b79f2ae462577
Not Before	10 Nov 2006 00:00:00 UTC
Not After	10 Nov 2031 00:00:00 UTC
Key Usage	digitalSignature, keyCertSign, cRLSign
Issuer
Issuer DN	CN=DigiCert High Assurance EV Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Self-signed
Authority Key Identifier	keyid:b13ec36903f8bf4701d498261a0802ef63642bc3
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	5fb7ee0633e259dbad0c4c9ae6d38f1a61c7dc25
SHA256	7431e5f4c3c1ce4690774f0b61e05440883ba9a01ed00ba6abd7806ed3b118cf
SPKI SHA256	5a889647220e54d6bd8a16817224520bb5c78e58984bd570506388b9de0f075f

Analysis

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

SPF policy found

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

Location: aol.com

SPF policy is valid

Good. Your SPF policy is syntactically valid.

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

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

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;

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;

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

Date	Sun, 22 Dec 2024 19:31:26 GMT
Connection	keep-alive
Server	ATS
Cache-Control	no-store
Content-Type	text/html
Content-Language	en
X-Frame-Options	DENY
X-Content-Type-Options	nosniff
Referrer-Policy	strict-origin-when-cross-origin
Content-Security-Policy	sandbox allow-scripts; default-src 'self'; img-src https:; style-src 'unsafe-inline'; script-src 'unsafe-inline'; report-uri https://csp.yahoo.com/beacon/csp?src=redirect
Location	https://www.aol.com/
Content-Length	4376

2

https://www.aol.com/

HTTP/1.1 200 OK

Date	Sun, 22 Dec 2024 19:31:26 GMT
Content-Type	text/html; charset=utf-8
Expect-CT	max-age=31536000, report-uri="http://csp.yahoo.com/beacon/csp?src=yahoocom-expect-ct-report-only
Referrer-Policy	no-referrer-when-downgrade
Strict-Transport-Security	max-age=31536000
X-Content-Type-Options	nosniff
X-Frame-Options	SAMEORIGIN
X-XSS-Protection	1; mode=block
Vary	Accept-Encoding
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;
cache-control	no-cache, no-store, private, must-revalidate
Age	3
Server	ATS
Transfer-Encoding	chunked
Connection	keep-alive
Set-Cookie	A1=d=AQABBA5paGcCEIo-8aXw7QUQxo2HJssXhhgFEgEBAQG6aWdyZ9xS0iMA_eMAAA&S=AQAAAkN97IYt1HKqJviy5dapOOI; Expires=Tue, 23 Dec 2025 01:31:27 GMT; Max-Age=31557600; Domain=.aol.com; Path=/; SameSite=Lax; Secure; HttpOnly
Set-Cookie	A3=d=AQABBA5paGcCEIo-8aXw7QUQxo2HJssXhhgFEgEBAQG6aWdyZ9xS0iMA_eMAAA&S=AQAAAkN97IYt1HKqJviy5dapOOI; Expires=Tue, 23 Dec 2025 01:31:27 GMT; Max-Age=31557600; Domain=.aol.com; Path=/; SameSite=None; Secure; HttpOnly
Set-Cookie	A1S=d=AQABBA5paGcCEIo-8aXw7QUQxo2HJssXhhgFEgEBAQG6aWdyZ9xS0iMA_eMAAA&S=AQAAAkN97IYt1HKqJviy5dapOOI; Domain=.aol.com; Path=/; SameSite=Lax; Secure

Analysis

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

Date	Sun, 22 Dec 2024 19:31:27 GMT
Connection	keep-alive
Server	ATS
Cache-Control	no-store
Location	https://www.aol.com/
Content-Type	text/html
Content-Language	en
Content-Length	302

2

https://www.aol.com/

HTTP/1.1 200 OK

Date	Sun, 22 Dec 2024 19:31:27 GMT
Content-Type	text/html; charset=utf-8
Expect-CT	max-age=31536000, report-uri="http://csp.yahoo.com/beacon/csp?src=yahoocom-expect-ct-report-only
Referrer-Policy	no-referrer-when-downgrade
Strict-Transport-Security	max-age=31536000
X-Content-Type-Options	nosniff
X-Frame-Options	SAMEORIGIN
X-XSS-Protection	1; mode=block
Vary	Accept-Encoding
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;
cache-control	no-cache, no-store, private, must-revalidate
Age	0
Server	ATS
Transfer-Encoding	chunked
Connection	keep-alive
Set-Cookie	A1=d=AQABBA9paGcCEISd_hWSV6ZUMrgdjTaPaKkFEgEBAQG6aWdyZ9xS0iMA_eMAAA&S=AQAAAqi1f9K6X9jhETX8C0Yt_Sw; Expires=Tue, 23 Dec 2025 01:31:27 GMT; Max-Age=31557600; Domain=.aol.com; Path=/; SameSite=Lax; Secure; HttpOnly
Set-Cookie	A3=d=AQABBA9paGcCEISd_hWSV6ZUMrgdjTaPaKkFEgEBAQG6aWdyZ9xS0iMA_eMAAA&S=AQAAAqi1f9K6X9jhETX8C0Yt_Sw; Expires=Tue, 23 Dec 2025 01:31:27 GMT; Max-Age=31557600; Domain=.aol.com; Path=/; SameSite=None; Secure; HttpOnly
Set-Cookie	A1S=d=AQABBA9paGcCEISd_hWSV6ZUMrgdjTaPaKkFEgEBAQG6aWdyZ9xS0iMA_eMAAA&S=AQAAAqi1f9K6X9jhETX8C0Yt_Sw; Domain=.aol.com; Path=/; SameSite=Lax; Secure

Analysis

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

Date	Sun, 22 Dec 2024 19:31:27 GMT
Connection	keep-alive
Strict-Transport-Security	max-age=31536000
Server	ATS
Cache-Control	no-store
Content-Type	text/html
Content-Language	en
X-Frame-Options	DENY
X-Content-Type-Options	nosniff
Referrer-Policy	strict-origin-when-cross-origin
Content-Security-Policy	sandbox allow-scripts; default-src 'self'; img-src https:; style-src 'unsafe-inline'; script-src 'unsafe-inline'; report-uri https://csp.yahoo.com/beacon/csp?src=redirect
Location	https://www.aol.com/
Content-Length	4377

2

https://www.aol.com/

HTTP/1.1 200 OK

Date	Sun, 22 Dec 2024 19:31:28 GMT
Content-Type	text/html; charset=utf-8
Expect-CT	max-age=31536000, report-uri="http://csp.yahoo.com/beacon/csp?src=yahoocom-expect-ct-report-only
Referrer-Policy	no-referrer-when-downgrade
Strict-Transport-Security	max-age=31536000
X-Content-Type-Options	nosniff
X-Frame-Options	SAMEORIGIN
X-XSS-Protection	1; mode=block
Vary	Accept-Encoding
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;
cache-control	no-cache, no-store, private, must-revalidate
Age	2
Server	ATS
Transfer-Encoding	chunked
Connection	keep-alive
Set-Cookie	A1=d=AQABBA9paGcCEDCtDiZQK5p0LifH4A7wxKgFEgEBAQG6aWdyZ9xS0iMA_eMAAA&S=AQAAAsmDp7Ipw6n8fuMwEflLRBs; Expires=Tue, 23 Dec 2025 01:31:28 GMT; Max-Age=31557600; Domain=.aol.com; Path=/; SameSite=Lax; Secure; HttpOnly
Set-Cookie	A3=d=AQABBA9paGcCEDCtDiZQK5p0LifH4A7wxKgFEgEBAQG6aWdyZ9xS0iMA_eMAAA&S=AQAAAsmDp7Ipw6n8fuMwEflLRBs; Expires=Tue, 23 Dec 2025 01:31:28 GMT; Max-Age=31557600; Domain=.aol.com; Path=/; SameSite=None; Secure; HttpOnly
Set-Cookie	A1S=d=AQABBA9paGcCEDCtDiZQK5p0LifH4A7wxKgFEgEBAQG6aWdyZ9xS0iMA_eMAAA&S=AQAAAsmDp7Ipw6n8fuMwEflLRBs; Domain=.aol.com; Path=/; SameSite=Lax; Secure

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

1

https://www.aol.com/

HTTP/1.1 200 OK

Date	Sun, 22 Dec 2024 19:31:28 GMT
Content-Type	text/html; charset=utf-8
Expect-CT	max-age=31536000, report-uri="http://csp.yahoo.com/beacon/csp?src=yahoocom-expect-ct-report-only
Referrer-Policy	no-referrer-when-downgrade
Strict-Transport-Security	max-age=31536000
X-Content-Type-Options	nosniff
X-Frame-Options	SAMEORIGIN
X-XSS-Protection	1; mode=block
Vary	Accept-Encoding
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;
cache-control	no-cache, no-store, private, must-revalidate
Age	0
Server	ATS
Transfer-Encoding	chunked
Connection	keep-alive
Set-Cookie	A1=d=AQABBBBpaGcCEP3zRwoS1t-xK2f_Y3k-YK0FEgEBAQG6aWdyZ9xS0iMA_eMAAA&S=AQAAAoJlwyl1ujuXSbcIAOO_1bg; Expires=Tue, 23 Dec 2025 01:31:28 GMT; Max-Age=31557600; Domain=.aol.com; Path=/; SameSite=Lax; Secure; HttpOnly
Set-Cookie	A3=d=AQABBBBpaGcCEP3zRwoS1t-xK2f_Y3k-YK0FEgEBAQG6aWdyZ9xS0iMA_eMAAA&S=AQAAAoJlwyl1ujuXSbcIAOO_1bg; Expires=Tue, 23 Dec 2025 01:31:28 GMT; Max-Age=31557600; Domain=.aol.com; Path=/; SameSite=None; Secure; HttpOnly
Set-Cookie	A1S=d=AQABBBBpaGcCEP3zRwoS1t-xK2f_Y3k-YK0FEgEBAQG6aWdyZ9xS0iMA_eMAAA&S=AQAAAoJlwyl1ujuXSbcIAOO_1bg; Domain=.aol.com; Path=/; SameSite=Lax; Secure

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

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.

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.

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.

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.

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.

Server enforces cipher suite preferences

Excellent. This server enforces server cipher suite preference, which means that it is able to select the best suite from the options submitted by clients. Combined with a well-designed list of supported cipher suites, this setting enables negotiation of best security.

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

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

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

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.

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.

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.

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.

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.

Server enforces cipher suite preferences

Excellent. This server enforces server cipher suite preference, which means that it is able to select the best suite from the options submitted by clients. Combined with a well-designed list of supported cipher suites, this setting enables negotiation of best security.

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

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

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

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.

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.

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.

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.

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.

Server enforces cipher suite preferences

Excellent. This server enforces server cipher suite preference, which means that it is able to select the best suite from the options submitted by clients. Combined with a well-designed list of supported cipher suites, this setting enables negotiation of best security.

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

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

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

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.

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.

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.

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.

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.

Server enforces cipher suite preferences

Excellent. This server enforces server cipher suite preference, which means that it is able to select the best suite from the options submitted by clients. Combined with a well-designed list of supported cipher suites, this setting enables negotiation of best security.

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

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

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

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.

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.

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.

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.

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.

Server enforces cipher suite preferences

Excellent. This server enforces server cipher suite preference, which means that it is able to select the best suite from the options submitted by clients. Combined with a well-designed list of supported cipher suites, this setting enables negotiation of best security.

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

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

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

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.

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.

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.

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.

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.

Server enforces cipher suite preferences

Excellent. This server enforces server cipher suite preference, which means that it is able to select the best suite from the options submitted by clients. Combined with a well-designed list of supported cipher suites, this setting enables negotiation of best security.

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

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

DHE suites not supported

This server doesn't support the Diffie-Hellman (DH) key exchange.

WWW Certificates

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

Test passed

Everything seems to be well configured. Well done.

Certificate: www.aol.com

Leaf certificate

jp.techcrunch.com
Issuer: DigiCert
Not Before: 20 Nov 2024 00:00:00 UTC
Not After: 19 Feb 2025 23:59:59 UTC (expires in 1 month 28 days)
Key: EC 256 bits
Signature: SHA256withRSA
View details

Names	jp.techcrunch.com external.cap.yahoo.net external-staging.cap.yahoo.net glp.searchjam.com qa-glp.searchjam.com stage-glp.searchjam.com prodramp-glp.searchjam.com testvideo.advertising.yahoo.net dev-astra.commerce.aol.com stg-astra.commerce.aol.com perf-astra.commerce.aol.com astra.commerce.aol.com us.y.ycpi.atwola.com eu.y.ycpi.atwola.com as.y.ycpi.atwola.com .at.atwola.com .mail.yahoo.net .mail.aol.net .jac.yahoosandbox.com .qa-jac.yahoosandbox.com .stage-jac.yahoosandbox.com dmxml.godaddy.overture.com external.graphdb.yk.yahoo.com external-staging.graphdb.yk.yahoo.com order.store.yahoo.net us-dc1-order.store.yahoo.net us-dc2-order.store.yahoo.net .stores.yahoo.net .store.yahoo.net edgecast-img.yahoo.net edgecast-img-staging.yahoo.net www.aol.com s.aol.com homepage.aol.com canary-www.aol.com firefox-startpage.aol.com o2.aol.de www.aol.de welcomescreen.aol.de www.aol.ca www.aol.co.uk o2.welcomescreen.aol.de 200.web.aol.com aolbroadband.welcomescreen.aol.co.uk w.main.welcomescreen.aol.com .forums.rivals.com .n.rivals.com .rivals.com uncrowned.com pbs.www.aol.com pbs.techcrunch.com pbs-staging.www.aol.com pbs-staging.techcrunch.com cdn.desktop.aol.com updates.desktop.aol.com api.alyavista.com .engadget.com datenschutz.aol.de privacy.aol.ca privacy.aol.co.uk privacy.aol.com privacidad.aol.es privacy.aol.de legal.aol.com confidentialite.aol.fr
Subject DN	CN=jp.techcrunch.com, O=Yahoo Holdings Inc., L=New York, ST=New York, C=US
Subject Key Identifier	55f859dcf61a0c90d4154477c13374245c7b1140
Serial	73f01bee305d8171082a7370b5caf15
Not Before	20 Nov 2024 00:00:00 UTC
Not After	19 Feb 2025 23:59:59 UTC
Validity period	92 days
Key Usage	digitalSignature, keyAgreement
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=DigiCert SHA2 High Assurance Server CA, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:5168ff90af0207753cccd9656462a212b859723b
Parent Certificate	http://cacerts.digicert.com/DigiCertSHA2HighAssuranceServerCA.crt
CRL	http://crl3.digicert.com/sha2-ha-server-g6.crl http://crl4.digicert.com/sha2-ha-server-g6.crl
OCSP	http://ocsp.digicert.com
Certificate Transparency
Signed Certificate Timestamps	20 Nov 2024 17:53:46 UTC \| Google 'Argon2025h1' log \| Qualified 20 Nov 2024 17:53:46 UTC \| DigiCert Nessie2025 Log \| Qualified 20 Nov 2024 17:53:46 UTC \| Cloudflare 'Nimbus2025' \| Qualified
Fingerprints
SHA1	7e7b5ff045d0c398a99b937608e814b77ba10de1
SHA256	5d2d609bb704ae97151ac29a757bffacf966deaf79d6548fdc48702107554023
SPKI SHA256	19bc6822f0752fb3924e0b59f2549f7f90483fb5231e2862ec7c6af5bf70250d

Analysis

Strong private key

Good. The private key associated with this certificate is secure.

Strong signature algorithm

Good. This certificate uses a strong signature algorithm.

Certificate matches hostname

Good. The provided certificate matches the expected hostnames.

Certificate dates match

Good. The certificate is valid for use at this point of time.

Certificate has not been revoked

Good. This certificate has not been revoked.

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 | 5d2d609
Not After: 19 Feb 2025 23:59:59 UTC (expires in 1 month 28 days)
Authentication: EC 256 bits (SHA256withRSA)
View details

Names	jp.techcrunch.com external.cap.yahoo.net external-staging.cap.yahoo.net glp.searchjam.com qa-glp.searchjam.com stage-glp.searchjam.com prodramp-glp.searchjam.com testvideo.advertising.yahoo.net dev-astra.commerce.aol.com stg-astra.commerce.aol.com perf-astra.commerce.aol.com astra.commerce.aol.com us.y.ycpi.atwola.com eu.y.ycpi.atwola.com as.y.ycpi.atwola.com .at.atwola.com .mail.yahoo.net .mail.aol.net .jac.yahoosandbox.com .qa-jac.yahoosandbox.com .stage-jac.yahoosandbox.com dmxml.godaddy.overture.com external.graphdb.yk.yahoo.com external-staging.graphdb.yk.yahoo.com order.store.yahoo.net us-dc1-order.store.yahoo.net us-dc2-order.store.yahoo.net .stores.yahoo.net .store.yahoo.net edgecast-img.yahoo.net edgecast-img-staging.yahoo.net www.aol.com s.aol.com homepage.aol.com canary-www.aol.com firefox-startpage.aol.com o2.aol.de www.aol.de welcomescreen.aol.de www.aol.ca www.aol.co.uk o2.welcomescreen.aol.de 200.web.aol.com aolbroadband.welcomescreen.aol.co.uk w.main.welcomescreen.aol.com .forums.rivals.com .n.rivals.com .rivals.com uncrowned.com pbs.www.aol.com pbs.techcrunch.com pbs-staging.www.aol.com pbs-staging.techcrunch.com cdn.desktop.aol.com updates.desktop.aol.com api.alyavista.com .engadget.com datenschutz.aol.de privacy.aol.ca privacy.aol.co.uk privacy.aol.com privacidad.aol.es privacy.aol.de legal.aol.com confidentialite.aol.fr
Subject DN	CN=jp.techcrunch.com, O=Yahoo Holdings Inc., L=New York, ST=New York, C=US
Subject Key Identifier	55f859dcf61a0c90d4154477c13374245c7b1140
Serial	73f01bee305d8171082a7370b5caf15
Not Before	20 Nov 2024 00:00:00 UTC
Not After	19 Feb 2025 23:59:59 UTC
Validity period	92 days
Key Usage	digitalSignature, keyAgreement
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=DigiCert SHA2 High Assurance Server CA, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:5168ff90af0207753cccd9656462a212b859723b
Parent Certificate	http://cacerts.digicert.com/DigiCertSHA2HighAssuranceServerCA.crt
CRL	http://crl3.digicert.com/sha2-ha-server-g6.crl http://crl4.digicert.com/sha2-ha-server-g6.crl
OCSP	http://ocsp.digicert.com
Certificate Transparency
Signed Certificate Timestamps	20 Nov 2024 17:53:46 UTC \| Google 'Argon2025h1' log \| Qualified 20 Nov 2024 17:53:46 UTC \| DigiCert Nessie2025 Log \| Qualified 20 Nov 2024 17:53:46 UTC \| Cloudflare 'Nimbus2025' \| Qualified
Fingerprints
SHA1	7e7b5ff045d0c398a99b937608e814b77ba10de1
SHA256	5d2d609bb704ae97151ac29a757bffacf966deaf79d6548fdc48702107554023
SPKI SHA256	19bc6822f0752fb3924e0b59f2549f7f90483fb5231e2862ec7c6af5bf70250d

Intermediate certificate

DigiCert SHA2 High Assurance Server CA | 19400be
Not After: 22 Oct 2028 12:00:00 UTC (expires in 3 years 9 months)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Subject DN	CN=DigiCert SHA2 High Assurance Server CA, OU=www.digicert.com, O=DigiCert Inc, C=US
Subject Key Identifier	5168ff90af0207753cccd9656462a212b859723b
Serial	4e1e7a4dc5cf2f36dc02b42b85d159f
Not Before	22 Oct 2013 12:00:00 UTC
Not After	22 Oct 2028 12:00:00 UTC
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	serverAuth, clientAuth
Issuer
Issuer DN	CN=DigiCert High Assurance EV Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Not Applicable
Authority Key Identifier	keyid:b13ec36903f8bf4701d498261a0802ef63642bc3
CRL	http://crl4.digicert.com/DigiCertHighAssuranceEVRootCA.crl
OCSP	http://ocsp.digicert.com
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	a031c46782e6e6c662c2c87c76da9aa62ccabd8e
SHA256	19400be5b7a31fb733917700789d2f0a2471c0c9d506c0e504c06c16d7cb17c0
SPKI SHA256	936bfae7bc41b0e55ed4f411c0eb07b30ddbb064f657322acf92bee7db0d430b

Root certificate

DigiCert High Assurance EV Root CA | 7431e5f
Not After: 10 Nov 2031 00:00:00 UTC (expires in 6 years 10 months)
Authentication: RSA 2048 bits (SHA1withRSA)
View details

Subject DN	CN=DigiCert High Assurance EV Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
Subject Key Identifier	b13ec36903f8bf4701d498261a0802ef63642bc3
Serial	2ac5c266a0b409b8f0b79f2ae462577
Not Before	10 Nov 2006 00:00:00 UTC
Not After	10 Nov 2031 00:00:00 UTC
Key Usage	digitalSignature, keyCertSign, cRLSign
Issuer
Issuer DN	CN=DigiCert High Assurance EV Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Self-signed
Authority Key Identifier	keyid:b13ec36903f8bf4701d498261a0802ef63642bc3
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	5fb7ee0633e259dbad0c4c9ae6d38f1a61c7dc25
SHA256	7431e5f4c3c1ce4690774f0b61e05440883ba9a01ed00ba6abd7806ed3b118cf
SPKI SHA256	5a889647220e54d6bd8a16817224520bb5c78e58984bd570506388b9de0f075f

Analysis

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: 17 Sep 2024 00:00:00 UTC
Not After: 12 Mar 2025 23:59:59 UTC (expires in 2 months 18 days)
Key: RSA 4096 bits
Signature: SHA256withRSA
View details

Names	src6.yahoo.com alephd.com alephd.fr altomail.com aol.ca aol.co.uk aol.com aol.de aol.fr aol.jp webmail.aol.com.br mail.latino.aol.com att.my.yahoo.com au.be.yahoo.com au.solutions.yahoo.com beboundless.jp blog.postmaster.verizonmedia.com brightroll.com broman.vzbuilders.com corp.aol.com csi.com deals.gdgt.com dns.ops.yahoo.com engadget.com helpisp.netscape.com hk.ent.yahoo.com hk.smartr.yahoo.com hk.youcard.yahoo.com id.berita.yahoo.com id.omg.search.yahoo.com joystiq.com kr.edit.billing.yahoo.com kr.img.search.yahoo.com luxist.com m.order.yahoo.com.tw makers.com mando.data.yahoo.com maw-looker-api.analytics.verizonmedia.com maw.analytics.verizonmedia.com money-a2z.com netdeals.com netfind.com netscape.com no.profiles.yahoo.com oath.com parentdish.ca pets.world ryotstudio.co.uk see-it.live sfrclient.welcome.aol.fr shelterpop.com shopfone.com sport-king.com streampad.com stylelist.com tech24.deals tech247.co thatsfit.ca thegifts.co theparanoids.com think24-7.com tw.discount.yahoo.net tw.smartr.yahoo.com tw.youcard.yahoo.com uk.360.yahoo.com viral.site when.com wmconnect.com wow.com www.altomail.com www.ar.yahoo.com www.brightroll.com www.csi.com www.netscape.com www.theparanoids.com yahoo.dev hk.mobi.yahoo.com tw.mobi.yahoo.com yahooforcreators.com www.yahooforcreators.com www.gamerfeed.com www.gamescanvas.com www.gamedailyxl.com www.yahoogamez.com www.yahoogames.com www.gamesdomain.com gamesdomain.com gamerfeed.com gamescanvas.com gamedailyxl.com yahoogames.com yahoogamez.com
Subject DN	CN=src6.yahoo.com, O=Yahoo Holdings Inc., L=New York, ST=New York, C=US
Subject Key Identifier	10df21618deabf2d41e77ca564bbf4c39bc37d2d
Serial	4fdf454ca00e592fd77f0c78f29afbe
Not Before	17 Sep 2024 00:00:00 UTC
Not After	12 Mar 2025 23:59:59 UTC
Validity period	177 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=DigiCert SHA2 High Assurance Server CA, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:5168ff90af0207753cccd9656462a212b859723b
Parent Certificate	http://cacerts.digicert.com/DigiCertSHA2HighAssuranceServerCA.crt
CRL	http://crl3.digicert.com/sha2-ha-server-g6.crl http://crl4.digicert.com/sha2-ha-server-g6.crl
OCSP	http://ocsp.digicert.com
Certificate Transparency
Signed Certificate Timestamps	17 Sep 2024 07:07:19 UTC \| Google 'Argon2025h1' log \| Qualified 17 Sep 2024 07:07:19 UTC \| DigiCert Yeti2025 Log \| Qualified 17 Sep 2024 07:07:19 UTC \| DigiCert Nessie2025 Log \| Qualified
Fingerprints
SHA1	ce0bfb4b05bb55c3456175967e4e88ddc8c9d0fd
SHA256	b2b8c00e7b82fcd2bc167555f99febc7795024b38396d02035c960fcec060c4a
SPKI SHA256	7e5082aaef2fbd6fb8a0aae8bfc4e3ffdd0cd0c4388907004da5ab88b5d3d8d9

Analysis

Strong private key

Good. The private key associated with this certificate is secure.

Strong signature algorithm

Good. This certificate uses a strong signature algorithm.

Certificate matches hostname

Good. The provided certificate matches the expected hostnames.

Certificate dates match

Good. The certificate is valid for use at this point of time.

Certificate has not been revoked

Good. This certificate has not been revoked.

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 | b2b8c00
Not After: 12 Mar 2025 23:59:59 UTC (expires in 2 months 18 days)
Authentication: RSA 4096 bits (SHA256withRSA)
View details

Names	src6.yahoo.com alephd.com alephd.fr altomail.com aol.ca aol.co.uk aol.com aol.de aol.fr aol.jp webmail.aol.com.br mail.latino.aol.com att.my.yahoo.com au.be.yahoo.com au.solutions.yahoo.com beboundless.jp blog.postmaster.verizonmedia.com brightroll.com broman.vzbuilders.com corp.aol.com csi.com deals.gdgt.com dns.ops.yahoo.com engadget.com helpisp.netscape.com hk.ent.yahoo.com hk.smartr.yahoo.com hk.youcard.yahoo.com id.berita.yahoo.com id.omg.search.yahoo.com joystiq.com kr.edit.billing.yahoo.com kr.img.search.yahoo.com luxist.com m.order.yahoo.com.tw makers.com mando.data.yahoo.com maw-looker-api.analytics.verizonmedia.com maw.analytics.verizonmedia.com money-a2z.com netdeals.com netfind.com netscape.com no.profiles.yahoo.com oath.com parentdish.ca pets.world ryotstudio.co.uk see-it.live sfrclient.welcome.aol.fr shelterpop.com shopfone.com sport-king.com streampad.com stylelist.com tech24.deals tech247.co thatsfit.ca thegifts.co theparanoids.com think24-7.com tw.discount.yahoo.net tw.smartr.yahoo.com tw.youcard.yahoo.com uk.360.yahoo.com viral.site when.com wmconnect.com wow.com www.altomail.com www.ar.yahoo.com www.brightroll.com www.csi.com www.netscape.com www.theparanoids.com yahoo.dev hk.mobi.yahoo.com tw.mobi.yahoo.com yahooforcreators.com www.yahooforcreators.com www.gamerfeed.com www.gamescanvas.com www.gamedailyxl.com www.yahoogamez.com www.yahoogames.com www.gamesdomain.com gamesdomain.com gamerfeed.com gamescanvas.com gamedailyxl.com yahoogames.com yahoogamez.com
Subject DN	CN=src6.yahoo.com, O=Yahoo Holdings Inc., L=New York, ST=New York, C=US
Subject Key Identifier	10df21618deabf2d41e77ca564bbf4c39bc37d2d
Serial	4fdf454ca00e592fd77f0c78f29afbe
Not Before	17 Sep 2024 00:00:00 UTC
Not After	12 Mar 2025 23:59:59 UTC
Validity period	177 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=DigiCert SHA2 High Assurance Server CA, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:5168ff90af0207753cccd9656462a212b859723b
Parent Certificate	http://cacerts.digicert.com/DigiCertSHA2HighAssuranceServerCA.crt
CRL	http://crl3.digicert.com/sha2-ha-server-g6.crl http://crl4.digicert.com/sha2-ha-server-g6.crl
OCSP	http://ocsp.digicert.com
Certificate Transparency
Signed Certificate Timestamps	17 Sep 2024 07:07:19 UTC \| Google 'Argon2025h1' log \| Qualified 17 Sep 2024 07:07:19 UTC \| DigiCert Yeti2025 Log \| Qualified 17 Sep 2024 07:07:19 UTC \| DigiCert Nessie2025 Log \| Qualified
Fingerprints
SHA1	ce0bfb4b05bb55c3456175967e4e88ddc8c9d0fd
SHA256	b2b8c00e7b82fcd2bc167555f99febc7795024b38396d02035c960fcec060c4a
SPKI SHA256	7e5082aaef2fbd6fb8a0aae8bfc4e3ffdd0cd0c4388907004da5ab88b5d3d8d9

Intermediate certificate

DigiCert SHA2 High Assurance Server CA | 19400be
Not After: 22 Oct 2028 12:00:00 UTC (expires in 3 years 9 months)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Subject DN	CN=DigiCert SHA2 High Assurance Server CA, OU=www.digicert.com, O=DigiCert Inc, C=US
Subject Key Identifier	5168ff90af0207753cccd9656462a212b859723b
Serial	4e1e7a4dc5cf2f36dc02b42b85d159f
Not Before	22 Oct 2013 12:00:00 UTC
Not After	22 Oct 2028 12:00:00 UTC
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	serverAuth, clientAuth
Issuer
Issuer DN	CN=DigiCert High Assurance EV Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Not Applicable
Authority Key Identifier	keyid:b13ec36903f8bf4701d498261a0802ef63642bc3
CRL	http://crl4.digicert.com/DigiCertHighAssuranceEVRootCA.crl
OCSP	http://ocsp.digicert.com
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	a031c46782e6e6c662c2c87c76da9aa62ccabd8e
SHA256	19400be5b7a31fb733917700789d2f0a2471c0c9d506c0e504c06c16d7cb17c0
SPKI SHA256	936bfae7bc41b0e55ed4f411c0eb07b30ddbb064f657322acf92bee7db0d430b

Root certificate

DigiCert High Assurance EV Root CA | 7431e5f
Not After: 10 Nov 2031 00:00:00 UTC (expires in 6 years 10 months)
Authentication: RSA 2048 bits (SHA1withRSA)
View details

Subject DN	CN=DigiCert High Assurance EV Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
Subject Key Identifier	b13ec36903f8bf4701d498261a0802ef63642bc3
Serial	2ac5c266a0b409b8f0b79f2ae462577
Not Before	10 Nov 2006 00:00:00 UTC
Not After	10 Nov 2031 00:00:00 UTC
Key Usage	digitalSignature, keyCertSign, cRLSign
Issuer
Issuer DN	CN=DigiCert High Assurance EV Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Self-signed
Authority Key Identifier	keyid:b13ec36903f8bf4701d498261a0802ef63642bc3
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	5fb7ee0633e259dbad0c4c9ae6d38f1a61c7dc25
SHA256	7431e5f4c3c1ce4690774f0b61e05440883ba9a01ed00ba6abd7806ed3b118cf
SPKI SHA256	5a889647220e54d6bd8a16817224520bb5c78e58984bd570506388b9de0f075f

Analysis

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: 20 Nov 2024 00:00:00 UTC
Not After: 19 Feb 2025 23:59:59 UTC (expires in 1 month 28 days)
Key: RSA 4096 bits
Signature: SHA256withRSA
View details

Names	jp.techcrunch.com external.cap.yahoo.net external-staging.cap.yahoo.net glp.searchjam.com qa-glp.searchjam.com stage-glp.searchjam.com prodramp-glp.searchjam.com testvideo.advertising.yahoo.net dev-astra.commerce.aol.com stg-astra.commerce.aol.com perf-astra.commerce.aol.com astra.commerce.aol.com us.y.ycpi.atwola.com eu.y.ycpi.atwola.com as.y.ycpi.atwola.com .at.atwola.com .mail.yahoo.net .mail.aol.net .jac.yahoosandbox.com .qa-jac.yahoosandbox.com .stage-jac.yahoosandbox.com dmxml.godaddy.overture.com external.graphdb.yk.yahoo.com external-staging.graphdb.yk.yahoo.com order.store.yahoo.net us-dc1-order.store.yahoo.net us-dc2-order.store.yahoo.net .stores.yahoo.net .store.yahoo.net edgecast-img.yahoo.net edgecast-img-staging.yahoo.net www.aol.com s.aol.com homepage.aol.com canary-www.aol.com firefox-startpage.aol.com o2.aol.de www.aol.de welcomescreen.aol.de www.aol.ca www.aol.co.uk o2.welcomescreen.aol.de 200.web.aol.com aolbroadband.welcomescreen.aol.co.uk w.main.welcomescreen.aol.com .forums.rivals.com .n.rivals.com .rivals.com uncrowned.com pbs.www.aol.com pbs.techcrunch.com pbs-staging.www.aol.com pbs-staging.techcrunch.com cdn.desktop.aol.com updates.desktop.aol.com api.alyavista.com .engadget.com datenschutz.aol.de privacy.aol.ca privacy.aol.co.uk privacy.aol.com privacidad.aol.es privacy.aol.de legal.aol.com confidentialite.aol.fr
Subject DN	CN=jp.techcrunch.com, O=Yahoo Holdings Inc., L=New York, ST=New York, C=US
Subject Key Identifier	8c3c62f8b6a728c3e4b288c19b14385e30375679
Serial	e061e8a58e75661a69d89efface5f99
Not Before	20 Nov 2024 00:00:00 UTC
Not After	19 Feb 2025 23:59:59 UTC
Validity period	92 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=DigiCert SHA2 High Assurance Server CA, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:5168ff90af0207753cccd9656462a212b859723b
Parent Certificate	http://cacerts.digicert.com/DigiCertSHA2HighAssuranceServerCA.crt
CRL	http://crl3.digicert.com/sha2-ha-server-g6.crl http://crl4.digicert.com/sha2-ha-server-g6.crl
OCSP	http://ocsp.digicert.com
Certificate Transparency
Signed Certificate Timestamps	20 Nov 2024 17:53:43 UTC \| Google 'Argon2025h1' log \| Qualified 20 Nov 2024 17:53:43 UTC \| DigiCert Nessie2025 Log \| Qualified 20 Nov 2024 17:53:43 UTC \| Cloudflare 'Nimbus2025' \| Qualified
Fingerprints
SHA1	dbb8ea2929f35648659f7b38069aec0be87f9166
SHA256	869479c073f386303a79000a97722cad9fd2a4539055fb591045e1424fbf383c
SPKI SHA256	0274530851947d1a20281220edb30ff859defda3bf03807d14bbb4e7e440ba3f

Analysis

Strong private key

Good. The private key associated with this certificate is secure.

Strong signature algorithm

Good. This certificate uses a strong signature algorithm.

Certificate matches hostname

Good. The provided certificate matches the expected hostnames.

Certificate dates match

Good. The certificate is valid for use at this point of time.

Certificate has not been revoked

Good. This certificate has not been revoked.

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 | 869479c
Not After: 19 Feb 2025 23:59:59 UTC (expires in 1 month 28 days)
Authentication: RSA 4096 bits (SHA256withRSA)
View details

Names	jp.techcrunch.com external.cap.yahoo.net external-staging.cap.yahoo.net glp.searchjam.com qa-glp.searchjam.com stage-glp.searchjam.com prodramp-glp.searchjam.com testvideo.advertising.yahoo.net dev-astra.commerce.aol.com stg-astra.commerce.aol.com perf-astra.commerce.aol.com astra.commerce.aol.com us.y.ycpi.atwola.com eu.y.ycpi.atwola.com as.y.ycpi.atwola.com .at.atwola.com .mail.yahoo.net .mail.aol.net .jac.yahoosandbox.com .qa-jac.yahoosandbox.com .stage-jac.yahoosandbox.com dmxml.godaddy.overture.com external.graphdb.yk.yahoo.com external-staging.graphdb.yk.yahoo.com order.store.yahoo.net us-dc1-order.store.yahoo.net us-dc2-order.store.yahoo.net .stores.yahoo.net .store.yahoo.net edgecast-img.yahoo.net edgecast-img-staging.yahoo.net www.aol.com s.aol.com homepage.aol.com canary-www.aol.com firefox-startpage.aol.com o2.aol.de www.aol.de welcomescreen.aol.de www.aol.ca www.aol.co.uk o2.welcomescreen.aol.de 200.web.aol.com aolbroadband.welcomescreen.aol.co.uk w.main.welcomescreen.aol.com .forums.rivals.com .n.rivals.com .rivals.com uncrowned.com pbs.www.aol.com pbs.techcrunch.com pbs-staging.www.aol.com pbs-staging.techcrunch.com cdn.desktop.aol.com updates.desktop.aol.com api.alyavista.com .engadget.com datenschutz.aol.de privacy.aol.ca privacy.aol.co.uk privacy.aol.com privacidad.aol.es privacy.aol.de legal.aol.com confidentialite.aol.fr
Subject DN	CN=jp.techcrunch.com, O=Yahoo Holdings Inc., L=New York, ST=New York, C=US
Subject Key Identifier	8c3c62f8b6a728c3e4b288c19b14385e30375679
Serial	e061e8a58e75661a69d89efface5f99
Not Before	20 Nov 2024 00:00:00 UTC
Not After	19 Feb 2025 23:59:59 UTC
Validity period	92 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=DigiCert SHA2 High Assurance Server CA, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:5168ff90af0207753cccd9656462a212b859723b
Parent Certificate	http://cacerts.digicert.com/DigiCertSHA2HighAssuranceServerCA.crt
CRL	http://crl3.digicert.com/sha2-ha-server-g6.crl http://crl4.digicert.com/sha2-ha-server-g6.crl
OCSP	http://ocsp.digicert.com
Certificate Transparency
Signed Certificate Timestamps	20 Nov 2024 17:53:43 UTC \| Google 'Argon2025h1' log \| Qualified 20 Nov 2024 17:53:43 UTC \| DigiCert Nessie2025 Log \| Qualified 20 Nov 2024 17:53:43 UTC \| Cloudflare 'Nimbus2025' \| Qualified
Fingerprints
SHA1	dbb8ea2929f35648659f7b38069aec0be87f9166
SHA256	869479c073f386303a79000a97722cad9fd2a4539055fb591045e1424fbf383c
SPKI SHA256	0274530851947d1a20281220edb30ff859defda3bf03807d14bbb4e7e440ba3f

Intermediate certificate

DigiCert SHA2 High Assurance Server CA | 19400be
Not After: 22 Oct 2028 12:00:00 UTC (expires in 3 years 9 months)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Subject DN	CN=DigiCert SHA2 High Assurance Server CA, OU=www.digicert.com, O=DigiCert Inc, C=US
Subject Key Identifier	5168ff90af0207753cccd9656462a212b859723b
Serial	4e1e7a4dc5cf2f36dc02b42b85d159f
Not Before	22 Oct 2013 12:00:00 UTC
Not After	22 Oct 2028 12:00:00 UTC
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	serverAuth, clientAuth
Issuer
Issuer DN	CN=DigiCert High Assurance EV Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Not Applicable
Authority Key Identifier	keyid:b13ec36903f8bf4701d498261a0802ef63642bc3
CRL	http://crl4.digicert.com/DigiCertHighAssuranceEVRootCA.crl
OCSP	http://ocsp.digicert.com
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	a031c46782e6e6c662c2c87c76da9aa62ccabd8e
SHA256	19400be5b7a31fb733917700789d2f0a2471c0c9d506c0e504c06c16d7cb17c0
SPKI SHA256	936bfae7bc41b0e55ed4f411c0eb07b30ddbb064f657322acf92bee7db0d430b

Root certificate

DigiCert High Assurance EV Root CA | 7431e5f
Not After: 10 Nov 2031 00:00:00 UTC (expires in 6 years 10 months)
Authentication: RSA 2048 bits (SHA1withRSA)
View details

Subject DN	CN=DigiCert High Assurance EV Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
Subject Key Identifier	b13ec36903f8bf4701d498261a0802ef63642bc3
Serial	2ac5c266a0b409b8f0b79f2ae462577
Not Before	10 Nov 2006 00:00:00 UTC
Not After	10 Nov 2031 00:00:00 UTC
Key Usage	digitalSignature, keyCertSign, cRLSign
Issuer
Issuer DN	CN=DigiCert High Assurance EV Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Self-signed
Authority Key Identifier	keyid:b13ec36903f8bf4701d498261a0802ef63642bc3
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	5fb7ee0633e259dbad0c4c9ae6d38f1a61c7dc25
SHA256	7431e5f4c3c1ce4690774f0b61e05440883ba9a01ed00ba6abd7806ed3b118cf
SPKI SHA256	5a889647220e54d6bd8a16817224520bb5c78e58984bd570506388b9de0f075f

Analysis

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: 17 Sep 2024 00:00:00 UTC
Not After: 12 Mar 2025 23:59:59 UTC (expires in 2 months 18 days)
Key: EC 256 bits
Signature: SHA256withRSA
View details

Names	src6.yahoo.com alephd.com alephd.fr altomail.com aol.ca aol.co.uk aol.com aol.de aol.fr aol.jp webmail.aol.com.br mail.latino.aol.com att.my.yahoo.com au.be.yahoo.com au.solutions.yahoo.com beboundless.jp blog.postmaster.verizonmedia.com brightroll.com broman.vzbuilders.com corp.aol.com csi.com deals.gdgt.com dns.ops.yahoo.com engadget.com helpisp.netscape.com hk.ent.yahoo.com hk.smartr.yahoo.com hk.youcard.yahoo.com id.berita.yahoo.com id.omg.search.yahoo.com joystiq.com kr.edit.billing.yahoo.com kr.img.search.yahoo.com luxist.com m.order.yahoo.com.tw makers.com mando.data.yahoo.com maw-looker-api.analytics.verizonmedia.com maw.analytics.verizonmedia.com money-a2z.com netdeals.com netfind.com netscape.com no.profiles.yahoo.com oath.com parentdish.ca pets.world ryotstudio.co.uk see-it.live sfrclient.welcome.aol.fr shelterpop.com shopfone.com sport-king.com streampad.com stylelist.com tech24.deals tech247.co thatsfit.ca thegifts.co theparanoids.com think24-7.com tw.discount.yahoo.net tw.smartr.yahoo.com tw.youcard.yahoo.com uk.360.yahoo.com viral.site when.com wmconnect.com wow.com www.altomail.com www.ar.yahoo.com www.brightroll.com www.csi.com www.netscape.com www.theparanoids.com yahoo.dev hk.mobi.yahoo.com tw.mobi.yahoo.com yahooforcreators.com www.yahooforcreators.com www.gamerfeed.com www.gamescanvas.com www.gamedailyxl.com www.yahoogamez.com www.yahoogames.com www.gamesdomain.com gamesdomain.com gamerfeed.com gamescanvas.com gamedailyxl.com yahoogames.com yahoogamez.com
Subject DN	CN=src6.yahoo.com, O=Yahoo Holdings Inc., L=New York, ST=New York, C=US
Subject Key Identifier	7f0856e6b7a135de27c258ffa6f7334dadb35173
Serial	b23d3945ce5ff8ff72bdebb5a8849e4
Not Before	17 Sep 2024 00:00:00 UTC
Not After	12 Mar 2025 23:59:59 UTC
Validity period	177 days
Key Usage	digitalSignature, keyAgreement
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=DigiCert SHA2 High Assurance Server CA, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:5168ff90af0207753cccd9656462a212b859723b
Parent Certificate	http://cacerts.digicert.com/DigiCertSHA2HighAssuranceServerCA.crt
CRL	http://crl3.digicert.com/sha2-ha-server-g6.crl http://crl4.digicert.com/sha2-ha-server-g6.crl
OCSP	http://ocsp.digicert.com
Certificate Transparency
Signed Certificate Timestamps	17 Sep 2024 07:07:56 UTC \| Google 'Argon2025h1' log \| Qualified 17 Sep 2024 07:07:57 UTC \| DigiCert Yeti2025 Log \| Qualified 17 Sep 2024 07:07:57 UTC \| DigiCert Nessie2025 Log \| Qualified
Fingerprints
SHA1	f57d16ce023de665f0bd8e4d97617e04deb0733a
SHA256	13a3f39c24782831112c9eb7c7e127814137944b715d13fe718be75e70dcba45
SPKI SHA256	6a4ca20e32fd9c6c074a9cc3721748f8b857af99e742cf752de9dad3225b2482

Analysis

Strong private key

Good. The private key associated with this certificate is secure.

Strong signature algorithm

Good. This certificate uses a strong signature algorithm.

Certificate matches hostname

Good. The provided certificate matches the expected hostnames.

Certificate dates match

Good. The certificate is valid for use at this point of time.

Certificate has not been revoked

Good. This certificate has not been revoked.

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 | 13a3f39
Not After: 12 Mar 2025 23:59:59 UTC (expires in 2 months 18 days)
Authentication: EC 256 bits (SHA256withRSA)
View details

Names	src6.yahoo.com alephd.com alephd.fr altomail.com aol.ca aol.co.uk aol.com aol.de aol.fr aol.jp webmail.aol.com.br mail.latino.aol.com att.my.yahoo.com au.be.yahoo.com au.solutions.yahoo.com beboundless.jp blog.postmaster.verizonmedia.com brightroll.com broman.vzbuilders.com corp.aol.com csi.com deals.gdgt.com dns.ops.yahoo.com engadget.com helpisp.netscape.com hk.ent.yahoo.com hk.smartr.yahoo.com hk.youcard.yahoo.com id.berita.yahoo.com id.omg.search.yahoo.com joystiq.com kr.edit.billing.yahoo.com kr.img.search.yahoo.com luxist.com m.order.yahoo.com.tw makers.com mando.data.yahoo.com maw-looker-api.analytics.verizonmedia.com maw.analytics.verizonmedia.com money-a2z.com netdeals.com netfind.com netscape.com no.profiles.yahoo.com oath.com parentdish.ca pets.world ryotstudio.co.uk see-it.live sfrclient.welcome.aol.fr shelterpop.com shopfone.com sport-king.com streampad.com stylelist.com tech24.deals tech247.co thatsfit.ca thegifts.co theparanoids.com think24-7.com tw.discount.yahoo.net tw.smartr.yahoo.com tw.youcard.yahoo.com uk.360.yahoo.com viral.site when.com wmconnect.com wow.com www.altomail.com www.ar.yahoo.com www.brightroll.com www.csi.com www.netscape.com www.theparanoids.com yahoo.dev hk.mobi.yahoo.com tw.mobi.yahoo.com yahooforcreators.com www.yahooforcreators.com www.gamerfeed.com www.gamescanvas.com www.gamedailyxl.com www.yahoogamez.com www.yahoogames.com www.gamesdomain.com gamesdomain.com gamerfeed.com gamescanvas.com gamedailyxl.com yahoogames.com yahoogamez.com
Subject DN	CN=src6.yahoo.com, O=Yahoo Holdings Inc., L=New York, ST=New York, C=US
Subject Key Identifier	7f0856e6b7a135de27c258ffa6f7334dadb35173
Serial	b23d3945ce5ff8ff72bdebb5a8849e4
Not Before	17 Sep 2024 00:00:00 UTC
Not After	12 Mar 2025 23:59:59 UTC
Validity period	177 days
Key Usage	digitalSignature, keyAgreement
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=DigiCert SHA2 High Assurance Server CA, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:5168ff90af0207753cccd9656462a212b859723b
Parent Certificate	http://cacerts.digicert.com/DigiCertSHA2HighAssuranceServerCA.crt
CRL	http://crl3.digicert.com/sha2-ha-server-g6.crl http://crl4.digicert.com/sha2-ha-server-g6.crl
OCSP	http://ocsp.digicert.com
Certificate Transparency
Signed Certificate Timestamps	17 Sep 2024 07:07:56 UTC \| Google 'Argon2025h1' log \| Qualified 17 Sep 2024 07:07:57 UTC \| DigiCert Yeti2025 Log \| Qualified 17 Sep 2024 07:07:57 UTC \| DigiCert Nessie2025 Log \| Qualified
Fingerprints
SHA1	f57d16ce023de665f0bd8e4d97617e04deb0733a
SHA256	13a3f39c24782831112c9eb7c7e127814137944b715d13fe718be75e70dcba45
SPKI SHA256	6a4ca20e32fd9c6c074a9cc3721748f8b857af99e742cf752de9dad3225b2482

Intermediate certificate

DigiCert SHA2 High Assurance Server CA | 19400be
Not After: 22 Oct 2028 12:00:00 UTC (expires in 3 years 9 months)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Subject DN	CN=DigiCert SHA2 High Assurance Server CA, OU=www.digicert.com, O=DigiCert Inc, C=US
Subject Key Identifier	5168ff90af0207753cccd9656462a212b859723b
Serial	4e1e7a4dc5cf2f36dc02b42b85d159f
Not Before	22 Oct 2013 12:00:00 UTC
Not After	22 Oct 2028 12:00:00 UTC
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	serverAuth, clientAuth
Issuer
Issuer DN	CN=DigiCert High Assurance EV Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Not Applicable
Authority Key Identifier	keyid:b13ec36903f8bf4701d498261a0802ef63642bc3
CRL	http://crl4.digicert.com/DigiCertHighAssuranceEVRootCA.crl
OCSP	http://ocsp.digicert.com
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	a031c46782e6e6c662c2c87c76da9aa62ccabd8e
SHA256	19400be5b7a31fb733917700789d2f0a2471c0c9d506c0e504c06c16d7cb17c0
SPKI SHA256	936bfae7bc41b0e55ed4f411c0eb07b30ddbb064f657322acf92bee7db0d430b

Root certificate

DigiCert High Assurance EV Root CA | 7431e5f
Not After: 10 Nov 2031 00:00:00 UTC (expires in 6 years 10 months)
Authentication: RSA 2048 bits (SHA1withRSA)
View details

Subject DN	CN=DigiCert High Assurance EV Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
Subject Key Identifier	b13ec36903f8bf4701d498261a0802ef63642bc3
Serial	2ac5c266a0b409b8f0b79f2ae462577
Not Before	10 Nov 2006 00:00:00 UTC
Not After	10 Nov 2031 00:00:00 UTC
Key Usage	digitalSignature, keyCertSign, cRLSign
Issuer
Issuer DN	CN=DigiCert High Assurance EV Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Self-signed
Authority Key Identifier	keyid:b13ec36903f8bf4701d498261a0802ef63642bc3
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	5fb7ee0633e259dbad0c4c9ae6d38f1a61c7dc25
SHA256	7431e5f4c3c1ce4690774f0b61e05440883ba9a01ed00ba6abd7806ed3b118cf
SPKI SHA256	5a889647220e54d6bd8a16817224520bb5c78e58984bd570506388b9de0f075f

Analysis

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=AQABBBBpaGcCEP3zRwoS1t-xK2f_Y3k-YK0FEgEBAQG6aWdyZ9xS0iMA_eMAAA&S=AQAAAoJlwyl1ujuXSbcIAOO_1bg
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

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=AQABBBBpaGcCEP3zRwoS1t-xK2f_Y3k-YK0FEgEBAQG6aWdyZ9xS0iMA_eMAAA&S=AQAAAoJlwyl1ujuXSbcIAOO_1bg
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	Tue Dec 23 01:31:31 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

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=AQABBBBpaGcCEP3zRwoS1t-xK2f_Y3k-YK0FEgEBAQG6aWdyZ9xS0iMA_eMAAA&S=AQAAAoJlwyl1ujuXSbcIAOO_1bg
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	Tue Dec 23 01:31:31 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

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

All cookies are secure

Great. All observed cookies are marked secure.

HTML Content

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

Test passed

Everything seems to be well configured. Well done.

Encryption of Embedded Resources

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

3 script(s)
3 out of 3 are secure View all

Status	Link
Encrypted	https://s.yimg.com/...enji/benji-2.2.24.js
Encrypted	https://s.yimg.com/oa/consent.js
Encrypted	https://consent.cmp.oath.com/...version/7.0.0/cmp.js

13 CSS file(s)
13 out of 13 are secure View all

Status	Link
Encrypted	https://s.aolcdn.com/...ut/main.5504af7d.css
Encrypted	https://s.aolcdn.com/.../custom.5fcdebca.css
Encrypted	https://s.aolcdn.com/...page_v2.450ca5fa.css
Encrypted	https://s.aolcdn.com/...a1a6f956dff4a3bf.css
Encrypted	https://s.aolcdn.com/...444ce5f0a04dfb57.css
Encrypted	https://s.aolcdn.com/...35f949ab045720f0.css
Encrypted	https://s.aolcdn.com/...69e1114b5e2a6cf8.css
Encrypted	https://s.aolcdn.com/...83a88a4e4e6cf5eb.css
Encrypted	https://s.aolcdn.com/...03794bc12e05390f.css
Encrypted	https://s.aolcdn.com/...222b82cbc83c524a.css
Encrypted	https://s.aolcdn.com/...576ed3b2e8deaf38.css
Encrypted	https://s.aolcdn.com/...7455314af8d9b923.css
Encrypted	https://s.aolcdn.com/...833ffbee38781bc8.css

0 media file(s)
0 out of 0 are secure

Encryption of Outbound Links

Ideally, an encrypted page should only have links that lead to other encrypted pages. If plaintext links are used, passive network attackers can see where people go after they visit your web site. It's also possible that some sensitive information is leaked in the Referer header.

0 link(s)
0 out of 0 are encrypted

HTTP Strict Transport Security

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

Test passed, but there are warnings

Some aspect of your site's configuration require your attention.

HSTS Policy Main host

URL from which this policy was obtained.Location	https://www.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

Policy is valid

OK. Your HSTS policy uses correct syntax.

Long policy age

Your HSTS policy has a long max-age value, which offers better protection.

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.

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.

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.

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

Policy is valid

OK. Your HSTS policy uses correct syntax.

Long policy age

Your HSTS policy has a long max-age value, which offers better protection.

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.

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.

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

Mixed content upgraded

Good. This CSP policy instructs browsers to seamlessly upgrade plaintext resources to encryption.

All mixed content is blocked

Good. This CSP policy blocks all mixed content, which includes insecure images that browsers allow.

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

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.2.24.js

https://s.yimg.com/oa/consent.js

https://consent.cmp.oath.com/...version/7.0.0/cmp.js

View all

Status	Link
Remote	https://s.yimg.com/aaq/benji/benji-2.2.24.js
Remote	https://s.yimg.com/oa/consent.js
Remote	https://consent.cmp.oath.com/version/7.0.0/cmp.js

13 CSS file(s)
0 out of 13 are secure

https://s.aolcdn.com/...ut/main.5504af7d.css

https://s.aolcdn.com/.../custom.5fcdebca.css

https://s.aolcdn.com/...page_v2.450ca5fa.css

https://s.aolcdn.com/...a1a6f956dff4a3bf.css

https://s.aolcdn.com/...444ce5f0a04dfb57.css

https://s.aolcdn.com/...35f949ab045720f0.css

https://s.aolcdn.com/...69e1114b5e2a6cf8.css

https://s.aolcdn.com/...83a88a4e4e6cf5eb.css

https://s.aolcdn.com/...03794bc12e05390f.css

https://s.aolcdn.com/...222b82cbc83c524a.css

https://s.aolcdn.com/...576ed3b2e8deaf38.css

https://s.aolcdn.com/...7455314af8d9b923.css

https://s.aolcdn.com/...833ffbee38781bc8.css

View all

Status	Link
Remote	https://s.aolcdn.com/td-app-aol-production/assets/v1/css/layout/main.5504af7d.css
Remote	https://s.aolcdn.com/td-app-aol-production/assets/v1/css/custom.5fcdebca.css
Remote	https://s.aolcdn.com/td-app-aol-production/assets/v1/css/layout/homepage_v2.450ca5fa.css
Remote	https://s.aolcdn.com/caas-assets-production/assets/v1/common.a1a6f956dff4a3bf.css
Remote	https://s.aolcdn.com/caas-assets-production/assets/v1/aol_footer.444ce5f0a04dfb57.css
Remote	https://s.aolcdn.com/caas-assets-production/assets/v1/dispatcher.35f949ab045720f0.css
Remote	https://s.aolcdn.com/caas-assets-production/assets/v1/notification_banner.69e1114b5e2a6cf8.css
Remote	https://s.aolcdn.com/caas-assets-production/assets/v1/dl.83a88a4e4e6cf5eb.css
Remote	https://s.aolcdn.com/caas-assets-production/assets/v1/gam.03794bc12e05390f.css
Remote	https://s.aolcdn.com/caas-assets-production/assets/v1/special_event.222b82cbc83c524a.css
Remote	https://s.aolcdn.com/caas-assets-production/assets/v1/stream.576ed3b2e8deaf38.css
Remote	https://s.aolcdn.com/caas-assets-production/assets/v1/weather.7455314af8d9b923.css
Remote	https://s.aolcdn.com/caas-assets-production/assets/v1/aol_header.833ffbee38781bc8.css

Analysis

SRI required

This page contains remote resources that are under the control of third parties. Deploy SRI to protect them from modification.

Expect CT

Expect-CT is a deprecated response HTTP header designed to enable web sites to monitor problems related to their Certificate Transparency (CT) compliance. Should any CT issues arise, browsers that supported this header will submit reports to the specified reporting endpoint. Chrome was the browser that introduced support for this response header, but later deprecated it and removed it in version 107.

Test failed

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

Expect-CT Policy Invalid

URL from which this policy was obtained.Location

https://www.aol.com/

max-age=31536000, report-uri="http://csp.yahoo.com/beacon/csp?src=yahoocom-expect-ct-report-only

Analysis

Invalid policy syntax

The policy provided by the server is invalid and can't be parsed. Please refer to the Expect-CT specification for more information. If you're configured your policy based on an older version of the specification, please note that newer versions use commas to separate directives. URLs should be enclosed in double quotes.

Analysis

Header information

Policy text: max-age=31536000, report-uri="http://csp.yahoo.com/beacon/csp?src=yahoocom-expect-ct-report-only

Frame Options

The X-Frame-Options header controls page framing, which occurs when a page is incorporated into some other page, possibly on a different site. If framing is allowed, attackers can employ clever tricks to make victims perform arbitrary actions on your site; they do this by showing their web site while forwarding the victim's clicks to yours.

Test passed

Everything seems to be well configured. Well done.

Analysis

Header information

Name: X-Frame-Options

Value: SAMEORIGIN

Framing allowed from the same origin only

OK. Your site allows page framing only from itself. This should generally be safe, except maybe on sites that host user content.

XSS Protection

Some browsers ship with so-called XSS Auditors, built-in defenses against XSS. Although these defenses work against simple reflective XSS attacks, they can be abused by skillful attackers to add weaknesses to otherwise secure web sites. These dangers are present in both filtering and blocking modes. At this time, the Safari browser ships with its XSS defenses enabled by default. For this reason, the best approach is to explicitly disable this functionality.

Test passed, but there are warnings

Some aspect of your site's configuration require your attention.

Analysis

Header information

Name: X-XSS-Protection

Value: 1; mode=block

XSS auditor blocking is dangerous

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

Content Type Options

Some browsers use a technique called content sniffing to override response MIME types provided by HTTP servers and interpret responses as something else (usually HTML). This behavior, which could potentially lead to security issues, should be disabled by attaching an X-Content-Type-Options header to all responses.

Test passed

Everything seems to be well configured. Well done.

Analysis

Header information

Name: X-Content-Type-Options

Value: nosniff

Valid configuration

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

Public Report | aol.com

aol.com

Domain Name System

Email

WWW

Domain Registration

Registration Data Access Protocol (RDAP)

WHOIS

DNS Zone

Nameserver Names

Nameserver Addresses

Start of Authority (SOA) Record

Analysis

Backing DNS Queries

DNS Records

DNS Records

Analysis

Backing DNS Queries

DNSSEC

Useful DNSSEC Tools

Certification Authority Authorization

CAA Policy Information

Analysis

Email (SMTP)

Analysis

Email TLS (SMTP)

TLS Configuration: mx-aol.mail.gm0.yahoodns.net (67.195.204.80) Cached

Analysis

TLS Configuration: mx-aol.mail.gm0.yahoodns.net (67.195.204.75) Cached

Analysis

TLS Configuration: mx-aol.mail.gm0.yahoodns.net (67.195.228.86) Cached

Analysis

TLS Configuration: mx-aol.mail.gm0.yahoodns.net (67.195.228.84) Cached

Analysis

TLS Configuration: mx-aol.mail.gm0.yahoodns.net (98.136.96.93) Cached

Analysis

TLS Configuration: mx-aol.mail.gm0.yahoodns.net (98.136.96.92) Cached

Analysis

Email Certificates (SMTP)

Certificate #1 Cached

Analysis

Certificate Chain

Analysis

Email DANE (SMTP)

SPF

SPF Policy Information Main policy

Analysis

SPF Policy Information Included policy

DMARC

DMARC Policy Information

Analysis

MTA Strict Transport Security

SMTP TLS Reporting

HTTP (80)

URL: http://aol.com/

Analysis

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

Analysis

HTTP (443)

URL: https://aol.com/

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

WWW TLS

TLS Configuration: www.aol.com (2001:4998:14:800:0:0:0:1001)

Analysis

TLS Configuration: www.aol.com (69.147.92.12)

Analysis

TLS Configuration: www.aol.com (69.147.92.11)

Analysis

TLS Configuration: www.aol.com (2001:4998:14:800:0:0:0:1000)

Analysis

TLS Configuration: aol.com (13.248.158.7)

Analysis

TLS Configuration: aol.com (76.223.84.192)

Analysis

WWW Certificates

Certificate: www.aol.com

Analysis

Certificate Trust

Certificate Chain

Analysis