SSL-Tools

SSL check results of nanoid.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for nanoid.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 Thu, 21 Nov 2024 01:31:28 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
hal.nanoid.net
149.210.138.19
 10
supported
hal.nanoid.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=hal.nanoid.net

Certificate chain
  • hal.nanoid.net
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • hal.nanoid.net
Alternative Names
  • hal.nanoid.net
  • www.nanoid.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2024-10-02
Not valid after
2024-12-31
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
C0:8A:0D:AB:FD:7C:AD:62:AD:28:90:D4:77:32:E1:87:61:24:C9:8F:6B:75:B5:AA:4F:C2:3B:2A:8F:96:E3:A0
SHA1
90:F8:71:F5:F0:55:2B:D4:CD:D7:2C:22:09:3E:74:C4:A5:C0:65:59
X509v3 extensions
subjectKeyIdentifier
  • C8:AA:2E:F0:A1:90:D5:49:94:BD:B2:0D:5C:C3:8F:66:4D:3F:EA:DC
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.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 : Oct 2 05:30:13.579 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:64:DC:C5:B4:D8:56:4E:D1:65:34:22:B6:
  • 5D:46:85:49:28:1A:5A:98:9A:62:C4:40:89:30:8D:16:
  • 20:74:23:DF:02:21:00:DB:C7:B2:82:FC:91:A2:2A:72:
  • AD:5B:FE:55:C3:09:FB:1D:45:43:58:8F:36:E3:94:08:
  • E1:25:81:14:48:E4:BF
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E3:0A:E4:45:EF:BD:AD:9B:7E:38:ED:47:67:77:53:
  • D7:82:5B:84:94:D7:2B:5E:1B:2C:C4:B9:50:A4:47:E7
  • Timestamp : Oct 2 05:30:13.590 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:DF:02:D9:1F:B0:21:F8:33:8B:0A:18:
  • E3:78:F2:10:B3:BD:43:1D:B3:D6:FC:AF:BF:B3:92:B0:
  • 48:FE:CE:D0:C3:02:20:52:3A:58:51:46:60:EC:A7:5E:
  • DD:83:BF:EF:54:45:32:13:D2:DB:C5:2F:77:2F:19:5E:
  • 02:8E:BE:DB:3E:49:16