SSL-Tools

SSL check results of maxxor.org

NEW You can also bulk check multiple servers.

Discover if the mail servers for maxxor.org 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 Tue, 17 Jun 2025 18:59:52 +0000

The mailservers of maxxor.org can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @maxxor.org addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.maxxor.org
2a01:4f9:c010:195d::1
 10
supported
mail.maxxor.org
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
9 s
mail.maxxor.org
95.216.161.89
 10
supported
mail.maxxor.org
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
5 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.maxxor.org

Certificate chain
  • mail.maxxor.org
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.maxxor.org
Alternative Names
  • autoconfig.maxxor.org
  • autodiscover.maxxor.org
  • mail.maxxor.org
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2025-05-11
Not valid after
2025-08-09
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
BA:26:FE:23:A2:2B:B0:74:6E:80:CA:9D:0C:BA:72:80:21:1E:1F:54:D3:F6:51:5C:69:13:ED:44:C7:79:54:F3
SHA1
66:BF:97:D7:EC:46:4D:EC:35:1C:FD:3F:80:71:D4:7B:8A:8C:98:04
X509v3 extensions
subjectKeyIdentifier
  • AC:3D:23:F1:E8:E5:21:F5:EB:36:B2:FE:60:F6:FD:43:64:91:8B:BE
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r10.c.lencr.org/25.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : ED:3C:4B:D6:E8:06:C2:A4:A2:00:57:DB:CB:24:E2:38:
  • 01:DF:51:2F:ED:C4:86:C5:70:0F:20:DD:B7:3E:3F:E0
  • Timestamp : May 11 19:15:42.944 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:9A:19:76:D2:DE:C9:32:44:18:DD:5D:
  • 88:6E:34:85:A5:72:C2:8A:CE:C4:81:87:50:6F:67:C2:
  • DE:C6:B5:DF:4A:02:20:6E:82:84:BF:F0:91:12:B0:07:
  • E5:FE:FC:54:52:9F:0A:C7:C2:E2:8D:1E:07:55:7B:18:
  • E3:6D:36:03:5D:F1:EE
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:
  • 22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0
  • Timestamp : May 11 19:15:42.971 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:7C:7B:E0:9B:6E:97:48:B8:17:88:2A:1F:
  • F6:85:61:C6:21:7A:79:C7:D9:82:48:30:21:BA:50:B3:
  • 0C:7E:EE:C6:02:20:0A:B4:FE:D4:25:6B:74:60:D9:E8:
  • 49:F2:30:52:36:9C:F8:0B:44:28:4F:E2:0D:5A:64:AA:
  • 45:F6:B3:1E:E2:6A

DANE

DNS-based Authentication of Named Entities (DANE) is a protocol to allow X.509 certificates to be bound to DNS using TLSA records and DNSSEC.

Name Options DNSSEC Matches
_25._tcp.mail.maxxor.org
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid