SSL-Tools

SSL check results of pedrolucca.email

NEW You can also bulk check multiple servers.

Discover if the mail servers for pedrolucca.email can be reached through a secure connection.

To establish a secure connection a mail server has to offer STARTTLS (SSL), a trustworthy SSL certificate, support for the Diffie-Hellman-Algorithm to guarantee Perfect Forward Secrecy and must not be vulnerable against the Heartbleed attack. Futhermore we recommend using end-to-end encryption with GnuPG.

Summary

JSON Refresh

Report created Tue, 21 Oct 2025 00:30:18 +0000

The mailservers of pedrolucca.email can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @pedrolucca.email addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mx.actuallyreliable.com
2a01:4f8:c013:2672::1
 10
supported
mx.actuallyreliable.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
mx.actuallyreliable.com
128.140.90.251
 10
supported
mx.actuallyreliable.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

We have not received any emails from a @pedrolucca.email address so far. Test mail delivery

Certificates

First seen at:

CN=mx.actuallyreliable.com

Certificate chain
  • mx.actuallyreliable.com
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • E7
        • remaining
        • 384 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mx.actuallyreliable.com
Alternative Names
  • mx.actuallyreliable.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E7
validity period
Not valid before
2025-10-18
Not valid after
2026-01-16
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
5B:9B:39:43:F8:63:B4:5B:DB:77:08:99:00:3C:10:7C:3B:49:F6:82:04:EF:20:62:E9:54:DB:13:86:DB:DB:64
SHA1
AD:66:19:C6:2F:89:23:B9:B6:03:F9:9A:96:57:88:7C:10:09:98:B6
X509v3 extensions
subjectKeyIdentifier
  • 38:01:75:52:54:50:1A:55:80:97:01:DB:97:2A:71:40:56:A1:3C:6A
authorityKeyIdentifier
  • keyid:AE:48:9E:DC:87:1D:44:A0:6F:DA:A2:E5:60:74:04:78:C2:9C:00:80
authorityInfoAccess
  • CA Issuers - URI:http://e7.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://e7.c.lencr.org/38.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 64:11:C4:6C:A4:12:EC:A7:89:1C:A2:02:2E:00:BC:AB:
  • 4F:28:07:D4:1E:35:27:AB:EA:FE:D5:03:C9:7D:CD:F0
  • Timestamp : Oct 18 04:13:58.033 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:C4:A0:F6:AA:DF:14:DC:A7:A7:09:98:
  • B1:59:C8:20:F2:50:CE:D5:F5:8B:79:9C:C7:6A:9D:22:
  • 54:11:38:58:D3:02:20:38:54:8B:09:AD:38:02:34:58:
  • D6:B6:CC:7D:CB:0E:44:0E:AF:0F:58:9D:37:62:08:2C:
  • 7D:27:5E:79:AF:46:E3
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 19:86:D4:C7:28:AA:6F:FE:BA:03:6F:78:2A:4D:01:91:
  • AA:CE:2D:72:31:0F:AE:CE:5D:70:41:2D:25:4C:C7:D4
  • Timestamp : Oct 18 04:13:58.042 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:6E:6F:E2:3D:22:70:04:0D:7C:8F:0B:62:
  • 83:3A:4E:BC:90:EE:06:D0:95:7D:23:65:E6:C8:2F:96:
  • 3A:CD:E7:E2:02:21:00:B2:93:61:80:7B:93:AA:FB:46:
  • 04:4E:AD:73:33:54:EE:8A:0E:BF:F4:43:3F:9A:0C:8A:
  • 23:2D:52:8B:41:04:2A