SSL-Tools

SSL check results of skryt.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for skryt.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:47:02 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.skryt.net
45.80.168.176
 10
supported
mail.skryt.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
3 s
mailfb.skryt.net
81.172.142.22
 20
supported
mail.skryt.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
3 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.skryt.net

Certificate chain
  • mail.skryt.net
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.skryt.net
Alternative Names
  • autoconfig.skryt.net
  • autoconfig.xornet.nl
  • autodiscover.skryt.net
  • autodiscover.xornet.nl
  • mail.skryt.net
  • mailfb.skryt.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2025-03-19
Not valid after
2025-06-17
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
02:F2:2B:E6:7B:1B:06:B1:78:F2:EE:5F:33:FB:E5:08:2C:8E:3A:54:D7:F8:5F:59:26:15:64:67:5A:BC:0C:55
SHA1
E7:55:82:78:0D:5B:CC:0F:0A:63:C9:CB:97:79:87:E2:46:70:F5:D1
X509v3 extensions
subjectKeyIdentifier
  • C7:34:0C:AA:5A:44:3F:70:B9:8E:C9:92:1F:64:58:08:01:55:58:35
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/106.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 19 03:01:38.257 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:96:C5:DC:B9:5B:AC:1A:7C:F6:85:15:
  • 01:41:6C:D2:E0:5E:D7:7C:0A:E6:44:0E:A2:92:0B:7C:
  • 33:FC:17:48:53:02:20:39:75:16:1E:94:A5:24:C3:46:
  • 91:9C:F0:05:44:E1:34:B8:FF:E5:36:56:E3:68:E9:D1:
  • A8:C8:00:BD:22:66:36
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:
  • 22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0
  • Timestamp : Mar 19 03:01:40.289 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:A0:45:B4:85:3D:DE:19:8E:FD:1A:AD:
  • 04:72:50:72:09:47:12:92:C4:42:4A:9E:08:08:C5:DB:
  • 4A:4A:85:13:01:02:21:00:E2:E7:39:EE:E1:EE:FE:1A:
  • CE:E9:5B:45:D5:37:BE:8D:55:C6:2D:7C:47:80:3C:73:
  • 8C:4C:97:67:E5:78:DE:74