SSL check results of instantroot.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for instantroot.de 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

Report created Wed, 03 Sep 2025 20:17:19 +0000

The mailservers of instantroot.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @instantroot.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
petersen-it-services-de.mail.cloud.nospamproxy.com
193.37.132.21
10
supported
*.mail.cloud.nospamproxy.com
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
petersen-it-services-de.mail.cloud.nospamproxy.com
178.212.92.66
10
supported
*.mail.cloud.nospamproxy.com
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=*.mail.cloud.nospamproxy.com

Certificate chain
  • *.mail.cloud.nospamproxy.com
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption

      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption

Subject
Common Name (CN)
  • *.mail.cloud.nospamproxy.com
Alternative Names
  • *.mail.cloud.nospamproxy.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-08-04
Not valid after
2025-11-02
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
FA:D5:C4:46:36:39:6A:73:DB:B1:DF:42:7C:5F:81:37:AD:C4:D7:9C:6B:70:87:2E:C6:E2:7E:CD:18:A3:C8:EB
SHA1
56:22:A2:C7:81:8D:E8:3D:8D:D7:C5:E8:1C:1F:EF:9A:0F:00:E7:7A
X509v3 extensions
subjectKeyIdentifier
  • 45:CD:45:92:E0:B8:9B:30:66:42:F3:88:98:2C:4A:F5:2A:1E:36:C5
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r11.c.lencr.org/65.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 0D:E1:F2:30:2B:D3:0D:C1:40:62:12:09:EA:55:2E:FC:
  • 47:74:7C:B1:D7:E9:30:EF:0E:42:1E:B4:7E:4E:AA:34
  • Timestamp : Aug 4 07:19:25.541 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:19:F9:0D:F9:63:6C:AC:B5:E7:78:67:94:
  • 9F:8D:1A:3F:9B:2B:8D:47:8B:8E:2D:B5:41:76:19:57:
  • 9C:26:02:5C:02:20:56:24:DB:5A:98:43:2F:1F:83:FA:
  • 4B:4C:3A:3F:80:1D:95:41:F6:6B:5A:DD:CF:40:72:3A:
  • 71:F1:C9:DA:A7:F0
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 12:F1:4E:34:BD:53:72:4C:84:06:19:C3:8F:3F:7A:13:
  • F8:E7:B5:62:87:88:9C:6D:30:05:84:EB:E5:86:26:3A
  • Timestamp : Aug 4 07:19:25.585 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:D9:70:BE:F5:41:DE:4F:2B:12:5E:F3:
  • 33:E4:06:35:D3:C9:D3:BD:8D:37:D6:32:56:F3:AE:70:
  • 66:B0:A1:6F:4F:02:20:53:D1:D1:A7:DB:B8:9C:3E:D3:
  • 91:A8:7E:42:CA:D7:6A:32:B7:B4:1C:94:3E:84:0A:BC:
  • 22:73:8C:34:58:72:0F

DANE

DNS-based Authentication of Named Entities (DANE) is a protocol to allow X.509 certificates to be bound to DNS using TLSA records and DNSSEC.

Name Options DNSSEC Matches
_25._tcp.petersen-it-services-de.mail.cloud.nospamproxy.com
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid