SSL-Tools

SSL check results of roelscheper.nl

NEW You can also bulk check multiple servers.

Discover if the mail servers for roelscheper.nl 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 Wed, 24 Apr 2024 09:59:22 +0000

The mailservers of roelscheper.nl can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @roelscheper.nl addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.roelscheper.nl
2001:67c:b30:897a::1
 10
supported
roelscheper.nl
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
mail.roelscheper.nl
5.254.39.18
 10
supported
roelscheper.nl
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=roelscheper.nl

Certificate chain
  • roelscheper.nl
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • roelscheper.nl
Alternative Names
  • *.roelscheper.nl
  • roelscheper.nl
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-24
Not valid after
2024-07-23
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
E0:49:5A:B8:B1:E5:9B:6F:81:F6:17:52:9F:F4:D8:E8:D9:9C:F9:2A:46:6E:53:61:C0:B6:EB:FE:0E:2A:D8:2E
SHA1
38:80:27:4D:D7:72:A5:0D:93:57:A9:10:38:2C:3F:68:26:A3:8A:7A
X509v3 extensions
subjectKeyIdentifier
  • 24:1C:30:2B:6F:41:79:A1:6A:25:58:1A:62:C2:43:C1:1E:69:E4:F0
authorityKeyIdentifier
  • keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
authorityInfoAccess
  • OCSP - URI:http://r3.o.lencr.org
  • CA Issuers - URI:http://r3.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 3F:17:4B:4F:D7:22:47:58:94:1D:65:1C:84:BE:0D:12:
  • ED:90:37:7F:1F:85:6A:EB:C1:BF:28:85:EC:F8:64:6E
  • Timestamp : Apr 24 08:38:44.041 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:EF:66:09:14:5B:F6:5D:02:F7:C5:B4:
  • A8:D4:9A:93:94:5E:DE:81:6C:C5:40:28:F6:F0:EF:BF:
  • D6:DD:3B:CD:63:02:21:00:C5:30:5E:27:C6:9C:EE:FE:
  • 20:FF:BF:87:75:FA:ED:D6:F6:25:05:8A:00:FA:D6:80:
  • 48:D9:5F:37:1C:F8:B3:95
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DF:E1:56:EB:AA:05:AF:B5:9C:0F:86:71:8D:A8:C0:32:
  • 4E:AE:56:D9:6E:A7:F5:A5:6A:01:D1:C1:3B:BE:52:5C
  • Timestamp : Apr 24 08:38:44.233 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:17:06:09:C1:CB:43:D2:76:F0:04:92:89:
  • 4D:D1:96:22:BB:48:1B:7D:34:4C:C9:41:04:02:49:52:
  • E4:E3:31:BE:02:21:00:92:A1:E2:1D:74:55:DB:0D:0D:
  • F4:EF:2D:7A:60:D8:A4:FF:7E:D3:1C:01:6D:D3:9F:78:
  • C1:F3:B1:EA:F5:BA:E3