SSL-Tools

SSL check results of whiteagle.eu

NEW You can also bulk check multiple servers.

Discover if the mail servers for whiteagle.eu 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 Thu, 28 Mar 2024 21:17:39 +0000

The mailservers of whiteagle.eu can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @whiteagle.eu addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.whiteagle.eu
87.106.136.33
 5
supported
whiteagle.eu
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 @whiteagle.eu address so far. Test mail delivery

Certificates

First seen at:

CN=whiteagle.eu

Certificate chain
  • whiteagle.eu
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • whiteagle.eu
Alternative Names
  • autoconfig.whiteagle.eu
  • autodiscover.whiteagle.eu
  • ftp.whiteagle.eu
  • mail.whiteagle.eu
  • ocean.whiteagle.eu
  • whiteagle.eu
  • www.whiteagle.eu
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-28
Not valid after
2024-06-26
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
96:14:34:95:C3:AD:9E:76:C1:2D:40:1D:91:B3:9F:41:2F:50:73:ED:4F:B0:D3:B6:B9:98:40:03:01:67:E7:7F
SHA1
39:42:2C:16:4F:65:E9:E5:31:D4:DA:6C:EB:D7:A8:25:4B:D5:7B:C9
X509v3 extensions
subjectKeyIdentifier
  • ED:56:B7:47:99:5B:33:E0:E3:8A:E5:18:FB:17:40:C5:E7:08:8B:76
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 : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
  • 32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
  • Timestamp : Mar 28 13:45:23.527 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:1C:3C:70:84:48:19:59:9B:D1:18:82:70:
  • 60:76:36:FE:ED:52:B5:F1:D5:CA:6A:9B:07:62:55:72:
  • 62:0E:79:12:02:20:6E:74:C0:30:83:DB:8E:08:1F:CF:
  • E4:E3:B6:CA:19:19:63:C3:EA:6B:3B:F1:A2:9E:06:2C:
  • 67:65:D4:9C:D4:3A
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E2:BF:D6:1E:DE:2F:2F:07:A0:D6:4E:6D:37:A7:DC:
  • 65:43:B0:C6:B5:2E:A2:DA:B7:8A:F8:9A:6D:F5:17:D8
  • Timestamp : Mar 28 13:45:23.524 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:67:F5:C9:C8:ED:95:9C:49:B8:91:AE:DE:
  • 67:B8:E4:03:50:AE:2A:D0:1A:C3:8C:71:CC:4F:C6:28:
  • 29:55:E1:28:02:20:59:F9:D6:33:0F:78:43:46:F5:48:
  • BE:F0:84:FC:51:72:42:17:1A:8A:CA:3B:F4:0D:D5:E8:
  • 84:52:24:91:03:B6