SSL check results of bravo.n-dns.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for bravo.n-dns.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

Report created Tue, 24 Sep 2024 09:07:26 +0000

We can not guarantee a secure connection to the mailservers of bravo.n-dns.net!

Please contact the operator of bravo.n-dns.net and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/bravo.n-dns.net

Servers

Incoming Mails

These servers are responsible for incoming mails to @bravo.n-dns.net addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
bravo.n-dns.net
194.59.206.110
Results incomplete
-
supported
not checked
DANE
missing
PFS
not checked
Heartbleed
not vulnerable
Weak ciphers
not checked
11 s
bravo.n-dns.net
2a03:4000:34:53a:4428:baff:fedc:94da
-
supported
bravo.n-dns.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
supported
  • ECDHE_RSA_WITH_RC4_128_SHA
  • SSL_RSA_WITH_RC4_128_SHA
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
14 s

Outgoing Mails

We have not received any emails from a @bravo.n-dns.net address so far. Test mail delivery

Certificates

First seen at:

CN=bravo.n-dns.net

Certificate chain
  • bravo.n-dns.net
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption

      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption

Subject
Common Name (CN)
  • bravo.n-dns.net
Alternative Names
  • bravo.n-dns.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2024-09-03
Not valid after
2024-12-02
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
FF:5C:E9:C7:16:A3:F3:19:74:AF:05:ED:74:8C:4A:1C:C2:F8:E4:94:9A:54:74:98:34:A5:11:08:89:98:E2:EC
SHA1
3B:F3:CD:1C:31:81:F9:C9:4E:C7:39:73:5B:25:5A:EA:F8:C1:D6:54
X509v3 extensions
subjectKeyIdentifier
  • 95:87:8A:16:18:50:57:0F:C4:7B:5D:86:2F:B3:4D:D6:0D:C7:5C:39
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • OCSP - URI:http://r10.o.lencr.org
  • CA Issuers - URI:http://r10.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 : Sep 4 00:22:15.234 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:5B:27:40:84:6A:4D:C9:CA:A6:32:E6:AE:
  • E7:B1:C3:74:01:9B:9D:F2:5E:E7:CF:0E:AC:A7:B0:29:
  • F6:3F:17:9C:02:20:5B:B7:76:D3:05:AD:A0:03:C8:8A:
  • 7F:56:95:35:87:64:D6:66:33:78:70:F0:1F:77:CC:8A:
  • 5E:E8:F3:09:05:BC
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 76:FF:88:3F:0A:B6:FB:95:51:C2:61:CC:F5:87:BA:34:
  • B4:A4:CD:BB:29:DC:68:42:0A:9F:E6:67:4C:5A:3A:74
  • Timestamp : Sep 4 00:22:15.282 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:C7:50:55:0A:42:3A:57:9A:C6:8C:A9:
  • 96:0B:4A:5A:8E:70:62:A8:7A:76:C2:CB:65:33:E9:2D:
  • 36:10:74:C4:D0:02:21:00:B4:CB:92:39:65:57:AA:2D:
  • BE:A3:9B:D7:B3:24:32:E9:4D:FA:A1:A0:4F:C5:63:11:
  • 49:03:4E:7E:04:52:DF:90