SSL-Tools

SSL check results of netcube.dk

NEW You can also bulk check multiple servers.

Discover if the mail servers for netcube.dk 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 Fri, 29 Mar 2024 08:19:20 +0000

The mailservers of netcube.dk can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @netcube.dk addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.netcube.dk
80.209.99.136
 10
supported
mail.netcube.dk
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
8 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.netcube.dk

Certificate chain
  • mail.netcube.dk
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.netcube.dk
Alternative Names
  • autoconfig.albog.dk
  • autoconfig.hmork.dk
  • autoconfig.netcube.dk
  • autoconfig.pernillejacobsen.dk
  • autodiscover.albog.dk
  • autodiscover.hmork.dk
  • autodiscover.netcube.dk
  • autodiscover.pernillejacobsen.dk
  • mail.netcube.dk
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-29
Not valid after
2024-06-27
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
64:EF:18:AD:0B:D4:92:AF:6B:6E:3C:03:94:87:1B:54:3C:56:D2:90:59:E5:F0:50:69:A2:6E:59:29:02:34:17
SHA1
1B:41:39:E2:41:76:79:93:A8:34:ED:5F:69:8B:16:AA:3F:DF:2C:A3
X509v3 extensions
subjectKeyIdentifier
  • D1:4A:2B:1E:A4:7E:79:00:93:0A:A3:4F:41:8E:1F:71:25:01:03:38
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 29 08:08:53.760 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:75:2E:BA:F9:F4:73:56:1A:67:E2:22:80:
  • F1:A6:5A:CD:19:F4:6B:46:AC:34:F1:28:A4:0F:D1:D9:
  • D1:4C:BB:06:02:20:5C:14:88:CD:71:2C:77:1C:4C:CE:
  • D8:CE:B4:25:81:3E:2B:F1:27:15:97:3F:88:D8:FA:D4:
  • D1:9B:D5:79:5E:81
  • 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 29 08:08:53.767 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:FB:F5:BD:2A:EF:F4:3D:DB:8A:3F:4A:
  • DD:ED:62:50:CB:78:EE:02:31:F8:BC:0B:42:B9:09:33:
  • EC:A8:36:0D:C0:02:20:6E:B6:A5:3C:E6:59:CD:88:8B:
  • 9F:AB:70:F1:3B:82:6C:AF:CE:97:45:2A:09:BC:BC:40:
  • 1A:A0:F1:5B:C5:E5:33

DANE

DNS-based Authentication of Named Entities (DANE) is a protocol to allow X.509 certificates to be bound to DNS using TLSA records and DNSSEC.

Name Options DNSSEC Matches
_25._tcp.mail.netcube.dk
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid