SSL-Tools

SSL check results of smtp-in.bulkprosend.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for smtp-in.bulkprosend.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 Mon, 05 May 2025 08:09:36 +0000

The mailservers of smtp-in.bulkprosend.com can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @smtp-in.bulkprosend.com addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
smtp-in.bulkprosend.com
45.133.148.3
 -
supported
*.bulkprosend.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
3 s
smtp-in.bulkprosend.com
2a00:ab00:403:1:133:148::3
 -
supported
*.bulkprosend.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
4 s

Outgoing Mails

We have not received any emails from a @smtp-in.bulkprosend.com address so far. Test mail delivery

Certificates

First seen at:

CN=*.bulkprosend.com

Certificate chain
  • *.bulkprosend.com
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • *.bulkprosend.com
Alternative Names
  • *.bulkprosend.com
  • bulkprosend.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-04-01
Not valid after
2025-06-30
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
26:07:18:FA:65:F6:98:01:D2:29:FF:B6:60:8C:A0:75:02:50:7E:B0:98:12:4E:83:30:4D:B2:77:E6:E9:B2:FF
SHA1
9D:F2:F6:BC:FF:F1:6F:00:84:C6:8A:93:67:C8:A1:BA:80:55:EB:E8
X509v3 extensions
subjectKeyIdentifier
  • 5C:E1:BA:63:09:D3:E3:23:31:53:41:18:B6:5B:57:74:B2:56:D4:3A
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r11.c.lencr.org/13.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:
  • 22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0
  • Timestamp : Apr 1 15:15:48.658 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:8E:B5:D6:4B:9C:C4:C6:8B:2B:E0:55:
  • 45:E5:DA:1D:D2:EA:ED:E2:22:77:2F:49:4A:83:BE:CA:
  • 50:45:61:1E:2E:02:21:00:9E:2C:52:02:47:98:FB:6A:
  • 48:29:DB:ED:E7:B3:8A:12:F9:86:E3:39:D7:18:B6:EF:
  • 9E:2D:AF:99:E5:49:E5:73
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 4E:75:A3:27:5C:9A:10:C3:38:5B:6C:D4:DF:3F:52:EB:
  • 1D:F0:E0:8E:1B:8D:69:C0:B1:FA:64:B1:62:9A:39:DF
  • Timestamp : Apr 1 15:15:48.618 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:46:27:68:96:2C:06:69:9B:E3:E0:83:82:
  • DA:B5:3B:AA:48:EC:5C:A5:D6:D9:C8:29:D8:B6:97:8C:
  • 60:68:21:FD:02:20:70:7B:37:02:4F:7D:0D:64:46:FD:
  • 8E:B3:21:4E:4D:AD:CA:73:1C:C0:B3:66:F7:AF:DD:77:
  • AA:2A:F1:35:2C:6D
tlsfeature
  • status_request