Hardenize Report: anonaddy.me

Web Security Overview

HTTPS

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

For all sites VERY IMPORTANT medium EFFORT

HTTPS Redirection

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

For all sites VERY IMPORTANT low EFFORT

HTTP Strict Transport Security

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

For important sites VERY IMPORTANT medium EFFORT

HSTS Preloaded

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

For important sites VERY IMPORTANT medium EFFORT

Content Security Policy

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

For important sites IMPORTANT high EFFORT

Email Security Overview

STARTTLS

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

For all sites VERY IMPORTANT low EFFORT

SPF

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

For important sites IMPORTANT low EFFORT

DMARC

Domain-based Message Authentication, Reporting, and Conformance (DMARC) is a mechanism that allows organizations to specify how unauthenticated email (identified using SPF and DKIM) should be handled.

For important sites IMPORTANT low EFFORT

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
get.desec.io. STEALTH PRIMARY 88.99.64.5 2a01:4f8:10a:1044:deec:642:ac10:80				SOA
ns1.desec.io. 45.54.76.1 2607:f740:e633:deec::2				NS REFERRAL
ns2.desec.org. 157.53.224.1 2607:f740:e00a:deec::2				NS REFERRAL

Nameserver Addresses

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

Nameserver	Sources	Payload Size
157.53.224.1 ns2.desec.org. PTR: ns2.desec.org.	NAME	1400
45.54.76.1 ns1.desec.io. PTR: ns1.desec.io.	NAME	1400
88.99.64.5 STEALTH PRIMARY get.desec.io. PTR: digga.desec.io.	NAME	-
2607:f740:e00a:deec::2 ns2.desec.org. PTR: ns2.desec.org.	NAME	1400
2607:f740:e633:deec::2 ns1.desec.io. PTR: ns1.desec.io.	NAME	1400
2a01:4f8:10a:1044:deec:642:ac10:80 STEALTH PRIMARY get.desec.io.	NAME	-

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	get.desec.io.
Email address of the persons responsible for this zone. Also known as RNAME.Admin email	get.desec.io.
Zone serial or version number.Serial number	2024103765
The length of time secondary nameservers should wait before querying the primary for changes.Refresh interval	86,400 seconds (about 1 day)
The length of time secondary nameservers should wait before querying an unresponsive primary again.Retry interval	3,600 seconds (about 1 hour)
The length of time after which secondary nameservers should stop responding to queries for a zone, assuming no updates were obtained from the primary.Expire interval	2,419,200 seconds (about 28 days)
TTL for purposes of negative response caching. Negative cache TTL	3,600 seconds (about 1 hour)
Time To Live (TTL) indicates for how long a record remains valid. SOA record TTL	300 seconds (about 5 minutes)

Analysis

No problems detected with the zone configuration

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

Backing DNS Queries

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

	ID	Server	Transport	Question Name	Type	Status

DNS Records

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

Test passed

Everything seems to be well configured. Well done.

DNS Records

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

Name	TTL	Type	Data
anonaddy.me.	3600	A	185.70.196.149
www.anonaddy.me.	3600	A	185.70.196.149
anonaddy.me.	3600	AAAA	2a04:3544:8000:1000:e8b5:6ff:fe29:56c
www.anonaddy.me.	3600	AAAA	2a04:3544:8000:1000:e8b5:6ff:fe29:56c
anonaddy.me.	3600	CAA	0 iodef "mailto:caapolicy@anonaddy.com"
anonaddy.me.	3600	CAA	0 issue "letsencrypt.org"
anonaddy.me.	3600	CAA	0 issuewild "letsencrypt.org"
anonaddy.me.	3600	DNSKEY	257 3 13 Heb+ZaCYyjmR+iOG8SShjJKHrjyejNoX8UcQbGHij0D1yNuQ40fqZ2erhcSFKTXwGxtPQG6K3ih7y9kuzXEApA==
anonaddy.me.	3600	MX	10 mail.anonaddy.me.
anonaddy.me.	3600	MX	5 mail2.anonaddy.me.
anonaddy.me.	3600	NS	ns1.desec.io.
anonaddy.me.	3600	NS	ns2.desec.org.
anonaddy.me.	300	SOA	get.desec.io. get.desec.io. 2024103765 86400 3600 2419200 3600
anonaddy.me.	3600	TXT	"v=spf1 mx -all"
anonaddy.me.	3600	TXT	"google-site-verification=nkTySSfgwEqJc8QOWhRHR0BnOg9EysTbDv4qEzzeP54"
_dmarc.anonaddy.me.	3600	TXT	"v=DMARC1; p=reject; pct=100; rua=mailto:dmarc@anonaddy.uriports.com; ruf=mailto:dmarc@anonaddy.uriports.com; sp=reject; aspf=r; fo=1:d:s"
_mta-sts.anonaddy.me.	3600	TXT	"v=STSv1; id=1618995452;"
_smtp._tls.anonaddy.me.	3600	TXT	"v=TLSRPTv1; rua=mailto:tlsrpt@anonaddy.uriports.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.

Test passed

Everything seems to be well configured. Well done.

Analysis

DNSSEC is well configured

Good. This domain name has well-configured DNSSEC.

Useful DNSSEC Tools

Certification Authority Authorization

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

Test passed

Everything seems to be well configured. Well done.

CAA Policy Information

The DNS hostname where this policy is located.Policy host	anonaddy.me
The iodef property specifies a means of reporting certificate issue requests or cases of certificate issue for the corresponding domain that violate the security policy of the issuer or the domain name holder.iodef	mailto:caapolicy@anonaddy.com flags: 0
The issuewild property has the same syntax and semantics as the issue property except that issuewild properties only grant authorization to issue certificates that specify a wildcard domain and issuewild properties take precedence over issue properties when specified.issuewild	letsencrypt.org flags: 0
The issue property tag is used to request that certificate issuers perform CAA issue restriction processing for the domain and to grant authorization to specific certificate issuers.issue	letsencrypt.org flags: 0

Analysis

Issuance of S/MIME certificates not restricted

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

Issuance of BIMI not restricted

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

CAA policy restricts issuance

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

Policy uses reporting

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

Email (SMTP)

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

Test passed

Everything seems to be well configured. Well done.

Server	Preference	Operational	STARTTLS	TLS	PKI	DNSSEC	DANE
mail2.anonaddy.me 2a04:3544:8000:1000:e8b5:6ff:fe29:56c PTR: mail2.anonaddy.me	5
mail2.anonaddy.me 185.70.196.149 PTR: mail2.anonaddy.me	5
mail.anonaddy.me 2a00:c6c0:0:108:3:0:0:10 PTR: mail.anonaddy.me	10
mail.anonaddy.me 213.108.105.57 PTR: mail.anonaddy.me	10

Analysis

Email servers match MTA-STS policy

Good. This host supports MTA-STS, which means that it restricts which MX servers can be used and how they are configured. We've verified that all MX servers listed here match the policy.

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.anonaddy.me (2a00:c6c0:0:108:3:0:0:10)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.3 TLS v1.2
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3 Server preference	Suite: TLS_AES_256_GCM_SHA384 Suite ID: 0x1302 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: secp384r1 Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (ECDHE 384 bits) Suite: TLS_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: secp384r1 Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 384 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: secp384r1 Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (ECDHE 384 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02b Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 384 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 secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 384 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc02c Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 384 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 secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 384 bits) Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca9 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 384 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 384 bits)

Analysis

TLS 1.2 supported

Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.

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.

Strong key exchange detected

Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.

Server prefers forward secrecy and authenticated encryption suites

Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.

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.

DHE suites not supported

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

TLS Configuration: mail2.anonaddy.me (2a04:3544:8000:1000:e8b5:6ff:fe29:56c)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.3 TLS v1.2
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3 Server preference	Suite: TLS_AES_256_GCM_SHA384 Suite ID: 0x1302 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: secp384r1 Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (ECDHE 384 bits) Suite: TLS_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: secp384r1 Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 384 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: secp384r1 Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (ECDHE 384 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02b Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 384 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 secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 384 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc02c Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 384 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 secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 384 bits) Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca9 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 384 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 384 bits)

Analysis

TLS 1.2 supported

Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.

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.

Strong key exchange detected

Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.

Server prefers forward secrecy and authenticated encryption suites

Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.

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.

DHE suites not supported

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

TLS Configuration: mail.anonaddy.me (213.108.105.57)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.3 TLS v1.2
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3 Server preference	Suite: TLS_AES_256_GCM_SHA384 Suite ID: 0x1302 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: secp384r1 Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (ECDHE 384 bits) Suite: TLS_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: secp384r1 Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 384 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: secp384r1 Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (ECDHE 384 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02b Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 384 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 secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 384 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc02c Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 384 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 secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 384 bits) Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca9 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 384 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 384 bits)

Analysis

TLS 1.2 supported

Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.

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.

Strong key exchange detected

Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.

Server prefers forward secrecy and authenticated encryption suites

Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.

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.

DHE suites not supported

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

TLS Configuration: mail2.anonaddy.me (185.70.196.149)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.3 TLS v1.2
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3 Server preference	Suite: TLS_AES_256_GCM_SHA384 Suite ID: 0x1302 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: secp384r1 Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (ECDHE 384 bits) Suite: TLS_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: secp384r1 Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 384 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: secp384r1 Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (ECDHE 384 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02b Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 384 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 secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 384 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc02c Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 384 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 secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 384 bits) Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca9 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 384 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 384 bits)

Analysis

TLS 1.2 supported

Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.

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.

Strong key exchange detected

Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.

Server prefers forward secrecy and authenticated encryption suites

Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.

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.

DHE suites not supported

This server doesn't support the Diffie-Hellman (DH) 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

Everything seems to be well configured. Well done.

Certificate #1

Leaf certificate

anonaddy.me
Issuer: Let's Encrypt
Not Before: 09 Oct 2024 22:03:10 UTC
Not After: 07 Jan 2025 22:03:09 UTC (expires in 2 months 5 days)
Key: EC 256 bits
Signature: SHA384withECDSA
View details

Names	*.anonaddy.me anonaddy.me
Subject DN	CN=anonaddy.me
Subject Key Identifier	6a8537c0fff19536c297af4756665705a9d8bef8
Serial	34a90143e1a0b25809dfc40c48ca1f70188
Not Before	09 Oct 2024 22:03:10 UTC
Not After	07 Jan 2025 22:03:09 UTC
Validity period	90 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=E6, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:9327469803a951688e98d6c44248db23bf5894d2
Parent Certificate	http://e6.i.lencr.org/
OCSP	http://e6.o.lencr.org
Certificate Transparency
Signed Certificate Timestamps	09 Oct 2024 23:01:40 UTC \| Let's Encrypt 'Oak2025h1' \| Qualified 09 Oct 2024 23:01:40 UTC \| Google 'Xenon2025h1' log \| Qualified
Fingerprints
SHA1	cd2ff6bb1584600ffdaccfbc7e47085677dc9388
SHA256	dfe1344b0c8250e287cbad0af4fb22801664ebc71bcb8ee92043b12409739a18
SPKI SHA256	f8c82ce3975879068b2e6fbe292cb7c967726b81f1c31249f72be666e20b88e4

Analysis

Strong private key

Good. The private key associated with this certificate is secure.

Strong signature algorithm

Good. This certificate uses a strong signature algorithm.

Certificate matches hostname

Good. The provided certificate matches the expected hostnames.

Certificate dates match

Good. The certificate is valid for use at this point of time.

Certificate has not been revoked

Good. This certificate has not been revoked.

Certificate satisfies Apple's CT compliance requirements

Good. This certificate satisfies Apple's CT requirements at present.

Certificate Chain

Leaf certificate

anonaddy.me | dfe1344
Not After: 07 Jan 2025 22:03:09 UTC (expires in 2 months 5 days)
Authentication: EC 256 bits (SHA384withECDSA)
View details

Names	*.anonaddy.me anonaddy.me
Subject DN	CN=anonaddy.me
Subject Key Identifier	6a8537c0fff19536c297af4756665705a9d8bef8
Serial	34a90143e1a0b25809dfc40c48ca1f70188
Not Before	09 Oct 2024 22:03:10 UTC
Not After	07 Jan 2025 22:03:09 UTC
Validity period	90 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=E6, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:9327469803a951688e98d6c44248db23bf5894d2
Parent Certificate	http://e6.i.lencr.org/
OCSP	http://e6.o.lencr.org
Certificate Transparency
Signed Certificate Timestamps	09 Oct 2024 23:01:40 UTC \| Let's Encrypt 'Oak2025h1' \| Qualified 09 Oct 2024 23:01:40 UTC \| Google 'Xenon2025h1' log \| Qualified
Fingerprints
SHA1	cd2ff6bb1584600ffdaccfbc7e47085677dc9388
SHA256	dfe1344b0c8250e287cbad0af4fb22801664ebc71bcb8ee92043b12409739a18
SPKI SHA256	f8c82ce3975879068b2e6fbe292cb7c967726b81f1c31249f72be666e20b88e4

Intermediate certificate

E6 | 76e9e28
Not After: 12 Mar 2027 23:59:59 UTC (expires in 2 years 4 months)
Authentication: EC 384 bits (SHA256withRSA)
View details

Subject DN	CN=E6, O=Let's Encrypt, C=US
Subject Key Identifier	9327469803a951688e98d6c44248db23bf5894d2
Serial	b0573e9173972770dbb487cb3a452b38
Not Before	13 Mar 2024 00:00:00 UTC
Not After	12 Mar 2027 23:59:59 UTC
Validity period	1095 days
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	clientAuth, serverAuth
Issuer
Issuer DN	CN=ISRG Root X1, O=Internet Security Research Group, C=US
Certification Authority	Let's Encrypt
Validation Type	Not Applicable
Authority Key Identifier	keyid:79b459e67bb6e5e40173800888c81a58f6e99b6e
Parent Certificate	http://x1.i.lencr.org/
CRL	http://x1.c.lencr.org/
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	c94dc4831a901a9fec0fb49b71bd49b5aad4fad0
SHA256	76e9e288aafc0e37f4390cbf946aad997d5c1c901b3ce513d3d8fadbabe2ab85
SPKI SHA256	d016e1fe311948aca64f2de44ce86c9a51ca041df6103bb52a88eb3f761f57d7

Root certificate

ISRG Root X1 | 96bcec0
Not After: 04 Jun 2035 11:04:38 UTC (expires in 10 years 7 months)
Authentication: RSA 4096 bits (SHA256withRSA)
View details

Subject DN	CN=ISRG Root X1, O=Internet Security Research Group, C=US
Subject Key Identifier	79b459e67bb6e5e40173800888c81a58f6e99b6e
Serial	8210cfb0d240e3594463e0bb63828b00
Not Before	04 Jun 2015 11:04:38 UTC
Not After	04 Jun 2035 11:04:38 UTC
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=ISRG Root X1, O=Internet Security Research Group, C=US
Certification Authority	Let's Encrypt
Validation Type	Self-signed
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	cabd2a79a1076a31f21d253635cb039d4329a5e8
SHA256	96bcec06264976f37460779acf28c5a7cfe8a3c0aae11a8ffcee05c0bddf08c6
SPKI SHA256	0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3

Analysis

Certificate chain is correct

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

Certificate #2

Leaf certificate

anonaddy.me
Issuer: Let's Encrypt
Not Before: 10 Oct 2024 22:01:37 UTC
Not After: 08 Jan 2025 22:01:36 UTC (expires in 2 months 6 days)
Key: RSA 4096 bits
Signature: SHA256withRSA
View details

Names	*.anonaddy.me anonaddy.me
Subject DN	CN=anonaddy.me
Subject Key Identifier	c5bacc2180334f1b7d646c83aaba67c3aaa7a584
Serial	31a6445c90421e388e629e8eda5f9642fba
Not Before	10 Oct 2024 22:01:37 UTC
Not After	08 Jan 2025 22:01:36 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R11, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:c5cf46a4eaf4c3c07a6c95c42db05e922f26e3b9
Parent Certificate	http://r11.i.lencr.org/
OCSP	http://r11.o.lencr.org
Certificate Transparency
Signed Certificate Timestamps	10 Oct 2024 23:00:07 UTC \| Google 'Xenon2025h1' log \| Qualified 10 Oct 2024 23:00:09 UTC \| Let's Encrypt 'Oak2024H2' log \| Qualified
Fingerprints
SHA1	e4f0ee0789d1fba0b9faa5c44cd9ece3101cb13d
SHA256	77d96280db8cad90911c4c2907dd271277490a275eb9ce7fd4936be9ca4b6c6d
SPKI SHA256	748a42fa079323bea4147b783466bcfd757505e14dc5c8ff8307e017b1499027

Analysis

Strong private key

Good. The private key associated with this certificate is secure.

Strong signature algorithm

Good. This certificate uses a strong signature algorithm.

Certificate matches hostname

Good. The provided certificate matches the expected hostnames.

Certificate dates match

Good. The certificate is valid for use at this point of time.

Certificate has not been revoked

Good. This certificate has not been revoked.

Certificate satisfies Apple's CT compliance requirements

Good. This certificate satisfies Apple's CT requirements at present.

Certificate Chain

Leaf certificate

anonaddy.me | 77d9628
Not After: 08 Jan 2025 22:01:36 UTC (expires in 2 months 6 days)
Authentication: RSA 4096 bits (SHA256withRSA)
View details

Names	*.anonaddy.me anonaddy.me
Subject DN	CN=anonaddy.me
Subject Key Identifier	c5bacc2180334f1b7d646c83aaba67c3aaa7a584
Serial	31a6445c90421e388e629e8eda5f9642fba
Not Before	10 Oct 2024 22:01:37 UTC
Not After	08 Jan 2025 22:01:36 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R11, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:c5cf46a4eaf4c3c07a6c95c42db05e922f26e3b9
Parent Certificate	http://r11.i.lencr.org/
OCSP	http://r11.o.lencr.org
Certificate Transparency
Signed Certificate Timestamps	10 Oct 2024 23:00:07 UTC \| Google 'Xenon2025h1' log \| Qualified 10 Oct 2024 23:00:09 UTC \| Let's Encrypt 'Oak2024H2' log \| Qualified
Fingerprints
SHA1	e4f0ee0789d1fba0b9faa5c44cd9ece3101cb13d
SHA256	77d96280db8cad90911c4c2907dd271277490a275eb9ce7fd4936be9ca4b6c6d
SPKI SHA256	748a42fa079323bea4147b783466bcfd757505e14dc5c8ff8307e017b1499027

Intermediate certificate

R11 | 591e9ce
Not After: 12 Mar 2027 23:59:59 UTC (expires in 2 years 4 months)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Subject DN	CN=R11, O=Let's Encrypt, C=US
Subject Key Identifier	c5cf46a4eaf4c3c07a6c95c42db05e922f26e3b9
Serial	8a7d3e13d62f30ef2386bd29076b34f8
Not Before	13 Mar 2024 00:00:00 UTC
Not After	12 Mar 2027 23:59:59 UTC
Validity period	1095 days
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	clientAuth, serverAuth
Issuer
Issuer DN	CN=ISRG Root X1, O=Internet Security Research Group, C=US
Certification Authority	Let's Encrypt
Validation Type	Not Applicable
Authority Key Identifier	keyid:79b459e67bb6e5e40173800888c81a58f6e99b6e
Parent Certificate	http://x1.i.lencr.org/
CRL	http://x1.c.lencr.org/
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	696db3af0dffc17e65c6a20d925c5a7bd24dec7e
SHA256	591e9ce6c863d3a079e9fabe1478c7339a26b21269dde795211361024ae31a44
SPKI SHA256	6ddac18698f7f1f7e1c69b9bce420d974ac6f94ca8b2c761701623f99c767dc7

Root certificate

ISRG Root X1 | 96bcec0
Not After: 04 Jun 2035 11:04:38 UTC (expires in 10 years 7 months)
Authentication: RSA 4096 bits (SHA256withRSA)
View details

Subject DN	CN=ISRG Root X1, O=Internet Security Research Group, C=US
Subject Key Identifier	79b459e67bb6e5e40173800888c81a58f6e99b6e
Serial	8210cfb0d240e3594463e0bb63828b00
Not Before	04 Jun 2015 11:04:38 UTC
Not After	04 Jun 2035 11:04:38 UTC
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=ISRG Root X1, O=Internet Security Research Group, C=US
Certification Authority	Let's Encrypt
Validation Type	Self-signed
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	cabd2a79a1076a31f21d253635cb039d4329a5e8
SHA256	96bcec06264976f37460779acf28c5a7cfe8a3c0aae11a8ffcee05c0bddf08c6
SPKI SHA256	0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3

Analysis

Certificate chain is correct

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

Email DANE (SMTP)

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

Test passed

Everything seems to be well configured. Well done.

DANE: mail2.anonaddy.me (2a04:3544:8000:1000:e8b5:6ff:fe29:56c)

Specifies which certificate in the chain is being pinned and how validation should be performed.Certificate Usage	Domain-issued certificate / DANE-EE (3)
Determines if the association is made with a certificate or with a public key (via its SPKI structure).Selector	SPKI structure (1)
Determines how matching is done; directly or via a hash. Matching Type	SHA2-256 (1)
Contains the data necessary to perform the matching. Data	f8c82ce3975879068b2e6fbe292cb7c967726b81f1c31249f72be666e20b88e4 Leaf certificate: EC 256 bits Subject: CN=anonaddy.me Issuer: CN=E6, O=Let's Encrypt, C=US anonaddy.me (EC 256 bits)

Specifies which certificate in the chain is being pinned and how validation should be performed.Certificate Usage	Domain-issued certificate / DANE-EE (3)
Determines if the association is made with a certificate or with a public key (via its SPKI structure).Selector	SPKI structure (1)
Determines how matching is done; directly or via a hash. Matching Type	SHA2-256 (1)
Contains the data necessary to perform the matching. Data	748a42fa079323bea4147b783466bcfd757505e14dc5c8ff8307e017b1499027 Leaf certificate: RSA 4096 bits Subject: CN=anonaddy.me Issuer: CN=R11, O=Let's Encrypt, C=US anonaddy.me (RSA 4096 bits)

Analysis

Valid DANE configuration

Excellent. Your DANE configuration matches the certificate chain(s) provided by the service. Your TLS configuration enjoys the additional benefit of DANE validation.

DANE: mail2.anonaddy.me (185.70.196.149)

Specifies which certificate in the chain is being pinned and how validation should be performed.Certificate Usage	Domain-issued certificate / DANE-EE (3)
Determines if the association is made with a certificate or with a public key (via its SPKI structure).Selector	SPKI structure (1)
Determines how matching is done; directly or via a hash. Matching Type	SHA2-256 (1)
Contains the data necessary to perform the matching. Data	f8c82ce3975879068b2e6fbe292cb7c967726b81f1c31249f72be666e20b88e4 Leaf certificate: EC 256 bits Subject: CN=anonaddy.me Issuer: CN=E6, O=Let's Encrypt, C=US anonaddy.me (EC 256 bits)

Specifies which certificate in the chain is being pinned and how validation should be performed.Certificate Usage	Domain-issued certificate / DANE-EE (3)
Determines if the association is made with a certificate or with a public key (via its SPKI structure).Selector	SPKI structure (1)
Determines how matching is done; directly or via a hash. Matching Type	SHA2-256 (1)
Contains the data necessary to perform the matching. Data	748a42fa079323bea4147b783466bcfd757505e14dc5c8ff8307e017b1499027 Leaf certificate: RSA 4096 bits Subject: CN=anonaddy.me Issuer: CN=R11, O=Let's Encrypt, C=US anonaddy.me (RSA 4096 bits)

Analysis

Valid DANE configuration

Excellent. Your DANE configuration matches the certificate chain(s) provided by the service. Your TLS configuration enjoys the additional benefit of DANE validation.

DANE: mail.anonaddy.me (2a00:c6c0:0:108:3:0:0:10)

Specifies which certificate in the chain is being pinned and how validation should be performed.Certificate Usage	Domain-issued certificate / DANE-EE (3)
Determines if the association is made with a certificate or with a public key (via its SPKI structure).Selector	SPKI structure (1)
Determines how matching is done; directly or via a hash. Matching Type	SHA2-256 (1)
Contains the data necessary to perform the matching. Data	f8c82ce3975879068b2e6fbe292cb7c967726b81f1c31249f72be666e20b88e4 Leaf certificate: EC 256 bits Subject: CN=anonaddy.me Issuer: CN=E6, O=Let's Encrypt, C=US anonaddy.me (EC 256 bits)

Specifies which certificate in the chain is being pinned and how validation should be performed.Certificate Usage	Domain-issued certificate / DANE-EE (3)
Determines if the association is made with a certificate or with a public key (via its SPKI structure).Selector	SPKI structure (1)
Determines how matching is done; directly or via a hash. Matching Type	SHA2-256 (1)
Contains the data necessary to perform the matching. Data	748a42fa079323bea4147b783466bcfd757505e14dc5c8ff8307e017b1499027 Leaf certificate: RSA 4096 bits Subject: CN=anonaddy.me Issuer: CN=R11, O=Let's Encrypt, C=US anonaddy.me (RSA 4096 bits)

Analysis

Valid DANE configuration

Excellent. Your DANE configuration matches the certificate chain(s) provided by the service. Your TLS configuration enjoys the additional benefit of DANE validation.

DANE: mail.anonaddy.me (213.108.105.57)

Specifies which certificate in the chain is being pinned and how validation should be performed.Certificate Usage	Domain-issued certificate / DANE-EE (3)
Determines if the association is made with a certificate or with a public key (via its SPKI structure).Selector	SPKI structure (1)
Determines how matching is done; directly or via a hash. Matching Type	SHA2-256 (1)
Contains the data necessary to perform the matching. Data	f8c82ce3975879068b2e6fbe292cb7c967726b81f1c31249f72be666e20b88e4 Leaf certificate: EC 256 bits Subject: CN=anonaddy.me Issuer: CN=E6, O=Let's Encrypt, C=US anonaddy.me (EC 256 bits)

Specifies which certificate in the chain is being pinned and how validation should be performed.Certificate Usage	Domain-issued certificate / DANE-EE (3)
Determines if the association is made with a certificate or with a public key (via its SPKI structure).Selector	SPKI structure (1)
Determines how matching is done; directly or via a hash. Matching Type	SHA2-256 (1)
Contains the data necessary to perform the matching. Data	748a42fa079323bea4147b783466bcfd757505e14dc5c8ff8307e017b1499027 Leaf certificate: RSA 4096 bits Subject: CN=anonaddy.me Issuer: CN=R11, O=Let's Encrypt, C=US anonaddy.me (RSA 4096 bits)

Analysis

Valid DANE configuration

Excellent. Your DANE configuration matches the certificate chain(s) provided by the service. Your TLS configuration enjoys the additional benefit of DANE validation.

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	anonaddy.me
SPF version used by this policy.v	spf1
This mechanism matches if the sending IP address is one of the MX hosts for the domain name. mx
This policy element always matches. It's normally used at the end of a policy to specify the handling of hosts that don't match earlier mechanisms. -all

Analysis

SPF policy found

Policy text: v=spf1 mx -all

Location: anonaddy.me

SPF policy is valid

Good. Your SPF policy is syntactically valid.

Policy uses default fail

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

Policy DNS lookups under limit

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

Lookups: 1

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.anonaddy.me
DMARC version used by this policy.v	DMARC1
Indicates the policy to be enacted by the receiver at the request of the domain owner. Possible values are: none, quarantine, and reject.p	reject
Percentage of messages from mail stream to which the DMARC policy is to be applied.pct	100
Addresses to which aggregate feedback is to be sent.rua	mailto:dmarc@anonaddy.uriports.com
Addresses to which message-specific failure information is to be reported.ruf	mailto:dmarc@anonaddy.uriports.com
Requested mail receiver policy for all subdomains. Same format as for the p tag.sp	reject
Indicates whether strict or relaxed SPF alignment mode is required.aspf	r
Configures failure reporting.fo	1:d:s

Analysis

DMARC policy found

Policy: v=DMARC1; p=reject; pct=100; rua=mailto:dmarc@anonaddy.uriports.com; ruf=mailto:dmarc@anonaddy.uriports.com; sp=reject; aspf=r; fo=1:d:s

Host: _dmarc.anonaddy.me

Valid external destination

Permission record location: anonaddy.me._report._dmarc.anonaddy.uriports.com

External destination: mailto:dmarc@anonaddy.uriports.com

Permission record contents: v=DMARC1;

Policy is valid

Good. You have a valid DMARC policy.

MTA Strict Transport Security

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

Test passed

Everything seems to be well configured. Well done.

MTA-STS Policy Indicator

Location from which we retrieved the policy indicator.Location	_mta-sts.anonaddy.me
MTA-STS standard version used by this policy indicator.Version	STSv1
Unique policy identifier, whose value must change every time the underlying policy changes.ID	1618995452

Analysis

MTA-STS policy indicator valid

Good. Your MTA-STS policy indicator is valid.

MTA-STS Policy

The URL from which the policy was obtained.Location	https://mta-sts.anonaddy.me/.well-known/mta-sts.txt
Policy standard version.version	STSv1
Policy duration, which specifies how long the sending MTAs should remember and enforce the server policy for.max‑age	10,368,000 seconds (about 4 months)
Policy mode, which can be one of 'none', 'testing' and 'enforcing'. Guess which is best! :)mode	enforce
One 'mx' directive specifies one email server pattern that's allowed for this host.mx	mail.anonaddy.me
One 'mx' directive specifies one email server pattern that's allowed for this host.mx	mail2.anonaddy.me

Analysis

MTA-STS policy is valid

Good. Your MTA-STS policy is valid.

Policy host certificate is valid

Good. Your MTA-STS policy is delivered via a web server that has a valid publicly trusted certificate. This is a necessary condition for the policy to be recognized.

Policy HTTPS response information

Status code: 200

Length: 90 bytes

Content-Type: text/plain; charset=utf-8

Certificate: mta-sts.anonaddy.me

Leaf certificate

anonaddy.me
Issuer: Let's Encrypt
Not Before: 09 Oct 2024 22:03:10 UTC
Not After: 07 Jan 2025 22:03:09 UTC (expires in 2 months 5 days)
Key: EC 256 bits
Signature: SHA384withECDSA
View details

Names	*.anonaddy.me anonaddy.me
Subject DN	CN=anonaddy.me
Subject Key Identifier	6a8537c0fff19536c297af4756665705a9d8bef8
Serial	34a90143e1a0b25809dfc40c48ca1f70188
Not Before	09 Oct 2024 22:03:10 UTC
Not After	07 Jan 2025 22:03:09 UTC
Validity period	90 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=E6, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:9327469803a951688e98d6c44248db23bf5894d2
Parent Certificate	http://e6.i.lencr.org/
OCSP	http://e6.o.lencr.org
Certificate Transparency
Signed Certificate Timestamps	09 Oct 2024 23:01:40 UTC \| Let's Encrypt 'Oak2025h1' \| Qualified 09 Oct 2024 23:01:40 UTC \| Google 'Xenon2025h1' log \| Qualified
Fingerprints
SHA1	cd2ff6bb1584600ffdaccfbc7e47085677dc9388
SHA256	dfe1344b0c8250e287cbad0af4fb22801664ebc71bcb8ee92043b12409739a18
SPKI SHA256	f8c82ce3975879068b2e6fbe292cb7c967726b81f1c31249f72be666e20b88e4

Analysis

Strong private key

Good. The private key associated with this certificate is secure.

Strong signature algorithm

Good. This certificate uses a strong signature algorithm.

Certificate matches hostname

Good. The provided certificate matches the expected hostnames.

Certificate dates match

Good. The certificate is valid for use at this point of time.

Certificate has not been revoked

Good. This certificate has not been revoked.

Certificate satisfies Apple's CT compliance requirements

Good. This certificate satisfies Apple's CT requirements at present.

Certificate Chain

Leaf certificate

anonaddy.me | dfe1344
Not After: 07 Jan 2025 22:03:09 UTC (expires in 2 months 5 days)
Authentication: EC 256 bits (SHA384withECDSA)
View details

Names	*.anonaddy.me anonaddy.me
Subject DN	CN=anonaddy.me
Subject Key Identifier	6a8537c0fff19536c297af4756665705a9d8bef8
Serial	34a90143e1a0b25809dfc40c48ca1f70188
Not Before	09 Oct 2024 22:03:10 UTC
Not After	07 Jan 2025 22:03:09 UTC
Validity period	90 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=E6, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:9327469803a951688e98d6c44248db23bf5894d2
Parent Certificate	http://e6.i.lencr.org/
OCSP	http://e6.o.lencr.org
Certificate Transparency
Signed Certificate Timestamps	09 Oct 2024 23:01:40 UTC \| Let's Encrypt 'Oak2025h1' \| Qualified 09 Oct 2024 23:01:40 UTC \| Google 'Xenon2025h1' log \| Qualified
Fingerprints
SHA1	cd2ff6bb1584600ffdaccfbc7e47085677dc9388
SHA256	dfe1344b0c8250e287cbad0af4fb22801664ebc71bcb8ee92043b12409739a18
SPKI SHA256	f8c82ce3975879068b2e6fbe292cb7c967726b81f1c31249f72be666e20b88e4

Intermediate certificate

E6 | 76e9e28
Not After: 12 Mar 2027 23:59:59 UTC (expires in 2 years 4 months)
Authentication: EC 384 bits (SHA256withRSA)
View details

Subject DN	CN=E6, O=Let's Encrypt, C=US
Subject Key Identifier	9327469803a951688e98d6c44248db23bf5894d2
Serial	b0573e9173972770dbb487cb3a452b38
Not Before	13 Mar 2024 00:00:00 UTC
Not After	12 Mar 2027 23:59:59 UTC
Validity period	1095 days
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	clientAuth, serverAuth
Issuer
Issuer DN	CN=ISRG Root X1, O=Internet Security Research Group, C=US
Certification Authority	Let's Encrypt
Validation Type	Not Applicable
Authority Key Identifier	keyid:79b459e67bb6e5e40173800888c81a58f6e99b6e
Parent Certificate	http://x1.i.lencr.org/
CRL	http://x1.c.lencr.org/
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	c94dc4831a901a9fec0fb49b71bd49b5aad4fad0
SHA256	76e9e288aafc0e37f4390cbf946aad997d5c1c901b3ce513d3d8fadbabe2ab85
SPKI SHA256	d016e1fe311948aca64f2de44ce86c9a51ca041df6103bb52a88eb3f761f57d7

Root certificate

ISRG Root X1 | 96bcec0
Not After: 04 Jun 2035 11:04:38 UTC (expires in 10 years 7 months)
Authentication: RSA 4096 bits (SHA256withRSA)
View details

Subject DN	CN=ISRG Root X1, O=Internet Security Research Group, C=US
Subject Key Identifier	79b459e67bb6e5e40173800888c81a58f6e99b6e
Serial	8210cfb0d240e3594463e0bb63828b00
Not Before	04 Jun 2015 11:04:38 UTC
Not After	04 Jun 2035 11:04:38 UTC
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=ISRG Root X1, O=Internet Security Research Group, C=US
Certification Authority	Let's Encrypt
Validation Type	Self-signed
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	cabd2a79a1076a31f21d253635cb039d4329a5e8
SHA256	96bcec06264976f37460779acf28c5a7cfe8a3c0aae11a8ffcee05c0bddf08c6
SPKI SHA256	0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3

Analysis

Certificate chain is correct

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

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.

Test passed

Everything seems to be well configured. Well done.

TLS-RPT Policy

Location from which we retrieved the policy indicator.Location	_smtp._tls.anonaddy.me
TLS-RPT standard version used by this policy indicator.Version	TLSRPTv1
Reporting endpoints specified in the policy.Reporting Endpoints	mailto:tlsrpt@anonaddy.uriports.com

Analysis

SMTP TLS-RPT policy valid

Good. Your TLS-RPT policy is valid. SMTP TLS Reporting is a young standard that is not yet widely supported, but support is probably going to increase over time.

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://anonaddy.me/

1

http://anonaddy.me/

HTTP/1.1 301 Moved Permanently

Server	nginx/1.27.2
Date	Sat, 02 Nov 2024 20:17:54 GMT
Content-Type	text/html
Content-Length	169
Connection	keep-alive
Location	https://anonaddy.me/

2

https://anonaddy.me/

HTTP/1.1 301 Moved Permanently

Server	nginx
Date	Sat, 02 Nov 2024 20:17:55 GMT
Content-Type	text/html
Content-Length	162
Connection	keep-alive
Location	https://addy.io/
X-Frame-Options	DENY
X-XSS-Protection	0
X-Content-Type-Options	nosniff
Strict-Transport-Security	max-age=63072000; includeSubDomains; preload
Content-Security-Policy	default-src 'none'; script-src 'self'; img-src 'self'; style-src 'self'; font-src 'self'; frame-src 'none'; frame-ancestors 'none'; object-src 'none'; base-uri 'none'; form-action 'none'; upgrade-insecure-requests;
Referrer-Policy	no-referrer

3

https://addy.io/

HTTP/1.1 200 OK

Server	nginx
Date	Sat, 02 Nov 2024 20:17:55 GMT
Content-Type	text/html; charset=utf-8
Content-Length	115278
Last-Modified	Sun, 13 Oct 2024 11:08:16 GMT
Connection	keep-alive
Vary	Accept-Encoding
ETag	"670baa20-1c24e"
Expires	Sun, 03 Nov 2024 20:17:55 GMT
Cache-Control	max-age=86400
X-Frame-Options	DENY
X-XSS-Protection	0
X-Content-Type-Options	nosniff
Strict-Transport-Security	max-age=63072000; includeSubDomains; preload
Content-Security-Policy	default-src 'none'; base-uri 'none'; form-action 'self' https://news.addy.io; connect-src 'self' https://app.addy.io/default-currency; manifest-src 'self'; frame-ancestors 'none'; script-src 'self' 'sha256-6qQWTVhBNcsGRyT26G26ZSIfLs+60+VhhX0ppPSgd50='; img-src 'self' data:; style-src 'self' 'sha256-47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=' 'sha256-/8CvIhEkJqzXuPzY8k7p4wTZ1zjLlE7mi3UcNExd8ao='; font-src 'self'; frame-src 'none'; object-src 'none'; upgrade-insecure-requests;
Referrer-Policy	no-referrer
Permissions-Policy	accelerometer=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=()
Cache-Control	public
Accept-Ranges	bytes

Analysis

HTTP redirects to HTTPS

Good. This plaintext HTTP server redirects to HTTPS.

URL: http://www.anonaddy.me/

1

http://www.anonaddy.me/

HTTP/1.1 301 Moved Permanently

Server	nginx/1.27.2
Date	Sat, 02 Nov 2024 20:17:56 GMT
Content-Type	text/html
Content-Length	169
Connection	keep-alive
Location	https://www.anonaddy.me/

2

https://www.anonaddy.me/

HTTP/1.1 301 Moved Permanently

Server	nginx
Date	Sat, 02 Nov 2024 20:17:56 GMT
Content-Type	text/html
Content-Length	162
Connection	keep-alive
Location	https://anonaddy.me/
X-Frame-Options	DENY
X-XSS-Protection	0
X-Content-Type-Options	nosniff
Strict-Transport-Security	max-age=63072000; includeSubDomains; preload
Content-Security-Policy	default-src 'none'; script-src 'self'; img-src 'self'; style-src 'self'; font-src 'self'; frame-src 'none'; frame-ancestors 'none'; object-src 'none'; base-uri 'none'; form-action 'none'; upgrade-insecure-requests;
Referrer-Policy	no-referrer

3

https://anonaddy.me/

HTTP/1.1 301 Moved Permanently

Server	nginx
Date	Sat, 02 Nov 2024 20:17:57 GMT
Content-Type	text/html
Content-Length	162
Connection	keep-alive
Location	https://addy.io/
X-Frame-Options	DENY
X-XSS-Protection	0
X-Content-Type-Options	nosniff
Strict-Transport-Security	max-age=63072000; includeSubDomains; preload
Content-Security-Policy	default-src 'none'; script-src 'self'; img-src 'self'; style-src 'self'; font-src 'self'; frame-src 'none'; frame-ancestors 'none'; object-src 'none'; base-uri 'none'; form-action 'none'; upgrade-insecure-requests;
Referrer-Policy	no-referrer

4

https://addy.io/

HTTP/1.1 200 OK

Server	nginx
Date	Sat, 02 Nov 2024 20:17:58 GMT
Content-Type	text/html; charset=utf-8
Content-Length	115278
Last-Modified	Sun, 13 Oct 2024 11:08:16 GMT
Connection	keep-alive
Vary	Accept-Encoding
ETag	"670baa20-1c24e"
Expires	Sun, 03 Nov 2024 20:17:58 GMT
Cache-Control	max-age=86400
X-Frame-Options	DENY
X-XSS-Protection	0
X-Content-Type-Options	nosniff
Strict-Transport-Security	max-age=63072000; includeSubDomains; preload
Content-Security-Policy	default-src 'none'; base-uri 'none'; form-action 'self' https://news.addy.io; connect-src 'self' https://app.addy.io/default-currency; manifest-src 'self'; frame-ancestors 'none'; script-src 'self' 'sha256-6qQWTVhBNcsGRyT26G26ZSIfLs+60+VhhX0ppPSgd50='; img-src 'self' data:; style-src 'self' 'sha256-47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=' 'sha256-/8CvIhEkJqzXuPzY8k7p4wTZ1zjLlE7mi3UcNExd8ao='; font-src 'self'; frame-src 'none'; object-src 'none'; upgrade-insecure-requests;
Referrer-Policy	no-referrer
Permissions-Policy	accelerometer=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=()
Cache-Control	public
Accept-Ranges	bytes

Analysis

HTTP redirects to HTTPS

Good. This plaintext HTTP server redirects to HTTPS.

HTTP (443)

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

Test passed

Everything seems to be well configured. Well done.

URL: https://anonaddy.me/

1

https://anonaddy.me/

HTTP/1.1 301 Moved Permanently

Server	nginx
Date	Sat, 02 Nov 2024 20:17:58 GMT
Content-Type	text/html
Content-Length	162
Connection	keep-alive
Location	https://addy.io/
X-Frame-Options	DENY
X-XSS-Protection	0
X-Content-Type-Options	nosniff
Strict-Transport-Security	max-age=63072000; includeSubDomains; preload
Content-Security-Policy	default-src 'none'; script-src 'self'; img-src 'self'; style-src 'self'; font-src 'self'; frame-src 'none'; frame-ancestors 'none'; object-src 'none'; base-uri 'none'; form-action 'none'; upgrade-insecure-requests;
Referrer-Policy	no-referrer

2

https://addy.io/

HTTP/1.1 200 OK

Server	nginx
Date	Sat, 02 Nov 2024 20:17:59 GMT
Content-Type	text/html; charset=utf-8
Content-Length	115278
Last-Modified	Sun, 13 Oct 2024 11:08:16 GMT
Connection	keep-alive
Vary	Accept-Encoding
ETag	"670baa20-1c24e"
Expires	Sun, 03 Nov 2024 20:17:59 GMT
Cache-Control	max-age=86400
X-Frame-Options	DENY
X-XSS-Protection	0
X-Content-Type-Options	nosniff
Strict-Transport-Security	max-age=63072000; includeSubDomains; preload
Content-Security-Policy	default-src 'none'; base-uri 'none'; form-action 'self' https://news.addy.io; connect-src 'self' https://app.addy.io/default-currency; manifest-src 'self'; frame-ancestors 'none'; script-src 'self' 'sha256-6qQWTVhBNcsGRyT26G26ZSIfLs+60+VhhX0ppPSgd50='; img-src 'self' data:; style-src 'self' 'sha256-47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=' 'sha256-/8CvIhEkJqzXuPzY8k7p4wTZ1zjLlE7mi3UcNExd8ao='; font-src 'self'; frame-src 'none'; object-src 'none'; upgrade-insecure-requests;
Referrer-Policy	no-referrer
Permissions-Policy	accelerometer=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=()
Cache-Control	public
Accept-Ranges	bytes

URL: https://www.anonaddy.me/

1

https://www.anonaddy.me/

HTTP/1.1 301 Moved Permanently

Server	nginx
Date	Sat, 02 Nov 2024 20:18:00 GMT
Content-Type	text/html
Content-Length	162
Connection	keep-alive
Location	https://anonaddy.me/
X-Frame-Options	DENY
X-XSS-Protection	0
X-Content-Type-Options	nosniff
Strict-Transport-Security	max-age=63072000; includeSubDomains; preload
Content-Security-Policy	default-src 'none'; script-src 'self'; img-src 'self'; style-src 'self'; font-src 'self'; frame-src 'none'; frame-ancestors 'none'; object-src 'none'; base-uri 'none'; form-action 'none'; upgrade-insecure-requests;
Referrer-Policy	no-referrer

2

https://anonaddy.me/

HTTP/1.1 301 Moved Permanently

Server	nginx
Date	Sat, 02 Nov 2024 20:18:00 GMT
Content-Type	text/html
Content-Length	162
Connection	keep-alive
Location	https://addy.io/
X-Frame-Options	DENY
X-XSS-Protection	0
X-Content-Type-Options	nosniff
Strict-Transport-Security	max-age=63072000; includeSubDomains; preload
Content-Security-Policy	default-src 'none'; script-src 'self'; img-src 'self'; style-src 'self'; font-src 'self'; frame-src 'none'; frame-ancestors 'none'; object-src 'none'; base-uri 'none'; form-action 'none'; upgrade-insecure-requests;
Referrer-Policy	no-referrer

3

https://addy.io/

HTTP/1.1 200 OK

Server	nginx
Date	Sat, 02 Nov 2024 20:18:01 GMT
Content-Type	text/html; charset=utf-8
Content-Length	115278
Last-Modified	Sun, 13 Oct 2024 11:08:16 GMT
Connection	keep-alive
Vary	Accept-Encoding
ETag	"670baa20-1c24e"
Expires	Sun, 03 Nov 2024 20:18:01 GMT
Cache-Control	max-age=86400
X-Frame-Options	DENY
X-XSS-Protection	0
X-Content-Type-Options	nosniff
Strict-Transport-Security	max-age=63072000; includeSubDomains; preload
Content-Security-Policy	default-src 'none'; base-uri 'none'; form-action 'self' https://news.addy.io; connect-src 'self' https://app.addy.io/default-currency; manifest-src 'self'; frame-ancestors 'none'; script-src 'self' 'sha256-6qQWTVhBNcsGRyT26G26ZSIfLs+60+VhhX0ppPSgd50='; img-src 'self' data:; style-src 'self' 'sha256-47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=' 'sha256-/8CvIhEkJqzXuPzY8k7p4wTZ1zjLlE7mi3UcNExd8ao='; font-src 'self'; frame-src 'none'; object-src 'none'; upgrade-insecure-requests;
Referrer-Policy	no-referrer
Permissions-Policy	accelerometer=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=()
Cache-Control	public
Accept-Ranges	bytes

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: anonaddy.me (185.70.196.149)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	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.2 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02b Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_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_ECDSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc02c Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_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_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca9 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits)

Analysis

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.

TLS 1.2 supported

Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.

Deprecated protocols not supported

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

Strong key exchange detected

Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.

Only strong suites supported

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

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

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

SCT transports: CERT

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

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

SCT transports: CERT

DHE suites not supported

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

TLS Configuration: anonaddy.me (2a04:3544:8000:1000:e8b5:6ff:fe29:56c)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	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.2 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02b Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_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_ECDSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc02c Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_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_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca9 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits)

Analysis

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.

TLS 1.2 supported

Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.

Deprecated protocols not supported

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

Strong key exchange detected

Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.

Only strong suites supported

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

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

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

SCT transports: CERT

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

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

SCT transports: CERT

DHE suites not supported

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

TLS Configuration: www.anonaddy.me (2a04:3544:8000:1000:e8b5:6ff:fe29:56c)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	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.2 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02b Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_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_ECDSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc02c Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_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_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca9 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits)

Analysis

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.

TLS 1.2 supported

Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.

Deprecated protocols not supported

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

Strong key exchange detected

Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.

Only strong suites supported

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

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

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

SCT transports: CERT

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

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

SCT transports: CERT

DHE suites not supported

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

TLS Configuration: www.anonaddy.me (185.70.196.149)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	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.2 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02b Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_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_ECDSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc02c Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_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_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca9 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits)

Analysis

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.

TLS 1.2 supported

Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.

Deprecated protocols not supported

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

Strong key exchange detected

Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.

Only strong suites supported

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

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

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

SCT transports: CERT

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

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

SCT transports: CERT

DHE suites not supported

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

WWW Certificates

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

Test passed

Everything seems to be well configured. Well done.

Certificate: anonaddy.me

Leaf certificate

anonaddy.me
Issuer: Let's Encrypt
Not Before: 09 Oct 2024 22:03:10 UTC
Not After: 07 Jan 2025 22:03:09 UTC (expires in 2 months 5 days)
Key: EC 256 bits
Signature: SHA384withECDSA
View details

Names	*.anonaddy.me anonaddy.me
Subject DN	CN=anonaddy.me
Subject Key Identifier	6a8537c0fff19536c297af4756665705a9d8bef8
Serial	34a90143e1a0b25809dfc40c48ca1f70188
Not Before	09 Oct 2024 22:03:10 UTC
Not After	07 Jan 2025 22:03:09 UTC
Validity period	90 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=E6, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:9327469803a951688e98d6c44248db23bf5894d2
Parent Certificate	http://e6.i.lencr.org/
OCSP	http://e6.o.lencr.org
Certificate Transparency
Signed Certificate Timestamps	09 Oct 2024 23:01:40 UTC \| Let's Encrypt 'Oak2025h1' \| Qualified 09 Oct 2024 23:01:40 UTC \| Google 'Xenon2025h1' log \| Qualified
Fingerprints
SHA1	cd2ff6bb1584600ffdaccfbc7e47085677dc9388
SHA256	dfe1344b0c8250e287cbad0af4fb22801664ebc71bcb8ee92043b12409739a18
SPKI SHA256	f8c82ce3975879068b2e6fbe292cb7c967726b81f1c31249f72be666e20b88e4

Analysis

Strong private key

Good. The private key associated with this certificate is secure.

Strong signature algorithm

Good. This certificate uses a strong signature algorithm.

Certificate matches hostname

Good. The provided certificate matches the expected hostnames.

Certificate dates match

Good. The certificate is valid for use at this point of time.

Certificate has not been revoked

Good. This certificate has not been revoked.

Certificate satisfies Apple's CT compliance requirements

Good. This certificate satisfies Apple's CT requirements at present.

Certificate Trust

Determining whether a certificate is considered valid is a complicated process that depends on the exact configuration of the validating party. For trust to be established, the certificate must form a chain that ends with a trusted root. In this section we evaluate the server's certificate against major root stores.

Platform	Trusted
Apple
Google AOSP
Microsoft
Mozilla

Certificate Chain

For a server certificate to be valid, it must be presented as part of a complete and valid certificate chain. The last certificate in the chain should be the root and is usually not included in the configuration.

Leaf certificate

anonaddy.me | dfe1344
Not After: 07 Jan 2025 22:03:09 UTC (expires in 2 months 5 days)
Authentication: EC 256 bits (SHA384withECDSA)
View details

Names	*.anonaddy.me anonaddy.me
Subject DN	CN=anonaddy.me
Subject Key Identifier	6a8537c0fff19536c297af4756665705a9d8bef8
Serial	34a90143e1a0b25809dfc40c48ca1f70188
Not Before	09 Oct 2024 22:03:10 UTC
Not After	07 Jan 2025 22:03:09 UTC
Validity period	90 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=E6, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:9327469803a951688e98d6c44248db23bf5894d2
Parent Certificate	http://e6.i.lencr.org/
OCSP	http://e6.o.lencr.org
Certificate Transparency
Signed Certificate Timestamps	09 Oct 2024 23:01:40 UTC \| Let's Encrypt 'Oak2025h1' \| Qualified 09 Oct 2024 23:01:40 UTC \| Google 'Xenon2025h1' log \| Qualified
Fingerprints
SHA1	cd2ff6bb1584600ffdaccfbc7e47085677dc9388
SHA256	dfe1344b0c8250e287cbad0af4fb22801664ebc71bcb8ee92043b12409739a18
SPKI SHA256	f8c82ce3975879068b2e6fbe292cb7c967726b81f1c31249f72be666e20b88e4

Intermediate certificate

E6 | 76e9e28
Not After: 12 Mar 2027 23:59:59 UTC (expires in 2 years 4 months)
Authentication: EC 384 bits (SHA256withRSA)
View details

Subject DN	CN=E6, O=Let's Encrypt, C=US
Subject Key Identifier	9327469803a951688e98d6c44248db23bf5894d2
Serial	b0573e9173972770dbb487cb3a452b38
Not Before	13 Mar 2024 00:00:00 UTC
Not After	12 Mar 2027 23:59:59 UTC
Validity period	1095 days
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	clientAuth, serverAuth
Issuer
Issuer DN	CN=ISRG Root X1, O=Internet Security Research Group, C=US
Certification Authority	Let's Encrypt
Validation Type	Not Applicable
Authority Key Identifier	keyid:79b459e67bb6e5e40173800888c81a58f6e99b6e
Parent Certificate	http://x1.i.lencr.org/
CRL	http://x1.c.lencr.org/
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	c94dc4831a901a9fec0fb49b71bd49b5aad4fad0
SHA256	76e9e288aafc0e37f4390cbf946aad997d5c1c901b3ce513d3d8fadbabe2ab85
SPKI SHA256	d016e1fe311948aca64f2de44ce86c9a51ca041df6103bb52a88eb3f761f57d7

Root certificate

ISRG Root X1 | 96bcec0
Not After: 04 Jun 2035 11:04:38 UTC (expires in 10 years 7 months)
Authentication: RSA 4096 bits (SHA256withRSA)
View details

Subject DN	CN=ISRG Root X1, O=Internet Security Research Group, C=US
Subject Key Identifier	79b459e67bb6e5e40173800888c81a58f6e99b6e
Serial	8210cfb0d240e3594463e0bb63828b00
Not Before	04 Jun 2015 11:04:38 UTC
Not After	04 Jun 2035 11:04:38 UTC
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=ISRG Root X1, O=Internet Security Research Group, C=US
Certification Authority	Let's Encrypt
Validation Type	Self-signed
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	cabd2a79a1076a31f21d253635cb039d4329a5e8
SHA256	96bcec06264976f37460779acf28c5a7cfe8a3c0aae11a8ffcee05c0bddf08c6
SPKI SHA256	0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3

Analysis

Certificate chain is correct

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

Certificate: anonaddy.me

Leaf certificate

anonaddy.me
Issuer: Let's Encrypt
Not Before: 10 Oct 2024 22:01:37 UTC
Not After: 08 Jan 2025 22:01:36 UTC (expires in 2 months 6 days)
Key: RSA 4096 bits
Signature: SHA256withRSA
View details

Names	*.anonaddy.me anonaddy.me
Subject DN	CN=anonaddy.me
Subject Key Identifier	c5bacc2180334f1b7d646c83aaba67c3aaa7a584
Serial	31a6445c90421e388e629e8eda5f9642fba
Not Before	10 Oct 2024 22:01:37 UTC
Not After	08 Jan 2025 22:01:36 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R11, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:c5cf46a4eaf4c3c07a6c95c42db05e922f26e3b9
Parent Certificate	http://r11.i.lencr.org/
OCSP	http://r11.o.lencr.org
Certificate Transparency
Signed Certificate Timestamps	10 Oct 2024 23:00:07 UTC \| Google 'Xenon2025h1' log \| Qualified 10 Oct 2024 23:00:09 UTC \| Let's Encrypt 'Oak2024H2' log \| Qualified
Fingerprints
SHA1	e4f0ee0789d1fba0b9faa5c44cd9ece3101cb13d
SHA256	77d96280db8cad90911c4c2907dd271277490a275eb9ce7fd4936be9ca4b6c6d
SPKI SHA256	748a42fa079323bea4147b783466bcfd757505e14dc5c8ff8307e017b1499027

Analysis

Strong private key

Good. The private key associated with this certificate is secure.

Strong signature algorithm

Good. This certificate uses a strong signature algorithm.

Certificate matches hostname

Good. The provided certificate matches the expected hostnames.

Certificate dates match

Good. The certificate is valid for use at this point of time.

Certificate has not been revoked

Good. This certificate has not been revoked.

Certificate satisfies Apple's CT compliance requirements

Good. This certificate satisfies Apple's CT requirements at present.

Certificate Trust

Determining whether a certificate is considered valid is a complicated process that depends on the exact configuration of the validating party. For trust to be established, the certificate must form a chain that ends with a trusted root. In this section we evaluate the server's certificate against major root stores.

Platform	Trusted
Apple
Google AOSP
Microsoft
Mozilla

Certificate Chain

For a server certificate to be valid, it must be presented as part of a complete and valid certificate chain. The last certificate in the chain should be the root and is usually not included in the configuration.

Leaf certificate

anonaddy.me | 77d9628
Not After: 08 Jan 2025 22:01:36 UTC (expires in 2 months 6 days)
Authentication: RSA 4096 bits (SHA256withRSA)
View details

Names	*.anonaddy.me anonaddy.me
Subject DN	CN=anonaddy.me
Subject Key Identifier	c5bacc2180334f1b7d646c83aaba67c3aaa7a584
Serial	31a6445c90421e388e629e8eda5f9642fba
Not Before	10 Oct 2024 22:01:37 UTC
Not After	08 Jan 2025 22:01:36 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R11, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:c5cf46a4eaf4c3c07a6c95c42db05e922f26e3b9
Parent Certificate	http://r11.i.lencr.org/
OCSP	http://r11.o.lencr.org
Certificate Transparency
Signed Certificate Timestamps	10 Oct 2024 23:00:07 UTC \| Google 'Xenon2025h1' log \| Qualified 10 Oct 2024 23:00:09 UTC \| Let's Encrypt 'Oak2024H2' log \| Qualified
Fingerprints
SHA1	e4f0ee0789d1fba0b9faa5c44cd9ece3101cb13d
SHA256	77d96280db8cad90911c4c2907dd271277490a275eb9ce7fd4936be9ca4b6c6d
SPKI SHA256	748a42fa079323bea4147b783466bcfd757505e14dc5c8ff8307e017b1499027

Intermediate certificate

R11 | 591e9ce
Not After: 12 Mar 2027 23:59:59 UTC (expires in 2 years 4 months)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Subject DN	CN=R11, O=Let's Encrypt, C=US
Subject Key Identifier	c5cf46a4eaf4c3c07a6c95c42db05e922f26e3b9
Serial	8a7d3e13d62f30ef2386bd29076b34f8
Not Before	13 Mar 2024 00:00:00 UTC
Not After	12 Mar 2027 23:59:59 UTC
Validity period	1095 days
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	clientAuth, serverAuth
Issuer
Issuer DN	CN=ISRG Root X1, O=Internet Security Research Group, C=US
Certification Authority	Let's Encrypt
Validation Type	Not Applicable
Authority Key Identifier	keyid:79b459e67bb6e5e40173800888c81a58f6e99b6e
Parent Certificate	http://x1.i.lencr.org/
CRL	http://x1.c.lencr.org/
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	696db3af0dffc17e65c6a20d925c5a7bd24dec7e
SHA256	591e9ce6c863d3a079e9fabe1478c7339a26b21269dde795211361024ae31a44
SPKI SHA256	6ddac18698f7f1f7e1c69b9bce420d974ac6f94ca8b2c761701623f99c767dc7

Root certificate

ISRG Root X1 | 96bcec0
Not After: 04 Jun 2035 11:04:38 UTC (expires in 10 years 7 months)
Authentication: RSA 4096 bits (SHA256withRSA)
View details

Subject DN	CN=ISRG Root X1, O=Internet Security Research Group, C=US
Subject Key Identifier	79b459e67bb6e5e40173800888c81a58f6e99b6e
Serial	8210cfb0d240e3594463e0bb63828b00
Not Before	04 Jun 2015 11:04:38 UTC
Not After	04 Jun 2035 11:04:38 UTC
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=ISRG Root X1, O=Internet Security Research Group, C=US
Certification Authority	Let's Encrypt
Validation Type	Self-signed
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	cabd2a79a1076a31f21d253635cb039d4329a5e8
SHA256	96bcec06264976f37460779acf28c5a7cfe8a3c0aae11a8ffcee05c0bddf08c6
SPKI SHA256	0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3

Analysis

Certificate chain is correct

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

Certificate: www.anonaddy.me

Leaf certificate

anonaddy.me
Issuer: Let's Encrypt
Not Before: 09 Oct 2024 22:03:10 UTC
Not After: 07 Jan 2025 22:03:09 UTC (expires in 2 months 5 days)
Key: EC 256 bits
Signature: SHA384withECDSA
View details

Names	*.anonaddy.me anonaddy.me
Subject DN	CN=anonaddy.me
Subject Key Identifier	6a8537c0fff19536c297af4756665705a9d8bef8
Serial	34a90143e1a0b25809dfc40c48ca1f70188
Not Before	09 Oct 2024 22:03:10 UTC
Not After	07 Jan 2025 22:03:09 UTC
Validity period	90 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=E6, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:9327469803a951688e98d6c44248db23bf5894d2
Parent Certificate	http://e6.i.lencr.org/
OCSP	http://e6.o.lencr.org
Certificate Transparency
Signed Certificate Timestamps	09 Oct 2024 23:01:40 UTC \| Let's Encrypt 'Oak2025h1' \| Qualified 09 Oct 2024 23:01:40 UTC \| Google 'Xenon2025h1' log \| Qualified
Fingerprints
SHA1	cd2ff6bb1584600ffdaccfbc7e47085677dc9388
SHA256	dfe1344b0c8250e287cbad0af4fb22801664ebc71bcb8ee92043b12409739a18
SPKI SHA256	f8c82ce3975879068b2e6fbe292cb7c967726b81f1c31249f72be666e20b88e4

Analysis

Strong private key

Good. The private key associated with this certificate is secure.

Strong signature algorithm

Good. This certificate uses a strong signature algorithm.

Certificate matches hostname

Good. The provided certificate matches the expected hostnames.

Certificate dates match

Good. The certificate is valid for use at this point of time.

Certificate has not been revoked

Good. This certificate has not been revoked.

Certificate satisfies Apple's CT compliance requirements

Good. This certificate satisfies Apple's CT requirements at present.

Certificate Trust

Determining whether a certificate is considered valid is a complicated process that depends on the exact configuration of the validating party. For trust to be established, the certificate must form a chain that ends with a trusted root. In this section we evaluate the server's certificate against major root stores.

Platform	Trusted
Apple
Google AOSP
Microsoft
Mozilla

Certificate Chain

For a server certificate to be valid, it must be presented as part of a complete and valid certificate chain. The last certificate in the chain should be the root and is usually not included in the configuration.

Leaf certificate

anonaddy.me | dfe1344
Not After: 07 Jan 2025 22:03:09 UTC (expires in 2 months 5 days)
Authentication: EC 256 bits (SHA384withECDSA)
View details

Names	*.anonaddy.me anonaddy.me
Subject DN	CN=anonaddy.me
Subject Key Identifier	6a8537c0fff19536c297af4756665705a9d8bef8
Serial	34a90143e1a0b25809dfc40c48ca1f70188
Not Before	09 Oct 2024 22:03:10 UTC
Not After	07 Jan 2025 22:03:09 UTC
Validity period	90 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=E6, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:9327469803a951688e98d6c44248db23bf5894d2
Parent Certificate	http://e6.i.lencr.org/
OCSP	http://e6.o.lencr.org
Certificate Transparency
Signed Certificate Timestamps	09 Oct 2024 23:01:40 UTC \| Let's Encrypt 'Oak2025h1' \| Qualified 09 Oct 2024 23:01:40 UTC \| Google 'Xenon2025h1' log \| Qualified
Fingerprints
SHA1	cd2ff6bb1584600ffdaccfbc7e47085677dc9388
SHA256	dfe1344b0c8250e287cbad0af4fb22801664ebc71bcb8ee92043b12409739a18
SPKI SHA256	f8c82ce3975879068b2e6fbe292cb7c967726b81f1c31249f72be666e20b88e4

Intermediate certificate

E6 | 76e9e28
Not After: 12 Mar 2027 23:59:59 UTC (expires in 2 years 4 months)
Authentication: EC 384 bits (SHA256withRSA)
View details

Subject DN	CN=E6, O=Let's Encrypt, C=US
Subject Key Identifier	9327469803a951688e98d6c44248db23bf5894d2
Serial	b0573e9173972770dbb487cb3a452b38
Not Before	13 Mar 2024 00:00:00 UTC
Not After	12 Mar 2027 23:59:59 UTC
Validity period	1095 days
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	clientAuth, serverAuth
Issuer
Issuer DN	CN=ISRG Root X1, O=Internet Security Research Group, C=US
Certification Authority	Let's Encrypt
Validation Type	Not Applicable
Authority Key Identifier	keyid:79b459e67bb6e5e40173800888c81a58f6e99b6e
Parent Certificate	http://x1.i.lencr.org/
CRL	http://x1.c.lencr.org/
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	c94dc4831a901a9fec0fb49b71bd49b5aad4fad0
SHA256	76e9e288aafc0e37f4390cbf946aad997d5c1c901b3ce513d3d8fadbabe2ab85
SPKI SHA256	d016e1fe311948aca64f2de44ce86c9a51ca041df6103bb52a88eb3f761f57d7

Root certificate

ISRG Root X1 | 96bcec0
Not After: 04 Jun 2035 11:04:38 UTC (expires in 10 years 7 months)
Authentication: RSA 4096 bits (SHA256withRSA)
View details

Subject DN	CN=ISRG Root X1, O=Internet Security Research Group, C=US
Subject Key Identifier	79b459e67bb6e5e40173800888c81a58f6e99b6e
Serial	8210cfb0d240e3594463e0bb63828b00
Not Before	04 Jun 2015 11:04:38 UTC
Not After	04 Jun 2035 11:04:38 UTC
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=ISRG Root X1, O=Internet Security Research Group, C=US
Certification Authority	Let's Encrypt
Validation Type	Self-signed
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	cabd2a79a1076a31f21d253635cb039d4329a5e8
SHA256	96bcec06264976f37460779acf28c5a7cfe8a3c0aae11a8ffcee05c0bddf08c6
SPKI SHA256	0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3

Analysis

Certificate chain is correct

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

Certificate: www.anonaddy.me

Leaf certificate

anonaddy.me
Issuer: Let's Encrypt
Not Before: 10 Oct 2024 22:01:37 UTC
Not After: 08 Jan 2025 22:01:36 UTC (expires in 2 months 6 days)
Key: RSA 4096 bits
Signature: SHA256withRSA
View details

Names	*.anonaddy.me anonaddy.me
Subject DN	CN=anonaddy.me
Subject Key Identifier	c5bacc2180334f1b7d646c83aaba67c3aaa7a584
Serial	31a6445c90421e388e629e8eda5f9642fba
Not Before	10 Oct 2024 22:01:37 UTC
Not After	08 Jan 2025 22:01:36 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R11, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:c5cf46a4eaf4c3c07a6c95c42db05e922f26e3b9
Parent Certificate	http://r11.i.lencr.org/
OCSP	http://r11.o.lencr.org
Certificate Transparency
Signed Certificate Timestamps	10 Oct 2024 23:00:07 UTC \| Google 'Xenon2025h1' log \| Qualified 10 Oct 2024 23:00:09 UTC \| Let's Encrypt 'Oak2024H2' log \| Qualified
Fingerprints
SHA1	e4f0ee0789d1fba0b9faa5c44cd9ece3101cb13d
SHA256	77d96280db8cad90911c4c2907dd271277490a275eb9ce7fd4936be9ca4b6c6d
SPKI SHA256	748a42fa079323bea4147b783466bcfd757505e14dc5c8ff8307e017b1499027

Analysis

Strong private key

Good. The private key associated with this certificate is secure.

Strong signature algorithm

Good. This certificate uses a strong signature algorithm.

Certificate matches hostname

Good. The provided certificate matches the expected hostnames.

Certificate dates match

Good. The certificate is valid for use at this point of time.

Certificate has not been revoked

Good. This certificate has not been revoked.

Certificate satisfies Apple's CT compliance requirements

Good. This certificate satisfies Apple's CT requirements at present.

Certificate Trust

Determining whether a certificate is considered valid is a complicated process that depends on the exact configuration of the validating party. For trust to be established, the certificate must form a chain that ends with a trusted root. In this section we evaluate the server's certificate against major root stores.

Platform	Trusted
Apple
Google AOSP
Microsoft
Mozilla

Certificate Chain

For a server certificate to be valid, it must be presented as part of a complete and valid certificate chain. The last certificate in the chain should be the root and is usually not included in the configuration.

Leaf certificate

anonaddy.me | 77d9628
Not After: 08 Jan 2025 22:01:36 UTC (expires in 2 months 6 days)
Authentication: RSA 4096 bits (SHA256withRSA)
View details

Names	*.anonaddy.me anonaddy.me
Subject DN	CN=anonaddy.me
Subject Key Identifier	c5bacc2180334f1b7d646c83aaba67c3aaa7a584
Serial	31a6445c90421e388e629e8eda5f9642fba
Not Before	10 Oct 2024 22:01:37 UTC
Not After	08 Jan 2025 22:01:36 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R11, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:c5cf46a4eaf4c3c07a6c95c42db05e922f26e3b9
Parent Certificate	http://r11.i.lencr.org/
OCSP	http://r11.o.lencr.org
Certificate Transparency
Signed Certificate Timestamps	10 Oct 2024 23:00:07 UTC \| Google 'Xenon2025h1' log \| Qualified 10 Oct 2024 23:00:09 UTC \| Let's Encrypt 'Oak2024H2' log \| Qualified
Fingerprints
SHA1	e4f0ee0789d1fba0b9faa5c44cd9ece3101cb13d
SHA256	77d96280db8cad90911c4c2907dd271277490a275eb9ce7fd4936be9ca4b6c6d
SPKI SHA256	748a42fa079323bea4147b783466bcfd757505e14dc5c8ff8307e017b1499027

Intermediate certificate

R11 | 591e9ce
Not After: 12 Mar 2027 23:59:59 UTC (expires in 2 years 4 months)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Subject DN	CN=R11, O=Let's Encrypt, C=US
Subject Key Identifier	c5cf46a4eaf4c3c07a6c95c42db05e922f26e3b9
Serial	8a7d3e13d62f30ef2386bd29076b34f8
Not Before	13 Mar 2024 00:00:00 UTC
Not After	12 Mar 2027 23:59:59 UTC
Validity period	1095 days
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	clientAuth, serverAuth
Issuer
Issuer DN	CN=ISRG Root X1, O=Internet Security Research Group, C=US
Certification Authority	Let's Encrypt
Validation Type	Not Applicable
Authority Key Identifier	keyid:79b459e67bb6e5e40173800888c81a58f6e99b6e
Parent Certificate	http://x1.i.lencr.org/
CRL	http://x1.c.lencr.org/
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	696db3af0dffc17e65c6a20d925c5a7bd24dec7e
SHA256	591e9ce6c863d3a079e9fabe1478c7339a26b21269dde795211361024ae31a44
SPKI SHA256	6ddac18698f7f1f7e1c69b9bce420d974ac6f94ca8b2c761701623f99c767dc7

Root certificate

ISRG Root X1 | 96bcec0
Not After: 04 Jun 2035 11:04:38 UTC (expires in 10 years 7 months)
Authentication: RSA 4096 bits (SHA256withRSA)
View details

Subject DN	CN=ISRG Root X1, O=Internet Security Research Group, C=US
Subject Key Identifier	79b459e67bb6e5e40173800888c81a58f6e99b6e
Serial	8210cfb0d240e3594463e0bb63828b00
Not Before	04 Jun 2015 11:04:38 UTC
Not After	04 Jun 2035 11:04:38 UTC
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=ISRG Root X1, O=Internet Security Research Group, C=US
Certification Authority	Let's Encrypt
Validation Type	Self-signed
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	cabd2a79a1076a31f21d253635cb039d4329a5e8
SHA256	96bcec06264976f37460779acf28c5a7cfe8a3c0aae11a8ffcee05c0bddf08c6
SPKI SHA256	0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3

Analysis

Certificate chain is correct

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

DANE (443)

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

Test passed

Everything seems to be well configured. Well done.

TLSA Record #1: _443._tcp.anonaddy.me.

Specifies which certificate in the chain is being pinned and how validation should be performed.Certificate Usage	Domain-issued certificate / DANE-EE (3)
Determines if the association is made with a certificate or with a public key (via its SPKI structure).Selector	SPKI structure (1)
Determines how matching is done; directly or via a hash. Matching Type	SHA2-256 (1)
Contains the data necessary to perform the matching. Data	748a42fa079323bea4147b783466bcfd757505e14dc5c8ff8307e017b1499027 Leaf certificate: RSA 4096 bits Subject: CN=anonaddy.me Issuer: CN=R11, O=Let's Encrypt, C=US anonaddy.me (RSA 4096 bits)

TLSA Record #2: _443._tcp.anonaddy.me.

Specifies which certificate in the chain is being pinned and how validation should be performed.Certificate Usage	Domain-issued certificate / DANE-EE (3)
Determines if the association is made with a certificate or with a public key (via its SPKI structure).Selector	SPKI structure (1)
Determines how matching is done; directly or via a hash. Matching Type	SHA2-256 (1)
Contains the data necessary to perform the matching. Data	f8c82ce3975879068b2e6fbe292cb7c967726b81f1c31249f72be666e20b88e4 Leaf certificate: EC 256 bits Subject: CN=anonaddy.me Issuer: CN=E6, O=Let's Encrypt, C=US anonaddy.me (EC 256 bits)

Analysis

DANE configuration matches

DANE configuration is present for this service and matches the certificate chain.

DANE configuration matches

DANE configuration is present for this service and matches the certificate chain.

Valid DANE configuration

Excellent. Your DANE configuration matches the certificate chain(s) provided by the service. Your TLS configuration enjoys the additional benefit of DANE validation.

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.anonaddy.me/
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

Policy is valid

OK. Your HSTS policy uses correct syntax.

Long policy age

Your HSTS policy has a long max-age value, which offers better protection.

Policy covers subdomains

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

Redirection from HTTP to HTTPS to the same host

Good. The redirection from HTTP to HTTPS is to the same host. This approach ensures that HSTS is activated on the hostname when it's accessed via plaintext.

Policy preloaded

Excellent. This host is covered by a preloaded HSTS policy.

Preloaded host: anonaddy.me; includeSubDomains=true

HSTS Policy Apex host

URL from which this policy was obtained.Location	https://anonaddy.me/
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

Policy is valid

OK. Your HSTS policy uses correct syntax.

Long policy age

Your HSTS policy has a long max-age value, which offers better protection.

Policy covers subdomains

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

Preload intent declared

Good. With the preload directive set, browsers have a green light to embed the HSTS policy.

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.

Policy preloaded

Excellent. This host is covered by a preloaded HSTS policy.

Preloaded host: anonaddy.me; 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

default-src	'none'
script-src	'self'
img-src	'self'
style-src	'self'
font-src	'self'
frame-ancestors	'none'
base-uri	-
form-action	-
upgrade-insecure-requests

Analysis

Mixed content upgraded

Good. This CSP policy instructs browsers to seamlessly upgrade plaintext resources to encryption.

Analysis

CSP policy detected

Header: Content-Security-Policy

Value: default-src 'none'; script-src 'self'; img-src 'self'; style-src 'self'; font-src 'self'; frame-src 'none'; frame-ancestors 'none'; object-src 'none'; base-uri 'none'; form-action 'none'; upgrade-insecure-requests;

Location: https://anonaddy.me/

Subresource Integrity

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

Test passed

Everything seems to be well configured. Well done.

No external scripts
SRI not needed

No external stylesheets
SRI not needed

Analysis

No remote resources

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

Expect CT

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

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

Analysis

Deploy Expect-CT to enable reporting

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

Frame Options

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

Test passed

Everything seems to be well configured. Well done.

Analysis

Header information

Name: X-Frame-Options

Value: DENY

Framing blocked

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

XSS Protection

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

Test passed

Everything seems to be well configured. Well done.

Analysis

Header information

Name: X-XSS-Protection

Value: 0

Browser XSS protection disabled

Great. XSS protection is explicitly disabled, making this web site safe even with browsers that have this functionality enabled by default.

Content Type Options

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

Test passed

Everything seems to be well configured. Well done.

Analysis

Header information

Name: X-Content-Type-Options

Value: nosniff

Valid configuration

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

Public Report | anonaddy.me

anonaddy.me

Domain Name System

Email

WWW

DNS Zone

Nameserver Names

Nameserver Addresses

Start of Authority (SOA) Record

Analysis

Backing DNS Queries

DNS Records

DNS Records

Backing DNS Queries

DNSSEC

Analysis

Useful DNSSEC Tools

Certification Authority Authorization

CAA Policy Information

Analysis

Email (SMTP)

Analysis

Email TLS (SMTP)

TLS Configuration: mail.anonaddy.me (2a00:c6c0:0:108:3:0:0:10)

Analysis

TLS Configuration: mail2.anonaddy.me (2a04:3544:8000:1000:e8b5:6ff:fe29:56c)

Analysis

TLS Configuration: mail.anonaddy.me (213.108.105.57)

Analysis

TLS Configuration: mail2.anonaddy.me (185.70.196.149)

Analysis

Email Certificates (SMTP)

Certificate #1

Analysis

Certificate Chain

Analysis

Certificate #2

Analysis

Certificate Chain

Analysis

Email DANE (SMTP)

DANE: mail2.anonaddy.me (2a04:3544:8000:1000:e8b5:6ff:fe29:56c)

Analysis

DANE: mail2.anonaddy.me (185.70.196.149)

Analysis

DANE: mail.anonaddy.me (2a00:c6c0:0:108:3:0:0:10)

Analysis

DANE: mail.anonaddy.me (213.108.105.57)

Analysis

SPF

SPF Policy Information Main policy

Analysis

DMARC

DMARC Policy Information

Analysis

MTA Strict Transport Security

MTA-STS Policy Indicator

Analysis

MTA-STS Policy

Analysis

Certificate: mta-sts.anonaddy.me

Analysis

Certificate Chain

Analysis

SMTP TLS Reporting

TLS-RPT Policy

Analysis

HTTP (80)

URL: http://anonaddy.me/

Analysis

URL: http://www.anonaddy.me/

Analysis

HTTP (443)

URL: https://anonaddy.me/

URL: https://www.anonaddy.me/

WWW TLS

TLS Configuration: anonaddy.me (185.70.196.149)

Analysis

TLS Configuration: anonaddy.me (2a04:3544:8000:1000:e8b5:6ff:fe29:56c)

Analysis