SSL-Tools

SSL check results of mail.nuriyaa.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.nuriyaa.com 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 Wed, 20 Jan 2021 12:27:50 +0000

The mailservers of mail.nuriyaa.com can be reached through an encrypted connection.

However, we found problems that may affect the security.

Servers

Incoming Mails

These servers are responsible for incoming mails to @mail.nuriyaa.com addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.nuriyaa.com
31.220.59.188
 -
supported
mail.nuriyaa.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
supported
  • ECDHE_RSA_WITH_RC4_128_SHA
  • SSL_RSA_WITH_RC4_128_SHA
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
16 s
mail.nuriyaa.com
2a02:4780:1:1::1:8c1a
 -
supported
mail.nuriyaa.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
supported
  • ECDHE_RSA_WITH_RC4_128_SHA
  • SSL_RSA_WITH_RC4_128_SHA
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
16 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.nuriyaa.com

Certificate chain
  • mail.nuriyaa.com
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • DST Root CA X3 (Certificate is self-signed.)
            • remaining
            • 2048 bit
            • sha1WithRSAEncryption
Subject
Common Name (CN)
  • mail.nuriyaa.com
Alternative Names
  • mail.nuriyaa.com
  • www.mail.nuriyaa.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-01-13
Not valid after
2021-04-13
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
70:73:0A:73:8D:71:5F:AA:EB:AB:B6:C5:40:33:FD:29:0F:3D:7C:1B:E7:9B:F3:AC:01:37:A8:96:70:A1:35:2B
SHA1
7F:C7:D1:33:CE:16:6B:55:2F:F5:55:07:95:0C:64:44:59:6C:9A:96
X509v3 extensions
subjectKeyIdentifier
  • 1C:A8:59:DA:C2:EE:91:8C:7F:05:74:DA:EB:4F:22:24:90:8E:5E:B8
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
  • 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 : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
  • 15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
  • Timestamp : Jan 13 09:36:29.123 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:01:A5:BC:17:EC:75:73:28:A0:4B:AA:28:
  • 0D:7C:FF:D9:2C:3A:BC:13:57:8A:62:3D:DB:1B:5B:26:
  • 56:F1:7A:A4:02:20:06:90:1E:C9:D3:18:26:60:56:3C:
  • 9A:1C:44:18:20:A2:78:10:EF:B2:5D:28:88:7D:C4:AF:
  • 85:4E:31:37:50:16
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
  • E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
  • Timestamp : Jan 13 09:36:29.427 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:18:0F:C6:37:48:4C:20:12:87:64:B9:37:
  • 52:2A:5A:FE:B4:C6:6A:D7:D4:E3:7E:CC:B2:DB:7E:CB:
  • 63:67:DC:DB:02:21:00:C7:89:F5:35:AC:3F:0A:CD:71:
  • F9:C3:51:BE:C0:B8:2F:B0:CB:88:F7:38:9B:99:BD:74:
  • 84:F7:F8:FB:B2:A7:C8