SSL check results of ferusfragum.science

NEW You can also bulk check multiple servers.

Discover if the mail servers for ferusfragum.science 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 Sun, 06 Oct 2019 21:25:47 +0000

We can not guarantee a secure connection to the mailservers of ferusfragum.science!

Please contact the operator of ferusfragum.science and ask him or her to solve this problem. This result stays accessible under the following address:

https://ssl-tools.net/mailservers/ferusfragum.science

Servers

Incoming Mails

These servers are responsible for incoming mails to @ferusfragum.science addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
ferusfragum.science
2a01:4f8:221:1441::2
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
ferusfragum.science
188.40.82.62
10
supported
ferusfragum.science
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
11 s

Outgoing Mails

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

Certificates

First seen at:

CN=ferusfragum.science

Certificate chain
  • ferusfragum.science
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
    • Unknown Authority

      Let's Encrypt Authority X3
Subject
Common Name (CN)
  • ferusfragum.science
Alternative Names
  • ferusfragum.science
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • Let's Encrypt Authority X3
validity period
Not valid before
2019-09-22
Not valid after
2019-12-21
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
D6:77:0E:99:B8:5B:6D:3B:C6:D5:48:5F:17:CB:9B:57:7F:C6:C0:16:5C:26:E7:2F:79:2B:89:04:D0:87:73:11
SHA1
03:8B:E3:3C:CA:72:8D:C2:74:9B:DC:DE:84:3A:7C:3C:71:14:B2:D8
X509v3 extensions
subjectKeyIdentifier
  • 0D:70:0D:B7:BB:86:88:2A:E0:63:F7:C2:83:CD:E4:75:1A:34:F0:51
authorityKeyIdentifier
  • keyid:A8:4A:6A:63:04:7D:DD:BA:E6:D1:39:B7:A6:45:65:EF:F3:A8:EC:A1
authorityInfoAccess
  • OCSP - URI:http://ocsp.int-x3.letsencrypt.org
  • CA Issuers - URI:http://cert.int-x3.letsencrypt.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
  • Policy: 1.3.6.1.4.1.44947.1.1.1
  • CPS: http://cps.letsencrypt.org
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : E2:69:4B:AE:26:E8:E9:40:09:E8:86:1B:B6:3B:83:D4:
  • 3E:E7:FE:74:88:FB:A4:8F:28:93:01:9D:DD:F1:DB:FE
  • Timestamp : Sep 22 05:18:56.559 2019 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:92:AC:A5:AC:BD:83:53:B6:8C:1A:F9:
  • CB:51:6D:43:2D:71:9C:B9:35:1B:09:53:97:FD:E2:CE:
  • 84:EC:21:D9:86:02:21:00:90:8B:96:99:23:E4:03:D6:
  • 64:EF:9C:3E:57:82:B4:E3:F7:28:19:1E:C6:39:C5:91:
  • 1E:9C:35:46:2F:7C:61:8C
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 63:F2:DB:CD:E8:3B:CC:2C:CF:0B:72:84:27:57:6B:33:
  • A4:8D:61:77:8F:BD:75:A6:38:B1:C7:68:54:4B:D8:8D
  • Timestamp : Sep 22 05:18:56.590 2019 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:2C:C2:D2:0C:E4:B8:56:9C:A4:B1:08:5A:
  • D6:1C:4C:23:EC:44:6F:7A:6C:E6:A8:2C:5E:2D:51:5B:
  • 64:C7:20:00:02:20:14:94:71:F0:85:88:4E:0B:0B:5E:
  • E8:6F:20:2D:17:09:6D:2E:FC:47:68:19:AE:0F:B5:3D:
  • D7:9D:46:3C:F1:38