Web Security Overview
Error
HTTPS

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

For all sites VERY IMPORTANT medium EFFORT
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
Warning
HTTP Strict Transport Security

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

For important sites VERY IMPORTANT medium EFFORT
Not supported
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
Not supported
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
Warning
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.
There are issues with this site's SMTP configuration.

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
Supported and well configured
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

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 failed
We've detected serious problems that require your immediate attention.

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
ns.comapanuevolaredo.gob.mx.
201.144.113.99
The server is online. Name resolves to an IPv4 address. Name doesn't resolve to an IPv6 address. REFERRAL
ns1.comapanuevolaredo.gob.mx. PRIMARY
201.144.113.99
The server is online. Name resolves to an IPv4 address. Name doesn't resolve to an IPv6 address. NS SOA
ns2.comapanuevolaredo.gob.mx.
201.144.113.99
The server is online. Name resolves to an IPv4 address. Name doesn't resolve to an IPv6 address. NS
serverweb.comapa.local.
DOESN'T RESOLVE
The server is not fully operational or refuses to serve this zone. Name doesn't resolve to an IPv4 address. Name doesn't resolve to an IPv6 address. 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
201.144.113.99 PRIMARY
ns.comapanuevolaredo.gob.mx.
ns1.comapanuevolaredo.gob.mx.
ns2.comapanuevolaredo.gob.mx.
PTR: mail.comapanuevolaredo.gob.mx.
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, GLUE 4000

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 ns1.comapanuevolaredo.gob.mx.
Email address of the persons responsible for this zone. Also known as RNAME.Admin email websistemas.comapanuevolaredo.gob.mx.
Zone serial or version number.Serial number 2025011420
The length of time secondary nameservers should wait before querying the primary for changes.Refresh interval 60 seconds (about 1 minute)
The length of time secondary nameservers should wait before querying an unresponsive primary again.Retry interval 60 seconds (about 1 minute)
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 86,400 seconds (about 1 day)
TTL for purposes of negative response caching. Negative cache TTL 3,600 seconds (about 1 hour)
Time To Live (TTL) indicates for how long a record remains valid. SOA record TTL 86,400 seconds (about 1 day)

Analysis

Error
Nameserver name doesn't resolve
The provided nameserver name doesn't resolve to an IP address. This usually happens if internal names make their way to the public configuration, which shouldn't happen. If the name is public and doesn't resolve, someone taking control over it (e.g., by registering an expired domain name) could lead to a nameserver takeover.

Name: serverweb.comapa.local.

Notice
Nameserver not in NS records
This nameserver appears in the referrals from the parent zone nameservers, but doesn't appear in the NS records.

Name: ns.comapanuevolaredo.gob.mx.

Notice
Nameserver not in referrals
This nameserver appears in the NS records, but doesn't appear in any referrals from the parent zone nameservers.

Name: ns1.comapanuevolaredo.gob.mx.

Notice
Nameserver not in referrals
This nameserver appears in the NS records, but doesn't appear in any referrals from the parent zone nameservers.

Name: ns2.comapanuevolaredo.gob.mx.

Notice
Nameserver not in referrals
This nameserver appears in the NS records, but doesn't appear in any referrals from the parent zone nameservers.

Name: serverweb.comapa.local.

Warning
Zone has fewer than two nameservers
A properly configured DNS zone requires at least two nameservers for redundancy. This means that there should be two names delegated to at least two IP addresses.
Powerup!
Nameserver A and AAAA records should have matching reverse records
According to RFC 1912, nameserver's PTR records must match their A and AAAA records to ensure maximum interoperability.
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.

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
comapanuevolaredo.gob.mx.     86400 A 201.144.113.99            
www.comapanuevolaredo.gob.mx.     3600 A 201.144.113.99            
comapanuevolaredo.gob.mx.     86400 MX 10 mail.comapanuevolaredo.gob.mx.            
comapanuevolaredo.gob.mx.     3600 NS serverweb.comapa.local.            
comapanuevolaredo.gob.mx.     86400 NS ns1.comapanuevolaredo.gob.mx.            
comapanuevolaredo.gob.mx.     86400 NS ns2.comapanuevolaredo.gob.mx.            
comapanuevolaredo.gob.mx.     86400 SOA ns1.comapanuevolaredo.gob.mx. websistemas.comapanuevolaredo.gob.mx. 2025011420 60 60 86400 3600            
comapanuevolaredo.gob.mx.     3600 TXT "google-site-verification=DpsdpOo9hVY3NPscDOwwtHfDW6m7e-hQEaXY_ByihoM"            
comapanuevolaredo.gob.mx.     86400 TXT "v=spf1 +a +mx +a:SERVERWEB.comapa.local -all"            
_dmarc.comapanuevolaredo.gob.mx.     86400 TXT "v=DMARC1;p=reject;sp=reject;pct=100;rua=mailto:ruacomapa@comapanuevolaredo.gob.mx;ruf=mailto:rufcomapa@comapanuevolaredo.gob.mx;ri=86400;aspf=s;adkim=s;fo=1; "            
_domainkey.comapanuevolaredo.gob.mx.     86400 TXT "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.

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, but there are warnings
Some aspect of your site's configuration require your attention.
Server Preference Operational STARTTLS TLS PKI DNSSEC DANE
mail.comapanuevolaredo.gob.mx
201.144.113.99
PTR: mail.comapanuevolaredo.gob.mx
10
220 mail.comapanuevolaredo.gob.mx ESMTP MailEnable Service, Version: -- ready at 07/23/25 10:13:47
EHLO outbound.hardenize.com
250-comapanuevolaredo.gob.mx [192.168.1.4], this server offers 5 extensions
250-AUTH LOGIN
250-SIZE 40960000
250-HELP
250-AUTH=LOGIN
250 STARTTLS
QUIT
221 Service closing transmission channel
Supports STARTTLS. Not supported. Not applicable,
requires TLS.

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: mail.comapanuevolaredo.gob.mx (201.144.113.99)

Encryption protocol version determines what features are
available for negotiation between client and server.
Supported protocols
TLS v1.2
TLS v1.1
TLS v1.0
Servers should always enforce their own cipher
suite preference, as that is the only approach
that guarantees that the best possible suite is
selected.
Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.2
Server preference
Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_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_DHE_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0x9f
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA384
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (DHE 2048 bits)
Suite: TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0x9e
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA256
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
 128 bits (DHE 2048 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc028
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0xc027
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x39
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (DHE 2048 bits)
Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x33
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (DHE 2048 bits)
Suite: TLS_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0x9d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA384
TLS_RSA_WITH_AES_256_GCM_SHA384
 256 bits
Suite: TLS_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0x9c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_GCM_SHA256
 128 bits
Suite: TLS_RSA_WITH_AES_256_CBC_SHA256
Suite ID: 0x3d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_256_CBC_SHA256
 256 bits
Suite: TLS_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0x3c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_CBC_SHA256
 128 bits
Suite: TLS_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x35
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x2f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_128_CBC_SHA
 128 bits
Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA
Suite ID: 0xa
Cipher name: 3DES (WEAK)
Cipher strength: 112 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_3DES_EDE_CBC_SHA
 112 bits
Suite: TLS_RSA_WITH_RC4_128_SHA
Suite ID: 0x5
Cipher name: RC4 (WEAK)
Cipher strength: 128 bits
Cipher mode: Stream
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_RC4_128_SHA
 128 bits
Suite: TLS_RSA_WITH_RC4_128_MD5
Suite ID: 0x4
Cipher name: RC4 (WEAK)
Cipher strength: 128 bits
Cipher mode: Stream
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: MD5
TLS_RSA_WITH_RC4_128_MD5
 128 bits
Shows cipher suite configuration for this protocol version.TLS v1.1
Server preference
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x39
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (DHE 2048 bits)
Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x33
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (DHE 2048 bits)
Suite: TLS_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x35
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x2f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_128_CBC_SHA
 128 bits
Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA
Suite ID: 0xa
Cipher name: 3DES (WEAK)
Cipher strength: 112 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_3DES_EDE_CBC_SHA
 112 bits
Suite: TLS_RSA_WITH_RC4_128_SHA
Suite ID: 0x5
Cipher name: RC4 (WEAK)
Cipher strength: 128 bits
Cipher mode: Stream
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_RC4_128_SHA
 128 bits
Suite: TLS_RSA_WITH_RC4_128_MD5
Suite ID: 0x4
Cipher name: RC4 (WEAK)
Cipher strength: 128 bits
Cipher mode: Stream
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: MD5
TLS_RSA_WITH_RC4_128_MD5
 128 bits
Shows cipher suite configuration for this protocol version.TLS v1.0
Server preference
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x39
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (DHE 2048 bits)
Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x33
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (DHE 2048 bits)
Suite: TLS_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x35
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x2f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_128_CBC_SHA
 128 bits
Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA
Suite ID: 0xa
Cipher name: 3DES (WEAK)
Cipher strength: 112 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_3DES_EDE_CBC_SHA
 112 bits
Suite: TLS_RSA_WITH_RC4_128_SHA
Suite ID: 0x5
Cipher name: RC4 (WEAK)
Cipher strength: 128 bits
Cipher mode: Stream
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_RC4_128_SHA
 128 bits
Suite: TLS_RSA_WITH_RC4_128_MD5
Suite ID: 0x4
Cipher name: RC4 (WEAK)
Cipher strength: 128 bits
Cipher mode: Stream
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: MD5
TLS_RSA_WITH_RC4_128_MD5
 128 bits

Analysis

Notice
Deprecated TLS 1.0 protocol supported
TLS 1.0 is a weak older protocol that should be phased out. Sites that aim at a wide audience might still need to support TLS 1.0 for the time being, because many older clients don't support newer protocol versions. Sites with a modern user base might be able to disable TLS 1.0 even now. We recommend that you enable logging of encryption parameters, after which you can examine your protocol usage and make decisions with confidence.
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
Server enforces cipher suite preferences
Excellent. This server enforces server cipher suite preference, which means that it is able to select the best suite from the options submitted by clients. Combined with a well-designed list of supported cipher suites, this setting enables negotiation of best security.
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
Server prefers forward secrecy and authenticated encryption suites
Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.
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.
Good
DHE server parameter not reused
This server does not reuse the private value used for the Diffie-Hellman key exchange.

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, but there are warnings
Some aspect of your site's configuration require your attention.

Certificate #1

Leaf certificate www.comapanuevolaredo.gob.mx
Issuer: Let's Encrypt
Not Before: 19 Apr 2025 13:21:06 UTC
Not After: 18 Jul 2025 13:21:05 UTC (expired 5 days 4 hours ago)
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.
Warning
Certificate doesn't match hostname
The provided certificate doesn't match the expected hostname. Default relaxed criteria for SMTP applies.

Expected hostname: mail.comapanuevolaredo.gob.mx

Warning
Certificate expired
The certificate has expired. Default relaxed criteria for SMTP applies.
Good
Certificate has not been revoked
Good. This certificate has not been revoked.
Notice
CT requirements not checked for expired certificates
Expired certificates usually refer to temporal CT logs that are retired once all certificates they hold expire. For this reason, we don't check CT compliance of expired certificates.
Warning
Certificate not publicly trusted
This certificate is not trusted. Default relaxed criteria for SMTP applies.

Certificate Chain

Leaf certificate
www.comapanuevolaredo.gob.mx | 29e7bea
Not After: 18 Jul 2025 13:21:05 UTC (expired 5 days 4 hours ago)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Intermediate certificate
R11 | 591e9ce
Not After: 12 Mar 2027 23:59:59 UTC (expires in 1 year 7 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Root certificate
ISRG Root X1 | 96bcec0
Not After: 04 Jun 2035 11:04:38 UTC (expires in 9 years 10 months)
Authentication: RSA 4096 bits (SHA256withRSA)
 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 comapanuevolaredo.gob.mx
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
This mechanism matches if the sending IP address
is one of the MX hosts for the domain name.
mx
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
SERVERWEB.comapa.local
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 +a +mx +a:SERVERWEB.comapa.local -all

Location: comapanuevolaredo.gob.mx

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

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.comapanuevolaredo.gob.mx
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
Addresses to which aggregate feedback is to be sent.rua mailto:ruacomapa@comapanuevolaredo.gob.mx
Addresses to which message-specific failure
information is to be reported.
ruf
mailto:rufcomapa@comapanuevolaredo.gob.mx
Interval between aggregate reports. Defaults to 86400.ri 86400
Indicates whether strict or relaxed SPF
alignment mode is required.
aspf
s
Indicates whether strict or relaxed DKIM
alignment mode is required.
adkim
s
Configures failure reporting.fo 1

Analysis

Info
DMARC policy found

Policy: v=DMARC1;p=reject;sp=reject;pct=100;rua=mailto:ruacomapa@comapanuevolaredo.gob.mx;ruf=mailto:rufcomapa@comapanuevolaredo.gob.mx;ri=86400;aspf=s;adkim=s;fo=1;

Host: _dmarc.comapanuevolaredo.gob.mx

Good
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://comapanuevolaredo.gob.mx/

1
http://comapanuevolaredo.gob.mx/
HTTP/1.1 301 Moved Permanently
2
https://www.comapanuevolaredo.gob.mx/
HTTP/1.1 301 Moved Permanently
3
https://www.comapanuevolaredo.gob.mx/sitio
HTTP/1.1 301 Moved Permanently
4
https://www.comapanuevolaredo.gob.mx/sitio/
HTTP/1.1 200 OK

Analysis

Warning
Same-host permanent redirection
This is a little-bit unusual. There's a permanent redirection from a root to a specific path on the same site. This may cause problems if the subpath ever changes. A temporary redirection is more appropriate in this case.

From: https://www.comapanuevolaredo.gob.mx/

To: https://www.comapanuevolaredo.gob.mx/sitio

Powerup!
Information leakage in HTTP response header
A HTTP response provided by this server includes a server that reveals potentially sensitive information about the software running on it. There is no reason why this information should be provided to the public and we recommend that it is removed.

Header value: ASP.NET

Header name: X-Powered-By

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

URL: http://www.comapanuevolaredo.gob.mx/

1
http://www.comapanuevolaredo.gob.mx/
HTTP/1.1 301 Moved Permanently
2
https://www.comapanuevolaredo.gob.mx/
HTTP/1.1 301 Moved Permanently
3
https://www.comapanuevolaredo.gob.mx/sitio
HTTP/1.1 301 Moved Permanently
4
https://www.comapanuevolaredo.gob.mx/sitio/
HTTP/1.1 200 OK

Analysis

Warning
Same-host permanent redirection
This is a little-bit unusual. There's a permanent redirection from a root to a specific path on the same site. This may cause problems if the subpath ever changes. A temporary redirection is more appropriate in this case.

From: https://www.comapanuevolaredo.gob.mx/

To: https://www.comapanuevolaredo.gob.mx/sitio

Powerup!
Information leakage in HTTP response header
A HTTP response provided by this server includes a server that reveals potentially sensitive information about the software running on it. There is no reason why this information should be provided to the public and we recommend that it is removed.

Header value: ASP.NET

Header name: X-Powered-By

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://comapanuevolaredo.gob.mx/

1
https://comapanuevolaredo.gob.mx/
HTTP/1.1 301 Moved Permanently
2
https://www.comapanuevolaredo.gob.mx/
HTTP/1.1 301 Moved Permanently
3
https://www.comapanuevolaredo.gob.mx/sitio
HTTP/1.1 301 Moved Permanently
4
https://www.comapanuevolaredo.gob.mx/sitio/
HTTP/1.1 200 OK

Analysis

Warning
Same-host permanent redirection
This is a little-bit unusual. There's a permanent redirection from a root to a specific path on the same site. This may cause problems if the subpath ever changes. A temporary redirection is more appropriate in this case.

From: https://www.comapanuevolaredo.gob.mx/

To: https://www.comapanuevolaredo.gob.mx/sitio

Powerup!
Information leakage in HTTP response header
A HTTP response provided by this server includes a server that reveals potentially sensitive information about the software running on it. There is no reason why this information should be provided to the public and we recommend that it is removed.

Header value: ASP.NET

Header name: X-Powered-By

URL: https://www.comapanuevolaredo.gob.mx/

1
https://www.comapanuevolaredo.gob.mx/
HTTP/1.1 301 Moved Permanently
2
https://www.comapanuevolaredo.gob.mx/sitio
HTTP/1.1 301 Moved Permanently
3
https://www.comapanuevolaredo.gob.mx/sitio/
HTTP/1.1 200 OK

Analysis

Warning
Same-host permanent redirection
This is a little-bit unusual. There's a permanent redirection from a root to a specific path on the same site. This may cause problems if the subpath ever changes. A temporary redirection is more appropriate in this case.

From: https://www.comapanuevolaredo.gob.mx/

To: https://www.comapanuevolaredo.gob.mx/sitio

Powerup!
Information leakage in HTTP response header
A HTTP response provided by this server includes a server that reveals potentially sensitive information about the software running on it. There is no reason why this information should be provided to the public and we recommend that it is removed.

Header value: ASP.NET

Header name: X-Powered-By

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, but there are warnings
Some aspect of your site's configuration require your attention.

TLS Configuration: comapanuevolaredo.gob.mx (201.144.113.99)

Encryption protocol version determines what features are
available for negotiation between client and server.
Supported protocols
TLS v1.2
TLS v1.1
TLS v1.0
Servers should always enforce their own cipher
suite preference, as that is the only approach
that guarantees that the best possible suite is
selected.
Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.2
Server preference
Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_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_DHE_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0x9f
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA384
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (DHE 2048 bits)
Suite: TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0x9e
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA256
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
 128 bits (DHE 2048 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc028
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0xc027
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x39
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (DHE 2048 bits)
Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x33
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (DHE 2048 bits)
Suite: TLS_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0x9d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA384
TLS_RSA_WITH_AES_256_GCM_SHA384
 256 bits
Suite: TLS_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0x9c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_GCM_SHA256
 128 bits
Suite: TLS_RSA_WITH_AES_256_CBC_SHA256
Suite ID: 0x3d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_256_CBC_SHA256
 256 bits
Suite: TLS_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0x3c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_CBC_SHA256
 128 bits
Suite: TLS_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x35
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x2f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_128_CBC_SHA
 128 bits
Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA
Suite ID: 0xa
Cipher name: 3DES (WEAK)
Cipher strength: 112 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_3DES_EDE_CBC_SHA
 112 bits
Suite: TLS_RSA_WITH_RC4_128_SHA
Suite ID: 0x5
Cipher name: RC4 (WEAK)
Cipher strength: 128 bits
Cipher mode: Stream
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_RC4_128_SHA
 128 bits
Suite: TLS_RSA_WITH_RC4_128_MD5
Suite ID: 0x4
Cipher name: RC4 (WEAK)
Cipher strength: 128 bits
Cipher mode: Stream
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: MD5
TLS_RSA_WITH_RC4_128_MD5
 128 bits
Shows cipher suite configuration for this protocol version.TLS v1.1
Server preference
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x39
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (DHE 2048 bits)
Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x33
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (DHE 2048 bits)
Suite: TLS_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x35
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x2f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_128_CBC_SHA
 128 bits
Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA
Suite ID: 0xa
Cipher name: 3DES (WEAK)
Cipher strength: 112 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_3DES_EDE_CBC_SHA
 112 bits
Suite: TLS_RSA_WITH_RC4_128_SHA
Suite ID: 0x5
Cipher name: RC4 (WEAK)
Cipher strength: 128 bits
Cipher mode: Stream
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_RC4_128_SHA
 128 bits
Suite: TLS_RSA_WITH_RC4_128_MD5
Suite ID: 0x4
Cipher name: RC4 (WEAK)
Cipher strength: 128 bits
Cipher mode: Stream
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: MD5
TLS_RSA_WITH_RC4_128_MD5
 128 bits
Shows cipher suite configuration for this protocol version.TLS v1.0
Server preference
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x39
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (DHE 2048 bits)
Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x33
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (DHE 2048 bits)
Suite: TLS_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x35
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x2f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_128_CBC_SHA
 128 bits
Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA
Suite ID: 0xa
Cipher name: 3DES (WEAK)
Cipher strength: 112 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_3DES_EDE_CBC_SHA
 112 bits
Suite: TLS_RSA_WITH_RC4_128_SHA
Suite ID: 0x5
Cipher name: RC4 (WEAK)
Cipher strength: 128 bits
Cipher mode: Stream
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_RC4_128_SHA
 128 bits
Suite: TLS_RSA_WITH_RC4_128_MD5
Suite ID: 0x4
Cipher name: RC4 (WEAK)
Cipher strength: 128 bits
Cipher mode: Stream
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: MD5
TLS_RSA_WITH_RC4_128_MD5
 128 bits

Analysis

Notice
Deprecated protocols supported
TLS 1.0 and TLS 1.1 are deprecated protocols that should be disabled if possible. TLS 1.0, in particular, is a weak older protocol that has many weaknesses. Sites that aim at a wide audience might still need to support TLS 1.0 for the time being, because many older clients don't support newer protocol versions. Sites with a modern user base might be able to disable TLS 1.0 even now. We recommend that you enable logging of encryption parameters, after which you can examine your protocol usage and make a decision with confidence. As of July 2018, PCI DSS doesn't allow use of TLS 1.0. Exceptions apply in some cases.
Powerup!
TLS 1.3 not supported
TLS 1.3 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. This version of TLS should be the main protocol used with modern clients.
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.
Warning
Insecure RC4 cipher supported
This server uses RC4, which is considered insecure Modern TLS clients no longer support this cipher and virtually all clients support one or more alternatives.

First encountered suite: TLS_RSA_WITH_RC4_128_SHA

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
Server prefers forward secrecy and authenticated encryption suites
Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.
Good
Server enforces cipher suite preferences
Excellent. This server enforces server cipher suite preference, which means that it is able to select the best suite from the options submitted by clients. Combined with a well-designed list of supported cipher suites, this setting enables negotiation of best security.
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

Good
DHE server parameter not reused
This server does not reuse the private value used for the Diffie-Hellman key exchange.

TLS Configuration: www.comapanuevolaredo.gob.mx (201.144.113.99)

Encryption protocol version determines what features are
available for negotiation between client and server.
Supported protocols
TLS v1.2
TLS v1.1
TLS v1.0
Servers should always enforce their own cipher
suite preference, as that is the only approach
that guarantees that the best possible suite is
selected.
Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.2
Server preference
Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_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_DHE_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0x9f
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA384
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (DHE 2048 bits)
Suite: TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0x9e
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA256
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
 128 bits (DHE 2048 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc028
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0xc027
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x39
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (DHE 2048 bits)
Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x33
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (DHE 2048 bits)
Suite: TLS_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0x9d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA384
TLS_RSA_WITH_AES_256_GCM_SHA384
 256 bits
Suite: TLS_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0x9c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_GCM_SHA256
 128 bits
Suite: TLS_RSA_WITH_AES_256_CBC_SHA256
Suite ID: 0x3d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_256_CBC_SHA256
 256 bits
Suite: TLS_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0x3c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_CBC_SHA256
 128 bits
Suite: TLS_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x35
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x2f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_128_CBC_SHA
 128 bits
Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA
Suite ID: 0xa
Cipher name: 3DES (WEAK)
Cipher strength: 112 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_3DES_EDE_CBC_SHA
 112 bits
Suite: TLS_RSA_WITH_RC4_128_SHA
Suite ID: 0x5
Cipher name: RC4 (WEAK)
Cipher strength: 128 bits
Cipher mode: Stream
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_RC4_128_SHA
 128 bits
Suite: TLS_RSA_WITH_RC4_128_MD5
Suite ID: 0x4
Cipher name: RC4 (WEAK)
Cipher strength: 128 bits
Cipher mode: Stream
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: MD5
TLS_RSA_WITH_RC4_128_MD5
 128 bits
Shows cipher suite configuration for this protocol version.TLS v1.1
Server preference
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x39
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (DHE 2048 bits)
Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x33
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (DHE 2048 bits)
Suite: TLS_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x35
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x2f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_128_CBC_SHA
 128 bits
Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA
Suite ID: 0xa
Cipher name: 3DES (WEAK)
Cipher strength: 112 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_3DES_EDE_CBC_SHA
 112 bits
Suite: TLS_RSA_WITH_RC4_128_SHA
Suite ID: 0x5
Cipher name: RC4 (WEAK)
Cipher strength: 128 bits
Cipher mode: Stream
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_RC4_128_SHA
 128 bits
Suite: TLS_RSA_WITH_RC4_128_MD5
Suite ID: 0x4
Cipher name: RC4 (WEAK)
Cipher strength: 128 bits
Cipher mode: Stream
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: MD5
TLS_RSA_WITH_RC4_128_MD5
 128 bits
Shows cipher suite configuration for this protocol version.TLS v1.0
Server preference
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x39
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (DHE 2048 bits)
Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x33
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 2048 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (DHE 2048 bits)
Suite: TLS_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x35
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x2f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_128_CBC_SHA
 128 bits
Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA
Suite ID: 0xa
Cipher name: 3DES (WEAK)
Cipher strength: 112 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_3DES_EDE_CBC_SHA
 112 bits
Suite: TLS_RSA_WITH_RC4_128_SHA
Suite ID: 0x5
Cipher name: RC4 (WEAK)
Cipher strength: 128 bits
Cipher mode: Stream
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_RC4_128_SHA
 128 bits
Suite: TLS_RSA_WITH_RC4_128_MD5
Suite ID: 0x4
Cipher name: RC4 (WEAK)
Cipher strength: 128 bits
Cipher mode: Stream
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: MD5
TLS_RSA_WITH_RC4_128_MD5
 128 bits

Analysis

Notice
Deprecated protocols supported
TLS 1.0 and TLS 1.1 are deprecated protocols that should be disabled if possible. TLS 1.0, in particular, is a weak older protocol that has many weaknesses. Sites that aim at a wide audience might still need to support TLS 1.0 for the time being, because many older clients don't support newer protocol versions. Sites with a modern user base might be able to disable TLS 1.0 even now. We recommend that you enable logging of encryption parameters, after which you can examine your protocol usage and make a decision with confidence. As of July 2018, PCI DSS doesn't allow use of TLS 1.0. Exceptions apply in some cases.
Powerup!
TLS 1.3 not supported
TLS 1.3 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. This version of TLS should be the main protocol used with modern clients.
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.
Warning
Insecure RC4 cipher supported
This server uses RC4, which is considered insecure Modern TLS clients no longer support this cipher and virtually all clients support one or more alternatives.

First encountered suite: TLS_RSA_WITH_RC4_128_SHA

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
Server prefers forward secrecy and authenticated encryption suites
Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.
Good
Server enforces cipher suite preferences
Excellent. This server enforces server cipher suite preference, which means that it is able to select the best suite from the options submitted by clients. Combined with a well-designed list of supported cipher suites, this setting enables negotiation of best security.
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

Good
DHE server parameter not reused
This server does not reuse the private value used for the Diffie-Hellman 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 failed
We've detected serious problems that require your immediate attention.

Certificate: comapanuevolaredo.gob.mx

Leaf certificate comapanuevolaredo.gob.mx
Issuer: Let's Encrypt
Not Before: 19 Apr 2025 13:19:55 UTC
Not After: 18 Jul 2025 13:19:54 UTC (expired 5 days 4 hours ago)
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.
Error
Certificate expired
The certificate has expired and can no longer be used.
Good
Certificate has not been revoked
Good. This certificate has not been revoked.
Notice
CT requirements not checked for expired certificates
Expired certificates usually refer to temporal CT logs that are retired once all certificates they hold expire. For this reason, we don't check CT compliance of expired certificates.
Error
Certificate not publicly trusted
This certificate is not trusted and can't be used on public web sites.

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
comapanuevolaredo.gob.mx | 195ffc9
Not After: 18 Jul 2025 13:19:54 UTC (expired 5 days 4 hours ago)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Intermediate certificate
R10 | 9d7c3f1
Not After: 12 Mar 2027 23:59:59 UTC (expires in 1 year 7 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Root certificate
ISRG Root X1 | 96bcec0
Not After: 04 Jun 2035 11:04:38 UTC (expires in 9 years 10 months)
Authentication: RSA 4096 bits (SHA256withRSA)
 View details

Analysis

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

Certificate: www.comapanuevolaredo.gob.mx

Leaf certificate comapanuevolaredo.gob.mx
Issuer: Let's Encrypt
Not Before: 19 Apr 2025 13:19:55 UTC
Not After: 18 Jul 2025 13:19:54 UTC (expired 5 days 4 hours ago)
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.
Error
Certificate expired
The certificate has expired and can no longer be used.
Good
Certificate has not been revoked
Good. This certificate has not been revoked.
Notice
CT requirements not checked for expired certificates
Expired certificates usually refer to temporal CT logs that are retired once all certificates they hold expire. For this reason, we don't check CT compliance of expired certificates.
Error
Certificate not publicly trusted
This certificate is not trusted and can't be used on public web sites.

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
comapanuevolaredo.gob.mx | 195ffc9
Not After: 18 Jul 2025 13:19:54 UTC (expired 5 days 4 hours ago)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Intermediate certificate
R10 | 9d7c3f1
Not After: 12 Mar 2027 23:59:59 UTC (expires in 1 year 7 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Root certificate
ISRG Root X1 | 96bcec0
Not After: 04 Jun 2035 11:04:38 UTC (expires in 9 years 10 months)
Authentication: RSA 4096 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 failed
We've detected serious problems that require your immediate attention.

HTTP Cookie: PHPSESSID  Session cookie

Cookie value. As far as the cookie RFC is concerned, the value
is an opaque string which only the application should interpret.
Value
rqri88jl9vrdvm34ctohtaj915
Cookie domain. When domain is implied (not explicitly set in a cookie),
most browsers (but not IE) treat the cookie as host-only, meaning that
no other server can overwrite it.
Domain
Implied (www.comapanuevolaredo.gob.mx)
Cookie path. This field can't be used as security measure,
but it could be of use to avoid cookie name collision
in non-adversarial contexts.
Path
/
The HttpOnly flag prevents the cookie from being accessed
from JavaScript, thus making them more difficult
to obtain after a successful XSS attack.
HttpOnly
The Secure flag signals to browsers that the cookie
should be transmitted only over an encrypted channel.
Secure
Normally, when a browser makes a request to a web site,
it sends all associated cookies. This is not always
desirable, because it might allow third-party sites
to perform site actions under the identity of the user.
This attack is known as Cross-Site Request Forgery.
With SameSite cookies (still in development, but already
supported in some browsers), you can choose to be more
strict. The possible values are 'lax' and 'strict'.
SameSite

Analysis

Error
Session cookie is not secure
This cookie, which has been sent over an encrypted channel, doesn't have the secure flag set. As a result, an active network attacker can easily recover it and hijack the user session.
Powerup!
Session cookie is not HttpOnly
This session cookie is not marked as HttpOnly. Session cookies usually don't need to be accessed from JavaScript. When marked as HttpOnly, they can't be accessed from JavaScript, making it more difficult for an attacker to obtain them after a successful XSS attack.
Powerup!
SameSite attribute not used
An upcoming standard, SameSite cookies, creates more secure cookies that are sent only on requests that originate from the same site that issued them. They are designed to prevent Cross-Site Request Forgery (CSRF) or at least make it more difficult.
Powerup!
Name prefix not used
Cookie name prefixes are a recent improvement that enable web application developers to opt-in into a more secure type of cookies. Virtually all cookies would benefit from using either the '__Secure-' or the '__Host-' prefix. The former ensures that a plaintext cookie can't overwrite a secure cookie. The latter ensures that the cookie is sent back only to the host that issued it.

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, but there are warnings
Some aspect of your site's configuration require your attention.

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.

9 script(s)
  9 out of 9 are secure  View all
9 CSS file(s)
  9 out of 9 are secure  View all
18 media file(s)
  18 out of 18 are secure  View all

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.

17 link(s)
  11 out of 17 are encrypted
http://maps.google.com/maps
http://maps.google.com/maps
http://maps.google.com/maps
http://maps.google.com/maps
http://maps.google.com/maps
http://webmail.comapanuevolaredo.gob.mx/
 View all

Analysis

Warning
Plaintext outbound links in HTTPS page
When outbound links are not encrypted, a passive network attacker can see where your users go after visiting your web site.

HTTP Strict Transport Security

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

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

HSTS Policy  Main host

URL from which this policy was obtained.Location https://www.comapanuevolaredo.gob.mx/
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
15,768,000 seconds (about 6 months 1 day)
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.
Notice
Preload directive has no effect here
This policy doesn't enable preloading, but that's all right. The preload directive doesn't have any effect unless it's used on an apex hostname.
Warning
HSTS won't activate because cert(s) not trusted
This server appears to be deploying HSTS with one or more certificates that are not publicly trusted. Under these circumstances, browsers will ignore the HSTS configuration.

Location: www.comapanuevolaredo.gob.mx

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.

HSTS Policy  Apex host

URL from which this policy was obtained.Location https://comapanuevolaredo.gob.mx/
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
15,768,000 seconds (about 6 months 1 day)
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.
Powerup!
Preloading not enabled
This policy doesn't give browsers permission to embed it and provide protection even to the first request to the web site. Sites that wish to use preloading can apply at hstspreload.org.
Warning
HSTS won't activate because cert(s) not trusted
This server appears to be deploying HSTS with one or more certificates that are not publicly trusted. Under these circumstances, browsers will ignore the HSTS configuration.

Location: comapanuevolaredo.gob.mx

Warning
Redirection from HTTP to HTTPS not to the same host
When HSTS is used, the plaintext port should redirect to the HTTPS variant of the same hostname. This approach ensures that HSTS is enabled on that hostname, even if later the client is sent elsewhere. A redirection to another host is only safe if it is for a parent host that has HSTS with includeSubDomains enabled, but that's not the case here.

Starting point: http://comapanuevolaredo.gob.mx

Current redirection: https://www.comapanuevolaredo.gob.mx/

Expected redirection: https://comapanuevolaredo.gob.mx

Analysis

Warning
Policy set on plaintext port
HSTS policies must not be transmitted over insecure channels.

Location: http://comapanuevolaredo.gob.mx/

Warning
Policy set on plaintext port
HSTS policies must not be transmitted over insecure channels.

Location: http://www.comapanuevolaredo.gob.mx/

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.
9 script(s)
  4 out of 9 are secure
https://ajax.googleapis.com/.../2.2.4/jquery.min.js
https://cdn.datatables.net/...ry.dataTables.min.js
https://connect.facebook.net/es_LA/sdk.js
https://unpkg.com/...swiper-bundle.min.js
https://www.google.com/recaptcha/api.js
 View all
9 CSS file(s)
  5 out of 9 are secure
https://cdn.datatables.net/...y.dataTables.min.css
https://fonts.googleapis.com/css2
https://stackpath.bootstrapcdn.com/...font-awesome.min.css
https://unpkg.com/...wiper-bundle.min.css
 View all

Analysis

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

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.

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

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

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