SSL check results of nmail.no

NEW You can also bulk check multiple servers.

Discover if the mail servers for nmail.no 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 Mon, 16 Sep 2024 10:53:12 +0000

The mailservers of nmail.no can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @nmail.no addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mx2.storstein-nett.no
109.247.192.115
0
supported
mx2.storstein-nett.no
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 @nmail.no address so far. Test mail delivery

Certificates

First seen at:

CN=mx2.storstein-nett.no

Certificate chain
  • mx2.storstein-nett.no
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption

      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

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

Subject
Common Name (CN)
  • mx2.storstein-nett.no
Alternative Names
  • autoconfig.mx2.storstein-nett.no
  • autodiscover.mx2.storstein-nett.no
  • cpanel.mx2.storstein-nett.no
  • cpcalendars.mx2.storstein-nett.no
  • cpcontacts.mx2.storstein-nett.no
  • ipv6.mx2.storstein-nett.no
  • mail.mx2.storstein-nett.no
  • mx2.storstein-nett.no
  • webdisk.mx2.storstein-nett.no
  • webmail.mx2.storstein-nett.no
  • whm.mx2.storstein-nett.no
  • www.mx2.storstein-nett.no
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2024-07-18
Not valid after
2024-10-16
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
70:85:D2:EF:8F:C6:0B:3B:83:FD:E6:82:C5:A7:61:F2:02:D2:F8:72:C1:69:0C:DF:A0:08:DB:64:99:59:B6:3C
SHA1
6E:93:F1:69:4B:C1:E4:50:BF:1C:5A:7D:25:29:83:7E:E9:20:1D:77
X509v3 extensions
subjectKeyIdentifier
  • 19:F4:84:9F:FD:36:FA:B3:84:6C:F3:C4:A8:97:2F:47:36:4C:33:4C
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 : 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 : Jul 18 19:22:36.503 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:F5:1C:B6:F4:2D:07:7E:C2:BE:E0:00:
  • 1B:50:FB:7C:1E:5C:8E:FF:C8:7D:3E:9E:FA:B2:B1:14:
  • C9:80:CD:4A:4C:02:21:00:AB:B8:77:B9:20:CA:67:4E:
  • 26:12:A4:5B:8F:46:74:8E:21:C0:14:31:8A:E8:FA:85:
  • 49:DB:E2:3D:70:E1:7C:A1
  • 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 : Jul 18 19:22:36.502 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:9F:82:9D:CD:36:41:54:5A:BE:55:A5:
  • BA:18:24:DA:E5:AF:2C:20:91:81:F5:4C:3B:08:EA:4C:
  • F1:1D:81:AA:E2:02:20:15:11:2B:C2:4E:3F:76:B4:BB:
  • 53:AC:39:2A:65:F0:4E:8F:0E:11:B4:DF:13:EA:86:36:
  • 95:D8:73:BF:9C:66:B7