Hardenize has joined Red Sift! Find out more in our blog post.
Hardenize Logo

Public Report | mailjet.com

TEST ANOTHER

mailjet.com

29 Apr 2025 13:29 UTC

Domain Name System

DNS Zonegood
DNS Recordserror
DNSSECneutral
CAAneutral

Email

Mail serversgood
TLSgood
Certificatesgood
MTA-STSneutral
TLS-RPTneutral
DANEneutral
SPFgood
DMARCerror

WWW

HTTP (80)good
HTTPS (443)good
TLSgood
Certificatesgood
Cookiesgood
HTML Contentgood
Strict Transport Securitygood
Content Security Policygood
Subresource Integritygood
Frame Optionsgood
XSS Protectionwarning
Content Type Optionsgood
Web Security Overview
Supported and well configured
HTTPS

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

For all sites VERY IMPORTANT medium EFFORT
Supported and well configured
HTTPS Redirection

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

For all sites VERY IMPORTANT low EFFORT
Supported and well configured
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
Supported and well configured
HSTS Preloaded

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

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

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

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

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

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

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

For important sites IMPORTANT low EFFORT
Error
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.
There are issues with this site's DMARC configuration.

For important sites IMPORTANT low EFFORT

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
ns0.mljt.tech. PRIMARY
104.199.73.221 		The server is online. Name resolves to an IPv4 address. Name doesn't resolve to an IPv6 address. SOA REFERRAL NS
ns1.mljt.tech.
35.238.164.182 		The server is online. Name resolves to an IPv4 address. Name doesn't resolve to an IPv6 address. REFERRAL NS
ns2.mljt.tech.
212.47.237.20 		The server is online. Name resolves to an IPv4 address. Name doesn't resolve to an IPv6 address. REFERRAL NS

Nameserver Addresses

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

Nameserver Operational Authoritative Recursive UDP TCP Sources Payload Size
104.199.73.221 PRIMARY
ns0.mljt.tech.
PTR: ns0.mljt.tech. 		The server appears to be online. Nameserver provides authoritative responses Nameserver doesn't provide recursive service Nameserver responds to UDP queries Nameserver responds to TCP queries NAME 1232
212.47.237.20
ns2.mljt.tech.
PTR: ns2.mljt.tech. 		The server appears to be online. Nameserver provides authoritative responses Nameserver doesn't provide recursive service Nameserver responds to UDP queries Nameserver responds to TCP queries NAME 1232
35.238.164.182
ns1.mljt.tech.
PTR: ns1.mljt.tech. 		The server appears to be online. Nameserver provides authoritative responses Nameserver doesn't provide recursive service Nameserver responds to UDP queries Nameserver responds to TCP queries NAME 1232

Start of Authority (SOA) Record

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

The domain name of the primary nameserver for the zone. Also known as MNAME.Primary nameserver ns0.mljt.tech.
Email address of the persons responsible for this zone. Also known as RNAME.Admin email abuse.mailjet.com.
Zone serial or version number.Serial number 2019223545
The length of time secondary nameservers should wait before querying the primary for changes.Refresh interval 14,400 seconds (about 4 hours)
The length of time secondary nameservers should wait before querying an unresponsive primary again.Retry interval 900 seconds (about 15 minutes)
The length of time after which secondary nameservers should stop responding to queries for a zone, assuming no updates were obtained from the primary.Expire interval 604,800 seconds (about 7 days)
TTL for purposes of negative response caching. Negative cache TTL 180 seconds (about 3 minutes)
Time To Live (TTL) indicates for how long a record remains valid. SOA record TTL 7,200 seconds (about 2 hours)

Analysis

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

Backing DNS Queries

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

ID Server Transport Question Name Type Status

DNS Records

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

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

DNS Records

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

Name TTL Type Data
mailjet.com.     60 A 147.75.40.150            
www.mailjet.com.     60 CNAME mailjet.netlifyglobalcdn.com.            
mailjet.netlifyglobalcdn.com.     300 A 15.197.167.90            
mailjet.netlifyglobalcdn.com.     300 A 3.33.186.135            
mailjet.netlifyglobalcdn.com.     20 AAAA 2600:1f16:1a4:a002:0:0:0:1f4            
mailjet.netlifyglobalcdn.com.     20 AAAA 2600:1f16:1a4:a001:0:0:0:1f4            
mailjet.com.     7200 DNSKEY 257 3 13 77XSXlHZO2J/FCFMURrUwom5DF/Ed+FKW//wnvBl2B3hnnRaXjrxNJMt06/31+aXY6iPeUkZVyXSddFvVsd4iQ==            
mailjet.com.     7200 DNSKEY 256 3 13 xECkOvIgbJcDEo2ChACy4W3IGfGAPk2yX3N7SE70tE/yKtE1wFNHelfd/jig+hcIlflR43lG7WIL5p7M70sttA==            
mailjet.com.     60 MX 0 mailjet-com.mail.protection.outlook.com.            
mailjet.com.     7200 NS ns2.mljt.tech.            
mailjet.com.     7200 NS ns0.mljt.tech.            
mailjet.com.     7200 NS ns1.mljt.tech.            
mailjet.com.     7200 SOA ns0.mljt.tech. abuse.mailjet.com. 2019223545 14400 900 604800 180            
_xmpp-server._tcp.mailjet.com.     7200 SRV 20 0 5269 xmpp-server4.l.google.com.            
_xmpp-server._tcp.mailjet.com.     7200 SRV 5 0 5269 xmpp-server.l.google.com.            
_xmpp-server._tcp.mailjet.com.     7200 SRV 20 0 5269 xmpp-server1.l.google.com.            
_xmpp-server._tcp.mailjet.com.     7200 SRV 20 0 5269 xmpp-server2.l.google.com.            
_xmpp-server._tcp.mailjet.com.     7200 SRV 20 0 5269 xmpp-server3.l.google.com.            
mailjet.com.     7200 TXT "pardot830283=160f36035bfbba957664c7476bfd671b41ad6be534e9aeafd49ae3c5ee68dcfa"            
mailjet.com.     7200 TXT "v=spf1 include:spf.mailjet.com include:aspmx.pardot.com include:mailgun.org include:spf.protection.outlook.com -all"            
mailjet.com.     7200 TXT "v=DMARC1; p=reject; sp=reject; pct=100; fo=1; adkim=r; aspf=r; rua=mailto:mailjet@dmarc.mailjet.tech; ruf=mailto:mailjet@dmarc.mailjet.tech"            
mailjet.com.     7200 TXT "A92908FF8D"            
mailjet.com.     7200 TXT "MS=ms67111241"            
mailjet.com.     7200 TXT "MS=ms78882229"            
mailjet.com.     7200 TXT "MS=ms90249674"            
mailjet.com.     7200 TXT "38r6l3fxh9zg2rn2fxmn6jdnz46p33my"            
mailjet.com.     7200 TXT "_woqrfcvxusfyyjwqzxgqp18q5bhet1b"            
mailjet.com.     7200 TXT "b1wvgkfvl4xsdsksh97lcj7c3j3vx3rc"            
mailjet.com.     7200 TXT "jjbq97v741t054z5d8mmypwfwvjpy5sq"            
mailjet.com.     7200 TXT "detectify-verification=58ab2ecefd6a8fced3ea405f3513cadf"            
mailjet.com.     7200 TXT "google-site-verification=JYc849ZiuN8hDIOVfNHpILrj4YHHdRodeoEHpTdznDo"            
mailjet.com.     7200 TXT "google-site-verification=NIwZYjCk3zPRJWXOoCOaNgGCRDIszz_e7vrDtl0bHtg"            
mailjet.com.     7200 TXT "google-site-verification=TBOvw7EGxhIf59OmIiWPa9S0V1PG4B-1TCrEYS1iSvQ"            
mailjet.com.     7200 TXT "google-site-verification=TYUL0nXfz8-kNX2DchqUZtaCBfbYNazyFbw2M-WS4SA"            
mailjet.com.     7200 TXT "google-site-verification=cOcuVXOqzRUJRxZ5Rr3wITXgaJqVXfQP_pwwWrs1QeQ"            
mailjet.com.     7200 TXT "google-site-verification=eOA4KDa6flW9B2s9_P_Fbn2N0nUkDn3hnrvbW88tsWU"            
mailjet.com.     7200 TXT "google-site-verification=fH820-W_oo2SOX5A-noteq0XsKFKvtOzNUZxUn28oYQ"            
mailjet.com.     7200 TXT "mgverify=7e50634a833722533888024ae60ce1fb2f6bf7e8b3e68dea174e8a078803a268"            
mailjet.com.     7200 TXT "mgverify=c2b25f5241de4cb58eaca68b4674bf6188a4bfd3d63511aad66350f48cf9057d"            
_dmarc.mailjet.com.     7200 TXT "v=DMARC1; p=reject; sp=reject; pct=100; fo=1; adkim=r; aspf=r; rua=mailto:w8fajs9t@ag.us.dmarcian.com,mailto:mailjet@dmarc.mailjet.tech; ruf=mailto:w8fajs9t@fr.us.dmarcian.com,mailto:mailjet@dmarc.mailjet.tech"            
_domainkey.mailjet.com.     7200 TXT "t=y; o=~;"            

Analysis

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

Error: Dangling DNS record: _xmpp-server._tcp.mailjet.com./SRV (destination: xmpp-server4.l.google.com.)

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

Error: Dangling DNS record: _xmpp-server._tcp.mailjet.com./SRV (destination: xmpp-server.l.google.com.)

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

Error: Dangling DNS record: _xmpp-server._tcp.mailjet.com./SRV (destination: xmpp-server1.l.google.com.)

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

Error: Dangling DNS record: _xmpp-server._tcp.mailjet.com./SRV (destination: xmpp-server2.l.google.com.)

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

Error: Dangling DNS record: _xmpp-server._tcp.mailjet.com./SRV (destination: xmpp-server3.l.google.com.)

Backing DNS Queries

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

ID Server Question Name Type Status

DNSSEC

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

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

Useful DNSSEC Tools

Certification Authority Authorization

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

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

Analysis

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

Email (SMTP)

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

Test passed
Everything seems to be well configured. Well done.
Server Preference Operational STARTTLS TLS PKI DNSSEC DANE
mailjet-com.mail.protection.outlook.com
52.101.68.10
PTR: mail-dbbpr03cu00102.inbound.protection.outlook.com		 0 
220 DB1PEPF000509E9.mail.protection.outlook.com Microsoft ESMTP MAIL Service ready at Tue, 29 Apr 2025 13:28:52 +0000 [08DD86FC11D4CF67]

EHLO outbound.hardenize.com
250-DB1PEPF000509E9.mail.protection.outlook.com Hello [172.99.67.55]
250-SIZE 157286400
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-STARTTLS
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250 SMTPUTF8

STARTTLS
220 2.0.0 SMTP server ready
Supports STARTTLS. Not supported. Not applicable,
requires TLS.

Analysis

Notice
Limited testing of third-party SMTP servers
We employ limited testing of third-party SMTP servers because they tend to be used by a great many domain names. Because we also continuously test a great many domain names, we want to avoid sending too many near-identical connections to these SMTP servers. It doesn't serve a practical purpose and also tends to get us on their bad side. TLS protocol testing, in particular, requires a lot of connections, which mean that we're often treated like spammers, even though we don't send any email. When testing third-party servers we may check only IP address per SMTP destination. When this is the case, the list of IP addresses shown here may not be complete. Further, in some situations with top services, we may show only the TLS configuration from a representative sample of their servers.
Notice
Some SMTP server assessments contain partial information
Comprehensive TLS assessments require many connections, which is exactly what many SMTP servers don't like. We implement a two-tier assessment approach. To give you some results as fast as possible, we perform shallow assessments that use only one connection per SMTP server. We then have a background process that performs complete assessments slowly, trying to accommodate each server individually. The results presented here contain partial information. If you come back later we may be able to provide complete assessment results.

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.

TLS Configuration: mailjet-com.mail.protection.outlook.com (52.101.68.10)

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

Analysis

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

Email Certificates (SMTP)

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

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

Certificate #1

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

Analysis

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

Certificate Chain

Leaf certificate
mail.protection.outlook.com | c6d2c97
Not After: 17 Sep 2025 23:59:59 UTC (expires in 4 months 19 days)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Intermediate certificate
DigiCert Cloud Services CA-1 | 5f88694
Not After: 24 Sep 2030 23:59:59 UTC (expires in 5 years 4 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Root certificate
DigiCert Global Root CA | 4348a0e
Not After: 10 Nov 2031 00:00:00 UTC (expires in 6 years 6 months)
Authentication: RSA 2048 bits (SHA1withRSA)
 View details

Analysis

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

Email DANE (SMTP)

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

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

SPF

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

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

SPF Policy Information Main policy

Host where this policy is located.Location mailjet.com
SPF version used by this policy.v spf1
Evaluates SPF policy specified in another DNS location. This
directive is typically used to allow hosts controlled by
another organization. include 		spf.mailjet.com
Evaluates SPF policy specified in another DNS location. This
directive is typically used to allow hosts controlled by
another organization. include 		aspmx.pardot.com
Evaluates SPF policy specified in another DNS location. This
directive is typically used to allow hosts controlled by
another organization. include 		mailgun.org
Evaluates SPF policy specified in another DNS location. This
directive is typically used to allow hosts controlled by
another organization. include 		spf.protection.outlook.com
This policy element always matches. It's normally used
at the end of a policy to specify the handling of hosts
that don't match earlier mechanisms. -all

Analysis

Info
SPF policy found

Policy text: v=spf1 include:spf.mailjet.com include:aspmx.pardot.com include:mailgun.org include:spf.protection.outlook.com -all

Location: mailjet.com

Good
SPF policy is valid
Good. Your SPF policy is syntactically valid.
Good
Policy uses default fail
Excellent. This policy fails hosts that are not allowed to send email for this domain name.
Good
Policy DNS lookups under limit
Good. Your policy stays under the limit of up to 10 DNS queries. The SPF specification Section 4.6.4. requires implementations to limit the total number of DNS queries. Policies that exceed the limit should not be used and may not work in practice.

Lookups: 9

SPF Policy Information Included policy

Host where this policy is located.Location spf.mailjet.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 		87.253.232.0/21
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		185.189.236.0/22
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		185.211.120.0/22
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		185.250.236.0/22
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		45.14.148.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 aspmx.pardot.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 		et._spf.pardot.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 et._spf.pardot.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 		198.245.81.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		136.147.176.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		13.111.0.0/16
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		136.147.182.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		136.147.135.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		199.122.123.0/24
This policy element always matches. It's normally used
at the end of a policy to specify the handling of hosts
that don't match earlier mechanisms. -all

SPF Policy Information Included policy

Host where this policy is located.Location mailgun.org
SPF version used by this policy.v spf1
Evaluates SPF policy specified in another DNS location. This
directive is typically used to allow hosts controlled by
another organization. include 		_spf.mailgun.org
Evaluates SPF policy specified in another DNS location. This
directive is typically used to allow hosts controlled by
another organization. include 		_spf.eu.mailgun.org
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.mailgun.org
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 		_spf1.mailgun.org
Evaluates SPF policy specified in another DNS location. This
directive is typically used to allow hosts controlled by
another organization. include 		_spf2.mailgun.org
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 _spf1.mailgun.org
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 		209.61.151.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		166.78.68.0/22
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		198.61.254.0/23
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		192.237.158.0/23
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		23.253.182.0/23
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		104.130.96.0/28
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		146.20.113.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		146.20.191.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		159.135.224.0/20
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		69.72.32.0/20
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.mailgun.org
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 		104.130.122.0/23
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		146.20.112.0/26
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		161.38.192.0/20
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		143.55.224.0/21
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		143.55.232.0/22
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		159.112.240.0/20
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		198.244.48.0/20
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		204.220.168.0/21
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		204.220.176.0/20
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.eu.mailgun.org
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 		141.193.32.0/23
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		159.135.140.80/29
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		159.135.132.128/25
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		161.38.204.0/22
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		87.253.232.0/21
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		185.189.236.0/22
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		185.211.120.0/22
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		185.250.236.0/22
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		143.55.236.0/22
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		198.244.60.0/22
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		204.220.160.0/21
This policy element always matches. It's normally used
at the end of a policy to specify the handling of hosts
that don't match earlier mechanisms. ~all

SPF Policy Information Included policy

Host where this policy is located.Location spf.protection.outlook.com
SPF version used by this policy.v spf1
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		40.92.0.0/15
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		40.107.0.0/16
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		52.100.0.0/15
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		52.102.0.0/16
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		52.103.0.0/17
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network. ip4 		104.47.0.0/17
This mechanism tests whether the IP address being
tested is contained within a given IPv6 network. ip6 		2a01:111:f400::/48
This mechanism tests whether the IP address being
tested is contained within a given IPv6 network. ip6 		2a01:111:f403::/49
This mechanism tests whether the IP address being
tested is contained within a given IPv6 network. ip6 		2a01:111:f403:8000::/51
This mechanism tests whether the IP address being
tested is contained within a given IPv6 network. ip6 		2a01:111:f403:c000::/51
This mechanism tests whether the IP address being
tested is contained within a given IPv6 network. ip6 		2a01:111:f403:f000::/52
This policy element always matches. It's normally used
at the end of a policy to specify the handling of hosts
that don't match earlier mechanisms. -all

DMARC

Domain-based Message Authentication, Reporting, and Conformance (DMARC) is a scalable mechanism by which a mail-originating organization can express domain-level policies and preferences for message validation, disposition, and reporting, that a mail-receiving organization can use to improve mail handling.

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

DMARC Policy Information

The location from which we obtained this policy.Policy location _dmarc.mailjet.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
Requested mail receiver policy for all subdomains.
Same format as for the p tag.sp 		reject
Percentage of messages from mail stream to
which the DMARC policy is to be applied.pct 		100
Configures failure reporting.fo 1
Indicates whether strict or relaxed DKIM
alignment mode is required.adkim 		r
Indicates whether strict or relaxed SPF
alignment mode is required.aspf 		r
Addresses to which aggregate feedback is to be sent.rua mailto:w8fajs9t@ag.us.dmarcian.com,mailto:mailjet@dmarc.mailjet.tech
Addresses to which message-specific failure
information is to be reported.ruf 		mailto:w8fajs9t@fr.us.dmarcian.com,mailto:mailjet@dmarc.mailjet.tech

Analysis

Info
DMARC policy found

Policy: v=DMARC1; p=reject; sp=reject; pct=100; fo=1; adkim=r; aspf=r; rua=mailto:w8fajs9t@ag.us.dmarcian.com,mailto:mailjet@dmarc.mailjet.tech; ruf=mailto:w8fajs9t@fr.us.dmarcian.com,mailto:mailjet@dmarc.mailjet.tech

Host: _dmarc.mailjet.com

Good
Valid external destination

Permission record location: mailjet.com._report._dmarc.ag.us.dmarcian.com

External destination: mailto:w8fajs9t@ag.us.dmarcian.com

Permission record contents: v=DMARC1;

Good
Valid external destination

Permission record location: mailjet.com._report._dmarc.fr.us.dmarcian.com

External destination: mailto:w8fajs9t@fr.us.dmarcian.com

Permission record contents: v=DMARC1;

Error
Invalid external destination
This policy uses an external report destination that is not authorized because the permission record doesn't exist. Please refer to RFC 7489, Section 7.1, for instructions how to correct this problem.

Expected permission record location: mailjet.com._report._dmarc.dmarc.mailjet.tech

External destination: mailto:mailjet@dmarc.mailjet.tech

Error
DMARC policy is invalid
Your DMARC policy is invalid.

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

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

Analysis

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

URL: http://www.mailjet.com/

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

Analysis

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

HTTP (443)

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

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

URL: https://mailjet.com/

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

URL: https://www.mailjet.com/

1
https://www.mailjet.com/
HTTP/1.1 200 OK

WWW TLS

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

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

TLS Configuration: mailjet.com (147.75.40.150)

Encryption protocol version determines what features are
available for negotiation between client and server.Supported protocols 		TLS v1.3
TLS v1.2
Servers should always enforce their own cipher
suite preference, as that is the only approach
that guarantees that the best possible suite is
selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3
Server preference 		Suite: TLS_CHACHA20_POLY1305_SHA256
Suite ID: 0x1303
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
 TLS_CHACHA20_POLY1305_SHA256  256 bits (ECDHE 256 bits)
Suite: TLS_AES_128_GCM_SHA256
Suite ID: 0x1301
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
 TLS_AES_128_GCM_SHA256  128 bits (ECDHE 256 bits)
Suite: TLS_AES_256_GCM_SHA384
Suite ID: 0x1302
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
 TLS_AES_256_GCM_SHA384  256 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2
Server preference 		Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcca8
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256  256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0xc02f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256  128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384  256 bits (ECDHE 256 bits)

Analysis

Good
TLS 1.3 supported
Excellent. This server supports TLS 1.3, which is the latest revision of the TLS protocol and a significant improvement over earlier versions. Developed over a period of several years and extensively analyzed prior to the release, TLS 1.3 removed insecure features, and improved both security and performance.
Good
TLS 1.2 supported
Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.
Good
Deprecated protocols not supported
Excellent. This server doesn't support any of the deprecated protocol (TLS 1.1 and earlier).
Good
Strong key exchange detected
Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.
Good
Only strong suites supported
Excellent. This server supports only strong cipher suites, which use strong authenticated encryption and provide forward secrecy.
Good
All TLS connections with this server satisfy Apple's CT requirements
All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

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

SCT transports: CERT

Notice
DHE suites not supported
This server doesn't support the Diffie-Hellman (DH) key exchange.

TLS Configuration: www.mailjet.com (2600:1f16:1a4:a001:0:0:0:1f4)

Encryption protocol version determines what features are
available for negotiation between client and server.Supported protocols 		TLS v1.3
TLS v1.2
Servers should always enforce their own cipher
suite preference, as that is the only approach
that guarantees that the best possible suite is
selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3
Server preference 		Suite: TLS_CHACHA20_POLY1305_SHA256
Suite ID: 0x1303
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
 TLS_CHACHA20_POLY1305_SHA256  256 bits (ECDHE 256 bits)
Suite: TLS_AES_128_GCM_SHA256
Suite ID: 0x1301
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
 TLS_AES_128_GCM_SHA256  128 bits (ECDHE 256 bits)
Suite: TLS_AES_256_GCM_SHA384
Suite ID: 0x1302
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
 TLS_AES_256_GCM_SHA384  256 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2
Server preference 		Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcca8
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256  256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0xc02f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256  128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384  256 bits (ECDHE 256 bits)

Analysis

Good
TLS 1.3 supported
Excellent. This server supports TLS 1.3, which is the latest revision of the TLS protocol and a significant improvement over earlier versions. Developed over a period of several years and extensively analyzed prior to the release, TLS 1.3 removed insecure features, and improved both security and performance.
Good
TLS 1.2 supported
Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.
Good
Deprecated protocols not supported
Excellent. This server doesn't support any of the deprecated protocol (TLS 1.1 and earlier).
Good
Strong key exchange detected
Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.
Good
Only strong suites supported
Excellent. This server supports only strong cipher suites, which use strong authenticated encryption and provide forward secrecy.
Good
All TLS connections with this server satisfy Apple's CT requirements
All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

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

SCT transports: CERT

Notice
DHE suites not supported
This server doesn't support the Diffie-Hellman (DH) key exchange.

TLS Configuration: www.mailjet.com (15.197.167.90)

Encryption protocol version determines what features are
available for negotiation between client and server.Supported protocols 		TLS v1.3
TLS v1.2
Servers should always enforce their own cipher
suite preference, as that is the only approach
that guarantees that the best possible suite is
selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3
Server preference 		Suite: TLS_CHACHA20_POLY1305_SHA256
Suite ID: 0x1303
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
 TLS_CHACHA20_POLY1305_SHA256  256 bits (ECDHE 256 bits)
Suite: TLS_AES_128_GCM_SHA256
Suite ID: 0x1301
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
 TLS_AES_128_GCM_SHA256  128 bits (ECDHE 256 bits)
Suite: TLS_AES_256_GCM_SHA384
Suite ID: 0x1302
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
 TLS_AES_256_GCM_SHA384  256 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2
Server preference 		Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcca8
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256  256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0xc02f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256  128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384  256 bits (ECDHE 256 bits)

Analysis

Good
TLS 1.3 supported
Excellent. This server supports TLS 1.3, which is the latest revision of the TLS protocol and a significant improvement over earlier versions. Developed over a period of several years and extensively analyzed prior to the release, TLS 1.3 removed insecure features, and improved both security and performance.
Good
TLS 1.2 supported
Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.
Good
Deprecated protocols not supported
Excellent. This server doesn't support any of the deprecated protocol (TLS 1.1 and earlier).
Good
Strong key exchange detected
Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.
Good
Only strong suites supported
Excellent. This server supports only strong cipher suites, which use strong authenticated encryption and provide forward secrecy.
Good
All TLS connections with this server satisfy Apple's CT requirements
All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

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

SCT transports: CERT

Notice
DHE suites not supported
This server doesn't support the Diffie-Hellman (DH) key exchange.

TLS Configuration: www.mailjet.com (2600:1f16:1a4:a002:0:0:0:1f4)

Encryption protocol version determines what features are
available for negotiation between client and server.Supported protocols 		TLS v1.3
TLS v1.2
Servers should always enforce their own cipher
suite preference, as that is the only approach
that guarantees that the best possible suite is
selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3
Server preference 		Suite: TLS_CHACHA20_POLY1305_SHA256
Suite ID: 0x1303
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
 TLS_CHACHA20_POLY1305_SHA256  256 bits (ECDHE 256 bits)
Suite: TLS_AES_128_GCM_SHA256
Suite ID: 0x1301
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
 TLS_AES_128_GCM_SHA256  128 bits (ECDHE 256 bits)
Suite: TLS_AES_256_GCM_SHA384
Suite ID: 0x1302
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
 TLS_AES_256_GCM_SHA384  256 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2
Server preference 		Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcca8
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256  256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0xc02f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256  128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384  256 bits (ECDHE 256 bits)

Analysis

Good
TLS 1.3 supported
Excellent. This server supports TLS 1.3, which is the latest revision of the TLS protocol and a significant improvement over earlier versions. Developed over a period of several years and extensively analyzed prior to the release, TLS 1.3 removed insecure features, and improved both security and performance.
Good
TLS 1.2 supported
Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.
Good
Deprecated protocols not supported
Excellent. This server doesn't support any of the deprecated protocol (TLS 1.1 and earlier).
Good
Strong key exchange detected
Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.
Good
Only strong suites supported
Excellent. This server supports only strong cipher suites, which use strong authenticated encryption and provide forward secrecy.
Good
All TLS connections with this server satisfy Apple's CT requirements
All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

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

SCT transports: CERT

Notice
DHE suites not supported
This server doesn't support the Diffie-Hellman (DH) key exchange.

TLS Configuration: www.mailjet.com (3.33.186.135)

Encryption protocol version determines what features are
available for negotiation between client and server.Supported protocols 		TLS v1.3
TLS v1.2
Servers should always enforce their own cipher
suite preference, as that is the only approach
that guarantees that the best possible suite is
selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3
Server preference 		Suite: TLS_CHACHA20_POLY1305_SHA256
Suite ID: 0x1303
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
 TLS_CHACHA20_POLY1305_SHA256  256 bits (ECDHE 256 bits)
Suite: TLS_AES_128_GCM_SHA256
Suite ID: 0x1301
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
 TLS_AES_128_GCM_SHA256  128 bits (ECDHE 256 bits)
Suite: TLS_AES_256_GCM_SHA384
Suite ID: 0x1302
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
 TLS_AES_256_GCM_SHA384  256 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2
Server preference 		Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcca8
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256  256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0xc02f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256  128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384  256 bits (ECDHE 256 bits)

Analysis

Good
TLS 1.3 supported
Excellent. This server supports TLS 1.3, which is the latest revision of the TLS protocol and a significant improvement over earlier versions. Developed over a period of several years and extensively analyzed prior to the release, TLS 1.3 removed insecure features, and improved both security and performance.
Good
TLS 1.2 supported
Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.
Good
Deprecated protocols not supported
Excellent. This server doesn't support any of the deprecated protocol (TLS 1.1 and earlier).
Good
Strong key exchange detected
Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.
Good
Only strong suites supported
Excellent. This server supports only strong cipher suites, which use strong authenticated encryption and provide forward secrecy.
Good
All TLS connections with this server satisfy Apple's CT requirements
All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

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

SCT transports: CERT

Notice
DHE suites not supported
This server doesn't support the Diffie-Hellman (DH) key exchange.

WWW Certificates

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

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

Certificate: www.mailjet.com

Leaf certificate mailjet.com
Issuer: DigiCert
Not Before: 17 Mar 2025 00:00:00 UTC
Not After: 15 Apr 2026 23:59:59 UTC (expires in 11 months 17 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
 View details

Analysis

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

Certificate 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
mailjet.com | 81e1733
Not After: 15 Apr 2026 23:59:59 UTC (expires in 11 months 17 days)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Intermediate certificate
DigiCert Global G2 TLS RSA SHA256 2020 CA1 | c8025f9
Not After: 29 Mar 2031 23:59:59 UTC (expires in 5 years 11 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Root certificate
DigiCert Global Root G2 | cb3ccbb
Not After: 15 Jan 2038 12:00:00 UTC (expires in 12 years 8 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details

Analysis

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

Certificate: mailjet.com

Leaf certificate mailjet.com
Issuer: DigiCert
Not Before: 17 Mar 2025 00:00:00 UTC
Not After: 15 Apr 2026 23:59:59 UTC (expires in 11 months 17 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
 View details

Analysis

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

Certificate 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
mailjet.com | 81e1733
Not After: 15 Apr 2026 23:59:59 UTC (expires in 11 months 17 days)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Intermediate certificate
DigiCert Global G2 TLS RSA SHA256 2020 CA1 | c8025f9
Not After: 29 Mar 2031 23:59:59 UTC (expires in 5 years 11 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Root certificate
DigiCert Global Root G2 | cb3ccbb
Not After: 15 Jan 2038 12:00:00 UTC (expires in 12 years 8 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details

Analysis

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

DANE (443)

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

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

Cookies

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

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

HTML Content

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

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

Encryption of Embedded Resources

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

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

Encryption of Outbound Links

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

0 link(s)
  0 out of 0 are encrypted

HTTP Strict Transport Security

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

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

HSTS Policy  Main host

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

Analysis

Good
Policy is valid
OK. Your HSTS policy uses correct syntax.
Good
Long policy age
Your HSTS policy has a long max-age value, which offers better protection.
Good
Policy covers subdomains
When subdomains are included, network attackers are unable to manufacture arbitrary subdomains to manipulate cookies and trick users.
Good
Redirection from HTTP to HTTPS to the same host
Good. The redirection from HTTP to HTTPS is to the same host. This approach ensures that HSTS is activated on the hostname when it's accessed via plaintext.
Good
Policy preloaded
Excellent. This host is covered by a preloaded HSTS policy.

Preloaded host: mailjet.com; includeSubDomains=true

HSTS Policy  Apex host

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

Analysis

Good
Policy is valid
OK. Your HSTS policy uses correct syntax.
Good
Long policy age
Your HSTS policy has a long max-age value, which offers better protection.
Good
Policy covers subdomains
When subdomains are included, network attackers are unable to manufacture arbitrary subdomains to manipulate cookies and trick users.
Good
Preload intent declared
Good. With the preload directive set, browsers have a green light to embed the HSTS policy.
Good
Redirection from HTTP to HTTPS to the same host
Good. The redirection from HTTP to HTTPS is to the same host. This approach ensures that HSTS is activated on the hostname when it's accessed via plaintext.
Good
Policy preloaded
Excellent. This host is covered by a preloaded HSTS policy.

Preloaded host: mailjet.com; includeSubDomains=true

HTTP Public Key Pinning

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

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

Content Security Policy

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

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

Content-Security-Policy

upgrade-insecure-requests
frame-ancestors 'none'  

Analysis

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

Analysis

Info
CSP policy detected

Header: Content-Security-Policy

Value: upgrade-insecure-requests; frame-ancestors 'none'

Location: https://www.mailjet.com/

Subresource Integrity

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

Test passed
Everything seems to be well configured. Well done.
No external scripts
  SRI not needed
No external stylesheets
  SRI not needed

Analysis

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

Expect CT

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

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

Analysis

Powerup!
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

Info
Header information

Name: X-Frame-Options

Value: DENY

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

XSS Protection

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

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

Analysis

Info
Header information

Name: X-Xss-Protection

Value: 1; mode=block

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

Content Type Options

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

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

Analysis

Info
Header information

Name: X-Content-Type-Options

Value: nosniff

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