SSL-Tools

SSL check results of paste.org

NEW You can also bulk check multiple servers.

Discover if the mail servers for paste.org 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 Sat, 06 Mar 2021 06:27:16 +0000

We can not guarantee a secure connection to the mailservers of paste.org!

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

/mailservers/paste.org

Servers

Incoming Mails

These servers are responsible for incoming mails to @paste.org addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.paste.org
203.57.114.33
 10
supported
mail.paste.org
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
supported
  • SSL_RSA_WITH_RC4_128_SHA
  • TLSv1.2
  • SSLv3
11 s
diurnal.kray.net.au
103.230.158.154
Results incomplete
20
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
3 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.paste.org

Certificate chain
  • mail.paste.org
    • 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.paste.org
Alternative Names
  • mail.paste.org
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-02-25
Not valid after
2021-05-26
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
1A:6B:7D:7A:E9:DE:A5:E8:0C:93:53:14:BF:CF:41:C4:93:78:D0:FD:DE:53:BF:41:E3:E0:A3:F9:40:2A:16:D0
SHA1
B3:B0:F3:D6:6D:4E:EF:06:15:52:09:3E:1A:17:26:4C:5E:39:02:9C
X509v3 extensions
subjectKeyIdentifier
  • BD:C5:F3:55:8B:3E:34:68:20:39:BC:23:20:17:94:F9:31:C6:C4:F0
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 : 5C:DC:43:92:FE:E6:AB:45:44:B1:5E:9A:D4:56:E6:10:
  • 37:FB:D5:FA:47:DC:A1:73:94:B2:5E:E6:F6:C7:0E:CA
  • Timestamp : Feb 25 18:19:23.097 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:92:9A:4B:AF:00:C4:59:5A:2C:AF:7D:
  • 06:87:70:4B:F5:CE:E6:BC:91:DD:F5:D2:FB:85:09:D7:
  • B1:4D:37:A9:33:02:21:00:CE:AC:99:12:F9:0B:B3:CB:
  • 7A:48:CE:D7:EE:1A:1F:30:66:21:0C:25:82:9D:84:FE:
  • DB:37:41:42:B8:B1:13:3E
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
  • 79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
  • Timestamp : Feb 25 18:19:23.139 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:D2:69:BE:39:AE:53:6B:B0:61:A9:05:
  • 2E:FB:7D:DF:FE:95:16:62:FB:CA:89:88:90:2F:C9:D0:
  • 6A:F1:E7:42:0F:02:21:00:D9:F3:94:AE:59:1A:40:F6:
  • 61:9D:E2:89:65:D6:00:9C:99:B0:EC:09:B7:B0:78:78:
  • 97:6B:85:98:60:48:62:98