SSL-Tools

SSL check results of mail.netpure.biz

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.netpure.biz 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 Thu, 25 Apr 2024 12:40:26 +0000

The mailservers of mail.netpure.biz can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @mail.netpure.biz addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.netpure.biz
144.76.101.254
 -
supported
netpure.biz
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s
mail.netpure.biz
2a01:4f8:192:41e2::2
 -
supported
netpure.biz
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
6 s

Outgoing Mails

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

Certificates

First seen at:

CN=netpure.biz

Certificate chain
  • netpure.biz
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • netpure.biz
Alternative Names
  • mail.netpure.biz
  • netpure.biz
  • www.netpure.biz
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-12
Not valid after
2024-06-10
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
70:7B:85:34:20:56:C2:30:A3:84:DC:F5:5B:2F:5B:9B:E9:16:86:E6:B5:A8:BF:8F:4C:D1:50:03:40:DE:C5:8B
SHA1
65:64:3E:A4:6F:83:76:8E:4D:AE:2E:CF:29:5B:AD:BF:1F:AC:BA:89
X509v3 extensions
subjectKeyIdentifier
  • 3C:E2:F8:B0:7E:E5:2B:1A:4D:FE:02:11:B0:24:94:E3:22:99:63:D1
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 12 20:05:19.487 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:98:86:A7:B3:25:A9:5C:2F:ED:0C:48:
  • F9:62:69:04:CB:EA:80:F6:08:05:F7:A2:CD:44:86:40:
  • 91:52:39:A2:E9:02:20:3E:1B:69:A1:8C:32:3F:B9:BF:
  • B1:66:59:9E:39:F0:5E:3B:58:C3:25:2D:58:F7:5D:FD:
  • D5:9F:DC:B2:38:12:DF
  • 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 12 20:05:19.994 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:B4:F1:20:16:B2:CD:4D:0B:3A:1B:DA:
  • 20:54:4A:18:D2:2A:6C:A7:A6:5D:AC:A2:88:DC:C1:BA:
  • 5D:7A:31:1A:DE:02:20:12:C5:CB:4F:6D:A0:BA:8C:15:
  • F5:EF:5F:77:B0:5E:CD:7E:B3:82:8B:99:A3:F3:10:86:
  • A8:AF:97:49:3A:F6:0A