SSL check results of mail2.noxant.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail2.noxant.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

Report created Tue, 23 Apr 2024 14:05:18 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail2.noxant.com
80.14.231.184
-
supported
mail.noxant.com
DANE
missing
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 @mail2.noxant.com address so far. Test mail delivery

Certificates

First seen at:

CN=mail.noxant.com

Certificate chain
  • mail.noxant.com
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

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

Subject
Common Name (CN)
  • mail.noxant.com
Alternative Names
  • autoconfig.noxant.com
  • autodiscover.noxant.com
  • cal.noxant.com
  • home.noxant.com
  • mail.noxant.com
  • mail2.noxant.com
  • share.noxant.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-15
Not valid after
2024-06-13
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
EF:4F:5F:EB:4F:2B:C8:F4:02:80:9D:67:9C:90:42:21:48:0B:6E:18:10:88:50:EC:0F:2D:7F:5C:85:D1:12:DD
SHA1
2C:1D:7D:76:E4:EA:96:81:FF:D7:AC:D3:82:2B:CC:9B:8A:40:15:C4
X509v3 extensions
subjectKeyIdentifier
  • 47:AC:99:D3:31:D6:19:3D:60:2A:57:D2:11:82:3D:93:8B:42:B4:F9
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 : Mar 15 10:58:16.413 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:32:FD:4B:99:FF:13:DE:DA:95:A2:73:AA:
  • 41:D3:1E:92:B7:86:0B:44:FB:2D:12:C3:88:E6:FE:60:
  • B7:A3:10:21:02:21:00:CD:42:BD:90:46:7A:E2:C0:A6:
  • B7:31:6D:B6:FB:9E:3A:A8:05:0C:41:27:FF:8B:62:7A:
  • A0:8D:95:6B:CB:4A:73
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 3B:53:77:75:3E:2D:B9:80:4E:8B:30:5B:06:FE:40:3B:
  • 67:D8:4F:C3:F4:C7:BD:00:0D:2D:72:6F:E1:FA:D4:17
  • Timestamp : Mar 15 10:58:16.409 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:C8:45:8E:D9:EE:B9:BF:F2:3F:14:26:
  • 16:C7:97:9B:A5:31:D9:1E:FD:6E:51:FF:65:C3:AA:58:
  • 62:9C:CC:E2:6C:02:21:00:A7:32:AE:94:84:78:ED:AA:
  • 49:39:E1:7C:F1:0B:77:84:94:63:53:A6:C4:DE:F2:A1:
  • 37:33:88:0C:98:14:49:E3