SSL-Tools

SSL check results of tsubame.or.jp

NEW You can also bulk check multiple servers.

Discover if the mail servers for tsubame.or.jp 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 Sat, 21 Dec 2024 01:30:27 +0000

The mailservers of tsubame.or.jp can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @tsubame.or.jp addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
ns.tsubame.or.jp
211.19.31.77
 0
supported
pop.echigo.ne.jp
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
22 s

Outgoing Mails

We have not received any emails from a @tsubame.or.jp address so far. Test mail delivery

Certificates

First seen at:

CN=pop.echigo.ne.jp

Certificate chain
  • pop.echigo.ne.jp
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • pop.echigo.ne.jp
Alternative Names
  • buildos.jp
  • echigo.ne.jp
  • internet025.ne.jp
  • mail.echigo.ne.jp
  • mail.internet025.ne.jp
  • mail.pavc.ne.jp
  • mail.px0256.ne.jp
  • mail.spnet.ne.jp
  • ns.tsubame.or.jp
  • pavc.ne.jp
  • pop.echigo.ne.jp
  • pop.internet025.ne.jp
  • pop.pavc.ne.jp
  • pop.px0256.ne.jp
  • pop.spnet.ne.jp
  • pop.tsubame.or.jp
  • pop3.pavc.ne.jp
  • px0256.ne.jp
  • spnet.ne.jp
  • tsubame.or.jp
  • www.pavc.ne.jp
  • www.spnet.ne.jp
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2024-12-12
Not valid after
2025-03-12
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
5B:B9:64:E3:DF:21:77:CA:73:8B:E9:61:33:A2:29:A7:1B:F8:2F:91:BD:F7:29:1B:94:47:00:1B:75:D8:A4:C8
SHA1
D7:3F:71:AF:BC:B9:3C:03:A3:F7:07:48:07:B1:C2:F4:71:3E:CD:58
X509v3 extensions
subjectKeyIdentifier
  • 84:AB:9A:4A:B9:77:18:F4:D5:AF:58:F5:15:59:A7:C5:41:97:D2:49
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 : 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 : Dec 12 03:32:20.397 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:D9:04:3E:F4:6C:16:95:E2:FC:3C:B1:
  • 20:12:46:80:F2:BD:BF:DB:A6:EA:E5:8F:5C:A7:B8:B5:
  • 52:B7:96:16:13:02:21:00:8F:97:20:DF:79:DB:B7:16:
  • CD:71:13:56:91:EC:CE:EE:A6:D1:C2:A7:D3:A8:C9:51:
  • F2:A9:B4:B7:E1:0C:24:B0
  • 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 : Dec 12 03:32:20.448 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:B3:25:C2:96:CD:CB:65:AC:DE:76:62:
  • 15:2F:E1:3A:E7:C9:ED:59:C9:03:A2:8C:8D:C5:64:9F:
  • 9E:F1:CD:14:0F:02:21:00:C2:CB:02:F5:4E:EF:27:87:
  • CB:12:6F:34:7B:C5:0E:67:C0:B3:FD:BA:AB:F6:85:A7:
  • 15:00:82:E2:44:80:FA:07