SSL-Tools

SSL check results of adc.name

NEW You can also bulk check multiple servers.

Discover if the mail servers for adc.name 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 Fri, 23 Aug 2024 00:30:23 +0000

The mailservers of adc.name can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @adc.name addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
relay3.btnet.de
194.172.160.7
 10
supported
relay.btnet.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
relay1.btnet.de
217.78.136.7
 20
supported
relay.btnet.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
relay2.btnet.de
217.9.116.7
 30
supported
relay.btnet.de
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 @adc.name address so far. Test mail delivery

Certificates

First seen at:

CN=relay.btnet.de

Certificate chain
  • relay.btnet.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • relay.btnet.de
Alternative Names
  • relay.btnet.de
  • relay0.rittec.de
  • relay1.btnet.de
  • relay2.btnet.de
  • relay3.btnet.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2024-07-31
Not valid after
2024-10-29
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
00:D2:62:AA:3F:D8:75:80:5B:63:25:BC:4E:C3:9C:98:2B:54:14:78:96:38:87:C1:88:DC:6A:ED:58:6C:4E:DD
SHA1
5A:EF:B0:10:C1:EF:03:6F:34:BB:B9:56:2D:99:77:B8:E3:9E:35:0F
X509v3 extensions
subjectKeyIdentifier
  • E0:A2:86:25:1F:8F:24:78:B1:83:CB:56:C8:C4:2B:C8:5D:DB:1C:CD
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • OCSP - URI:http://r10.o.lencr.org
  • CA Issuers - URI:http://r10.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 : Jul 31 20:56:16.720 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:64:D9:4B:29:FD:09:7B:E3:CB:1A:46:BC:
  • 61:13:02:1E:E6:C2:F0:94:A7:E8:9F:9D:85:E8:CA:34:
  • 48:4E:07:9A:02:21:00:CA:87:9C:77:EC:73:47:2B:E1:
  • 5B:7B:93:7D:4D:E5:18:79:CA:6B:91:FD:92:66:7A:DB:
  • 08:69:35:DD:80:80:FE
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
  • 1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
  • Timestamp : Jul 31 20:56:17.732 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:43:02:20:5B:AE:72:55:AF:FB:58:60:EC:8C:8E:27:
  • 4D:F6:FA:07:3F:84:68:FC:94:D3:5F:FD:1A:68:3C:A8:
  • 93:9E:1F:84:02:1F:06:2B:57:A9:9D:FD:AE:11:6A:6A:
  • B0:CF:3B:6D:5C:F4:9C:F2:A1:D7:69:D3:A5:47:41:DB:
  • AC:37:90:7A:93