SSL-Tools

SSL check results of zapzap.dk

NEW You can also bulk check multiple servers.

Discover if the mail servers for zapzap.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 Mon, 08 Jun 2020 00:30:42 +0000

We can not guarantee a secure connection to the mailservers of zapzap.dk!

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

/mailservers/zapzap.dk

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mx.zapzap.dk
2001:470:6847::2
Results incomplete
10
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
mx.zapzap.dk
86.52.214.56
 10
supported
zapzap.dk
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • SSLv3
7 s

Outgoing Mails

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

Certificates

First seen at:

CN=zapzap.dk

Certificate chain
  • zapzap.dk
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
Subject
Common Name (CN)
  • zapzap.dk
Alternative Names
  • cloud.zapzap.dk
  • mail.zapzap.dk
  • mx.zapzap.dk
  • office.zapzap.dk
  • www.zapzap.dk
  • zapzap.dk
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • Let's Encrypt Authority X3
validity period
Not valid before
2020-04-15
Not valid after
2020-07-14
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
93:84:36:9C:18:F4:85:C1:9B:99:09:65:33:01:F2:9D:E1:C4:FF:B4:88:00:73:5C:DE:C1:3D:CE:F5:01:51:CE
SHA1
E3:7D:1F:3C:32:DB:71:BE:1A:79:60:F8:E2:69:DF:EF:DF:CC:A0:DE
X509v3 extensions
subjectKeyIdentifier
  • 91:6B:88:14:99:F9:F6:13:48:09:25:60:57:75:73:66:6F:DD:FF:F0
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 : F0:95:A4:59:F2:00:D1:82:40:10:2D:2F:93:88:8E:AD:
  • 4B:FE:1D:47:E3:99:E1:D0:34:A6:B0:A8:AA:8E:B2:73
  • Timestamp : Apr 15 04:28:28.763 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:67:58:C0:2A:50:90:3B:A6:52:86:B7:2F:
  • B2:F1:6A:4C:F7:7F:BD:5D:C2:9C:E6:B9:4C:5F:51:27:
  • BC:B4:55:C8:02:21:00:9D:25:EE:91:1B:A8:33:4D:DB:
  • 20:EB:6D:39:87:BA:DF:14:97:62:0B:C6:CC:2B:C0:3E:
  • 25:15:97:59:33:39:39
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 07:B7:5C:1B:E5:7D:68:FF:F1:B0:C6:1D:23:15:C7:BA:
  • E6:57:7C:57:94:B7:6A:EE:BC:61:3A:1A:69:D3:A2:1C
  • Timestamp : Apr 15 04:28:28.803 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:78:3B:16:CF:C0:DC:13:36:B3:CC:20:0D:
  • 9E:13:B6:9C:38:10:7C:7B:EE:12:6B:A3:E7:9C:D2:41:
  • 1B:0D:61:2E:02:21:00:8F:3A:AC:59:A6:1E:6E:3E:5A:
  • EE:A8:FD:BB:2F:93:F9:08:C5:B4:B1:57:00:EE:B0:98:
  • 53:F0:6D:EB:93:D7:63