Hardenize Report: mailchimp.com

Web Security Overview

HTTPS

Web sites need to use encryption to help their visitors know they're in the right place, as well as provide confidentiality and content integrity. Sites that don't support HTTPS may expose sensitive data and have their pages modified and subverted.

For all sites VERY IMPORTANT medium EFFORT

HTTPS Redirection

To deploy HTTPS properly, web sites must redirect all unsafe (plaintext) traffic to the encrypted variant. This approach ensures that no sensitive data is exposed and that further security technologies can be activated.

For all sites VERY IMPORTANT low EFFORT

HTTP Strict Transport Security

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

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	30 Oct 2024 00:29 UTC
Registrar
Registrar	MarkMonitor Inc.
Registrar IANA ID	292
Events
Registration	29 Jun 2001 22:51 UTC
Update	21 Jun 2024 19:20 UTC
Expiration	29 Jun 2029 22:51 UTC
Configuration
Statuses	clientDeleteProhibited clientTransferProhibited clientUpdateProhibited serverDeleteProhibited serverTransferProhibited serverUpdateProhibited
Registrar Lock
Registry Lock
Nameservers	a1-205.akam.net a14-66.akam.net a4-65.akam.net a5-65.akam.net a6-66.akam.net a7-66.akam.net
Contacts
Registrar	MarkMonitor Inc. Email: Phone: Fax:
Abuse	Email: abusecomplaints@markmonitor.com Phone: +1.2086851750 Fax:

{
  "meta": {
    "timestamp": "2024-10-30T00:29:30.350827449Z",
    "id": "f4346196-269d-4b8f-aa97-9e5980f11886",
    "type": "HZ_REGISTRABLE_DOMAIN",
    "schemaVersion": "2022-02-02",
    "producer": "whois-rdap-clients/2022-03-23",
    "sequenceNo": 0,
    "source": "NET",
    "status": "OK",
    "duration": "0.006s"
  },
  "name": "mailchimp.com",
  "punyName": "mailchimp.com",
  "source": "SOURCE_RDAP",
  "sourceLocation": "https://rdap.verisign.com/com/v1/domain/mailchimp.com",
  "sourceRaw": "{\"objectClassName\":\"domain\",\"handle\":\"74127467_DOMAIN_COM-VRSN\",\"ldhName\":\"MAILCHIMP.COM\",\"links\":[{\"value\":\"https:\\/\\/rdap.verisign.com\\/com\\/v1\\/domain\\/MAILCHIMP.COM\",\"rel\":\"self\",\"href\":\"https:\\/\\/rdap.verisign.com\\/com\\/v1\\/domain\\/MAILCHIMP.COM\",\"type\":\"application\\/rdap+json\"},{\"value\":\"https:\\/\\/rdap.markmonitor.com\\/rdap\\/domain\\/MAILCHIMP.COM\",\"rel\":\"related\",\"href\":\"https:\\/\\/rdap.markmonitor.com\\/rdap\\/domain\\/MAILCHIMP.COM\",\"type\":\"application\\/rdap+json\"}],\"status\":[\"client delete prohibited\",\"client transfer prohibited\",\"client update prohibited\",\"server delete prohibited\",\"server transfer prohibited\",\"server update prohibited\"],\"entities\":[{\"objectClassName\":\"entity\",\"handle\":\"292\",\"roles\":[\"registrar\"],\"publicIds\":[{\"type\":\"IANA Registrar ID\",\"identifier\":\"292\"}],\"vcardArray\":[\"vcard\",[[\"version\",{},\"text\",\"4.0\"],[\"fn\",{},\"text\",\"MarkMonitor Inc.\"]]],\"entities\":[{\"objectClassName\":\"entity\",\"roles\":[\"abuse\"],\"vcardArray\":[\"vcard\",[[\"version\",{},\"text\",\"4.0\"],[\"fn\",{},\"text\",\"\"],[\"tel\",{\"type\":\"voice\"},\"uri\",\"tel:+1.2086851750\"],[\"email\",{},\"text\",\"abusecomplaints@markmonitor.com\"]]]}]}],\"events\":[{\"eventAction\":\"registration\",\"eventDate\":\"2001-06-29T22:51:45Z\"},{\"eventAction\":\"expiration\",\"eventDate\":\"2029-06-29T22:51:44Z\"},{\"eventAction\":\"last changed\",\"eventDate\":\"2024-06-21T19:20:56Z\"},{\"eventAction\":\"last update of RDAP database\",\"eventDate\":\"2024-10-29T16:16:37Z\"}],\"secureDNS\":{\"delegationSigned\":false},\"nameservers\":[{\"objectClassName\":\"nameserver\",\"ldhName\":\"A1-205.AKAM.NET\"},{\"objectClassName\":\"nameserver\",\"ldhName\":\"A14-66.AKAM.NET\"},{\"objectClassName\":\"nameserver\",\"ldhName\":\"A4-65.AKAM.NET\"},{\"objectClassName\":\"nameserver\",\"ldhName\":\"A5-65.AKAM.NET\"},{\"objectClassName\":\"nameserver\",\"ldhName\":\"A6-66.AKAM.NET\"},{\"objectClassName\":\"nameserver\",\"ldhName\":\"A7-66.AKAM.NET\"}],\"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": "2001-06-29T22:51:45Z",
  "expireTime": "2029-06-29T22:51:44Z",
  "updateTime": "2024-06-21T19:20:56Z",
  "autoRenewal": false,
  "privacy": false,
  "registrarLock": true,
  "registryLock": true,
  "registrarName": "MarkMonitor Inc.",
  "registrarIanaId": "292",
  "nameservers": [{
    "name": "a1-205.akam.net",
    "punyName": "",
    "addresses": []
  }, {
    "name": "a14-66.akam.net",
    "punyName": "",
    "addresses": []
  }, {
    "name": "a4-65.akam.net",
    "punyName": "",
    "addresses": []
  }, {
    "name": "a5-65.akam.net",
    "punyName": "",
    "addresses": []
  }, {
    "name": "a6-66.akam.net",
    "punyName": "",
    "addresses": []
  }, {
    "name": "a7-66.akam.net",
    "punyName": "",
    "addresses": []
  }],
  "statuses": ["clientDeleteProhibited", "clientTransferProhibited", "clientUpdateProhibited", "serverDeleteProhibited", "serverTransferProhibited", "serverUpdateProhibited"],
  "sourceStatuses": ["client delete prohibited", "client transfer prohibited", "client update prohibited", "server delete prohibited", "server transfer prohibited", "server update prohibited"],
  "contacts": [{
    "type": "CONTACT_REGISTRAR",
    "id": "",
    "firstName": "",
    "lastName": "",
    "organization": "MarkMonitor Inc.",
    "street1": "",
    "street2": "",
    "city": "",
    "state": "",
    "postcode": "",
    "country": "",
    "countryCode": "",
    "email": "",
    "phone": "",
    "fax": ""
  }, {
    "type": "CONTACT_ABUSE",
    "id": "",
    "firstName": "",
    "lastName": "",
    "organization": "",
    "street1": "",
    "street2": "",
    "city": "",
    "state": "",
    "postcode": "",
    "country": "",
    "countryCode": "",
    "email": "abusecomplaints@markmonitor.com",
    "phone": "+1.2086851750",
    "fax": ""
  }]
}

{
  "objectClassName": "domain",
  "handle": "74127467_DOMAIN_COM-VRSN",
  "ldhName": "MAILCHIMP.COM",
  "links": [
    {
      "value": "https://rdap.verisign.com/com/v1/domain/MAILCHIMP.COM",
      "rel": "self",
      "href": "https://rdap.verisign.com/com/v1/domain/MAILCHIMP.COM",
      "type": "application/rdap+json"
    },
    {
      "value": "https://rdap.markmonitor.com/rdap/domain/MAILCHIMP.COM",
      "rel": "related",
      "href": "https://rdap.markmonitor.com/rdap/domain/MAILCHIMP.COM",
      "type": "application/rdap+json"
    }
  ],
  "status": [
    "client delete prohibited",
    "client transfer prohibited",
    "client update prohibited",
    "server delete prohibited",
    "server transfer prohibited",
    "server update prohibited"
  ],
  "entities": [
    {
      "objectClassName": "entity",
      "handle": "292",
      "roles": [
        "registrar"
      ],
      "publicIds": [
        {
          "type": "IANA Registrar ID",
          "identifier": "292"
        }
      ],
      "vcardArray": [
        "vcard",
        [
          [
            "version",
            {},
            "text",
            "4.0"
          ],
          [
            "fn",
            {},
            "text",
            "MarkMonitor Inc."
          ]
        ]
      ],
      "entities": [
        {
          "objectClassName": "entity",
          "roles": [
            "abuse"
          ],
          "vcardArray": [
            "vcard",
            [
              [
                "version",
                {},
                "text",
                "4.0"
              ],
              [
                "fn",
                {},
                "text",
                ""
              ],
              [
                "tel",
                {
                  "type": "voice"
                },
                "uri",
                "tel:+1.2086851750"
              ],
              [
                "email",
                {},
                "text",
                "abusecomplaints@markmonitor.com"
              ]
            ]
          ]
        }
      ]
    }
  ],
  "events": [
    {
      "eventAction": "registration",
      "eventDate": "2001-06-29T22:51:45Z"
    },
    {
      "eventAction": "expiration",
      "eventDate": "2029-06-29T22:51:44Z"
    },
    {
      "eventAction": "last changed",
      "eventDate": "2024-06-21T19:20:56Z"
    },
    {
      "eventAction": "last update of RDAP database",
      "eventDate": "2024-10-29T16:16:37Z"
    }
  ],
  "secureDNS": {
    "delegationSigned": false
  },
  "nameservers": [
    {
      "objectClassName": "nameserver",
      "ldhName": "A1-205.AKAM.NET"
    },
    {
      "objectClassName": "nameserver",
      "ldhName": "A14-66.AKAM.NET"
    },
    {
      "objectClassName": "nameserver",
      "ldhName": "A4-65.AKAM.NET"
    },
    {
      "objectClassName": "nameserver",
      "ldhName": "A5-65.AKAM.NET"
    },
    {
      "objectClassName": "nameserver",
      "ldhName": "A6-66.AKAM.NET"
    },
    {
      "objectClassName": "nameserver",
      "ldhName": "A7-66.AKAM.NET"
    }
  ],
  "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	DNStination Inc.
Lookup Time	30 Oct 2024 00:29 UTC
Registrar
Registrar	MarkMonitor, Inc.
Registrar IANA ID	292
Events
Registration	29 Jun 2001 22:51 UTC
Update	02 Aug 2024 02:17 UTC
Expiration	29 Jun 2029 22:51 UTC
Configuration
Statuses	clientUpdateProhibited clientDeleteProhibited clientTransferProhibited
Registrar Lock
Registry Lock	-
Nameservers	a7-66.akam.net a4-65.akam.net a14-66.akam.net a1-205.akam.net a6-66.akam.net a5-65.akam.net
Contacts
Registrar	MarkMonitor, Inc. MarkMonitor, Inc. Email: Phone: Fax:
Abuse	Email: abusecomplaints@markmonitor.com Phone: +1.2086851750 Fax:
Registrant	Domain Administrator DNStination Inc. 3450 Sacramento Street, Suite 405 94118 US Email: admin@dnstinations.com Phone: +1.4155319335 Fax: +1.4155319336
Administrative	Domain Administrator DNStination Inc. 3450 Sacramento Street, Suite 405 94118 US Email: admin@dnstinations.com Phone: +1.4155319335 Fax: +1.4155319336
Technical	Domain Administrator DNStination Inc. 3450 Sacramento Street, Suite 405 94118 US Email: admin@dnstinations.com Phone: +1.4155319335 Fax: +1.4155319336

{
  "meta": {
    "timestamp": "2024-10-30T00:29:30.556612105Z",
    "id": "955e0c83-ea35-4948-b923-2c002606447d",
    "type": "HZ_REGISTRABLE_DOMAIN",
    "schemaVersion": "2022-02-02",
    "producer": "whois-rdap-clients/2022-03-23",
    "sequenceNo": 0,
    "source": "NET",
    "status": "OK",
    "duration": "0.203s"
  },
  "name": "mailchimp.com",
  "punyName": "mailchimp.com",
  "source": "SOURCE_WHOIS",
  "sourceLocation": "whois.markmonitor.com:43",
  "sourceRaw": "Domain Name: mailchimp.com\nRegistry Domain ID: 74127467_DOMAIN_COM-VRSN\nRegistrar WHOIS Server: whois.markmonitor.com\nRegistrar URL: http://www.markmonitor.com\nUpdated Date: 2024-08-02T02:17:33+0000\nCreation Date: 2001-06-29T22:51:45+0000\nRegistrar Registration Expiration Date: 2029-06-29T22:51:44+0000\nRegistrar: MarkMonitor, Inc.\nRegistrar IANA ID: 292\nRegistrar Abuse Contact Email: abusecomplaints@markmonitor.com\nRegistrar Abuse Contact Phone: +1.2086851750\nDomain Status: clientUpdateProhibited (https://www.icann.org/epp#clientUpdateProhibited)\nDomain Status: clientTransferProhibited (https://www.icann.org/epp#clientTransferProhibited)\nDomain Status: clientDeleteProhibited (https://www.icann.org/epp#clientDeleteProhibited)\nRegistry Registrant ID: \nRegistrant Name: Domain Administrator\nRegistrant Organization: DNStination Inc.\nRegistrant Street: 3450 Sacramento Street, Suite 405\nRegistrant City: San Francisco\nRegistrant State/Province: CA\nRegistrant Postal Code: 94118\nRegistrant Country: US\nRegistrant Phone: +1.4155319335\nRegistrant Phone Ext: \nRegistrant Fax: +1.4155319336\nRegistrant Fax Ext: \nRegistrant Email: admin@dnstinations.com\nRegistry Admin ID: \nAdmin Name: Domain Administrator\nAdmin Organization: DNStination Inc.\nAdmin Street: 3450 Sacramento Street, Suite 405\nAdmin City: San Francisco\nAdmin State/Province: CA\nAdmin Postal Code: 94118\nAdmin Country: US\nAdmin Phone: +1.4155319335\nAdmin Phone Ext: \nAdmin Fax: +1.4155319336\nAdmin Fax Ext: \nAdmin Email: admin@dnstinations.com\nRegistry Tech ID: \nTech Name: Domain Administrator\nTech Organization: DNStination Inc.\nTech Street: 3450 Sacramento Street, Suite 405\nTech City: San Francisco\nTech State/Province: CA\nTech Postal Code: 94118\nTech Country: US\nTech Phone: +1.4155319335\nTech Phone Ext: \nTech Fax: +1.4155319336\nTech Fax Ext: \nTech Email: admin@dnstinations.com\nName Server: a7-66.akam.net\nName Server: a4-65.akam.net\nName Server: a14-66.akam.net\nName Server: a1-205.akam.net\nName Server: a6-66.akam.net\nName Server: a5-65.akam.net\nDNSSEC: unsigned\nURL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/\n\u003e\u003e\u003e Last update of WHOIS database: 2024-10-29T16:16:59+0000 \u003c\u003c\u003c\n\nFor more information on WHOIS status codes, please visit:\n  https://www.icann.org/resources/pages/epp-status-codes\n\nIf you wish to contact this domain’s Registrant, Administrative, or Technical\ncontact, and such email address is not visible above, you may do so via our web\nform, pursuant to ICANN’s Temporary Specification. To verify that you are not a\nrobot, please enter your email address to receive a link to a page that\nfacilitates email communication with the relevant contact(s).\n\nWeb-based WHOIS:\n  https://domains.markmonitor.com/whois\n\nIf you have a legitimate interest in viewing the non-public WHOIS details, send\nyour request and the reasons for your request to whoisrequest@markmonitor.com\nand specify the domain name in the subject line. We will review that request and\nmay ask for supporting documentation and explanation.\n\nThe data in MarkMonitor’s WHOIS database is provided for information purposes,\nand to assist persons in obtaining information about or related to a domain\nname’s registration record. While MarkMonitor believes the data to be accurate,\nthe data is provided \"as is\" with no guarantee or warranties regarding its\naccuracy.\n\nBy submitting a WHOIS query, you agree that you will use this data only for\nlawful purposes and that, under no circumstances will you use this data to:\n  (1) allow, enable, or otherwise support the transmission by email, telephone,\nor facsimile of mass, unsolicited, commercial advertising, or spam; or\n  (2) enable high volume, automated, or electronic processes that send queries,\ndata, or email to MarkMonitor (or its systems) or the domain name contacts (or\nits systems).\n\nMarkMonitor reserves the right to modify these terms at any time.\n\nBy submitting this query, you agree to abide by this policy.\n\nMarkMonitor Domain Management(TM)\nProtecting companies and consumers in a digital world.\n\nVisit MarkMonitor at https://www.markmonitor.com\nContact us at +1.8007459229\nIn Europe, at +44.02032062220\n\n",
  "tld": "com",
  "suffix": "com",
  "createTime": "2001-06-29T22:51:45Z",
  "expireTime": "2029-06-29T22:51:44Z",
  "updateTime": "2024-08-02T02:17:33Z",
  "autoRenewal": false,
  "privacy": false,
  "registrarLock": true,
  "registrarName": "MarkMonitor, Inc.",
  "registrarIanaId": "292",
  "registrarUrl": "http://www.markmonitor.com",
  "registrant": "DNStination Inc.",
  "nameservers": [{
    "name": "a7-66.akam.net",
    "punyName": "",
    "addresses": []
  }, {
    "name": "a4-65.akam.net",
    "punyName": "",
    "addresses": []
  }, {
    "name": "a14-66.akam.net",
    "punyName": "",
    "addresses": []
  }, {
    "name": "a1-205.akam.net",
    "punyName": "",
    "addresses": []
  }, {
    "name": "a6-66.akam.net",
    "punyName": "",
    "addresses": []
  }, {
    "name": "a5-65.akam.net",
    "punyName": "",
    "addresses": []
  }],
  "statuses": ["clientUpdateProhibited", "clientDeleteProhibited", "clientTransferProhibited"],
  "sourceStatuses": ["clientUpdateProhibited (https://www.icann.org/epp#clientUpdateProhibited)", "clientTransferProhibited (https://www.icann.org/epp#clientTransferProhibited)", "clientDeleteProhibited (https://www.icann.org/epp#clientDeleteProhibited)"],
  "contacts": [{
    "type": "CONTACT_REGISTRAR",
    "id": "",
    "firstName": "MarkMonitor, Inc.",
    "lastName": "",
    "organization": "MarkMonitor, Inc.",
    "street1": "",
    "street2": "",
    "city": "",
    "state": "",
    "postcode": "",
    "country": "",
    "countryCode": "",
    "email": "",
    "phone": "",
    "fax": ""
  }, {
    "type": "CONTACT_ABUSE",
    "id": "",
    "firstName": "",
    "lastName": "",
    "organization": "",
    "street1": "",
    "street2": "",
    "city": "",
    "state": "",
    "postcode": "",
    "country": "",
    "countryCode": "",
    "email": "abusecomplaints@markmonitor.com",
    "phone": "+1.2086851750",
    "fax": ""
  }, {
    "type": "CONTACT_REGISTRANT",
    "id": "",
    "firstName": "Domain Administrator",
    "lastName": "",
    "organization": "DNStination Inc.",
    "street1": "3450 Sacramento Street, Suite 405",
    "street2": "",
    "city": "San Francisco",
    "state": "CA",
    "postcode": "94118",
    "country": "US",
    "countryCode": "",
    "email": "admin@dnstinations.com",
    "phone": "+1.4155319335",
    "fax": "+1.4155319336"
  }, {
    "type": "CONTACT_ADMINISTRATIVE",
    "id": "",
    "firstName": "Domain Administrator",
    "lastName": "",
    "organization": "DNStination Inc.",
    "street1": "3450 Sacramento Street, Suite 405",
    "street2": "",
    "city": "San Francisco",
    "state": "CA",
    "postcode": "94118",
    "country": "US",
    "countryCode": "",
    "email": "admin@dnstinations.com",
    "phone": "+1.4155319335",
    "fax": "+1.4155319336"
  }, {
    "type": "CONTACT_TECHNICAL",
    "id": "",
    "firstName": "Domain Administrator",
    "lastName": "",
    "organization": "DNStination Inc.",
    "street1": "3450 Sacramento Street, Suite 405",
    "street2": "",
    "city": "San Francisco",
    "state": "CA",
    "postcode": "94118",
    "country": "US",
    "countryCode": "",
    "email": "admin@dnstinations.com",
    "phone": "+1.4155319335",
    "fax": "+1.4155319336"
  }]
}

Domain Name: mailchimp.com
Registry Domain ID: 74127467_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.markmonitor.com
Registrar URL: http://www.markmonitor.com
Updated Date: 2024-08-02T02:17:33+0000
Creation Date: 2001-06-29T22:51:45+0000
Registrar Registration Expiration Date: 2029-06-29T22:51:44+0000
Registrar: MarkMonitor, Inc.
Registrar IANA ID: 292
Registrar Abuse Contact Email: abusecomplaints@markmonitor.com
Registrar Abuse Contact Phone: +1.2086851750
Domain Status: clientUpdateProhibited (https://www.icann.org/epp#clientUpdateProhibited)
Domain Status: clientTransferProhibited (https://www.icann.org/epp#clientTransferProhibited)
Domain Status: clientDeleteProhibited (https://www.icann.org/epp#clientDeleteProhibited)
Registry Registrant ID: 
Registrant Name: Domain Administrator
Registrant Organization: DNStination Inc.
Registrant Street: 3450 Sacramento Street, Suite 405
Registrant City: San Francisco
Registrant State/Province: CA
Registrant Postal Code: 94118
Registrant Country: US
Registrant Phone: +1.4155319335
Registrant Phone Ext: 
Registrant Fax: +1.4155319336
Registrant Fax Ext: 
Registrant Email: admin@dnstinations.com
Registry Admin ID: 
Admin Name: Domain Administrator
Admin Organization: DNStination Inc.
Admin Street: 3450 Sacramento Street, Suite 405
Admin City: San Francisco
Admin State/Province: CA
Admin Postal Code: 94118
Admin Country: US
Admin Phone: +1.4155319335
Admin Phone Ext: 
Admin Fax: +1.4155319336
Admin Fax Ext: 
Admin Email: admin@dnstinations.com
Registry Tech ID: 
Tech Name: Domain Administrator
Tech Organization: DNStination Inc.
Tech Street: 3450 Sacramento Street, Suite 405
Tech City: San Francisco
Tech State/Province: CA
Tech Postal Code: 94118
Tech Country: US
Tech Phone: +1.4155319335
Tech Phone Ext: 
Tech Fax: +1.4155319336
Tech Fax Ext: 
Tech Email: admin@dnstinations.com
Name Server: a7-66.akam.net
Name Server: a4-65.akam.net
Name Server: a14-66.akam.net
Name Server: a1-205.akam.net
Name Server: a6-66.akam.net
Name Server: a5-65.akam.net
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2024-10-29T16:16:59+0000 <<<

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

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

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

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

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

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

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

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

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

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

DNS Zone

The global DNS infrastructure is organized as a series of hierarchical DNS zones. The root zone hosts a number of global and country TLDs, which in turn host further zones that are delegated to their customers. Each organization that controls a zone can delegate parts of its namespace to other zones. In this test we perform detailed inspection of a DNS zone, but only if the host being tested matches the zone.

Test passed

Everything seems to be well configured. Well done.

Nameserver Names

Nameservers can be referred to by name and by address. In this section we show the names, which can appear in the NS records, the referrals from the parent zone, and the SOA record. In some situations, servers from the parent zone respond authoritatively, in which case we will include them in the list as well.

Nameserver	Operational	IPv4	IPv6	Sources
a1-205.akam.net. PRIMARY 193.108.91.205 2600:1401:2::cd				SOA REFERRAL NS
a14-66.akam.net. 184.26.161.66 2600:1480:1800::42				REFERRAL NS
a4-65.akam.net. 72.246.46.65 2600:1480:9000::41				REFERRAL NS
a5-65.akam.net. 95.100.168.65 2600:1480:b000::41				REFERRAL NS
a6-66.akam.net. 23.211.133.66 2600:1401:1::42				REFERRAL NS
a7-66.akam.net. 23.61.199.66 2600:1406:32::42				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
184.26.161.66 a14-66.akam.net. PTR: a14-66.akam.net.	NAME	4096
193.108.91.205 PRIMARY a1-205.akam.net. PTR: ns1-205.akam.net. PTR: a1-205.akam.net.	NAME	4096
23.211.133.66 a6-66.akam.net. PTR: a6-66.akam.net.	NAME	4096
23.61.199.66 a7-66.akam.net. PTR: a7-66.akam.net. PTR: ns3-66.akam.net.	NAME	4096
72.246.46.65 a4-65.akam.net. PTR: a4-65.akam.net.	NAME	4096
95.100.168.65 a5-65.akam.net. PTR: a5-65.akam.net. PTR: ns6-65.akam.net.	NAME	4096
2600:1401:1::42 a6-66.akam.net. PTR: a6-66.akam.net.	NAME	4096
2600:1401:2::cd PRIMARY a1-205.akam.net. PTR: ns1-205.akam.net. PTR: a1-205.akam.net.	NAME	4096
2600:1406:32::42 a7-66.akam.net. PTR: a7-66.akam.net. PTR: ns3-66.akam.net.	NAME	4096
2600:1480:1800::42 a14-66.akam.net. PTR: a14-66.akam.net.	NAME	4096
2600:1480:9000::41 a4-65.akam.net. PTR: a4-65.akam.net.	NAME	4096
2600:1480:b000::41 a5-65.akam.net. PTR: a5-65.akam.net. PTR: ns6-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	a1-205.akam.net.
Email address of the persons responsible for this zone. Also known as RNAME.Admin email	domains.mailchimp.com.
Zone serial or version number.Serial number	2016033303
The length of time secondary nameservers should wait before querying the primary for changes.Refresh interval	10,800 seconds (about 3 hours)
The length of time secondary nameservers should wait before querying an unresponsive primary again.Retry interval	3,600 seconds (about 1 hour)
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	600 seconds (about 10 minutes)
Time To Live (TTL) indicates for how long a record remains valid. SOA record TTL	300 seconds (about 5 minutes)

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
mailchimp.com.	20	A	23.13.176.191
www.mailchimp.com.	60	CNAME	swc2.mailchimp.com.edgekey.net.
swc2.mailchimp.com.edgekey.net.	21600	CNAME	e230.x.akamaiedge.net.
e230.x.akamaiedge.net.	20	A	23.13.180.236
mailchimp.com.	1800	CAA	0 issue "letsencrypt.org"
mailchimp.com.	1800	CAA	0 issue "pki.goog"
mailchimp.com.	1800	CAA	0 issue "amazonaws.com"
mailchimp.com.	1800	CAA	0 issue "digicert.com"
mailchimp.com.	60	MX	5 mx1.intuit.iphmx.com.
mailchimp.com.	60	MX	5 mx2.intuit.iphmx.com.
mailchimp.com.	7200	NS	a1-205.akam.net.
mailchimp.com.	7200	NS	a7-66.akam.net.
mailchimp.com.	7200	NS	a14-66.akam.net.
mailchimp.com.	7200	NS	a6-66.akam.net.
mailchimp.com.	7200	NS	a5-65.akam.net.
mailchimp.com.	7200	NS	a4-65.akam.net.
mailchimp.com.	300	SOA	a1-205.akam.net. domains.mailchimp.com. 2016033303 10800 3600 1209600 600
mailchimp.com.	60	TXT	"onetrust-domain-verification=c77e00667a61495a933ef5219a1f71db"
mailchimp.com.	60	TXT	"google-gws-recovery-domain-verification=48989807"
mailchimp.com.	60	TXT	"MS=ms64719398"
mailchimp.com.	60	TXT	"google-site-verification=kjsRysndjNMMbqiWeLDEWuFKQifOKoBTpHJWZhFwr6E"
mailchimp.com.	60	TXT	"google-site-verification=gYGKtLPycLOsWo5xUlOOGWsvENDmTYIt1X9iE1PZEP8"
mailchimp.com.	60	TXT	"google-site-verification=WW0kxheERt2YHAEclRL_5DCFawde0CCdmJtXyNXS_7I"
mailchimp.com.	60	TXT	"google-site-verification=ruul5w2E3u_oxPm-3xBtwAPFtTus0sysqVmIxy5frlg"
mailchimp.com.	60	TXT	"google-site-verification=iBzo6FrDJ3rlsGoEUXL_YNHKVreLxzetIZRuCUlnBeQ"
mailchimp.com.	60	TXT	"smartsheet-site-validation=iJlsJdcpCMM9BUovg1yWWyqVYfZZWDdx"
mailchimp.com.	60	TXT	"facebook-domain-verification=hmwpoaxoffl9lyv7a1jag656uo66wb"
mailchimp.com.	60	TXT	"atlassian-domain-verification=rOuxrbpoM8X0dyjve2lLYnnHEXBtmxbGzk17YgboFB62K3dXo2gnekijahD5DdOg"
mailchimp.com.	60	TXT	"google-site-verification=6dAIWpnctxIKj5r1bLhn2iGED8AGy8W_17S6scTDbbw"
mailchimp.com.	60	TXT	"digicert-verification=zp2grw3qhjdfrzqpyybxtfbpzrk266g7"
mailchimp.com.	60	TXT	"onetrust-domain-verification=a014c8e6937e453f8448babef5311dfd"
mailchimp.com.	60	TXT	"MS=5D41393E1B1E2A326C6154F96B8D4EEBDC58A667"
mailchimp.com.	60	TXT	"google-site-verification=qSv3r3tfEN8dtGaL1jVStrokm_jKImsl4cvgUG_6q5g"
mailchimp.com.	60	TXT	"v=spf1 ip4:205.201.128.0/20 ip4:198.2.128.0/18 ip4:148.105.0.0/16 ip4:129.145.74.12 include:_spf.google.com include:mailsenders.netsuite.com include:_spf2.intuit.com " "include:_spf.qualtrics.com ip4:199.33.145.1 ip4:199.33.145.32 ip4:35.176.132.251 ip4:52.60.115.116 ~all"
mailchimp.com.	60	TXT	"adobe-idp-site-verification=b462bb17fbdf88e847859454079da73265c27a30a38d2c83f4a6e21a085a6d72"
mailchimp.com.	60	TXT	"google-site-verification=HceFICpk7mLeoOmNAIxQyKx6NMEEjRlNgU_GC7UmaZI"
mailchimp.com.	60	TXT	"docusign=a0dc4d7a-5002-4653-bb4f-959c68aa9074"
mailchimp.com.	60	TXT	"apple-domain-verification=VyVmVW02Ds1n6FQa"
mailchimp.com.	60	TXT	"zapier-domain-verification-challenge=7f0c4720-f8f2-4f40-b264-cb21fe731403"
_dmarc.mailchimp.com.	60	TXT	"v=DMARC1; p=reject; rua=mailto:19ezfriw@ag.dmarcian.com,mailto:dmarc_rua@emaildefense.proofpoint.com; ruf=mailto:19ezfriw@fr.dmarcian.com,mailto:dmarc_ruf@emaildefense.proofpoint.com;"
_domainkey.mailchimp.com.	21600	TXT	"t=y; o=~;"

Backing DNS Queries

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

	ID	Server	Question Name	Type	Status

DNSSEC

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

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

Useful DNSSEC Tools

Certification Authority Authorization

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

Test passed

Everything seems to be well configured. Well done.

CAA Policy Information

The DNS hostname where this policy is located.Policy host	mailchimp.com
The issue property tag is used to request that certificate issuers perform CAA issue restriction processing for the domain and to grant authorization to specific certificate issuers.issue	pki.goog flags: 0
The issue property tag is used to request that certificate issuers perform CAA issue restriction processing for the domain and to grant authorization to specific certificate issuers.issue	letsencrypt.org flags: 0
The issue property tag is used to request that certificate issuers perform CAA issue restriction processing for the domain and to grant authorization to specific certificate issuers.issue	amazonaws.com flags: 0
The issue property tag is used to request that certificate issuers perform CAA issue restriction processing for the domain and to grant authorization to specific certificate issuers.issue	digicert.com flags: 0

Analysis

Issuance of S/MIME certificates not restricted

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

Issuance of BIMI not restricted

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

CAA policy restricts issuance

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

Policy doesn't use reporting

This policy doesn't use reporting, which means that there is no way to contact you when a violation is detected. The CAA RFC defines the iodef property that can be used for this purpose. Do note that you're not guaranteed to be notified, given that CAs generally don't support notifications yet.

Email (SMTP)

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

Test passed

Everything seems to be well configured. Well done.

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

Server	Preference	Operational	STARTTLS	TLS	PKI	DNSSEC	DANE
mx2.intuit.iphmx.com 68.232.135.147 PTR: esa2.intuit.iphmx.com	5
mx2.intuit.iphmx.com 68.232.143.160 PTR: esa12.intuit.iphmx.com	5
mx2.intuit.iphmx.com 207.54.92.90 PTR: esa9.intuit.iphmx.com	5
mx2.intuit.iphmx.com 68.232.146.251 PTR: esa3.intuit.iphmx.com	5
mx2.intuit.iphmx.com 216.71.141.217 PTR: esa8.intuit.iphmx.com	5
mx2.intuit.iphmx.com 216.71.141.216 PTR: esa6.intuit.iphmx.com	5
mx2.intuit.iphmx.com 68.232.146.61 PTR: esa1.intuit.iphmx.com	5
mx2.intuit.iphmx.com 216.71.138.62 PTR: esa7.intuit.iphmx.com	5
mx2.intuit.iphmx.com 207.54.92.93 PTR: esa11.intuit.iphmx.com	5
mx2.intuit.iphmx.com 68.232.135.250 PTR: esa10.intuit.iphmx.com	5
mx2.intuit.iphmx.com 216.71.138.61 PTR: esa5.intuit.iphmx.com	5
mx2.intuit.iphmx.com 68.232.148.142 PTR: esa4.intuit.iphmx.com	5
mx1.intuit.iphmx.com 68.232.146.251 PTR: esa3.intuit.iphmx.com	5
mx1.intuit.iphmx.com 68.232.135.250 PTR: esa10.intuit.iphmx.com	5
mx1.intuit.iphmx.com 68.232.148.142 PTR: esa4.intuit.iphmx.com	5
mx1.intuit.iphmx.com 216.71.141.217 PTR: esa8.intuit.iphmx.com	5
mx1.intuit.iphmx.com 68.232.146.61 PTR: esa1.intuit.iphmx.com	5
mx1.intuit.iphmx.com 207.54.92.90 PTR: esa9.intuit.iphmx.com	5
mx1.intuit.iphmx.com 216.71.138.61 PTR: esa5.intuit.iphmx.com	5
mx1.intuit.iphmx.com 216.71.141.216 PTR: esa6.intuit.iphmx.com	5
mx1.intuit.iphmx.com 68.232.135.147 PTR: esa2.intuit.iphmx.com	5
mx1.intuit.iphmx.com 216.71.138.62 PTR: esa7.intuit.iphmx.com	5
mx1.intuit.iphmx.com 207.54.92.93 PTR: esa11.intuit.iphmx.com	5
mx1.intuit.iphmx.com 68.232.143.160 PTR: esa12.intuit.iphmx.com	5

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: 29 Oct 2024 03:55 UTC

Earliest cache timestamp: 29 Oct 2024 03:55 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: mx2.intuit.iphmx.com (68.232.135.147) Cached

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

mx1.intuit.iphmx.com
Issuer: IdenTrust Commercial Root CA 1
Not Before: 09 May 2024 20:15:12 UTC
Not After: 09 May 2025 20:14:12 UTC (expires in 6 months 9 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
View details

Names	mx1.intuit.iphmx.com mx2.intuit.iphmx.com ob1.intuit.iphmx.com esa1.intuit.iphmx.com esa2.intuit.iphmx.com esa3.intuit.iphmx.com esa4.intuit.iphmx.com esa5.intuit.iphmx.com esa6.intuit.iphmx.com esa7.intuit.iphmx.com esa8.intuit.iphmx.com esa9.intuit.iphmx.com esa10.intuit.iphmx.com esa11.intuit.iphmx.com esa12.intuit.iphmx.com
Subject DN	CN=mx1.intuit.iphmx.com, O=Cisco Systems Inc., L=San Jose, ST=California, C=US
Subject Key Identifier	fda6d79521fee330241c65a8fcd51bdb45f38e60
Serial	40018f5efee05297dc4e1c2db75b04cb
Not Before	09 May 2024 20:15:12 UTC
Not After	09 May 2025 20:14:12 UTC
Validity period	365 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=HydrantID Server CA O1, OU=HydrantID Trusted Certificate Service, O=IdenTrust, C=US
Certification Authority	IdenTrust Commercial Root CA 1
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:89b89bb69eedfbb0c6bd0dec674e3ca3929d2df9
Parent Certificate	http://validation.identrust.com/certs/hydrantidcaO1.p7c
CRL	http://validation.identrust.com/crl/hydrantidcao1.crl
OCSP	http://commercial.ocsp.identrust.com
Certificate Transparency
Signed Certificate Timestamps	09 May 2024 20:15:13 UTC \| Google 'Argon2025h1' log \| Qualified 09 May 2024 20:15:14 UTC \| Google 'Xenon2025h1' log \| Qualified 09 May 2024 20:15:13 UTC \| DigiCert Yeti2025 Log \| Qualified
Fingerprints
SHA1	66fc9d75b55cfac58d2921f9eabaf8c9825de11c
SHA256	faaa1233a6b592d58da192ea28538596dec108ad87ca1fdf4352c3c95f91c150
SPKI SHA256	60fd4426b4804bda295633efe4597771220550d39dc6f5ddee700b88aac3d1ee

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

mx1.intuit.iphmx.com | faaa123
Not After: 09 May 2025 20:14:12 UTC (expires in 6 months 9 days)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Names	mx1.intuit.iphmx.com mx2.intuit.iphmx.com ob1.intuit.iphmx.com esa1.intuit.iphmx.com esa2.intuit.iphmx.com esa3.intuit.iphmx.com esa4.intuit.iphmx.com esa5.intuit.iphmx.com esa6.intuit.iphmx.com esa7.intuit.iphmx.com esa8.intuit.iphmx.com esa9.intuit.iphmx.com esa10.intuit.iphmx.com esa11.intuit.iphmx.com esa12.intuit.iphmx.com
Subject DN	CN=mx1.intuit.iphmx.com, O=Cisco Systems Inc., L=San Jose, ST=California, C=US
Subject Key Identifier	fda6d79521fee330241c65a8fcd51bdb45f38e60
Serial	40018f5efee05297dc4e1c2db75b04cb
Not Before	09 May 2024 20:15:12 UTC
Not After	09 May 2025 20:14:12 UTC
Validity period	365 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=HydrantID Server CA O1, OU=HydrantID Trusted Certificate Service, O=IdenTrust, C=US
Certification Authority	IdenTrust Commercial Root CA 1
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:89b89bb69eedfbb0c6bd0dec674e3ca3929d2df9
Parent Certificate	http://validation.identrust.com/certs/hydrantidcaO1.p7c
CRL	http://validation.identrust.com/crl/hydrantidcao1.crl
OCSP	http://commercial.ocsp.identrust.com
Certificate Transparency
Signed Certificate Timestamps	09 May 2024 20:15:13 UTC \| Google 'Argon2025h1' log \| Qualified 09 May 2024 20:15:14 UTC \| Google 'Xenon2025h1' log \| Qualified 09 May 2024 20:15:13 UTC \| DigiCert Yeti2025 Log \| Qualified
Fingerprints
SHA1	66fc9d75b55cfac58d2921f9eabaf8c9825de11c
SHA256	faaa1233a6b592d58da192ea28538596dec108ad87ca1fdf4352c3c95f91c150
SPKI SHA256	60fd4426b4804bda295633efe4597771220550d39dc6f5ddee700b88aac3d1ee

Intermediate certificate

HydrantID Server CA O1 | 8bb2f68
Not After: 12 Dec 2029 16:56:15 UTC (expires in 5 years 1 month)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Subject DN	CN=HydrantID Server CA O1, OU=HydrantID Trusted Certificate Service, O=IdenTrust, C=US
Subject Key Identifier	89b89bb69eedfbb0c6bd0dec674e3ca3929d2df9
Serial	40016efb0a205cfaebe18f71d73abb78
Not Before	12 Dec 2019 16:56:15 UTC
Not After	12 Dec 2029 16:56:15 UTC
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	serverAuth, clientAuth
Issuer
Issuer DN	CN=IdenTrust Commercial Root CA 1, O=IdenTrust, C=US
Certification Authority	IdenTrust Services, LLC
Validation Type	Not Applicable
Authority Key Identifier	keyid:ed4419c0d3f0068beea47bbe42e72654c88e3676
Parent Certificate	http://validation.identrust.com/roots/commercialrootca1.p7c
CRL	http://validation.identrust.com/crl/commercialrootca1.crl
OCSP	http://commercial.ocsp.identrust.com
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	3c97cbb4491fc8d63d12b4890c28548164198edb
SHA256	8bb2f6883fed289a521ba27c478482950874e143caccec6fc025990c0c46813e
SPKI SHA256	11ea695d391af31c89703421b8a768f572f82d644e1c463b975a991b9e65308a

Root certificate

IdenTrust Commercial Root CA 1 | aae38f6
Not After: 16 Jan 2034 18:12:23 UTC (expires in 9 years 2 months)
Authentication: RSA 4096 bits (SHA256withRSA)
View details

Subject DN	CN=IdenTrust Commercial Root CA 1, O=IdenTrust, C=US
Subject Key Identifier	ed4419c0d3f0068beea47bbe42e72654c88e3676
Serial	ab8995b917dddb983e8447cb108b8b11
Not Before	16 Jan 2014 18:12:23 UTC
Not After	16 Jan 2034 18:12:23 UTC
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=IdenTrust Commercial Root CA 1, O=IdenTrust, C=US
Certification Authority	IdenTrust Services, LLC
Validation Type	Self-signed
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	a84babb85decbe457fc35e88958c38dfd8b9d3dd
SHA256	aae38f67f0a626805928507b078d89d5598d760d17335927b46606ecdfa1b946
SPKI SHA256	07e854f26a7cbd389927aa041bfef1b6cd21dd143818ad947dc655a9e587fe88

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	mailchimp.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	205.201.128.0/20
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	198.2.128.0/18
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	148.105.0.0/16
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	129.145.74.12
Evaluates SPF policy specified in another DNS location. This directive is typically used to allow hosts controlled by another organization. include	_spf.google.com
Evaluates SPF policy specified in another DNS location. This directive is typically used to allow hosts controlled by another organization. include	mailsenders.netsuite.com
Evaluates SPF policy specified in another DNS location. This directive is typically used to allow hosts controlled by another organization. include	_spf2.intuit.com
Evaluates SPF policy specified in another DNS location. This directive is typically used to allow hosts controlled by another organization. include	_spf.qualtrics.com
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	199.33.145.1
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	199.33.145.32
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	35.176.132.251
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	52.60.115.116
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 ip4:205.201.128.0/20 ip4:198.2.128.0/18 ip4:148.105.0.0/16 ip4:129.145.74.12 include:_spf.google.com include:mailsenders.netsuite.com include:_spf2.intuit.com include:_spf.qualtrics.com ip4:199.33.145.1 ip4:199.33.145.32 ip4:35.176.132.251 ip4:52.60.115.116 ~all

Location: mailchimp.com

SPF policy is valid

Good. Your SPF policy is syntactically valid.

Policy DNS lookups under limit

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

Lookups: 10

SPF Policy Information Included policy

Host where this policy is located.Location	_spf.google.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	_netblocks.google.com
Evaluates SPF policy specified in another DNS location. This directive is typically used to allow hosts controlled by another organization. include	_netblocks2.google.com
Evaluates SPF policy specified in another DNS location. This directive is typically used to allow hosts controlled by another organization. include	_netblocks3.google.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	_netblocks.google.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	35.190.247.0/24
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	64.233.160.0/19
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	66.102.0.0/20
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	66.249.80.0/20
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	72.14.192.0/18
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	74.125.0.0/16
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	108.177.8.0/21
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	173.194.0.0/16
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	209.85.128.0/17
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	216.58.192.0/19
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	216.239.32.0/19
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	_netblocks2.google.com
SPF version used by this policy.v	spf1
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2001:4860:4000::/36
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2404:6800:4000::/36
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2607:f8b0:4000::/36
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2800:3f0:4000::/36
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2a00:1450:4000::/36
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2c0f:fb50:4000::/36
This 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	_netblocks3.google.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	172.217.0.0/19
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	172.217.32.0/20
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	172.217.128.0/19
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	172.217.160.0/20
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	172.217.192.0/19
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	172.253.56.0/21
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	172.253.112.0/20
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	108.177.96.0/19
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	35.191.0.0/16
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	130.211.0.0/22
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	mailsenders.netsuite.com
SPF version used by this policy.v	spf1
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	outboundips.netsuite.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	_spf2.intuit.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	stspg-customer.com
Evaluates SPF policy specified in another DNS location. This directive is typically used to allow hosts controlled by another organization. include	mail.zendesk.com
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	139.138.35.44
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	139.138.46.121
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	139.138.46.176
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	139.138.46.219
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	139.138.57.55
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	139.138.58.119
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	216.71.138.33
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	68.232.140.138
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	107.20.210.250
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	52.1.14.157
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	stspg-customer.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	23.253.182.103
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	23.253.183.145
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	23.253.183.146
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	23.253.183.147
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	23.253.183.148
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	23.253.183.150
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	166.78.68.221
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	167.89.46.159
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	167.89.64.9
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	167.89.65.0
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	167.89.65.53
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	167.89.65.100
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	167.89.74.233
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	167.89.75.33
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	167.89.75.126
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	167.89.75.136
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	167.89.75.164
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	192.237.159.42
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	192.237.159.43
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	159.112.242.162
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	159.135.228.10
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	mail.zendesk.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	103.151.192.0/23
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	185.12.80.0/22
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	188.172.128.0/20
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	192.161.144.0/20
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	216.198.0.0/18
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.qualtrics.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	162.247.216.0/22
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	139.60.152.0/22
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	98.97.248.0/21
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	64.69.212.0/24
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	54.186.193.102/32
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	52.222.73.120/32
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	52.222.73.83
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	52.222.62.51
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	52.222.75.85
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	52.222.89.228
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	160.1.62.192
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	52.61.91.9
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	15.200.21.50
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	15.200.201.185
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	15.200.44.248
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.mailchimp.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
Addresses to which aggregate feedback is to be sent.rua	mailto:19ezfriw@ag.dmarcian.com,mailto:dmarc_rua@emaildefense.proofpoint.com
Addresses to which message-specific failure information is to be reported.ruf	mailto:19ezfriw@fr.dmarcian.com,mailto:dmarc_ruf@emaildefense.proofpoint.com

Analysis

DMARC policy found

Policy: v=DMARC1; p=reject; rua=mailto:19ezfriw@ag.dmarcian.com,mailto:dmarc_rua@emaildefense.proofpoint.com; ruf=mailto:19ezfriw@fr.dmarcian.com,mailto:dmarc_ruf@emaildefense.proofpoint.com;

Host: _dmarc.mailchimp.com

Valid external destination

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

External destination: mailto:19ezfriw@ag.dmarcian.com

Permission record contents: v=DMARC1;

Valid external destination

Permission record location: mailchimp.com._report._dmarc.emaildefense.proofpoint.com

External destination: mailto:dmarc_rua@emaildefense.proofpoint.com

Permission record contents: v=DMARC1;

Valid external destination

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

External destination: mailto:19ezfriw@fr.dmarcian.com

Permission record contents: v=DMARC1;

Policy is valid

Good. You have a valid DMARC policy.

MTA Strict Transport Security

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

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

SMTP TLS Reporting

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

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

HTTP (80)

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

Test passed

Everything seems to be well configured. Well done.

URL: http://mailchimp.com/

1

http://mailchimp.com/

HTTP/1.1 301 Moved Permanently

Server	AkamaiGHost
Content-Length	0
Location	https://mailchimp.com/
Date	Wed, 30 Oct 2024 00:29:30 GMT
Connection	keep-alive
Server-Timing	cdn-cache; desc=HIT
Server-Timing	edge; dur=1
Set-Cookie	_abck=97F4C84A7D25D8B43A8AF438BA9A2C53~-1~YAAQlGrcF8yjRdaSAQAAWNzT2gyNgPv/Enbvels3b83OW1SpYbFLQmxLvpP2IAj0XRfytDY3vCb/ag6aDEWsE6zIJQFT4LW8BQwNDl0qmItMkMA/LrFXlnYgkUVJBentGKYg0k4FSxibuR+VhE6LOTMxOwTp87BNHoDio4oJVyWlxwPP/MsZOb+ZlpeG0NQRZxq4J7z/YfxnCtEgR5vEQpSnMQ2zS+d75XY1mstr/dRS7doZD7Xm10UXpEmpAyMywkgHkl5MpMxWuTqZ1EU8i6EVpj1xJ8eMS3whDwdBvJIxbiCThrW19XK5lT7i38pfUp2JnvMHU4ZjoCgvtT56f08lNfc/wrk5jkbBtHqHwvlXeyQr1mC1jzcHcISe5xbS9EbEoQmvAUf68/Q=~-1~-1~-1; Domain=.mailchimp.com; Path=/; Expires=Thu, 30 Oct 2025 00:29:30 GMT; Max-Age=31536000; SameSite=None; Secure
Set-Cookie	bm_sz=12CD4E329CD6F82BAA6DB87A88F5CF56~YAAQlGrcF82jRdaSAQAAWNzT2hlmqevxg+VCmAbMKDpUE7WGnCxJQjJFzwQzzJ819MP/zPIZLR0m9kvjY0TXLBwxNN9t6igpAvxRKBcvamAuAw8U9AuuZ5j7h+onPXq9HXquGHekqtr8tO/btke1cWSu73YxLi59MnTjVUc+DJ6IjWbt8cT8kOkAySkr/yCWlyucEn8mcatzFcQfJEvVQ8MJ5qyU6eFQIsrcg0Efeqeot+bEheieZwv+0b0SZgkCalm1qWpqUvKnGviSeFH5dKtBGLO1nhKMWdRB5ZQ39odNxggyHsM9sbqIFpJIRk50OIt5z4Sgcyo66U0FrlrrBjE9hoGzjzBEgQrIjB5/iOiw2ShURtdNGx3sKT6gzQBZgBd0z10f~4605507~4340034; Domain=.mailchimp.com; Path=/; Expires=Wed, 30 Oct 2024 04:29:30 GMT; Max-Age=14400; SameSite=None; Secure
Server-Timing	ak_p; desc="1730248170572_400321172_270921952_14_10572_2_0_-";dur=1

2

https://mailchimp.com/

HTTP/1.1 200 OK

Content-Type	text/html; charset=UTF-8
X-UA-Compatible	IE=edge,chrome=1
X-Plums-Vary	Accept-Encoding, Accept-Language, Cookie
X-Frame-Options	SAMEORIGIN
Cache-Control	max-age=600, private, must-revalidate
X-EdgeConnect-MidMile-RTT	0
X-EdgeConnect-Origin-MEX-Latency	422
X-Akamai-Transformed	9 - 0 pmb=mTOE,1mRUM,2
Date	Wed, 30 Oct 2024 00:29:31 GMT
Connection	keep-alive
Vary	Accept-Encoding
Set-Cookie	_mcid=1.f1247f1589c4c2f227034fe107e2579f.a0c536dc16064b4fc6baa3986eaebac661f776eb2c119e0b9d4d6ecd5b4d02f0; expires=Thu, 30-Oct-2025 00:29:30 GMT; Max-Age=31536000; path=/; domain=.mailchimp.com
Set-Cookie	_mc_anon_id=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.mailchimp.com
Server-Timing	cdn-cache; desc=REVALIDATE
Server-Timing	edge; dur=373
Server-Timing	origin; dur=422
Set-Cookie	bm_sz=12CD4E329CD6F82BAA6DB87A88F5CF56~YAAQk2rcF5emAtSSAQAAnd/T2hnrFZlazUqSajoDuFsNUG0OpwfRyTpFCETv4dUY1vtNnNsAP0O7zoUaHopur90iX1NrMIKqrS9qPAt/eyD6ZXEg8nS+ZqkyeMuRZyXBtiwKsjXi+D+FDs/CEqhoWq0WvxHbp4MsVOKbN6kSe7q6soisu3iHIsoypijvv8vcbBHTeTCoTrId9092aoixiu+9UzKrXEPgwIHEB8CKSJkbKeK4gE9Sl5vNqkaJR68ASOrAEiyD+75mN9cEdrAyCNXBQT2MzLSaDwWp8NnOE955IsyIw4lCr98eB8woBax5SDlp58rQi3us51qNsBd/OR/gUf51PWjCOb8fD4SGI3pYSGWLqkZqeeVUFBNtF5HytloKXNTFyHlya9Y=~4605507~4340034; Domain=.mailchimp.com; Path=/; Expires=Wed, 30 Oct 2024 04:29:30 GMT; Max-Age=14399; SameSite=None; Secure
Server-Timing	ak_p; desc="1730248170604_400321171_440937759_79571_14027_4_5_-";dur=1

Analysis

HTTP redirects to HTTPS

Good. This plaintext HTTP server redirects to HTTPS.

URL: http://www.mailchimp.com/

1

http://www.mailchimp.com/

HTTP/1.1 302 Moved Temporarily

Server	AkamaiGHost
Content-Length	0
Location	https://www.mailchimp.com/
Cache-Control	max-age=60
Expires	Wed, 30 Oct 2024 00:30:31 GMT
Date	Wed, 30 Oct 2024 00:29:31 GMT
Connection	keep-alive
Set-Cookie	_abck=FBC191FA2373711389D40AE38ADCD8D7~-1~YAAQjWrcF1ke7IiSAQAA79/T2gw0g3+IMJj9c7/ZAr1gHGi9y6vylTF0UBHv54Bm/3Z1lVhP9OmmoU2Omj/yTUrKvFe1G3Y4dLELrPy08k6vQ4eFt3xVecvIxe+cpBRXfOPxLMqwqCParSu671fNy4yL7qHm/7jMQ17lqq88ZD5ZVIfvYemeCsYKPaeiTEdrh0359uudd2dwCCO8JskTo+bQADbXacWX7Sch420OoU3lkH4yZs5nLJtSiuR490lKptVq4zNv+GMnwgZTysNixq6lo1bILECvDIZjIL8D8QWyVPVwxe+mnOUWJTZddxrGSo2px1VA0XbBfGmgewVEbeOh2tJaDb7u8e33GUuP1QGKKEr7SdcAUd277nY/UCM6HqGmUoctylVHs/w=~-1~-1~-1; Domain=.mailchimp.com; Path=/; Expires=Thu, 30 Oct 2025 00:29:31 GMT; Max-Age=31536000; SameSite=None; Secure
Set-Cookie	bm_sz=AB629367D3069761CE4570D280034FA2~YAAQjWrcF1oe7IiSAQAA79/T2hlcNSi+BJq1/oCK3o57LrwskWkeCSfOL4LNc3VRGnxbiwpNYAJf7cm6hoLzE5Y4LjktZuOcY2lBsKjW5CrNQyYOxaPlRv/lHJSQWVcSOFdM051fbYusrG/AmNuz3k+kUbUmVThkAZVA4FEizSxaG4/aYaynSlqUkRv1CPq3FwX7aASLjB5AWyBiQTyFwGM6lp+DDH0VWT6KOdnv43O71bB6688yuPut5C7wVQLgDL1xrNtmtiK6lU0WuVfsnri4KhqkMJSF3Yv5U52YYPCdpYXhSy1k2XWKkX7/thAH3+bDKj2GyD9wd6vRM2zRWK9qLy5aQ5y5eV+nZabpuhUFyQAUs6Z2Dl4lpHl5PJ0xJyUbwhsX~3291203~3682372; Domain=.mailchimp.com; Path=/; Expires=Wed, 30 Oct 2024 04:29:31 GMT; Max-Age=14400; SameSite=None; Secure

2

https://www.mailchimp.com/

HTTP/1.1 301 Moved Permanently

Server	AkamaiGHost
Content-Length	0
Location	https://mailchimp.com/
Cache-Control	max-age=60
Expires	Wed, 30 Oct 2024 00:30:31 GMT
Date	Wed, 30 Oct 2024 00:29:31 GMT
Connection	keep-alive
Set-Cookie	bm_sz=AB629367D3069761CE4570D280034FA2~YAAQjWrcF10e7IiSAQAAGuDT2hmBRbjmchbbj/CB5s+nv9rUbERonuBbH8ZO4pkbol5gcT2CzYF3Lmxh7AJQIiqW86phUkiZ8KZzp0J/5a/U5QC8j2bWd+Wp+dghKxjGkI1wwehS5DLOiEbIFMeqaCW75WqbDQJB9G/qM5GFLYDu6sFsPeGhH1zLwvaqTImiBAAMpAlgLBS/4BFGCRTdpvLctluTZpnnnpELtN5sazNAWTemUrPmbaFMvNXzIi1Y+ysXq/HNAVnY0pqG1rssnMqm1MFg04x5BEaUjTLX/GihiM+aRO21jvBcGspS7Ub4ahpHTAiBD4h28kz6BKWN6J2GrFHOaT/st+b0Dp4Qg4OmyTj++rCnD68qXNrS4odb25rTaHTgTZ6sjns=~3291203~3682372; Domain=.mailchimp.com; Path=/; Expires=Wed, 30 Oct 2024 04:29:31 GMT; Max-Age=14400; SameSite=None; Secure

3

https://mailchimp.com/

HTTP/1.1 200 OK

Content-Type	text/html; charset=UTF-8
X-UA-Compatible	IE=edge,chrome=1
X-Plums-Vary	Accept-Encoding, Accept-Language, Cookie
X-Frame-Options	SAMEORIGIN
Cache-Control	max-age=600, private, must-revalidate
X-EdgeConnect-MidMile-RTT	0
X-EdgeConnect-Origin-MEX-Latency	422
X-Akamai-Transformed	9 - 0 pmb=mTOE,1mRUM,2
Date	Wed, 30 Oct 2024 00:29:31 GMT
Transfer-Encoding	chunked
Connection	keep-alive
Vary	Accept-Encoding
Connection	Transfer-Encoding
Server-Timing	cdn-cache; desc=HIT
Server-Timing	edge; dur=1
Set-Cookie	bm_sz=AB629367D3069761CE4570D280034FA2~YAAQk2rcF7WmAtSSAQAAauDT2hkolYAMxWu4+Ywsk1Vev2qJy1IJxmUt0uAx8l1GYYd+jZE2B8HIFa9MyASEIclF4nswvnuZNxo2xiTKoj76KNTsU2Pir75zlSt+a2LFDafW05Q7+B5yp8BTXyY4gRuqMCWteHSL6Xtzuqtizutxb+WdtQvXl044uxy7iZknOdhBDLmrCBXWjoi9ihTnSAI69vYyjR1ITZRTlDBhKvVzvVuPbLw3GE8BWRthxN5oaDWQIyw5RquB8vlWFIdyF0ZsFmXA9YJA+tUuhSM+0ka/O5sYdqlZgrIAkNCCmN+1cNqG+iYhV4iNv/vRd/AwhQhiQLppJIX9IC8ieTL/zkKmS/JpqC2O8XDJjO6zyw9meoTdnnxjHIZCrfv5V6KUDw==~3291203~3682372; Domain=.mailchimp.com; Path=/; Expires=Wed, 30 Oct 2024 04:29:31 GMT; Max-Age=14400; SameSite=None; Secure
Server-Timing	ak_p; desc="1730248171561_400321171_440942264_44_14368_4_8_-";dur=1

Analysis

HTTP redirects to HTTPS

Good. This plaintext HTTP server redirects to HTTPS.

HTTP (443)

To observe your HTTPS implementation, we submit a request to the homepage of your site on port 443, follow all redirections (even when they take us to other domain names), and record the returned HTTP headers. We use the most recent set of headers returned from the tested hostname for further tests such as HSTS and HPKP.

Test passed

Everything seems to be well configured. Well done.

URL: https://mailchimp.com/

1

https://mailchimp.com/

HTTP/1.1 200 OK

Content-Type	text/html; charset=UTF-8
X-UA-Compatible	IE=edge,chrome=1
X-Plums-Vary	Accept-Encoding, Accept-Language, Cookie
X-Frame-Options	SAMEORIGIN
Cache-Control	max-age=600, private, must-revalidate
X-EdgeConnect-MidMile-RTT	0
X-EdgeConnect-Origin-MEX-Latency	422
X-Akamai-Transformed	9 - 0 pmb=mTOE,1mRUM,2
Date	Wed, 30 Oct 2024 00:29:31 GMT
Transfer-Encoding	chunked
Connection	keep-alive
Vary	Accept-Encoding
Connection	Transfer-Encoding
Server-Timing	cdn-cache; desc=HIT
Server-Timing	edge; dur=1
Set-Cookie	_abck=AE442B24F47B43F73F3292AF95354F40~-1~YAAQk2rcF9mmAtSSAQAAVOHT2gyh0GmDB/qJjGLsi+5dLF6PcKTBE2E8AYWU6G0atSFa94a2jgXQcA7O5Eox6x9sNVZ2oROQL01WpcAKk2EWDKQI98QBQfUv6nSIFfqV74geIJxQMqm4Fz9OCSzMCk6M90b1lZsRIQFiTrowzja9ue7l65f3PeRogJKA9gWcfZw3i4qcDyysmkXQAOZHC4OsWh9Zr8dnAihz01tlXnlCmU3mulkwGmJ7ulM2aaKLxZ/cAUFn9ByqGQzeiULWjUcNB/d62h7sY26gmETl8++BjUl5u6FkE12WyKTXMWI+arq0/KMz94NMS/4Y1OxtuEHMiOFBknFt1I27VaGrKkuPYfx5jfC7crnzMxomrtJJR7oKr/fNkftQB2/4a6KBzSsyMEpRVrg5A3O9CAMKieg=~-1~-1~-1; Domain=.mailchimp.com; Path=/; Expires=Thu, 30 Oct 2025 00:29:31 GMT; Max-Age=31536000; SameSite=None; Secure
Set-Cookie	bm_sz=C2999A5B6C29B5ECC90B7E7022B6D23D~YAAQk2rcF9qmAtSSAQAAVOHT2hmHppSI3y34ISFLgRQ2qqVYP0CUr9/a2SAIvdK5xBm233UNd6FMxhJE9oQ+xhiJk1je6JYcvL+uC1ldkDg4C8paVQAz6w6/InJFT/9AJv+0gnlKriefpDOYRHgoXTRWCNp4F1U+ztlWZ+qnWvIqzLcpPpvd1KEuAwZa8mCNmb7VqUwo6EfmCTCYgsSrBjlZQdpNWDTMVDuf04KoeUMSwKEvrBcL7UmYKQX+O9/05173FXcpKSTbqwYtsvcYRkvZd9oGaSiZfKPH9yhC8q9kDqR0FPuXZsntzQhRZya6ymqpzqlK+UYk1B0tzH2SvTXv1uSQCIlMf1I+NOsNwvMIBrEvisiES7Q6vAmEwgQi2bxCEAH8~4342322~4274486; Domain=.mailchimp.com; Path=/; Expires=Wed, 30 Oct 2024 04:29:31 GMT; Max-Age=14400; SameSite=None; Secure
Server-Timing	ak_p; desc="1730248171824_400321171_440943550_47_13175_4_9_-";dur=1

URL: https://www.mailchimp.com/

1

https://www.mailchimp.com/

HTTP/1.1 301 Moved Permanently

Server	AkamaiGHost
Content-Length	0
Location	https://mailchimp.com/
Cache-Control	max-age=60
Expires	Wed, 30 Oct 2024 00:30:31 GMT
Date	Wed, 30 Oct 2024 00:29:31 GMT
Connection	keep-alive
Set-Cookie	_abck=AE77414E1D26E4025CCC0039C78121C4~-1~YAAQjWrcF4Ee7IiSAQAAseHT2gwsFUUnTOsjwfJTbkhms3Dbuj9kx9Z19b5qAOdyYMi+l9Nz/XmX63ViH8+WCwjVFNqWEJrnarERw9zKmkNWRfcsxC3xFAnN8gg0EmOTyHtBGaTFll43slMb/nAa0tqvfZd7iXwt9CRNidpMdua3B5K8XCOgghamlOqK/Gwbd7AyYfBF6kHcqeYBXoZZ+f5GKkwwIype7vpHas6y0VBQ4tLEQKifM5POiRVshTL/xX32v3WILdqP1+yOjczc5ZK7Q1fKrfbPrcEBRpv8wUcvPYV9r3D72wYgheUJKMPq8S3t3y342RC6FgYTuINR80SjK04U3QQV5bJL/TFE0OHHOX1RI39ocRBjh0XLMjrF2UffEpxRrVBHfisdij4nxwIigoCzsGgZFZJlKB/gBn8=~-1~-1~-1; Domain=.mailchimp.com; Path=/; Expires=Thu, 30 Oct 2025 00:29:31 GMT; Max-Age=31536000; SameSite=None; Secure
Set-Cookie	bm_sz=9AE46DE7CEF4EE860EBE05C3FDE5866E~YAAQjWrcF4Ie7IiSAQAAseHT2hkXN42ZaIIUPoYu0vkcZlu8ZpOuRPp3gvFGiuUSnKa9vu/M4uUFd+nnlxOPS1mhMzVDobggcSYoY/0MsDiFWk4hcnXk/LfJenG1tjsSArVO1N5peEaMiRqyFF69avHvcSkyu5w9RMxfK6py5aN95QpL4kZ9deWGLkmV474DKe4I0EXftJBd1kvmm7+5jaKHHiwI3ubfzRTAZG52/TkP284zsbzEukmU/1G/2OopHkH/k6ygFeCzSwr2ZTb5Fk8gg1SLXzqw9di1+mX1ZMHTyI/bDUSSr+ozjaiEqIbJjkFCUNmGSGHNNbAHl7akcKiB/eebVUZ30jl6F50vibhvkM3BsWt8uT3psQax3d9I4bLbDXLI~3291203~3682372; Domain=.mailchimp.com; Path=/; Expires=Wed, 30 Oct 2024 04:29:31 GMT; Max-Age=14400; SameSite=None; Secure

2

https://mailchimp.com/

HTTP/1.1 200 OK

Content-Type	text/html; charset=UTF-8
X-UA-Compatible	IE=edge,chrome=1
X-Plums-Vary	Accept-Encoding, Accept-Language, Cookie
X-Frame-Options	SAMEORIGIN
Cache-Control	max-age=600, private, must-revalidate
X-EdgeConnect-MidMile-RTT	0
X-EdgeConnect-Origin-MEX-Latency	422
X-Akamai-Transformed	9 - 0 pmb=mTOE,1mRUM,2
Date	Wed, 30 Oct 2024 00:29:32 GMT
Transfer-Encoding	chunked
Connection	keep-alive
Vary	Accept-Encoding
Connection	Transfer-Encoding
Server-Timing	cdn-cache; desc=HIT
Server-Timing	edge; dur=1
Set-Cookie	bm_sz=9AE46DE7CEF4EE860EBE05C3FDE5866E~YAAQk2rcF/ymAtSSAQAAEeLT2hnHSjOO4Z2GLZ5AZ38WfjpqJxo2lngslm+ZN/lF+9rdIWnVlmp0m7rTOFjg/KyqcGBsU1d5851s7NQlzSCkFQ6gjSq0ygvhXY4juIKm9+3lQ9p+UyK8gU3EFvv0SzzuS6BfdcRerwN0RBOQOm3FJtDwnWX19PanvUdc7eYLqkciCTAhbF2+tQ1kQ0DBeKgGJdYSXY1lsWwrbh6VHRiTamkSmRtuNMikRRY1xxeCiCahOyM7JfQrE69RoEARCpk1SFWNi2PqzxwWA8N92wWPq5bkPbHB3P3G5WPzuHaYdtWTtXsKruqaW779YEd18ms2wSgEjGqJ7/g5vxM6ThRGd65Gps7JJDFii2EyXil31mPbZxsWvJZS2+U=~3291203~3682372; Domain=.mailchimp.com; Path=/; Expires=Wed, 30 Oct 2024 04:29:31 GMT; Max-Age=14399; SameSite=None; Secure
Server-Timing	ak_p; desc="1730248171967_400321171_440944250_49_14762_3_5_-";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: mailchimp.com (23.13.176.191)

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)
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)

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.

Only strong suites supported

Excellent. This server supports only strong cipher suites, which use strong authenticated encryption and provide forward secrecy.

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.mailchimp.com (23.13.180.236)

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)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca9 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC secp256r1 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC secp256r1 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc02c Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC secp256r1 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02b Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC secp256r1 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC 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)

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.

Only strong suites supported

Excellent. This server supports only strong cipher suites, which use strong authenticated encryption and provide forward secrecy.

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

Leaf certificate

mailchimp.com
Issuer: DigiCert
Not Before: 16 Apr 2024 00:00:00 UTC
Not After: 19 Apr 2025 23:59:59 UTC (expires in 5 months 20 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
View details

Names	mailchimp.com
Subject DN	CN=mailchimp.com, O=THE ROCKET SCIENCE GROUP LLC, L=Atlanta, ST=Georgia, C=US
Subject Key Identifier	5f9a0298281368e3605422ea7c465a9d55f0004c
Serial	e0c922a5ebcfb8fb53e476c173c0424
Not Before	16 Apr 2024 00:00:00 UTC
Not After	19 Apr 2025 23:59:59 UTC
Validity period	369 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=DigiCert TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:b76ba2eaa8aa848c79eab4da0f98b2c59576b9f4
Parent Certificate	http://cacerts.digicert.com/DigiCertTLSRSASHA2562020CA1-1.crt
CRL	http://crl3.digicert.com/DigiCertTLSRSASHA2562020CA1-4.crl http://crl4.digicert.com/DigiCertTLSRSASHA2562020CA1-4.crl
OCSP	http://ocsp.digicert.com
Certificate Transparency
Signed Certificate Timestamps	16 Apr 2024 01:11:46 UTC \| Google 'Argon2025h1' log \| Qualified 16 Apr 2024 01:11:46 UTC \| DigiCert Yeti2025 Log \| Qualified 16 Apr 2024 01:11:46 UTC \| DigiCert Nessie2025 Log \| Qualified
Fingerprints
SHA1	ef747c44066d45a70072fb48e4360d9e42556621
SHA256	e3686a923032d4ee6011298dc23a16ede4f680967a44fed98ec0e13149ac1677
SPKI SHA256	4a355c154bc8728b137cba065b678b78b5fd2516efa20fea80184ebbb1ad4ffd

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

mailchimp.com | e3686a9
Not After: 19 Apr 2025 23:59:59 UTC (expires in 5 months 20 days)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Names	mailchimp.com
Subject DN	CN=mailchimp.com, O=THE ROCKET SCIENCE GROUP LLC, L=Atlanta, ST=Georgia, C=US
Subject Key Identifier	5f9a0298281368e3605422ea7c465a9d55f0004c
Serial	e0c922a5ebcfb8fb53e476c173c0424
Not Before	16 Apr 2024 00:00:00 UTC
Not After	19 Apr 2025 23:59:59 UTC
Validity period	369 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=DigiCert TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:b76ba2eaa8aa848c79eab4da0f98b2c59576b9f4
Parent Certificate	http://cacerts.digicert.com/DigiCertTLSRSASHA2562020CA1-1.crt
CRL	http://crl3.digicert.com/DigiCertTLSRSASHA2562020CA1-4.crl http://crl4.digicert.com/DigiCertTLSRSASHA2562020CA1-4.crl
OCSP	http://ocsp.digicert.com
Certificate Transparency
Signed Certificate Timestamps	16 Apr 2024 01:11:46 UTC \| Google 'Argon2025h1' log \| Qualified 16 Apr 2024 01:11:46 UTC \| DigiCert Yeti2025 Log \| Qualified 16 Apr 2024 01:11:46 UTC \| DigiCert Nessie2025 Log \| Qualified
Fingerprints
SHA1	ef747c44066d45a70072fb48e4360d9e42556621
SHA256	e3686a923032d4ee6011298dc23a16ede4f680967a44fed98ec0e13149ac1677
SPKI SHA256	4a355c154bc8728b137cba065b678b78b5fd2516efa20fea80184ebbb1ad4ffd

Intermediate certificate

DigiCert TLS RSA SHA256 2020 CA1 | 52274c5
Not After: 13 Apr 2031 23:59:59 UTC (expires in 6 years 5 months)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Subject DN	CN=DigiCert TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US
Subject Key Identifier	b76ba2eaa8aa848c79eab4da0f98b2c59576b9f4
Serial	6d8d904d5584346f68a2fa754227ec4
Not Before	14 Apr 2021 00:00:00 UTC
Not After	13 Apr 2031 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
OCSP	http://ocsp.digicert.com
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	1c58a3a8518e8759bf075b76b750d4f2df264fcd
SHA256	52274c57ce4dee3b49db7a7ff708c040f771898b3be88725a86fb4430182fe14
SPKI SHA256	450799901e36ce751fb0320815621189811c2a5ee71f0345c160ab9cc3096d57

Root certificate

DigiCert Global Root CA | 4348a0e
Not After: 10 Nov 2031 00:00:00 UTC (expires in 7 years 10 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.

Certificate: www.mailchimp.com

Leaf certificate

wildcardsan2.mailchimp.com
Issuer: DigiCert
Not Before: 25 Apr 2024 00:00:00 UTC
Not After: 26 Apr 2025 23:59:59 UTC (expires in 5 months 27 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
View details

Names	wildcardsan2.mailchimp.com .admin.mailchimp.com .api.mailchimp.com .campaign-archive.com .campaign-archive1.com .campaign-archive2.com .chimpstatic.com .forward-to-friend.com .forward-to-friend1.com .forward-to-friend2.com .list-manage.com .list-manage1.com .list-manage2.com .mailchimp.com .mandrill.com .mccrowdsource.com .parsimony-target.mailchimp.com .partner-api.mailchimp.com .partners.mailchimp.com *.vip-reports.net chimpstatic.com eep.io eepurl.com mailchimp.com thenomdepot.com vip-reports.net
Subject DN	CN=wildcardsan2.mailchimp.com, O=The Rocket Science Group LLC, L=Atlanta, ST=Georgia, C=US
Subject Key Identifier	2b4e7202a60dfab08302a17e08db8d9e19a616dc
Serial	84ee90709675b311a75eaafbb840bf2
Not Before	25 Apr 2024 00:00:00 UTC
Not After	26 Apr 2025 23:59:59 UTC
Validity period	367 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=DigiCert TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:b76ba2eaa8aa848c79eab4da0f98b2c59576b9f4
Parent Certificate	http://cacerts.digicert.com/DigiCertTLSRSASHA2562020CA1-1.crt
CRL	http://crl3.digicert.com/DigiCertTLSRSASHA2562020CA1-4.crl http://crl4.digicert.com/DigiCertTLSRSASHA2562020CA1-4.crl
OCSP	http://ocsp.digicert.com
Certificate Transparency
Signed Certificate Timestamps	25 Apr 2024 20:44:06 UTC \| Google 'Argon2025h1' log \| Qualified 25 Apr 2024 20:44:06 UTC \| DigiCert Yeti2025 Log \| Qualified 25 Apr 2024 20:44:06 UTC \| DigiCert Nessie2025 Log \| Qualified
Fingerprints
SHA1	35a7eb07f6586167463290be11c85e48a2518abb
SHA256	ba32370674d465b409bdcd78a79c82fd8d99b01a5da164f5919fff22ca50961b
SPKI SHA256	f2eb402b1724735c5ba986b9385d36353913fcf7a3bbef8081f85cad9db2b7d0

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

wildcardsan2.mailchimp.com | ba32370
Not After: 26 Apr 2025 23:59:59 UTC (expires in 5 months 27 days)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Names	wildcardsan2.mailchimp.com .admin.mailchimp.com .api.mailchimp.com .campaign-archive.com .campaign-archive1.com .campaign-archive2.com .chimpstatic.com .forward-to-friend.com .forward-to-friend1.com .forward-to-friend2.com .list-manage.com .list-manage1.com .list-manage2.com .mailchimp.com .mandrill.com .mccrowdsource.com .parsimony-target.mailchimp.com .partner-api.mailchimp.com .partners.mailchimp.com *.vip-reports.net chimpstatic.com eep.io eepurl.com mailchimp.com thenomdepot.com vip-reports.net
Subject DN	CN=wildcardsan2.mailchimp.com, O=The Rocket Science Group LLC, L=Atlanta, ST=Georgia, C=US
Subject Key Identifier	2b4e7202a60dfab08302a17e08db8d9e19a616dc
Serial	84ee90709675b311a75eaafbb840bf2
Not Before	25 Apr 2024 00:00:00 UTC
Not After	26 Apr 2025 23:59:59 UTC
Validity period	367 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=DigiCert TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:b76ba2eaa8aa848c79eab4da0f98b2c59576b9f4
Parent Certificate	http://cacerts.digicert.com/DigiCertTLSRSASHA2562020CA1-1.crt
CRL	http://crl3.digicert.com/DigiCertTLSRSASHA2562020CA1-4.crl http://crl4.digicert.com/DigiCertTLSRSASHA2562020CA1-4.crl
OCSP	http://ocsp.digicert.com
Certificate Transparency
Signed Certificate Timestamps	25 Apr 2024 20:44:06 UTC \| Google 'Argon2025h1' log \| Qualified 25 Apr 2024 20:44:06 UTC \| DigiCert Yeti2025 Log \| Qualified 25 Apr 2024 20:44:06 UTC \| DigiCert Nessie2025 Log \| Qualified
Fingerprints
SHA1	35a7eb07f6586167463290be11c85e48a2518abb
SHA256	ba32370674d465b409bdcd78a79c82fd8d99b01a5da164f5919fff22ca50961b
SPKI SHA256	f2eb402b1724735c5ba986b9385d36353913fcf7a3bbef8081f85cad9db2b7d0

Intermediate certificate

DigiCert TLS RSA SHA256 2020 CA1 | 52274c5
Not After: 13 Apr 2031 23:59:59 UTC (expires in 6 years 5 months)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Subject DN	CN=DigiCert TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US
Subject Key Identifier	b76ba2eaa8aa848c79eab4da0f98b2c59576b9f4
Serial	6d8d904d5584346f68a2fa754227ec4
Not Before	14 Apr 2021 00:00:00 UTC
Not After	13 Apr 2031 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
OCSP	http://ocsp.digicert.com
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	1c58a3a8518e8759bf075b76b750d4f2df264fcd
SHA256	52274c57ce4dee3b49db7a7ff708c040f771898b3be88725a86fb4430182fe14
SPKI SHA256	450799901e36ce751fb0320815621189811c2a5ee71f0345c160ab9cc3096d57

Root certificate

DigiCert Global Root CA | 4348a0e
Not After: 10 Nov 2031 00:00:00 UTC (expires in 7 years 10 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.

Certificate: www.mailchimp.com

Leaf certificate

wildcardsan2.mailchimp.com
Issuer: DigiCert
Not Before: 25 Apr 2024 00:00:00 UTC
Not After: 26 Apr 2025 23:59:59 UTC (expires in 5 months 27 days)
Key: EC 256 bits
Signature: SHA256withRSA
View details

Names	wildcardsan2.mailchimp.com .admin.mailchimp.com .api.mailchimp.com .campaign-archive.com .campaign-archive1.com .campaign-archive2.com .chimpstatic.com .forward-to-friend.com .forward-to-friend1.com .forward-to-friend2.com .list-manage.com .list-manage1.com .list-manage2.com .mailchimp.com .mandrill.com .mccrowdsource.com .parsimony-target.mailchimp.com .partner-api.mailchimp.com .partners.mailchimp.com *.vip-reports.net chimpstatic.com eep.io eepurl.com mailchimp.com thenomdepot.com vip-reports.net
Subject DN	CN=wildcardsan2.mailchimp.com, O=The Rocket Science Group LLC, L=Atlanta, ST=Georgia, C=US
Subject Key Identifier	c3067df776b5974e67161e2f893dbb63dac98ed0
Serial	c70ec9149c402d2e06c754064472138
Not Before	25 Apr 2024 00:00:00 UTC
Not After	26 Apr 2025 23:59:59 UTC
Validity period	367 days
Key Usage	digitalSignature, keyAgreement
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=DigiCert TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:b76ba2eaa8aa848c79eab4da0f98b2c59576b9f4
Parent Certificate	http://cacerts.digicert.com/DigiCertTLSRSASHA2562020CA1-1.crt
CRL	http://crl3.digicert.com/DigiCertTLSRSASHA2562020CA1-4.crl http://crl4.digicert.com/DigiCertTLSRSASHA2562020CA1-4.crl
OCSP	http://ocsp.digicert.com
Certificate Transparency
Signed Certificate Timestamps	25 Apr 2024 21:34:48 UTC \| Google 'Xenon2025h1' log \| Qualified 25 Apr 2024 21:34:48 UTC \| DigiCert Yeti2025 Log \| Qualified 25 Apr 2024 21:34:48 UTC \| DigiCert Nessie2025 Log \| Qualified
Fingerprints
SHA1	c2c072e9fc1673383fb59c451dc9d6a19a59f52d
SHA256	56c2ec7eb67e4d1f476e3f0520786465b780d7d2ef41606eb4755ba257f773e0
SPKI SHA256	2d9eeab11a90825b8cc398b18323bdf91854dd511fde361dc6be95da89d16aa9

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

wildcardsan2.mailchimp.com | 56c2ec7
Not After: 26 Apr 2025 23:59:59 UTC (expires in 5 months 27 days)
Authentication: EC 256 bits (SHA256withRSA)
View details

Names	wildcardsan2.mailchimp.com .admin.mailchimp.com .api.mailchimp.com .campaign-archive.com .campaign-archive1.com .campaign-archive2.com .chimpstatic.com .forward-to-friend.com .forward-to-friend1.com .forward-to-friend2.com .list-manage.com .list-manage1.com .list-manage2.com .mailchimp.com .mandrill.com .mccrowdsource.com .parsimony-target.mailchimp.com .partner-api.mailchimp.com .partners.mailchimp.com *.vip-reports.net chimpstatic.com eep.io eepurl.com mailchimp.com thenomdepot.com vip-reports.net
Subject DN	CN=wildcardsan2.mailchimp.com, O=The Rocket Science Group LLC, L=Atlanta, ST=Georgia, C=US
Subject Key Identifier	c3067df776b5974e67161e2f893dbb63dac98ed0
Serial	c70ec9149c402d2e06c754064472138
Not Before	25 Apr 2024 00:00:00 UTC
Not After	26 Apr 2025 23:59:59 UTC
Validity period	367 days
Key Usage	digitalSignature, keyAgreement
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=DigiCert TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:b76ba2eaa8aa848c79eab4da0f98b2c59576b9f4
Parent Certificate	http://cacerts.digicert.com/DigiCertTLSRSASHA2562020CA1-1.crt
CRL	http://crl3.digicert.com/DigiCertTLSRSASHA2562020CA1-4.crl http://crl4.digicert.com/DigiCertTLSRSASHA2562020CA1-4.crl
OCSP	http://ocsp.digicert.com
Certificate Transparency
Signed Certificate Timestamps	25 Apr 2024 21:34:48 UTC \| Google 'Xenon2025h1' log \| Qualified 25 Apr 2024 21:34:48 UTC \| DigiCert Yeti2025 Log \| Qualified 25 Apr 2024 21:34:48 UTC \| DigiCert Nessie2025 Log \| Qualified
Fingerprints
SHA1	c2c072e9fc1673383fb59c451dc9d6a19a59f52d
SHA256	56c2ec7eb67e4d1f476e3f0520786465b780d7d2ef41606eb4755ba257f773e0
SPKI SHA256	2d9eeab11a90825b8cc398b18323bdf91854dd511fde361dc6be95da89d16aa9

Intermediate certificate

DigiCert TLS RSA SHA256 2020 CA1 | 52274c5
Not After: 13 Apr 2031 23:59:59 UTC (expires in 6 years 5 months)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Subject DN	CN=DigiCert TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US
Subject Key Identifier	b76ba2eaa8aa848c79eab4da0f98b2c59576b9f4
Serial	6d8d904d5584346f68a2fa754227ec4
Not Before	14 Apr 2021 00:00:00 UTC
Not After	13 Apr 2031 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
OCSP	http://ocsp.digicert.com
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	1c58a3a8518e8759bf075b76b750d4f2df264fcd
SHA256	52274c57ce4dee3b49db7a7ff708c040f771898b3be88725a86fb4430182fe14
SPKI SHA256	450799901e36ce751fb0320815621189811c2a5ee71f0345c160ab9cc3096d57

Root certificate

DigiCert Global Root CA | 4348a0e
Not After: 10 Nov 2031 00:00:00 UTC (expires in 7 years 10 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.

DANE (443)

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

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

Cookies

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

Test passed

Everything seems to be well configured. Well done.

HTTP Cookie: bm_sz

Cookie value. As far as the cookie RFC is concerned, the value is an opaque string which only the application should interpret.Value	9AE46DE7CEF4EE860EBE05C3FDE5866E~YAAQk2rcF/ymAtSSAQAAEeLT2hnHSjOO4Z2GLZ5AZ38WfjpqJxo2lngslm+ZN/lF+9rdIWnVlmp0m7rTOFjg/KyqcGBsU1d5851s7NQlzSCkFQ6gjSq0ygvhXY4juIKm9+3lQ9p+UyK8gU3EFvv0SzzuS6BfdcRerwN0RBOQOm3FJtDwnWX19PanvUdc7eYLqkciCTAhbF2+tQ1kQ0DBeKgGJdYSXY1lsWwrbh6VHRiTamkSmRtuNMikRRY1xxeCiCahOyM7JfQrE69RoEARCpk1SFWNi2PqzxwWA8N92wWPq5bkPbHB3P3G5WPzuHaYdtWTtXsKruqaW779YEd18ms2wSgEjGqJ7/g5vxM6ThRGd65Gps7JJDFii2EyXil31mPbZxsWvJZS2+U=~3291203~3682372
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	mailchimp.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 30 04:29:32 UTC 2024 (3 hours 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.

Analysis

All cookies are secure

Great. All observed cookies are marked secure.

HTML Content

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

Test passed

Everything seems to be well configured. Well done.

Encryption of Embedded Resources

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

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

Status	Link
Encrypted	https://uxfabric.app.intuit.com/...com-appfabric-webapp
Encrypted	https://mailchimp.com/...3550dc3ee2ecf8c9b.js
Encrypted	https://cdn.optimizely.com/js/8896740779.js
Encrypted	https://cdn.intellimize.co/...snippet/117482039.js
Encrypted	https://mailchimp.com/ex.js
Encrypted	https://mailchimp.com/.../index.b4533b48.1.js
Encrypted	https://static.ada.support/embed2.js

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

Status	Link
Encrypted	https://mailchimp.com/...ommon.a1ec8ca2.1.css
Encrypted	https://mailchimp.com/...tical.f2a1ca60.1.css
Encrypted	https://mailchimp.com/...-less.f421beb2.1.css
Encrypted	https://mailchimp.com/...-less.037b82f0.1.css

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

Encryption of Outbound Links

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

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

Status	Link
Encrypted	https://www.intuit.com/
Encrypted	https://turbotax.intuit.com/
Encrypted	https://www.creditkarma.com/
Encrypted	https://quickbooks.intuit.com/

HTTP Strict Transport Security

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

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

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

7 script(s)
3 out of 7 are secure

https://uxfabric.app.intuit.com/...com-appfabric-webapp

https://cdn.optimizely.com/js/8896740779.js

https://cdn.intellimize.co/...snippet/117482039.js

https://static.ada.support/embed2.js

View all

Status	Link
Remote	https://uxfabric.app.intuit.com/v3/appfabric-integration/lib/dotcom-appfabric-webapp?appfabric_version=5.60.1
Local	/release/1.1.12cd6901f3c9137ef66c019ae3fd192a8d2086806/js-src/cookie-preferences-manager.aeb3550dc3ee2ecf8c9b.js
Remote	https://cdn.optimizely.com/js/8896740779.js
Remote	https://cdn.intellimize.co/snippet/117482039.js
Local	/ex.js
Local	/release/plums/cxp/js/index.b4533b48.1.js
Remote	https://static.ada.support/embed2.js

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

Status	Link
Local	/release/plums/cxp/css/common.a1ec8ca2.1.css
Local	/release/plums/cxp/css/critical.f2a1ca60.1.css
Local	/release/plums/cxp/css/presenters/modules/p23_flexible_highlight-less.f421beb2.1.css
Local	/release/plums/cxp/css/page_specific/p23-less.037b82f0.1.css

Analysis

SRI required

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

Expect CT

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

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

Analysis

Deploy Expect-CT to enable reporting

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

Frame Options

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

Test passed

Everything seems to be well configured. Well done.

Analysis

Header information

Name: X-Frame-Options

Value: SAMEORIGIN

Framing allowed from the same origin only

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

XSS Protection

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

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

mailchimp.com

Domain Name System

Email

WWW

Domain Registration

Registration Data Access Protocol (RDAP)

WHOIS

DNS Zone

Nameserver Names

Nameserver Addresses

Start of Authority (SOA) Record

Analysis

Backing DNS Queries

DNS Records

DNS Records

Backing DNS Queries

DNSSEC

Useful DNSSEC Tools

Certification Authority Authorization

CAA Policy Information

Analysis

Email (SMTP)

Analysis

Email TLS (SMTP)

TLS Configuration: mx2.intuit.iphmx.com (68.232.135.147) Cached

Analysis

TLS Configuration: mx2.intuit.iphmx.com (68.232.143.160) Cached

Analysis

TLS Configuration: mx2.intuit.iphmx.com (207.54.92.90) Cached

Analysis

TLS Configuration: mx2.intuit.iphmx.com (68.232.146.251) Cached

Analysis

TLS Configuration: mx2.intuit.iphmx.com (216.71.141.217) Cached

Analysis

TLS Configuration: mx2.intuit.iphmx.com (216.71.141.216) Cached

Analysis

TLS Configuration: mx2.intuit.iphmx.com (68.232.146.61) Cached

Analysis

TLS Configuration: mx2.intuit.iphmx.com (216.71.138.62) Cached

Analysis

TLS Configuration: mx2.intuit.iphmx.com (207.54.92.93) Cached

Analysis

TLS Configuration: mx2.intuit.iphmx.com (68.232.135.250) Cached

Analysis

TLS Configuration: mx2.intuit.iphmx.com (216.71.138.61) Cached

Analysis

TLS Configuration: mx2.intuit.iphmx.com (68.232.148.142) Cached

Analysis

TLS Configuration: mx1.intuit.iphmx.com (68.232.146.251) Cached

Analysis

TLS Configuration: mx1.intuit.iphmx.com (68.232.135.250) Cached

Analysis

TLS Configuration: mx1.intuit.iphmx.com (68.232.148.142) Cached

Analysis

TLS Configuration: mx1.intuit.iphmx.com (216.71.141.217) Cached

Analysis

TLS Configuration: mx1.intuit.iphmx.com (68.232.146.61) Cached

Analysis

TLS Configuration: mx1.intuit.iphmx.com (207.54.92.90) Cached

Analysis

TLS Configuration: mx1.intuit.iphmx.com (216.71.138.61) Cached

Analysis

TLS Configuration: mx1.intuit.iphmx.com (216.71.141.216) Cached

Analysis

TLS Configuration: mx1.intuit.iphmx.com (68.232.135.147) Cached

Analysis

TLS Configuration: mx1.intuit.iphmx.com (216.71.138.62) Cached

Analysis

TLS Configuration: mx1.intuit.iphmx.com (207.54.92.93) Cached

Analysis

TLS Configuration: mx1.intuit.iphmx.com (68.232.143.160) Cached

Analysis

Email Certificates (SMTP)

Certificate #1 Cached

Analysis

Certificate Chain

Analysis

Email DANE (SMTP)

SPF