SSL-Tools

SSL check results of stamann.dev

NEW You can also bulk check multiple servers.

Discover if the mail servers for stamann.dev 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 Sun, 07 Sep 2025 00:30:40 +0000

We can not guarantee a secure connection to the mailservers of stamann.dev!

Please contact the operator of stamann.dev and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/stamann.dev

Servers

Incoming Mails

These servers are responsible for incoming mails to @stamann.dev addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.stamann.online
85.215.51.19
 20
supported
mail.stamann.online
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
7 s
mx2.stamann.online
217.154.69.178
Results incomplete
200
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
7 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.stamann.online

Certificate chain
  • mail.stamann.online
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.stamann.online
Alternative Names
  • mail.stamann.online
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2025-08-13
Not valid after
2025-11-11
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
E7:47:96:48:E3:72:4E:AF:C8:58:DB:A1:5D:5D:1D:93:2B:25:F0:94:F5:28:6C:1C:52:98:C0:05:0C:56:A8:EE
SHA1
1A:4B:DF:9B:02:17:EF:26:7E:82:88:DA:09:A9:18:C4:FC:C3:D5:3F
X509v3 extensions
subjectKeyIdentifier
  • ED:5A:43:7D:1E:2C:9F:28:B9:FD:E4:D3:DE:91:93:18:B9:47:9C:4A
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r10.c.lencr.org/114.crl
ct_precert_scts
  • 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 : Aug 13 21:31:28.853 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:26:E2:E5:E4:57:B0:20:08:E9:44:B6:23:
  • 66:DC:87:4D:CF:78:F1:00:69:DB:B6:F5:39:08:3B:C5:
  • 20:4E:D2:05:02:21:00:B3:EF:25:EC:AE:6C:48:E3:FC:
  • CC:F9:9C:33:F7:A9:37:AA:CB:90:80:20:D3:81:A7:85:
  • F0:50:FA:6A:00:08:60
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A4:42:C5:06:49:60:61:54:8F:0F:D4:EA:9C:FB:7A:2D:
  • 26:45:4D:87:A9:7F:2F:DF:45:59:F6:27:4F:3A:84:54
  • Timestamp : Aug 13 21:31:28.836 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:7F:21:C1:27:B6:2F:3B:3A:FE:9D:BD:15:
  • 32:09:E9:28:0F:D2:9F:66:5C:A3:17:C8:39:1C:AD:92:
  • D9:40:6D:57:02:21:00:8F:B5:B2:5A:F8:48:79:58:DA:
  • 27:9A:9D:DD:50:52:E7:16:21:A0:8F:EF:B2:8D:D9:51:
  • 2A:C2:30:42:E4:C8:0F