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 Tue, 11 Jun 2024 13:44:14 +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
Results incomplete
- not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 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-05-12
Not valid after
2024-08-10
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
99:95:42:8B:D0:96:1C:4F:61:EE:4A:B8:6C:B5:6A:E7:CD:D6:C7:B8:F0:F0:95:57:3E:43:0A:27:48:CB:01:E1
SHA1
10:46:E2:DC:87:5D:B1:0A:75:1E:DB:B1:50:32:48:54:1E:D0:F9:7E
X509v3 extensions
subjectKeyIdentifier
  • B9:7C:9A:BB:73:5E:5A:85:5C:B9:93:71:B5:94:1C:2A:4F:6A:12:A3
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 : May 12 06:33:01.975 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:71:59:7E:CE:51:6B:8D:32:FA:F0:4C:67:
  • F2:95:29:C4:10:69:16:C7:F0:B0:26:14:65:9D:1E:50:
  • BD:0F:77:A9:02:20:30:96:DA:66:63:F1:C5:01:A0:61:
  • 11:78:8A:E7:BB:61:2C:41:73:20:00:A3:36:59:F3:FA:
  • 25:21:37:07:F8:96
  • 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 : May 12 06:33:01.978 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:1D:A1:C6:5E:34:6D:B2:6D:89:7B:C5:56:
  • 72:47:F6:89:25:20:0C:86:CD:3A:67:D5:3D:1F:2E:36:
  • EC:56:1D:30:02:21:00:A5:78:AD:69:30:01:E5:B7:EC:
  • 58:DE:54:A1:F1:F2:DC:41:87:81:82:EE:4C:FE:EF:DC:
  • 4C:5F:16:38:E8:63:03