SSL-Tools

SSL check results of petrounet.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for petrounet.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, 15 Jul 2026 21:12:32 +0000

The mailservers of petrounet.com can be reached through a secure connection.

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.petrounet.com
2001:4ba0:ffeb:1b4::5
 10
supported
petrounet.com
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
mail.petrounet.com
193.111.198.185
 10
supported
petrounet.com
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=petrounet.com

Certificate chain
  • petrounet.com
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • YE1
        • remaining
        • 384 bit
        • ecdsa-with-SHA384
          • Root YE
            • remaining
            • 384 bit
            • ecdsa-with-SHA384
              • ISRG Root X2 (Certificate is self-signed.)
                • remaining
                • 384 bit
                • ecdsa-with-SHA384
Subject
Common Name (CN)
  • petrounet.com
Alternative Names
  • *.petrounet.com
  • petrounet.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • YE1
validity period
Not valid before
2026-07-15
Not valid after
2026-10-13
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
Fingerprints
SHA256
F8:A0:6E:AA:DF:EF:5D:BC:6F:E5:DB:5B:CF:7B:CA:5F:19:E1:D5:71:5B:80:F7:BC:DF:66:3F:8C:28:06:C0:06
SHA1
61:86:EA:44:AE:8F:A4:D3:03:C7:3B:06:2D:A1:59:77:7B:EC:8B:9B
X509v3 extensions
subjectKeyIdentifier
  • B2:AA:3A:BE:05:75:AB:63:BE:54:9C:75:35:FF:54:58:8A:FC:2D:EA
authorityKeyIdentifier
  • keyid:BB:20:CA:47:0B:FE:D7:E5:9C:F9:8F:09:2A:A3:8C:37:45:B1:BC:D8
authorityInfoAccess
  • CA Issuers - URI:http://ye1.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://ye1.c.lencr.org/95.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : D7:6D:7D:10:D1:A7:F5:77:C2:C7:E9:5F:D7:00:BF:F9:
  • 82:C9:33:5A:65:E1:D0:B3:01:73:17:C0:C8:C5:69:77
  • Timestamp : Jul 15 18:51:14.162 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:C5:4F:73:05:EB:B7:E0:96:59:7A:C8:
  • D2:85:64:CB:63:FA:C8:C7:C6:96:F4:59:90:8E:D9:23:
  • C9:83:F5:2A:5F:02:20:1E:8E:5F:0F:C2:56:E5:5B:22:
  • 3B:00:BC:63:BA:DD:F8:88:AA:5A:80:64:0F:DE:E3:A1:
  • F3:24:98:27:C0:71:A4
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 26:E3:64:6E:58:69:21:23:BC:34:3F:47:24:35:9B:37:
  • 92:CD:24:5A:88:D8:15:D3:93:33:FD:99:18:AB:47:23
  • Timestamp : Jul 15 18:51:13.459 2026 GMT
  • Extensions: 00:00:05:00:29:82:21:C2
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:95:9B:CA:AC:8F:50:21:7D:54:75:B7:
  • C2:16:92:FC:39:7E:AA:31:40:1C:16:6E:19:59:92:7F:
  • AB:0B:21:6C:67:02:20:08:50:6D:93:75:A4:E1:D9:61:
  • 9E:07:73:16:1F:38:11:8C:D3:E8:2D:11:BF:B5:AD:04:
  • BD:9E:8E:5E:93:16:5F

DANE

DNS-based Authentication of Named Entities (DANE) is a protocol to allow X.509 certificates to be bound to DNS using TLSA records and DNSSEC.

Name Options DNSSEC Matches
_25._tcp.mail.petrounet.com
  • DANE-TA: Trust Anchor Assertion
  • Use full certificate
  • SHA-256 Hash
valid
valid