Hardenize Report: apple.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.
There are issues with this site's HTTPS configuration.

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	08 May 2024 06:11 UTC
Source	https://rdap.verisign.com/com/v1/domain/apple.com
Registrar
Registrar	Nom-iq Ltd. dba COM LAUDE
Registrar IANA ID	470
Events
Registration	19 Feb 1987 05:00 UTC
Update	28 Aug 2023 18:33 UTC
Expiration	20 Feb 2025 05:00 UTC
Configuration
Statuses	clientDeleteProhibited clientTransferProhibited clientUpdateProhibited serverDeleteProhibited serverTransferProhibited serverUpdateProhibited
Registrar Lock
Registry Lock
Nameservers	a.ns.apple.com b.ns.apple.com c.ns.apple.com d.ns.apple.com
Contacts
Registrar	Nom-iq Ltd. dba COM LAUDE
Abuse	Email: abuse@comlaude.com Phone: +442074218250

{
  "meta": {
    "timestamp": "2024-05-08T06:11:42Z",
    "id": "173b9b2a-56d2-4e6f-8057-93e329fcf8a2",
    "type": "HZ_REGISTRABLE_DOMAIN",
    "schemaVersion": "2022-02-02",
    "producer": "whois-rdap-clients/2022-03-23",
    "source": "NET",
    "status": "OK",
    "duration": "0.002s"
  },
  "name": "apple.com",
  "punyName": "apple.com",
  "source": "SOURCE_RDAP",
  "sourceLocation": "https://rdap.verisign.com/com/v1/domain/apple.com",
  "sourceRaw": "{\"objectClassName\":\"domain\",\"handle\":\"1225976_DOMAIN_COM-VRSN\",\"ldhName\":\"APPLE.COM\",\"links\":[{\"value\":\"https:\\/\\/rdap.verisign.com\\/com\\/v1\\/domain\\/APPLE.COM\",\"rel\":\"self\",\"href\":\"https:\\/\\/rdap.verisign.com\\/com\\/v1\\/domain\\/APPLE.COM\",\"type\":\"application\\/rdap+json\"},{\"value\":\"https:\\/\\/rdap.comlaude.com\\/rdap\\/domain\\/APPLE.COM\",\"rel\":\"related\",\"href\":\"https:\\/\\/rdap.comlaude.com\\/rdap\\/domain\\/APPLE.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\":\"470\",\"roles\":[\"registrar\"],\"publicIds\":[{\"type\":\"IANA Registrar ID\",\"identifier\":\"470\"}],\"vcardArray\":[\"vcard\",[[\"version\",{},\"text\",\"4.0\"],[\"fn\",{},\"text\",\"Nom-iq Ltd. dba COM LAUDE\"]]],\"entities\":[{\"objectClassName\":\"entity\",\"roles\":[\"abuse\"],\"vcardArray\":[\"vcard\",[[\"version\",{},\"text\",\"4.0\"],[\"fn\",{},\"text\",\"\"],[\"tel\",{\"type\":\"voice\"},\"uri\",\"tel:+442074218250\"],[\"email\",{},\"text\",\"abuse@comlaude.com\"]]]}]}],\"events\":[{\"eventAction\":\"registration\",\"eventDate\":\"1987-02-19T05:00:00Z\"},{\"eventAction\":\"expiration\",\"eventDate\":\"2025-02-20T05:00:00Z\"},{\"eventAction\":\"last changed\",\"eventDate\":\"2023-08-28T18:33:11Z\"},{\"eventAction\":\"last update of RDAP database\",\"eventDate\":\"2024-05-07T22:21:34Z\"}],\"secureDNS\":{\"delegationSigned\":false},\"nameservers\":[{\"objectClassName\":\"nameserver\",\"ldhName\":\"A.NS.APPLE.COM\"},{\"objectClassName\":\"nameserver\",\"ldhName\":\"B.NS.APPLE.COM\"},{\"objectClassName\":\"nameserver\",\"ldhName\":\"C.NS.APPLE.COM\"},{\"objectClassName\":\"nameserver\",\"ldhName\":\"D.NS.APPLE.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": "1987-02-19T05:00:00Z",
  "expireTime": "2025-02-20T05:00:00Z",
  "updateTime": "2023-08-28T18:33:11Z",
  "registrarLock": true,
  "registryLock": true,
  "registrarName": "Nom-iq Ltd. dba COM LAUDE",
  "registrarIanaId": "470",
  "nameservers": [{
    "name": "a.ns.apple.com",
    "punyName": "",
    "addresses": []
  }, {
    "name": "b.ns.apple.com",
    "punyName": "",
    "addresses": []
  }, {
    "name": "c.ns.apple.com",
    "punyName": "",
    "addresses": []
  }, {
    "name": "d.ns.apple.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",
    "organization": "Nom-iq Ltd. dba COM LAUDE"
  }, {
    "type": "CONTACT_ABUSE",
    "email": "abuse@comlaude.com",
    "phone": "+442074218250"
  }]
}

{
  "objectClassName": "domain",
  "handle": "1225976_DOMAIN_COM-VRSN",
  "ldhName": "APPLE.COM",
  "links": [
    {
      "value": "https://rdap.verisign.com/com/v1/domain/APPLE.COM",
      "rel": "self",
      "href": "https://rdap.verisign.com/com/v1/domain/APPLE.COM",
      "type": "application/rdap+json"
    },
    {
      "value": "https://rdap.comlaude.com/rdap/domain/APPLE.COM",
      "rel": "related",
      "href": "https://rdap.comlaude.com/rdap/domain/APPLE.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": "470",
      "roles": [
        "registrar"
      ],
      "publicIds": [
        {
          "type": "IANA Registrar ID",
          "identifier": "470"
        }
      ],
      "vcardArray": [
        "vcard",
        [
          [
            "version",
            {},
            "text",
            "4.0"
          ],
          [
            "fn",
            {},
            "text",
            "Nom-iq Ltd. dba COM LAUDE"
          ]
        ]
      ],
      "entities": [
        {
          "objectClassName": "entity",
          "roles": [
            "abuse"
          ],
          "vcardArray": [
            "vcard",
            [
              [
                "version",
                {},
                "text",
                "4.0"
              ],
              [
                "fn",
                {},
                "text",
                ""
              ],
              [
                "tel",
                {
                  "type": "voice"
                },
                "uri",
                "tel:+442074218250"
              ],
              [
                "email",
                {},
                "text",
                "abuse@comlaude.com"
              ]
            ]
          ]
        }
      ]
    }
  ],
  "events": [
    {
      "eventAction": "registration",
      "eventDate": "1987-02-19T05:00:00Z"
    },
    {
      "eventAction": "expiration",
      "eventDate": "2025-02-20T05:00:00Z"
    },
    {
      "eventAction": "last changed",
      "eventDate": "2023-08-28T18:33:11Z"
    },
    {
      "eventAction": "last update of RDAP database",
      "eventDate": "2024-05-07T22:21:34Z"
    }
  ],
  "secureDNS": {
    "delegationSigned": false
  },
  "nameservers": [
    {
      "objectClassName": "nameserver",
      "ldhName": "A.NS.APPLE.COM"
    },
    {
      "objectClassName": "nameserver",
      "ldhName": "B.NS.APPLE.COM"
    },
    {
      "objectClassName": "nameserver",
      "ldhName": "C.NS.APPLE.COM"
    },
    {
      "objectClassName": "nameserver",
      "ldhName": "D.NS.APPLE.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	Apple Inc.
Lookup Time	08 May 2024 06:11 UTC
Source	whois.comlaude.com:43
Registrar
Registrar	NOM-IQ Ltd dba Com Laude
Registrar IANA ID	470
Events
Registration	19 Feb 1987 05:00 UTC
Update	03 May 2024 09:53 UTC
Expiration	20 Feb 2025 00:00 UTC
Configuration
Statuses	serverTransferProhibited serverUpdateProhibited clientDeleteProhibited serverDeleteProhibited clientTransferProhibited clientUpdateProhibited
Registrar Lock
Registry Lock
Nameservers	a.ns.apple.com b.ns.apple.com c.ns.apple.com d.ns.apple.com
Contacts
Registrar	NOM-IQ Ltd dba Com Laude NOM-IQ Ltd dba Com Laude
Abuse	Email: abuse@comlaude.com Phone: +44.2074218250
Registrant	Apple Inc. US Email: apple.com-Registrant@anonymised.email
Administrative	Email: apple.com-Admin@anonymised.email
Technical	Email: apple.com-Tech@anonymised.email

{
  "meta": {
    "timestamp": "2024-05-08T06:11:42Z",
    "id": "4449ad69-d724-47e0-b0a9-e92fdafc45ee",
    "type": "HZ_REGISTRABLE_DOMAIN",
    "schemaVersion": "2022-02-02",
    "producer": "whois-rdap-clients/2022-03-23",
    "source": "NET",
    "status": "OK",
    "duration": "0.009s"
  },
  "name": "apple.com",
  "punyName": "apple.com",
  "source": "SOURCE_WHOIS",
  "sourceLocation": "whois.comlaude.com:43",
  "sourceRaw": "Domain Name: apple.com\r\nRegistry Domain ID: 1225976_DOMAIN_COM-VRSN\r\nRegistrar WHOIS Server: whois.comlaude.com\r\nRegistrar URL: https://www.comlaude.com\r\nUpdated Date: 2024-05-03T09:53:59Z\r\nCreation Date: 1987-02-19T05:00:00Z\r\nRegistrar Registration Expiration Date: 2025-02-20T00:00:00Z\r\nRegistrar: NOM-IQ Ltd dba Com Laude\r\nRegistrar IANA ID: 470\r\nDomain Status: clientDeleteProhibited https://www.icann.org/epp#clientDeleteProhibited\r\nDomain Status: clientTransferProhibited https://www.icann.org/epp#clientTransferProhibited\r\nDomain Status: clientUpdateProhibited https://www.icann.org/epp#clientUpdateProhibited\r\nDomain Status: serverDeleteProhibited https://www.icann.org/epp#serverDeleteProhibited\r\nDomain Status: serverTransferProhibited https://www.icann.org/epp#serverTransferProhibited\r\nDomain Status: serverUpdateProhibited https://www.icann.org/epp#serverUpdateProhibited\r\nRegistry Registrant ID: REDACTED FOR PRIVACY\r\nRegistrant Name: REDACTED FOR PRIVACY\r\nRegistrant Organization: Apple Inc.\r\nRegistrant Street: REDACTED FOR PRIVACY\r\nRegistrant City: REDACTED FOR PRIVACY\r\nRegistrant State/Province: CA\r\nRegistrant Postal Code: REDACTED FOR PRIVACY\r\nRegistrant Country: US\r\nRegistrant Phone: REDACTED FOR PRIVACY\r\nRegistrant Phone Ext: REDACTED FOR PRIVACY\r\nRegistrant Fax: REDACTED FOR PRIVACY\r\nRegistrant Fax Ext: REDACTED FOR PRIVACY\r\nRegistrant Email: apple.com-Registrant@anonymised.email\r\nRegistry Admin ID: REDACTED FOR PRIVACY\r\nAdmin Name: REDACTED FOR PRIVACY\r\nAdmin Organization: REDACTED FOR PRIVACY\r\nAdmin Street: REDACTED FOR PRIVACY\r\nAdmin City: REDACTED FOR PRIVACY\r\nAdmin State/Province: REDACTED FOR PRIVACY\r\nAdmin Postal Code: REDACTED FOR PRIVACY\r\nAdmin Country: REDACTED FOR PRIVACY\r\nAdmin Phone: REDACTED FOR PRIVACY\r\nAdmin Phone Ext: REDACTED FOR PRIVACY\r\nAdmin Fax: REDACTED FOR PRIVACY\r\nAdmin Fax Ext: REDACTED FOR PRIVACY\r\nAdmin Email: apple.com-Admin@anonymised.email\r\nRegistry Tech ID: REDACTED FOR PRIVACY\r\nTech Name: REDACTED FOR PRIVACY\r\nTech Organization: REDACTED FOR PRIVACY\r\nTech Street: REDACTED FOR PRIVACY\r\nTech City: REDACTED FOR PRIVACY\r\nTech State/Province: REDACTED FOR PRIVACY\r\nTech Postal Code: REDACTED FOR PRIVACY\r\nTech Country: REDACTED FOR PRIVACY\r\nTech Phone: REDACTED FOR PRIVACY\r\nTech Phone Ext: REDACTED FOR PRIVACY\r\nTech Fax: REDACTED FOR PRIVACY\r\nTech Fax Ext: REDACTED FOR PRIVACY\r\nTech Email: apple.com-Tech@anonymised.email\r\nName Server: a.ns.apple.com\r\nName Server: b.ns.apple.com\r\nName Server: c.ns.apple.com\r\nName Server: d.ns.apple.com\r\nDNSSEC: Unsigned Delegation\r\nRegistrar Abuse Contact Email: abuse@comlaude.com\r\nRegistrar Abuse Contact Phone: +44.2074218250\r\nURL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/\r\n\u003e\u003e\u003e Last update of WHOIS database: 2024-05-07T22:20:55Z \u003c\u003c\u003c\r\n\r\nFor more information on Whois status codes, please visit https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en\r\n\r\nPlease query the RDDS service of the Registrar of Record identified in this\r\noutput for information on how to contact the Registrant, Admin, or Tech contact\r\nof the queried domain name.\r\n\r\n-------------------------------------------------------------------------------\r\nCom Laude registers, maintains and renews domain names around the world for \r\nleading intellectual property owners and the law firms that support them.   \r\nIf you have queries about this domain, you may contact us via our website   \r\nat www.comlaude.com.                                                        \r\n-------------------------------------------------------------------------------\r\n\r\nThe data in the Com Laude Whois database is provided to assist you in obtaining\r\ninformation about a domain name registration record.  Com Laude makes this\r\ninformation available \"as is,\" and does not guarantee its accuracy.\r\nBy submitting a WHOIS query, you agree that you will use this data only for\r\nlawful purposes and that, under no circumstances will you use this data to:\r\n\r\n(1) allow, enable, or otherwise support the transmission of mass unsolicited,\r\ncommercial advertising or solicitations via e-mail (spam), telephone or fax; or\r\n(2) enable high volume, automated, electronic processes that that send queries\r\nor data to Com Laude or the systems of any Registry Operator or ICANN-Accredited\r\nregistrar.  The compilation, repackaging, dissemination or other use of this \r\ndata is expressly prohibited without the prior written consent of Com Laude.\r\n\r\nCom Laude reserves the right to modify these terms at any time. By submitting\r\nthis query, you agree to abide by these terms. If you fail to abide by this\r\npolicy, we may terminate your access to this WHOIS database.\r\n\r\n-------------------------------------------------------------------------------\r\nCom Laude protects intellectual property in the domain name system. Com Laude\r\nonly registers domain names for legitimate rights owners. Should you have any \r\nqueries about the legitimacy of this name or our work as a UK based, ICANN \r\nAccredited Registrar, contact us at:\r\nCom Laude, 28 Little Russell Street, London WC1A 2HN, UK.\r\nCom Laude is a business name of Nom IQ Ltd.\r\n-------------------------------------------------------------------------------\r\n\r\n",
  "tld": "com",
  "suffix": "com",
  "createTime": "1987-02-19T05:00:00Z",
  "expireTime": "2025-02-20T00:00:00Z",
  "updateTime": "2024-05-03T09:53:59Z",
  "privacy": true,
  "registrarLock": true,
  "registryLock": true,
  "registrarName": "NOM-IQ Ltd dba Com Laude",
  "registrarIanaId": "470",
  "registrarUrl": "https://www.comlaude.com",
  "registrant": "Apple Inc.",
  "nameservers": [{
    "name": "a.ns.apple.com",
    "punyName": "",
    "addresses": []
  }, {
    "name": "b.ns.apple.com",
    "punyName": "",
    "addresses": []
  }, {
    "name": "c.ns.apple.com",
    "punyName": "",
    "addresses": []
  }, {
    "name": "d.ns.apple.com",
    "punyName": "",
    "addresses": []
  }],
  "statuses": ["serverTransferProhibited", "serverUpdateProhibited", "clientDeleteProhibited", "serverDeleteProhibited", "clientTransferProhibited", "clientUpdateProhibited"],
  "sourceStatuses": ["clientDeleteProhibited https://www.icann.org/epp#clientDeleteProhibited", "clientTransferProhibited https://www.icann.org/epp#clientTransferProhibited", "clientUpdateProhibited https://www.icann.org/epp#clientUpdateProhibited", "serverDeleteProhibited https://www.icann.org/epp#serverDeleteProhibited", "serverTransferProhibited https://www.icann.org/epp#serverTransferProhibited", "serverUpdateProhibited https://www.icann.org/epp#serverUpdateProhibited"],
  "contacts": [{
    "type": "CONTACT_REGISTRAR",
    "firstName": "NOM-IQ Ltd dba Com Laude",
    "organization": "NOM-IQ Ltd dba Com Laude"
  }, {
    "type": "CONTACT_ABUSE",
    "email": "abuse@comlaude.com",
    "phone": "+44.2074218250"
  }, {
    "type": "CONTACT_REGISTRANT",
    "organization": "Apple Inc.",
    "state": "CA",
    "country": "US",
    "email": "apple.com-Registrant@anonymised.email"
  }, {
    "type": "CONTACT_ADMINISTRATIVE",
    "email": "apple.com-Admin@anonymised.email"
  }, {
    "type": "CONTACT_TECHNICAL",
    "email": "apple.com-Tech@anonymised.email"
  }]
}

Domain Name: apple.com
Registry Domain ID: 1225976_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.comlaude.com
Registrar URL: https://www.comlaude.com
Updated Date: 2024-05-03T09:53:59Z
Creation Date: 1987-02-19T05:00:00Z
Registrar Registration Expiration Date: 2025-02-20T00:00:00Z
Registrar: NOM-IQ Ltd dba Com Laude
Registrar IANA ID: 470
Domain Status: clientDeleteProhibited https://www.icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited https://www.icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://www.icann.org/epp#clientUpdateProhibited
Domain Status: serverDeleteProhibited https://www.icann.org/epp#serverDeleteProhibited
Domain Status: serverTransferProhibited https://www.icann.org/epp#serverTransferProhibited
Domain Status: serverUpdateProhibited https://www.icann.org/epp#serverUpdateProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: Apple Inc.
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: CA
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: US
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext: REDACTED FOR PRIVACY
Registrant Email: apple.com-Registrant@anonymised.email
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext: REDACTED FOR PRIVACY
Admin Email: apple.com-Admin@anonymised.email
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext: REDACTED FOR PRIVACY
Tech Email: apple.com-Tech@anonymised.email
Name Server: a.ns.apple.com
Name Server: b.ns.apple.com
Name Server: c.ns.apple.com
Name Server: d.ns.apple.com
DNSSEC: Unsigned Delegation
Registrar Abuse Contact Email: abuse@comlaude.com
Registrar Abuse Contact Phone: +44.2074218250
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2024-05-07T22:20:55Z <<<

For more information on Whois status codes, please visit https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en

Please query the RDDS service of the Registrar of Record identified in this
output for information on how to contact the Registrant, Admin, or Tech contact
of the queried domain name.

-------------------------------------------------------------------------------
Com Laude registers, maintains and renews domain names around the world for 
leading intellectual property owners and the law firms that support them.   
If you have queries about this domain, you may contact us via our website   
at www.comlaude.com.                                                        
-------------------------------------------------------------------------------

The data in the Com Laude Whois database is provided to assist you in obtaining
information about a domain name registration record.  Com Laude makes this
information available "as is," and does not guarantee 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 of mass unsolicited,
commercial advertising or solicitations via e-mail (spam), telephone or fax; or
(2) enable high volume, automated, electronic processes that that send queries
or data to Com Laude or the systems of any Registry Operator or ICANN-Accredited
registrar.  The compilation, repackaging, dissemination or other use of this 
data is expressly prohibited without the prior written consent of Com Laude.

Com Laude reserves the right to modify these terms at any time. By submitting
this query, you agree to abide by these terms. If you fail to abide by this
policy, we may terminate your access to this WHOIS database.

-------------------------------------------------------------------------------
Com Laude protects intellectual property in the domain name system. Com Laude
only registers domain names for legitimate rights owners. Should you have any 
queries about the legitimacy of this name or our work as a UK based, ICANN 
Accredited Registrar, contact us at:
Com Laude, 28 Little Russell Street, London WC1A 2HN, UK.
Com Laude is a business name of Nom IQ Ltd.
-------------------------------------------------------------------------------

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
a.ns.apple.com. 17.253.200.1 2620:149:ae0::53				NS REFERRAL
b.ns.apple.com. 17.253.207.1 2620:149:ae7::53				NS REFERRAL
c.ns.apple.com. 204.19.119.1 2620:171:800:714::1				NS REFERRAL
d.ns.apple.com. 204.26.57.1 2620:171:801:714::1				NS REFERRAL
usmsc2-extxfr-001.dns.apple.com. STEALTH PRIMARY 17.47.176.10				SOA

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
17.253.200.1 a.ns.apple.com. PTR: a.ns.apple.com.	NAME, GLUE	1232
17.253.207.1 b.ns.apple.com. PTR: b.ns.apple.com.	NAME, GLUE	1232
17.47.176.10 STEALTH PRIMARY usmsc2-extxfr-001.dns.apple.com. PTR: usmsc2-extxfr-001.dns.apple.com.	NAME	1220
204.19.119.1 c.ns.apple.com. PTR: c.ns.apple.com.	NAME, GLUE	1232
204.26.57.1 d.ns.apple.com. PTR: d.ns.apple.com.	NAME, GLUE	1232
2620:149:ae0::53 a.ns.apple.com. PTR: a.ns.apple.com.	NAME, GLUE	1232
2620:149:ae7::53 b.ns.apple.com. PTR: b.ns.apple.com.	NAME, GLUE	1232
2620:171:800:714::1 c.ns.apple.com. PTR: c.ns.apple.com.	NAME, GLUE	1232
2620:171:801:714::1 d.ns.apple.com. PTR: d.ns.apple.com.	NAME, GLUE	1232

Start of Authority (SOA) Record

Start of Authority (SOA) records contain administrative information pertaining to one DNS zone, especially the configuration that's used for zone transfers between the primary nameserver and the secondaries. Only one SOA record should exist, with all nameservers providing the same information.

The domain name of the primary nameserver for the zone. Also known as MNAME.Primary nameserver	usmsc2-extxfr-001.dns.apple.com.
Email address of the persons responsible for this zone. Also known as RNAME.Admin email	hostmaster.apple.com.
Zone serial or version number.Serial number	2010131442
The length of time secondary nameservers should wait before querying the primary for changes.Refresh interval	900 seconds (about 15 minutes)
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	2,016,000 seconds (about 23 days 8 hours)
TTL for purposes of negative response caching. Negative cache TTL	14,400 seconds (about 4 hours)
Time To Live (TTL) indicates for how long a record remains valid. SOA record TTL	43,200 seconds (about 12 hours)

Analysis

No problems detected with the zone configuration

Excellent. This DNS zone is in a good working order. No problems detected.

Backing DNS Queries

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

	ID	Server	Transport	Question Name	Type	Status

DNS Records

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

Test passed

Everything seems to be well configured. Well done.

DNS Records

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

Name	TTL	Type	Data
apple.com.	900	A	17.253.144.10
www.apple.com.	1800	CNAME	www.apple.com.edgekey.net.
www.apple.com.edgekey.net.	21600	CNAME	www.apple.com.edgekey.net.globalredir.akadns.net.
www.apple.com.edgekey.net.globalredir.akadns.net.	3600	CNAME	e6858.dscx.akamaiedge.net.
e6858.dscx.akamaiedge.net.	20	A	23.212.144.237
apple.com.	900	AAAA	2620:149:af0:0:0:0:0:10
e6858.dscx.akamaiedge.net.	20	AAAA	2600:1408:c400:1886:0:0:0:1aca
e6858.dscx.akamaiedge.net.	20	AAAA	2600:1408:c400:1889:0:0:0:1aca
apple.com.	299	CAA	0 issue "pki.apple.com"
apple.com.	299	CAA	0 issue "entrust.net"
apple.com.	299	CAA	0 iodef "mailto:contact_pki@apple.com"
apple.com.	3600	MX	20 mx-in-hfd.apple.com.
apple.com.	3600	MX	20 mx-in-vib.apple.com.
apple.com.	3600	MX	10 mx-in.g.apple.com.
apple.com.	3600	MX	20 mx-in-mdn.apple.com.
apple.com.	3600	MX	20 mx-in-rno.apple.com.
apple.com.	43200	NS	d.ns.apple.com.
apple.com.	43200	NS	a.ns.apple.com.
apple.com.	43200	NS	b.ns.apple.com.
apple.com.	43200	NS	c.ns.apple.com.
apple.com.	43200	SOA	usmsc2-extxfr-001.dns.apple.com. hostmaster.apple.com. 2010131442 900 900 2016000 14400
_sip._tls.apple.com.	3600	SRV	5 5 5060 gslb-b2b-ext.v.aaplimg.com.
apple.com.	3600	TXT	"apple-domain-verification=X5Jt76bn3Dnmgzjj"
apple.com.	3600	TXT	"cerner-client-id=22dd1d8a-5e8b-4e1e-80ef-39bcdfd42798"
apple.com.	3600	TXT	"cerner-client-id=ce3abf18-ee87-43b9-9927-9eb24b4bac4a"
apple.com.	3600	TXT	"ValidationTokenValue=77a4a6de-da14-449c-83c4-85366e0f55f9"
apple.com.	3600	TXT	"miro-verification=2494d255c4c50b1e521650a0659cbf3fa08b0072"
apple.com.	3600	TXT	"facebook-domain-verification=n6cqjfucq6plswmtfbwnbbeu1qiq3v"
apple.com.	3600	TXT	"v=spf1 include:_spf.apple.com include:_spf-txn.apple.com ~all"
apple.com.	3600	TXT	"adobe-idp-site-verification=6bd5e74c-a3a0-4781-b2e1-e95399b5e11c"
apple.com.	3600	TXT	"webexdomainverification.8C462=b728ec3f-dfc9-42f9-92cb-9ba8853cbee8"
apple.com.	3600	TXT	"google-site-verification=8M6XjQCzydT62jk8HY3VXPAG-nKDllTRV-JpA3-Ktyw"
apple.com.	3600	TXT	"google-site-verification=L5kkMdiFI8npvb6KlHui84fJaCw5G64DWhaDRIAT4_c"
apple.com.	3600	TXT	"google-site-verification=zBSq1mG5ssu2If-C17UAz_MzSZDcx03MVxmeDwMNc5w"
apple.com.	3600	TXT	"cisco-ci-domain-verification=6f3bfb849796a518061f8e8c4356f687a138502d86db742791685059176547dd"
apple.com.	3600	TXT	"Dynatrace-site-verification=7d881a7c-c13f-4146-9d27-2731459e2509__iqls0105tagglcsaul0m16ibrf"
apple.com.	3600	TXT	"atlassian-domain-verification=mLabq99iaT8kquJechF6l31FAYoNUe3WB7tLpLFUiUYVJCse9SKq83hOJzFkwqrh"
apple.com.	3600	TXT	"json:eyJ3aHkiOiJUaGlzIGlzIHRvIHRydW5jYXRlIFVEUCByZXNwb25zZXMgZm9yIFRYVCBxdWVyaWVzIHRvIGFwcGxlLmNvbSIsInBhZGRpbmciOiJpZW4wYWVHaGF0aG9oNmhhaHZpZWphaTNlYXkwYWh2YWhjaGFocXVhZWxlZTBZdWw0cGhpZXRoMHNvNXZpZXllZWNvaDRpZThzaGVlcGllVDNwYWVjaGVpVjZqb2h3aWVwaG82In0K"
apple.com.	3600	TXT	"json:eyJ3aHkiOiJUaGlzIGlzIHRvIHRydW5jYXRlIFVEUCByZXNwb25zZXMgZm9yIFRYVCBxdWVyaWVzIHRvIGFwcGxlLmNvbSIsInBhZGRpbmciOiJxdWFoMGVpamFhNGVlajh0aWVkYWlnaG9jZWljaGFlOGVUb3ppZTVmdTVhaFRoMldlaU00aWsyaHVxdThpZXBoaWVxdW9oc2hlaXBhZWdoOUthZWw3b2NoaWVuZ2llem9lc2g1In0K"
apple.com.	3600	TXT	"77a4a6de-da14-449c-83c4-85366e0f55f9"
_dmarc.apple.com.	3600	TXT	"v=DMARC1; p=quarantine; sp=reject; rua=mailto:d@rua.agari.com; ruf=mailto:d@ruf.agari.com;"
_mta-sts.apple.com.	3600	TXT	"v=spf1 redirect=_spf.apple.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	apple.com
The issue property tag is used to request that certificate issuers perform CAA issue restriction processing for the domain and to grant authorization to specific certificate issuers.issue	entrust.net flags: 0
The issue property tag is used to request that certificate issuers perform CAA issue restriction processing for the domain and to grant authorization to specific certificate issuers.issue	pki.apple.com flags: 0
The iodef property specifies a means of reporting certificate issue requests or cases of certificate issue for the corresponding domain that violate the security policy of the issuer or the domain name holder.iodef	mailto:contact_pki@apple.com flags: 0

Analysis

CAA policy found

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

Policy uses reporting

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

Email (SMTP)

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

Test passed

Everything seems to be well configured. Well done.

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

Server	Preference	Operational	STARTTLS	TLS	PKI	DNSSEC	DANE
mx-in.g.apple.com 17.32.222.242 PTR: mx-in-mdn.apple.com	10
mx-in-mdn.apple.com 17.32.222.242 PTR: mx-in-mdn.apple.com	20
mx-in-rno.apple.com 17.179.253.242 PTR: mx-in-rno.apple.com	20
mx-in-hfd.apple.com 17.57.165.2 PTR: mx-in-hfd.apple.com	20
mx-in-vib.apple.com 17.57.170.2 PTR: mx-in-vib.apple.com	20

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: 06 May 2024 22:10 UTC

Earliest cache timestamp: 06 May 2024 22:10 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-in.g.apple.com (17.32.222.242) Cached

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.2
Shows cipher suite configuration for this protocol version.TLS v1.2	Suite: TLS_ECDHE_RSA_WITH_AES_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	06 May 2024 22:10 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-in-mdn.apple.com (17.32.222.242) Cached

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.2
Shows cipher suite configuration for this protocol version.TLS v1.2	Suite: TLS_ECDHE_RSA_WITH_AES_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	06 May 2024 22:10 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-in-rno.apple.com (17.179.253.242) Cached

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.2
Shows cipher suite configuration for this protocol version.TLS v1.2	Suite: TLS_ECDHE_RSA_WITH_AES_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	06 May 2024 22:10 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-in-hfd.apple.com (17.57.165.2) 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	06 May 2024 22:10 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-in-vib.apple.com (17.57.170.2) 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	06 May 2024 22:10 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

mx-in.g.apple.com
Issuer: Apple Inc.
Not Before: 30 Apr 2024 13:04:19 UTC
Not After: 29 Jul 2024 13:14:19 UTC (expires in 2 months 21 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
View details

Names	mx-in-sng.apple.com mx-in-mdn.apple.com mx-in-rno.apple.com mx-in-hfd.apple.com mx-in-vib.apple.com mx-in.g.apple.com
Subject DN	CN=mx-in.g.apple.com, O=Apple Inc., ST=California, C=US
Subject Key Identifier	fda1866799341bfb3c4711ae1b897592518de29c
Serial	6bd58b623c5c551cdc8b017556c254cc
Not Before	30 Apr 2024 13:04:19 UTC
Not After	29 Jul 2024 13:14:19 UTC
Validity period	91 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth
Must Staple	No
Issuer
Issuer DN	C=US, ST=California, O=Apple Inc., CN=Apple Public Server RSA CA 11 - G1
Certification Authority	Apple Inc.
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:5002b8132c1583d141c3118a8b423b012343a956
Parent Certificate	http://certs.apple.com/apsrsaca11g1.der
CRL	http://crl.apple.com/apsrsaca11g1.crl
OCSP	http://ocsp.apple.com/ocsp03-apsrsaca11g1
Certificate Transparency
Signed Certificate Timestamps	30 Apr 2024 13:14:20 UTC \| Let's Encrypt 'Oak2024H2' log \| Qualified 30 Apr 2024 13:14:20 UTC \| DigiCert Yeti2024 Log \| Qualified 30 Apr 2024 13:14:20 UTC \| Google 'Xenon2024' log \| Qualified 30 Apr 2024 13:14:20 UTC \| Cloudflare 'Nimbus2024' Log \| Qualified
Fingerprints
SHA1	87b0074a32693b8faa62018d967bea5771070975
SHA256	d3493fbb2fd9c1c3aafdb714aa7c694316696273241afd15e796b8f33b63be5c
SPKI SHA256	07bbe9ab02e2dcc204fa40ecd1e1352801d0d5a0717a3d236c9d71b4d12ca775

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

mx-in.g.apple.com | d3493fb
Not After: 29 Jul 2024 13:14:19 UTC (expires in 2 months 21 days)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Names	mx-in-sng.apple.com mx-in-mdn.apple.com mx-in-rno.apple.com mx-in-hfd.apple.com mx-in-vib.apple.com mx-in.g.apple.com
Subject DN	CN=mx-in.g.apple.com, O=Apple Inc., ST=California, C=US
Subject Key Identifier	fda1866799341bfb3c4711ae1b897592518de29c
Serial	6bd58b623c5c551cdc8b017556c254cc
Not Before	30 Apr 2024 13:04:19 UTC
Not After	29 Jul 2024 13:14:19 UTC
Validity period	91 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth
Must Staple	No
Issuer
Issuer DN	C=US, ST=California, O=Apple Inc., CN=Apple Public Server RSA CA 11 - G1
Certification Authority	Apple Inc.
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:5002b8132c1583d141c3118a8b423b012343a956
Parent Certificate	http://certs.apple.com/apsrsaca11g1.der
CRL	http://crl.apple.com/apsrsaca11g1.crl
OCSP	http://ocsp.apple.com/ocsp03-apsrsaca11g1
Certificate Transparency
Signed Certificate Timestamps	30 Apr 2024 13:14:20 UTC \| Let's Encrypt 'Oak2024H2' log \| Qualified 30 Apr 2024 13:14:20 UTC \| DigiCert Yeti2024 Log \| Qualified 30 Apr 2024 13:14:20 UTC \| Google 'Xenon2024' log \| Qualified 30 Apr 2024 13:14:20 UTC \| Cloudflare 'Nimbus2024' Log \| Qualified
Fingerprints
SHA1	87b0074a32693b8faa62018d967bea5771070975
SHA256	d3493fbb2fd9c1c3aafdb714aa7c694316696273241afd15e796b8f33b63be5c
SPKI SHA256	07bbe9ab02e2dcc204fa40ecd1e1352801d0d5a0717a3d236c9d71b4d12ca775

Intermediate certificate

Apple Public Server RSA CA 11 - G1 | 6c66578
Not After: 04 Dec 2030 23:59:59 UTC (expires in 6 years 6 months)
Authentication: RSA 2048 bits (SHA384withRSA)
View details

Subject DN	C=US, ST=California, O=Apple Inc., CN=Apple Public Server RSA CA 11 - G1
Subject Key Identifier	5002b8132c1583d141c3118a8b423b012343a956
Serial	5dfabb9577cfab671fc7ddfed1cf205b
Not Before	19 Jun 2019 00:00:00 UTC
Not After	04 Dec 2030 23:59:59 UTC
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	serverAuth, clientAuth
Issuer
Issuer DN	CN=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, ST=New Jersey, C=US
Certification Authority	Sectigo
Validation Type	Not Applicable
Authority Key Identifier	keyid:5379bf5aaa2b4acf5480e1d89bc09df2b20366cb
CRL	http://crl.usertrust.com/USERTrustRSACertificationAuthority.crl
OCSP	http://ocsp.usertrust.com
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	714fc0240b1c3d6276c52d854f563f848c5995e7
SHA256	6c66578dc96ad13eb7b688bdc09db472d5fbf03b3bd21309665052a886d7e9b4
SPKI SHA256	c570d7b37e68cdc8f09342601ce9883be257431b5ad5b6fdad0d7815512a7561

Root certificate

USERTrust RSA Certification Authority | e793c9b
Not After: 18 Jan 2038 23:59:59 UTC (expires in 13 years 8 months)
Authentication: RSA 4096 bits (SHA384withRSA)
View details

Subject DN	CN=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, ST=New Jersey, C=US
Subject Key Identifier	5379bf5aaa2b4acf5480e1d89bc09df2b20366cb
Serial	1fd6d30fca3ca51a81bbc640e35032d
Not Before	01 Feb 2010 00:00:00 UTC
Not After	18 Jan 2038 23:59:59 UTC
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, ST=New Jersey, C=US
Certification Authority	Sectigo
Validation Type	Self-signed
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	2b8f1b57330dbba2d07a6c51f70ee90ddab9ad8e
SHA256	e793c9b02fd8aa13e21c31228accb08119643b749c898964b1746d46c3d4cbd2
SPKI SHA256	c784333d20bcd742b9fdc3236f4e509b8937070e73067e254dd3bf9c45bf4dde

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	apple.com
SPF version used by this policy.v	spf1
Evaluates SPF policy specified in another DNS location. This directive is typically used to allow hosts controlled by another organization. include	_spf.apple.com
Evaluates SPF policy specified in another DNS location. This directive is typically used to allow hosts controlled by another organization. include	_spf-txn.apple.com
This policy element always matches. It's normally used at the end of a policy to specify the handling of hosts that don't match earlier mechanisms. ~all

Analysis

SPF policy found

Policy text: v=spf1 include:_spf.apple.com include:_spf-txn.apple.com ~all

Location: apple.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: 2

SPF Policy Information Included policy

Host where this policy is located.Location	_spf.apple.com
SPF version used by this policy.v	spf1
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	17.151.62.66
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	17.151.62.67
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	17.151.62.68
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	17.171.2.60
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	17.171.2.68
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	17.171.2.72
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	17.179.253.33
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	17.179.253.34
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	17.179.253.38
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	17.179.253.39
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	17.179.253.43
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	17.179.253.44
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	17.179.253.48
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	17.179.253.49
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	17.179.253.22/31
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	17.179.253.24/31
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	17.32.222.22/31
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	17.32.222.24/31
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	17.72.136.23
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	17.72.136.24/31
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	17.132.96.0/31
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	17.132.100.0/31
This policy element always matches. It's normally used at the end of a policy to specify the handling of hosts that don't match earlier mechanisms. ~all

SPF Policy Information Included policy

Host where this policy is located.Location	_spf-txn.apple.com
SPF version used by this policy.v	spf1
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	17.151.1.0/24
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	17.171.37.0/24
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	17.111.110.0/23
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	17.23.6.0/24
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.apple.com
DMARC version used by this policy.v	DMARC1
Indicates the policy to be enacted by the receiver at the request of the domain owner. Possible values are: none, quarantine, and reject.p	quarantine
Requested mail receiver policy for all subdomains. Same format as for the p tag.sp	reject
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=quarantine; sp=reject; rua=mailto:d@rua.agari.com; ruf=mailto:d@ruf.agari.com;

Host: _dmarc.apple.com

Valid external destination

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

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

Permission record contents: v=DMARC1;

Valid external destination

Permission record location: apple.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://apple.com/

1

http://apple.com/

HTTP/1.1 301 Redirect

Date	Wed, 08 May 2024 06:11:42 GMT
Connection	close
Via	http/1.1 usqas2-edge-bx-018.ts.apple.com (acdn/153.14426)
Cache-Control	no-store
Location	https://www.apple.com/
Content-Type	text/html
Content-Language	en
X-Cache	none
CDNUUID	8f9034fa-b408-4b93-8df9-3f8ccfba132f-11486281132
Content-Length	304

2

https://www.apple.com/

HTTP/1.1 200 OK

Server	Apple
Content-Type	text/html; charset=utf-8
Set-Cookie	geo=US; path=/; domain=.apple.com
X-Frame-Options	SAMEORIGIN
Vary	Accept-Encoding
Content-Security-Policy	default-src 'self' blob: data: .akamaized.net .apple.com .apple-mapkit.com .cdn-apple.com .organicfruitapps.com; child-src blob: embed.music.apple.com embed.podcasts.apple.com https://recyclingprogram.apple.com swdlp.apple.com www.apple.com www.instagram.com platform.twitter.com www.youtube-nocookie.com; img-src 'unsafe-inline' blob: data: .apple.com .apple-mapkit.com .cdn-apple.com .mzstatic.com; script-src 'unsafe-inline' 'unsafe-eval' blob: .apple.com .apple-mapkit.com www.instagram.com platform.twitter.com; style-src 'unsafe-inline' .apple.com
Referrer-Policy	no-referrer-when-downgrade
Strict-Transport-Security	max-age=31536000; includeSubdomains; preload
X-Content-Type-Options	nosniff
X-Xss-Protection	1; mode=block
Cache-Control	max-age=0
Expires	Wed, 08 May 2024 06:11:42 GMT
Date	Wed, 08 May 2024 06:11:42 GMT
X-Cache	TCP_MEM_HIT from a23-62-155-205.deploy.akamaitechnologies.com (AkamaiGHost/11.5.0.1-56208139) (-)
Connection	keep-alive

Analysis

HTTP redirects to HTTPS

Good. This plaintext HTTP server redirects to HTTPS.

URL: http://www.apple.com/

1

http://www.apple.com/

HTTP/1.1 301 Moved Permanently

Server	AkamaiGHost
Content-Length	0
Location	https://www.apple.com/
Cache-Control	max-age=0
Expires	Wed, 08 May 2024 06:11:42 GMT
Date	Wed, 08 May 2024 06:11:42 GMT
X-Cache	TCP_MISS from a23-34-240-244.deploy.akamaitechnologies.com (AkamaiGHost/11.5.0.1-56208139) (-)
Connection	keep-alive
strict-transport-security	max-age=31536000
Set-Cookie	geo=US; path=/; domain=.apple.com

2

https://www.apple.com/

HTTP/1.1 200 OK

Server	Apple
Content-Type	text/html; charset=utf-8
X-Frame-Options	SAMEORIGIN
Vary	Accept-Encoding
Content-Security-Policy	default-src 'self' blob: data: .akamaized.net .apple.com .apple-mapkit.com .cdn-apple.com .organicfruitapps.com; child-src blob: embed.music.apple.com embed.podcasts.apple.com https://recyclingprogram.apple.com swdlp.apple.com www.apple.com www.instagram.com platform.twitter.com www.youtube-nocookie.com; img-src 'unsafe-inline' blob: data: .apple.com .apple-mapkit.com .cdn-apple.com .mzstatic.com; script-src 'unsafe-inline' 'unsafe-eval' blob: .apple.com .apple-mapkit.com www.instagram.com platform.twitter.com; style-src 'unsafe-inline' .apple.com
Referrer-Policy	no-referrer-when-downgrade
Strict-Transport-Security	max-age=31536000; includeSubdomains; preload
X-Content-Type-Options	nosniff
X-Xss-Protection	1; mode=block
Cache-Control	max-age=0
Expires	Wed, 08 May 2024 06:11:43 GMT
Date	Wed, 08 May 2024 06:11:43 GMT
X-Cache	TCP_MEM_HIT from a23-34-240-215.deploy.akamaitechnologies.com (AkamaiGHost/11.5.0.1-56208139) (-)
Connection	keep-alive

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://apple.com/

1

https://apple.com/

HTTP/1.1 301 Redirect

Date	Wed, 08 May 2024 06:11:43 GMT
Connection	close
Via	http/1.1 usqas2-edge-bx-009.ts.apple.com (acdn/153.14426)
Cache-Control	no-store
Location	https://www.apple.com/
Content-Type	text/html
Content-Language	en
X-Cache	none
CDNUUID	39981819-a1e9-4693-b62a-057485c28036-6688454332
Content-Length	304

2

https://www.apple.com/

HTTP/1.1 200 OK

Server	Apple
Content-Type	text/html; charset=utf-8
Set-Cookie	geo=US; path=/; domain=.apple.com
X-Frame-Options	SAMEORIGIN
Vary	Accept-Encoding
Content-Security-Policy	default-src 'self' blob: data: .akamaized.net .apple.com .apple-mapkit.com .cdn-apple.com .organicfruitapps.com; child-src blob: embed.music.apple.com embed.podcasts.apple.com https://recyclingprogram.apple.com swdlp.apple.com www.apple.com www.instagram.com platform.twitter.com www.youtube-nocookie.com; img-src 'unsafe-inline' blob: data: .apple.com .apple-mapkit.com .cdn-apple.com .mzstatic.com; script-src 'unsafe-inline' 'unsafe-eval' blob: .apple.com .apple-mapkit.com www.instagram.com platform.twitter.com; style-src 'unsafe-inline' .apple.com
Referrer-Policy	no-referrer-when-downgrade
Strict-Transport-Security	max-age=31536000; includeSubdomains; preload
X-Content-Type-Options	nosniff
X-Xss-Protection	1; mode=block
Cache-Control	max-age=0
Expires	Wed, 08 May 2024 06:11:43 GMT
Date	Wed, 08 May 2024 06:11:43 GMT
X-Cache	TCP_MEM_HIT from a23-62-155-202.deploy.akamaitechnologies.com (AkamaiGHost/11.5.0.1-56208139) (-)
Connection	keep-alive

URL: https://www.apple.com/

1

https://www.apple.com/

HTTP/1.1 200 OK

Server	Apple
Content-Type	text/html; charset=utf-8
Set-Cookie	geo=US; path=/; domain=.apple.com
X-Frame-Options	SAMEORIGIN
Vary	Accept-Encoding
Content-Security-Policy	default-src 'self' blob: data: .akamaized.net .apple.com .apple-mapkit.com .cdn-apple.com .organicfruitapps.com; child-src blob: embed.music.apple.com embed.podcasts.apple.com https://recyclingprogram.apple.com swdlp.apple.com www.apple.com www.instagram.com platform.twitter.com www.youtube-nocookie.com; img-src 'unsafe-inline' blob: data: .apple.com .apple-mapkit.com .cdn-apple.com .mzstatic.com; script-src 'unsafe-inline' 'unsafe-eval' blob: .apple.com .apple-mapkit.com www.instagram.com platform.twitter.com; style-src 'unsafe-inline' .apple.com
Referrer-Policy	no-referrer-when-downgrade
Strict-Transport-Security	max-age=31536000; includeSubdomains; preload
X-Content-Type-Options	nosniff
X-Xss-Protection	1; mode=block
Cache-Control	max-age=0
Expires	Wed, 08 May 2024 06:11:43 GMT
Date	Wed, 08 May 2024 06:11:43 GMT
X-Cache	TCP_MEM_HIT from a23-34-240-244.deploy.akamaitechnologies.com (AkamaiGHost/11.5.0.1-56208139) (-)
Connection	keep-alive

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: apple.com (2620:149:af0:0:0:0:0:10)

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

Analysis

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.

Deprecated protocols not supported

Excellent. This server doesn't support any of the deprecated protocol (TLS 1.1 and earlier).

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 settings 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: apple.com (17.253.144.10)

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

Analysis

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.

Deprecated protocols not supported

Excellent. This server doesn't support any of the deprecated protocol (TLS 1.1 and earlier).

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 settings 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.apple.com (2600:1408:c400:1889:0:0:0:1aca)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.3 TLS v1.2
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3 Server preference	Suite: TLS_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_AES_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_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_128_CCM_8_SHA256 Suite ID: 0x1305 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_CCM_8_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_AES_128_CCM_SHA256 Suite ID: 0x1304 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_CCM_SHA256 128 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC secp256r1 (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_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC secp256r1 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) 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 secp256r1 (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_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 secp256r1 (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_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 secp256r1 (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_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 secp256r1 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_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 secp256r1 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0x9d Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA384 TLS_RSA_WITH_AES_256_GCM_SHA384 256 bits Suite: TLS_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0x9c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_GCM_SHA256 128 bits Suite: TLS_RSA_WITH_AES_256_CBC_SHA256 Suite ID: 0x3d Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_256_CBC_SHA256 256 bits Suite: TLS_RSA_WITH_AES_128_CBC_SHA256 Suite ID: 0x3c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_CBC_SHA256 128 bits Suite: TLS_RSA_WITH_AES_256_CBC_SHA Suite ID: 0x35 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_256_CBC_SHA 256 bits Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits

Analysis

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.

Deprecated protocols not supported

Excellent. This server doesn't support any of the deprecated protocol (TLS 1.1 and earlier).

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 settings 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.apple.com (23.212.144.237)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.3 TLS v1.2
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3 Server preference	Suite: TLS_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_AES_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_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_128_CCM_8_SHA256 Suite ID: 0x1305 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_CCM_8_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_AES_128_CCM_SHA256 Suite ID: 0x1304 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_CCM_SHA256 128 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC secp256r1 (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_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC secp256r1 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) 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 secp256r1 (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_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 secp256r1 (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_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 secp256r1 (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_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 secp256r1 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_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 secp256r1 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0x9d Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA384 TLS_RSA_WITH_AES_256_GCM_SHA384 256 bits Suite: TLS_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0x9c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_GCM_SHA256 128 bits Suite: TLS_RSA_WITH_AES_256_CBC_SHA256 Suite ID: 0x3d Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_256_CBC_SHA256 256 bits Suite: TLS_RSA_WITH_AES_128_CBC_SHA256 Suite ID: 0x3c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_CBC_SHA256 128 bits Suite: TLS_RSA_WITH_AES_256_CBC_SHA Suite ID: 0x35 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_256_CBC_SHA 256 bits Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits

Analysis

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.

Deprecated protocols not supported

Excellent. This server doesn't support any of the deprecated protocol (TLS 1.1 and earlier).

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 settings 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.apple.com (2600:1408:c400:1886:0:0:0:1aca)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.3 TLS v1.2
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3 Server preference	Suite: TLS_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_AES_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_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_128_CCM_8_SHA256 Suite ID: 0x1305 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_CCM_8_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_AES_128_CCM_SHA256 Suite ID: 0x1304 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_CCM_SHA256 128 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC secp256r1 (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_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC secp256r1 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) 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 secp256r1 (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_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 secp256r1 (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_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 secp256r1 (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_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 secp256r1 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_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 secp256r1 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0x9d Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA384 TLS_RSA_WITH_AES_256_GCM_SHA384 256 bits Suite: TLS_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0x9c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_GCM_SHA256 128 bits Suite: TLS_RSA_WITH_AES_256_CBC_SHA256 Suite ID: 0x3d Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_256_CBC_SHA256 256 bits Suite: TLS_RSA_WITH_AES_128_CBC_SHA256 Suite ID: 0x3c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_CBC_SHA256 128 bits Suite: TLS_RSA_WITH_AES_256_CBC_SHA Suite ID: 0x35 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_256_CBC_SHA 256 bits Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits

Analysis

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.

Deprecated protocols not supported

Excellent. This server doesn't support any of the deprecated protocol (TLS 1.1 and earlier).

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 settings 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.apple.com

Leaf certificate

www.apple.com
Issuer: Apple Inc.
Not Before: 09 Jan 2024 11:52:35 UTC
Not After: 07 Jul 2024 12:02:35 UTC (expires in 1 month 29 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
View details

Names	www.apple.com.cn images.apple.com www.apple.com
Subject DN	CN=www.apple.com, O=Apple Inc., L=Cupertino, ST=California, C=US, SERIALNUMBER=C0806592, OID.1.3.6.1.4.1.311.60.2.1.2=California, OID.1.3.6.1.4.1.311.60.2.1.3=US, OID.2.5.4.15=Private Organization
Subject Key Identifier	e07c9542cf2d93742932cf095ad221ac755be792
Serial	1a52412bde1c028136bb389ae727e412
Not Before	09 Jan 2024 11:52:35 UTC
Not After	07 Jul 2024 12:02:35 UTC
Validity period	181 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth
Must Staple	No
Issuer
Issuer DN	CN=Apple Public EV Server RSA CA 2 - G1, O=Apple Inc., C=US
Certification Authority	Apple Inc.
Validation Type	Extended Validation (EV)
Authority Key Identifier	keyid:5055ab43a1afa9482b5ac1a2878904e47a0ecada
Parent Certificate	http://certs.apple.com/apevsrsa2g1.der
CRL	http://crl.apple.com/apevsrsa2g1.crl
OCSP	http://ocsp.apple.com/ocsp03-apevsrsa2g101
Certificate Transparency
Signed Certificate Timestamps	09 Jan 2024 12:02:36 UTC \| DigiCert Yeti2024 Log \| Qualified 09 Jan 2024 12:02:36 UTC \| Google 'Xenon2024' log \| Qualified 09 Jan 2024 12:02:36 UTC \| Cloudflare 'Nimbus2024' Log \| Qualified 09 Jan 2024 12:02:36 UTC \| Google 'Argon2024' log \| Qualified
Fingerprints
SHA1	cf7a9aa024cc6d07c7e12cfabe097b5dafbfbe64
SHA256	be08616db8014b96057755d2ca3335658d390d025e59dbe793058c7bd6b22ed1
SPKI SHA256	c5651d7b332c202434b217a88d8e239f4d4669aaeb4d2e14632422c9e071ac79

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

www.apple.com | be08616
Not After: 07 Jul 2024 12:02:35 UTC (expires in 1 month 29 days)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Names	www.apple.com.cn images.apple.com www.apple.com
Subject DN	CN=www.apple.com, O=Apple Inc., L=Cupertino, ST=California, C=US, SERIALNUMBER=C0806592, OID.1.3.6.1.4.1.311.60.2.1.2=California, OID.1.3.6.1.4.1.311.60.2.1.3=US, OID.2.5.4.15=Private Organization
Subject Key Identifier	e07c9542cf2d93742932cf095ad221ac755be792
Serial	1a52412bde1c028136bb389ae727e412
Not Before	09 Jan 2024 11:52:35 UTC
Not After	07 Jul 2024 12:02:35 UTC
Validity period	181 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth
Must Staple	No
Issuer
Issuer DN	CN=Apple Public EV Server RSA CA 2 - G1, O=Apple Inc., C=US
Certification Authority	Apple Inc.
Validation Type	Extended Validation (EV)
Authority Key Identifier	keyid:5055ab43a1afa9482b5ac1a2878904e47a0ecada
Parent Certificate	http://certs.apple.com/apevsrsa2g1.der
CRL	http://crl.apple.com/apevsrsa2g1.crl
OCSP	http://ocsp.apple.com/ocsp03-apevsrsa2g101
Certificate Transparency
Signed Certificate Timestamps	09 Jan 2024 12:02:36 UTC \| DigiCert Yeti2024 Log \| Qualified 09 Jan 2024 12:02:36 UTC \| Google 'Xenon2024' log \| Qualified 09 Jan 2024 12:02:36 UTC \| Cloudflare 'Nimbus2024' Log \| Qualified 09 Jan 2024 12:02:36 UTC \| Google 'Argon2024' log \| Qualified
Fingerprints
SHA1	cf7a9aa024cc6d07c7e12cfabe097b5dafbfbe64
SHA256	be08616db8014b96057755d2ca3335658d390d025e59dbe793058c7bd6b22ed1
SPKI SHA256	c5651d7b332c202434b217a88d8e239f4d4669aaeb4d2e14632422c9e071ac79

Intermediate certificate

Apple Public EV Server RSA CA 2 - G1 | d6ef3e0
Not After: 10 Apr 2030 23:59:59 UTC (expires in 5 years 11 months)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Subject DN	CN=Apple Public EV Server RSA CA 2 - G1, O=Apple Inc., C=US
Subject Key Identifier	5055ab43a1afa9482b5ac1a2878904e47a0ecada
Serial	7177911005d2267f68892f68f8b5058
Not Before	29 Apr 2020 12:54:50 UTC
Not After	10 Apr 2030 23:59:59 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	Entrust
Validation Type	Not Applicable
Authority Key Identifier	keyid:b13ec36903f8bf4701d498261a0802ef63642bc3
CRL	http://crl3.digicert.com/DigiCertHighAssuranceEVRootCA.crl
OCSP	http://ocsp.digicert.com
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	8ba88d2c0f20439fb7d00f3910159023cfe91dc8
SHA256	d6ef3e09ebe0d9370e51f5c09a532b3ac70d3ce822253f9fc84c28e9bfa550d5
SPKI SHA256	e1930104a956ca1a5db0aa8a9db5c492ea380a74b1c3a6fbb2f95c2882567c40

Root certificate

DigiCert High Assurance EV Root CA | 7431e5f
Not After: 10 Nov 2031 00:00:00 UTC (expires in 7 years 6 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	Entrust
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: apple.com

Leaf certificate

apple.com
Issuer: Apple Inc.
Not Before: 01 Apr 2024 22:10:27 UTC
Not After: 30 Jun 2024 22:20:27 UTC (expires in 1 month 22 days)
Key: EC 256 bits
Signature: SHA256withECDSA
View details

Names	apple.com
Subject DN	CN=apple.com, O=Apple Inc., L=Cupertino, ST=California, C=US, SERIALNUMBER=C0806592, OID.1.3.6.1.4.1.311.60.2.1.2=California, OID.1.3.6.1.4.1.311.60.2.1.3=US, OID.2.5.4.15=Private Organization
Subject Key Identifier	4406d96b76c1a12f5b592638f5ea7b34ae1a39e7
Serial	2fac29e0d50d29baeddb7de079873c32
Not Before	01 Apr 2024 22:10:27 UTC
Not After	30 Jun 2024 22:20:27 UTC
Validity period	91 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth
Must Staple	No
Issuer
Issuer DN	CN=Apple Public EV Server ECC CA 1 - G1, O=Apple Inc., C=US
Certification Authority	Apple Inc.
Validation Type	Extended Validation (EV)
Authority Key Identifier	keyid:e085487d13a6d310199f5ccb6b782492f8ae1bae
Parent Certificate	http://certs.apple.com/apevsecc1g1.der
CRL	http://crl.apple.com/apevsecc1g1.crl
OCSP	http://ocsp.apple.com/ocsp03-apevsecc1g101
Certificate Transparency
Signed Certificate Timestamps	01 Apr 2024 22:20:28 UTC \| Let's Encrypt 'Oak2024H1' log \| Qualified 01 Apr 2024 22:20:28 UTC \| Let's Encrypt 'Oak2024H2' log \| Qualified 01 Apr 2024 22:20:28 UTC \| Google 'Argon2024' log \| Qualified 01 Apr 2024 22:20:28 UTC \| Sectigo 'Sabre2024h1' \| Qualified
Fingerprints
SHA1	e2faf1486e01238a5450f9705f9d0dffc1811baa
SHA256	ac0773cd78aab8a81155b8045dda89be7eb3d88e83a5b17baba1a05e600314b8
SPKI SHA256	24968a3d1f1b213d239eb2765a3d424afb93636b598650238bc64166b00cc972

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.

Symantec subordinate CA excluded from early expiration

Although the leaf certificate ultimately chains to a Symantec root, it has been issued from an independently-operated subordinate CA that has been excluded from early expiration.

Certificate 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

apple.com | ac0773c
Not After: 30 Jun 2024 22:20:27 UTC (expires in 1 month 22 days)
Authentication: EC 256 bits (SHA256withECDSA)
View details

Names	apple.com
Subject DN	CN=apple.com, O=Apple Inc., L=Cupertino, ST=California, C=US, SERIALNUMBER=C0806592, OID.1.3.6.1.4.1.311.60.2.1.2=California, OID.1.3.6.1.4.1.311.60.2.1.3=US, OID.2.5.4.15=Private Organization
Subject Key Identifier	4406d96b76c1a12f5b592638f5ea7b34ae1a39e7
Serial	2fac29e0d50d29baeddb7de079873c32
Not Before	01 Apr 2024 22:10:27 UTC
Not After	30 Jun 2024 22:20:27 UTC
Validity period	91 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth
Must Staple	No
Issuer
Issuer DN	CN=Apple Public EV Server ECC CA 1 - G1, O=Apple Inc., C=US
Certification Authority	Apple Inc.
Validation Type	Extended Validation (EV)
Authority Key Identifier	keyid:e085487d13a6d310199f5ccb6b782492f8ae1bae
Parent Certificate	http://certs.apple.com/apevsecc1g1.der
CRL	http://crl.apple.com/apevsecc1g1.crl
OCSP	http://ocsp.apple.com/ocsp03-apevsecc1g101
Certificate Transparency
Signed Certificate Timestamps	01 Apr 2024 22:20:28 UTC \| Let's Encrypt 'Oak2024H1' log \| Qualified 01 Apr 2024 22:20:28 UTC \| Let's Encrypt 'Oak2024H2' log \| Qualified 01 Apr 2024 22:20:28 UTC \| Google 'Argon2024' log \| Qualified 01 Apr 2024 22:20:28 UTC \| Sectigo 'Sabre2024h1' \| Qualified
Fingerprints
SHA1	e2faf1486e01238a5450f9705f9d0dffc1811baa
SHA256	ac0773cd78aab8a81155b8045dda89be7eb3d88e83a5b17baba1a05e600314b8
SPKI SHA256	24968a3d1f1b213d239eb2765a3d424afb93636b598650238bc64166b00cc972

Intermediate certificate

Apple Public EV Server ECC CA 1 - G1 | 2585928
Not After: 10 Apr 2030 23:59:59 UTC (expires in 5 years 11 months)
Authentication: EC 256 bits (SHA384withECDSA)
View details

Subject DN	CN=Apple Public EV Server ECC CA 1 - G1, O=Apple Inc., C=US
Subject Key Identifier	e085487d13a6d310199f5ccb6b782492f8ae1bae
Serial	cabaad1cec4e97cc2665881d02138f7
Not Before	29 Apr 2020 12:34:52 UTC
Not After	10 Apr 2030 23:59:59 UTC
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	serverAuth, clientAuth
Issuer
Issuer DN	CN=DigiCert Global Root G3, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Not Applicable
Authority Key Identifier	keyid:b3db48a4f9a1c5d8ae3641cc1163696229bc4bc6
CRL	http://crl3.digicert.com/DigiCertGlobalRootG3.crl
OCSP	http://ocsp.digicert.com
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	222902acfb934c606d45bdc31c603daaf8b13e4f
SHA256	2585928d2c5bfd952e025bd12e27c6776224cf752ec362d3031cdd49351844d4
SPKI SHA256	2ebd9f63cf5ab1b13da2177b596f2d2c8d29be83cb5fe5adfcdee63feae2ddcd

Root certificate

DigiCert Global Root G3 | 31ad664
Not After: 15 Jan 2038 12:00:00 UTC (expires in 13 years 8 months)
Authentication: EC 384 bits (SHA384withECDSA)
View details

Subject DN	CN=DigiCert Global Root G3, OU=www.digicert.com, O=DigiCert Inc, C=US
Subject Key Identifier	b3db48a4f9a1c5d8ae3641cc1163696229bc4bc6
Serial	55556bcf25ea43535c3a40fd5ab4572
Not Before	01 Aug 2013 12:00:00 UTC
Not After	15 Jan 2038 12:00:00 UTC
Key Usage	digitalSignature, keyCertSign, cRLSign
Issuer
Issuer DN	CN=DigiCert Global Root G3, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Self-signed
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	7e04de896a3e666d00e687d33ffad93be83d349e
SHA256	31ad6648f8104138c738f39ea4320133393e3a18cc02296ef97c2ac9ef6731d0
SPKI SHA256	b94c198300cec5c057ad0727b70bbe91816992256439a7b32f4598119dda9c97

Analysis

Certificate chain is correct

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

Certificate: apple.com

Leaf certificate

apple.com
Issuer: Apple Inc.
Not Before: 01 Apr 2024 22:11:09 UTC
Not After: 30 Jun 2024 22:21:09 UTC (expires in 1 month 22 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
View details

Names	apple.com
Subject DN	CN=apple.com, O=Apple Inc., L=Cupertino, ST=California, C=US, SERIALNUMBER=C0806592, OID.1.3.6.1.4.1.311.60.2.1.2=California, OID.1.3.6.1.4.1.311.60.2.1.3=US, OID.2.5.4.15=Private Organization
Subject Key Identifier	74a82b1b6a6b446702ad33f2aed963c47cafc147
Serial	31a4531d2d8f5b237452db1eca0fcceb
Not Before	01 Apr 2024 22:11:09 UTC
Not After	30 Jun 2024 22:21:09 UTC
Validity period	91 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth
Must Staple	No
Issuer
Issuer DN	CN=Apple Public EV Server RSA CA 2 - G1, O=Apple Inc., C=US
Certification Authority	Apple Inc.
Validation Type	Extended Validation (EV)
Authority Key Identifier	keyid:5055ab43a1afa9482b5ac1a2878904e47a0ecada
Parent Certificate	http://certs.apple.com/apevsrsa2g1.der
CRL	http://crl.apple.com/apevsrsa2g1.crl
OCSP	http://ocsp.apple.com/ocsp03-apevsrsa2g101
Certificate Transparency
Signed Certificate Timestamps	01 Apr 2024 22:21:10 UTC \| Let's Encrypt 'Oak2024H1' log \| Qualified 01 Apr 2024 22:21:10 UTC \| Let's Encrypt 'Oak2024H2' log \| Qualified 01 Apr 2024 22:21:10 UTC \| Cloudflare 'Nimbus2024' Log \| Qualified 01 Apr 2024 22:21:10 UTC \| Google 'Argon2024' log \| Qualified
Fingerprints
SHA1	1641a2ca7958255dbcf7f819e619b3b8689c25fd
SHA256	c6bcb8c6e4b3ef0201f06d49b9d41063fc9a715c6fcab28e8ae2df4356a17800
SPKI SHA256	f21419256be08793830e63a61a8f06f9e178c82e8f279cf84cdef9e2deaa019f

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

apple.com | c6bcb8c
Not After: 30 Jun 2024 22:21:09 UTC (expires in 1 month 22 days)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Names	apple.com
Subject DN	CN=apple.com, O=Apple Inc., L=Cupertino, ST=California, C=US, SERIALNUMBER=C0806592, OID.1.3.6.1.4.1.311.60.2.1.2=California, OID.1.3.6.1.4.1.311.60.2.1.3=US, OID.2.5.4.15=Private Organization
Subject Key Identifier	74a82b1b6a6b446702ad33f2aed963c47cafc147
Serial	31a4531d2d8f5b237452db1eca0fcceb
Not Before	01 Apr 2024 22:11:09 UTC
Not After	30 Jun 2024 22:21:09 UTC
Validity period	91 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth
Must Staple	No
Issuer
Issuer DN	CN=Apple Public EV Server RSA CA 2 - G1, O=Apple Inc., C=US
Certification Authority	Apple Inc.
Validation Type	Extended Validation (EV)
Authority Key Identifier	keyid:5055ab43a1afa9482b5ac1a2878904e47a0ecada
Parent Certificate	http://certs.apple.com/apevsrsa2g1.der
CRL	http://crl.apple.com/apevsrsa2g1.crl
OCSP	http://ocsp.apple.com/ocsp03-apevsrsa2g101
Certificate Transparency
Signed Certificate Timestamps	01 Apr 2024 22:21:10 UTC \| Let's Encrypt 'Oak2024H1' log \| Qualified 01 Apr 2024 22:21:10 UTC \| Let's Encrypt 'Oak2024H2' log \| Qualified 01 Apr 2024 22:21:10 UTC \| Cloudflare 'Nimbus2024' Log \| Qualified 01 Apr 2024 22:21:10 UTC \| Google 'Argon2024' log \| Qualified
Fingerprints
SHA1	1641a2ca7958255dbcf7f819e619b3b8689c25fd
SHA256	c6bcb8c6e4b3ef0201f06d49b9d41063fc9a715c6fcab28e8ae2df4356a17800
SPKI SHA256	f21419256be08793830e63a61a8f06f9e178c82e8f279cf84cdef9e2deaa019f

Intermediate certificate

Apple Public EV Server RSA CA 2 - G1 | d6ef3e0
Not After: 10 Apr 2030 23:59:59 UTC (expires in 5 years 11 months)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Subject DN	CN=Apple Public EV Server RSA CA 2 - G1, O=Apple Inc., C=US
Subject Key Identifier	5055ab43a1afa9482b5ac1a2878904e47a0ecada
Serial	7177911005d2267f68892f68f8b5058
Not Before	29 Apr 2020 12:54:50 UTC
Not After	10 Apr 2030 23:59:59 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	Entrust
Validation Type	Not Applicable
Authority Key Identifier	keyid:b13ec36903f8bf4701d498261a0802ef63642bc3
CRL	http://crl3.digicert.com/DigiCertHighAssuranceEVRootCA.crl
OCSP	http://ocsp.digicert.com
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	8ba88d2c0f20439fb7d00f3910159023cfe91dc8
SHA256	d6ef3e09ebe0d9370e51f5c09a532b3ac70d3ce822253f9fc84c28e9bfa550d5
SPKI SHA256	e1930104a956ca1a5db0aa8a9db5c492ea380a74b1c3a6fbb2f95c2882567c40

Root certificate

DigiCert High Assurance EV Root CA | 7431e5f
Not After: 10 Nov 2031 00:00:00 UTC (expires in 7 years 6 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	Entrust
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, but there are warnings

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

HTTP Cookie: geo

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

Analysis

Cookie is not secure

This cookie, which has been sent over an encrypted channel, doesn't have the secure flag set. As a result, an active network attacker can easily recover it.

Mixed Content

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

Test passed

Everything seems to be well configured. Well done.

Embedded Resources

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

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

Status	Link
Encrypted	https://www.apple.com/...cripts/head.built.js

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

Status	Link
Encrypted	https://www.apple.com/...ets/globalheader.css
Encrypted	https://www.apple.com/...obalfooter.built.css
Encrypted	https://www.apple.com/...c-localnav.built.css
Encrypted	https://www.apple.com/wss/fonts
Encrypted	https://www.apple.com/...s/overview.built.css

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

Outbound Links

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

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

Status	Link
Encrypted	https://support.apple.com/

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

Policy covers subdomains

When subdomains are included, network attackers are unable to manufacture arbitrary subdomains to manipulate cookies and trick users.

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.

Analysis

No HSTS on apex hostname

Even though the main host uses HSTS, the protection is not as good as it could be because the apex hostname doesn't have HSTS deployed. Without robust HSTS, attackers can sometimes abuse cookies and make up plaintext subdomains to use for phishing.

Location: https://apple.com

Policy set on plaintext port

HSTS policies must not be transmitted over insecure channels.

Location: http://www.apple.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

default-src	'self' blob: data: .akamaized.net .apple.com .apple-mapkit.com .cdn-apple.com *.organicfruitapps.com
child-src	blob: embed.music.apple.com embed.podcasts.apple.com https://recyclingprogram.apple.com swdlp.apple.com www.apple.com www.instagram.com platform.twitter.com www.youtube-nocookie.com
img-src	This parameter shouldn't be used because it reenables insecure behavior that CSP disables by default.'unsafe-inline' blob: data: .apple.com .apple-mapkit.com .cdn-apple.com .mzstatic.com
script-src	This parameter shouldn't be used because it reenables insecure behavior that CSP disables by default.'unsafe-inline' This parameter shouldn't be used because it reenables insecure behavior that CSP disables by default.'unsafe-eval' blob: .apple.com .apple-mapkit.com www.instagram.com platform.twitter.com
style-src	This parameter shouldn't be used because it reenables insecure behavior that CSP disables by default.'unsafe-inline' *.apple.com

Analysis

Inline scripts are allowed

By default, CSP doesn't allow inline script execution, but this policy overrides that behavior by specifying 'unsafe-inline' in the 'script-src' directive. As a result, all XSS defenses provided by CSP are significantly weakened.

Inline styles are allowed

This policy allows inline styles. Although they are not as bad as inline scripts in terms of security, an injection bug in script area would allow the attacker to modify page appearance.

Dynamic code execution is allowed

By default, CSP doesn't allow dynamic script execution via eval and friends, but this policy overrides that behavior by specifyin 'unsafe-eval' in the 'script-src' directive. As a result, XSS defenses provided by CSP are significantly weakened.

Mixed content not blocked

This CSP policy doesn't use any of the directives designed to handle mixed content. Consider using the 'block-all-mixed-content' and 'upgrade-insecure-requests' directives as appropriate to ensure that no mixed content is allowed.

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: default-src 'self' blob: data: *.akamaized.net *.apple.com *.apple-mapkit.com *.cdn-apple.com *.organicfruitapps.com; child-src blob: embed.music.apple.com embed.podcasts.apple.com https://recyclingprogram.apple.com swdlp.apple.com www.apple.com www.instagram.com platform.twitter.com www.youtube-nocookie.com; img-src 'unsafe-inline' blob: data: *.apple.com *.apple-mapkit.com *.cdn-apple.com *.mzstatic.com; script-src 'unsafe-inline' 'unsafe-eval' blob: *.apple.com *.apple-mapkit.com www.instagram.com platform.twitter.com; style-src 'unsafe-inline' *.apple.com

Location: https://www.apple.com/

Subresource Integrity

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

Test passed

Everything seems to be well configured. Well done.

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

Status	Link
Local	/v/home/takeover/l/built/scripts/head.built.js

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

Status	Link
Local	/api-www/global-elements/global-header/v1/assets/globalheader.css
Local	/ac/globalfooter/8/en_US/styles/ac-globalfooter.built.css
Local	/ac/localnav/8/styles/ac-localnav.built.css
Local	/wss/fonts?families=SF+Pro,v3\|SF+Pro+Icons,v3
Local	/v/home/takeover/l/built/styles/overview.built.css

Analysis

No remote resources

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

Expect CT

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

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

Analysis

Deploy Expect-CT to enable reporting

An Expect-CT policy enables web sites to monitor for any problems related to their Expect-CT compliance, detecting potentially serious issues quickly. When issues arise, compliant browsers will submit reports to the specified reporting endpoints. Before CT became required for all public certificates the Expect-CT was also used to require CT, but that use case no longer applies.

Frame Options

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

Test passed

Everything seems to be well configured. Well done.

Analysis

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

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

Backing DNS Queries

DNSSEC

Useful DNSSEC Tools

Certification Authority Authorization

CAA Policy Information

Analysis

Email (SMTP)

Analysis

Email TLS (SMTP)

TLS Configuration: mx-in.g.apple.com (17.32.222.242) Cached

Analysis

TLS Configuration: mx-in-mdn.apple.com (17.32.222.242) Cached

Analysis

TLS Configuration: mx-in-rno.apple.com (17.179.253.242) Cached

Analysis

TLS Configuration: mx-in-hfd.apple.com (17.57.165.2) Cached

Analysis

TLS Configuration: mx-in-vib.apple.com (17.57.170.2) 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

SPF Policy Information Included policy

DMARC

DMARC Policy Information

Analysis

MTA Strict Transport Security

SMTP TLS Reporting

HTTP (80)

URL: http://apple.com/

Analysis

URL: http://www.apple.com/

Analysis

HTTP (443)

URL: https://apple.com/

URL: https://www.apple.com/

WWW TLS

TLS Configuration: apple.com (2620:149:af0:0:0:0:0:10)

Analysis

TLS Configuration: apple.com (17.253.144.10)

Analysis

TLS Configuration: www.apple.com (2600:1408:c400:1889:0:0:0:1aca)

Analysis

TLS Configuration: www.apple.com (23.212.144.237)

Analysis

TLS Configuration: www.apple.com (2600:1408:c400:1886:0:0:0:1aca)

Analysis

WWW Certificates

Certificate: www.apple.com

Analysis

Certificate Trust

Certificate Chain

Analysis

Certificate: apple.com

Analysis

Certificate Trust

Certificate Chain