SSL-Tools

SSL check results of foxular.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for foxular.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, 29 Apr 2024 02:49:26 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
umbreon.foxular.net
2a01:4f8:1c0c:74aa::
 10
supported
foxular.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s
umbreon.foxular.net
195.201.100.157
 10
supported
foxular.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=foxular.net

Certificate chain
  • foxular.net
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • foxular.net
Alternative Names
  • foxular.net
  • mail.foxular.net
  • umbreon.foxular.net
  • www.foxular.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-31
Not valid after
2024-06-29
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
61:BF:EB:E0:02:93:07:AC:92:21:CC:42:75:1D:0F:D2:07:5F:35:EE:A0:C7:EB:CC:37:88:B7:6A:F9:2D:62:F7
SHA1
E3:08:22:C3:42:53:43:64:E9:4D:D6:09:72:20:16:A5:61:5F:FB:B7
X509v3 extensions
subjectKeyIdentifier
  • 34:6F:48:7F:91:C4:96:8B:9E:F3:E6:34:48:0D:71:CE:9B:53:0C:02
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 : 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 : Mar 31 10:30:48.188 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:E1:5B:D8:AF:EC:8F:8B:8D:F0:51:B7:
  • 58:D1:A5:B7:93:E9:F6:5D:D2:9B:51:C4:28:C8:CC:C9:
  • 9E:F6:58:44:20:02:20:72:F9:64:69:69:D1:23:96:70:
  • 48:B2:F4:2A:9D:B7:64:00:E7:27:CA:15:4F:D5:88:F6:
  • C1:3D:FA:D7:3F:21:69
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 3B:53:77:75:3E:2D:B9:80:4E:8B:30:5B:06:FE:40:3B:
  • 67:D8:4F:C3:F4:C7:BD:00:0D:2D:72:6F:E1:FA:D4:17
  • Timestamp : Mar 31 10:30:48.202 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:00:DA:0C:D7:6C:94:7A:4C:C4:D3:EE:B4:
  • 68:49:D2:ED:B9:1F:4B:6E:0F:AC:1A:4E:B6:C0:B4:64:
  • BB:12:57:1C:02:20:4C:E5:CD:47:88:14:3C:BD:3D:96:
  • 86:FD:61:8A:F2:FB:D1:F8:C1:4C:0E:D8:FE:9D:AD:81:
  • 10:CE:42:6D:40:18