SSL-Tools

SSL check results of aulhorn.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for aulhorn.net 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, 14 Apr 2025 22:12:25 +0000

The mailservers of aulhorn.net can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @aulhorn.net addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.aulhorn.net
2a02:247a:221:4a00:1::1
 10
supported
mail.aulhorn.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
mail.aulhorn.net
85.215.45.120
 10
supported
mail.aulhorn.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

We have received emails from these servers with @aulhorn.net sender addresses. Test mail delivery

Host TLS Version & Cipher
unknown (IPv6:2a01:488:66:1000:b24d:4deb:0:1)
TLSv1.3 TLS_AES_256_GCM_SHA384

Certificates

First seen at:

CN=mail.aulhorn.net

Certificate chain
  • mail.aulhorn.net
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.aulhorn.net
Alternative Names
  • mail.aulhorn.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2025-03-15
Not valid after
2025-06-13
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
E5:08:52:CC:8C:0B:EF:DD:D7:D4:EF:E0:2A:DB:2D:CD:6B:D0:F3:F1:6B:94:D6:F3:1E:9B:23:F4:52:D3:73:86
SHA1
FD:84:4D:4D:5F:D6:25:ED:E1:E8:80:FC:2C:57:F3:A8:3B:B0:E8:7B
X509v3 extensions
subjectKeyIdentifier
  • EC:22:E9:F6:12:1C:2F:49:CC:63:05:BA:D4:C6:40:34:A4:34:0F:24
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
crlDistributionPoints
  • Full Name:
  • URI:http://r10.c.lencr.org/74.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E3:0A:E4:45:EF:BD:AD:9B:7E:38:ED:47:67:77:53:
  • D7:82:5B:84:94:D7:2B:5E:1B:2C:C4:B9:50:A4:47:E7
  • Timestamp : Mar 15 23:40:45.103 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:48:BE:92:56:6B:B2:C1:15:82:50:DA:4B:
  • A2:62:B0:EB:8E:0B:BB:3B:D4:7D:7C:91:03:8C:BE:A6:
  • 81:37:7E:DE:02:21:00:C7:AD:08:96:54:A9:41:3C:C5:
  • 9C:7B:0A:95:3D:78:3F:79:1A:44:D6:54:CB:B0:6A:EA:
  • B3:74:63:D1:C7:8E:E9
  • 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 : Mar 15 23:40:45.144 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:1E:93:5A:B5:DC:B0:A0:BB:FE:26:16:62:
  • FA:85:C7:97:56:48:3F:B1:34:80:AE:13:03:4C:D6:33:
  • 4D:73:60:EE:02:20:2A:9F:93:51:50:1C:1B:85:C6:2E:
  • 12:87:AF:E9:BE:38:C7:6A:98:B3:7F:08:BE:0B:7B:97:
  • E9:12:93:76:49:A9