SSL-Tools

SSL check results of m0.rg.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for m0.rg.net 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, 20 Nov 2024 01:30:56 +0000

The mailservers of m0.rg.net can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @m0.rg.net addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
m0.rg.net
198.180.152.22
 -
supported
m0.rg.net
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • SSLv3
12 s
m0.rg.net
2001:418:3807::22
 -
supported
m0.rg.net
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • SSLv3
12 s

Outgoing Mails

We have not received any emails from a @m0.rg.net address so far. Test mail delivery

Certificates

First seen at:

CN=m0.rg.net

Certificate chain
  • m0.rg.net
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • E6
        • remaining
        • 384 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • m0.rg.net
Alternative Names
  • m0.rg.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E6
validity period
Not valid before
2024-10-21
Not valid after
2025-01-19
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
30:2A:0B:37:9A:14:CF:52:46:8A:33:F4:FC:9A:9A:4A:05:4E:2A:B7:3C:34:D4:AE:5B:DA:AA:BA:82:36:77:FF
SHA1
E5:36:92:4E:3E:4A:7F:00:5D:74:6E:66:DC:80:79:CE:50:C5:9E:69
X509v3 extensions
subjectKeyIdentifier
  • E0:E2:29:2E:50:45:15:8E:C2:A5:D6:DD:5E:17:FE:C1:5A:EA:17:D4
authorityKeyIdentifier
  • keyid:93:27:46:98:03:A9:51:68:8E:98:D6:C4:42:48:DB:23:BF:58:94:D2
authorityInfoAccess
  • OCSP - URI:http://e6.o.lencr.org
  • CA Issuers - URI:http://e6.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 3F:17:4B:4F:D7:22:47:58:94:1D:65:1C:84:BE:0D:12:
  • ED:90:37:7F:1F:85:6A:EB:C1:BF:28:85:EC:F8:64:6E
  • Timestamp : Oct 21 01:52:04.643 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:71:94:BC:88:94:C3:B2:C2:13:10:1F:C5:
  • 49:B1:E2:52:1A:40:F6:DF:54:03:4C:05:08:7A:C4:FC:
  • CC:B2:84:92:02:21:00:B6:E5:4A:7C:ED:02:34:36:5A:
  • E9:C3:8F:75:8D:59:CA:17:9E:31:81:F8:44:CD:35:EA:
  • A3:00:11:E9:F1:9F:EB
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CF:11:56:EE:D5:2E:7C:AF:F3:87:5B:D9:69:2E:9B:E9:
  • 1A:71:67:4A:B0:17:EC:AC:01:D2:5B:77:CE:CC:3B:08
  • Timestamp : Oct 21 01:52:04.686 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:41:E7:37:A4:B8:9A:18:A9:BD:39:4C:35:
  • 09:91:27:B3:6D:EE:F0:A0:79:50:33:91:A0:D3:0C:33:
  • F9:56:49:EB:02:20:61:26:8A:AC:11:00:09:35:75:77:
  • 5C:88:96:FC:5A:9C:09:88:A2:1C:28:F9:28:DF:E0:D5:
  • FB:C3:B3:39:5D:27

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.m0.rg.net
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid