SSL-Tools

SSL check results of kitahama.or.jp

NEW You can also bulk check multiple servers.

Discover if the mail servers for kitahama.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, 14 Jun 2025 01:40:18 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mx.securemx.jp
210.130.202.96
 10
supported
securemx.jp
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
15 s
mx.securemx.jp
210.130.202.92
 10
supported
securemx.jp
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
14 s
mx.securemx.jp
210.130.202.93
 10
supported
securemx.jp
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
14 s
mx.securemx.jp
210.130.202.99
 10
supported
securemx.jp
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
15 s

Outgoing Mails

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

Certificates

First seen at:

CN=securemx.jp

Certificate chain
  • securemx.jp
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • securemx.jp
Alternative Names
  • *.p.securemx.jp
  • *.securemx.jp
  • securemx.jp
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-04-13
Not valid after
2025-07-12
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
B5:27:E7:51:FC:31:0D:45:D2:37:93:E2:E3:37:85:01:8A:30:4C:33:B4:E3:08:2B:7F:73:D5:6D:0F:D1:C6:4E
SHA1
A3:C2:29:D0:94:22:45:65:01:E0:5E:A0:42:7F:E5:B6:EC:DC:2A:47
X509v3 extensions
subjectKeyIdentifier
  • D2:8E:40:45:CD:19:46:29:E7:BA:A9:F2:03:6D:AE:0D:FC:8C:14:56
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
crlDistributionPoints
  • Full Name:
  • URI:http://r11.c.lencr.org/49.crl
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 : Apr 13 11:25:13.031 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:FF:BA:9D:84:16:5D:1F:7C:D7:1E:05:
  • 13:AC:A9:2E:DC:C5:7B:A0:1A:B2:4B:C4:E9:99:EC:AE:
  • 20:3B:46:8C:FB:02:20:4F:12:D6:7B:E1:D2:DA:45:31:
  • FB:EF:4D:D6:81:D1:5A:C0:AB:49:5F:AB:E3:C6:02:76:
  • 2D:0E:62:D9:B0:15:0D
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A4:42:C5:06:49:60:61:54:8F:0F:D4:EA:9C:FB:7A:2D:
  • 26:45:4D:87:A9:7F:2F:DF:45:59:F6:27:4F:3A:84:54
  • Timestamp : Apr 13 11:25:13.039 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:EC:BD:38:05:C7:64:47:86:55:12:43:
  • 31:79:99:D0:76:E4:F6:CD:D0:BE:75:C5:BC:CB:DF:69:
  • F9:FA:7E:BD:FC:02:21:00:B1:08:A2:A9:2C:FF:88:C4:
  • 0E:A6:0B:39:95:5A:6D:88:19:C6:ED:80:D3:87:98:EE:
  • 1E:40:1F:43:F2:5B:2F:B4