SSL-Tools

SSL check results of brightonhappiness.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for brightonhappiness.com 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, 25 Jan 2025 00:38:23 +0000

The mailservers of brightonhappiness.com can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @brightonhappiness.com addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.brightonhappiness.com
104.152.168.12
 10
supported
brightonhappiness.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
6 s

Outgoing Mails

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

Certificates

First seen at:

CN=brightonhappiness.com

Certificate chain
  • brightonhappiness.com
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • E5
        • remaining
        • 384 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • brightonhappiness.com
Alternative Names
  • *.brightonhappiness.com
  • brightonhappiness.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E5
validity period
Not valid before
2024-12-22
Not valid after
2025-03-22
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
90:5A:BE:D1:A0:9D:D0:10:4E:BC:78:6A:2D:A2:AD:F4:67:CD:8A:85:DF:BA:4B:6F:06:23:E6:ED:72:F0:DC:14
SHA1
4D:39:88:AC:F9:43:3B:33:90:C9:94:A0:7E:39:BD:AC:66:23:0D:0F
X509v3 extensions
subjectKeyIdentifier
  • E4:6C:4D:9E:3F:94:AF:C5:F2:F6:7D:01:60:5E:4A:70:55:EA:11:DD
authorityKeyIdentifier
  • keyid:9F:2B:5F:CF:3C:21:4F:9D:04:B7:ED:2B:2C:C4:C6:70:8B:D2:D7:0D
authorityInfoAccess
  • OCSP - URI:http://e5.o.lencr.org
  • CA Issuers - URI:http://e5.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 73:20:22:0F:08:16:8A:F9:F3:C4:A6:8B:0A:B2:6A:9A:
  • 4A:00:EE:F5:77:85:8A:08:4D:05:00:D4:A5:42:44:59
  • Timestamp : Dec 22 06:54:40.247 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:68:64:26:7E:29:BA:8C:A8:00:F2:CA:2B:
  • 58:FF:AE:B7:25:6F:16:06:EB:86:22:67:09:1B:6F:28:
  • DD:C0:68:D3:02:20:00:95:D4:3D:AA:31:67:09:25:01:
  • B1:BF:B2:0F:2D:B0:3C:9C:7E:07:65:3E:CB:6E:09:41:
  • 23:49:34:EC:5D:C0
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : E0:92:B3:FC:0C:1D:C8:E7:68:36:1F:DE:61:B9:96:4D:
  • 0A:52:78:19:8A:72:D6:72:C4:B0:4D:A5:6D:6F:54:04
  • Timestamp : Dec 22 06:54:40.355 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:2C:E5:26:89:A1:CB:4B:2A:B4:F9:63:52:
  • 26:1D:B0:F3:66:D3:4B:05:0F:10:6B:D5:7B:B1:0B:CF:
  • 3A:D9:CC:73:02:21:00:E2:46:B7:F1:CA:CC:76:68:B8:
  • E1:43:C6:81:A6:6C:48:D9:BB:79:13:6C:D9:63:19:3D:
  • 61:1E:EC:43:7E:20:B4