SSL-Tools

SSL check results of rossi.team

NEW You can also bulk check multiple servers.

Discover if the mail servers for rossi.team 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 Mon, 31 Aug 2026 09:43:35 +0000

The mailservers of rossi.team can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @rossi.team addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mx2.rossi.team
2a00:6d40:40:6310::1
 10
supported
*.rossi.team
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s
mx2.rossi.team
77.81.226.16
 10
supported
*.rossi.team
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=*.rossi.team

Certificate chain
  • *.rossi.team
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • YE1
        • remaining
        • 384 bit
        • ecdsa-with-SHA384
          • Root YE
            • remaining
            • 384 bit
            • ecdsa-with-SHA384
              • ISRG Root X2 (Certificate is self-signed.)
                • remaining
                • 384 bit
                • ecdsa-with-SHA384
Subject
Common Name (CN)
  • *.rossi.team
Alternative Names
  • *.rossi.team
  • rossi.team
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • YE1
validity period
Not valid before
2026-08-08
Not valid after
2026-11-06
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
Fingerprints
SHA256
52:D7:38:3E:10:A3:41:95:A9:6B:6D:8C:4B:EE:CD:8B:8C:0F:1B:AA:C3:3A:82:B4:AC:59:83:D1:92:F9:A1:B8
SHA1
EA:9B:A6:A2:6A:AF:EA:1B:C6:96:90:55:DD:CA:80:50:3A:6F:81:0E
X509v3 extensions
subjectKeyIdentifier
  • A0:7A:AE:40:F6:ED:B0:46:6C:82:70:80:2C:C0:F8:0B:54:81:F8:66
authorityKeyIdentifier
  • keyid:BB:20:CA:47:0B:FE:D7:E5:9C:F9:8F:09:2A:A3:8C:37:45:B1:BC:D8
authorityInfoAccess
  • CA Issuers - URI:http://ye1.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://ye1.c.lencr.org/82.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : AF:67:88:3B:57:B0:4E:DD:8F:A6:D9:7E:F6:2E:A8:EB:
  • 81:0A:C7:71:60:F0:24:5E:55:D6:0C:2F:E7:85:87:3A
  • Timestamp : Aug 8 14:25:12.717 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:9A:90:3E:05:78:FC:50:F2:9C:86:50:
  • 8E:85:04:9B:79:1B:02:E4:5C:18:73:8D:0A:7E:7E:81:
  • 9E:B9:C9:88:2E:02:21:00:E4:DC:FD:59:5B:B8:41:9E:
  • C9:F4:A3:4C:08:24:9A:09:44:33:5C:5D:69:DB:A2:CE:
  • 70:36:71:F1:D0:9B:D3:3C
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 6C:FE:50:19:43:A8:5E:A9:16:BC:52:D1:33:E4:DC:C9:
  • 1E:F1:41:1C:7D:25:84:20:D1:73:80:9E:18:18:EB:3A
  • Timestamp : Aug 8 14:25:12.993 2026 GMT
  • Extensions: 00:00:05:00:1A:E8:85:21
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:6D:3D:A3:84:90:A3:E4:F6:2F:D5:0D:98:
  • 10:F8:6E:07:F1:ED:FA:DD:D6:1A:F3:29:76:A1:5C:65:
  • 44:5A:63:1B:02:20:18:48:43:3B:48:03:C5:8F:ED:41:
  • 5A:C8:B4:41:7A:91:B8:21:67:63:E9:24:D0:BA:93:9B:
  • 24:37:F0:8D:B3:9E