SSL-Tools

SSL check results of mailservers.name

NEW You can also bulk check multiple servers.

Discover if the mail servers for mailservers.name 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 Thu, 13 Mar 2025 13:10:36 +0000

The mailservers of mailservers.name can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @mailservers.name addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
4.mailservers.name
85.163.54.136
 10
supported
mailservers.name
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s
3.mailservers.name
2a02:25b0:aaaa:aaaa:2e24:99bc:1cd::
Results incomplete
90 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s
3.mailservers.name
46.36.36.44
Results incomplete
90 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s

Outgoing Mails

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

Certificates

First seen at:

CN=mailservers.name

Certificate chain
  • mailservers.name
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • E5
        • remaining
        • 384 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mailservers.name
Alternative Names
  • 3.mailservers.name
  • 4.mailservers.name
  • mailservers.name
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E5
validity period
Not valid before
2025-03-12
Not valid after
2025-06-10
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
13:4A:5F:19:71:5E:EA:8E:8E:73:68:D3:5E:39:6C:2F:D8:44:99:ED:8D:96:99:32:21:10:7A:A0:BE:FE:37:D1
SHA1
0E:D0:F5:A9:1A:9A:1E:97:5C:B1:3F:F0:CA:7C:8C:F7:07:EA:10:B8
X509v3 extensions
subjectKeyIdentifier
  • B5:33:41:F0:91:55:D4:29:3F:BB:BE:F8:B4:5D:04:96:CC:03:6E:1B
authorityKeyIdentifier
  • keyid:9F:2B:5F:CF:3C:21:4F:9D:04:B7:ED:2B:2C:C4:C6:70:8B:D2:D7:0D
authorityInfoAccess
  • OCSP - URI:http://e5.o.lencr.org
  • CA Issuers - URI:http://e5.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7D:59:1E:12:E1:78:2A:7B:1C:61:67:7C:5E:FD:F8:D0:
  • 87:5C:14:A0:4E:95:9E:B9:03:2F:D9:0E:8C:2E:79:B8
  • Timestamp : Mar 12 16:00:33.468 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:23:7D:D2:7F:06:43:B9:18:0E:6E:94:74:
  • C1:88:10:DF:D6:F4:81:BB:C3:F0:76:D6:2D:AB:EF:3B:
  • 87:3D:A2:B5:02:21:00:DA:D0:67:8B:45:2B:34:20:A9:
  • F9:A0:21:A6:C6:73:B9:03:A6:30:6C:A2:6A:52:BE:3E:
  • 3F:8F:BC:DA:19:14:E6
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:
  • 22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0
  • Timestamp : Mar 12 16:00:33.494 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:5C:A2:E7:66:77:0C:8B:F0:45:E0:BC:30:
  • 89:99:4B:00:E8:A5:4C:5A:EC:1E:1C:4F:D2:E7:50:35:
  • 3D:E3:D8:A2:02:21:00:B4:AE:E1:D0:53:76:2F:7D:8E:
  • 69:04:42:A6:DE:B5:4F:1E:3D:9B:E0:BD:C6:97:8D:C5:
  • 51:AE:51:BE:AB:53:21