SSL-Tools

SSL check results of rompe.org

NEW You can also bulk check multiple servers.

Discover if the mail servers for rompe.org 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 Sat, 21 Dec 2024 01:30:33 +0000

The mailservers of rompe.org can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @rompe.org addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.rompe.org
148.251.132.184
 10
supported
mail2.rompe.org
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
7 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail2.rompe.org

Certificate chain
  • mail2.rompe.org
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail2.rompe.org
Alternative Names
  • gate.rompe.org
  • imap.rompe.org
  • mail.rompe.org
  • mail2.rompe.org
  • neu.rompe.org
  • smtp.rompe.org
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2024-10-27
Not valid after
2025-01-25
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
74:06:2C:BB:55:D7:0C:20:DB:9F:4B:84:B3:4F:95:BA:F4:36:32:0E:27:49:47:7D:95:7F:54:28:DA:90:89:41
SHA1
14:5B:7D:66:D6:B6:71:86:29:CA:0C:11:1B:0F:32:E0:43:46:85:8D
X509v3 extensions
subjectKeyIdentifier
  • 21:9A:54:07:D6:7C:44:04:D7:3F:7C:FB:1A:FE:63:33:20:20:68:27
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : E6:D2:31:63:40:77:8C:C1:10:41:06:D7:71:B9:CE:C1:
  • D2:40:F6:96:84:86:FB:BA:87:32:1D:FD:1E:37:8E:50
  • Timestamp : Oct 27 20:55:06.021 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:5B:BB:A6:17:34:78:22:E8:CD:E6:AF:9E:
  • E2:F2:02:3F:29:21:86:79:18:A8:8F:23:CF:55:1D:60:
  • 4B:30:10:B2:02:21:00:BB:B4:ED:3C:9C:02:3B:6E:76:
  • 20:87:62:D7:86:35:A4:FD:88:AC:ED:96:DD:3A:24:10:
  • 88:02:A1:B1:E5:9F:96
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : E0:92:B3:FC:0C:1D:C8:E7:68:36:1F:DE:61:B9:96:4D:
  • 0A:52:78:19:8A:72:D6:72:C4:B0:4D:A5:6D:6F:54:04
  • Timestamp : Oct 27 20:55:06.020 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:55:F8:C2:55:B7:1F:CE:E6:FB:CD:B2:88:
  • 59:9C:B4:A1:D4:75:E9:A5:DA:A2:15:5C:B4:E0:27:77:
  • 37:6C:B7:75:02:20:18:CB:FE:0C:28:0E:86:46:EC:BC:
  • 1C:22:33:A0:CE:DA:14:77:C4:9D:45:7A:AD:42:A0:02:
  • 24:B0:57:67:05:40