SSL-Tools

SSL check results of arlinghausbuilders.net

NEW You can also bulk check multiple servers.

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

JSON Refresh

Report created Sun, 10 Dec 2023 03:34:49 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.arlinghausbuilders.net
207.250.212.92
 5
supported
arlinghaus.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
5 s

Outgoing Mails

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

Certificates

First seen at:

CN=arlinghaus.com

Certificate chain
  • arlinghaus.com
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • arlinghaus.com
Alternative Names
  • *.arlinghaus.com
  • *.arlinghaus.me
  • *.arlinghausbuilders.com
  • *.arlinghausbuilders.net
  • arlinghaus.com
  • arlinghaus.me
  • arlinghausbuilders.com
  • arlinghausbuilders.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2023-12-04
Not valid after
2024-03-03
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
51:92:72:3C:D4:C0:05:29:F0:7A:81:C3:0D:AF:DA:13:83:33:43:25:1C:F4:0F:91:D9:BF:58:53:B1:4B:0C:18
SHA1
F3:68:D6:40:38:6B:9E:C2:04:41:F2:22:1E:4B:3E:02:51:FE:01:07
X509v3 extensions
subjectKeyIdentifier
  • 26:7A:FC:56:91:71:43:21:26:5E:4B:08:48:09:50:77:C5:45:52:19
authorityKeyIdentifier
  • keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
authorityInfoAccess
  • OCSP - URI:http://r3.o.lencr.org
  • CA Issuers - URI:http://r3.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
  • 1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
  • Timestamp : Dec 4 04:20:58.447 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:A1:E0:18:BC:0D:E8:8C:5D:90:BB:74:
  • 3E:91:A6:72:5B:F0:84:13:69:C8:5B:BE:95:A3:69:5A:
  • AA:FD:5E:64:BB:02:21:00:E0:B9:22:09:2A:0F:22:04:
  • D1:B1:0C:F2:E7:0F:49:6C:A4:AD:B0:A0:21:A8:1B:53:
  • 86:E2:B5:3B:CE:E6:7B:76
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 29:D0:3A:1B:B6:74:AA:71:1C:D3:03:5B:65:57:C1:4F:
  • 8A:A7:8B:4F:E8:38:94:49:EC:A4:53:F9:44:BD:24:68
  • Timestamp : Dec 4 04:20:58.686 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:96:EC:2B:F3:83:65:5F:C6:47:EC:B2:
  • 95:1B:85:25:5B:E9:12:0E:DC:71:C3:BF:E9:94:A1:30:
  • E7:3F:13:24:A5:02:20:22:A1:10:C9:F6:FA:38:52:B3:
  • 5D:3D:88:06:9B:8D:64:8B:ED:67:51:A5:14:79:26:5B:
  • C1:29:67:90:D0:51:68