Hardenize Report: godaddy.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.

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	29 Oct 2024 03:11 UTC
Registrar
Registrar	GoDaddy.com, LLC
Registrar IANA ID	146
Events
Registration	02 Mar 1999 05:00 UTC
Update	26 Oct 2023 20:31 UTC
Expiration	01 Nov 2032 11:59 UTC
Configuration
Statuses	clientDeleteProhibited clientRenewProhibited clientTransferProhibited clientUpdateProhibited serverDeleteProhibited serverTransferProhibited serverUpdateProhibited
Registrar Lock
Registry Lock
Nameservers	a1-245.akam.net a11-64.akam.net a20-65.akam.net a6-66.akam.net a8-67.akam.net a9-67.akam.net cns1.godaddy.com cns2.godaddy.com
Contacts
Registrar	GoDaddy.com, LLC Email: Phone: Fax:
Abuse	Email: abuse@godaddy.com Phone: 480-624-2505 Fax:

{
  "meta": {
    "timestamp": "2024-10-29T03:11:18.868452553Z",
    "id": "c172b9a2-7478-468b-b400-732b85b953c2",
    "type": "HZ_REGISTRABLE_DOMAIN",
    "schemaVersion": "2022-02-02",
    "producer": "whois-rdap-clients/2022-03-23",
    "sequenceNo": 0,
    "source": "NET",
    "status": "OK",
    "duration": "1.596s"
  },
  "name": "godaddy.com",
  "punyName": "godaddy.com",
  "source": "SOURCE_RDAP",
  "sourceLocation": "https://rdap.verisign.com/com/v1/domain/godaddy.com",
  "sourceRaw": "{\"objectClassName\":\"domain\",\"handle\":\"4013247_DOMAIN_COM-VRSN\",\"ldhName\":\"GODADDY.COM\",\"links\":[{\"value\":\"https:\\/\\/rdap.verisign.com\\/com\\/v1\\/domain\\/GODADDY.COM\",\"rel\":\"self\",\"href\":\"https:\\/\\/rdap.verisign.com\\/com\\/v1\\/domain\\/GODADDY.COM\",\"type\":\"application\\/rdap+json\"},{\"value\":\"https:\\/\\/rdap.godaddy.com\\/v1\\/domain\\/GODADDY.COM\",\"rel\":\"related\",\"href\":\"https:\\/\\/rdap.godaddy.com\\/v1\\/domain\\/GODADDY.COM\",\"type\":\"application\\/rdap+json\"}],\"status\":[\"client delete prohibited\",\"client renew prohibited\",\"client transfer prohibited\",\"client update prohibited\",\"server delete prohibited\",\"server transfer prohibited\",\"server update prohibited\"],\"entities\":[{\"objectClassName\":\"entity\",\"handle\":\"146\",\"roles\":[\"registrar\"],\"publicIds\":[{\"type\":\"IANA Registrar ID\",\"identifier\":\"146\"}],\"vcardArray\":[\"vcard\",[[\"version\",{},\"text\",\"4.0\"],[\"fn\",{},\"text\",\"GoDaddy.com, LLC\"]]],\"entities\":[{\"objectClassName\":\"entity\",\"roles\":[\"abuse\"],\"vcardArray\":[\"vcard\",[[\"version\",{},\"text\",\"4.0\"],[\"fn\",{},\"text\",\"\"],[\"tel\",{\"type\":\"voice\"},\"uri\",\"tel:480-624-2505\"],[\"email\",{},\"text\",\"abuse@godaddy.com\"]]]}]}],\"events\":[{\"eventAction\":\"registration\",\"eventDate\":\"1999-03-02T05:00:00Z\"},{\"eventAction\":\"expiration\",\"eventDate\":\"2032-11-01T11:59:59Z\"},{\"eventAction\":\"last changed\",\"eventDate\":\"2023-10-26T20:31:51Z\"},{\"eventAction\":\"last update of RDAP database\",\"eventDate\":\"2024-10-29T03:11:09Z\"}],\"secureDNS\":{\"delegationSigned\":false},\"nameservers\":[{\"objectClassName\":\"nameserver\",\"ldhName\":\"A1-245.AKAM.NET\"},{\"objectClassName\":\"nameserver\",\"ldhName\":\"A11-64.AKAM.NET\"},{\"objectClassName\":\"nameserver\",\"ldhName\":\"A20-65.AKAM.NET\"},{\"objectClassName\":\"nameserver\",\"ldhName\":\"A6-66.AKAM.NET\"},{\"objectClassName\":\"nameserver\",\"ldhName\":\"A8-67.AKAM.NET\"},{\"objectClassName\":\"nameserver\",\"ldhName\":\"A9-67.AKAM.NET\"},{\"objectClassName\":\"nameserver\",\"ldhName\":\"CNS1.GODADDY.COM\"},{\"objectClassName\":\"nameserver\",\"ldhName\":\"CNS2.GODADDY.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": "1999-03-02T05:00:00Z",
  "expireTime": "2032-11-01T11:59:59Z",
  "updateTime": "2023-10-26T20:31:51Z",
  "autoRenewal": false,
  "privacy": false,
  "registrarLock": true,
  "registryLock": true,
  "registrarName": "GoDaddy.com, LLC",
  "registrarIanaId": "146",
  "nameservers": [{
    "name": "a1-245.akam.net",
    "punyName": "",
    "addresses": []
  }, {
    "name": "a11-64.akam.net",
    "punyName": "",
    "addresses": []
  }, {
    "name": "a20-65.akam.net",
    "punyName": "",
    "addresses": []
  }, {
    "name": "a6-66.akam.net",
    "punyName": "",
    "addresses": []
  }, {
    "name": "a8-67.akam.net",
    "punyName": "",
    "addresses": []
  }, {
    "name": "a9-67.akam.net",
    "punyName": "",
    "addresses": []
  }, {
    "name": "cns1.godaddy.com",
    "punyName": "",
    "addresses": []
  }, {
    "name": "cns2.godaddy.com",
    "punyName": "",
    "addresses": []
  }],
  "statuses": ["clientDeleteProhibited", "clientRenewProhibited", "clientTransferProhibited", "clientUpdateProhibited", "serverDeleteProhibited", "serverTransferProhibited", "serverUpdateProhibited"],
  "sourceStatuses": ["client delete prohibited", "client renew prohibited", "client transfer prohibited", "client update prohibited", "server delete prohibited", "server transfer prohibited", "server update prohibited"],
  "contacts": [{
    "type": "CONTACT_REGISTRAR",
    "id": "",
    "firstName": "",
    "lastName": "",
    "organization": "GoDaddy.com, LLC",
    "street1": "",
    "street2": "",
    "city": "",
    "state": "",
    "postcode": "",
    "country": "",
    "countryCode": "",
    "email": "",
    "phone": "",
    "fax": ""
  }, {
    "type": "CONTACT_ABUSE",
    "id": "",
    "firstName": "",
    "lastName": "",
    "organization": "",
    "street1": "",
    "street2": "",
    "city": "",
    "state": "",
    "postcode": "",
    "country": "",
    "countryCode": "",
    "email": "abuse@godaddy.com",
    "phone": "480-624-2505",
    "fax": ""
  }]
}

{
  "objectClassName": "domain",
  "handle": "4013247_DOMAIN_COM-VRSN",
  "ldhName": "GODADDY.COM",
  "links": [
    {
      "value": "https://rdap.verisign.com/com/v1/domain/GODADDY.COM",
      "rel": "self",
      "href": "https://rdap.verisign.com/com/v1/domain/GODADDY.COM",
      "type": "application/rdap+json"
    },
    {
      "value": "https://rdap.godaddy.com/v1/domain/GODADDY.COM",
      "rel": "related",
      "href": "https://rdap.godaddy.com/v1/domain/GODADDY.COM",
      "type": "application/rdap+json"
    }
  ],
  "status": [
    "client delete prohibited",
    "client renew prohibited",
    "client transfer prohibited",
    "client update prohibited",
    "server delete prohibited",
    "server transfer prohibited",
    "server update prohibited"
  ],
  "entities": [
    {
      "objectClassName": "entity",
      "handle": "146",
      "roles": [
        "registrar"
      ],
      "publicIds": [
        {
          "type": "IANA Registrar ID",
          "identifier": "146"
        }
      ],
      "vcardArray": [
        "vcard",
        [
          [
            "version",
            {},
            "text",
            "4.0"
          ],
          [
            "fn",
            {},
            "text",
            "GoDaddy.com, LLC"
          ]
        ]
      ],
      "entities": [
        {
          "objectClassName": "entity",
          "roles": [
            "abuse"
          ],
          "vcardArray": [
            "vcard",
            [
              [
                "version",
                {},
                "text",
                "4.0"
              ],
              [
                "fn",
                {},
                "text",
                ""
              ],
              [
                "tel",
                {
                  "type": "voice"
                },
                "uri",
                "tel:480-624-2505"
              ],
              [
                "email",
                {},
                "text",
                "abuse@godaddy.com"
              ]
            ]
          ]
        }
      ]
    }
  ],
  "events": [
    {
      "eventAction": "registration",
      "eventDate": "1999-03-02T05:00:00Z"
    },
    {
      "eventAction": "expiration",
      "eventDate": "2032-11-01T11:59:59Z"
    },
    {
      "eventAction": "last changed",
      "eventDate": "2023-10-26T20:31:51Z"
    },
    {
      "eventAction": "last update of RDAP database",
      "eventDate": "2024-10-29T03:11:09Z"
    }
  ],
  "secureDNS": {
    "delegationSigned": false
  },
  "nameservers": [
    {
      "objectClassName": "nameserver",
      "ldhName": "A1-245.AKAM.NET"
    },
    {
      "objectClassName": "nameserver",
      "ldhName": "A11-64.AKAM.NET"
    },
    {
      "objectClassName": "nameserver",
      "ldhName": "A20-65.AKAM.NET"
    },
    {
      "objectClassName": "nameserver",
      "ldhName": "A6-66.AKAM.NET"
    },
    {
      "objectClassName": "nameserver",
      "ldhName": "A8-67.AKAM.NET"
    },
    {
      "objectClassName": "nameserver",
      "ldhName": "A9-67.AKAM.NET"
    },
    {
      "objectClassName": "nameserver",
      "ldhName": "CNS1.GODADDY.COM"
    },
    {
      "objectClassName": "nameserver",
      "ldhName": "CNS2.GODADDY.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	Domains By Proxy, LLC
Lookup Time	29 Oct 2024 03:11 UTC
Registrar
Registrar	GoDaddy.com, LLC
Registrar IANA ID	146
Events
Registration	02 Mar 1999 00:00 UTC
Update	26 Oct 2023 13:05 UTC
Expiration	01 Nov 2032 06:59 UTC
Configuration
Statuses	clientRenewProhibited clientUpdateProhibited clientDeleteProhibited clientTransferProhibited
Registrar Lock
Registry Lock	-
Nameservers	cns1.godaddy.com cns2.godaddy.com a11-64.akam.net a1-245.akam.net a20-65.akam.net a6-66.akam.net a8-67.akam.net a9-67.akam.net
Contacts
Registrar	GoDaddy.com, LLC GoDaddy.com, LLC Email: Phone: Fax:
Abuse	Email: abuse@godaddy.com Phone: +1.4806242505 Fax:
Registrant	Registration Private Domains By Proxy, LLC DomainsByProxy.com 85281 US Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=GODADDY.COM Phone: +1.4806242599 Fax:
Technical	Registration Private Domains By Proxy, LLC DomainsByProxy.com 85281 US Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=GODADDY.COM Phone: +1.4806242599 Fax:

{
  "meta": {
    "timestamp": "2024-10-29T03:11:20.117961362Z",
    "id": "a8d068b7-f162-4a28-9258-ba440aec859e",
    "type": "HZ_REGISTRABLE_DOMAIN",
    "schemaVersion": "2022-02-02",
    "producer": "whois-rdap-clients/2022-03-23",
    "sequenceNo": 0,
    "source": "NET",
    "status": "OK",
    "duration": "1.249s"
  },
  "name": "godaddy.com",
  "punyName": "godaddy.com",
  "source": "SOURCE_WHOIS",
  "sourceLocation": "whois.godaddy.com:43",
  "sourceRaw": "Domain Name: GODADDY.COM\r\nRegistry Domain ID: 4013247_DOMAIN_COM-VRSN\r\nRegistrar WHOIS Server: whois.godaddy.com\r\nRegistrar URL: https://www.godaddy.com\r\nUpdated Date: 2023-10-26T13:05:54Z\r\nCreation Date: 1999-03-02T00:00:00Z\r\nRegistrar Registration Expiration Date: 2032-11-01T06:59:59Z\r\nRegistrar: GoDaddy.com, LLC\r\nRegistrar IANA ID: 146\r\nRegistrar Abuse Contact Email: abuse@godaddy.com\r\nRegistrar Abuse Contact Phone: +1.4806242505\r\nDomain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited\r\nDomain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited\r\nDomain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited\r\nDomain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited\r\nRegistry Registrant ID: Not Available From Registry\r\nRegistrant Name: Registration Private\r\nRegistrant Organization: Domains By Proxy, LLC\r\nRegistrant Street: DomainsByProxy.com\r\nRegistrant Street: 100 S. Mill Ave, Suite 1600\r\nRegistrant City: Tempe\r\nRegistrant State/Province: Arizona\r\nRegistrant Postal Code: 85281\r\nRegistrant Country: US\r\nRegistrant Phone: +1.4806242599\r\nRegistrant Phone Ext:\r\nRegistrant Fax: \r\nRegistrant Fax Ext:\r\nRegistrant Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain\u003dGODADDY.COM\r\nRegistry Tech ID: Not Available From Registry\r\nTech Name: Registration Private\r\nTech Organization: Domains By Proxy, LLC\r\nTech Street: DomainsByProxy.com\r\nTech Street: 100 S. Mill Ave, Suite 1600\r\nTech City: Tempe\r\nTech State/Province: Arizona\r\nTech Postal Code: 85281\r\nTech Country: US\r\nTech Phone: +1.4806242599\r\nTech Phone Ext:\r\nTech Fax: \r\nTech Fax Ext:\r\nTech Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain\u003dGODADDY.COM\r\nName Server: CNS1.GODADDY.COM\r\nName Server: CNS2.GODADDY.COM\r\nName Server: A11-64.AKAM.NET\r\nName Server: A1-245.AKAM.NET\r\nName Server: A20-65.AKAM.NET\r\nName Server: A6-66.AKAM.NET\r\nName Server: A8-67.AKAM.NET\r\nName Server: A9-67.AKAM.NET\r\nDNSSEC: unsigned\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-10-29T03:11:19Z \u003c\u003c\u003c\r\nFor more information on Whois status codes, please visit https://icann.org/epp\r\n\r\nTERMS OF USE: The data contained in this registrar\u0027s Whois database, while believed by the\r\nregistrar to be reliable, is provided \"as is\" with no guarantee or warranties regarding its\r\naccuracy. This information is provided for the sole purpose of assisting you in obtaining\r\ninformation about domain name registration records. Any use of this data for any other purpose\r\nis expressly forbidden without the prior written permission of this registrar. By submitting\r\nan inquiry, you agree to these terms and limitations of warranty. In particular, you agree not\r\nto use this data to allow, enable, or otherwise support the dissemination or collection of this\r\ndata, in part or in its entirety, for any purpose, such as transmission by e-mail, telephone,\r\npostal mail, facsimile or other means of mass unsolicited, commercial advertising or solicitations\r\nof any kind, including spam. You further agree not to use this data to enable high volume, automated\r\nor robotic electronic processes designed to collect or compile this data for any purpose, including\r\nmining this data for your own personal or commercial purposes. Failure to comply with these terms\r\nmay result in termination of access to the Whois database. These terms may be subject to modification\r\nat any time without notice.\r\n\r\n",
  "tld": "com",
  "suffix": "com",
  "createTime": "1999-03-02T00:00:00Z",
  "expireTime": "2032-11-01T06:59:59Z",
  "updateTime": "2023-10-26T13:05:54Z",
  "autoRenewal": false,
  "privacy": false,
  "registrarLock": true,
  "registrarName": "GoDaddy.com, LLC",
  "registrarIanaId": "146",
  "registrarUrl": "https://www.godaddy.com",
  "registrant": "Domains By Proxy, LLC",
  "nameservers": [{
    "name": "cns1.godaddy.com",
    "punyName": "",
    "addresses": []
  }, {
    "name": "cns2.godaddy.com",
    "punyName": "",
    "addresses": []
  }, {
    "name": "a11-64.akam.net",
    "punyName": "",
    "addresses": []
  }, {
    "name": "a1-245.akam.net",
    "punyName": "",
    "addresses": []
  }, {
    "name": "a20-65.akam.net",
    "punyName": "",
    "addresses": []
  }, {
    "name": "a6-66.akam.net",
    "punyName": "",
    "addresses": []
  }, {
    "name": "a8-67.akam.net",
    "punyName": "",
    "addresses": []
  }, {
    "name": "a9-67.akam.net",
    "punyName": "",
    "addresses": []
  }],
  "statuses": ["clientRenewProhibited", "clientUpdateProhibited", "clientDeleteProhibited", "clientTransferProhibited"],
  "sourceStatuses": ["clientTransferProhibited https://icann.org/epp#clientTransferProhibited", "clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited", "clientRenewProhibited https://icann.org/epp#clientRenewProhibited", "clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited"],
  "contacts": [{
    "type": "CONTACT_REGISTRAR",
    "id": "",
    "firstName": "GoDaddy.com, LLC",
    "lastName": "",
    "organization": "GoDaddy.com, LLC",
    "street1": "",
    "street2": "",
    "city": "",
    "state": "",
    "postcode": "",
    "country": "",
    "countryCode": "",
    "email": "",
    "phone": "",
    "fax": ""
  }, {
    "type": "CONTACT_ABUSE",
    "id": "",
    "firstName": "",
    "lastName": "",
    "organization": "",
    "street1": "",
    "street2": "",
    "city": "",
    "state": "",
    "postcode": "",
    "country": "",
    "countryCode": "",
    "email": "abuse@godaddy.com",
    "phone": "+1.4806242505",
    "fax": ""
  }, {
    "type": "CONTACT_REGISTRANT",
    "id": "",
    "firstName": "Registration Private",
    "lastName": "",
    "organization": "Domains By Proxy, LLC",
    "street1": "DomainsByProxy.com",
    "street2": "",
    "city": "Tempe",
    "state": "Arizona",
    "postcode": "85281",
    "country": "US",
    "countryCode": "",
    "email": "Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain\u003dGODADDY.COM",
    "phone": "+1.4806242599",
    "fax": ""
  }, {
    "type": "CONTACT_TECHNICAL",
    "id": "",
    "firstName": "Registration Private",
    "lastName": "",
    "organization": "Domains By Proxy, LLC",
    "street1": "DomainsByProxy.com",
    "street2": "",
    "city": "Tempe",
    "state": "Arizona",
    "postcode": "85281",
    "country": "US",
    "countryCode": "",
    "email": "Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain\u003dGODADDY.COM",
    "phone": "+1.4806242599",
    "fax": ""
  }]
}

Domain Name: GODADDY.COM
Registry Domain ID: 4013247_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: https://www.godaddy.com
Updated Date: 2023-10-26T13:05:54Z
Creation Date: 1999-03-02T00:00:00Z
Registrar Registration Expiration Date: 2032-11-01T06:59:59Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: abuse@godaddy.com
Registrar Abuse Contact Phone: +1.4806242505
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Registry Registrant ID: Not Available From Registry
Registrant Name: Registration Private
Registrant Organization: Domains By Proxy, LLC
Registrant Street: DomainsByProxy.com
Registrant Street: 100 S. Mill Ave, Suite 1600
Registrant City: Tempe
Registrant State/Province: Arizona
Registrant Postal Code: 85281
Registrant Country: US
Registrant Phone: +1.4806242599
Registrant Phone Ext:
Registrant Fax: 
Registrant Fax Ext:
Registrant Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=GODADDY.COM
Registry Tech ID: Not Available From Registry
Tech Name: Registration Private
Tech Organization: Domains By Proxy, LLC
Tech Street: DomainsByProxy.com
Tech Street: 100 S. Mill Ave, Suite 1600
Tech City: Tempe
Tech State/Province: Arizona
Tech Postal Code: 85281
Tech Country: US
Tech Phone: +1.4806242599
Tech Phone Ext:
Tech Fax: 
Tech Fax Ext:
Tech Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=GODADDY.COM
Name Server: CNS1.GODADDY.COM
Name Server: CNS2.GODADDY.COM
Name Server: A11-64.AKAM.NET
Name Server: A1-245.AKAM.NET
Name Server: A20-65.AKAM.NET
Name Server: A6-66.AKAM.NET
Name Server: A8-67.AKAM.NET
Name Server: A9-67.AKAM.NET
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2024-10-29T03:11:19Z <<<
For more information on Whois status codes, please visit https://icann.org/epp

TERMS OF USE: The data contained in this registrar's Whois database, while believed by the
registrar to be reliable, is provided "as is" with no guarantee or warranties regarding its
accuracy. This information is provided for the sole purpose of assisting you in obtaining
information about domain name registration records. Any use of this data for any other purpose
is expressly forbidden without the prior written permission of this registrar. By submitting
an inquiry, you agree to these terms and limitations of warranty. In particular, you agree not
to use this data to allow, enable, or otherwise support the dissemination or collection of this
data, in part or in its entirety, for any purpose, such as transmission by e-mail, telephone,
postal mail, facsimile or other means of mass unsolicited, commercial advertising or solicitations
of any kind, including spam. You further agree not to use this data to enable high volume, automated
or robotic electronic processes designed to collect or compile this data for any purpose, including
mining this data for your own personal or commercial purposes. Failure to comply with these terms
may result in termination of access to the Whois database. These terms may be subject to modification
at any time without notice.

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
a1-245.akam.net. 193.108.91.245 2600:1401:2::f5				REFERRAL NS
a11-64.akam.net. 84.53.139.64 2600:1480:1::40				REFERRAL NS
a20-65.akam.net. 95.100.175.65 2a02:26f0:67::41				REFERRAL NS
a6-66.akam.net. 23.211.133.66 2600:1401:1::42				REFERRAL NS
a8-67.akam.net. 2.16.40.67 2600:1403:a::43				REFERRAL NS
a9-67.akam.net. 184.85.248.67 2a02:26f0:117::43				REFERRAL NS
cns1.godaddy.com. PRIMARY 97.74.96.100 2603:5:2100::64				SOA REFERRAL NS
cns2.godaddy.com. 173.201.64.100 2603:5:2200::64				REFERRAL NS

Nameserver Addresses

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

Nameserver	Sources	Payload Size
173.201.64.100 cns2.godaddy.com. PTR: cns2.godaddy.com.	NAME, GLUE	987
184.85.248.67 a9-67.akam.net. PTR: ns5-67.akam.net. PTR: a9-67.akam.net.	NAME	4096
193.108.91.245 a1-245.akam.net. PTR: a1-245.akam.net. PTR: ns1-245.akam.net.	NAME	4096
2.16.40.67 a8-67.akam.net. PTR: a8-67.akam.net.	NAME	4096
23.211.133.66 a6-66.akam.net. PTR: a6-66.akam.net.	NAME	4096
84.53.139.64 a11-64.akam.net. PTR: ns4-64.akam.net. PTR: a11-64.akam.net.	NAME	4096
95.100.175.65 a20-65.akam.net. PTR: a20-65.akam.net.	NAME	4096
97.74.96.100 PRIMARY cns1.godaddy.com. PTR: cns1.godaddy.com.	NAME, GLUE	987
2600:1401:1::42 a6-66.akam.net. PTR: a6-66.akam.net.	NAME	4096
2600:1401:2::f5 a1-245.akam.net. PTR: ns1-245.akam.net. PTR: a1-245.akam.net.	NAME	4096
2600:1403:a::43 a8-67.akam.net. PTR: a8-67.akam.net.	NAME	4096
2600:1480:1::40 a11-64.akam.net. PTR: ns4-64.akam.net. PTR: a11-64.akam.net.	NAME	4096
2603:5:2100::64 PRIMARY cns1.godaddy.com. PTR: cns1.godaddy.com.	NAME, GLUE	987
2603:5:2200::64 cns2.godaddy.com. PTR: cns2.godaddy.com.	NAME, GLUE	987
2a02:26f0:117::43 a9-67.akam.net. PTR: ns5-67.akam.net. PTR: a9-67.akam.net.	NAME	4096
2a02:26f0:67::41 a20-65.akam.net. PTR: a20-65.akam.net.	NAME	4096

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	cns1.godaddy.com.
Email address of the persons responsible for this zone. Also known as RNAME.Admin email	dns.jomax.net.
Zone serial or version number.Serial number	2024102822
The length of time secondary nameservers should wait before querying the primary for changes.Refresh interval	300 seconds (about 5 minutes)
The length of time secondary nameservers should wait before querying an unresponsive primary again.Retry interval	600 seconds (about 10 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	1,209,600 seconds (about 14 days)
TTL for purposes of negative response caching. Negative cache TTL	3,600 seconds (about 1 hour)
Time To Live (TTL) indicates for how long a record remains valid. SOA record TTL	3,600 seconds (about 1 hour)

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
godaddy.com.	300	A	208.109.192.70
www.godaddy.com.	300	CNAME	wildcard-ipv6.godaddy.com.edgekey.net.
wildcard-ipv6.godaddy.com.edgekey.net.	21600	CNAME	e6001.dscx.akamaiedge.net.
e6001.dscx.akamaiedge.net.	20	A	23.13.154.6
e6001.dscx.akamaiedge.net.	20	AAAA	2600:1408:c400:1881:0:0:0:1771
e6001.dscx.akamaiedge.net.	20	AAAA	2600:1408:c400:1887:0:0:0:1771
godaddy.com.	3600	MX	0 godaddy-com.mail.protection.outlook.com.
godaddy.com.	3600	NS	a6-66.akam.net.
godaddy.com.	3600	NS	cns2.godaddy.com.
godaddy.com.	3600	NS	a20-65.akam.net.
godaddy.com.	3600	NS	cns1.godaddy.com.
godaddy.com.	3600	NS	a1-245.akam.net.
godaddy.com.	3600	NS	a8-67.akam.net.
godaddy.com.	3600	NS	a9-67.akam.net.
godaddy.com.	3600	NS	a11-64.akam.net.
godaddy.com.	3600	SOA	cns1.godaddy.com. dns.jomax.net. 2024102822 300 600 1209600 3600
_sip._tls.godaddy.com.	3600	SRV	0 0 443 access.godaddy.com.
_sipfederationtls._tcp.godaddy.com.	3600	SRV	0 0 5061 access.godaddy.com.
_xmpp-server._tcp.godaddy.com.	60	SRV	0 0 5269 nxpfs.ucfederationcloud.com.
godaddy.com.	60	TXT	"v=spf1 include:spf-0.godaddy.com -all"
godaddy.com.	60	TXT	"RBH9V8U0D0K9PIA701RL7MCUFR"
godaddy.com.	60	TXT	"docusign=814dfd45-515d-4f50-90c2-0329708784a1"
godaddy.com.	60	TXT	"74kgo19jj7lrshufc9voqhitr1"
godaddy.com.	60	TXT	"mgverify=d0f1838e5c6e0bb6c7a00c895e3849b23839687e87015188ac0e4f767be6c173"
godaddy.com.	60	TXT	"7oZZbMavd5aj2djFeYFY58d1EAodffVMC9RJbSpi9zw4i8R9dVR+LZ4Xcdy4QNMH8t4G/bHO/yPVRxW9Q01lNQ=="
godaddy.com.	60	TXT	"google-site-verification=0UJ0HlvzwhMwV0bS0FNTyUXXWdfXw94mk4PaLgDpr24"
godaddy.com.	60	TXT	"mailru-verification: 51155022e43530db"
godaddy.com.	60	TXT	"atlassian-domain-verification=0FFz3ZaXmdxD7yHY5Q/nI2dnLHDM5Zi0tdvyuYN1JFWq3UIZMf6FaDJgsku9N2m3"
godaddy.com.	60	TXT	"41g3tbd5l406i30iv0f6uqqqlt"
godaddy.com.	60	TXT	"UCAKWQI9OUVXRQA63I7IBCHLELCI8YBIT07VXA4R"
godaddy.com.	60	TXT	"openai-domain-verification=dv-T83w1LIPbiVRivc4A3hY5B0R"
godaddy.com.	60	TXT	"apple-domain-verification=gQKC3eLuUdntRagJ"
godaddy.com.	60	TXT	"mgverify=6087be40f70e4c3ee3721081bb9a9a4af6edacf568053026e98e9ecceacf632e"
godaddy.com.	60	TXT	"dropbox-domain-verification=xl2s10u0jrq0"
godaddy.com.	60	TXT	"IPROTA_D17829-XXX.TXT"
godaddy.com.	60	TXT	"atlassian-sending-domain-verification=504ab315-6307-4433-b116-12ebd3dfb645"
godaddy.com.	60	TXT	"MS=ms83569812"
godaddy.com.	60	TXT	"gf1bnvgsl5bmekl6e1mke3c46c"
godaddy.com.	60	TXT	"google-site-verification=HUFIfAuQcl4c0V8lc7IZhit2UEFKQQVA838L7YIoCAY"
godaddy.com.	60	TXT	"google-site-verification=t7JT1iH2iscenNr74R-kgXPljL_ru6OPiT9RE8zDk04"
godaddy.com.	60	TXT	"adobe-idp-site-verification=2a5d58f1-1f72-48f5-9dee-65553c77beea"
godaddy.com.	60	TXT	"lsugtvmirlfdu755r3uuavkrno"
_dmarc.godaddy.com.	300	TXT	"v=DMARC1; p=reject; pct=100; rua=mailto:report@dmarc.em.secureserver.net, mailto:dmarc_agg@dmarc.250ok.net; ruf=mailto:godaddy-dmarc@datafeeds.phishlabs.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.

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

Analysis

There is no CAA policy on this domain

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

Email (SMTP)

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

Test passed

Everything seems to be well configured. Well done.

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

Server	Preference	Operational	STARTTLS	TLS	PKI	DNSSEC	DANE
godaddy-com.mail.protection.outlook.com 52.101.194.19 PTR: mail-ch5pr02cu00303.inbound.protection.outlook.com	0
godaddy-com.mail.protection.outlook.com 52.101.41.0 PTR: mail-byapr05cu00400.inbound.protection.outlook.com	0
godaddy-com.mail.protection.outlook.com 52.101.10.6 PTR: mail-bn1pr21cu00106.inbound.protection.outlook.com	0
godaddy-com.mail.protection.outlook.com 52.101.11.3 PTR: mail-sn1pr0501cu00103.inbound.protection.outlook.com	0

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: 28 Oct 2024 03:24 UTC

Earliest cache timestamp: 23 Oct 2024 03:06 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: godaddy-com.mail.protection.outlook.com (52.101.194.19) Cached

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.2
Shows cipher suite configuration for this protocol version.TLS v1.2	Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 384 bits)
These results have been retrieved from our cache. This row indicates when was that the original test ran.Retrieved from cache	26 Oct 2024 11:06 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: godaddy-com.mail.protection.outlook.com (52.101.41.0) Cached

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.2
Shows cipher suite configuration for this protocol version.TLS v1.2	Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 384 bits)
These results have been retrieved from our cache. This row indicates when was that the original test ran.Retrieved from cache	23 Oct 2024 03:06 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: godaddy-com.mail.protection.outlook.com (52.101.10.6) Cached

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.2
Shows cipher suite configuration for this protocol version.TLS v1.2	Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 384 bits)

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: godaddy-com.mail.protection.outlook.com (52.101.11.3) Cached

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.2
Shows cipher suite configuration for this protocol version.TLS v1.2	Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 384 bits)
These results have been retrieved from our cache. This row indicates when was that the original test ran.Retrieved from cache	28 Oct 2024 03:24 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

mail.protection.outlook.com
Issuer: DigiCert
Not Before: 18 Sep 2024 00:00:00 UTC
Not After: 17 Sep 2025 23:59:59 UTC (expires in 10 months 19 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
View details

Names	mail.protection.outlook.com .mail.eo.outlook.com .mail.protection.outlook.com mail.messaging.microsoft.com outlook.com .olc.protection.outlook.com .pamx1.hotmail.com .mail.protection.outlook.de .mx.microsoft .k-v1.mx.microsoft .n-v1.mx.microsoft .q-v1.mx.microsoft .y-v1.mx.microsoft .d-v1.mx.microsoft .e-v1.mx.microsoft .a-v1.mx.microsoft .r-v1.mx.microsoft .w-v1.mx.microsoft .p-v1.mx.microsoft .x-v1.mx.microsoft .j-v1.mx.microsoft .s-v1.mx.microsoft .c-v1.mx.microsoft .b-v1.mx.microsoft .f-v1.mx.microsoft .i-v1.mx.microsoft .t-v1.mx.microsoft .m-v1.mx.microsoft .o-v1.mx.microsoft .g-v1.mx.microsoft .v-v1.mx.microsoft .h-v1.mx.microsoft .l-v1.mx.microsoft *.u-v1.mx.microsoft
Subject DN	CN=mail.protection.outlook.com, O=Microsoft Corporation, L=Redmond, ST=Washington, C=US
Subject Key Identifier	80f6a64b6e022eb58e77c8c9466e2dc52f1eac61
Serial	4cf0b5a9d67a87e3397aca32337f538
Not Before	18 Sep 2024 00:00:00 UTC
Not After	17 Sep 2025 23:59:59 UTC
Validity period	365 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=DigiCert Cloud Services CA-1, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:dd51d0a23173a973ae8fb4017e5d8c57cb9ff0f7
Parent Certificate	http://cacerts.digicert.com/DigiCertCloudServicesCA-1.crt
CRL	http://crl3.digicert.com/DigiCertCloudServicesCA-1-g1.crl http://crl4.digicert.com/DigiCertCloudServicesCA-1-g1.crl
OCSP	http://ocspx.digicert.com
Certificate Transparency
Signed Certificate Timestamps	18 Sep 2024 12:46:04 UTC \| Google 'Argon2025h2' log \| Qualified 18 Sep 2024 12:46:04 UTC \| DigiCert Nessie2025 Log \| Qualified 18 Sep 2024 12:46:04 UTC \| Cloudflare 'Nimbus2025' \| Qualified
Fingerprints
SHA1	b19c121e37cd29d820d740bf19a6e464f3d29250
SHA256	c6d2c973df529c2164fef6b56d095174d13bb60e2c6651f1d21c479ecd861dcf
SPKI SHA256	ea9d0bf13f63da402adc8e4b88b6edf9968ebacba927ae7ececec746b6bb1fec

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

mail.protection.outlook.com | c6d2c97
Not After: 17 Sep 2025 23:59:59 UTC (expires in 10 months 19 days)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Names	mail.protection.outlook.com .mail.eo.outlook.com .mail.protection.outlook.com mail.messaging.microsoft.com outlook.com .olc.protection.outlook.com .pamx1.hotmail.com .mail.protection.outlook.de .mx.microsoft .k-v1.mx.microsoft .n-v1.mx.microsoft .q-v1.mx.microsoft .y-v1.mx.microsoft .d-v1.mx.microsoft .e-v1.mx.microsoft .a-v1.mx.microsoft .r-v1.mx.microsoft .w-v1.mx.microsoft .p-v1.mx.microsoft .x-v1.mx.microsoft .j-v1.mx.microsoft .s-v1.mx.microsoft .c-v1.mx.microsoft .b-v1.mx.microsoft .f-v1.mx.microsoft .i-v1.mx.microsoft .t-v1.mx.microsoft .m-v1.mx.microsoft .o-v1.mx.microsoft .g-v1.mx.microsoft .v-v1.mx.microsoft .h-v1.mx.microsoft .l-v1.mx.microsoft *.u-v1.mx.microsoft
Subject DN	CN=mail.protection.outlook.com, O=Microsoft Corporation, L=Redmond, ST=Washington, C=US
Subject Key Identifier	80f6a64b6e022eb58e77c8c9466e2dc52f1eac61
Serial	4cf0b5a9d67a87e3397aca32337f538
Not Before	18 Sep 2024 00:00:00 UTC
Not After	17 Sep 2025 23:59:59 UTC
Validity period	365 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=DigiCert Cloud Services CA-1, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:dd51d0a23173a973ae8fb4017e5d8c57cb9ff0f7
Parent Certificate	http://cacerts.digicert.com/DigiCertCloudServicesCA-1.crt
CRL	http://crl3.digicert.com/DigiCertCloudServicesCA-1-g1.crl http://crl4.digicert.com/DigiCertCloudServicesCA-1-g1.crl
OCSP	http://ocspx.digicert.com
Certificate Transparency
Signed Certificate Timestamps	18 Sep 2024 12:46:04 UTC \| Google 'Argon2025h2' log \| Qualified 18 Sep 2024 12:46:04 UTC \| DigiCert Nessie2025 Log \| Qualified 18 Sep 2024 12:46:04 UTC \| Cloudflare 'Nimbus2025' \| Qualified
Fingerprints
SHA1	b19c121e37cd29d820d740bf19a6e464f3d29250
SHA256	c6d2c973df529c2164fef6b56d095174d13bb60e2c6651f1d21c479ecd861dcf
SPKI SHA256	ea9d0bf13f63da402adc8e4b88b6edf9968ebacba927ae7ececec746b6bb1fec

Intermediate certificate

DigiCert Cloud Services CA-1 | 5f88694
Not After: 24 Sep 2030 23:59:59 UTC (expires in 5 years 10 months)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Subject DN	CN=DigiCert Cloud Services CA-1, O=DigiCert Inc, C=US
Subject Key Identifier	dd51d0a23173a973ae8fb4017e5d8c57cb9ff0f7
Serial	f171a48c6f223809218cd2ed6ddc0e8
Not Before	25 Sep 2020 00:00:00 UTC
Not After	24 Sep 2030 23:59:59 UTC
Validity period	3652 days
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	serverAuth, clientAuth
Issuer
Issuer DN	CN=DigiCert Global Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Not Applicable
Authority Key Identifier	keyid:03de503556d14cbb66f0a3e21b1bc397b23dd155
Parent Certificate	http://cacerts.digicert.com/DigiCertGlobalRootCA.crt
CRL	http://crl3.digicert.com/DigiCertGlobalRootCA.crl http://crl4.digicert.com/DigiCertGlobalRootCA.crl
OCSP	http://ocsp.digicert.com
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	b3f6b64a07bb9611f47174407841f564fb991f29
SHA256	5f88694615e4c61686e106b84c3338c6720c535f60d36f61282ed15e1977dd44
SPKI SHA256	520a545696ab8a693c4028ed59069443b106aedaf291cfcbf0deba121158dd51

Root certificate

DigiCert Global Root CA | 4348a0e
Not After: 10 Nov 2031 00:00:00 UTC (expires in 7 years 11 days)
Authentication: RSA 2048 bits (SHA1withRSA)
View details

Subject DN	CN=DigiCert Global Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
Subject Key Identifier	03de503556d14cbb66f0a3e21b1bc397b23dd155
Serial	83be056904246b1a1756ac95991c74a
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 Global Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Self-signed
Authority Key Identifier	keyid:03de503556d14cbb66f0a3e21b1bc397b23dd155
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	a8985d3a65e5e5c4b2d7d66d40c6dd2fb19c5436
SHA256	4348a0e9444c78cb265e058d5e8944b4d84f9662bd26db257f8934a443c70161
SPKI SHA256	aff988906dde12955d9bebbf928fdcc31cce328d5b9384f21c8941ca26e20391

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	godaddy.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-0.godaddy.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-0.godaddy.com -all

Location: godaddy.com

SPF policy is valid

Good. Your SPF policy is syntactically valid.

Policy uses default fail

Excellent. This policy fails hosts that are not allowed to send email for this domain name.

Policy DNS lookups under limit

Good. Your policy stays under the limit of up to 10 DNS queries. The SPF specification Section 4.6.4. requires implementations to limit the total number of DNS queries. Policies that exceed the limit should not be used and may not work in practice.

Lookups: 3

SPF Policy Information Included policy

Host where this policy is located.Location	spf-0.godaddy.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	207.200.21.144/28
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	12.151.77.31
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	69.64.33.132
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	68.233.77.16
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	184.168.131.0/24
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	173.201.192.0/24
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	182.50.132.0/24
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	170.146.0.0/16
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	174.128.1.0/24
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	173.201.193.0/24
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	174.128.7.0/24
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	206.252.132.65
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	24.75.14.201
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	144.202.243.25
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	68.232.128.0/19
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	216.55.155.13
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	216.55.162.41
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	195.246.112.0/24
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	92.51.170.64/27
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	216.69.160.6
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	66.246.252.57
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	216.242.235.41
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	207.71.241.81
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	4.79.224.144/29
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	68.178.252.0/24
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	208.109.0.0/16
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	64.202.160.0/19
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	68.178.232.0/24
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	72.167.0.0/16
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	66.98.158.77
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	68.178.213.0/24
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	198.71.224.0/24
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	198.71.225.0/24
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	198.71.244.0/25
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	198.71.245.0/25
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	198.71.246.0/25
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	198.71.247.0/25
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	198.71.253.0/24
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	198.71.254.0/24
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	198.71.255.0/24
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	52.89.65.132
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	54.214.222.76
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	54.184.82.65
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	52.26.164.15
This mechanism matches if the sending IP address is one of the IP addresses that belong to the target domain name. Matches both IPv4 and IPv6 addresses. a	spf-0.godaddy.com
Evaluates SPF policy specified in another DNS location. This directive is typically used to allow hosts controlled by another organization. include	spf.protection.outlook.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

SPF Policy Information Included policy

Host where this policy is located.Location	spf.protection.outlook.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	40.92.0.0/15
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	40.107.0.0/16
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	52.100.0.0/15
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	52.102.0.0/16
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	52.103.0.0/17
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	104.47.0.0/17
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2a01:111:f400::/48
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2a01:111:f403::/49
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2a01:111:f403:8000::/51
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2a01:111:f403:c000::/51
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2a01:111:f403:f000::/52
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.godaddy.com
DMARC version used by this policy.v	DMARC1
Indicates the policy to be enacted by the receiver at the request of the domain owner. Possible values are: none, quarantine, and reject.p	reject
Percentage of messages from mail stream to which the DMARC policy is to be applied.pct	100
Addresses to which aggregate feedback is to be sent.rua	mailto:report@dmarc.em.secureserver.net, mailto:dmarc_agg@dmarc.250ok.net
Addresses to which message-specific failure information is to be reported.ruf	mailto:godaddy-dmarc@datafeeds.phishlabs.com

Analysis

DMARC policy found

Policy: v=DMARC1; p=reject; pct=100; rua=mailto:report@dmarc.em.secureserver.net, mailto:dmarc_agg@dmarc.250ok.net; ruf=mailto:godaddy-dmarc@datafeeds.phishlabs.com

Host: _dmarc.godaddy.com

Valid external destination

Permission record location: godaddy.com._report._dmarc.datafeeds.phishlabs.com

External destination: mailto:godaddy-dmarc@datafeeds.phishlabs.com

Permission record contents: v=DMARC1

Valid external destination

Permission record location: godaddy.com._report._dmarc.dmarc.250ok.net

External destination: mailto:dmarc_agg@dmarc.250ok.net

Permission record contents: v=DMARC1

Valid external destination

Permission record location: godaddy.com._report._dmarc.dmarc.em.secureserver.net

External destination: mailto:report@dmarc.em.secureserver.net

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

1

http://godaddy.com/

HTTP/1.1 301 Redirect

Date	Tue, 29 Oct 2024 03:11:20 GMT
Connection	keep-alive
Server	ATS/9.2.3
Cache-Control	no-store
Location	https://www.godaddy.com/
Content-Type	text/html
Content-Language	en
Content-Length	306

2

https://www.godaddy.com/

HTTP/1.1 403 Forbidden

Server	AkamaiGHost
Mime-Version	1.0
Content-Type	text/html
Content-Length	369
Expires	Tue, 29 Oct 2024 03:11:20 GMT
Cache-Control	max-age=0, no-cache, no-store
Pragma	no-cache
Date	Tue, 29 Oct 2024 03:11:20 GMT
Connection	close
Set-Cookie	market=en-US; expires=Wed, 29-Oct-2025 03:11:20 GMT; path=/; domain=.godaddy.com
Set-Cookie	currency=USD; expires=Wed, 29-Oct-2025 03:11:20 GMT; path=/; domain=.godaddy.com
Set-Cookie	AKA_A2=A; expires=Tue, 29-Oct-2024 04:11:20 GMT; path=/; domain=godaddy.com; secure; HttpOnly
X-Frame-Options	DENY
X-ORIGIN-TAG	frontdoor
Set-Cookie	akaas_godaddy-com-wildcard=2147483647~rv=54~id=4f48d2e7b4c3cc6d26201be849a48d25~rn=; path=/; Secure; SameSite=None
X-ARC	2
X-ARC	6a
Server-Timing	ak_p; desc="1730171480250_389979083_433613277_269_21378_3_24_-";dur=1

Analysis

HTTP redirects to HTTPS

Good. This plaintext HTTP server redirects to HTTPS.

URL: http://www.godaddy.com/

1

http://www.godaddy.com/

HTTP/1.1 403 Forbidden

Server	AkamaiGHost
Mime-Version	1.0
Content-Type	text/html
Content-Length	369
Expires	Tue, 29 Oct 2024 03:11:20 GMT
Cache-Control	max-age=0, no-cache, no-store
Pragma	no-cache
Date	Tue, 29 Oct 2024 03:11:20 GMT
Connection	close
Set-Cookie	market=en-US; expires=Wed, 29-Oct-2025 03:11:20 GMT; path=/; domain=.godaddy.com
Set-Cookie	currency=USD; expires=Wed, 29-Oct-2025 03:11:20 GMT; path=/; domain=.godaddy.com
X-Frame-Options	DENY
X-ORIGIN-TAG	frontdoor
Set-Cookie	akaas_godaddy-com-wildcard=2147483647~rv=49~id=4d4c58af7546f8c36cf48ea6f572d07f~rn=; path=/
X-ARC	2
X-ARC	1
X-ARC	6a
Set-Cookie	bm_ss=ab8e18ef4e; Domain=.godaddy.com; Path=/; HttpOnly; Max-Age=3600
Set-Cookie	_abck=3C1E48CB63B7E50B7BC1312C3E4D40BF~-1~YAAQiWrcFx4bl8CSAQAAEqlB1gzaDEPpVqShKaNs2+0aogYbzrrA0bRj6lDkYxdWQv5rRx8199d3hKULYznCS1cFSDeGVPU9Mf8iuDvZws5/gXXI1K7QrzSTjyWIvdaDzPAnOlHZ4kf7ZqbpHW0AiG8Tzu2xsHb15vVaWX9gJUQw4UEWk/z4LyLHEOo8T7hDPkvpuoeQTgc+AhKt6uc4CqcP3l/bhngIpn/iW3caQkYFeVli2smJ7asMj0zE4B1eHO0AqHZru77CLXVzZWqKcccXsuLVrar9aDsChRj1w4N7ly3k/aY5taMilgvlq77XybcpyPj4ZwfRTKAyumD2WSG5ojbf1eTWeGefbBXF6FnXoTdYIjG1+Q7GBWzDEi+107FPb3Q6cG22~-1~-1~-1; Domain=.godaddy.com; Path=/; Expires=Wed, 29 Oct 2025 03:11:20 GMT; Max-Age=31536000
Set-Cookie	bm_s=YAAQiWrcFx8bl8CSAQAAEqlB1gKKt4w1oiFpwytnfo8qpU4GpkdSUTvW+pc3UNKTsN2pOz6s4BSvnW57cOCTnX2HLgH/bUCuO1ukrIR8lSTbefLa6AwZj+HSDdmw/wYgMK0mfRqMR+UbegVigY7EVj90VptOGqb7Jl7+DlzLYiw93wfSP0ZPVRK3JxXLkHutAov9Ha+GFv+Jnq7vBI81qfRnhdfzSM4tUrLit+BkXUi7dRBODx9rX9D+l1kKkkvK9M5cl/YyO/sfDZ2hecyGXbGqhkq4a/jHzjAyoJWgmeoOXlDvlSjsXTVgNhe3QF38JU+GdA+OMfq3UUZ2FZQ4Rnm9Q2A+; Domain=.godaddy.com; Path=/; Expires=Fri, 29 Nov 2024 03:11:20 GMT; Max-Age=2678400; HttpOnly
Set-Cookie	bm_sz=23BE0044377D2804841141F4319122B9~YAAQiWrcFyAbl8CSAQAAEqlB1hlE6STwjvTGEC0+oxxVG+8B6ZUxPUQynkyARJmwcszf5ugo0eRs+xXCefrbGf4oQSvhLGLTK/1u+rdqn4Ndk98StsBT/pZwWFwe4AcaCw0ZPn632OTzHOpltHFGUJ8XobYkUvw4AjmPH5eBBuDsQiK5j/meDNWY7YtVPw9ucST4BWPssUYx00kSmhghkc/QSBnzo8CCZX2fk1HCwV1Z4A+r++0vxq4PtdplSu6SX1zNLWXTAQUm2jTiIGqW/YGinwoEwCqmEDWkZU7aa3XatkwzeSxVxmNj/1lP89C6BDp6mDt06N2mHwwVGNuGN31qs8cLy+XXoHnc6UiGxOQsIWkFD00NQlmatxlPKOFaW5wG~3163188~4407605; Domain=.godaddy.com; Path=/; Expires=Tue, 29 Oct 2024 07:11:20 GMT; Max-Age=14400
Server-Timing	ak_p; desc="1730171480313_400321161_1396511201_15_22842_3_0_-";dur=1

Analysis

Plaintext HTTP server without HTTPS redirection doesn't appear to serve content

This plaintext HTTP server doesn't redirect to HTTPS, but it appears that no content is served from this insecure location. For web sites it is usually a good idea to redirect to port 443. For hosts that are intended for machine use (e.g., API and resource servers), it's better to fail hard. Redirections are often insecure and yet difficult to detect.

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

1

https://godaddy.com/

HTTP/1.1 301 Redirect

Date	Tue, 29 Oct 2024 03:11:20 GMT
Connection	keep-alive
Server	ATS/9.2.3
Cache-Control	no-store
Location	https://www.godaddy.com/
Content-Type	text/html
Content-Language	en
Content-Length	306

2

https://www.godaddy.com/

HTTP/1.1 403 Forbidden

Server	AkamaiGHost
Mime-Version	1.0
Content-Type	text/html
Content-Length	369
Expires	Tue, 29 Oct 2024 03:11:20 GMT
Cache-Control	max-age=0, no-cache, no-store
Pragma	no-cache
Date	Tue, 29 Oct 2024 03:11:20 GMT
Connection	close
Set-Cookie	market=en-US; expires=Wed, 29-Oct-2025 03:11:20 GMT; path=/; domain=.godaddy.com
Set-Cookie	currency=USD; expires=Wed, 29-Oct-2025 03:11:20 GMT; path=/; domain=.godaddy.com
Set-Cookie	AKA_A2=A; expires=Tue, 29-Oct-2024 04:11:20 GMT; path=/; domain=godaddy.com; secure; HttpOnly
X-Frame-Options	DENY
X-ORIGIN-TAG	frontdoor
Set-Cookie	akaas_godaddy-com-wildcard=2147483647~rv=27~id=a7ce72f85a5046e3cba1a7282e63c12d~rn=; path=/; Secure; SameSite=None
X-ARC	2
X-ARC	6a
Server-Timing	ak_p; desc="1730171480628_389979083_433614701_18_20734_3_52_-";dur=1

URL: https://www.godaddy.com/

1

https://www.godaddy.com/

HTTP/1.1 403 Forbidden

Server	AkamaiGHost
Mime-Version	1.0
Content-Type	text/html
Content-Length	369
Expires	Tue, 29 Oct 2024 03:11:20 GMT
Cache-Control	max-age=0, no-cache, no-store
Pragma	no-cache
Date	Tue, 29 Oct 2024 03:11:20 GMT
Connection	close
Set-Cookie	market=en-US; expires=Wed, 29-Oct-2025 03:11:20 GMT; path=/; domain=.godaddy.com
Set-Cookie	currency=USD; expires=Wed, 29-Oct-2025 03:11:20 GMT; path=/; domain=.godaddy.com
Set-Cookie	AKA_A2=A; expires=Tue, 29-Oct-2024 04:11:20 GMT; path=/; domain=godaddy.com; secure; HttpOnly
X-Frame-Options	DENY
X-ORIGIN-TAG	frontdoor
Set-Cookie	akaas_godaddy-com-wildcard=2147483647~rv=20~id=4fc17173834e040079e2dcaf47d292a0~rn=; path=/; Secure; SameSite=None
X-ARC	2
X-ARC	6a
Server-Timing	ak_p; desc="1730171480716_400321161_1396512405_24_21105_3_47_-";dur=1

WWW TLS

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

Test passed

Everything seems to be well configured. Well done.

TLS Configuration: www.godaddy.com (2600:1408:c400:1881:0:0:0:1771)

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 setting enables negotiation of best security.

All TLS connections with this server satisfy Apple's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

All TLS connections with this server satisfy Chrome's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

DHE suites not supported

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

TLS Configuration: www.godaddy.com (23.13.154.6)

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 setting enables negotiation of best security.

All TLS connections with this server satisfy Apple's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

All TLS connections with this server satisfy Chrome's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

DHE suites not supported

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

TLS Configuration: www.godaddy.com (2600:1408:c400:1887:0:0:0:1771)

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 setting enables negotiation of best security.

All TLS connections with this server satisfy Apple's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

All TLS connections with this server satisfy Chrome's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

DHE suites not supported

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

TLS Configuration: godaddy.com (208.109.192.70)

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_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_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_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_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 Suite ID: 0xc028 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_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)

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 setting enables negotiation of best security.

All TLS connections with this server satisfy Apple's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

All TLS connections with this server satisfy Chrome's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

DHE suites not supported

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

WWW Certificates

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

Test passed

Everything seems to be well configured. Well done.

Certificate: www.godaddy.com

Leaf certificate

*.godaddy.com
Issuer: GoDaddy
Not Before: 17 Oct 2024 16:36:33 UTC
Not After: 18 Nov 2025 16:36:33 UTC (expires in 1 year 20 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
View details

Names	*.godaddy.com godaddy.com
Subject DN	CN=*.godaddy.com, O=GoDaddy Inc., L=Tempe, ST=Arizona, C=US
Subject Key Identifier	02c7519e22a7b7989744861a4cdd6000735197c5
Serial	a122f26a583fe9f5
Not Before	17 Oct 2024 16:36:33 UTC
Not After	18 Nov 2025 16:36:33 UTC
Validity period	398 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=Go Daddy Secure Certificate Authority - G2, OU=http://certs.godaddy.com/repository/, O="GoDaddy.com, Inc.", L=Scottsdale, ST=Arizona, C=US
Certification Authority	GoDaddy
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:40c2bd278ecc348330a233d7fb6cb3f0b42c80ce
Parent Certificate	http://certificates.godaddy.com/repository/gdig2.crt
CRL	http://crl.godaddy.com/gdig2s2-40.crl
OCSP	http://ocsp.godaddy.com/
Certificate Transparency
Signed Certificate Timestamps	17 Oct 2024 16:36:34 UTC \| Google 'Argon2025h2' log \| Qualified 17 Oct 2024 16:36:34 UTC \| DigiCert Yeti2025 Log \| Qualified 17 Oct 2024 16:36:37 UTC \| Cloudflare 'Nimbus2025' \| Qualified
Fingerprints
SHA1	00f6a37c8aa3ace206a6e64c0046de6d2dddb549
SHA256	e68a3da6956f6017da5a559b0e391a76b6fcaa7df70b3e5f4c0e876edf0c63fd
SPKI SHA256	dd607116f7aaf9d801d9bc17a4b804f46b60bfa708c10e9ccf0d5fa2b62040eb

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

*.godaddy.com | e68a3da
Not After: 18 Nov 2025 16:36:33 UTC (expires in 1 year 20 days)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Names	*.godaddy.com godaddy.com
Subject DN	CN=*.godaddy.com, O=GoDaddy Inc., L=Tempe, ST=Arizona, C=US
Subject Key Identifier	02c7519e22a7b7989744861a4cdd6000735197c5
Serial	a122f26a583fe9f5
Not Before	17 Oct 2024 16:36:33 UTC
Not After	18 Nov 2025 16:36:33 UTC
Validity period	398 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=Go Daddy Secure Certificate Authority - G2, OU=http://certs.godaddy.com/repository/, O="GoDaddy.com, Inc.", L=Scottsdale, ST=Arizona, C=US
Certification Authority	GoDaddy
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:40c2bd278ecc348330a233d7fb6cb3f0b42c80ce
Parent Certificate	http://certificates.godaddy.com/repository/gdig2.crt
CRL	http://crl.godaddy.com/gdig2s2-40.crl
OCSP	http://ocsp.godaddy.com/
Certificate Transparency
Signed Certificate Timestamps	17 Oct 2024 16:36:34 UTC \| Google 'Argon2025h2' log \| Qualified 17 Oct 2024 16:36:34 UTC \| DigiCert Yeti2025 Log \| Qualified 17 Oct 2024 16:36:37 UTC \| Cloudflare 'Nimbus2025' \| Qualified
Fingerprints
SHA1	00f6a37c8aa3ace206a6e64c0046de6d2dddb549
SHA256	e68a3da6956f6017da5a559b0e391a76b6fcaa7df70b3e5f4c0e876edf0c63fd
SPKI SHA256	dd607116f7aaf9d801d9bc17a4b804f46b60bfa708c10e9ccf0d5fa2b62040eb

Intermediate certificate

Go Daddy Secure Certificate Authority - G2 | 973a412
Not After: 03 May 2031 07:00:00 UTC (expires in 6 years 6 months)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Subject DN	CN=Go Daddy Secure Certificate Authority - G2, OU=http://certs.godaddy.com/repository/, O="GoDaddy.com, Inc.", L=Scottsdale, ST=Arizona, C=US
Subject Key Identifier	40c2bd278ecc348330a233d7fb6cb3f0b42c80ce
Serial	7
Not Before	03 May 2011 07:00:00 UTC
Not After	03 May 2031 07:00:00 UTC
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=Go Daddy Root Certificate Authority - G2, O="GoDaddy.com, Inc.", L=Scottsdale, ST=Arizona, C=US
Certification Authority	GoDaddy
Validation Type	Not Applicable
Authority Key Identifier	keyid:3a9a8507106728b6eff6bd05416e20c194da0fde
CRL	http://crl.godaddy.com/gdroot-g2.crl
OCSP	http://ocsp.godaddy.com/
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	27ac9369faf25207bb2627cefaccbe4ef9c319b8
SHA256	973a41276ffd01e027a2aad49e34c37846d3e976ff6a620b6712e33832041aa6
SPKI SHA256	f11c3dd048f74edb7c45192b83e5980d2f67ec84b4ddb9396e33ff5173ed698f

Root certificate

Go Daddy Root Certificate Authority - G2 | 45140b3
Not After: 31 Dec 2037 23:59:59 UTC (expires in 13 years 2 months)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Subject DN	CN=Go Daddy Root Certificate Authority - G2, O="GoDaddy.com, Inc.", L=Scottsdale, ST=Arizona, C=US
Subject Key Identifier	3a9a8507106728b6eff6bd05416e20c194da0fde
Serial	0
Not Before	01 Sep 2009 00:00:00 UTC
Not After	31 Dec 2037 23:59:59 UTC
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=Go Daddy Root Certificate Authority - G2, O="GoDaddy.com, Inc.", L=Scottsdale, ST=Arizona, C=US
Certification Authority	GoDaddy
Validation Type	Self-signed
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	47beabc922eae80e78783462a79f45c254fde68b
SHA256	45140b3247eb9cc8c5b4f0d7b53091f73292089e6e5a63e2749dd3aca9198eda
SPKI SHA256	2a8f2d8af0eb123898f74c866ac3fa669054e23c17bc7a95bd0234192dc635d0

Analysis

Certificate chain is correct

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

Certificate: godaddy.com

Leaf certificate

godaddy.com
Issuer: GoDaddy
Not Before: 29 Dec 2023 21:00:29 UTC
Not After: 29 Jan 2025 21:00:29 UTC (expires in 3 months 17 hours)
Key: RSA 2048 bits
Signature: SHA256withRSA
View details

Names	godaddy.com www.godaddy.com
Subject DN	CN=godaddy.com
Subject Key Identifier	40ba6bd080570ca64b0a3c8c95d294a447dd1aad
Serial	21c7d335b1935c1a
Not Before	29 Dec 2023 21:00:29 UTC
Not After	29 Jan 2025 21:00:29 UTC
Validity period	398 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=Go Daddy Secure Certificate Authority - G2, OU=http://certs.godaddy.com/repository/, O="GoDaddy.com, Inc.", L=Scottsdale, ST=Arizona, C=US
Certification Authority	GoDaddy
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:40c2bd278ecc348330a233d7fb6cb3f0b42c80ce
Parent Certificate	http://certificates.godaddy.com/repository/gdig2.crt
CRL	http://crl.godaddy.com/gdig2s1-14457.crl
OCSP	http://ocsp.godaddy.com/
Certificate Transparency
Signed Certificate Timestamps	29 Dec 2023 21:00:30 UTC \| Google 'Argon2025h1' log \| Qualified 29 Dec 2023 21:00:30 UTC \| DigiCert Yeti2025 Log \| Qualified 29 Dec 2023 21:00:30 UTC \| DigiCert Nessie2025 Log \| Qualified
Fingerprints
SHA1	1f1f9e745cc405266cc80e1863b98b9ed3e5dbf7
SHA256	26e74bdf0486406402cb3d494a6d8e7905f553013eb26c5591ccf6e725d49528
SPKI SHA256	f80d97e19e3b223489ad09229ebd5143caa036392e3122d950c54378bcef6681

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

godaddy.com | 26e74bd
Not After: 29 Jan 2025 21:00:29 UTC (expires in 3 months 17 hours)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Names	godaddy.com www.godaddy.com
Subject DN	CN=godaddy.com
Subject Key Identifier	40ba6bd080570ca64b0a3c8c95d294a447dd1aad
Serial	21c7d335b1935c1a
Not Before	29 Dec 2023 21:00:29 UTC
Not After	29 Jan 2025 21:00:29 UTC
Validity period	398 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=Go Daddy Secure Certificate Authority - G2, OU=http://certs.godaddy.com/repository/, O="GoDaddy.com, Inc.", L=Scottsdale, ST=Arizona, C=US
Certification Authority	GoDaddy
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:40c2bd278ecc348330a233d7fb6cb3f0b42c80ce
Parent Certificate	http://certificates.godaddy.com/repository/gdig2.crt
CRL	http://crl.godaddy.com/gdig2s1-14457.crl
OCSP	http://ocsp.godaddy.com/
Certificate Transparency
Signed Certificate Timestamps	29 Dec 2023 21:00:30 UTC \| Google 'Argon2025h1' log \| Qualified 29 Dec 2023 21:00:30 UTC \| DigiCert Yeti2025 Log \| Qualified 29 Dec 2023 21:00:30 UTC \| DigiCert Nessie2025 Log \| Qualified
Fingerprints
SHA1	1f1f9e745cc405266cc80e1863b98b9ed3e5dbf7
SHA256	26e74bdf0486406402cb3d494a6d8e7905f553013eb26c5591ccf6e725d49528
SPKI SHA256	f80d97e19e3b223489ad09229ebd5143caa036392e3122d950c54378bcef6681

Intermediate certificate

Go Daddy Secure Certificate Authority - G2 | 973a412
Not After: 03 May 2031 07:00:00 UTC (expires in 6 years 6 months)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Subject DN	CN=Go Daddy Secure Certificate Authority - G2, OU=http://certs.godaddy.com/repository/, O="GoDaddy.com, Inc.", L=Scottsdale, ST=Arizona, C=US
Subject Key Identifier	40c2bd278ecc348330a233d7fb6cb3f0b42c80ce
Serial	7
Not Before	03 May 2011 07:00:00 UTC
Not After	03 May 2031 07:00:00 UTC
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=Go Daddy Root Certificate Authority - G2, O="GoDaddy.com, Inc.", L=Scottsdale, ST=Arizona, C=US
Certification Authority	GoDaddy
Validation Type	Not Applicable
Authority Key Identifier	keyid:3a9a8507106728b6eff6bd05416e20c194da0fde
CRL	http://crl.godaddy.com/gdroot-g2.crl
OCSP	http://ocsp.godaddy.com/
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	27ac9369faf25207bb2627cefaccbe4ef9c319b8
SHA256	973a41276ffd01e027a2aad49e34c37846d3e976ff6a620b6712e33832041aa6
SPKI SHA256	f11c3dd048f74edb7c45192b83e5980d2f67ec84b4ddb9396e33ff5173ed698f

Root certificate

Go Daddy Root Certificate Authority - G2 | 45140b3
Not After: 31 Dec 2037 23:59:59 UTC (expires in 13 years 2 months)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Subject DN	CN=Go Daddy Root Certificate Authority - G2, O="GoDaddy.com, Inc.", L=Scottsdale, ST=Arizona, C=US
Subject Key Identifier	3a9a8507106728b6eff6bd05416e20c194da0fde
Serial	0
Not Before	01 Sep 2009 00:00:00 UTC
Not After	31 Dec 2037 23:59:59 UTC
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=Go Daddy Root Certificate Authority - G2, O="GoDaddy.com, Inc.", L=Scottsdale, ST=Arizona, C=US
Certification Authority	GoDaddy
Validation Type	Self-signed
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	47beabc922eae80e78783462a79f45c254fde68b
SHA256	45140b3247eb9cc8c5b4f0d7b53091f73292089e6e5a63e2749dd3aca9198eda
SPKI SHA256	2a8f2d8af0eb123898f74c866ac3fa669054e23c17bc7a95bd0234192dc635d0

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: akaas_godaddy-com-wildcard

Cookie value. As far as the cookie RFC is concerned, the value is an opaque string which only the application should interpret.Value	2147483647~rv=20~id=4fc17173834e040079e2dcaf47d292a0~rn=
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	Implied (www.godaddy.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 secure

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

HTTP Cookie: market

Cookie value. As far as the cookie RFC is concerned, the value is an opaque string which only the application should interpret.Value	en-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	godaddy.com
Cookie path. This field can't be used as security measure, but it could be of use to avoid cookie name collision in non-adversarial contexts.Path	/
Cookies are designed to always expire. Session cookies are truly ephemeral and remain cached until the browser is closed. The Expires and Max-Age cookie attributes can be used to specify that a cookie should stay alive for longer.Expires	Wed Oct 29 03:11:20 UTC 2025 (11 months 29 days)
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.

HTTP Cookie: currency

Cookie value. As far as the cookie RFC is concerned, the value is an opaque string which only the application should interpret.Value	USD
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	godaddy.com
Cookie path. This field can't be used as security measure, but it could be of use to avoid cookie name collision in non-adversarial contexts.Path	/
Cookies are designed to always expire. Session cookies are truly ephemeral and remain cached until the browser is closed. The Expires and Max-Age cookie attributes can be used to specify that a cookie should stay alive for longer.Expires	Wed Oct 29 03:11:20 UTC 2025 (11 months 29 days)
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.

HTTP Cookie: AKA_A2

Cookie value. As far as the cookie RFC is concerned, the value is an opaque string which only the application should interpret.Value	A
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	godaddy.com
Cookie path. This field can't be used as security measure, but it could be of use to avoid cookie name collision in non-adversarial contexts.Path	/
Cookies are designed to always expire. Session cookies are truly ephemeral and remain cached until the browser is closed. The Expires and Max-Age cookie attributes can be used to specify that a cookie should stay alive for longer.Expires	Tue Oct 29 04:11:20 UTC 2024 (59 minutes)
The HttpOnly flag prevents the cookie from being accessed from JavaScript, thus making them more difficult to obtain after a successful XSS attack.HttpOnly
The Secure flag signals to browsers that the cookie should be transmitted only over an encrypted channel.Secure
Normally, when a browser makes a request to a web site, it sends all associated cookies. This is not always desirable, because it might allow third-party sites to perform site actions under the identity of the user. This attack is known as Cross-Site Request Forgery. With SameSite cookies (still in development, but already supported in some browsers), you can choose to be more strict. The possible values are 'lax' and 'strict'.SameSite

Analysis

Cookie is secure

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

HTML Content

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

Test passed

Everything seems to be well configured. Well done.

Encryption of Embedded Resources

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

0 script(s)
0 out of 0 are secure

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

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

Encryption of Outbound Links

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

0 link(s)
0 out of 0 are encrypted

HTTP Strict Transport Security

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

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

HSTS Policy

URL from which this policy was obtained.Location

https://www.godaddy.com/

Analysis

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

Deploy HSTS on this host

This host doesn't use HSTS, which means that its users can be easily attacked via MITM attacks. Consider deploying HSTS to disable certificate warnings and increase content and cookie security.

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.

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

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.

No external scripts
SRI not needed

No external stylesheets
SRI not needed

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

Framing blocked

Good. Your site doesn't allow page framing from any other page.

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.

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

Analysis

Explicitly disable browser XSS protection

For best security, every web site should explicitly disable browser-based XSS protection. This is because this type of functionality can be used to introduce vulnerabilities into otherwise error-free web sites.

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.

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

Public Report | godaddy.com

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

Analysis

Email (SMTP)

Analysis

Email TLS (SMTP)

TLS Configuration: godaddy-com.mail.protection.outlook.com (52.101.194.19) Cached

Analysis

TLS Configuration: godaddy-com.mail.protection.outlook.com (52.101.41.0) Cached

Analysis

TLS Configuration: godaddy-com.mail.protection.outlook.com (52.101.10.6) Cached

Analysis

TLS Configuration: godaddy-com.mail.protection.outlook.com (52.101.11.3) 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://godaddy.com/

Analysis

URL: http://www.godaddy.com/

Analysis

HTTP (443)

URL: https://godaddy.com/

URL: https://www.godaddy.com/

WWW TLS

TLS Configuration: www.godaddy.com (2600:1408:c400:1881:0:0:0:1771)

Analysis

TLS Configuration: www.godaddy.com (23.13.154.6)

Analysis

TLS Configuration: www.godaddy.com (2600:1408:c400:1887:0:0:0:1771)

Analysis

TLS Configuration: godaddy.com (208.109.192.70)

Analysis

WWW Certificates

Certificate: www.godaddy.com

Analysis

Certificate Trust

Certificate Chain

Analysis

Certificate: godaddy.com

Analysis

Certificate Trust

Certificate Chain

Analysis

DANE (443)

Cookies

HTTP Cookie: akaas_godaddy-com-wildcard

Analysis