SSL check results of synthgularity.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for synthgularity.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

Report created Tue, 16 Jul 2024 09:23:35 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mx1.synthgularity.net
81.35.121.254
10
supported
synthgularity.net
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
7 s

Outgoing Mails

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

Certificates

First seen at:

CN=synthgularity.net

Certificate chain
  • synthgularity.net
    • remaining
    • 256 bit
    • ecdsa-with-SHA384

      • E6
        • remaining
        • 384 bit
        • sha256WithRSAEncryption

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

Subject
Common Name (CN)
  • synthgularity.net
Alternative Names
  • *.synthgularity.net
  • synthgularity.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E6
validity period
Not valid before
2024-07-13
Not valid after
2024-10-11
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
79:B7:EA:8B:4F:6C:36:8C:2F:51:54:19:36:D3:01:7F:62:5F:6B:72:F7:0D:31:D7:1D:AE:4C:B6:E4:F2:45:A0
SHA1
2D:A7:3C:F9:1D:9C:28:CC:AD:73:D9:08:32:5F:A1:05:C3:36:B5:50
X509v3 extensions
subjectKeyIdentifier
  • 51:9B:D9:B0:72:C3:14:80:4B:07:12:B1:1E:4C:D3:E7:EE:67:D7:0E
authorityKeyIdentifier
  • keyid:93:27:46:98:03:A9:51:68:8E:98:D6:C4:42:48:DB:23:BF:58:94:D2
authorityInfoAccess
  • OCSP - URI:http://e6.o.lencr.org
  • CA Issuers - URI:http://e6.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 19:98:10:71:09:F0:D6:52:2E:30:80:D2:9E:3F:64:BB:
  • 83:6E:28:CC:F9:0F:52:8E:EE:DF:CE:4A:3F:16:B4:CA
  • Timestamp : Jul 13 22:22:46.059 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:02:A3:2C:CE:0E:69:76:94:4E:91:2F:49:
  • 3A:26:69:77:B0:17:E2:B6:72:71:64:29:78:E3:1D:75:
  • 48:32:E3:07:02:21:00:C8:6B:F1:D5:61:95:68:27:D2:
  • FE:28:A7:74:8B:F8:0C:58:A8:45:68:B2:3F:D9:0C:ED:
  • E9:CA:CD:89:89:0E:38
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 76:FF:88:3F:0A:B6:FB:95:51:C2:61:CC:F5:87:BA:34:
  • B4:A4:CD:BB:29:DC:68:42:0A:9F:E6:67:4C:5A:3A:74
  • Timestamp : Jul 13 22:22:46.061 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:88:57:18:7C:2B:ED:63:D6:30:AB:8E:
  • AF:B4:CB:DE:A1:03:08:ED:F5:00:B1:2C:F7:D7:D7:00:
  • EF:1B:FF:83:EB:02:21:00:C5:83:4C:3C:48:2F:EC:DA:
  • 32:F7:25:25:69:74:D1:A8:DE:56:87:B5:6D:52:D7:2D:
  • 12:D5:B1:7A:D6:76:96:4F

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.mx1.synthgularity.net
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid