SSL-Tools

SSL check results of mailcity.ws

NEW You can also bulk check multiple servers.

Discover if the mail servers for mailcity.ws 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 19:27:10 +0000

The mailservers of mailcity.ws can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @mailcity.ws addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.mailcity.ws
2001:470:1f15:819::25
 10
supported
mail.mailcity.ws
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
6 s
mail.mailcity.ws
77.249.184.51
 10
supported
mail.mailcity.ws
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.mailcity.ws

Certificate chain
  • mail.mailcity.ws
    • remaining
    • 256 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.mailcity.ws
Alternative Names
  • mail.mailcity.ws
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-15
Not valid after
2024-06-13
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
3C:64:B9:E0:B6:BF:3F:16:3F:72:38:30:0D:40:34:0C:12:F7:58:1B:40:B5:F9:29:A4:7A:BB:BF:4E:2F:FE:49
SHA1
DE:7D:5C:05:7C:FF:F1:82:5F:CC:07:9E:0F:5B:A6:3D:D2:FD:16:84
X509v3 extensions
subjectKeyIdentifier
  • F8:0E:FB:F4:D8:F9:1B:48:80:DE:12:80:D2:1D:52:25:1A:E3:43:11
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 15 10:40:30.137 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:C9:27:6D:10:2E:1A:A7:C8:4C:92:18:
  • 20:15:A9:51:D1:09:7C:B0:78:26:2A:29:AC:36:B4:03:
  • E6:76:38:34:F0:02:20:07:8F:C4:C5:C9:97:B3:7C:82:
  • 3E:8D:B5:06:5D:73:A8:E4:98:30:A0:C7:36:C5:CF:CB:
  • B7:B2:EE:F7:37:AA:56
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
  • 32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
  • Timestamp : Mar 15 10:40:30.133 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:6D:48:EC:D7:78:67:60:59:6A:8A:91:A0:
  • 8A:FD:B9:72:68:C9:6A:3F:99:47:7C:16:13:7A:59:5E:
  • FE:EF:55:F1:02:21:00:EF:C1:AA:34:2E:BC:65:86:88:
  • D0:43:6B:E5:8E:D4:B7:64:EC:B9:A1:A9:6F:2A:C0:8B:
  • 02:5E:FA:4D:AF:F3:FE

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.mailcity.ws
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid